1353NM Equipment Specific - Operator's Handbook Vol.1 - 3

NR5 Equipment Specific Operator’s Handbook
Alcatel 1350NM
Network Management
1353NM
Equipment management operations applicable to Alcatel
Network Elements supported by 1350 suite in Network
Release 5.x
Release 7.0 on
VOLUME 1/3:
Q3 NE Management Part 1
3AL 89062 AAAA Ed.01

1353NM NR5 EQP–SPEC. OPERATOR’S HANDBOOK
not permitted without written authorization from Alcatel.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
TABLE OF CONTENTS
1 HANDBOOK STRUCTURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3.1 Notes on Ed.01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 LIST OF NES SUPPORTED BY 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4 1353NM NR5 EQUIPMENT SPECIFIC HANDBOOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4.1 Contents of Volume 1/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.1.1 Q3 NEs Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.1 1st generation QB3* NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2.2 QB3* NEs Management – ADM & Microwave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3.1 1st generation terrestrial WDM and Submarine NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.1 Products, product-releases, versions and Customer Documentation . . . . . . . . . . . . . . 11
5.2 Handbook supply to Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.3 Aims of standard Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.4 Handbook Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.4.1 Changes introduced in the same product-release (same handbook P/N) . . . . . . . . . . . . 12
5.4.2 Supplying updated handbooks to Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.4.3 Changes due to a new product-release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
01 040130 V.SCORTECCI ITAVE V.PORRO ITAVE

L.FORESTA
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
1AA 00014 0004 (9007) A4 – ALICE 04.10
1353NM
NR5 EQP–SPEC. OPER. HDBK
Release 7.0 on
ED 01 SC. 1.1: HANDBOOK GUIDE
3AL 89062 AA AA 1 / 12
12
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
SC. 1.1: HANDBOOK GUIDE
12
3AL 89062 AA AA
2 / 12
1 HANDBOOK STRUCTURE
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 several product-releases starting from the following product-release:
PRODUCT ANV P/N

1353NM 3AL 89052 AAAA
PRODUCT RELEASE VERSION (N.B.) ANV P/N

1353NM 7.0 7.0.0 on 3AL 89053 AAAA
N.B. 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 3 / 12
12
1.3 History
VERSIONS AS INTERNAL DOCUMENTS

Specified at the beginning of each section.

RELEASED VERSIONS (as 3AL 89062 AAAA handbook)
ED Creation Scope Archived
01 January 2004 Creation YES
1.3.1 Notes on Ed.01
This handbook issue is relevant to 1353NM Rel.7.0 Version 7.0.0. validated software, which is conceived
for the management of Q3, SNMP, Q2 and QB3* Alcatel Network Elements supported by 1353NM.
The handbook won’t be changed 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
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 4 / 12
12
2 PRODUCT-RELEASE HANDBOOKS
For the standard Customer Documentation refer to the list inserted in the 1353NM main
Operator’s Handbook of the supplied release.
The main Operator’s Handbooks given here below is valid on the issue date of this
Handbook and is only referred, as an example, to the 1353NM Rel.7.0.
2.1 Handbooks related to the product’s software
Table 1. Handbooks related to the specific software application (example 1353NM Rel.7.0)
REF HANDBOOK ANV Part No.
[1] 1353NM Rel.7.0 Operator’s Handbook 3AL 89061 AAAA
[2] 1353 NM NE LIST Handbook 3AL 89063 AAAA

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 5 / 12
12
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
3AL 89062 AA AA 6 / 12
12
3 LIST OF NES SUPPORTED BY 1353NM
The NE list has been moved in the NE LIST Handbook [2]. The NE LIST Handbook contains the different
NE lists of the 1353SH/NM Release and Software Version starting from Release 7.0.
Notice that from Rel.7.0 the product name changed from 1353SH to 1353NM.
4 1353NM NR5 EQUIPMENT SPECIFIC HANDBOOK
This handbook is composed of the following volumes, main parts and Manuals:
4.1 Contents of Volume 1/3
SECTION 1.1: HANDBOOK GUIDE (This document)
The Handbook Guide gives general information on the application and use of the Handbook.
4.1.1 Q3 NEs Management Part 1
SECTION 1.2: Q3 NEs Management (2nd generation Q3 NEs)
The aim of this document is to help the operator understand, configure and manipulate Network Elements
(NEs) easily, using the SDH Manager Operation System (OS). The different functionalities related to the
equipment views, the menu items and the different actions that can be undertaken from these views are
described in detail.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 7 / 12
12
4.2.1 Q3 NEs Management Part 2

SECTION 2.1: 1641SX & 1664SX ALARM REFERENCE Manual
This document is written for operators, who want to get an overview of all 1641SX & 1664SX alarms
indicated by the alarm manager, their causes, their effects on service and ways to get out of alarm
situations.
SECTION 2.2: 1674 LAMBDA GATE ALARM REFERENCE Manual
This document is written for operators, who want to get an overview of all Lambda Gate alarms indicated
by the alarm manager, their causes, their effects on service and ways to get out of alarm situations.
4.2.2 QB3* NEs Management – ADM & Microwave
SECTION 2.3: QB3* NE MANAGEMENT Manual
(NEs) easily, using the SDH Manager Operation System (OS). The different functionalities related to the
SECTION 2.4: QB3* NE TRANSMISSION MANAGEMENT Manual
The aim of this document is to help the operator understand the different functionalities related to the
Transmission for the QB3* NEs.
SECTION 2.5: QB3* NE SYNCHRONIZATION MANAGEMENT Manual
The aim of this document is to help the operator understand the different functionalities related to the
synchronization for the QB3* NEs.
SECTION 2.6: QB3* NE PERFORMANCE MONITORING MANAGEMENT Manual
The aim of this document is to describe the operations related to the configuration of the counting interval
for each performance measurement point, configuration of the quality thresholds or to obtain a collection
performance data.
SECTION 2.7: QB3* NE SOFTWARE MANAGEMENT Manual
The aim of this document is to describe the operations related to the management of the NE software.
SECTION 2.8: ADM MANAGEMENT Manual
This document describes all the specific functionalities provided by the1353NM Manager to manage the
ADM equipments and their extensions managed by the SH since SH3.1.
SECTION 2.9: OAS AND OA-TPD MANAGEMENT Manual
This document describes all the functionalities provided by the 1353NM to manage the OAES Submarine
Amplifiers and 1610OA–TPD Transponders
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 8 / 12
12
SECTION 2.10: REGENERATOR MANAGEMENT Manual
This document describes all the functionalities provided by the 1353NM to manage the 1666SR and
1655SR Optical Regenerator NEs.
SECTION 2.11: SDH MICROWAVE MANAGEMENT Manual
This document describes all the functionalities provided by the SDH Manager to manage the SDH
Microwave equipments.
This document refers to SDH Microwave managed by the SH since SH3.0.
SECTION 2.12: PDH MICROWAVE MANAGEMENT Manual
This document describes all the functionalities provided by the 1353NM to manage the PDH Microwave
products.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 9 / 12
12
4.3.1 1st generation terrestrial WDM and Submarine NEs

SECTION 3.1: WDM 3.x TERRESTRIAL MANAGEMENT Manual
This document describes the specific functionalities provided by the 1353NM to manage the line system
1686WM Wavelength Division Multiplexer (WDM), commonly refered to as the 1686WM or WDM
Terrestrial Network Element.
This document refers only to the 1686WM release 3.1 / 3.2 managed by the NM.
SECTION 3.2: WDM 2.x TERRESTRIAL MANAGEMENT Manual
This document describes the specific functionalities provided by the 1353NM to manage the line system
1686WM Wavelength Division Multiplexer (WDM), commonly refered to as the 1686WM or WDM
Terrestrial Network Element.
This document refers only to the 1686WM release 2.1 / 2.1d managed by the SH since SH3.1.
SECTION 3.3: WDM SUBMARINE PFE Manual
This document describes all the functionalities provided by the 1353NM to manage the Wavelength
Division Multiplexer (WDM) Submarine Power Feeding Equipments.
SECTION 3.4: WDM SUBMARINE OALW16 AND OALW40 Manual
This document describes all the functionalities provided by the 1353NM to manage the 2.5 Gb/s
Wavelength Division Multiplexer (WDM) Submarine NEs .
SECTION 3.5: WDM SUBMARINE OALW40 (TERA10) Manual
This document describes all the functionalities provided by the 1353NM to manage the 10 Gb/s
Wavelength Division Multiplexer (WDM) Submarine NEs .
SECTION 3.6: WDM SUBMARINE OALW40 (TERA10) Alarms Manual
This document describes all the functionalities provided by the 1353NM to manage the TERA10 alarms
.
SECTION 3.7: WDM SUBMARINE URW 1666UT / OA Manual
This document describes all the functionalities provided by the 1353NM to manage the unrepeatered
Submarine NEs .
SECTION 3.8: SNMP MELODI Manual
This document describes all the functionalities provided by the 1353NM to manage the SNMP Melodi
Equipments.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 10 / 12
12
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 12.
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
3AL 89062 AA AA 11 / 12
12
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:
• 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
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.2 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).
5.4.3 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.
1AA 00014 0004 (9007) A4 – ALICE 04.10
END OF DOCUMENT
3AL 89062 AA AA 12 / 12
12
1353NM NR5 EQP–SPEC. OPERATOR’S HANDBOOK
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
HISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
REFERENCED DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.1.2 Edition scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.1.3 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.2 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.3 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2 MENU COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.1 Menu Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.2 1353SH Menu Commands for OMSN using P.3.x. USM version . . . . . . . . . . . . . . . . . . . . 35
2.3 1353SH Menu Commands for W/OMSN using P.4.x. USM version . . . . . . . . . . . . . . . . . . 42
2.5 1353SH Menu Commands for UHR, LHR 1, UHRN with P.5.x. USM version . . . . . . . . . 56
2.7 1353SH Menu Commands for OMSG using USM P.4.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
2.8 1353SH Menu Commands for OMSG using USM P.7.x. . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
2.9 1353SH Menu Commands for 1674LG Rel.1.1 using USM P.8.x. . . . . . . . . . . . . . . . . . . . 84
2.10 1353SH Menu Commands for 1686 WM Rel. 3.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
2.11 1353SH Menu Commands for 1686 WM Rel. 3.4A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
2.12 1353SH Menu Commands for 1686WM Rel. 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
2.13 1353SH Menu Commands for 1640 WM Rel. 1.2A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
2.14 1353SH Menu Commands for 1640 WM Rel. 1.2C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
2.15 1353SH Menu Commands for 1640 WM Rel. 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
2.16 1353SH Menu Commands for 1640WM Rel. 3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
2.17 1353SH Menu Commands for OPS Rel. 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
2.18 1353SH Menu Commands for OCP Rel. 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
2.19 1353SH Menu Commands for 1696MS Rel.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
2.20 1353SH Menu Commands for 1696MS Rel.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
01 040130 V.SCORTECCI ITAVE V.Porro ITAVE

L.Foresta H.Hottenbacher
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
1AA 00014 0004 (9007) A4 – ALICE 04.10
1353NM
NR5 EQP–SPEC. OPER. HDBK
Release 7.0 on
ED 01 SC.1.2: Q3 NE MANAGEMENT
3AL 89062 AA AA 1 / 926
926
3 NE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
3.1 NE management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
3.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
3.2 Allow or Inhibit NE Craft access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

3.2.1 Switching from the OS to the Craft access state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

3.2.2 Switching from the Craft access state back to the OS access state . . . . . . . . . . . . . . . . 144
3.3 Changing NE Address (only available for W/OMSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
3.4 USM Time Configuration / Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
3.4.1 Set Alarm Severities (for W/OMSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
3.4.2 Set Alarm Severities (for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
3.5 Alarm Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
3.5.1 Alarm Severities Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
3.5.2 Alarm Severity Assignment Profile Management (ASAP) . . . . . . . . . . . . . . . . . . . . . . . . . 157
3.5.3 Alarm severity editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
3.5.4 Allow/Inhibit Alarm Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
3.5.5 Alarm re–synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
3.5.6 Refresh / Close / Exit View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
3.6 Navigation Between Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
3.6.1 Navigation to Management Domain Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
3.6.2 Navigation Between Different Hierarchical Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
3.6.3 Navigation To Previous View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
3.6.4 Navigation Using “Open” Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
3.6.5 Navigation using the Popup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
3.7 User Preferences (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
3.7.1 Save User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
3.7.2 Load User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
3.7.3 Delete User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
3.8 Clipboard Dialog (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
3.8.1 Using the Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
3.8.2 Using the Structure Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
3.9 Drag and Drop (DnD) (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
3.9.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
3.9.2 Examples of Operational Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
3.10 Print Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
3.11 Show Matrix Type (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
4 SECURITY MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

4.1 Security Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
4.2 Check Level Configuration (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
4.2.1 ACD Check at NE Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
4.2.2 ACD Check at Port Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
4.2.3 No Check on Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
4.3 Access Control Management on Port Level (only available for OMSG) . . . . . . . . . . . . . 186
4.4 Manager List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
4.5 NE Port/User Assignment (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
5 ROOM VIEW (ONLY AVAILABLE FOR OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
5.2 View Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
5.3 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
5.3.1 Navigation using the Room Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
1AA 00014 0004 (9007) A4 – ALICE 04.10
5.3.2 Navigation using the Popup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

5.4 Rack Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
3AL 89062 AA AA 2 / 926
926
6 EQUIPMENT OVERVIEW (ONLY AVAILABLE FOR OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6.2 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
6.2.1 View Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
6.2.2 Popup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

6.2.3 Expand/Hide Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

6.2.4 Navigate to... Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6.3 Add Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.4 Clipboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
7 BOARD/SUBRACK MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

7.1 Board / Subrack / Rack / NE Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
7.2 Board management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
7.2.1 OMSG Board management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
7.2.2 W/OMSN Board management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
7.2.3 Multi Access Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
7.3 Board View Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
7.4 Board States and EPS States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
7.5 Navigation Commands in Board View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
7.5.1 Show Supporting Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
7.5.2 Navigate to Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
7.5.3 Navigate to Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
7.5.4 ATM Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7.6 ATM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7.7 Cable configuration (only applicable to OMSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
7.8 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
7.8.1 Rack Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
7.8.2 Subrack Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
7.8.3 Board Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
7.9 Board Configuration for WDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
7.9.1 Output Power Level Configuration for 1640WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
7.9.2 Frequency and grid configuration (available only for 1640WM) . . . . . . . . . . . . . . . . . . . . 252
7.9.3 Pumps Configuration (available only for 1640WM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.9.4 Amplifier Msv configuration (available only for 1640WM) . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.9.5 MSV Configuration (available only for 1640WM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
7.9.6 Alarm threshold configuration (If supported by the board) . . . . . . . . . . . . . . . . . . . . . . . . . 255
7.9.7 Payload Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
7.9.8 Current intantaneous measurements on 1696MS and 1640WM . . . . . . . . . . . . . . . . . . . 260
7.9.9 Optical Protection Configuration for 1696MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
7.9.10 OAC amplifier board output setting on 1696MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
7.9.11 Variable Optical Attenuator tuning on 1696MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
7.9.12 Board menu options of 1686WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
8 DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
8.1 Alarms Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
8.2 Event Log / Log Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
8.3 View Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
8.4 Abnormal Condition (not available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
9 EQUIPMENT PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
1AA 00014 0004 (9007) A4 – ALICE 04.10
9.2 EPS Status (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

9.2.1 Navigation between views in the EPS status dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
9.3 EPS Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
3AL 89062 AA AA 3 / 926
926
9.4 EPS Configuration (not available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
9.5 Switching EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
9.6 EPS Overview (not available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

10 MULTIPLEX SECTION PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

10.1 Architecture types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
10.2 MSP Create (not available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
10.2.1 MSP creation on 1670SM R.3.0B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
10.3 MSP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
10.3.1 MSP modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
10.4 MSP Delete (not available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
10.5 Display of Protection State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
10.6 MSP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
10.7 MSP overview (not available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
10.8 MSP Status (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
10.9 Setting up linear MSP with SH–RM interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
10.9.1 Alarm behaviour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
11 RADIO MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

11.1 Radio protection management for UHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
11.2 UHRN equipment configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
11.2.1 UHRN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
11.2.2 EPS protection on UHRN 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
11.3 LHR Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
11.3.1 BER Not Intrusive on LHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
11.4 EPS protection on UHR 1.0, UHR 2.0 and UHRN 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
11.5 RPS (Radio Protection Switching) Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
11.5.1 RPS on UHR 1.0 and UHRN 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
11.5.2 RPS on UHRN 2.0, LHR 1.0 and UHR 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
11.6 RFCOH (Radio Frequency Channel Overhead) management on LHR . . . . . . . . . . . . . . 385
11.6.1 RFCOH Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
11.6.2 RFCOH Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
11.6.3 RFCOH Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
11.7 ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
11.7.1 ATPC Power Setting on UHR 1 and on UHRN 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
11.7.2 ATPC on UHRN 2.0, LHR 1.0 and UHR 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
11.8 Static Delay on UHR 1 and UHRN 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
11.9 Frequency / Frequency Agility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
11.9.1 Frequency on LHR 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
11.9.2 Frequency Agility on UHR and UHRN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
11.10 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
11.11 Power Measurement File Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
11.12 Squelch Management on LHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
11.13 Gain Management on LHR 1.0, UHR 2.0 and UHRN 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . 415
11.14 Hop Trace Management on LHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
11.15 Radio Abnormal Condition on LHR 1.0, UHR 2.0 and UHRN 2.0 . . . . . . . . . . . . . . . . . . 418
11.16 Frequency Reuse on LHR and Carrier Status on UHR and UHRN 2.0 . . . . . . . . . . . . . 419
11.17 Equalization Delay on LHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
11.18 V.C.O. (Voltage Control Oscillator) Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
12 PORT VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

1AA 00014 0004 (9007) A4 – ALICE 04.10
12.1 View Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

12.2 Port View Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
12.2.1 Optical Laser Configuration / Show Optical Configuration . . . . . . . . . . . . . . . . . . . . . . . . 427
3AL 89062 AA AA 4 / 926
926
12.2.2 Automatic Laser Shutdown Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
12.2.3 Single Fiber Configuration (only available for W/OMSN) . . . . . . . . . . . . . . . . . . . . . . . . . 432
12.3 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
12.3.1 Line and internal Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
12.3.2 Loopback Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

12.3.3 Loopback Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

12.4 Concatenation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
12.4.1 Concatenation on OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
12.4.2 Concatenation on W/OMSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
12.5 Ms Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
12.6 PDH Line Length Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
12.7 Set Retiming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
12.8 Show Supporting Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
12.9 Navigation Commands in Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
12.9.1 Navigate to Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
12.9.2 Navigate to Equipment Overview (available on OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . 455
12.9.3 Navigate to MSP Related Unit (available on OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
12.9.4 Navigate to Msspring View (available on OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
12.10 Port View Configuration for 1540 PO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
12.10.1 NT Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
12.11 Optical Port Configuration for WDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
12.11.1 OGPI Port View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
12.11.2 Show Supporting Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
12.11.3 Navigate to Transmission view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
12.11.4 FEC Enabled on 1640WM and 1686WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
12.11.5 Display channel Frequency on 1640WM and 1686WM . . . . . . . . . . . . . . . . . . . . . . . . . 468
12.11.6 Current Counters Values Display (for 1686WM without PM) . . . . . . . . . . . . . . . . . . . . . 469
12.11.7 Payload configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
12.11.8 Shutdown criteria configuration on 1640WM and 1686WM . . . . . . . . . . . . . . . . . . . . . 470
12.11.9 Performance option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
12.11.10 SDH Section Monitoring – Trail Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
12.11.11 Path trace configuration on 1686WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
12.11.12 Cable configuration on 1696MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
12.11.13 OTS/OMS port view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
12.11.14 APSD Configuration on 1686WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
12.11.15 APS configuration on 1696WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
12.11.16 OSC Synchronization Configuration on 1686WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
12.11.17 Cross Connection management on 1696MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
12.11.18 Optical Add/Drop configuration on 1686WM and 1640WM . . . . . . . . . . . . . . . . . . . . . 480
12.11.19 BER Threshold configuration on 1640WM and 1686WM . . . . . . . . . . . . . . . . . . . . . . 482
12.11.20 OSC BER Threshold configuration on 1686WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
12.11.21 Show OCH port view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
12.11.22 Loopback management for WDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
13 PORT DETAILS DIALOG (ONLY AVAILABLE FOR OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491

13.1 Port Details Dialog Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
13.1.1 TP Notebook Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
13.1.2 TP Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
13.1.3 Port Functional State Information Message Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
13.1.4 Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
13.1.5 Button Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
1AA 00014 0004 (9007) A4 – ALICE 04.10
13.1.6 The Pop-Up Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

13.2 TP Object Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
13.3 Port Details Dialog Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
3AL 89062 AA AA 5 / 926
926
13.3.1 Adding TPs to the Port Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
13.3.2 Removing TPs from the Port Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
13.3.3 Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
13.3.4 Alarm Persistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

13.3.5 PM Current Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500

13.3.6 Switching to MSP Related Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
13.3.7 Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
14 TRANSMISSION VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
14.2 View Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
14.3 View Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
14.3.1 View Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
14.3.2 Number of TPs Displayed in Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
14.3.3 Naming TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
14.3.4 Show Panner (on OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
14.3.5 Shifting Large Views (on OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
14.3.6 Dynamic View Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
14.3.7 Popup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
14.4 Add TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
14.4.1 Default Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
14.4.2 Search Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
14.4.3 Common Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
14.5 Navigation Commands in Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
14.5.1 Expand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
14.5.2 Hide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
14.5.3 “Port Details”, “Show Supported Board” and “Navigate to...” Commands . . . . . . . . . . . 521
14.5.4 Show Supported Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
14.5.5 Navigate to Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
14.5.6 Navigate to Equipment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
14.6 TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
14.6.1 J0 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
14.6.2 High Order TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
14.6.3 Low Order TP Configuration (only available on OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . 531
14.7 PDH TP / TP Frame Mode – Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
14.8 Alarm Persistency Time Configuration (on OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
14.9 Degraded Signal Threshold / TP Threshold Configuration . . . . . . . . . . . . . . . . . . . . . . . 538
14.9.1 Degraded Signal Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
14.9.2 TP Thresholds Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
14.10 Terminate / Disterminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
14.10.1 Terminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
14.10.2 Disterminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
14.11 POM/SUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
14.11.1 POM/SUT Creation/Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
14.11.2 POM/SUT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
14.12 Structure TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
15 CROSS-CONNECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
15.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
15.1.2 Multiplex Structures for SDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
1AA 00014 0004 (9007) A4 – ALICE 04.10
15.1.3 Definition of Termination Points (TP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560

15.1.4 Mapping Tables: TP Names on OMSG and W/OMSN . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
15.1.5 Cross-Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
3AL 89062 AA AA 6 / 926
926
15.1.6 Cross-Connection Protection (SNCP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
15.2 Cross-Connection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
15.3 Create/Modify Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
15.3.1 Cross-Connection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
15.3.2 Create a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585

15.3.3 Modify a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591

15.4 Activate/Deactivate/Delete Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
15.4.1 Activate a Cross-Connection (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . 595
15.4.2 Deactivate a Cross-Connection (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . 595
15.4.3 Delete a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
15.5 Operative Sequence to execute Cross-Connections (for W/OMSN) . . . . . . . . . . . . . . . 596
15.6 Split and Join Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
15.6.1 Split a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
15.6.2 Join Two Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
15.7 Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
15.8 Port Switch Over (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
15.9 Blocking Information (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
15.10 Show Cross Connected TPs / Show All Cross Connected TPs . . . . . . . . . . . . . . . . . . 607
15.11 Cross Connections for 1696MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
15.11.1 Cross Connections management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
16 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

16.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
16.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
16.1.2 Supported Performance Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
16.1.3 Far End Performance Counting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
16.1.4 Bidirectional counting (24 h Bi) for QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
16.1.5 End to End (e–e 24h) Performance Counting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
16.1.6 Performance Monitoring on AU–PJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
16.1.7 Performance Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
16.1.8 Performance Monitoring History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
16.1.9 Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
16.2 PM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
16.2.1 EML–OS Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
16.3 PM Threshold Table Creation / Modification / Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
16.3.1 Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
16.3.2 Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
16.3.3 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
16.4 PM Threshold Table Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
16.5 Display PM Current Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
16.6 Display PM History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
16.7 Performance Monitoring for WDM equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
16.7.1 Performance monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
16.8 Show Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
16.8.1 Performance monitoring visualization (PMV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
17 SYNCHRONIZATION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

17.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
17.1.1 Displaying the Synchronization View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
17.1.2 Synchronization View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
17.2 Synchronization commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
1AA 00014 0004 (9007) A4 – ALICE 04.10
17.2.1 Timing Source Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666

17.2.2 Create Timing Source (only available for OMSG – USM 8.x) . . . . . . . . . . . . . . . . . . . . . 670
17.2.3 Synchronization Protection Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
3AL 89062 AA AA 7 / 926
926
17.2.4 Synchronization Protection Commands for OMSG – USM 7.x . . . . . . . . . . . . . . . . . . . . 675
17.2.5 Synchronization Protection Commands for OMSG – USM 8.x . . . . . . . . . . . . . . . . . . . . 676
17.2.6 Synchronization Configuration for T0/T4 and T4 squelch criteria . . . . . . . . . . . . . . . . . . 677
17.2.7 Output Configuration (only available for OMSG – USM 8.x) . . . . . . . . . . . . . . . . . . . . . . 680

17.2.8 SSU Configuration (only applicable to W/OMSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683

17.2.9 Remove Timing Reference / Remove Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
17.2.10 Set and Remove T0 Equal T4 (only available for W/OMSN) . . . . . . . . . . . . . . . . . . . . 685
17.2.11 Connect / Disconnect T0–>T4 (only available for OMSG) . . . . . . . . . . . . . . . . . . . . . . . 685
17.2.12 Change T4 <–> T5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
17.2.13 Change 2MHz –>2Mbit (only available for W/OMSN USM 5.x, 6.x) . . . . . . . . . . . . . . 688
17.2.14 Frame Mode Configuration (only available for W/OMSN) . . . . . . . . . . . . . . . . . . . . . . . 690
17.2.15 T0 Test Configuration (only applicable to OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
17.2.16 Transmission of SSM Quality Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693
17.2.17 Show Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
18 MS–SPRING MANAGEMENT FOR W/OMSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695

18.1 MS–SPRING Management for ADM Equipments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
18.1.1 2–Fiber MS–SPRING description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
18.1.2 4–Fiber MS–SPRING description ( not actually supported ) . . . . . . . . . . . . . . . . . . . . . . 703
18.1.3 NPE ( 4 Fiber MS–SPRING transoceanic ) description . . . . . . . . . . . . . . . . . . . . . . . . . . 704
18.1.4 Different protection mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
18.2 MS–SPRING Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
18.2.1 MS–SPRing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
18.2.2 Squelching table with Terrestrial applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
18.2.3 Traffic Map with Transoceanic application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
18.2.4 Traffic map table description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
18.2.5 Symbolic representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
18.2.6 Ring Normal / Extra–Traffic Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
18.2.7 Activate, Deactivate and Delete commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
18.3 MS–SPRING Protection Status – Commands for NPE Application . . . . . . . . . . . . . . . . 739
18.3.1 4F MS–SPRing protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
18.3.2 External commands (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
18.3.3 4F MS–SPRing dual protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
18.3.4 Main differences between 1660SM Rel.3.1/3.2/3.3 and 1670SM Rel.3.0 . . . . . . . . . . . 757
18.3.5 4F Protection Status Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
18.3.6 Protocol Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
18.4 MS–SPRING Protection Status – Commands for 2F Terrestrial Application . . . . . . . . 784
18.4.1 2F MS–SPRing protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
18.4.2 External commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
18.4.3 2F MS–SPRing dual protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
18.4.4 2F Protection Status Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
19 MS-SPRING MANAGEMENT FOR OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817

19.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
19.2 Create/Delete MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
19.2.1 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
19.2.2 Create MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
19.2.3 Delete MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
19.3 Activate/Deactivate MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
19.4 Modify MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
19.4.1 Ring Traffic Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
1AA 00014 0004 (9007) A4 – ALICE 04.10
19.4.2 Ring Map Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831

19.4.3 Squelching Table Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
19.4.4 Wait to Restore Time Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
3AL 89062 AA AA 8 / 926
926
19.5 Display MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
19.5.1 Display MS-SPRing in MS-SPRing view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
19.5.2 Display MS-SPRing in Transmission view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
19.5.3 Display MS-SPRing in Port view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
19.6 Protection States and Commands for 2-Fiber Classic MS-SPRing . . . . . . . . . . . . . . . . 838
19.6.1 Node States Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838

19.6.2 Externally Initiated Protection Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
19.6.3 Protection State Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
19.6.4 MS-SPRing Protocol Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
20 ATM CONFIGURATION (ONLY AVAILABLE FOR W/OMSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . 845

20.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
20.2 ATM board TTPs creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
21 SOFTWARE MANAGEMENT (NOT AVAILABLE FOR OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . 849

21.1 Generalities and descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
21.1.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
21.1.2 Software Management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
21.2 Software Download Management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
21.3 Init download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
21.4 SW package Activation and Units information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
21.5 Servers Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
21.6 On Board Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
21.6.1 Generalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
21.7 Simulator operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
21.7.1 Starting the simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
21.7.2 Stopping the simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
21.7.3 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
21.7.4 View of configuration during Q3 isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
21.7.5 Off–line configuration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
21.8 Mib management starting from SH5.5 for NE with OBS . . . . . . . . . . . . . . . . . . . . . . . . . . 874
21.8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
21.8.2 MIB align–up descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
21.8.3 MIB align–up operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
21.8.4 MIB align–down and activate descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
21.9 Mib management without OBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
21.9.1 MIB backup and restore field options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
21.9.2 MIB backup, restore and delete procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
21.10 Restart NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
21.11 ATM Installation notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
22 OVERHEAD MANAGEMENT (NOT AVAILABLE FOR OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . 885

22.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
22.2 OH Connection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886
22.3 Overhead views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
22.4 OH Cross Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
22.4.1 Cross-Connection Management dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
22.5 OH TP creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
22.6 OH TP deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
22.7 OH Phone Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
1AA 00014 0004 (9007) A4 – ALICE 04.10
23 ROUTING MANAGEMENT (NOT AVAILABLE FOR OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897

23.1 Overview on Communication and Routing Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
23.1.1 Partitioning into Routing Subdomains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
23.1.2 Partitioning into separate Routing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
3AL 89062 AA AA 9 / 926
926
23.1.3 IP over OSI tunneling for ATM/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
23.1.4 OSI over IP tunneling on QB3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
23.2 Communication and routing views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
23.3 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901

23.4 OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903

23.5 NTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
23.6 LAPD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
23.7 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
23.8 Reachable Address Prefixes Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
23.9 Manual ES Adjacencies Table Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
23.10 IP Static Routing Configuration (USM 6.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913
23.11 OSPF Area Table Configuration (USM 6.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
23.12 IP Address Configuration of Point–to–Point Interfaces (USM 6.x) . . . . . . . . . . . . . . . . 916
23.13 ISA board IP Address (USM 6.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
23.14 IP over OSI (USM 6.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
24 EXTERNAL POINTS MANAGEMENT (NOT AVAILABLE FOR OMSG) . . . . . . . . . . . . . . . . . . 921

24.1 Displaying external points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
24.1.1 Expanding or reducing external points list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
24.2 External points configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 10 / 926
926
LIST OF FIGURES AND TABLES
FIGURES
Figure 1. OMSN Menu bar for P.3.x USM version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Figure 2. W/OMSN Menu bar for P.4.x. USM version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 4. WMSN Menu bar for P.5.x. USM version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 6. OMSG Menu bar for 4.x USM version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 7. OMSG Menu bar for 7.x USM version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 8. 1674LG Menu bar for 8.x USM version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 9. 1686WM Rel 3.3 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 10. 1686WM Rel. 3.4A Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 11. 1686WM Rel. 3.5 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 12. 1640 WM Rel. 1.2A Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 13. 1640 WM Rel. 1.2C Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 14. 1640WM Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Figure 15. 1640WM Menu bar (continued) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 17. 1640 WM Menu bar (continued) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Figure 20. 1640WM Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Figure 26. OPS R1.0 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 27. OCP R.1.0 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Figure 28. 1696MS R1.0 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Figure 29. 1696MS R.1.1 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 30. Local (CT) mode selectable from Supervision, Access State USM view . . . . . . . . . . . . 143
Figure 31. Access state icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Figure 32. Example of Local Configuration box dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Figure 33. Consulting and/or setting the local NE time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 34. NE Time dialogue box on W/OMSN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 35. NTP protocol icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Figure 36. Example of Set Alarm Severities window (USM 5.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Figure 37. ASAP Edition window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 38. Set ASAP Dialog (USM 7.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Figure 39. Configuring Alarm Severity Assignment Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 40. Example of ASAPs Management dialogue box (USM 5.x). . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 41. ASAP Edition dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 42. Inhibit alarm notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 43. Alarm Panel with Disabled Alarm Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Figure 44. Alarm Panel with Enabled Alarm Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 45. Save Preference Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Figure 46. Load Preference Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 47. Clipboard Dialog Opened from the “POM/SUT Creation/Deletion” Dialog . . . . . . . . . . . . 172
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 48. POM/SUT Creation in Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Figure 49. Select Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 50. Print to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
3AL 89062 AA AA 11 / 926
926
Figure 51. Print to Export File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Figure 52. Installation Details – Show Matrix Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Figure 53. ACD Level Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Figure 54. Set the Port ACD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Figure 55. Supervision menu for setting the Manager List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Figure 56. Set the NE Manager List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Figure 57. NAD Object Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Figure 58. New NAD1 elementary object definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Figure 59. OADNAD1 – operator group combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Figure 60. Activation of OAD–FAD combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Figure 61. Killing lss process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Figure 62. Room View with One Room and Different Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Figure 63. Modify User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Figure 64. Navigation in the Equipment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 65. Appearance of the Equipment Last Shown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Figure 66. Popup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 67. Add Equipment to the Equipment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 68. Equipment Filter Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Figure 69. Clipboard of the Equipment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Figure 70. Clipboard – Equipment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Figure 71. Equipment Overview – Subrack level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Figure 72. Equipment Overview – Rack level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Figure 73. Equipment Overview – Equipment level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 74. Equipment menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 75. Setting a Board in Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Figure 76. Setting a Board Out of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Figure 77. Setting a board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Figure 78. List of different equipped boards relative to an NE slot (example). . . . . . . . . . . . . . . . . . . 219
Figure 79. Replaceable Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Figure 80. Removing a board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Figure 81. NE Equipment View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Figure 82. Software Description dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 83. Multi access board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Figure 84. Error indications removing a board equipped with its modules . . . . . . . . . . . . . . . . . . . . . 227
Figure 85. Change Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Figure 86. Example of a Board View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Figure 87. Detailed Board State example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Figure 88. EPS Protection State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Figure 89. Show Supporting Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Figure 90. Navigate to Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Figure 91. Navigate to Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Figure 92. ISA navigation option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Figure 93. ATM Configuration option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Figure 94. Cable configuration selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Figure 95. Cable configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Figure 96. Remote Inventory confirmation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Figure 97. Remote Inventory completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Figure 98. Rack Remote Inventory menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Figure 99. Visualization of rack remote inventory file with “vi” editor . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Figure 100. General remote inventory data example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 101. Subrack Remote Inventory menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Figure 102. Remote Inventory of a NE subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Figure 103. Board Remote Inventory menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Figure 104. Board Remote Inventory window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
3AL 89062 AA AA 12 / 926
926
Figure 105. Board menu displayed (examples) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Figure 106. Output power level measurement typical views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Figure 107. Output power level measurement Typical views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Figure 108. Alarm threshold configuration view (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Figure 109. Alarm threshold table modification (example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Figure 110. Payload configuration dialog box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Figure 111. Current Instantaneous measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Figure 112. Create, Modify Equipments screen example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Figure 113. Pramphasis value setting example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Figure 114. Board menu displayed examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Figure 115. Laser Control For Test Menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Figure 116. Laser Control For Test Menu option on a WLA_TR_FEC64 board. . . . . . . . . . . . . . . . . 268
Figure 117. Example of Alarms menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Figure 118. NE Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Figure 119. Example of object alarm window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Figure 120. Event Log / Log Browsing option in Network Element context view . . . . . . . . . . . . . . . . 272
Figure 121. Alarm log file example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Figure 122. Event Log file example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Figure 123. Trace Log file example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Figure 124. Abnormal condition menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Figure 125. Example of abnormal condition list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Figure 126. Example of loopback dialog window management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Figure 127. Abnormal Conditions alarm icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Figure 128. EPS Status Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Figure 129. Equipment Filter Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Figure 130. Example of an EPS status Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Figure 131. EPS Functional State from Protected Active Board View . . . . . . . . . . . . . . . . . . . . . . . . . 283
Figure 132. EPS Functional State from Protecting Active Board View (Forced Protection is Active) 284
Figure 133. Consulting EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Figure 134. Example of EPS Management dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Figure 135. EPS: board selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Figure 136. EPS Functional State from Protected Active Board View . . . . . . . . . . . . . . . . . . . . . . . . . 288
Figure 137. EPS Functional State from Protecting Active Board View (Forced Protection is Active) 288
Figure 138. EPS menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Figure 139. Example of an EPS configuratiuo window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Figure 140. Switching EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Figure 141. Example of EPS Switch dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Figure 142. EPS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Figure 143. EPS overview after Search (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Figure 144. Example of subrack view after “Open Subrack View” command . . . . . . . . . . . . . . . . . . . 300
Figure 145. Example of board view after “Open Board View” command . . . . . . . . . . . . . . . . . . . . . . . 300
Figure 146. Linear 1+1 single ended protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Figure 147. Linear 1+1 dual ended protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Figure 148. Example of MSP Menu Options ( USM 3.1.. menu) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Figure 149. MSP Schema Creation on W/OMSN R.2.1B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Figure 150. TP Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Figure 151. MSP Schema Creation on 1670SM R.3.0B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
Figure 152. MSP schema creation – Port dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Figure 153. MSP 1+1 standard protection schema (example) on 1670SM R.3.0B . . . . . . . . . . . . . . 310
Figure 154. MSP N:1 standard protection schema (example) on 1670SM R.3.0B . . . . . . . . . . . . . . 310
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 155. MSP Schema Configuration on OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Figure 156. MSP Schema Configuration on OMSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Figure 157. MSP Management view on 1670SM R.3.0B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Figure 158. MSP Schema Deletion example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
3AL 89062 AA AA 13 / 926
926
Figure 159. MSP Protection Status Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Figure 160. MSP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Figure 161. MSP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Figure 162. Board examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Figure 163. Status examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Figure 164. MSP overview after Search (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Figure 165. Port view after “Open Port View” command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Figure 166. MSP Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Figure 167. TP Search Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Figure 168. Example of an MSP Browser Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Figure 169. Example of radio equipment protection block diagram for 1+1 HST configuration . . . . 333
Figure 170. IDU/ODU UHR Units in 1+1 HST configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Figure 171. UHR equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Figure 172. LRST board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Figure 173. TX/RX and Local Oscillator ODU board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Figure 174. UHRN 1 Equipment Overview – NE. level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Figure 175. IDU Equipment Overview – Rack level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Figure 176. IDU Equipment Overview – Subrack level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Figure 177. UHRN 2 Equipment Overview– NE level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Figure 178. EPS RX (receiver) block diagram on UHRN 2 (3+1 conf.) . . . . . . . . . . . . . . . . . . . . . . . 346
Figure 179. EPS TX (transmit) block diagram on UHRN 2 (3+1 conf.) . . . . . . . . . . . . . . . . . . . . . . . . 347
Figure 180. EPS Equipment Overview – Rack level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Figure 181. EPS Equipment Overview – Subrack level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Figure 182. EPS module and OPT/EIS box setting dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Figure 183. EPS board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Figure 184. EPS Port view window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Figure 185. Selectable modules view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Figure 186. RRA–MODEM card ( RMD 128 or RMD16 QAM ) screen. . . . . . . . . . . . . . . . . . . . . . . . 354
Figure 187. Electrical Interface module ( CMI–E ) screen ( Daughter 1 ). . . . . . . . . . . . . . . . . . . . . . . 355
Figure 188. LHR equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Figure 189. SRBB–N1 subrack example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Figure 190. Transmission Radio Interface View example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Figure 191. BER Not Intrusive option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Figure 192. Ber Not Intrusive box dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Figure 193. BER Not Intrusive measurement example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Figure 194. BER Not Intrusive window (Overflow condition) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Figure 195. EPS menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Figure 196. EPS configuration for ODU–TX radio equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Figure 197. External switching commands for ODU–TX radio equipment . . . . . . . . . . . . . . . . . . . . . 365
Figure 198. EPS statuses after a “Force to protecting” switching command applied to ODU–TX . 366
Figure 199. EPS statuses with a “Lockout” switching command applied to the IDU (LRST) . . . . . . 367
Figure 200. EPS statuses on UHRN 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Figure 201. RPS options on UHR 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Figure 202. RPS options on UHRN 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Figure 203. RPS Configure dialogue box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Figure 204. Configure Units dialogue box example on UHRN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Figure 205. RPS Commands dialogue box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Figure 206. Protection status after a “Force To” command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Figure 207. Protection switching statuses on the port view (Force to) . . . . . . . . . . . . . . . . . . . . . . . . . 374
Figure 208. RPS Synthesis dialogue box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 209. Extra Traffic dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

Figure 210. Example of Radio menu ( on LHR ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Figure 211. RPS Configure Schema box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Figure 212. RPS Configure Units box example (on LHR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
3AL 89062 AA AA 14 / 926
926
Figure 213. Example of Privilege Channel (channel “1”) on LHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Figure 214. Static Delay on Rx Side box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Figure 215. Static Delay Manual Configuration box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Figure 216. Static Delay Manual Result box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Figure 217. Setting the “Static Delay” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Figure 218. Example of switch Command box ( on LHR ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

Figure 219. RPS Synthesis box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Figure 220. Extra Traffic Enable / Disable box on LHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Figure 221. Selecting the daughter board to configure the overhead protection . . . . . . . . . . . . . . . . 385
Figure 222. Overhead Protection modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Figure 223. RFCOH menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Figure 224. RFCOH Configuration box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Figure 225. RFCOH Configuration box after “Choose Schema” Command . . . . . . . . . . . . . . . . . . . . 387
Figure 226. Rfcoh configuration window example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Figure 227. RFCOH Switch command box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Figure 228. RFCOH Synthesis box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Figure 229. ATPC option offered by the RADIO menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Figure 230. ATPC dialogue box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Figure 231. ATPC dialog box with the Set command example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Figure 232. ATCP menu on UHRN 2, LHR 1 and UHR 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Figure 233. ATPC management window example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Figure 234. Set command on the enable ATPC channel with error indication . . . . . . . . . . . . . . . . . 395
Figure 235. ATCP configuration dialog box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Figure 236. ATPC Manual Power Setting window example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Figure 237. ATPC Single direction Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Figure 238. Static Delay menu option on UHR / UHRN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Figure 239. Static Delay dialog box example on UHRN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Figure 240. Static Delay dialogue box on UHR 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Figure 241. Setting the “Static Delay” on UHR 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Figure 242. Frequency Agility menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Figure 243. Frequency dialogue box on LHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Figure 244. Frequency Agility dialogue box on UHR 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Figure 245. 1+1 Radio Configuration schema for “Frequency Agility” . . . . . . . . . . . . . . . . . . . . . . . . . 402
Figure 246. Frequency set dialogue box example on UHR / UHRN . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Figure 247. Frequency Agility screen on UHR 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Figure 248. Frequency Range Dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Figure 249. Power Measurement menu on UHR 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Figure 250. Power Measurement menu on LHR 1 and UHR 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Figure 251. Power Measurement dialog box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Figure 252. Power measurement dialogue box with the “Log file” indication . . . . . . . . . . . . . . . . . . . 408
Figure 253. Warning/Confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Figure 254. Example of Graphical power measurement window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Figure 255. Details Dialog box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Figure 256. Power Meas. File Reading menu example ( on UHR 1 ). . . . . . . . . . . . . . . . . . . . . . . . . . 412
Figure 257. File Chooser dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Figure 258. File reading output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Figure 259. Arrows navigation on the graphical file reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Figure 260. Squelch management dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Figure 261. Gain management box dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Figure 262. Choosing radio port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 263. Gain box dialog with the selected channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Figure 264. Hop Trace dialog box with the selected channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Figure 265. Radio abnormal Condition list example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Figure 266. Frequency Reuse dialog box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
3AL 89062 AA AA 15 / 926
926
Figure 267. Equalization Delay box with the radio port channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Figure 268. VCO Status window on LHR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Figure 269. Voltage Control Oscillator screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Figure 270. Example of a Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

Figure 271. Example of a termination TP box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

Figure 272. Example of G.783 Termination TP box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Figure 273. Visualizing a port optical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Figure 274. Automatic Laser Shutdown Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Figure 275. Automatic Laser Shutdown Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Figure 276. ALS and Laser current state (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Figure 277. Bidirectional Transmission on a single fiber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Figure 278. Single Fiber Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Figure 279. Loopback configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Figure 280. Example of Port Loopbacks View on OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Figure 281. Example of Loopback Management View (on OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Figure 282. Example of AU-4-4c CTP in the Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Figure 283. Example of AU4 concatenation groups for STM–16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Figure 284. Example of a AU4c in the port view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Figure 285. Example of AU4 deconcatenated command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Figure 286. MS Configuration Dialog displayed on OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Figure 287. PDH Line Length Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Figure 288. Set Retiming enable (before) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Figure 289. Set Retiming enable (after) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
Figure 290. Board View Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
Figure 291. After “Navigate to Transmission view” selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Figure 292. 1540 PO equipment view example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Figure 293. HDSL configuration menu for HLTCA board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Figure 294. HDSL port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Figure 295. Twisted pair window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Figure 296. Map with PO and NT equipments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Figure 297. NT creation board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Figure 298. NT Physical Media menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Figure 299. NT port configuration for 1512... boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Figure 300. X21 interface configuration window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Figure 301. Circuit status window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Figure 302. Port View on NT Rel.2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Figure 303. PM configuration and threshold table window on NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Figure 304. OGPI Port view Menu displayed (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Figure 305. 1686WM – Channel number information dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Figure 306. Transmit FEC counters displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Figure 307. 1686WM – Trail monitor block view example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Figure 308. Cable configuration display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Figure 309. 1686WM – OTS port Menu view (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Figure 310. 1686WM – APSD Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Figure 311. 1696M Span – APSD Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Figure 312. 1686WM – APSD Configuration dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Figure 313. 1686 WM – OTS Port menu view– Optical Add/Drop configuration display (example) 481
Figure 314. Threshold BER option selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Figure 315. Local loopback without cross connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Figure 316. Remote loopback without cross connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 317. Local drop–insert loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

Figure 318. Remote drop–insert loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Figure 319. Local pass–through loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Figure 320. Remote pass–through loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
3AL 89062 AA AA 16 / 926
926
Figure 321. Local loopback symbol – Transmission view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Figure 322. Remote loopback symbol – Transmission view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Figure 323. Example of a Port Details Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Figure 324. Examples of TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Figure 325. Port Details Dialog without any TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496

Figure 326. TP Search Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

Figure 327. Port Details Dialog with TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Figure 328. Symbols Used in Transmission View (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Figure 329. Transmission View with Activated Panner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Figure 330. Entries manager buttons on OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Figure 331. Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Figure 332. TP Search Dialog on W/OMSN (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Figure 333. TP Search Dialog with Various TP Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Figure 334. Cross-Connection Access Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Figure 335. Cross-Connection Access Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Figure 336. Cross-Connection State Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Figure 337. Cross-Connection State Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Figure 338. Board History Check List example on OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Figure 339. TP Search Dialog with different filtering options example . . . . . . . . . . . . . . . . . . . . . . . . . 516
Figure 340. “Information...” Dialog for Search Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Figure 341. Results of a “AU4 TPs” filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Figure 342. Example Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Figure 343. Board View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Figure 344. Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Figure 345. J0 Configuration on OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Figure 346. High Order TP Configuration (on W/OMSN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Figure 347. Low Order TP Configuration on OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Figure 348. PDH Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Figure 349. TP Frame Mode Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Figure 350. Alarm Persistence Time Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Figure 351. Degraded Signal Threshold Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Figure 352. TP Thresholds Configuration Dialog on OMSG–CL2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Figure 353. POM/SUT Creation/Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Figure 354. Example of POM/SUT in Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Figure 355. POM/SUT displayed on 1674LG Rel.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Figure 356. POM/SUT Configuration example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Figure 357. SDH Multiplex Structure according to ITU-T G.707 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Figure 358. Frame Construction within the Synchronous Digital Hierarchy . . . . . . . . . . . . . . . . . . . . 558
Figure 359. SDH Transport Level Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
Figure 360. PDH Transport Level Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Figure 361. Unidirectional Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Figure 362. Bidirectional Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Figure 363. Example of Broadcast Connection with Three Legs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Figure 364. Protected Unidirectional Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Figure 365. Bidirectional Connection – Input Protected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Figure 366. Bidirectional Connection – Output Protected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Figure 367. Protected Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Figure 368. Drop and Continue – Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
Figure 369. Drop and Continue Insert Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Figure 370. Cross-Connection Management Dialog – Filter Area on OMSG . . . . . . . . . . . . . . . . . . . 571
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 371. Cross-Connection Management Dialog (After Search) . . . . . . . . . . . . . . . . . . . . . . . . . . . 576

Figure 372. Example of “Protection Criteria” for OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Figure 373. Example of “Protection Criteria” for W/OMSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Figure 374. Cross-Connection Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
3AL 89062 AA AA 17 / 926
926
Figure 375. Creation of a Unidirectional, Non-Protected Cross-Connection . . . . . . . . . . . . . . . . . . . . 584
Figure 376. Create a Bidirectional Protected Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Figure 377. Search for Cross-Connection Output on W/OMSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Figure 378. Create an Unprotected Broadcast Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589

Figure 379. Unprotect a Unidirectional Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

Figure 380. Protect one Leg of a Broadcast Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Figure 381. Split/Join Unprotected Bidirectional Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Figure 382. Split/Join to Protected Bidirectional Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Figure 383. Protection Actions Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Figure 384. Port Switch Over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Figure 385. Port Switch Over Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Figure 386. Example of Blocking Info TPs Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Figure 387. Show Cross Connected TPs (TP 01#Au4P selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
Figure 388. Show All Cross Connected TPs (TP MSP selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Figure 389. MCC default cross–connection configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Figure 390. Add and Drop cross–connection – Line terminal architecture . . . . . . . . . . . . . . . . . . . . . 612
Figure 391. Add and Drop cross–connection – OADM / back to back architecture . . . . . . . . . . . . . 612
Figure 392. Pass–through cross–connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Figure 393. Protected cross–connection – OADM architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Figure 394. OCHTTP port implied in a cross connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
Figure 395. Far End Performance Monitoring Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Figure 396. PM Configuration Dialog on OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Figure 397. PM question dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Figure 398. EML OS monitoring window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Figure 399. Create / Modify PM Threshold Table (USM 3.x, 4.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
Figure 400. PM Threshold Table Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
Figure 401. PM Current Data dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Figure 402. PM History Data Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Figure 403. Displaying performance data from a Network Topology view. . . . . . . . . . . . . . . . . . . . . . 655
Figure 404. Displaying performance data from an Equipment view. . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Figure 405. SETS Internal organization. Dashed lines are for W/OMSN NEs . . . . . . . . . . . . . . . . . . 657
Figure 406. Obtaining the synchronization view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Figure 407. Example of the Synchronization View (on OMSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Figure 408. Example of Timing reference graphical object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
Figure 409. Example of the Internal Oscillator graphical object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Figure 410. Symbol used to represent a Squelch Status T1/T4 and the Selector C . . . . . . . . . . . . 663
Figure 411. Symbol used to represent a Output Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
Figure 412. Synchronization Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
Figure 413. Example of synch. source configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
Figure 414. Example of synch. source configuration for 1664SM equipment . . . . . . . . . . . . . . . . . . . 668
Figure 415. Timing Source Configuration Dialog (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Figure 416. Choose External Timing Source Dialog (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
Figure 417. Lockout, Force and Manual commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Figure 418. Protection Commands Dialog – Internal Oscillator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Figure 419. T0 Configuration dialog box on OMSG USM 8.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Figure 420. Configuring the T4 SSM algorithm and the squelch criteria . . . . . . . . . . . . . . . . . . . . . . . 679
Figure 421. Output Configuration (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Figure 422. SSU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Figure 423. Synchronization source removing on W/OMSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Figure 424. T4 equal T0 setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 425. Change T4 <–> T5 menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686

Figure 426. Change T4 <–> T5 confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Figure 427. Change T4 <–> T5: command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Figure 428. Change 2MHz –>2Mbit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
3AL 89062 AA AA 18 / 926
926
Figure 429. Change 2MHz –>2Mbit confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
Figure 430. Change 2MHz –>2Mbit: command execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Figure 431. Frame Mode Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Figure 432. T0_TEST Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Figure 433. Transmission SSM Quality box dialog example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693

Figure 434. Timing Source Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694

Figure 435. 2F MS SPRING Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Figure 436. Effect of a BRIDGE EAST operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Figure 437. Effect of SWITCH WEST operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Figure 438. Line break recovering operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
Figure 439. 2F MS–SPRING example of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
Figure 440. Squelching on isolated Node connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Figure 441. MS SPRING Drop and Continue, Insert Continues (protected) . . . . . . . . . . . . . . . . . . . 702
Figure 442. 4 F MS–SPRING Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Figure 443. 4F–MSSPRING. Full capacity NPE (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Figure 444. 4F–MSSPRING. Example of routing in case of failures . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Figure 445. Protection mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
Figure 446. Display MS–SPRing pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Figure 447. MS–SPRing Management dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
Figure 448. Creation Schema dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Figure 449. Activated MS–SPRing Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
Figure 450. Node Id and associated ring node position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Figure 451. Ring map configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
Figure 452. WTR dialog box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Figure 453. Example of error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Figure 454. Squelching table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
Figure 455. Example of a ring traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Figure 456. Squelching table of Figure 455. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
Figure 457. Insert to East . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Figure 458. Drop East . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Figure 459. Example of West to East Pass–through with its protection . . . . . . . . . . . . . . . . . . . . . . . 723
Figure 460. Point–to–Multipoint path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Figure 461. Point–to–Multipoint configuration and relevant protection channel . . . . . . . . . . . . . . . . . 724
Figure 462. Drop & Continue and Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Figure 463. Example of Last Drop & Continue on West side (protection on East) . . . . . . . . . . . . . . 726
Figure 464. Example of Traffic table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Figure 465. Drop/Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
Figure 466. Pass–Through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Figure 467. Point–to–Multipoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Figure 468. Drop & Continue plus Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Figure 469. Last Drop Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Figure 470. Traffic example in ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
Figure 471. Ring normal traffic map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
Figure 472. Ring extra–traffic map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Figure 473. Ring Normal traffic map: concatenated path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Figure 474. Point–to–multipoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Figure 475. Ring normal traffic map describing a point–to–multipoint unidirectional path . . . . . . . . 733
Figure 476. 2 NPE rings, bidir, D&C, no prot. in NPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Figure 477. Path of Figure 476. B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Figure 478. Bidir, D&C, no prot. in NPE, (add/drop node = Primary) . . . . . . . . . . . . . . . . . . . . . . . . . . 735
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 479. Traffic map of Figure 478. A and Figure 476. A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Figure 480. Path of Figure 478. B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Figure 481. Bidir, D&C, no prot. in NPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Figure 482. Traffic map of Figure 481. C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
3AL 89062 AA AA 19 / 926
926
Figure 483. Traffic map of Figure 481. D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Figure 484. Unidir, D&C, no prot. in NPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Figure 485. Traffic map of Figure 484. B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Figure 486. Confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738

Figure 487. Example of protection states and commands ”Idle” status (4F) . . . . . . . . . . . . . . . . . . . . 739

Figure 488. Span and Ring Protection (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
Figure 489. Lockout commands (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Figure 490. Protection and working channels where the lockout command can be activated (4F) 741
Figure 491. Tail–end / Head–end association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
Figure 492. Ring protection with a lockout protection span and a ring failure (4F) . . . . . . . . . . . . . . 743
Figure 493. Lockout command and non–served failures (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Figure 494. Forced and Manual commands (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Figure 495. Manual and Force Span/Ring command (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Figure 496. Examples of a “Force” command and a “Automatic” protection span (4F) . . . . . . . . . . 746
Figure 497. Automatic protection Bridge/Switch (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Figure 498. Example of confirmation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Figure 499. Clear WTR commands (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
Figure 500. Ring network reference scheme for dual “Events” (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
Figure 501. Automatic protection for double ring failures (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Figure 502. Protection span and ring failure with a tail–end/head–end node mode ( R,CMs) . . . . . 753
Figure 503. Protection span and ring failure with a tail–end/tail–end node mode ( R,Cs) . . . . . . . . 754
Figure 504. Dual “Events” Protection table (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
Figure 505. Examples of dual “Exercise” and “Manual” commands for 1670SM (4F) . . . . . . . . . . . 757
Figure 506. Protection Status with the Exercise Span command (4F) . . . . . . . . . . . . . . . . . . . . . . . 759
Figure 507. Visualization of the Forced / Manual / Exercise protection Statuses (4F) . . . . . . . . . . . 760
Figure 508. Visualization of the Lockout command Statuses (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . 761
Figure 509. Visualization of Automatic Protection Statuses (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
Figure 510. Automatic Protection and Alarm Clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Figure 511. Dual “Events” Ring network reference scheme (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Figure 512. Considered cases on 1664SM /1670SM with different visualization statuses . . . . . . . 764
Figure 513. Automatic protection with double ring failures on 1664SM (4F) . . . . . . . . . . . . . . . . . . . . 765
Figure 514. Automatic protection for double ring failures on 1670SM (4F) . . . . . . . . . . . . . . . . . . . . . 767
Figure 515. Protection Span failure between ADM 1 and ADM 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Figure 516. Working Span failure between ADM 1 and ADM 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
Figure 517. Clearing of “Working Span failure” between ADM 1 and ADM 4 . . . . . . . . . . . . . . . . . . 770
Figure 518. Protection span failure between ADM1–ADM2 plus ring failure
between ADM4–ADM3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
Figure 519. Working span failure between ADM 1– ADM4 plus working ring failure between
ADM1–ADM2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 772
Figure 520. Ring failure between ADM1–ADM2 plus ring failure between ADM3–ADM4 . . . . . . . . 773
Figure 521. Ring failure between ADM1–ADM4 and between ADM1–ADM2
(ADM1=isolation node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774
Figure 522. Exercise Span between 1670_N1–1670_N2 plus Exercise Ring between
1670_N6–1670_N5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Figure 523. Double Exercise Span commands: between 1670_N1–1670_N2 and between
1670_N2–1670_N5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
Figure 524. Manual Span between 1670_N1–1670_N2 plus Exercise Ring between
1670_N5–1670_N6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
Figure 525. Ring failure between 1670_N1–1670_N6 plus Working span failure (SS–AN) . . . . . . . 778
Figure 526. Ring failure between 1670_N1–1670_N6 plus working span failure (OS–SN) . . . . . . 779
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 527. Ring failure between 1670_N1–1670_N6 plus Working Span failure (OS–RN) . . . . . . 780
Figure 528. Ring failure between 1670_N1–1670_N6 plus Protection Span failure (SS–AN) . . . . . 781
Figure 529. Ring failure between 1670_N1–1670_N6 plus Protection Span failure (OS–SN) . . . . 782
Figure 530. Protection states and commands “idle” status (2F). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
3AL 89062 AA AA 20 / 926
926
Figure 531. Ring Protection (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
Figure 532. Lockout commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Figure 533. Protection and working channels where the lockout command can be activated (2F) 786
Figure 534. Tail–end / head–end ring protection with a lockout working and a ring failure (2F) . . . 787
Figure 535. Ring protection with a lockout and a ring failure (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
Figure 536. Lockout command and non–served failures (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789

Figure 537. Forced and Manual commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
Figure 538. Manual and Force commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
Figure 539. Ring Protection with Force and Manual commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . 791
Figure 540. Automatic protection Bridge/Switch (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
Figure 541. Example of confirmation dialog box (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
Figure 542. Clear WTR commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
Figure 543. Ring network reference scheme (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Figure 544. Examples of Double ring failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
Figure 545. 2F Automatic protection (tail/head) for double ring failure visualization . . . . . . . . . . . . . 797
Figure 546. Tail / head dual “Events” Protection table (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
Figure 547. Manual command applied at the “Reference Point” ring network (Figure 543. ) . . . . . 800
Figure 548. Visualization of the Forced / Manual protection Statuses (2F) . . . . . . . . . . . . . . . . . . . . . 801
Figure 549. Visualization of the Lockout command Statuses (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
Figure 550. Visualization of Automatic Protection Statuses (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Figure 551. Protection status with double ring failure (reference point––SS–AN) . . . . . . . . . . . . . . . 804
Figure 552. Protection status with double ring failure (reference point––SS–RN) . . . . . . . . . . . . . . . 805
Figure 553. Protection status with double ring failure (reference point––OS–AN) . . . . . . . . . . . . . . . 806
Figure 554. Protection status with double ring failure (reference point––OS–AN)
recovering to “idle” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Figure 555. Double manual ring command (reference point––SS–AN) . . . . . . . . . . . . . . . . . . . . . . . . 808
Figure 556. Double manual ring command (reference point––OS–AN) . . . . . . . . . . . . . . . . . . . . . . . 809
Figure 557. Manual ring and Lockout Protection (reference point––SS–SN) . . . . . . . . . . . . . . . . . . 810
Figure 558. Manual ring and Lockout Protection (reference point––SS–RN) . . . . . . . . . . . . . . . . . . 811
Figure 559. Automatic working ring and Manual Ring (reference point––OS–AN) . . . . . . . . . . . . . 812
Figure 560. Automatic working ring and Force Ring (reference point––SS–AN) . . . . . . . . . . . . . . . 813
Figure 561. Automatic working ring and Lockout working Ring (reference point––SS–SN) . . . . . 814
Figure 562. Automatic working ring and Lockout Protection (reference point––OS–RN) . . . . . . . . 815
Figure 563. 2-Fiber MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
Figure 564. Default Mode of MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Figure 565. MS-SPRing Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
Figure 566. Ring Parameter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
Figure 567. Ring Map Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824
Figure 568. Squelch Table Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826
Figure 569. Finish Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
Figure 570. Example of created MS-SPRings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
Figure 571. Example for deletion of a MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
Figure 572. Example for Different Modifications of a MS-SPRing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Figure 573. Example for Modification of Ring Map Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
Figure 574. Example for Modification of Squelching Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
Figure 575. Example for Modification of WTR Time Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
Figure 576. Example of a MS-SPRing view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
Figure 577. Example of a MS-SPRing in Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
Figure 578. Example of a MS-SPRing in Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
Figure 579. Example for MS-SPRing Protection Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 580. Example of a “Forced Switch to Protection – Ring” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841

Figure 581. Example of a “Manual Switch to Protection – Ring” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
Figure 582. ATM ports Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Figure 583. ATM ports Configuration (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
3AL 89062 AA AA 21 / 926
926
Figure 584. ATM board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
Figure 585. ATM PSEUDO–SUBBOARD view (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
Figure 586. Software Download general principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Figure 587. Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852

Figure 588. Download menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853

Figure 589. SW Downloading dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
Figure 590. Software download in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Figure 591. Software Package Information dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
Figure 592. Detail of units info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
Figure 593. Detail software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
Figure 594. Servers management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Figure 595. Example of server “remote1” data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
Figure 596. Chosen Server address does not match the relative NE . . . . . . . . . . . . . . . . . . . . . . . . . 860
Figure 597. Simulator inside SH environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Figure 598. Supervision Menu window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
Figure 599. Start simulator confirmation box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
Figure 600. On–board simulator monitoring window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
Figure 601. Start simulator confirmation icon window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Figure 602. EML–IM crash box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Figure 603. Supervision menu and stop simulator window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Figure 604. Simulator stopping confirmation box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Figure 605. Off–line navigation mode Equipment menu window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
Figure 606. Off–line navigation mode Supervision menu window (NE not reachable) . . . . . . . . . . . 869
Figure 607. Off–line navigation mode (NE reachable) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
Figure 608. Off–line configuration mode: Set out of service window . . . . . . . . . . . . . . . . . . . . . . . . . . 872
Figure 609. Set board window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
Figure 610. Select board window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
Figure 611. Supervision menu and Align–up selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
Figure 612. Align–up confirmation box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
Figure 613. MIB alignment Information box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Figure 614. Supervision menu and Align–down selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
Figure 615. Align–down confirmation box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878
Figure 616. First NE MIB management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
Figure 617. NE MIB management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Figure 618. Restart NE confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
Figure 619. Overhead options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
Figure 620. Cross Connection Management for OverHead dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
Figure 621. Main Cross-Connection for OverHead dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
Figure 622. OH TP creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
Figure 623. OH Search TP for creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
Figure 624. OH TP deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
Figure 625. Phone Parameters dialog window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
Figure 626. Routing subdomain organization example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
Figure 627. OSI over IP tunneling on QB3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
Figure 628. Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
Figure 629. OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
Figure 630. NTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
Figure 631. LAPD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
Figure 632. Example of Ethernet Configuration window (USM 6.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
Figure 633. Ethernet Configuration – L2 only parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 634. RAP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911

Figure 635. MESA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
Figure 636. IP Static Routing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
Figure 637. OSPF Area Table Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
3AL 89062 AA AA 22 / 926
926
Figure 638. IP Address Configuration of Point–to–Point Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
Figure 639. ISA Board IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
Figure 640. IP over OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
Figure 641. External points option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
Figure 642. Example of external points view (USM 4.x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922

Figure 643. Expanding or reducing the external points list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923

Figure 644. Configuring external points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
Figure 645. External input point configuration dialogue box example. . . . . . . . . . . . . . . . . . . . . . . . . . 924
Figure 646. External output point configuration dialogue box example. . . . . . . . . . . . . . . . . . . . . . . . 924
TABLES
Table 1. Assignment of Service Dependency and Severity on OMSG and WDM . . . . . . . . . . . . . . . 158
Table 2. Default Assignment of Service Dependency and Severity on OMSN . . . . . . . . . . . . . . . . . 159
Table 3. Possible Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Table 4. Drag Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Table 5. Drop Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Table 6. Examples of EPS–W/OMSN protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Table 7. APS for OMSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Table 8. APS for OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Table 9. MSP commands and Auto–switch protection priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Table 10. UHRN 1. Composition: two channels (RT) for any RKODU. . . . . . . . . . . . . . . . . . . . . . . . . 342
Table 11. UHRN 2. Composition: one channel (RT) for any RKODU . . . . . . . . . . . . . . . . . . . . . . . . . 344
Table 12. UHRN 2 EPS rack composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Table 13. OMSG SDH Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Table 14. Supported Loopback Types Dedicated I/Os . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Table 15. Default Values for C2/V5 Signal Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Table 16. Max. Values for Bursty Degrade Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Table 17. Max. Values for Bursty Signal Degrade Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Table 18. Max. Values of Bursty Degrade Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Table 19. PDH TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Table 20. SDH TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Table 21. Optional and Mandatory Configurable Parameters for Cross-Connection Creation . . . . 582
Table 22. Modifiable Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Table 23. Maximum Performance Parameter Values on W/OMSN . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Table 24. Maximum Threshold Values on OMSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Table 25. Example of a threshold table entities association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 23 / 926
926
HISTORY
This section has no Internal Document Reference

REFERENCED DOCUMENTS
Applicable documents (for Alcatel internal use only)
[1] TSD–France, Manuel Qualite Branche Systemes de Transmission – TSD,

8AS 11002 0001 UZALB, Ed8
[2] Alcatel/NMU, NMU Application Development Process,

NMU/GT/96/022, Ed1
[3] Alcatel/NMU, EMLCore.x Quality Assurance Plan,

3BP 22100 0034 QMZZA, Ed1
[4] Alcatel/NMU, EMLCore.x QAP Addendum,

NMU/L/VE/98/415, Ed1
[5] Alcatel/NMU, NMU Documentation Management Procedure,

8AY 02000 0000 ASZZA, Ed4
[6] Alcatel/NMU, Amendment of SQF, DMP, DIP, PDL procedures,

NMU/L/VG/98/051, Ed1
[7] Alcatel/NMU, EMLCore 98 Technical Requirements Specification,

3BP 22100 0008 DSZZA, Ed1
[8] Alcatel/NMU, EMLCore 98 System Architecture Description: Application Architecture: Part 1,

3BP 22100 0001 EBZZA, Ed1
[9] Alcatel/NMU, EMLCore 98 System Architecture Description: Application Architecture: Part 2,

3BP 22100 0002 EBZZA, Ed1
[10] Alcatel/NMU, EMLCore 98 User Interface Specification,

3BP 22100 0025 DSZZA, Ed4.0
[11] Alcatel/NMU, NMU Technical Glossary,

See NMU Web Server
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 24 / 926
926
Reference documents (for Alcatel internal use only)
[12] Alcatel/NMU, EMLCore 98 Introduction manual,

3BP 22100 0066 OMZZA, Ed1.2
[13] Alcatel/NMU, EMLCore 98 Getting Started manual,

3BP 22100 0067 OMZZA, Ed1.2
[14] Alcatel/NMU 1353SH3.1 Operator Manual NE Management,

NMU/C/98/0072, Ed2
[15] Alcatel 1641 SX Operator Manual Craft Terminal Management,

3AL 69394 AAAA, Ed1
[16] Alcatel/NMU, ALMAP – ELM 5.X User’s Guide,

3BP 21608 0009 TCZZA, Ed2
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 25 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
SC.1.2: Q3 NE MANAGEMENT
926
3AL 89062 AA AA
26 / 926
1 INTRODUCTION
1.1 Scope
1.1.1 Document scope
(NEs) easily, using the SHD Manager Operation System (OS). The different functionalities related to the
1.1.2 Edition scope
None.
1.1.3 Target audience
This document is intended for the operators whose role is to manage the Network Elements.
The document that should be read before starting this document is:
– Getting Started section of the 1353NM Operator’s Handbook (for examle 7.0).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 27 / 926
926
1.2 Document structure
This document is composed of the following chapters:

– Chapter 2: Menu Commands

• Menu Overview
• 1353SH Menu Commands for OMSN using P.3.x. USM version
• 1353SH Menu Commands for W/OMSN using P.4.x USM version
• 1353SH Menu Commands for UHR, LHR 1, UHRN with P.5.x USM version
• 1353SH Menu Commands for OMSG using USM P.4.x
• 1353SH Menu Commands for OMSG using USM P.7.x
• 1353SH Menu Commands for 1674LG Rel.1.1 using USM P.8.x
• 1353SH Menu Commands for 1686 WM R.3.3
• 1353SH Menu Commands for 1686 WM R.3.4A
• 1353SH Menu Commands for 1686 WM R.3.5
• 1353SH Menu Commands for 1640 WM R.1.2A
• 1353SH Menu Commands for 1640 WM R.1.2C
• 1353SH Menu Commands for 1640 WM R. 3.0
• 1353SH Menu Commands for 1640 WM R. 3.1
• 1353SH Menu Commands for OPS Rel.1.0
• 1353SH Menu Commands for OCP Rel.1.0
• 1353SH Menu Commands for 1696WM Rel. 1.0
• 1353SH Menu Commands for 1696WM Rel. 1.1
– Chapter 3: NE Management.
• NE management states
• Allow or Inhibit NE Craft access
• Changing NE Address (only available for W/OMSN)
• USM Time Configuration / Status
• Alarm Configuration
• Navigation Between Views
• User Preferences (only available for OMSG)
• Clipboard Dialog (only available for OMSG)
• Drag and Drop (DnD) (only available for OMSG)
• Print Dialog
• Show Matrix Type (only available for OMSG)
– Chapter 4: Security Management
• Security Check
• Check Level Configuration (only available for OMSG)
• Access Control Management on Port Level (only available for OMSG)
• Manager List
• NE Port/User Assignment (only available for OMSG)
– Chapter 5: Room View (only available for OMSG).
• Overview
1AA 00014 0004 (9007) A4 – ALICE 04.10
• View layout
• Navigation
• Rack Label
3AL 89062 AA AA 28 / 926
926
– Chapter 6: Equipment Overview (only available for OMSG).
• Overview
• Navigation
• Add Equipment
• Clipboard
– Chapter 7: Board and Subrack Management.
• Board / Subrack / Rack / NE Level

• Board management
• Board View Layout
• Board States and EPS States
• Navigation Commands in Board view
• ATM Configuration
• Cable configuration (only applicable to W/OMSN)
• Remote Inventory
• Board Configuration for WDM
– Chapter 8: Diagnosis.
• Alarms Surveillance
• Event Log / Log Browsing
• View Remote Inventory
• Abnormal Condition (not available for OMSG)
– Chapter 9: Equipment Protection Management.
• Introduction
• EPS Status (only available for OMSG)
• EPS Management
• EPS Configuration (not available for OMSG)
• Switching EPS
• EPS Overview (not available for OMSG)
– Chapter 10: Multiplex Section Protection Management.
• Architecture Types
• MSP Create (not available for OMSG)
• MSP Management
• MSP Delete (not available for OMSG)
• Display of Protection State
• MSP Commands
• MSP overview (not available for OMSG)
• MSP Status (only available for OMSG)
• Setting up linear MSP with SH–RM interworking
– Chapter 11: Radio Management.
• Radio protection management for UHR

• UHRN equipment configuration
• LHR Equipment
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
EPS protection on UHR 1.0, UHR 2.0 and UHRN 2.0

• RPS (Radio Protection Switching) Protection
• RFCOH (Radiio Frequency Channel Overhead) management on LHR
• ATPC
3AL 89062 AA AA 29 / 926
926
• Static Delay on UHR 1 and UHRN 1
• Frequency / Frequency Agility
• Power Measurement
• Power Measurement File Reading

•

Squelch Management on LHR

• Gain Management on LHR 1.0, UHR 2.0 and UHRN 2.0
• Hop Trace Management on LHR
• Radio Abnormal Condition on LHR 1.0, UHR 2.0 and UHRN 2.0
• Frequency Reuse on LHR and Carrier Status on UHR and UHRN 2.0
• Equalization Delay on LHR
• V.C.O. (Voltage Control Oscillator) Management on LHR
– Chapter 12: Port View.
• View Elements
• Port View Commands
• Loopback
• Concatenation Procedure
• MS Configuration
• PDH Line Length Configuration
• Set retiming
• Show Supporting Board
• Navigation Commands in Port View
• Port View Configuration for 1540PO
• Optical Port Configuration for WDM
– Chapter 13: Port Details Dialog (only available for OMSG).
• Port Details Dialog Layout

• TP Object Design
• Port Details Dialog Configuration
– Chapter 14: Transmission View.
• Overview
• View Elements
• View Layout
• Add TP
• Navigation Commands in Transmission View
• TP Configuration
• PDH TP / TP Frame mode Configuration
• Alarm Persistency Time Configuration (on OMSG)
• Degraded Signal Threshold / TP Threshold Configuration
• Terminate / Disterminate TP
• POM/SUT
• Structure TPs
– Chapter 15: Cross Connection Management
• Introduction
• Cross–Connection Management
• Create/Modify Cross–Connections
1AA 00014 0004 (9007) A4 – ALICE 04.10
• Activate/Deactivate/Delete Cross–Connections
• Operative Sequence to execute Cross–Connections (for W/OMSN)
• Split and Join Cross–Connections
3AL 89062 AA AA 30 / 926
926
• Protection Switching
• Port Switch Over (only available for OMSG)
• Blocking Information (only available for OMSG)
• Show Cross Connected TPs / Show All Cross Connected TPs
•
Cross Connections for 1696MS

– Chapter 16: Performance Monitoring
• Introduction
• PM Configuration
• PM Threshold Table Creation / Modification / Display
• PM Threshold Table Selection
• Display PM Current Data
• Display PM History Data
• Performance Monitoring for WDM equipment
• Show Performance Data
– Chapter 17: Synchronization Management
• Introduction
• Synchronization Commands
– Chapter 18: MS–SPRing Management For W/OMSN
• MS–SPRing Management for ADM Equipments

• MS–SPRing Management
• MS–SPRing Protection Status – Commands for NPE Application
• MS–SPRing Protection Status – Commands for 2F Terrestrial Application
– Chapter 19: MS–SPRing Management For OMSG
• Introduction
• Create / Delete MS–SPRing
• Activate / Deactivate MS–SPRing
• Modify MS–SPRing
• Display MS–SPRing
• Protection States and Commands for 2–Fiber Classic MS–SPRing
– Chapter 20: ATM Configuration (only available for W/OMSN)
• Introduction
• ATM board TTPs creation
– Chapter 21: Software Management (not available for OMSG)
• Generalities and descriptions

• Software Download Management commands
• Init download
• SW package Activation and Units information
• Servers Management
• On Board Simulator
• Simulator operations
• Mib management starting from SH5.5 for NE with OBS
1AA 00014 0004 (9007) A4 – ALICE 04.10
• MIB management without OBS

• Restart NE
• ATM Installation notes
3AL 89062 AA AA 31 / 926
926
– Chapter 22: Overhead Management (not available for OMSG)
• Introduction
• OH Connection overview

• Overhead views

• OH Cross Connection
• OH TP creation
• OH TP deleting
• OH Phone Parameters
– Chapter 23: Routing Management (not available for OMSG)
• Overview on Communication and Routing Domain

• Communication and routing views
• Local Configuration
• OS Configuration
• NTP Server Configuration
• LAPD Configuration
• Ethernet Configuration
• Reachable Address Prefixes Configuration
• Manual ES Adjacencies Table Configuration
• IP Static Routing Configuration (USM 6.x)
• OSPF Area Table Configuration (USM 6.x)
• IP Address Configuration of Point–to–Point Interfaces (USM 6.x)
• ISA board IP Address (USM 6.x)
• IP over OSI (USM 6.x)
– Chapter 24: External Points Management (not available for OMSG)
• Displaying external points

• External points configuration
1.3 Terminology
Refer to the Introduction Manual for abbreviations and glossary.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 32 / 926
926
2 MENU COMMANDS
The Windows inserted in the Q3 NE Management have to be considered only for the option
command described.
The menu commands hereinafter described are also applicable to family ADM listed in the “Handbook
Guide” section of this 1353SH release. The features described in this “Q3–NE Management” section,
when applicable, can be extended to the menu commands of 1640WM, 1686WM and 1696MS Q3
equipments.
2.1 Menu Overview
The menu commands represented, for every USM, with different menu windows provide all the available
commands. The menu commands are distributed to three levels: a menu bar, a pull down menu and
another branch commands ( if an arrow, in the branch, is represented ).
The 1353SH manages different NE families and to every family is associated one or more USMs. The
following USM are here reported:
• USM P.3.x. for OMSN (valid only for some NE types)

• USM P.4.x, P.5.x and P.6.x for W/OMSN family.
• USM P.5.x for WMSN: LHR Rel.1, UHR Rel. 1/2 and HUD Rel. 2
• USM P.4.x. and USM P.7.x for OMSG family.
• USM 8.x for 1674LG Rel.1.1
• USM P.1.2.x for 1686WM Rel. 3.3, USM P.1.4.x for 1686WM Rel. 3.4 and USM1.5.x for
1686WM Rel. 3.5.
• USM P.1.2.x for 1640WM Rel. 1.2A, USM P.1.4.x for 1640WM Rel. 1.2C / 3.0 and USM 1.5.x
for 1640WM Rel3.1.
• USM P.1.4.x for OPS Rel.1.0
• USM P.1.4.x for OCP Rel.1.0
• USM P.1.4.x for 1696MS Rel.1.0
• USM P.1.5.x for 1696MS Rel.1.1
The main view represents a general structure of the Q3NEs composed of subracks, in which different
boards are represented. Icons alarms in the top and left hand corners give information on the number and
the severity of the current alarms.
The lock representation which appears over some boards, indicates that these boards cannot be removed
because they are in service.
To be able to remove one of this boards, first stop the running process in which it is involved and then put
the board “Out of Service” to disable the alarm sources.
The NE view contains a severity alarm synthesis, a view title, a domain alarm synthesis, a management
status control panel and a message area. They provide you with information needed to manage the Q3NE
equipment.
The Board menu and then the Port View menu are opened when the user, after selecting, in the Equipment
View, the board type opens the selected object. The Synchronization, the Transmission and the External
Points menu are available with the Views menu. The user can also access to the Transmission menu
through the Port View menu. The menu options are visualized according to the TP or board selected. A
1AA 00014 0004 (9007) A4 – ALICE 04.10
disable option is visualized with a grey text.
3AL 89062 AA AA 33 / 926
926
The menu bar here has been represented with a black vertical line and the grouping command is reported
in bold on the left side. The main groupings are: Views, Configuration, Diagnosis, Supervision, Download,
Equipment, Room and other items depending on the USM provided. The help option contains the
documentation on line to help the user to understand the different commands that can be applied. The help

menu (On help, On Context, Glossary, About, Tutorial) is not reported in the menu bar.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 34 / 926
926
2.2 1353SH Menu Commands for OMSN using P.3.x. USM version
1353SH USM 3.x FOR OMSN

Views Previous
Equipment
External Points
Transmission
Synchronization
Comm/Routing Local Configuration

OS Configuration
NTP Server Configuration
LAPD Configuration
Ethernet Configuration
RAP Configuration
MESA Configuration
OverHead OH Cross Connection
OH Phone Parameters
OH Tp Creation
OH Tp Deleting
Open object
Open in Window
Close
Configuration Alarms Severities
Set alarms Severities
NE Time
Performance Forced Performance Collection

Threshold Tables
Set ACD Level
Cross Connection Management
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 1. OMSN Menu bar for P.3.x USM version
3AL 89062 AA AA 35 / 926
926

Diagnosis Alarms (Show) NE alarms
Object Alarms
Subtree Alarms
Synchronization Alarms
Equipment Alarms
Transmission Alarms
External Points Alarms
Performance Data 15 Minutes

24 Hours
Events Log (logld,1)

(logld,2)
View Remote Inventory
Abnormal Condition List
Supervision Simulator Start

Stop
Align Down
Align Up
Activate
Allow Periodic Upload
Inhibit Periodic Upload
Access State OS
Local
Alarms Resynchronize
Allow Notifs
Upload Remote Inventory
Inhibit Notifs
Set Manager List
continues Figure 1. OMSN Menu bar for P.3.x USM version

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 36 / 926
926
MS–SPRing Main Dialog for MS–SPRing management

Create a MS–SPRing Scema
Set WTR Time parameters
Manage Ring Map
Configure Squelch Table
Configure Ring Traffic Map
View Protection Status parameters
Download Init download

Units info
Mib management
Servers management
Restart NE
EPS Management
Configure
Switch
Equipment Set
Modify
Remove
Set in service
Set out of service
Reset
Software description
Remote Inventory Subrack Level
Board Level
Show supporting equipment

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 37 / 926
926

From the Equipment View open the selected board (open object or mouse clicking) to visualize the
Board menu
Board Port Access

From the Board View open the selected board (open object or mouse clicking) to visualize the Port menu.
SDH or PDH port menu will be available according to the selected board.
SDH port
Port Physical Media Ms Ber Configuration

Optical Laser Configuration
ALS Management
SDH TXSsm Quality Configuration
SDH Single Fiber Configuration
MSP Create
MSP Management
MSP Commands
MSP Delete
Port Loopback Configuration
Loopback Management
LAPD Configuration
AU4 Concatenation
POM/SUT Configuration
TP Configuration

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 38 / 926
926
SDH port
Port TP Thresholds Configuration

Cross Connection Cross Connection Management
Create Cross Connections
Modify Cross Connections
Show Supporting Board
Show TP Performance Data 15 minutes

24 hours
Performance Configure Monitoring

Display Current Data
Display History Data
Navigate to Transmission View
PDH port
Port Physical Media PDH Line Length Configuration

Loopback Management
PDH TP Configuration
TP Configuration
TP Thresholds Configuration

24 hours


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 39 / 926
926
Transmission Add TP

Expand Next Level of Lower TPs
All Lower TPs
Next Level of Upper TPs
All Upper TPs
Hide Lower TPs
Upper TPs
TP Configuration Selected TPs
Alarm Persistency time
Degraded Signal Threshold
Terminate TP
Disterminate TP

Port Switch Over
Show Cross Connected TPs
POM/SUT Creation/Delation
Configuration

Structure TPs TU2

TU3
TU12
VC3 / VC4
VC12

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 40 / 926
926
Transmission Physical Media Als Management
Show Optical Configuration

Tx Quality Configuration
Single Fiber Configuration
Extra Traffic
Regenerator Section Management
MSP Management
MS_Configuration
MSP Commands
NE MSP Synthesis
Loopback Management
Line Length Configuration
Show Supported Board
Navigate to Port View

Navigate to selected TP
Synchronization Timing Source Configuration

Protection Commands
T0 Configuration
T4 Configuration
T0_TEST Configuration
SSU Configuration
Remove Timing Reference
Set T0 Equal T4
Remove T0 Equal T4
Transmitted SSM Quality Configuration
Frame Mode Configuration

Show Timing Source
External Points Configuration

Display Show External Input Points
Show External Output Points
Show All External Points

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 41 / 926
926
2.3 1353SH Menu Commands for W/OMSN using P.4.x. USM version
1353SH USM 4.x. FOR W/OMSN

Views Previous
Equipment
External Points
Transmission
Synchronization
Open object
Open in Window
Close
Set SdhNe Alarms Severities
NE Time
Performance Forced Performances Collection
Threshold Tables
Set ACD Level

Loopback Management

OS Configuration
LAPD Configuration
RAP Configuration
MESA Configuration

OH Phone Parameters
OH Tp Creation
OH Tp Deleting
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 2. W/OMSN Menu bar for P.4.x. USM version
3AL 89062 AA AA 42 / 926
926
Diagnosis Alarms NE alarms
Object Alarms
Subtree Alarms
Equipment Alarms
Transmission Alarms

24 Hours
(logld,2)
Stop
Align down
Align up
Activate
Access State OS
Local
Allow Notifs
Inhibit Notifs
Set Manager List
Restart NE
continues Figure 2. W/OMSN Menu bar for P.4.x. USM version

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 43 / 926
926

Create a MS–SPRing Schema
Manage Ring Map
Units info
Mib management
Servers management
UHR 1
Radio RPS Configure
UHRN 1
Switch
Synthesis
ATPC Power Setting
Configure Scheme
Static Delay Configure Units
Frequency Agility Switch
Power Measurement Synthesis
Power Meas File Reading Extra Traffic
EPS Management
Configure
Switch
Equipment Set
Modify
Remove
Set in Service
Set out of Service
Reset
Software Desription
Cable Connection Board Level
Show Supporting Equipment

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 44 / 926
926
Board menu
Board Port Access
SDH port
Port TP Configuration
AU4 Concatenation
POM/SUT Creation/Deletion
Configuration

24 hours


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 45 / 926
926
SDH port

Port Loopback Port Loopback Configuration
Loopback Management
Physical Media ALS Management

TX Quality Configuration
LAPD Configuration
MSP MSP Create
MSP Management
MSP Commands
MSP Delete

PDH port

24 hours
Loopback Port Loopback Configuration

Loopback Management
Physical Media Line Length Configuration


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 46 / 926
926
Transmission Add TP

All Lower TPs
All Upper TPs
Hide Lower TPs
TP Configuration Upper TPs
PDH TP Configuration Selected TPs

Port Switch Over
Show Cross Connected Tps
Configuration

Structure VC4 TU3 TU3 TU3
” ” ”
TU12 TU12 TU12
Loopback Port LoopbackConfiguration
Loopback Management

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 47 / 926
926
Transmission Physical Media ALS Management

Extra traffic
MSP MSP Create

MSP Management
MSP Commands
MSP Delete
Show Supported Board NE MSP Synthesis

Protection Commands
T0 Configuration
T4 Configuration
SSU Configuration
Set T0 Equal T4
Remove T0 Equal T4
(Frame Mode Configuration)

Show Timing Source


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 48 / 926
926
1353SH USM 5.x FOR W/OMSN

Views Previous
Equipment
External Points
Transmission
Synchronization
Open object
Open in Window
Close
NE Time
Set ACD Level Threshold Tables

Loopback Management

OS Configuration
LAPD Configuration
RAP Configuration
MESA Configuration

OH Phone Parameters
OH Tp Creation
OH Tp Deleting
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 49 / 926
926

Object Alarms
Subtree Alarms
Equipment Alarms
Transmission Alarms

24 Hours
(logld,2)
Stop
Align down
Align up
Activate
Access State OS
Local
Allow Notifs
Inhibit Notifs
Set Manager List
Restart NE

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 50 / 926
926

Create a MS–SPRing Schema
Manage Ring Map
Units info
Mib management
Servers management
EPS Management
Configure
Switch
Equipment Set
Modify
Remove
Set in Service
Set out of Service
Reset
Software Desription
Board Level

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 51 / 926
926


Board menu
Board Port Access
Change Physical Interface
SDH port
AU4 Concatenation
Configuration

24 hours


Loopback Management

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 52 / 926
926
SDH port
Port MSP MSP Create

MSP Management
MSP Commands
MSP Delete
LAPD Configuration
Ms Configuration
PDH port
TP Frame Mode Configuration

24 hours

Loopback Management
HDSL Configuration
NT G703/704 Configuration
Show Supporting Board NT X21 Configuration

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 53 / 926
926
Transmission Add TP

All Lower TPs
All Upper TPs
Hide Lower TPs
TP Frame Configuration Selected TPs
Terminate TP
Disterminate TP

Port Switch Over
Configuration

Structure TPs TU2

TU3
TU12
VC3/VC4
VC12
Loopback Management

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 54 / 926
926

Extra traffic
Set Domain
HDSL Configuration
NT Configuration
X21 Configuration
MSP MSP Create
Show Supported Board MSP Management
MSP Commands
Navigate to Port View MSP Delete
Synchronization Timing Source Configuration NE MSP Synthesis
Protection Commands
T0 Configuration
T4 Configuration
SSU Configuration
Change T4<–>T5
Change 2MHz.<–>2Mbit
Set T0 Equal T4
Remove T0 Equal T4
Show Timing Source

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 55 / 926
926
2.5 1353SH Menu Commands for UHR, LHR 1, UHRN with P.5.x. USM version
1353SH USM 5.x FOR WMSN

Views Backward
Forward
Equipment
External Points
Refresh
Open object
Open in Window
Close
NE Time
Performance Threshold Tables
EPS Overview (not on LHR)
Loopback Management

OS Configuration
Interfaces Config. LAPD Configuration
OSI Routing Config. RAP Configuration

MESA Configuration

OH Phone Parameters
Office Alarm Delay Time
(Not supported) OH Tp Creation
OH Tp Deleting
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 4. WMSN Menu bar for P.5.x. USM version
3AL 89062 AA AA 56 / 926
926
Object Alarms
Subtree Alarms
Equipment Alarms
Transmission Alarms

24 Hours
Log Browsing (logld,1)
(logld,2)

Stop
Align Down
Align Up
Activate
Access State OS
Local
Allow Notifs
Inhibit Notifs
Set Manager List

(not implemented yet)
Restart NE
Units info
Mib management
continues Figure 4. WMSN Menu bar for P.5.x. USM version

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 57 / 926
926
Radio RPS Configure Schema

for UHR

Units
Static Delay Rx Side
Switch
Synthesis
Extra Traffic (on UHR only)
Frequency Agility
Power Measurement Graphic Power Measurement
File Reading
ATPC Power and Threshold Setting

Gain ATPC Identifier
Radio Abnormal Condition list
Carrier Status
Voltage Control Oscillator Status

for LHR
Units
Switch
Synthesis
Extra Traffic
RFCOH Configure
Switch
Synthesis
Frequency
File Reading
Squelch ATPC Identifier
Gain
Hop Trace

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 58 / 926
926
Radio Radio Abnormal Condition list

for LHR
Frequency Reuse
Equalization Delay
EPS Management
(UHR
UHRN 2) Configure
Switch
Equipment Set
Modify
Remove
Set in Service
Set out of Service
Reset (Not implemented jet)
Software Desription
Board Level
Show Supported Port

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 59 / 926
926


Board menu
Board Port Access
Change Physical Interface (Not supported)
Port TP Configuration (on LHR only)
AU4 Concatenation (Not yet implemented)


Loopback Management

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 60 / 926
926
Port Physical Media ALS Management

(for UHR and LHR) Show Optical Configuration
LAPD Configuration
Ms Configuration (Not supported)

Refresh
Ber Not Intrusive (only on LHR)


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 61 / 926
926

Views Backward
Forward
Equipment
External Points
Transmission
Synchronization
Refresh
Open object
Open in Window
Close

NE Time
EPS overview Threshold Tables
Set ACD Level
Loopback Management

OS Configuration
Interfaces Configuration LAPD Configuration
OSI Routing Configuration RAP Configuration
MESA Configuration
IP Configuration IP Static Routing Configuration

OSPF Area Configuration
IP Address Configuration of
point–to–point interfaces
ISA board IP address
Tunnelling Configuration IP Over OSI

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 62 / 926
926
Configuration OverHead OH Cross Connection

OH Phone Parameters
OH Tp Creation
OH Tp Deleting
MSP Overview
ATM Configuration

Units
Switch
Synthesis
Extra Traffic (Not supported)
Frequency Agility
File Reading
Gain ATPC Identifier
Radio Abnormal Condition list
Carrier Status
Synchro Role

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 63 / 926
926

NE alarms

Diagnosis Alarms
Object Alarms
Subtree Alarms
Equipment Alarms
Transmission Alarms

24 Hours
Log Browsing Alarm Log
Event Log
Software Trace Log
Stop
Align down
Align up
Activate
Access State OS
Local
Allow Notifs
Inhibit Notifs
Set Manager List
Restart NE

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 64 / 926
926
Units info
(Mib Management for Craft only)
Servers management
EPS Management
Configure
Switch
Equipment Set
Modify
Remove
Set in Service
Set out of Service
Reset
Software Description
Board Level
ISA Board IP address (available at subrack level for B version)
ATM start sup.(not operative)

ATM stop sup.(not operative)
ATM navigate

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 65 / 926
926


Board menu
Board Port Access

ATM Configuration (available onB version)
SDH port
AU4 Concatenation

Configuration

24 hours


Loopback Management

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 66 / 926
926
SDH port
Port MSP MSP Create

MSP Management
MSP Commands
MSP Delete
LAPD Configuration
Ms Configuration
PDH port
TP Frame Mode Configuration
Set Retiming Enable
Disable
24 hours

Loopback Management
HDSL Configuration
NT G703/704 Configuration
NT X21 Configuration

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 67 / 926
926
Transmission Add TP

All Lower TPs
All Upper TPs
Hide Lower TPs
TP Frame Configuration Selected TPs
Terminate TP
Disterminate TP
AU4 Concatenation

Port Switch Over
Configuration

Structure TPs TU2

TU3
TU12
VC3/VC4
VC12
Loopback Management

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 68 / 926
926

Extra traffic
Set Domain
HDSL Configuration
NT Configuration
X21 Configuration
MSP MSP Create
Show Supported Board MSP Management
MSP Commands
Navigate to Port View MSP Delete
Synchronization Timing Source Configuration NE MSP Synthesis
Protection Commands
T0 Configuration
T4 Configuration
SSU Configuration
Change T4<–>T5
Change 2MHz.<–>2Mbit
Set T0 Equal T4
Remove T0 Equal T4
Show Timing Source

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 69 / 926
926
2.7 1353SH Menu Commands for OMSG using USM P.4.x.
1353SH USM 4....FOR OMSG

Views Previous
Room
Equipment Overview
Transmission
Synchronization
Open Object
Open in Window
Close

Set Alarms Severities
NE Time
Threshold Tables
Set ACD Level
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 6. OMSG Menu bar for 4.x USM version
3AL 89062 AA AA 70 / 926
926

Object Alarms
Subtree Alarms
Equipment Alarms
Transmission Alarms

24 Hours
Events Log (logId, theDefaultLog)

(logId, theSecurityLog)
(logld,1)
(logld,2)
Supervision Access State OS

Local
Allow Notifs
Inhibit Notifs
Set Manager List
continues Figure 6. OMSG Menu bar for 4.x USM version

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 71 / 926
926

Room

Zoom in
Zoom out
Fit to Contents
Navigate to Selected Rack
Edit
Equipment Set
Modify
Remove
Set in Service
Set out of Service
Reset
Remote Inventory Rack Level
Subrack Level
Board Level
Equipment Overview Add Equipment

Expand next level
Expand whole subtree
Hide equipment
Hide lower equipment
Hide all empty slots

Set in service
Set out of service
Reset
Remote Inventory
Navigate to Equipment View

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 72 / 926
926
EPS Management
Configure
Switch
Board menu
Board Set Domain

Port Access


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 73 / 926
926

Port Physical Media(PDH port) PDH Line Lengh Configuration
(SDH port) Ms Ber Configuration

Optical Laser Configuration
Als Management
SDH Tx Ssm Quality Configuration
SDH Single Fiber Configuration
MSP Management
MSP Commands
Concatenation (SDH port) Concatenate 4

(only 4/4 OMSG)
Deconcatenate
PDH TP Configuration (PDH port)
TP Configuration
POM/SUT (SDH port) Creation/Deletion

Configuration

Browse Cross Connections
Show Performance Data 15 minutes

24 hours

Navigate to MSP related unit (SDH port)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 74 / 926
926
Transmission Add TP

All Lower TPs
All Upper TPs
Hide Lower TPs
Upper TPs
TP Configuration Selected TPs
Alarm Persistency Time
Terminate TP
Disterminate TP

Port Switch Over
Blocking Info
Configuration
Show Performance Data 15 minutes
24 hours

Structure TPs TU2

TU3
TU12
VC3
VC4
VC12

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 75 / 926
926
Transmission Physical Media Als Management

MSP Management
MSP Commands
Loopback Management
Set Domain
Navigate to Equipment Overview

Protection Commands
T0 Configuration
T4 Configuration
Show Timing Source

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 76 / 926
926
2.8 1353SH Menu Commands for OMSG using USM P.7.x.
1353SH USM 7.x FOR OMSG

Views Previous
Room
MS–Spring
Equipment Overview
Transmission
Synchronization
Open Object
Open in Window
Refresh (not used for OMSG)
Close
Exit

NE Time
(only applicable on SH)
Threshold Tables
Set ACD Level
Loopback Management
EPS Status
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 7. OMSG Menu bar for 7.x USM version
3AL 89062 AA AA 77 / 926
926

Diagnosis

Alarms NE Alarms
Object Alarms
Subtree Alarms
Equipment Alarms
Transmission Alarms

24 Hours
Events Log Alarm Log

Event Log

Installation Details
(Show Matrix Type)
Supervision Access State OS (on CT and SH-DXC)

Requested (on CT) /
Local (on SH-DXC)
Allow Notifs
Inhibit Notifs
Set Manager List
MS–SPRing
Management

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 78 / 926
926
Room Zoom in
Zoom out
Fit to Contents
Modify User Data
Show PCT Rack ID
Show Rack Number
Edit
Equipment Set (not available on OMSG)
Modify (not available on OMSG)
Remove (not available on OMSG)
Set in Service
Set out of Service
Reset

Show Supporting Equipment Subrack Level
Navigate to Equipment Overview Board Level
Clipboard
Permanently hide empty slots
Expand next level
Hide equipment

Set in service
Set out of service
Reset
Remote Inventory (Board Level)
Set Domain

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 79 / 926
926

EPS EPS Status
Management
Configure (not available on OMSG)
Switch
From the Equipment View open the selected board (open object or mouse clicking) to visualize
the Board menu
Board Set Domain



1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 80 / 926
926
From the Board View open the selected board (open object or mouse clicking) to visualize the
Port menu: SDH or PDH port menu will be available according to the selected board.
Port Add TP
TP Configuration
AU4 Concatenation Concatenate 4
Concatenate 16
Concatenate 64
Deconcatenate
Port Switch Over
Browse Cross Connection
Configuration

Loopback Management
MSP MSP Management
MSP Commands
Physical Media Als Management

MS Configuration
Set Domain
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 81 / 926
926
Transmission Add TP


All Lower TPs
All Upper TPs
Hide Lower TPs
Upper TPs
Selected TPs
Sibling TPs
Preferences Active Updates
TP Configuration Show Panner
Terminate TP (not available on Lambda Gate)
Disterminate TP (not available on Lambda Gate)
Clipboard (not available on Lambda Gate)
Concatenate 16
Concatenate 64
Deconcatenate
Port Switch Over
Blocking Info
Show All Cross Connected TPs
Configuration
Structure TPs TU3
(not available on Lambda Gate) TU12
VC3/VC 4
VC12
Loopback Management
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 82 / 926
926
Transmission MSP MSP Management

MSP Commands

Tx SSM Quality Configuration
MS Configuration
Set Domain
Navigate to Msspring View

Protection Commands
T0 Configuration
T4 Configuration
SSU Configuration (not available on OMSG)
Remove Timing Reference(not applicable to OMSG)
Set T0 Equal T4 (not applicable to OMSG)
Frame Mode Configuration (not available on OMSG)
Show Timing Source

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 83 / 926
926
2.9 1353SH Menu Commands for 1674LG Rel.1.1 using USM P.8.x.
1353SH USM 8.x FOR 1674LG

Views Previous
Room
Equipment Overview
Transmission
Synchronization
Open Object
Open in Window
Refresh (not used for OMSG)
Close
Exit

NE Time
(only applicable on SH)
Threshold Tables
Set ACD Level
Loopback Management
Port Details
EPS Status
MSP Status
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 8. 1674LG Menu bar for 8.x USM version
3AL 89062 AA AA 84 / 926
926
Diagnosis
Alarms NE Alarms
Object Alarms
Subtree Alarms
Equipment Alarms
Transmission Alarms
Events Log Alarm Log

Event Log

Installation Details
(Show Matrix Type)
Supervision Access State OS (on CT and SH-DXC)

Requested (on CT) /
Local (on SH-DXC)
Allow Notifs
Inhibit Notifs
Set Manager List
continues Figure 8. 1674LG Menu bar for 8.x USM version

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 85 / 926
926
Room Zoom in

Zoom out
Fit to Contents
Modify User Data
Show PCT Rack ID
Show Rack Number
Edit
Equipment Set (not available on OMSG)

Modify (not available on OMSG)
Remove (not available on OMSG)
Set in Service
Set out of Service
Reset

Show Supporting Equipment Subrack Level
Navigate to Equipment Overview Board Level

Clipboard
Expand next level
Hide equipment

Set in service

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 86 / 926
926
Equipment Overview Set out of service
Reset
Remote Inventory (Board Level)
Set Domain
Port Details

EPS EPS Status

Management
Configure (not available on OMSG)
Switch
From the Equipment View open the selected board (open object or mouse clicking) to visualize
the Board menu
Board Set Domain

Port Details


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 87 / 926
926
From the Board View open the selected board (open object or mouse clicking) to visualize the

Port menu: SDH or PDH port menu will be available according to the selected board.

Port Add TP
TP Configuration
Concatenate 16
Concatenate 64
Deconcatenate
Port Switch Over
Browse Cross Connection
Configuration

Loopback Management
MSP MSP Management
MSP Commands

MS Configuration
Set Domain
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 88 / 926
926
Transmission Add TP

All Lower TPs

All Upper TPs
Hide Lower TPs

Upper TPs
Selected TPs
Sibling TPs
Preferences Active Updates

TP Configuration Show Panner

Concatenate 16
Concatenate 64
Deconcatenate

Port Switch Over
Blocking Info
Monitoring Operations Creation/Deletion

Configuration


Loopback Management
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 89 / 926
926

Transmission MSP MSP Management
MSP Commands
MSP Status

MS Configuration
Set Domain
Port Details
Synchronization Create Timing Source

Configuration Timing Source
Remove Timing Source
Protection Commands
T0 Configuration
Output Configuration
SSU Configuration (not supported by 1674LG 1.1)
Change Output T4–>T5 / Change Output T5–>T4
Change Output T0–>T4 / Disconnect T0–> T4


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 90 / 926
926
2.10 1353SH Menu Commands for 1686 WM Rel. 3.3
1353SH USM1.2.x FOR 1686WM

VIEW Previous
Equipment
External Points
Comm/routing Local configuration
Open objet OS configuration
Open in Window LAPD configuration
Close
Configuration Alarms Severities... ASAPs Management

Set alarms Severities ASAPs Management
NE Time...

Object Alarms
Subtree Alarms
Equipment Alarms
Transmission Alarms
Events log (logld,1)

(logld,2)

Local
Allow Notifs
Upload Remote Inventory Inhibit Notif
1AA 00014 0004 (9007) A4 – ALICE 04.10
Note: Some generic menus and options are used for the EML–USM. The Specific menus for 1686WM are
written in bold characters.
Figure 9. 1686WM Rel 3.3 Menu bar
3AL 89062 AA AA 91 / 926
926

Download Init download...
Units info...
Restart NE...
Equipment Set
Modify
Remove
Set in service
Set out of service
Reset
Remote Inventory Rack level
Subrack level
Board level
Help On help
On context
Glossary
About
Tutorial
continues Figure 9. 1686 WM Rel. 3.3 Menu bar

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 92 / 926
926
When the External Points is activated, External Points menu appears


Display Show External input Points
Show External output Points
Show All external Points
In a board view the board menu appears
Board Set Domain

Port Access
Output power
Alarm Threshold configuration If supported
Current instantaneous measures by the Equipment
From the board menu a port menu is avalailable. OGPI or OTS ports are used
according to the selected board.
OGPI port
Port Show supporting board

FEC configuration
Display channel number
OTS port

APSD configuration
Osc Synchr Configuration Local
Receive
Opt Add/Drop Configuration Drop – Insert
Pass – Through
continues Figure 9. 1686 WM Rel. 3.3 Menu bar

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 93 / 926
926
2.11 1353SH Menu Commands for 1686 WM Rel. 3.4A

Views Previous
Equipment
External Points A
Transmission B
Open Object
Open in Window...
Close
Configuration Alarms Severities...

Set Alarm Severities
NE Time...
Comm/routing Local Configuration
OS Configuration
NTP Status Configuration
LAPD Configuration
Diagnosis Alarms NE alarms...

Object Alarms...
Subtree Alarms...
Equipment Alarms...
Transmission Alarms...

(logld,2)
View Remote Inventory...

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 10. 1686WM Rel. 3.4A Menu bar
3AL 89062 AA AA 94 / 926
926

Local
Allow Notifs
Upload Remote Inventory Inhibit Notifs
Set Manager List
Restart NE...

Units info...
Mib management...
Set Manager List...
Equipment Set
Modify
Remove
Set in Service
Set out of Service
Subrack level
Board level
Help On Help
On Context
Glossary
About...
Tutorial
1AA 00014 0004 (9007) A4 – ALICE 04.10
continues Figure 10. 1686WM Rel. 3.4A Menu bar
3AL 89062 AA AA 95 / 926
926


A

Board Set Domain

Port Access
Alarm Threshold configuration
Optical power level configuration
Current instantaneous measures
If supported Forced ON
Laser control for test RX side
by the Equipment Normal
TX side
Forced OFF
OGPI/OCHA port
Show supporting board
FEC configuration
Display channel frequency
BER Threshold Configuration If supported
by the Equipment
Current Counter values
Payload configuration
Shutdown criteria configuration
Trail Monitor Create
Delete

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 96 / 926
926
OTS/OMS port
APSD configuration
Receive
Pass – Through
OTs/Oms Ber Threshold configuration E–3/E–4

E–4/E–5
E–5/E–6
Transmission Add TP

All Lower TPs
All Upper TPs
Hide Lower TPs
Upper TPs
Selected TPs
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 97 / 926
926
2.12 1353SH Menu Commands for 1686WM Rel. 3.5

Views Backward
Forward
Equipment
External Points A
Transmission B
Open Object
Open in Window...
Close

Set Alarm Severities
NE Time...

Threshold Tables
OS Configuration
Phone Parameters
OH Tp Creation
OH Tp Deleting
Object Alarms...
Subtree Alarms...
Equipment Alarms...
24 Hours
Event Log
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 11. 1686WM Rel. 3.5 Menu bar
3AL 89062 AA AA 98 / 926
926

Local
Allow Notifs
Restart NE...

Units info...
Mib management...
Equipment Set
Modify
Remove
Set in Service
Set out of Service
Reset
Subrack level
Board level
Help On Help
On Context
Glossary
About...
Tutorial
continues Figure 11. 1686WM Rel. 3.5 Menu bar

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 99 / 926
926


A

Board Set Domain (not operative)

Port Access
Change Physical Interface (not operative)
Alarm Threshold configuration
If supported Current instantaneous measures
by the Equipment Laser control for test Forced ON
Normal
Payload configuration Forced OFF
OGPI/OCHA port Show supporting board
FEC Enabled
Display channel frequency
BER Threshold Configuration
Current Counter values If supported
Shutdown criteria configuration by the Equipment

Delete
Path trace configuration
Note: The generic EML–USM options are common to W/OMSN . The Specific options for 1686WM are
1AA 00014 0004 (9007) A4 – ALICE 04.10
written in bold characters. Some common options are written in bold to distinguish them from the W/OMSN
common features.
3AL 89062 AA AA 100 / 926
926
OTS/OMS port
APSD configuration
Receive
Pass – Through

Display Channel Frequency E–4/E–5
E–5/E–6
Show OCH port view
B
Transmission Add TP

All Lower TPs
Expand all levels
All Upper TPs
Hide Lower TPs
Upper TPs
Show supporting board Selected TPs
LAPD Configuration
APSD configuration

E–4/E–5
Osc Synchr Configuration E–5/E–6
Local
Receive
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 101 / 926
926
2.13 1353SH Menu Commands for 1640 WM Rel. 1.2A


VIEWS Previous
Equipment
Comm/routing Local configuration
Open objet OS configuration
Open in Window LAPD configuration

Ethernet configuration
Close

NE Time...
Diagnosis Alarm NE alarms

Events log Object Alarms
Subtree Alarms
Equipment Alarms
Transmission Alarms

Local
Allow Notifs
Inhibit Notifs

Units info...
Restart NE...
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 12. 1640 WM Rel. 1.2A Menu bar
3AL 89062 AA AA 102 / 926
926
Equipment Set
Modify
Remove
Set in service
Set out of service
Reset
When a board is selected the board menu appears with the associated options
Board Set domain (not available in every version)

Port Access
Output power level
frequency and grid configuration
Current instantaneous measures
OGPI port

FEC configuration
Display channel number
OTS port
1AA 00014 0004 (9007) A4 – ALICE 04.10
continues Figure 12. 1640 WM Rel. 1.2A Menu bar
3AL 89062 AA AA 103 / 926
926
2.14 1353SH Menu Commands for 1640 WM Rel. 1.2C


Views Previous
Equipment
Transmission
Open Object
Open in Window
Close

Set Alarms Severities...
NE Time...
Performance Threshold Tables...
Set ACD Level...

Cross Connection Management...

OS Configuration
LAPD Configuration

Object Alarms...
Subtree Alarms...
Equipment Alarms...
Performance Data 15 Minutes...
24 Hours...
(logld,2)
Abnormal condition list
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 13. 1640 WM Rel. 1.2C Menu bar
3AL 89062 AA AA 104 / 926
926

Local
Allow Notifs
Set Manager List...
Restart NE...

Units info...
Mib management...
Equipment Set...
Modify...
Remove
Set in Service
Set out of Service
Reset
Software Description...
Remote Inventory Rack Level...
Subrack Level...
Show Supporting Equipment Board Level...
continues Figure 13. 1640 WM Rel.1.2C Menu bar

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 105 / 926
926

Board Set Domain...

Port Access
Alarm threshold configuration
Output power
Current instantaneous measurements
Frequency and grid configuration
Pumps configuration Connect pump 1
Disconnect pump 2
From the port view, a port meu is available. OGPI, OTS, OCHA or OCH ports are used
OGPI port
Port Show Supporting Board

Navigate to Transmission View A
FEC enabled
Display Channel Frequency
Delete

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 106 / 926
926
OTS port

OCHA block

FEC enabled
OCH port

FEC enabled

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 107 / 926
926

A
Transmission Add TP

All Lower TPs
All Upper TPs
Hide Lower TPs
Upper TPs
Selected TPs
FEC enabled
Display Channel Frequency...
LAPD configuration...

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 108 / 926
926
2.15 1353SH Menu Commands for 1640 WM Rel. 3.0

Views Previous
Equipment
Transmission
Open Object
Open in Window...
Close

NE Time...

OS Configuration
LAPD Configuration

Object Alarms...
Subtree Alarms...
Equipment Alarms...
24 Hours...
(logld,2)
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 14. 1640WM Menu bar
3AL 89062 AA AA 109 / 926
926

Local
Allow Notifs
Inhibit Notifs
Restart NE...

Units info...
Mib management...
Equipment Set...
Modify...
Remove
Set in Service
Set out of Service
Reset
Subrack Level...
Figure 15. 1640WM Menu bar (continued)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 110 / 926
926
Board Set Domain...

Port Access

Disconnect pump 2
Amplifier settings
MSV Configuration
From the port view, a port memu is available.

OGPI, OTS, OCHA, OCH, OMS or OMSA ports are displayed according to the board.
The Port menu depends on the selected port.
OGPI port

FEC enabled

Delete

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 111 / 926
926

OTS port
OCHA block

FEC enabled

OCH port

FEC enabled

Delete
Figure 17. 1640 WM Menu bar (continued)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 112 / 926
926
OMS port/OMSA port

Trail Monitoring Block

FEC enabled


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 113 / 926
926

A
Transmission Add TP...

All Lower TPs
All Upper TPs
Hide Lower TPs
Upper TPs
Selected TPs

FEC enabled

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 114 / 926
926
2.16 1353SH Menu Commands for 1640WM Rel. 3.1

Views Bacward
Forward
Equipment
External Points
Transmission
Open Object
Open in Window...
Close

NE Time...

OS Configuration
Interface Configuration LAPD Configuration
IP Configuration OSPF Area Configuration

Object Alarms...
Subtree Alarms...
Equipment Alarms...
External Alarms
24 Hours...
Event Log
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 20. 1640WM Menu bar
3AL 89062 AA AA 115 / 926
926

Local
Allow Notifs
Inhibit Notifs
Restart NE...

Units info...
Mib management...
Equipment Set...
Modify...
Remove
Set in Service
Set out of Service
Reset

Subrack Level...
Istantaneous Measurement On Selected Object

(not operative)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 116 / 926
926
Board Set Domain...

Port Access

Disconnect pump 2
Amplifier settings
MSV Configuration
From the port view, a port memu is available.

OGPI, OTS, OCHA, OCH, OMS or OMSA ports are displayed according to the board.
The Port menu depends on the selected port.
OGPI port

FEC enabled

Delete

1AA 00014 0004 (9007) A4 – ALICE 04.10
Note: The generic EML–USM options are common to W/OMSN . The Specific options for 1640WM are
common features.
3AL 89062 AA AA 117 / 926
926

OTS port
OCHA block

FEC enabled
BER Treshold Configuration
Opt Add/Drop Configuration Drop–Insert

Pass–Through

OCH port
FEC enabled

Delete

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 118 / 926
926
OMS port/OMSA port

Trail Monitoring Block

FEC enabled


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 119 / 926
926

A

All Lower TPs
All Upper TPs
Hide Lower TPs
Upper TPs
Selected TPs

FEC enabled

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 120 / 926
926
2.17 1353SH Menu Commands for OPS Rel. 1.0
1353SH USM1.4.x FOR OPS

Views Previous
Equipment
External Points A
Transmission
Open Object
Open in Window...
Close

NE Time...
Set ACD Level...

OS Configuration
NTP Status Configuration

Object Alarms...
Subtree Alarms...
Equipment Alarms...

(logld,2)

1AA 00014 0004 (9007) A4 – ALICE 04.10
Note: Some generic menus and options are used for the EML–USM. The Specific menus for OPS are writ-
ten in bold characters.
Figure 26. OPS R1.0 Menu bar
3AL 89062 AA AA 121 / 926
926

Local
Allow Notifs
Set Manager List...
Restart NE...

Units info...
Mib management...
Equipment Set
Remove
Set in Service
Set out of Service
Subrack level
Board level
Help On Help
On Context
Glossary
About...
Tutorial
continues Figure 26. OPS R.1.0 Menu bar

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 122 / 926
926


A Show External Output Points
Board Port Access
Alarm threshold configuration If supported

Current instantaneous measurement by the Equipment
From the board menu a port menu is avalailable. OGPI ports are used
OGPI port



1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 123 / 926
926


All Lower TPs
All Upper TPs
Hide Lower TPs
Upper TPs
Selected TPs
Cross connection Cross Connection Management


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 124 / 926
926
2.18 1353SH Menu Commands for OCP Rel. 1.0
1353SH USM 1.4.x FOR OCP

Views Previous
Equipment D
External Points A
Transmission B
Open Object
Open in Window...
Close

NE Time...

OS Configuration

Object Alarms...
Subtree Alarms...
Equipment Alarms...
External Points Alarms...

(logld,2)

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 27. OCP R.1.0 Menu bar
3AL 89062 AA AA 125 / 926
926

Local
Allow Notifs
Restart NE...

Units info...
Mib management...
Equipment Set...
Modify...
D Remove
Set in Service
Set out of Service
Reset
Subrack level...
Board level...
Help On Help
On Context
Glossary
About...
Tutorial
1AA 00014 0004 (9007) A4 – ALICE 04.10
continues Figure 27. OCP R.1.0 Menu bar
3AL 89062 AA AA 126 / 926
926
When the External Points is activated, External Points menu appears.

A
In a Board view, the following board menu is avalaible.
Board Set Domain
Port Access C
In the Port view, the following Port menu is avalaible.

OGPI ports are used according to the selected board.
OGPI port
C
Navigate to Transmission View B


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 127 / 926
926

B

All Lower TPs
All Upper TPs
Hide Lower TPs
Upper TPs
Selected TPs
Performance

Navigate to Port View C
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 128 / 926
926
2.19 1353SH Menu Commands for 1696MS Rel.1.0
1353SH USM1.4.x FOR 1696MS

Views Previous
Equipment
External Points A
Transmission
Open Object
Open in Window...
Close

NE Time...
Loopback Management

OS Configuration
Office Alarm Delay Time (not operatve)

Object Alarms...
Subtree Alarms...
Equipment Alarms...
Performance data (not operative)

(logld,2)

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 28. 1696MS R1.0 Menu bar
3AL 89062 AA AA 129 / 926
926

Local
Allow Notifs
Restart NE...

Units info...
Mib management...
Equipment Set
Modify (not operative)
Remove
Set in Service
Set out of Service
Reset
Show Supporting Equipment Subrack level
Board level
Help On Help
On Context
Glossary
About...
Tutorial
continues Figure 28. 1696MS R.1.0 Menu bar

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 130 / 926
926


Port Access

Current instantaneous measurement
From the board menu a port menu is avalailable. OGPI ports are used
OGPI port



Delete

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 131 / 926
926

OTS port

APSD Configuration
Osc Synchro Configuration (not operative)

Ots BER Threshold Configuration (not operative)
Opt Add / Drop Configuration Drop–Insert

Pass–Trough
Show OCH Port View

All Lower TPs
All Upper TPs
Hide Lower TPs
Upper TPs
Selected TPs
Performance Create Cross Connections
Loopback
APSD Configuration
Ots BER Threshold Configuration (not operative)


1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 132 / 926
926
2.20 1353SH Menu Commands for 1696MS Rel.1.1

Views Backward
Forward
Equipment
External Points A
Transmission
Open Object
Open in Window...
Close

NE Time...
Performance Threshold Tables
Loopback Management
OS Configuration
Office Alarm Delay Time Ethernet Configuration
(not operative)
Object Alarms...
Subtree Alarms...
Equipment Alarms...
External Points Alarms...
Performance data 15 Minutes

24 Hours
Event Log

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 29. 1696MS R.1.1 Menu bar
3AL 89062 AA AA 133 / 926
926

Local
Allow Notifs
Restart NE...

Units info...
Mib management...

(generic)
Equipment Set
Modify (not operative)
Remove
Set in Service
Set out of Service
Reset
Show Supporting Equipment Subrack level
Board level
Instantaneous Measurement On Selected Object

(not operative)
Help On Help
On Context
Glossary
About...
Tutorial

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 134 / 926
926


For different boards different board menus are available

Port Access

Current instantaneous measurement
Payload Configuration (on MCC)
Alarm Threshold Configuration (on OADM)
Output Setting (on OAC)
VOA Tunning (on OAC)
For different boards different port menus are displayed.
OGPI port Show Supporting Board



Delete

Loopback management
Cable Configuration
Note: The generic EML–USM options are common to W/OMSN . The Specific options for 1696MS are
1AA 00014 0004 (9007) A4 – ALICE 04.10
common features.
3AL 89062 AA AA 135 / 926
926

OTS port Show Supporting Board
APSD Configuration
Ots BER Threshold Configuration E–3E–4

E–4E–5
E–5E–6

Loopback Management

All Lower TPs
All Upper TPs
Hide Lower TPs

Upper TPs
Selected TPs
Cross connection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 136 / 926
926
Transmission Performance Configure Monitoring

Dispay Current Data

Loopback Management

Cable Confguration

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 137 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
138 / 926
3 NE MANAGEMENT
In this chapter the different actions relative to the Equipment NE views are defined (supervision, MIB align-
ment, time management, frame management ...) and the different menu options described.
3.1 NE management states
3.1.1 Introduction
The elementary building blocks of any telecommunication network are the Network Elements (NEs). This
section presents the different management states of an NE from the EML–USM point of view. There are
a number of Management states and one Alarm status:
– Supervision state:
– gives information relative to the supervision state of the NE. There are 4 states.
• Declared: the NE is not being supervised (e.g. it has just been declared to the OS: brown)).
• Supervised: the NE is under supervision (green).
• Activating: the NE is being brought under supervision and no management tasks can be per-
formed on it.
• Deactivating: the supervision process on the NE is being stopped and no management tasks
can be performed on it.
Only an NE in Supervised state can be fully managed by the USM application. Please note the
software downloading operations can be also applied to a Declared NE.
– MIB Alignment state:
relates to the agreement between the NE MIB and its representation within the simulator database
(for Q3 NEs, such as the OMSG, the EMLCore is used in an OS system without MIB). There are 2
states.
• Misaligned: the system is not able to provide the operator the vision of the current NE configu-
ration. This is due to a communication loss (blue).
• Aligned: the system is able to provide the operator the vision of the current NE configuration
(green).
N.B. The alignment state changes to misaligned automatically when the operational state goes
to disabled.
– occurs during the NE Supervision state. There are 2 states.

• Misaligned: this is a transitory state before being able to visualize the NE configuration.
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
Aligned: the system becomes aligned when all the operations for synchronizing the SH with
the NE are fully completed. For the Q3 / SNMP NEs the synchronization procedure involves the
alarms, the PM and the NE configuration while for the QB3* NEs the synchronization is relative
to alarms and PM only.
3AL 89062 AA AA 139 / 926
926
N.B. The alignment state goes automatically to misaligned state when the operational state
goes to disabled.

– Local access state:
relates to the ability for the NE to be managed from the local craft terminal CT. There are 3 states.
• Granted: the NE may be managed by the local craft terminal. In this case, the icon is displayed
green on the CT and blue on the OS (e.g. 1353 SH or SH-DXC).
• Denied: the NE can not be managed by the local craft terminal. In this case, the icon is dis-
played blue on the CT and green on the OS (e.g. 1353 SH or SH-DXC).
• Requested: the local manager (CT) has requested update permission from the OS (e.g.
1353 SH or SH-DXC)) and is waiting for a reply (granted or denied) from the remote manager.
This parameter is set from the OS (e.g. 1353 SH or SH-DXC) to Granted or Denied. The CT can
only request local access or return access to the OS.
When no OS is logged in, a CT gets a requested local access after a while. When an OS is logged
in, a CT does not get local access. In this case, it is necessary to call the OS operator to set the local
access state to Granted.
If the Local access state is Granted, some USM operations can be disabled (greyed).
As long as local access is granted for CT, the access for SH is denied.
CTC
– Craft Terminal Connected state:
The Craft Terminal Connected state on the SH-DXC shows if a CT is logged in on the NE. This means,
a Craft Terminal has started supervision on the selected NE in the PNM view.
• CT not connected (green): no CT supervises the NE
• CT connected (blue): CT supervises the NE.
– Operational state:
relates to the ability for the NE and the OS to communicate together. There are 2 states.
• Disabled: the communication link between the OS and the NE is interrupted (red color icon).
• Enabled: the NE is either in the activating, deactivating or supervised supervision state and
communication between the NE and OS is possible (green color icon).
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 140 / 926
926
– NML Assignment state:

indicates whether an NE is used for Network Management purposes. There are 3 states:
• Free: the NE is not assigned to Network management tasks. Element manager level ( 1353 SH
can be selected in the manager list), green color icon.
• Observed: Network management tasks may be applied to the NE.
• Assigned: the NE is assigned to Network management tasks (superior network manager se-
lected in the manager list, e.g. 1354 RM). This causes a reduced access on the 1353 SH, blue
color icon.
The NML assignment state can be activated with the Set Manager List dialog.
To supervise the NE, the SH establishes a permanent association with the NE.
– NTP (network timing protocol) state: specifies the NTP protocol state from the application point
of view. There are 3 states.
• Disabled: the NTP protocol is not active (brown icon color).

• Enable but Servers Unreachable: the NTP protocol is active but the NTP servers are un-
reachable (green icon color)
• Enable and Reachable: the NTP protocol is active and NTP servers (main, spare or both)
are reachable (light blue icon color).
– Simulator state: specifies the simulator state from the application point of view. There are 4 states.
• Disabled: the simulator is not active (green icon color).

• Enable: the simulator is enable. An optional field in this case indicates the managing system
which has required the start of the simulator. No management operations are allowed on the
simulator (blue icon color).
• Activating: the simulator is being started. No management operations are allowed on the simu-
lator.
• Deactivating: the simulator is being stopped. No management operations are allowed on the
simulator.
– AC (abnormal condition) state: specifies the AC status from the application point of view. There
1AA 00014 0004 (9007) A4 – ALICE 04.10
are 2 states.
• Not Present: green color icon

• Present: blue color icon
3AL 89062 AA AA 141 / 926
926
Any disruption in the communication link between the OS and the NE results in an update of the manage-
ment states when the OS has detected the communication failure. The severity alarm and the per domain
alarm are described in the Getting Started section, Equipment Views chapter of the SH Operator’s Hand-
book manual.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 142 / 926
926
3.2 Allow or Inhibit NE Craft access
The NE can be managed by the OS or by the Craft Terminal (directly connected to the NE). To control the
competition of the OS and the CT, a Local Access Control (LAC) is available.
Refer to the “Key” icon of the Equipment NE view.
If the LAC is ”access granted” that means the CT is allowed to manage the NE.
If the LAC is ”access denied” that means the SH manages the NE and the CT is not allowed to modify NE
configuration.
If LAC is “access requested” that means the CT has requested access permission.
The LAC is set from the OS (SH) to ”access granted” or ”access denied”. The CT can only request local
access or return access to the OS (SH).
However during access granted periods the OS (SH) does continue to provide a certain number of ser-
vices. These services includes:
– Reception and processing of alarms,

– Performance processing on TPs,
– Switching back to the OS access state.
The access state of an NE can be modified from the Supervision menu in the Equipment NE View and not
in PNM view.
The user can modify the access state of one particular NE only.
3.2.1 Switching from the OS to the Craft access state
The operation is identical in all other Equipment views (board views or port views).
Select the Supervision pull down menu. Then select the Local... option from the Access State cascad-
ing menu as shown in the following figure.
Supervision
Access State > OS...

Alarm > Local...
Figure 30. Local (CT) mode selectable from Supervision, Access State USM view
From the confirmation dialogue box that opens you can confirm or cancel the ”Craft access” operation
using the Yes or No push buttons. The NE is now in the Craft access state and can be managed from
a Craft Terminal.
N.B. Only one access state can be selected. The grey option, not selectable one, indicates the cur-
rent access state.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 143 / 926
926
3.2.2 Switching from the Craft access state back to the OS access state
Select the Supervision pull down menu. Then select the OS... option from the Access State cascading
menu as shown in Figure 30.

From the confirmation dialogue box that opens you can confirm or cancel the ”OS access” operation.
The NE is now managed by the OS.
N.B. The key symbol icon (Figure 31. ) on the management states of the NE view, indicates whether
the NE is managed by a craft terminal (blue color)or by the OS (green color).
N.B. The SH does no automatic take over after a Craft Terminal access granted. Local Craft Terminal
access is denied on recovery phase after a loss of communication of the NE. When communica-
tion is lost with the NE, the OS automatically recovers the communication and puts the state
that was set before the loss of communication (therefore the Craft Terminal access can be de-
nied or granted).
Access State Icon

Green frame color: OS Access
Blue frame color: Local Access
Figure 31. Access state icon

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 144 / 926
926
3.3 Changing NE Address (only available for W/OMSN)
The user can modify the NE address stored in the NE equipment following this procedure:
select the NE and start the emlusm selecting the PNM “Show Equipment” command. Then select, with
the USM menu commands, the Comm/Routing–>Local Configuration option (see USM Menu Commands
listed in chapter 2). Figure 32. opens.
Figure 32. Example of Local Configuration box dialog
The user can edit the addressing fields to change the NE Address and send it to the NE entering the “OK”
button. Note that the NE address has to be correctly modified by a person expert in network addressing.
Then the connection OS–NE will be loosed and the NE will be in Q3 isolation.
Come back to PNM and Stop the NE Supervision. Select the PNM NE Addresses menu and open the NE
address to restore the new NE address. Then Start again the NE Supervision selecting the Supervision–>
1AA 00014 0004 (9007) A4 – ALICE 04.10
Align down/up option and check that the NE–OS connections is again reestablished. The change address-
ing procedure starts with the Local Configuration, i.e. – at the beginning the user has to configure with
the craft terminal the NE address, stored in the equipment, to establish the right connection. Then it is
possible to change remotely the NE address with the 1353SH .
3AL 89062 AA AA 145 / 926
926
3.4 USM Time Configuration / Status
The NE local time of a selected NE can be visualized and/or re–aligned on the OS time basis.
The OS indication identifies the timing source connected to the NE: SH or CT. A timing source can be

defined as “Server” through to the Network Time Protocol procedure (see chapter 23.5)

The status of the Network Time Protocol can be also visualized on the NTP icon (see Figure 35. ) available
on the USM 6.x.
Select the NE Time... option from the Configuration pull down menu. Figure 34. opens.
Figure 33. Consulting and/or setting the local NE time.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 34. NE Time dialogue box on W/OMSN.
3AL 89062 AA AA 146 / 926
926
The following fields are available:
– NTP Status section (read only) with the following parameters:

• NTP protocol
It can be enabled (in the NTP Server Configuration option at para 23.5 on page 904) or
disabled or empty (greyed).
• NTP Main and NTP Spare

It displays the status of the Main and Spare NTP: reachable or unreachable.
– Time section with the following data:
• NE Time (or Operating System Time on OMSG) and OS Time (or Network Equipment Time
on OMSG)
It displays (read only) the time of the Network Element and of the SH–OS.
• Set NE Time With OS Time

It permits to align the NE time with the time of the SH–OS.
Two different operative conditions can be defined :

– NTP protocol enabled
In this case, NTP Main and NTP Spare will be reachable or unreachable. When both are reachable
the NE uses the Main.
The Set NE Time With OS Time message is not operative and the user cannot set manually the
NE Time.
– NTP protocol disabled

In this case, the NTP Main and NTP Spare are empty (greyed); the Set NE Time With OS Time
message is operative and the user can set manually the NE Time (i.e. change the NE time with the
Time of the Craft Terminal).
If you don’t want to set the NE local time, click on the Close push button to close the dialogue box.
To re–align the NE time on the OS time basis click in the Set NE Time With OS Time radio button and
either click on the Apply ( or click on the “Set” in the W/OMSN ) dialog box push button to validate or on
the Close push button to cancel and close the dialogue box. The OS time comes from the workstation date
configuration which corresponds to the legal GMT time.
N.B. The system re–aligns the time of all supervised NEs periodically and automatically with a
configured periodicity. This periodicity is common for all the NEs.
If you set the NE time, you will force the change, with an immediate effect on the NE. However
it will not have any effect on the periodic and automatic mechanism.
N.B. The functions Set NE Time With OS Time and NTP Protocol enabled are not supported on
the OMSG. Then, in the OMSG, the Operating System and Network Equipment Time will be
only visualized.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 147 / 926
926
Figure 35. NTP protocol icon
The NTP icon colour visualizes on USM 6.x the NTP protocol status:
– Brown: the associated help string will be NTP protocol : disabled.
– Green: the NTP is enabled and both NTP servers (main and spare) are unreachable; in this case
the associated help string will be NTP protocol enabled (NTP servers unreachable).
– Light Blue: the NTP protocol is enabled and at least one NTP server is reachable; depending on
the different servers reachable or unreachable, the associated help string will be:
• NTP protocol: enabled (main and spare NTP servers reachable)
• NTP protocol: enabled (main NTP server reachable)
• NTP protocol: enabled (spare NTP server reachable)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 148 / 926
926
3.4.1 Set Alarm Severities (for W/OMSN)
This option permits to send the ASAP to the previously selected object (rack, subrack, board, module,
TP). It permits also to check the currently operative ASAP used by the object. Only the alarms relative
to the selected object will be set.

Select the objiect and then the Set Alarm Severities... option from the Configuration pull down menu
(see Figure 39. ). Figure 36. opens. The ASAP operative on the TP is highlighted.
Figure 36. Example of Set Alarm Severities window (USM 5.x)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 149 / 926
926
Select an ASAP listed on the window and click on the Detail button . Figure 37. opens.
This window permits to visualize, for every probable cause, the alarm severity assigned to any service
type.

Figure 37. ASAP Edition window
Click on Cancel push button to close the window. To change the ASAP assignment, select a new ASAP
type from Figure 36. and then click on OK to send the selected ASAP to the selected objiect.
Selecting the Set SdhNE Alarms Severities option from the Configuration pull down menu only the
alarms at Equipment level (if the NE rack supports the ASAP) will be managed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 150 / 926
926
3.4.2 Set Alarm Severities (for OMSG)
To assign an alarm severity to a TP or equipment, select the TP or equipment in the related view and then
select the Set Alarm Severities... option from the Configuration pull down menu. The Set ASAP dialog
opens.
Figure 38. Set ASAP Dialog (USM 7.x)
The List of ASAPs on the left side lists all available ASAPs (Alarm Severity Assignment Profiles). If an
object was selected in a view before opening this dialog, its ASAP is highlighted in the list. Using the Detail
button or double-clicking on a list item opens the ASAP Edition dialog which displays detailed information
on this ASAP. (see Figure 37. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 151 / 926
926
Use the “Apply to” section on the right side, the user specifies the objects (TP or equipment) the ASAP
selected in the List of ASAPs (new ASAP) should be applied to:
Choose Scope

– Selected object only
The new ASAP is only applied to the object currently selected in the view.
This is the default if an object is selected in the view.
– Network element
The new ASAP is applied to all objects of the NE matching the criteria specified in “Choose Classes”
and “Choose current ASAP”.
Since this application process takes some time, its progress is shown in the Section “Execution
Monitoring”.
This is the default if no object is selected in the view.
– Selected object and subordinates

The new ASAP is applied to the selected object and those of its subordinates matching the criteria
specified in “Choose Classes” and “Choose current ASAP”.
Since this application process takes some time, its progress is shown in the Section “Execution
Monitoring”.
N.B. Due to system architecture, AU-4 CTPs are no subordinates of MSTTPs. Therefore, if the
AU-4 CTP should be included as subordinate, select the related OSTTP (OpS) or ESTTP
(ElS) as main object.
Choose Class(es)
Enabled if one of the scopes “Network element” or “Selected object and subordinates” is seleted.
– All classes
– Specific class(es)
Select one or more object classes the new ASAP shall be applied to.
Choose current ASAP
The new ASAP is only applied to objects which are currently assigned to this ASAP.
Execution Monitoring
Continuously shows the number of modified objects during the ASAP application process if one of the
scopes “Network element” or “Selected object and subordinates” is chosen.
Press Apply to confirm the ASAP assignment and leave the dialog open. Press Ok to confirm the ASAP
assignment and close the dialog. Press Close to close the dialog and discard any changes.
ASAP can be set for a number of TPs at once (USM 7.x). To define the TPs for which ASAP shall be set,
click on the Tp list button and open the Clipboard dialog. For a description of this dialog see Chapter
Clipboard. As long as the clipboard is open, the buttons Close and Ok are disabled.
N.B. After a modification of the ASAP assignment, it is mandatory to re-synchronize the alarms.
During this re-synchronization, the severity of each alarm is updated.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 152 / 926
926
The modification of ASAPs is generally not possible in Sync View. To change the ASAPs of ports that
serve as timing sources perform as follows:
– Select the port in Sync View.

– Click Show timing source from the Synchronization menu to display the port in port view.
– Change the ASAP in port view (select Configuration and then Set Alarm Severitys).
2MHz timing sources do not support the ASAP feature at all.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 153 / 926
926
3.5 Alarm Configuration
Alarms are always present on the operator’s workspace. The different types of alarms, their number and their
severity level are represented in all USM Equipment views (NE views, Board views and Port views). An icon

representation is used. It is always possible to know the alarm number and their severity for any NE equipment.

The operations that can be undertaken in this section are:
– Alarm Severities Overview

– Alarm Severity Assignment Profile management,
– Alarm Severities Editing
– Set Alarm Severities (for W/OMSN and for OMSG)
– Allow/Inhibit alarm notification,
– Alarm re–synchronization.
3.5.1 Alarm Severities Overview
This option permits to configure and display the ASAPs.
Select the Alarm Severities... option from the Configuration pull down menu.
Figure 39. Configuring Alarm Severity Assignment Profile.
The ASAP dialogue box is displayed.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 154 / 926
926
Figure 40. Example of ASAPs Management dialogue box (USM 5.x).
Two types of ASAP are defined:
– the predefined default ASAPs, pointed by all resources using ASAPs. These ASAPs are defined
as read–only, it is not possible to modify their contents and neither to remove them.
– the free–use ASAP, created by the managing system when needed. These ASAPs can be modified:
it is possible to change the perceivedSeverity of an existing probableCause. A free–use ASAP can
also be removed by the managing system.
The default presented profiles are:
Profile: #1 (USM 3.x, 4.x), No Alarms (others USM) ( i.e. all alarms disabled)
This ASAP inhibits the emission of any potential alarm.
Profile: #2 (USM 3.x, 4.x), Primary Alarms (others USM ) (AIS, SSF, and FERF disabled)
This ASAP enables the emission of all:

1AA 00014 0004 (9007) A4 – ALICE 04.10
– primary communication Alarms (i.e. the AIS, SSF & FERF alarms are disabled), and
– equipment Alarms.
3AL 89062 AA AA 155 / 926
926
Profile: #3 (USM 3.x, 4.x), No Remote Alarms (others USM ) shows the alarm criterion configuration
defined for “path alarm” (only AIS and FERF disabled)
This ASAP enables the emission of all

– primary communications Alarms plus SSF (i.e. the AIS & FERF alarms are disabled), and

– equipment Alarms.
Profile: #4 (USM 3.x, 4.x), All Alarms (others USM) (all alarms enabled)
This ASAP enables the emission of all alarms.
For OMSG has been added a fith predefined default ASAP:
Profile: #10 (USM 4.x), No Server Alarms (USM 7.x, 8.x...) ( only SSF disabled )
This ASAP enables the emission of all alarms except SSF, Redundant A/B Clock Fail and Redundant
A/B Matrix Failure.
For ASAP “No Alarms”, “Primary Alarms”, “No Remote Alarms” and “Primary Alarms” it is only possible
to choose Detail, or Clone buttons .
When you click on the Detail button the ASAP edition dialogue box is displayed, and values in this window
are not modifiable.
When you click on the Clone button you can create a new free–use ASAP identified with the default
number >#10000 (USM 3.x, 4.x) or with the default number and a string of characters or any alphanumeric
mix version (i.e., ID >#10000 140Mbit/s PDH).
The free–use ASAPs are always created cloning an already existing ASAP: hence, also in free–use
ASAPs all foreseen (for a certain NE) probableCauses will be always present. Removing or adding
probableCauses is not allowed.
The maximum number of free–use ASAPs supported in the SH–OS is product dependent: the free–use
ASAPs are 2 or 6 for W/OMSN, 2 for WDM (1686WM,..) and 128 for OMSG.
When the maximum number of ASAPs has been reached, the NE will refuse the new creation and the
Clone push button will be greyed. In this case a new ASAP can be only created after deleting a free–use
ASAP at least.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 156 / 926
926
3.5.2 Alarm Severity Assignment Profile Management (ASAP)
A malfunction of the managed entities generates an alarm. This section deals with the configuration of
ASAPs. An ASAP is a list of alarm probable causes to which the operator has assigned predefined or
settable Severities Profiles.

The following have to be considered:
– Alarm Probable Cause,

– Alarm Severity.
– Alarm Type (communication alarm, equipment alarm).
A limited pool of default ASAPs has been created for every NE family type (W/OMSN, OMSG,...).
This approach allows a simplification in the severity profiles management by limiting the explicit creation
of new ASAPs only to specific situations.
The alarm severity assignment profile dialogue box of Figure 41. displays a list of probable causes and
a list of alarm severity.
Figure 41. ASAP Edition dialogue box.
The Probable Cause Family check buttons allows to filter the probable causes that will appear in the
Probable Cause Name list. NOTE: choose one or more of these filters to have the list.
1AA 00014 0004 (9007) A4 – ALICE 04.10
To find a particular probable cause, enter its name in the Search entry box at the bottom. The alarm is
marked within the list, but not automatically displayed. Scroll to the mark with the mouse cursor.
3AL 89062 AA AA 157 / 926
926
ASAPs are already defined in the system with default values for the assigned severities.
You can modify the severity associated with each probable cause. Hence, select the Probable Cause
Families: Communication, Equipment,...and then the corresponding Probable Cause Name whose
severity level you want to modify. Click on the option button: Service Affecting, and then Non Service

Affecting and then Service Independent. For each one you can choose the severity value among

”Critical”, ”Major”, ”Minor”, ”Warning” or ”Non–alarm”. A ”Non–alarm” probable cause corresponds to no
alarm emitted for this probable cause. In general the NSA severity must be less than the SA severity (see
Table 2. ). On OMSN the SI field is not available: the SI severity can be provided selecting, in SA and NSA
, the same severity value (see case 2 ( SI ) of Table 2. ).
When you have configured the ASAP, press the OK button to confirm the settings and close the dialogue
box or the Cancel push button to cancel the new settings and close the dialogue box.
N.B. The number of severities is fixed by the Norms. The number of probable causes is fixed by the
customer IM. Their characteristics cannot be modified. The ASAP function only enables the
modification of the severities assigned to the probable causes, it does not allow to add, remove
or modify these severities and causes.
N.B. To take into account a profile modification, it is mandatory to perform a re–synchronization of

the alarms. During this re–synchronization, the severity of each alarm is updated. Otherwise,
the severities are updated only when the modified or new alarms are emitted by the NE.
N.B. This note concerns only the OMSG family (see Table 1. ).
Note that the OMSG handles the service dependency types “service affecting” and “non service
affecting” only in respect of replaceable unit missing (RUM) alarms (plug out of a board). All
other alarms are handled with severity type “service independent”. This means that:
– RUM is only alarmed if its severity is set as a service
affecting alarm to critical or major (Case 1
and
– RUM is not alarmed if its severity is set as a non service
affecting alarm to minor or warning.
All other alarms should be configured according to Case 4.
Table 1. Assignment of Service Dependency and Severity on OMSG and WDM
Case Service Affecting Non Service Affecting Service Independent

minor or warning or non-
1 critical or major not used
alarmed
2 critical or major not used not used
3 not used not used
alarmed
critical or major or minor
4 not used not used
or warning or non-alarmed
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 158 / 926
926
Table 2. Default Assignment of Service Dependency and Severity on OMSN
Case Service Affecting (SA) Non Service Affecting (NSA) Service Independent (SI)

1 major not used

alarmed
2 ( SI ) major, minor, warning major, minor, warning not used
For any specific NE (OMSN, OMSG, OMSW, WDM) see the description regarding the proper ASAP
severities assignment.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 159 / 926
926
3.5.3 Alarm severity editing
For free–use ASAPs it is possible to choose Detail, Modify, Clone or Delete buttons.

Clicking on Detail, Modify, or Clone button is displayed the ASAP edition dialogue box.

When selecting Detail the assigned severities are only shown and not modified.
When you click on the Clone button you can create a new free–use ASAP identifier, per default, with
number >#10000.
When selecting Modify you can configure the ASAP. For OMSG you can not Modify an ASAP but you
can only create a new one, with the Clone button (up to 128 ASAPs).
Here has been reported step by step a Procedure to modify/assign the TP ASAP
a) Select the TP (or the board/port/etc...) whose ASAP is to be changed
b) from the menu click on “Configuration” –> “Alarms Severities...”
c) (see Figure 40. on page 155 ) select one of the “user” profiles (#10001 ) and click on “Modify”
d) (see Figure 41. on page 157) click on the “Probable Cause Families” associated to the alarm
e) select the relevant alarm in the list of “Probable Cause Name”
f) in the “Service affecting/non–affecting” fields select the needed severity (critical/major/minor...)
g) click on “OK”
h) (see Figure 40. ) click on “Close”
i) select the relevant TP and then “Configuration” –> “Set Alarms Severities...” (see para.3.4.1)
j) in the box that appears select the just modified ASAP (eventually check it by means of “Detail”)
k) click on “OK”
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 160 / 926
926
3.5.4 Allow/Inhibit Alarm Notifications
The system provides the possibility to allow/inhibit the spontaneous incoming alarm notifications. Only the
current selected NE is concerned by the change.
Inhibiting the alarms notification means that they are not forwarded to the OS but alarms are still detected
by the NE.
a) To inhibit alarm notification,

Select the Supervision pull down menu. You can then select the Inhibit Notifs option from the Alarms
pull down menu as shown in the following figure.
Supervision
Simulator
Access State >
Alarms > Resynchronize
Upload Remote Inventory Allow Notifs
Set Manager List... Inhibit Notifs
Figure 42. Inhibit alarm notification
From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok
or Cancel push buttons respectively.
To inform the operator that alarms have been inhibited, the labels of the alarm panel are greyed out.
Figure 43. Alarm Panel with Disabled Alarm Notification
N.B. Inhibiting the alarms notification means that they are not forwarded to the OS but alarms
are still detected by the NE.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 161 / 926
926
b) To allow alarm notification
Select the Supervision pull down menu. You can then select the Allow Notifs option from the Alarms
pull down menu (see Figure 42. ).
From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok


Figure 44. Alarm Panel with Enabled Alarm Notification
3.5.5 Alarm re–synchronization
Even if the management system always guaranteed alarm consistency the system provides the possibility
of recovering alarms present on the NE and to update the current alarm list of the NE. After this operation
OS and NE current alarms are consistent.
To re–synchronize the alarms, select the Supervision pull down menu. Then select the Resynchronize
option from the Alarms pull down menu (see Figure 42. ).
From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok or
Cancel push buttons respectively.
N.B. This procedure has to be applied only if there is any perturbation (Q3 isolation, starting a new
NE alarm supervision,...).
3.5.6 Refresh / Close / Exit View
Use the Refresh menu item to update the view (not used on OMSG).
The “ Refresh” command re–synchronizes the SH with the selected NE avoiding any possible
misalignment. This misalignment is due to a loss of notifications coming from NE to SH–OS. All the primary
“View” windows and some Secondary Views ( on MS–SPRing ) can be updated, in real time, with this
command.
Use the Close menu item to close the window.
Use the Exit menu item on the View s menu to close all windows of the NE Equipment view (not available
on W/OMSN).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 162 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Exit
Views
Room
Close
Refresh
Previous
MS–Spring
Open Object
Transmission
Synchronization
Open in Window
Equipment Overview
926
3AL 89062 AA AA
163 / 926
3.6 Navigation Between Views
There are different ways to navigate from one view to another:

– In the hierarchical levels of the equipment structure, double-click on the related element in the view

to open this element in the lower level view. For example, double-clicking on a board in the subrack
level of the Equipment view opens this board in the Board view.
N.B. The Board view is locked in case the board is out of service or its state is “protected”.
– Mark the element in the current view and select the navigation command from the related view menu.
– Mark the element in the current view and select Open Object or Open in Window from the Views
menu.
N.B. The Open Object menu item cannot be used in the Port view.
The general navigation options are described in the following section. For the concrete navigation options,
refer to the related view description.
3.6.1 Navigation to Management Domain Views
The views that offer the user thematical information according to management domains on the OMSG are
Room view, MS-Spring, Equipment Overview, Synchronization view and Transmission view.
These views are always directly accessible via the Views menu, regardless of which one is currently ac-
tive:
Views
Previous
Room
MS–Spring
Equipment Overview
Transmission
Synchronization
Open Object
Open in Window
Refresh
Close
Exit
3.6.2 Navigation Between Different Hierarchical Levels
The views that reflect the equipment structure on different levels are Room view, Equipment view with
rack and subrack level, Board view and Port view. These views follow a hierarchical order and, apart from
1AA 00014 0004 (9007) A4 – ALICE 04.10
the Room view, cannot be directly accessed via the Views menu.
3AL 89062 AA AA 164 / 926
926
Using Room view as the access point, the user can either navigate through the various equipment levels
or directly access the relevant level via Equipment Overview (see Chapter “Equipment Overview – Navi-
gation”).
Navigation from higher to lower equipment levels is possible by double-clicking on the related element.
Navigation from lower to higher level has to be carried out using the navigation commands in the view
menu, e.g.
– use Show Supporting Board in the Port view to navigate back to the Board view
– use Show Supporting Equipment in the Board view to navigate back to the Equipment view (sub-
rack view)
– use Show Supporting Equipment in the Equipment view to navigate back to the next higher level
in the Equipment view (rack view, room view).
3.6.3 Navigation To Previous View
Use this menu item to go back to the view that was previously displayed in this window.
Views
Previous
Room
MS–Spring
Equipment Overview
Transmission
Synchronization
Open Object
Open in Window
Refresh
Close
Exit
Shortcut: Hit the “ESC”-key.
3.6.4 Navigation Using “Open” Commands
N.B. These commands are not accessible from the Port view.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 165 / 926
926
Views
Previous

Room

MS–Spring
Equipment Overview
Transmission
Synchronization
Open Object
Open in Window
Refresh
Close
Exit
Navigating amongst different views may be performed either inside the same window or by opening a new
window.
After selecting the desired element (e.g. board, port) from the current equipment view, select the Open Ob-
ject option from the View pulldown menu. The selected view is then displayed in the current window.
Opening a new window is used to navigate to another view without clearing the current view. After selecting
the desired element (board, port) from the current equipment view, select the Open In Window option from
the View pulldown menu. The selected view is then displayed in a new window.
N.B. Only three windows can be opened simultaneously.
3.6.5 Navigation using the Popup Menu
The following views also provide navigational commands within the view area:
– Equipment Overview
– Room view
– Transmission view
By clicking and holding the right mouse button in the view area, a popup menu appears offering navigation-
al commands. The popup menu contents vary according to the type of view.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 166 / 926
926
3.7 User Preferences (only available for OMSG)
The User Preference dialog is used to save and load user preferred filter settings, graphical adjustments
or TP/equipment lists for other dialogs.
The feature consists of two parts:
– Saving/loading user preferred filter settings and graphical adjustments in the Cross-Connection
Management dialog.
The user can save filter settings and graphical adjustments, such as column width, as a preference
set in a file. The named preference set can be reloaded later in the respective dialog or view. The
user can also delete named preference sets.
– Saving/loading of TP/equipment lists in the Clipboard dialog.

The user can save TP/equipment lists as a preference set in a file. The named preference set can
be reloaded later in the respective dialog or view. The user can also delete named preference sets.
The preference set list box contains all named preference sets, including the standard sets:
– default, which includes factory settings which cannot be changed by the user
– previous, which includes the filter settings automatically stored before the last close action (only
available in the Cross-Connection Management dialog).
Use the Preference Set text field to enter a name for a newly created set. The name may consist of
alphanumerical characters and underscores.
Action Buttons
– Load:
restores the preference set selected in the list box in the current dialog or view. If the user has entered
a set that does not exist, an error box appears.
– Save:
saves the current filter settings or TP/equipment list in the context with the name entered in the
Preference Set text field.
– Delete:
is only active after selection of a preference set in the preference set list box. Pressing the button
deletes the selected set.
– Close:
closes the dialog without automatically saving any changes
– Help
opens the online help on this topic.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 167 / 926
926
3.7.1 Save User Preferences
Save the preferred filter settings or a dedicated list of TPs/equipment of the current dialog in a preference
set:

1) Modify the filter settings in the Cross-Connection Management dialog according to your
preferences, or create a list of TPs/equipment in the Clipboard dialog.
2) Open the User Preferences dialog.
3) Type in a name for the preference set in the Preference Set text field.
4) Click on Save.
When trying to save a preference set which already exists, a confirmation request appears in which to
verify the save action.
The standard sets previous and default cannot be modified.
Figure 45. Save Preference Set
3.7.2 Load User Preferences
Load the preferred settings or a dedicated list of TPs or equipment from a preference set to the current
dialog:

2) Select the required preference set from the preference set list.
3) Click on Load.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Double-clicking on a set in the preference set list box executes the load action and closes the dialog.
3AL 89062 AA AA 168 / 926
926
On closing the Cross-Connection Management dialog, the current filter setting are automatically saved
and can be loaded with the previous preference set.
Figure 46. Load Preference Set
3.7.3 Delete User Preferences
Delete a preference set from the list:

2) Select the preference set from the preference set list.
3) Click on Delete to delete this preference set.
Each deletion has to be confirmed.

The standard sets previous (only available in the Cross-Connection Management dialog) and default
cannot be deleted, therefore the Delete button is disabled if one of these sets is selected.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 169 / 926
926
3.8 Clipboard Dialog (only available for OMSG)
Use the Clipboard dialog to perform the same action, e.g. PM configuration, on a number of objects (TPs
or equipment) in one step. The actions possible are listed in Table 3. together with the related access dia-

logs.


!

""
""

# $ %& $ $
# $ %& $ $
Table 3. Possible Actions
The list box on the left side of the dialog displays all the objects (TPs or equipment) the user has selected
(see Figure 47. ) for the current action.
The buttons on the right side of the dialog are used to create a list of objects:
– Add Tp
Opens the TP Search dialog in which the user selects the TPs to be configured. The selected TPs
are added to the clipboard list.
– Add EQP
Opens the Equipment Filter dialog in which the user selects the equipment to be configured. The
selected equipment is added to the clipboard list.
– Delete
Deletes the selected objects from the clipboard list.
– Delete All
Deletes all objects from the clipboard list.
– Load/Save
1AA 00014 0004 (9007) A4 – ALICE 04.10
Opens the User Preference dialog where a preference set can be loaded or saved. If a preference
set has been loaded, the name of this set is displayed on the lower left side of the dialog.
3AL 89062 AA AA 170 / 926
926
– Print
The Print dialog opens and the user selects the print destination and print format.
– Start
Starts the action process on the listed objects. The semantics of the action is defined in the calling
dialog.
After starting, an information window opens to cancel the action during its progress. Click on Ok to
cancel the process.
– Continue
Continues an action performed on the clipboard which was previously cancelled.
– Close
Closes the Clipboard dialog together with the related TP Search, Equipment Filter or User Prefer-
ence dialog.
Processing States
Having started the configuration or structure process, the current processing status of each item is dis-
played in the clipboard:
– access control failed

the user has no permission to configure this TP
– failed
the action failed
– N/A
this item has not been processed yet
– no POM/SUT (only in context with POM/SUT)

POM/SUT does not exist for this TP, therefore, PM configuration is not possible
– pending
the configuration is in process
– successful
the configuration was successful
– wrong tp (only in context with POM/SUT)

this TP type cannot be configured for POM/SUT
– selected monitor not existing

The monitor selected in the dialog does not exist for the TP in the clipboard.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 171 / 926
926
Figure 47. Clipboard Dialog Opened from the “POM/SUT Creation/Deletion” Dialog
3.8.1 Using the Dialog
The following description assumes that the settings which should be applied to a number of objects have
been made in the related dialog and the Clipboard dialog has been opened via the TP list... button.
1) Create a list of all the objects to which the desired action should be applied:
Click on Add TP to open the TP Search dialog and add a number of TPs to the clipboard list.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Or, click on Add EQP to open the Equipment Filter dialog and add a number of equipment to
the list. Or, click on Load/Save and load a predefined set of TPs to the list.
N.B. The settings of the related dialog are only applied to the TPs listed in the Clipboard dialog.
3AL 89062 AA AA 172 / 926
926
2) Click on Start to start the process. The objects in the list are processed from top to bottom. The
current processing status of each item is displayed in the clipboard (see Figure 48. ).
Use the Ok button in the information dialog box to stop the current process. Note that objects
which have already been processed remain in this state.
3.8.2 Using the Structure Payload
See Chapter Structure TPs.
Figure 48. POM/SUT Creation in Progress

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 173 / 926
926
3.9 Drag and Drop (DnD) (only available for OMSG)
3.9.1 Description

By using DnD, objects such as TPs and ports can be easily copied between different views and dialogs
using the mouse.
1) Select the object on a drag site by pressing the middle mouse button. The mouse pointer
changes appearance to indicate the beginning of the operation.
2) Move the mouse pointer to the drop site keeping the middle mouse button pressed.
3) Release the middle mouse button on the designated drop site. Releasing anywhere else can-
cels the operation.
Table 4. and Table 5. provide an overview of the drag and drop sites available.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 174 / 926
926

#' (
"

) "

* (

+

%
# " &
%& , " &

# "

"

)' "

)' "

$ " )-
. $

#' ( "

" )-
$ " )-
Table 4. Drag Sites

"
"

" "

) " )-
* / +

"

)01
* /

(
"

01
%
# " &
%& $ $ " &
"

1AA 00014 0004 (9007) A4 – ALICE 04.10

# "

"

3AL 89062 AA AA 175 / 926
926

"


"



)' "

$ " )-
""
"

"

2 "

$ " )-
Table 5. Drop Sites
3.9.2 Examples of Operational Scenarios
Add TPs to Transmission View
1) Open the TP Search dialog within the Transmission view (menu option Add TP).
2) Navigate to the relevant TP in the dialog and drag it to the Transmission view. The TP Search
dialog remains on screen.
3) After completing the work on this TP, the next one can be dragged to Transmission view without
having to reopen the TP Search dialog.
Show Port in Transmission View
1) Open the Equipment Overview and select a port.
2) Open a second view using the Transmission view.
3) Mark the selected port in the Equipment Overview and drop it in the Transmission view.
Creating Cross-Connections
1) Display the TP to be cross connected (Input TP) in the Transmission view.
2) Open the Main Cross Connection dialog by double-clicking the TP from Step in the Transmis-
sion view.
3) Select Output and Protected Input TP (if necessary) in the Transmission view or TP Search dia-
log and drop them in the respective entry boxes in the Main Cross-Connection dialog.
1AA 00014 0004 (9007) A4 – ALICE 04.10
4) For broadcast connections:

Drop additional legs in the output list box.
3AL 89062 AA AA 176 / 926
926
Proceed as described in Chapter 15.3.
Search for Cross-Connections with specified TP

1) Display a TP in the Transmission view or in the TP Search dialog.
2) Open the Cross-Connection Management dialog.
3) Drag the TP from Step 1 and drop it in the “TP Id Prefix” edit field or in the list area.
4) Click on the Search button.
5) All cross-connections related to this TP are displayed.
Perform a Port Switch Over
1) Display the substitute AU-4 TP in the Transmission view or TP Search dialog.
2) Open the Port Switch Over dialog from the Transmission menu.
3) Drag the TP from Step 1 and drop it in the “New Au4” edit field.
4) Confirm the configuration.
For further details relating to the configuration, refer to Chapter Port Switch Over.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 177 / 926
926
3.10 Print Dialog
The Print option is used to select the print destination and the output format.

Print Destination

– Printer
Print to the selected network printer.
N.B. If no printer is installed, there is no error message displayed to indicate this.

If the selected printer is displayed with none, the user has to choose another printer, to
execute the print job.
Figure 49. Select Printer
– File
Print to a file in any directory.
Enter the name of the output directory and file in the input field. Or, define a directory and file name
in the File Chooser dialog which can be opened by clicking on Select file.
The default name is print.ps for postscript files and print.txt for ASCII files. If no other
directory is specified, the file is printed to the default directory
/alcatel/1353sh/maintenance/core/emlusm.
N.B. Remember to select a file name complying with the DOS format (8+3 characters) if the file
must be copied on a floppy disk later.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 178 / 926
926
Figure 50. Print to File
– Export (only available for OMSG)

Print to the export file in directory /alcatel/export. Use this option if the printed data has to
be exported to floppy disk or tape.
Enter the name of the output file in the input field. The default name is export.ps for postscript
files and export.txt for ASCII files.
N.B. Remember to select a file name complying with the DOS format (8+3 characters) if the file
should be later on copied on floppy disk.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 179 / 926
926
Figure 51. Print to Export File
Output Format
When printing to file, the user has to specify whether the file format should be Postscript or ASCII.
The output file is generated after clicking on OK. Use Cancel to stop the process.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 180 / 926
926
3.11 Show Matrix Type (only available for OMSG)
To display the matrix type of the selected NE, select the option “Installation Details” from the “Diagnosis
– View” menu option.
An information window pops up providing the matrix type used in the cross connect. Confirm with OK to
close window.
Figure 52. Installation Details – Show Matrix Type
Examples:

334 56 7#89 7#56 53:56
334*
4 7#89 7#56 53:56
993
334*
3 7#89 7#56 53:56
559
843 56 7#89 7#56 59:56
843*
4 7#89 7#56 59:56
5;9
843*
3 7#89 7#56 59:56
;6
34< 56 7#3< 7#56 59:56
;6< 89 7#3< %7#89 93:89
;6<*
56 7#3< %7#89 93:89
843

63< 3< 7#3< 7#3< 56:3<

594< 3< 7#3< 7#3< 89:3<
LMC = Large Matrix Configuration
HPC = High Order Path Connection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 181 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
182 / 926
4 SECURITY MANAGEMENT
4.1 Security Check

This feature provides the possibility to assign single ports of the Q3–NEs to different users. This, e.g.
enables the management of one NE by two different companies.
It is a general decision whether the Q3–NE should be managed as one entity (NE level) or on port level.
The check level has to be configured during the configuration phase of the SH application by the
administrator.
The security concept works in the following way:

Objects like TPs or cross-connections can be assigned to a single user or a group of users. This is done
by means of OADs (Object Access Domains). In an OAD the users are grouped, e.g. according to the field
of work. To restrict access to an object, an OAD is assigned to it. As a result only those users can access
this object, that include the OAD in their user profile (i.e. that belong to the group).
OADs have to be created and assigned to each user profile by the administrator (see Chapter 6.2 of the
Administration manual).
The following can be configured using the Access Control Domain (ACD):
– The access control check level (only for administrator)
• Port level
• NE level
• No check
– The ACD at NE level (“NE domain”) or port level (“resource domain”).
– The manager list at NE level (“manager list”) or port level (“NML assignment”).
This feature is not checked in the CT or SH-DXC. Therefore, it has no influence on the CT or SH-DXC
access control. But it is used at higher management levels (e.g. by 1353 SH).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 183 / 926
926
4.2 Check Level Configuration (only available for OMSG)
N.B. This dialog can only be accessed by the administrator “axadmin”.

Configuration
Alarms Severities...
NE Time...
Performance >
Set ACD Level...
Cross Connection Manage-
ment...
Loopback Management...
EPS Status...
It is possible to specify the scope of the security check in the ACD Level Configuration dialog (see
Figure 53. ):
– No Check: the ACD is not managed
– NE level: access control attributes are checked for the global OMSG (default value)
– Port level: access control attributes are checked for each port on the OMSG
N.B. Changing the ACD level causes a restart of the user interface (EMLUSM) process. All views
belonging to that process will be closed. This concerns views of the same NE as well as views
of different NEs.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 184 / 926
926
Figure 53. ACD Level Configuration
4.2.1 ACD Check at NE Level
If the security check is set to NE level, only the Set Manager List dialog is relevant for access control.
4.2.2 ACD Check at Port Level
If the access control is set to port level, only the Set Domain dialog is relevant for access control.
4.2.3 No Check on Access Control
If the access control is set to No Check, no more access limitations apply.
This should only be used by the administrator as a last fallback solution when access restrictions prevent
a normal state being established on the OMSG.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 185 / 926
926
4.3 Access Control Management on Port Level (only available for OMSG)
If the level check is set to port level, it is possible to specify the resource domain for each port (see
Figure 54. ).

Using this feature, it is possible to assign ports exclusively to a specific group of users, so that different
users can work on the same NE but only a specific group can use ports with a specified resource domain.
If the resource domain assigned to a port is not present in the user profile, the user cannot use this port.
Board
Set Domain...
Port/Transmission
Als Management...
...
Show Optical Configuration...
Physical Media >
Tx SSM Quality Configuration...
... Regenerator Section Management...
Line Length Configuration...
MS Configuration... *
Set Domain...
* on Port menu
The access control attributes set in the Set Domain dialog are only checked if the check level is set to “Port
level” in the ACD Level Configuration dialog. The access control can be set on
– ESTTP (ElS)
– OSTTP (OpS)
– SPITTP (P)
– VC-4 TTP (ModVc4)
– Cross-connections.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 186 / 926
926
Figure 54. Set the Port ACD
NML Assignment
N.B. This feature is not checked in the CT or SH-DXC.

Therefore, it has no influence on the CT or SH-DXC access control. However, it is used for ac-
cess control on higher management levels. So be careful when changing the NML assignment
for other managers (e.g. 1353 SH).
Using the NML Assignment, each port can be assigned to a specific manager. If assigned to a special man-
ager, the port cannot be managed from any other manager.
If the related port has to be managed on OMSG level only, the NML Assignment must be EML Manager
or not assigned. If not assigned, the port can be managed from any manager in the list.
Resource Domain
This feature defines the Object Access Domain (OAD) that is assigned to this port. This means only the
users assigned to this OAD can access the port. The OAD has to be defined by the administrator.
Assign the port to the domains unknown or empty if no special restrictions on access or functions are
necessary.
Press OK to confirm the settings and close the dialog. Press Apply to confirm the settings and leave the
dialog open. Press Tp list... to open the clipboard dialog. Press Cancel to discard any changes and close
the dialog.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 187 / 926
926
4.4 Manager List
The Manager List contains the list of managers ( i.e. RM, SY, NPOS ) that work on the NE. The managers
marked are currently in control of the NE

Only the EMLUSM administrator can add or remove a manager from the list. This can be done by
selecting or deselecting the manager in the list ( see Figure 55. and Figure 56. ). Removing a manager
from the list should only be done in case of emergency (e.g. the manager looses the NE connection).
Each manager provides a set of available functions, so the NE, when it is assigned to a manager, can
perform only the granted operations: the user may not be able to perform a specific operation on the NE
if another manager is present in the Manager List (e.g. cannot create a cross-connection if the RM
manager is present in the Manager List)..
The attributes set in the Set Manager List dialog are only checked and hence relevant for ACD if the
security check is set to NE level.
N.B. This Set Manager List is not checked in the CT or SH-DXC.

Therefore, it has no influence on the CT or SH-DXC access control. However, it is used on
higher management levels. So be careful when adding or removing other managers from the
Manager List (e.g. 1353 SH).
The standard behaviour is to perform all the operations about Manager List automatically.
Figure 55. Supervision menu for setting the Manager List

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 188 / 926
926
Figure 56. Set the NE Manager List
It is also possible to assign a port to a specific manager present in the Manager List. To perform this
operation it is necessary to select the board and use the “Set Domain” menu, then the operator can
manage the port Manager List and Resource Domain as described in the previous para.4.3.
The SH operator should use this functionality in order to assign the port to itself and, only in case of
emergency, to remove the port from a Manager.
If the user profile contains the ignoreNMLAssignment FAD, he/she can work also on ports assigned to
other managers.
When the RM or SY manager takes the NE control , they are added to the manager list automatically. .
NE Domain
This option button indicates the access control of the NE.
Access control “unknown” (default) indicates that no domain is defined and there is no access restriction,
i.e. each user can access the NE.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 189 / 926
926
4.5 NE Port/User Assignment (only available for OMSG)
The purpose of the following application is to clarify the security management. Define two different
Network Access Domain (NAD )associated to two different users . One user is the axadmin with the

“administrator” profile, the second one is job_op with the “operator” profile (see the procedure described

in the Administration Guide Manual ). The job_op user can only work with the available local or distributed
maps. Then the following example shares some OMSG ports to job_op user
Create two different NADs: NAD1 associated to job_op and NAD2 associated to axadmin. To this concern:
– login as axadmin
– on the SMF interface select–> Operators Administration–> SEC Administration
The main Aca window opens. Select Configuration–>OAD–> Object and press the Add button.
Figure 57. NAD Object Creation
New object creation

1AA 00014 0004 (9007) A4 – ALICE 04.10
– Edit the new object “Name” (NAD1) and the “System Id” (NAD1_OAD) and select the “Access Control
Domain” family and the “job_op” creator from the parameter list (see Figure 57. ) . Execute the same
operation to create NAD2 associated to axadmin user.
3AL 89062 AA AA 190 / 926
926
New elementary OAD creation
– Close and come back to OAD Configuration, select Elementary and press the Add button. Name
the new elementary object access domain as OADNAD1 including the NAD1 object belonging to
control access domain family (see Figure 58. ). Execute the same operation to create the elementary
OADNAD2 object including NAD2.
Figure 58. New NAD1 elementary object definition
The OADND1–FAD combination enables the elementary object OADNAD1 to work with the Functional
Access Domain ( FAD ) system.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 191 / 926
926
OAD–FAD Combination
– select from the Aca main window Configuration–>OAD–FAD..and then press the Add button (see
Figure 59. ).Give a combination name ( in our example OADNAD1–operator) and select the right

combination ( in our example the Elementary object OADNAD1 with the System Fad operator)

– Execute the same operation to create the OADNAD2 combination with admin group.
Figure 59. OADNAD1 – operator group combination

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 192 / 926
926
OAD–FAD Combination Activation
– come back to the main Aca window and include the created combination on the right user. Then the
targhet object OADNAD1–operator will be included in the job_op ( see Figure 60. ). Apply the same
operation for the axadmin user.

Figure 60. Activation of OAD–FAD combination
To assign NAD1 to axadmin user come back to the main Aca window and include the OADND1 in the
axadmin user.
Activate the security configuration killing the lss process on SH workstation (Figure 61. ):
• ps –elf | grep lss usr/1353sh/sec/bin/ lss <pid>
• kill –9 <pid>
• lss automatically restarts.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 61. Killing lss process
3AL 89062 AA AA 193 / 926
926
If necessary, close and open again the USM application to update it.
Now login as “axadmin” and assign some OMSG ports to job_op and others to axadmin user.

Select the OMSG NE in the PNM map and then NE Directory –>NE Info –> “Unknown” in the Access

Control Domain field to permit to manage it with the job_op too. Open the “Set Manager List” dialog to
verify the NE Domain (unknown) and the OS managers (EML Manager,..).
Select the “Port Level” in Configuration–> Set ACD Level to open the ACD level configuration box dialog
(see para. 4.2 )
Open a 2MBit board view and assign “ EML – NAD1 “ in Board–>Set Domain command to the port #1,2,3
and “ EML – NAD2 “to the port#6,7,8 (see para. 4.3)
Now it is possible to verify that the job_op user can not manage the ND2 ports but only the ND1 ports:
selecting a cross–connection in Configuration–> Cross–Connection Management and visualize the ACD
assignment with the “Set ACD” button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 194 / 926
926
5 ROOM VIEW (ONLY AVAILABLE FOR OMSG)
5.1 Overview
The Room view depicts the physical layout of the equipment rack objects. The racks of the OMSG may
be built up in one or more rooms. Each room contains different rows of racks in which the rack objects are
positioned sequentially. The minimum size of the Room view equals 3x3 racks.
Rooms and rows are displayed in a single graphical presentation. The Room view provides information
about the rack types of the OMSG:
– double subracks
– common I/O shelfs
– non-OMSG racks
– air gaps
However, when the room view is displayed, all racks of the OMSG are displayed in one view. Layouts which
are bigger than the view area are handled by automatic zooming. The layout setup for the logical rack posi-
tion is dependent on the actual installation. The relevant data is provided by a system internal database.
The layout, therefore, cannot be changed, but maintenance personnel may adjust the label of the racks.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 195 / 926
926
5.2 View Layout
Figure 62. illustrates the Room View with equipment distribution in one room. Each room can have one
or more rows of racks.

=(= ) =)' >*?=' document, use and communication of its contents
Figure 62. Room View with One Room and Different Rows
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 196 / 926
926
5.3 Navigation
5.3.1 Navigation using the Room Menu

The following navigation commands are provided in the Room menu:
Room
Zoom in
Zoom out
Fit to Contents

...
...
Zoom in
This command enlarges the viewed objects to display more detailed information of the rooms and racks.
Use the scrollbar to display other parts of the room.
Zoom out
This command reduces the viewed objects to display a more overall view of the rooms and racks.
Fit to Contents
This command displays the complete room layout in the current view.
This command opens the Equipment view of the selected rack. A double click on the selected rack can
also be used to open the Equipment view.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 197 / 926
926
5.3.2 Navigation using the Popup Menu
The following commands are provided in the popup menu using the right mouse button in the Room view:

Room

Zoom in
Zoom out
Fit to Contents
Navigate to Selected Rack *

* only when rack is selected
Show PCT Rack ID / Show ** toggle function
Rack Number **
Refer to the previous section for explanation of the navigation commands.
Refer to the next section for explanation of the toggle commands.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 198 / 926
926
5.4 Rack Label
Room
...
...
Modify User Data
Show PCT Rack ID

Show Rack Number
Edit
Modify User Data
The rack labels within the Room view can be modified by the user.
Use the menu item Modify User Data to open the following dialog:
Figure 63. Modify User Data
N.B. Although it is possible to enter more characters, only 12 characters will be displayed in the corre-
sponding icon as User Data in the room view. Depending on the entered characters, even in
the status bar on bottom of the screen not all characters will be displayed.
Add the rack label in the User Data field.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Click Apply to save and implement the label. Therefore, a number of racks can be labelled without having
to close and reopen the dialog.
3AL 89062 AA AA 199 / 926
926
Click Close to close the dialog.
Help opens the online help related to this dialog.

Show PCT Rack ID

This command displays a rack’s PCT (Product Configuration Tool) ID. This ID is a factory adjustment.
Show Rack Number
This command displays a rack’s logical number within the system.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 200 / 926
926
6 EQUIPMENT OVERVIEW (ONLY AVAILABLE FOR OMSG)
6.1 Overview
The Equipment Overview displays equipment of an NE in a hierarchical tree structure.
The Equipment Overview enables fast navigation through all levels of the equipment hierarchy from rack
level down to port level. Navigation is done from higher to lower levels and across the tree structure. In
contrast to the other views, it is possible to display more than one subtree.
N.B. The DCC Server Board (DSB) is not integrated in the general supervision concept of the OMSG.
Therefore this board type is displayed as empty slot or with the board state “Empty”.
Starting the Equipment Overview the first time of a session, the root NE and the racks of the NE are dis-
played as basis to navigate through the different levels of the NE equipment. Each further time the Equip-
ment Overview is opened during a session, it displays the last contents.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 201 / 926
926
6.2 Navigation
The navigation through different levels of the NE equipment is performed by double clicking on the objects.

The following figure depicts zooming to the board level of a subrack.

Figure 64. Navigation in the Equipment Overview

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 202 / 926
926
6.2.1 View Description
Existing objects are shown in light grey. New objects called into the display (after double-clicking on them
or executing the Add Equipment command) are shown in dark grey.
?) )
$

) &

%

Figure 65. Appearance of the Equipment Last Shown
The alarm synthesis icon is located to the left of each object and the object name is shown to the right.
When moving the mouse pointer to the respective area, the related information appears in the status line
at the bottom of the view.
Board States:
At board level, a board status icon may be visible to the right of the alarm synthesis icon. After moving the
1AA 00014 0004 (9007) A4 – ALICE 04.10
mouse pointer to that area, the corresponding board state is shown in the status line at the bottom of the
view.
3AL 89062 AA AA 203 / 926
926
Refer to chapter 7.3 for a description of the detailed board states.
EPS Protection Status:

At board level, the EPS protection status may be visible to the left of the object name.

N.B. When selecting a board which is part of an EPS protection group, all the boards belonging to
that group are marked by a rectangle on the EPS protection status field.
After moving the mouse pointer to the EPS protection status area, the corresponding status is shown in
the status line at the bottom of the view.
Refer to chapter 9.3 for a description of the detailed EPS protection states.
6.2.2 Popup Menu
Every command of the menu is also available using the right mouse button in the view. Some of the com-
mands are not accessible depending on the object selected. The NE object cannot be selected.
Add Equipment
Expand next level

Hide equipment
Set in service
Set out of service
Reset
Remote Inventory

Figure 66. Popup Menu

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 204 / 926
926
6.2.3 Expand/Hide Commands

Permanently hides all empty slots of all objects in the Equipment Overview. Empty slots are never dis-
played as long as the menu option is active. Switch the function on or off by selecting the menu option
again.
Expand next level
Shows the objects of the next lower level.
Shows all objects of the subtree down to board level.
Hide equipment
It is possible to remove (hide) objects and the associated sub-objects from the Equipment Overview.
Hides the lower objects of the selected objects.
Hides all empty slots in the current view. When an object is displayed once again, empty slots are no longer
hidden.
To hide empty slots permanently, select menu “Permanently hide empty slots”.
6.2.4 Navigate to... Commands
The Navigate to... commands open the corresponding views (Equipment, Port or Transmission view) of
the selected object.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 205 / 926
926
6.3 Add Equipment
It is possible to filter the shown equipment in the Equipment Overview. Select the command Add Equip-
ment in the Equipment Overview menu or in the popup menu.

Equipment Overview
Add Equipment
...
Figure 67. Add Equipment to the Equipment Overview
The following dialog appears:

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 206 / 926
926
Figure 68. Equipment Filter Dialog
Select the rack or subrack on which the filter parameters should work in the left equipment list.
The User Preferences allows you to save and load preferred filter settings, graphical adjustments or TP/
equipment lists. For a detailed description of the handling of user preferences, refer to Chapter 3.7.
Select the Subrack Type and/or the Board Type of the equipment with the option button on the right.
The Port Type is only available when the check box Enable Port Level is selected.
For a detailed description of the ACD filter, refer to Chapter 4.2.
The Eps Filter is only available, when the check box Enable Eps Filter is selected.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The Eps Filter has two parameters:
– Board Type (Eps) lists all available Eps-Board-Types.
3AL 89062 AA AA 207 / 926
926
– Eps Status. The following status are selectable:
• Ignore

• No Request

• Manual
• Auto
• Forced
• Lockout
The board filter has two parameters:
– Board Status. The following status are selectable:
• Ignore
• Dependent inoperability
• Download
• Empty
• Faulty
• Active
• Out of service
• Stand by
• Out of service
• Stand by
N.B. The item Active stands for the administrative board state In Service. It does not denote the
board status Active as displayed in Equipment Overview for every board.
– Alarms Status. The following alarms are selectable:
• Ignore
• Cleared
• Indeterminate
• Warning
• Minor
• Major
• Critical
1AA 00014 0004 (9007) A4 – ALICE 04.10
Press Apply to start the filter process with the selected parameters or OK to start the filter process and
to subsequently close the dialog. Press Close to close the dialog without starting the filter process.
3AL 89062 AA AA 208 / 926
926
Help opens the online help related to this dialog.
N.B. During the search process, the message area of the Equipment Overview continuosly shows
the number of received objects. This is not the number of objects matching the filter criteria, but
indicates that the filter process is still in progress. After the filter process has finished, the num-
ber disappears.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 209 / 926
926
6.4 Clipboard
Use the Clipboard dialog to perform the same action on a number of objects (TPs or equipment) in one
step.

Equipment Overview
Clipboard...
...
Figure 69. Clipboard of the Equipment Overview
Figure 70. Clipboard – Equipment Overview
Within this dialog it is possible to Set one or more Boards in Service, to Set one or more Boards Out of
Service or to Reset one or more Boards.
1AA 00014 0004 (9007) A4 – ALICE 04.10
For a detailed description of the Clipboard dialog see chapter 3.8.
3AL 89062 AA AA 210 / 926
926
7 BOARD/SUBRACK MANAGEMENT
In the “Getting Started” , section SC. 1.3, have been described the Equipment views and the navigation
procedure. This chapter provides specific details info. for board management and for board view :
– Board / Subrack / Rack / NE Level
– Board / Subrack management
• OMSG Board management
• W/OMSN Board management
– Multi Access Board
– Board view layout
– Board states and EPS states
– Cable configuration
– Remote inventory
– Board Configuration for WDM
7.1 Board / Subrack / Rack / NE Level
This chapter deals mainly with the different subrack management level iand with the supporting command.
Using the W/OMSN menu, select the Equipment option from the Views pull down menu
The first level of the “Subrack management” will be displayed directly into the current window (see the
following figure). This level has been named “Equipment Overview” as the navigation procedure available
for OMSG family.
The Equipment Overview enables a fast navigation through all levels of the equipment hierarchy.
Navigation is done from higher to lower levels. Starting with the Room access point, the user can either
navigate through the various equipment levels or directly access the relevant level via Equipment
Overview.
The NE hierarchy is organized in the following way: subrack > board > port > TP
The navigation through different levels of the NE hierarchy is performed by double clicking on the objects:
• the first level shows the subrack level of the Equipment view (see Figure 71. );
• further, by double clicking on a board body, the board level of the Equipment view can be
reached.
• further, by double clicking on a port body contained in the board, the port level of the Equipment
view can be reached. The port view displays the inner TPs.
• it is possible to go back to the upper level of representation by pressing the <ESC> key on the
keyboard or selecting Backward (USM 6.x) option from the Views menu; or to go back to the
previous view, by selecting the Previous or Forward (USM 6.x) option from the Views menu.
N.B. Selecting in the first level of the Equipment view ( Subrack level, Figure 71. ) the Show
1AA 00014 0004 (9007) A4 – ALICE 04.10
supporting equipment option from the Equipment menu, the Rack level view of Figure 72.
is presented; further, selecting in the Rack level view the Show supporting equipment option
from the Equipment menu, the Equipment level view of Figure 73. is presented.
3AL 89062 AA AA 211 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 72. Equipment Overview – Rack level
Figure 71. Equipment Overview – Subrack level
926
3AL 89062 AA AA
212 / 926
Figure 73. Equipment Overview – Equipment level
In the Subrack view are available the options offered by the Equipment menu (see Figure 74. ) clicking
on it in the menu bar.
Alarms indications are present at every NE level. At any alarms / TPs the user can associate a different
severity profile as described in chapter 3.4.1
All the options offered by equipment menu are described in the next paragraphs.
Set and change the boards present on the Equipment is the main function.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 74. Equipment menu.
3AL 89062 AA AA 213 / 926
926
7.2 Board management
Board/Subrack setting operation are reported for OMSG and for W/OMSN with two distinguished para.
to point out clearly the difference procedure. The main aspects described are:

– configuration of a new board
• Set a Board in / out of Service
• Configure the board using the option “Set” (only for W/OMSN)
– change of board type (only for W/OMSN)

• “Set out of service” the board
• Configure the board using the option “Set”
– remove a board (only for W/OMSN)

• “Set out of service” the board
• “Remove” the board.
– multi access board: example of a multi access board Configuration
7.2.1 OMSG Board management
7.2.1.1 Set a Board in Service
1) In the Equipment Overview or in the Board view, click on the board in order to select it.
2) Select the Set in service option of the Equipment Overview or Equipment pull down menu
or select the command from the popup menu:
Equipment Overview Equipment
... ...
Set in service Set in service

Set out of service Set out of service
Reset Reset
Remote Inventory Remote Inventory >
... ...
Figure 75. Setting a Board in Service
Confirm the command in the following dialog with Ok. Cancel aborts the operation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 214 / 926
926
N.B. If, after setting an optical STM-1 board in service, the Port view still registers this board as ”Out
Of Service” and therefore the MSP Management dialog is not accessable, close and reopen
the NE Equipment view.
7.2.1.2 Setting a Board out of Service

( ** $ /1
*3 *63 )
"(> *5 *56 ) )
" $ @
) )
@
2) Select the Set out of service option of the Equipment Overview or Equipment pull down
menu or select the command from the popup menu.
N.B. Notes:
– Boards are not allowed to be configured, that are intended to set “Out of Service”.
– An active protecting STM-1 optical board cannot be taken out of service, even if the board is currently
not carrying traffic. Perform a manual or forced switch to the protected board first and then take the
protecting board which is now passive out of service.
– A protecting STM-1 electrical board (P4ES1) cannot be taken out of service in the current release.
If for maintenance purpose the card has to be plugged out, this can be done without setting it out of
service, but with caution that the card is not active protecting.
Perform a manual or forced switch to the protected board first and then take the protecting board
which is now passive out of service.
If the card is plugged out while it is active protecting you will risk a traffic hit of about 600 ms.
– On Common I/O Port boards, the related Access boards and the submodules have to be taken out
1AA 00014 0004 (9007) A4 – ALICE 04.10
of service before the board can be taken out of service.
3AL 89062 AA AA 215 / 926
926
... ...


Reset Reset
... ...
Figure 76. Setting a Board Out of Service
Confirm the command in the following dialog with Ok. Cancel aborts the operation.
N.B. The error message ”Can’t decode this ANY, keep it in BER” indicates that the board could not
be taken out of service.
7.2.1.3 Reset a Board
This command resets the selected board.
2) Select the Set out of service option of the Equipment Overview or Equipment pull down
menu or select the command from the popup menu.
... ...

Reset Reset
... ...
1AA 00014 0004 (9007) A4 – ALICE 04.10
Confirm it in the following dialog (which is only an example) with Ok. Cancel aborts the operation.
3AL 89062 AA AA 216 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
a reset.
01
926
3AL 89062 AA AA
Not all equipment types provide ’reset’, e.g. in the Common I/O shelfs only the SMX board can perform
217 / 926
7.2.2 W/OMSN Board management
The same procedure can be also applied to WDM subrack and boards. This chapter does not concern the
slot – board type association or specific setting and removing board procedures. For details see the proper

Craft Terminal NE docs.

7.2.2.1 Setting a Board
– Click on the empty slot (grey board) in which a board has to be added or on an existing
Out–of–service board (without the lock symbol) in order to change it (see para. 7.2.2.2) . The contour
becomes highlighted to show that operations can be done on it.
– Select the Equipment pull down menu. Then select the Set... option as shown in Figure 77.
Figure 77. Setting a board.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 218 / 926
926
– Figure 78. shows the different types of boards that can be equipped
Figure 78. List of different equipped boards relative to an NE slot (example).
N.B. The list of boards displayed during a ”Set Board” operation is restricted to those that can be
accepted by the equipment in the selected slot. For details on the board identified by acronyms
and NE physical composition refer to proper CT–NE Technical Handbook
– Choose the board type required, by clicking on the corresponding item in the list. The name of the
board is highlighted. Click on the OK push button to validate the choice.
– The board representation appears on the NE view in the slot when the board change is effective. A
lock representation appears over the boards (”In–Service”).
– In the Create/Modify dialogue box, the Cancel push button cancels the operation and closes the
dialogue box. The Help push button opens the Help view giving information about the context.
N.B. The OS does not perform consistency check between added boards and boards already
plugged at subrack level. For example, too many boards of a given type will not be recognized
1AA 00014 0004 (9007) A4 – ALICE 04.10
by the SH.
3AL 89062 AA AA 219 / 926
926
7.2.2.2 Modify board
The modify command is used to reconfigure a board with another that can be equipped in the same slot.

N.B. This procedure can be done to replace an existing optical module with another of different

type without previously remove it.
Changing the board, the same payload traffic is transported and the service assured: the new board,
chosen among a compatible board list, is configured remaining “In Service”.
Click on the optical module to replace. The outline of the slot becomes highlighted to show that operation
can be done on it. Select the Modify... menu option. Figure 79. opens
Figure 79. Replaceable Boards
Select the board type in the listed replaceable boards and click on the OK button. Wait the required time
for the operation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 220 / 926
926
7.2.2.3 Removing a board
Click on the board to remove. The outline of the slot becomes highlighted. This indicates that the board
is selected and that operations can be done on the slot.
Remove, if necessary, the padlock with the “Set out of Service” command (see para. 7.2.2.5 . ).
Select the Equipment pull down menu. Then select the Remove option as shown in Figure 80.
Figure 80. Removing a board.
N.B. It is possible to remove a board only if it is not involved in any type of cross connection (OH
bytes included) or Performance monitoring.
– From the confirmation dialogue box that opens you can confirm or cancel the ”Remove Board” operation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 221 / 926
926
7.2.2.4 Setting a board in service
Any configured board is normally created (with the “Set” command) with a padlock representation
(Figure 81. ). That means that the board is in service and can not be directly removed. When a board is

in service the traffic can be configured and the alarms are enabled. If the same slot can be equipped with

different board types the modify menu option is enable (black) and the user can follow the procedure
described in para. 7.2.2.2.
Figure 81. NE Equipment View
All the empty boards are automatically created without the padlock indication and the “Set in Service” or
the “Set out of Service” menu options are not available (greyed).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 222 / 926
926
7.2.2.5 Setting a board out of service
The padlock of “In Service” board can be removed with the “Set out of Service” command. In this case
select the locked board and then the Set out of service option on the Equipment pull down menu. Select
the Ok push button in the confirmation window which appears.

When the out of service command is applied on a W/OMSN board, no consequence on the generated
alarm, PM and on the transmitted traffic is provided. The lock representation is substituted by the symbol
over the boards.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 223 / 926
926
7.2.2.6 Software description
This function allows the operator to visualize information about the software(s) which is(are) present in the
selected board.

– Click on a board whose software you want to know. The outline of the slot becomes highlighted. This
indicates that the board is selected and that operations can be done on the slot.
– Select the Equipment pull down menu. Then select the Software description option of Figure 77.
The following window opens.
Figure 82. Software Description dialogue box.
The dialogue box contains as many folder sheets as there are softwares in the selected board.
Click on the Close push button to close the dialogue box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 224 / 926
926
7.2.3 Multi Access Board
7.2.3.1 Introduction
Different card types are available with the new USM version:
– access card: it is a board containing the physical interfaces (electrical connectors).
– port card: it is a board that performs the SDH signal processing.
– module (electrical or optical: it is a particular plug–in card (of small dimensions) inserted on the front
panel of some particular boards
These units can be equipped in different equipment shelf areas: the access area where are inserted the
access card and the basic area equipped with the port cards. The port cards can be terminated in the same
port card or in the access card. The name of the low speed port cards begins with the acronym “P...” (i.e.
P4E4N means 4x140/STM1 Switch O/E Port/1 ). The name of high speed port card STM4 and STM16
are preceded by the S or L characters depending on the haul type (short or long) (i.e. L–4...,S–16...). The
name of the access card begins always with the A character (i.e. A4ES1 means 4xSTM1 electrical). The
acronym meaning, slot number, access card associated to port card, and any other detail are described,
for any related NE, in the NE technical handbook.
The boards can be equipped with electrical or optical modules to provide a flexible equipment
configuration ( ICMI stands for the 140/155 electrical interface module).
For the multi access board creation and relevant changing and removing, the relative port, module and
access card slots have to be considered.
Alarms and Status indications referred to the board level are present at the bottom of any new view.
This information are “In/Out of service” of the board (Administrative State) and board alarms and status
like “missing” (RUM) or “mismatch” (RUTM), EPS condition if supported and other indications typical of
each unit. Here will not mentioned the commands described for the W/OMSN boards (see para. 7.2.2)
Some examples are here reported to show the configuration items to equip a 4xSTM1 optical board in a
1660SM 2.0A NE and 4x140/STM1 switchable electrical port using the USM 5.x version.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 225 / 926
926
7.2.3.2 Multi access board configuration
Select the appropriate empty slot in the 1660SM to equip the 4xSTM1 optical board: this board is named
P4S1N and can be equipped in the slot 24 to 39. Open the “Equipment” menu and, with the “Set”

command, select the P4S1N board. Double click on P4S1N to open Figure 83. Select the empty daughter

and again, with the “Set” command, select the required STM–1 module from the acronym list (i.e. IS–1.1
is for optical interface Short haul– STM1. first window). Complete the board configuration with the second
module and then select the associated access card. In fact, this port card needs four (electrical or optical)
modules to be fully connected. Two modules have to be inserted on the card front panel and two on the
corresponding access card 2 x STM1 front panel (A2S1).
Figure 83. Multi access board view
The slot of the associated access card can be identified with the relationship between port and access
card table reported on the technical manual (i.e. if the port card slot is 31, the access card slot will be 9).
Select the associated slot and click from the “Equipment” menu the “Set” command to select the access
“A2S1” card. Open the access card and repeat the previuosly module configuration to have a fully
equipped unit.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 226 / 926
926
When the user wants to remove a multi access board, he has to remove the modules inside the board itself.
An error indication points out a wrong followed procedure (see Figure 84. ).
Figure 84. Error indications removing a board equipped with its modules
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 227 / 926
926
7.2.3.3 Change Physical Interface
This command allows to change the type of physical interface in a bi–mode port (140 Mbit/s / 155 Mbit/s
switchable port) i.e it changes the SPI or PPI object into PPI or SPI (140 Mbit/s / 155 Mbit/s).

Select the Symbol of the port in the “Board view”.
To equip 4x140/155 switchable electrical ports into 1660SM NE, set, in the correct slot, the 4x140/STM1
switchable O/E port card: this board is named P4E4N (slot 24 to 39) while the electrical module is named
ICMI. Add the access card (A2S1: slot 2 to 9, 13 to 20) to have a 4–electrical port configuration.
Click on Change Physical Interface menu option of the Board menu
Figure 85. Change Physical Interface
The following dialog box is opened:

1AA 00014 0004 (9007) A4 – ALICE 04.10
Click on the OK push button to change the physical interface.
Click on the Cancel push button to abort the change of the physical interface.
3AL 89062 AA AA 228 / 926
926
7.3 Board View Layout
A general layout description is reported in the example of Figure 86.

The Board view shows:

– The icon representations of the ports it is composed of. There are as many icons as there are
different ports. In the above figure one type of ports are represented, an PDH port.
Double-clicking on this port icon opens the related Port view.
– An probable alarm causes information area which enables the user to determine the probable
cause of the alarms occurring in the board.
This probable alarm cause information area uses the alarm severity color definition described
previously to indicate the severity of the alarms occurring.
Refer to the Alarm Reference Guide, section SC2.2, for detailed alarm information.
– Small alarm icons next to the Port views that indicate the most critical alarm occurring in the port.
To get details on the alarms occurring in the ports, navigate to the Port view.
– The administrative state of the board.

)) $
1AA 00014 0004 (9007) A4 – ALICE 04.10
)
Figure 86. Example of a Board View
3AL 89062 AA AA 229 / 926
926
7.4 Board States and EPS States
The detailed board state is represented by a status icon on top of the board’s front label in the subrack
level of the Equipment view. As an exception, the statuses “In Service”, “Unspecified” and “Empty” are

displayed without specific “board” icons.

The EPS status of a board is represented in the same view by a status icon located below the board state
and alarm icons. On selecting a board which is part of an EPS protection group, all the boards belonging
to that group are marked: all the EPS protection status icons of the selected group turn dark grey while
all other EPS status icons remain light grey.
When pointing to a board with the mouse, the board name and the protection role are displayed in the
status line at the bottom of the view.
#=
(= $
Figure 87. Detailed Board State example
Detailed Board States:
– Dependent Inoperability
The board cannot provide its service due to a state of another board on which it is dependent.
Inoperability relates to the absence of intrinsic functional and/or management capabilities.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Download
The board is currently being loaded and/or tested automatically before it is put into operation.
3AL 89062 AA AA 230 / 926
926
– Empty
The board cannot be accessed, i.e. the slot is empty or a board which is plugged in is not detected.
N.B. The DCC Server Board (DSB) is not integrated in the general supervision concept of the
OMSG. Therefore, this board type is displayed as an empty slot or with the board state
“Empty”.
– Faulty
The board is faulty, in terms of either on the hardware or software; the usage may be intended or not
intended.
– In Service
The board has been put into operation and is now active (carrying traffic).
– Out of Service
The board has been taken out of service, i.e. the board management is internally operable but no
usage of the implemented functions is possible (e.g. traffic signal monitoring); therefore, the
functional objects may be deleted.
– Standby
The board has been put into operation, but remains on standby (operating correctly, but not carrying
traffic). This is the normal status of a protection board.
– Unspecified (no special board state icon displayed)

It is not intended to plug in a board. The slot should remain unequipped.
=
=? %
= #=
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 88. EPS Protection State
3AL 89062 AA AA 231 / 926
926
EPS Protection States:
Refer to the Protection Management chapter for more details about Equipment Protection Switch.

– Unknown state


During the period the EPS protection status is being requested from the NE a question mark is
displayed in the EPS status field.
– Normal state
No protection is currently active for the selected board.
– Lockout
EPS is disabled for the selected board.
– Switch
Used for Auto Switch, Forced Switch and Manual Switch (not supported on OMSG).
The board is involved in an EPS switch (either protected or protecting board).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 232 / 926
926
7.5 Navigation Commands in Board View
7.5.1 Show Supporting Equipment

Board
...

...
Figure 89. Show Supporting Equipment
This menu provides the possibility to navigate directly to the Equipment View of the subrack that supports
the board.
7.5.2 Navigate to Port View
Board
...
...
Figure 90. Navigate to Port View
This menu provides the possibility to navigate to the Port View of a selected port.
Alternatively the Port View can be accessed by double-clicking on the selected port.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 233 / 926
926
7.5.3 Navigate to Transmission View
Board

...

Figure 91. Navigate to Transmission View
This menu provides the possibility to navigate to the Transmission View of a selected port.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 234 / 926
926
7.5.4 ATM Navigation
The “ISA navigate” command starts the ATM application of the NE Craft Terminal . With an EPS ISA
board configuration select the correct active ISA board, the unit with the EPS state or the unit with
the protection switch but without the faulty indication, to access the navigation option.
Figure 92. ISA navigation option
The same indication can be obtained reading the ATM board states on “EPS management” window. The
ATM windows are described into ATM Operator’s Handbook, Craft Terminal for ATM Management chap-
ter, while the ISA Board IP address and the ATM configuration info. have been described in the 20o ATM
Management chapter of the SH Operator’s Handbook.
7.6 ATM Configuration

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 93. ATM Configuration option
The ATM Configuration feature, when supported, has been described in the chapter 20 on page 845.
3AL 89062 AA AA 235 / 926
926
7.7 Cable configuration (only applicable to OMSN)
Some NEs (i.e. 1670SM) have to be configured filling the Cable configuration table.

This option gives to the operator the possibility to describe the way in which the main sub–rack (1670SM)

is connected to the boosters and/or preamplifiers. In the following paragraphs will be described the way
to activate the cable list configuration view and the meaning of the displayed information.
To manage the connection execute the following operation:
– Click on the NE main sub–rack (for 1670SM select SR70M) in the equipment view. The outline of
the NE becomes highlighted. This indicates that the NE is selected.
– Select the Cable configuration option of the Equipment pull down menu.
Next figure shows these selections:

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 236 / 926
926
Figure 94. Cable configuration selection
The user can equip the NE with the boosters BTS 10 or BTS 15. The 1670SM in the 2.0.A version does
not provide “Preamplifier” units. The usually optical boards associated to the boosters are: L–642, S–642,
L–162.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 237 / 926
926
After the selection the following figure is displayed.

Figure 95. Cable configuration view
From a logical point of view, the window is divided in 3 parts:
– The upper field displays the configurations provisioned.
– The lower field (Add/Modify/Delete Element) is divided in 3 parts:
• the left part is related to a schematic representation of the optical port that could be equipped
in the NE
• the central part is related to preamplifiers
• the right part is related to boosters
– The bottom is related to the Ok, Cancel, and Help buttons.
Two arrows are placed near Preamplifier and Boosters text. The right arrow (–>) is representing the output
fiber, while the left arrow (<–) is representing the input fiber.
The combo box summarize the following possibilities:
– The optical port output fiber could be connected directly to line

1AA 00014 0004 (9007) A4 – ALICE 04.10
– The optical port output fiber could be connected to a booster placed in a slot in the example of
1670SM subrack; in this case the box will show a label referred to the Booster type and the physical
slot in which the board is inserted.
3AL 89062 AA AA 238 / 926
926
Of course it is not possible to have two boxes showing the same slot number.
Every time the operator wants to set up the cable list the most updated information are shown.
Then the operator can choose to connect an aggregate output to a booster and/or to connect an optical
port input to a preamplifier output. Both operations can be performed selecting the appropriate items from
the correspondent box.
It’s operator responsibility check that the selected booster/preamplifier is really equipped and correctly
inserted into its slot in the subrack. It is also operator responsibility verify that the selected cable list
configuration is coherent with the actual equipped board or with the boards she/he wants to equip.
It is software responsibility to show correct and congruent information in the boxes the operator can
activate.
At the end of the cable list configuration, send it to the NE pushing the Ok button and confirming the
operation to the standard message box that will appear.
After this close the cable list configuration window pushing the Cancel button.
To cancel the cable list configuration, push the Cancel button in the cable list configuration window. In this
case the window will be closed automatically.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 239 / 926
926
7.8 Remote Inventory
This paragraph describes the access to the remote inventory of this NE.
In the Remote Inventory are stored information of identification, construction data ect.

The options used are:
– Upload Remote Inventory: store the Remote Inventory data in the SH
Select “Supervision” –>Remote Inventory” to open Figure 96.
Figure 96. Remote Inventory confirmation request
Clicking on OK after a waiting time the information of Figure 97. is presented
Figure 97. Remote Inventory completed
To display the remote inventory data, previously stored in the SH, different procedures at rack, subrack
and board level are provided. The description starts from para. 7.8.1.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 240 / 926
926
7.8.1 Rack Remote Inventory
This command displays the remote inventory data of the selected rack.
Figure 98. Rack Remote Inventory menu option
If the NE is constituted by different racks (i.e. Cross–Connect ), select the rack type and then click on the
“Rack Level” menu option. Confirm the command on the confirmation dialog box with OK to open the
“Print” dialog window, Cancel aborts the operation.
Select the remote inventory print destination, printer or file. For a more detailed description of the print
procedure see chapter 3.10 “Printer dialog” .
If the remote inventory data is saved as ASCII file, it can be read using the Unix command “vi” (see
Figure 99.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 241 / 926
926
Figure 99. Visualization of rack remote inventory file with “vi” editor
The rack remote inventory list starts from the bottom subrack to the top subrack and for the same subrack
from the right board to the left board. In the example reported in Figure 99. the board location 03, 02 are
the last two boards of the lower subrack and the board location 17 is the first board on the right of the upper
subrack.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 242 / 926
926
The remote inventory are factory information identifying the boards, the final test and eventually other data.
The data are written inside each boards and the operator can only collect the data and read them. The
following remote inventory are available:
• Board Location
Specifies only the slot where the board is plugged in. The rack and subrack indications are fixed
to “00 0”
• Board Type
Specifies type of board, e.g. EmptySlot, AGG16... .
• ALCATEL Company
It indicates the Company’s (Alcatel’s branch) which designs the unit.
Refer to Alcatel for the abbreviation meaning (four characters).
• CLEI Code
It indicates the CLEI code according to Bellcore specs. TR–ISD–325
• Unit Part Number

It indicates Alcatel or Factory product Part No.. The number indicated is that printed on the
labels or on the units front plates.
• Software Part Number

It indicates the id. of the unit resident software
• Serial Number
It indicates the product serial number as specified by the NR 130 Norm.
• Unit Type
It indicates the units acronym
• Factory Identifier / Manufactoring plant

It indicates the Company’s manufacturing plant id. within the company, producing the unit.
Refer to Alcatel for the abbreviation’s meaning.
• Date identifier
It indicates the meaning of the date that follows.
It is a two–digit code supplying the following information:
00 date of construction at the time of final testing

01 production order data
02 construction date of the unit lot
03 date product has been forwarded to customer
04 customer order date
• Date (YYMMDD)
The identification of the date depends on the indications stated in the previous field. When only
the year is displayed, the format must be ”YY– – – – ”
• Operator Data
It indicates customer’s data ( name, site...)
• Free For System Use

1AA 00014 0004 (9007) A4 – ALICE 04.10
This is reserved for the registration of modifications at the site. Each modification is identified
by a number. Two numbers can be displayed at a time. After more than two modifications, the
oldest entry is deleted.
3AL 89062 AA AA 243 / 926
926
The operator can visualize the (General) remote inventory list of all racks, subracks and boards using the
following USM commands:
• Select “Supervision” menu and then Upload Remote Inventory menu option (see para.7.8).

• Select “Diagnosis” menu and then View–> Remote Inventory menu option (see Figure 100. ).
N.B. To visualize the updated “General” Remote Inventory data select before the Upload
Remote Inventory option and then the View of the Remote Inventory data. The data are
updated any time the remote inventory uploading command is applied.
Figure 100. General remote inventory data example
The USER LABEL of Figure 100. gives the information related to the NE type and the rack, subrack and
1AA 00014 0004 (9007) A4 – ALICE 04.10
slot board indications. Even here the list is ordered starting from the last rack on the right, the last subrack
on the bottom and the last board on the right.
3AL 89062 AA AA 244 / 926
926
7.8.2 Subrack Remote Inventory
This command displays the remote inventory data of the selected subrack.
Figure 101. Subrack Remote Inventory menu option
If the NE is constituted by different racks (i.e. Cross–Connect ), select the rack and then the subrack type
and then click on the “Subrack Level” menu option. Confirm the command on the confirmation dialog box
with OK to open the “Print dialog”, Cancel aborts the operation.
Follow the procedure described for the Rack Remote Inventory (see 7.8.1 paragraph) to get the data
information. The remote inventory window will contain data of all the equipped subrack boards.
As for a NE composed by many racks, subracks and boards even here it is possible for a NE composed
by a single subrack to visualize the remote inventory of all boards using the following USM commands:
• Select “Supervision” menu and then Upload Remote Inventory menu option.
• Select “Diagnosis” menu and then View–> Remote Inventory menu option. (see Figure 102. )
N.B. To visualize the updated subrack remote inventory data firstly select the Upload Remote
Inventory option and then the View of the Remote Inventory data. The data are updated
any time the remote inventory uploading command is applied.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 245 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 102. Remote Inventory of a NE subrack
926
3AL 89062 AA AA
246 / 926
7.8.3 Board Remote Inventory
This command displays the remote inventory data of the selected board.
This option, for OMSG, can be selected from the “Equipment” or from the “Equipment Overview” menus
while for W/OMSN from the “Equipment” menu only.
Select the board type and then click on the “Board Level” menu option to open Figure 104.
Figure 103. Board Remote Inventory menu option
The following data is displayed:
Board Information
• Board Location /Location name

It indicates, if present, the unit physical location (rack, subrack in the rack, board in the subrack).
• Board Type
It indicates the board type
Element Identification (as described for rack remote inventory, para. 7.8.1).
Manufacturing Information (as described for rack remote inventory, para. 7.8.1).
Operator Inventory Information
• Operator Data
It indicates customer’s data ( name, site...)
• Free For System Use

1AA 00014 0004 (9007) A4 – ALICE 04.10
It indicates additional info.
3AL 89062 AA AA 247 / 926
926
Figure 104. Board Remote Inventory window
The board Inventory window can be printed clicking on the “Print” button.
Using the Print button, remote inventory data can be saved to a file or printed on paper.
The default directory for printing to file is /alcatel/1353sh/maintenance/core/emlusm.
N.B. The file has to be printed to directory /alcatel/export in order to export (for OMSG) it to
floppy disk or tape.
If no printer is installed, no error message is displayed to indicate this.
See para. 3.10 for more details of the print dialog.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 248 / 926
926
7.9 Board Configuration for WDM
The features described in para. 7.9.1 7.9.5 are typical for 1640WM, those described in para. 7.9.6
7.9.8 are common to more NEs, those described in para. 7.9.9 7.9.11 are for 1696MS, and the para.
7.9.12 is for 1686WM. Some of WDM features can be also applied to OPS and OCP equipments.
Figure 105. Board menu displayed (examples)
According to the selected Board a specific menu is displayed. The following options are available (not all
at the same time) according to the board type.
7.9.1 Output Power Level Configuration for 1640WM
The setting of the Optical power level can be performed on different boards. These commands are
described in the following procedures:
– Set the Optical power level for Tributaries boards,

– Set the Optical power level for OFA boards,
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Set the Optical power level for TCS boards,

– Set the Optical power level for WDA boards,
– Set the Optical power level for MDX boards,
3AL 89062 AA AA 249 / 926
926
– Enable the Automatic Laser Control (ALC),
– Disable the Automatic Laser Control (ALC).
Set the Optical power level for Tributaries boards

1) Display the board view of the board you want to set.
2) Choose the Board – Optical power level configuration menu option.

The ALC & Output power level configuration dialog box is displayed.
3) Set the value of the Pre–emphasis channel within the authorized range.
4) Click on Apply to terminate.
Set the Optical power level for OFA boards

3) Set the value of the Optical power level – output second stage within the authorized range.
Set the Optical power level for TCSboards

3) Set the value of the Optical power level – output combiner within the authorized range.
The Output power level configuration is possible only if the ALC is disable.
Set the Optical power level for WDA boards

3) Set the value(s) of the Optical power level – aggregate ouput toward OFA [OFA identification,
with rack, subrack and slot information] within the authorized range.
Set the Optical power level for MDX boards

1AA 00014 0004 (9007) A4 – ALICE 04.10

3AL 89062 AA AA 250 / 926
926
3) Set the value of the Attenuation – VOA main path within the authorized range.

Enable the Automatic Laser Control (ALC)
N.B. For the TCS boards, only on the TCS301, TCS311 and TCS401 boards, the option ”Automatic
laser control enabled” is available.
1) Display the board view of the board you want to modify.

3) Choose the ALC Enabled menu option.
Disable the Automatic Laser Control (ALC)
N.B. For the TCS boards, only on the TCS301, TCS311 and TCS401 boards, the option ”Automatic
laser control enabled” is available.
1) Display the board view of the board you want to modify.

3) Choose the ALC Disabled menu option.
When available, this option allows the operator to enter a value. The system checks the customizable min
and max values. The range value depends on the board type and local data.
Note : On the TCS301 board, the option ”Automatic laser control enabled” is available.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 251 / 926
926
Example of values
applicable either to
TRB or OFA boards
TCS301 board
TCS401 board
Figure 106. Output power level measurement typical views
7.9.2 Frequency and grid configuration (available only for 1640WM)
1) Choose the Board –> Frequency and grid configuration menu option to open Figure 107. .
The Frequency and grid configuration dialog box is displayed.
The proposed options are Frequency (THZ) and Grid (GHZ)
Frequency (THZ) displays the channel identification of the board.
Grid (GHZ) displays the grid used: 50 or 100 GHz.
2) Click on Cancel to terminate.
N.B. The Grid configuration cannot be set from this option but during the board creation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 252 / 926
926
Figure 107. Output power level measurement Typical views
7.9.3 Pumps Configuration (available only for 1640WM)
1) Display the view of the board.
2) Choose the Board –> Pump Configuration menu option of Figure 105. :
The proposed options are:
– to connect or disconnect pump 1,
– to connect or disconnect pump 2.
N.B. When a Pump is connected (Inactive/active) the square below the Administrative State is
green and when a Pump is not connected (Undefined) the square is blue.
3) Choose one of the proposed option.
4) Click on OK to terminate.
7.9.4 Amplifier Msv configuration (available only for 1640WM)
The setting of the OFA boards Msv, can be performed by mean of one of the following procedures:
– Set manually the amplifier Msv,
– Set automatically the amplifier Msv.
These modifications could be traffic affecting.
Set manually the amplifier Msv
This option is only available for an OFA3xx board.
1) Display the board view of the OFA3xx you want to set.
2) Choose the Board – Amplifier settings menu option.

The Msv Manual Configuration dialog box is displayed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3) Set the value of the second stage output power within the given range.
4) Set the value of the mid–stage VOA attenuation within the given range:
3AL 89062 AA AA 253 / 926
926
– If no DCU is present at the interstage, provision the mid–stage VOA attenuation at 15 dB.
– If a DCU is present at the interstage, provision the mid–stage VOA attenuation at 15–DCU
losses.

N.B. It is recommanded to configure the value automatically (see the procedure: Amplifier

automatical setting, page 254).
5) Click on the Set reference push button to set the first stage input power data as the reference
input power data.
6) Set the value of the input power margin for DMS alarm within the given range.
This option is only available for an amplifier.
7) Click on Ok to terminate.
Set automatically the amplifier Msv
This option is available only from an OFA3xx preamplifier in a Terminal or an OFA3xx ILA in a Repeater.
1) Display the board view of the OFA3xx you want to set.
2) Choose the Board – MSV Configuration menu option.

The Msv Auto Configuration dialog box is displayed.
3) Click on the Calculate VOA push button.

The data is displayed in the New Mid Stage VOA field.
4) Click on Ok to terminate.
• Amplifiers Settings: Permits to set the MSV configuration for an OFA3xx.
7.9.5 MSV Configuration (available only for 1640WM)
• MSV Configuration: Permits to set the MSV configuration for an OFA3xx with an automatic
calculation of the mid–stage losses (see the above para.).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 254 / 926
926
7.9.6 Alarm threshold configuration (If supported by the board)
This command manages the alarm thresholds according the selected board type (i.e.: Tributaries, OSC,
OFA, Booster, Preamplifier, In–Line Amplifier, OMDX and OADM boards). Generally the power level of the
optical line input and output are monitored by alarm threshold values (in dBm or dB for tributary boards).
Some example of threshold values are:
– The input Fail Alarm High Threshold,

– The output Fail Alarm High Threshold.
– The input receive power degraded
– The output transmit power degraded
A threshold table is created and assign by default to each type of these boards. This default table can not
be modified or deleted. But you can create new tables, in which you can set the threshold values, and
assign them to the board types you want.
To manage these boards alarm threshold use the following procedures:
– Display the alarm threshold tables,

– Create an alarm threshold table,
– Modify an alarm threshold table,
– Assign an alarm threshold table,
– Delete an alarm threshold table.
N.B. On Figure 108. different command buttons will be available according with the threshold table
selected: for default tables the “Apply”, “Clone” and “View” commands; for clone tables, the
“Apply”, “Clone”, Modify”, and “Delete” commands
Display the alarm threshold tables of a board
1) Display the Board view of the chosen board.
2) Choose the Board –> Alarm Threshold Configuration menu option:

The Alarm Threshold Configuration dialog box of Figure 108. appears.
3) In the Threshold table list, select the table.
4) Click on View or on Modify:

The Alarm threshold view dialog box of Figure 109. appears.
5) Click on Cancel to close the dialog box.
6) Back to the Alarm Threshold Configuration dialog box, click on Close to terminate.
Create an alarm threshold table
1) Display the Board view of the chosen board.

3) In the Threshold table list area, select an existing table from which the table being created will
be cloned.
There at least one default table.
1AA 00014 0004 (9007) A4 – ALICE 04.10
4) Click on Clone:
The Alarm threshold table cloning dialog box of Figure 109. appears.
3AL 89062 AA AA 255 / 926
926
5) In the Table name field, type in the name of the new table.
6) In the threshold fields type the new value for each threshold or use the little arrows.

7) Click on Clone to create the new table.

Back to the Alarm Threshold Configuration dialog box, the new table name appears in the
Threshold table list.
8) To assign the new table:
a) Select the table.

b) Click on Apply.
The new table is now assigned to the board types that are displayed in the Board type area.
9) Click on Close to terminate.
Modify an alarm threshold table
N.B. The default table and the current table can not be modified.
1) Display the Board view of the chosen board (i.e. Optical Amplifier or OMDX or OADM) .

3) In the Threshold table list, select the table to be modified.
If the table you want to modify is currently assigned:
a) Select another table.

b) Click on Apply to assign it in place of the one you want to modify.
c) Select the table you want to modify.
4) Click on Modify:
The Alarm threshold table modification dialog box of Figure 109. appears.
5) In the Table name field, you can type in a new name or leave the current one.
6) In the threshold fields type in the required value for each threshold or use the little arrows.
7) Click on Modify to validate the modification and close the dialog box.
8) Back to the Alarm Threshold Configuration dialog box, to assign the modified table:
a) Select the table.

b) Click on Apply.
The modified table is now assigned to the board types that are displayed in the Board type area.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 256 / 926
926
Assign an alarm threshold table
1) Display the Board view of the chosen board (i.e. Optical Amplifier or OMDX or OADM).
2) Choose the Board – Alarm Threshold Configuration menu option:

3) In the Threshold table list, select the table to be assigned.
4) Click on Apply.
The selected table is now assigned to the board types that are displayed in the Board type area.
Delete an alarm threshold table
N.B. The default table and current the table can not be deleted.
1) Display the Board view of the chosen board (i.e. Optical Amplifier or OMDX or OADM).
2) Choose the Board – Alarm Threshold Configuration menu option:

3) In the Threshold table list, select the table to be deleted.
If the table you want to delete is currently assigned:
a) Select another table.
b) Click on Apply to assign it in place of the one you want to delete.
c) Select the table you want to delete.
4) Click on Delete:
The Alarm threshold table deletion dialog box of Figure 109. appears.
5) Click on Delete to delete the table and close the dialog box.
Back to the Alarm Threshold Configuration dialog box, the name of the table disappears from
the Threshold table list.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 257 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 108. Alarm threshold configuration view (example)
Figure 109. Alarm threshold table modification (example).
258 / 926
7.9.7 Payload Configuration
Payload configuration: Display the current payload type, the regeneration type and the bit rate
Payload configuration procedure on 1686WM

1) Select a TWLA with FEC functionality , a TRFEC64 on 1686WM, or a MCC board on 1696WM
and display the view of the board.
2) Choose the Board –> Payload configuration menu option:

the Payload configuration dialog box of Figure 110. appears and displays the following setting
values.
3) Payload type is either SDH or Generic (unknown) payload:
– SDH, with 3R regeneration (FEC boards) and STM level = 16 or 4
– Generic (unknown) payload with 2R or 3R

• 2R regeneration : min and max rates are displayed.
• 3R regeneration : bit rate is displayed
4) Click on Cancel to close the window.
Configure the payload of an MCC board on 1696MS
2) Choose the Board –> Payload Configuration menu option:

The Payload Configuration dialog box is displayed.
3) In function of the MCC board type, perform one of the following action:
– MCC_SDH: in the STM level scrolling list, select the STM level.
– MCC_SYN: in the Bit rate scrolling list, select the bit rate.
– MCC_ASY: there is nothing to configure for this type of MCC board.
4) Click on OK the terminate.
Payload configuration on 1640WM
2) Choose the Board –> Payload Configuration menu option:

The Payload Configuration dialog box is displayed.
3) In function of the tributary board type, information concerning the payload type, the
regeneration, the STM level and/or the bit rate are displayed.
4) Click on Cancel the terminate.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 259 / 926
926
If FEC is enable
Otherwise Bit Rate is displayed
Figure 110. Payload configuration dialog box example
7.9.8 Current intantaneous measurements on 1696MS and 1640WM
Click on Current intantaneous measurements menu option of the Board menu.
This option opens a dialog box which displays the associated Instantaneous measurement values for the
associated board.
Many different measurements can be displayed for 1696MS and 1640WM. See the proper NE CT docs.
for the possible measurement list.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 111. Current Instantaneous measurements
3AL 89062 AA AA 260 / 926
926
Display the instantaneous measurements
1) Display the view of the board to monitor.

2) Choose the Board –> Current instantaneous measurements menu option:

The Current Instantaneous Measurements dialog box appears. The display is not dynamically
updated.
3) Click on Refresh to update the measurements values.
N.B. For 1696MS
For the MCC boards, the measurements values have an error margin of 1 dB.
For the OADM and OMDX boards, the measurements values have an error margin of 3 dB.
N.B. For 1640WM
For an EPM board, the Current Instantaneous Measurements are valid only if the EPM board
is connected to the OFA board.
In a WADM configuration, the Current Instantaneous Measurements board are not significant
for an EPM102 or EPM103 board.
The Current Instantaneous Measurements are not significant for the OST111 board.
In case of a RUTM, RUM or RUP alarm on a Tributary board, the Current Instantaneous
Measurements are not significant.
In WADM configuration, for the OFA111 and OFA312, the Current instantaneous
measurements menu option is accessible from the Equipment – Instantaneous
Measurement On – Selected Object menu option.
The Current Instantaneous Measurements of the Tributaries boards are different according to
the tributary type. In the following table shows the different kinds of values given by the Current
Instantaneous Measurements.
Input Transmit Side Output Transmit Side
TRB201/301 Display the real power value (dBm) Display the relative power value (dB)
TRB401 Display the real power value (dBm) Not displayed
TRB60x Not displayed Display the real power value (dBm)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 261 / 926
926
7.9.9 Optical Protection Configuration for 1696MS
The Optical Protection Configuration for OPC board has been described in the procedures of para.
15.11 on page 610.

The setting of the MCC_2 boards output power level, can be performed by mean of the following proce-
dure:
Set the output of an MCC_2 board
1) Display the board view of the MCC_2 you want to set.

The ALC & Optical power level configuration dialog box is displayed.
3) Set the pre–emphasis by using the up and down arrows.
4) Click on Apply.
Wait a few seconds for the effective setting of the board. During this process the command but-
tons of the dialog box are disabled.
7.9.10 OAC amplifier board output setting on 1696MS
The setting of the OAC boards output power level, can be performed by mean of one of the following proce-
dures:
– Set manually the output of an OAC board
– Set automatically the output of an OAC board.
Set manually the output of an OAC board
1) Display the board view of the OAC you want to set.
2) Choose the Board – Output Setting menu option.

The Output Power Setting dialog box is displayed.
3) In the Output Power: Man/Auto scrolling list select Manual.
4) Set the 1st stage output power value.
5) Set the 2nd stage output power value.
6) Click on Apply.
7) Click on Refresh to obtain the measures of the setting applied to the board.
Set automatically the output of an OAC board

1AA 00014 0004 (9007) A4 – ALICE 04.10
2) Choose the Board – Output Setting menu option.
3AL 89062 AA AA 262 / 926
926
The Output Power Setting dialog box is displayed.
3) In the Output Power: Man/Auto scrolling list select Auto.

4) Set the End Of Life Span value.

5) Set the Interstage Attenuation value.
6) Click on Apply:
7) Click on Refresh to obtain the measures of the setting applied to the board.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 263 / 926
926
7.9.11 Variable Optical Attenuator tuning on 1696MS
The setting of the attenuation applied to the WDM line signal at the entry of an OAC board, can be per-
formed by mean of one of the following procedures:

– Set manually the VOA tuning

– Set automatically the VOA tuning.
Set manually the VOA tuning
2) Choose the Board – VOA tuning menu option.

The Voa Setting dialog box is displayed.
3) In the VOA: Man/Auto scrolling list select Manual.
4) Set the Variable optical attenuator value.
5) Click on Apply.
6) Click on Refresh to obtain the measure of the setting applied to the board.
Set automatically the VOA tuning
N.B. You will need to watch to the COCE ”Calculated VOA out of range” alarm indicator
during this procedure. So better make it always visible on the screen.
2) Choose the Board – VOA tuning menu option.

The Voa Setting dialog box is displayed.
3) In the VOA: Man/Auto scrolling list select Auto.
4) Set the Number of channels.
5) Set the End Of Life Span value.
6) Click on Apply and check the COCE ”Calculated VOA out of range” alarm indicator on the OAC
board view.
Wait a few seconds for the VOA value calculation and the effective setting of the board. During
this process the command buttons of the dialog box are disabled.
7) Click on Refresh to obtain the measure of the setting applied to the board.
8) In function of the COCE ”Calculated VOA out of range” alarm status, proceed as follows:
– If the alarm does not raise, click on Close to terminate. The VOA setting is applied to the
OAC board.
– If the alarm raises, plug a 15 dB fixed attenuator at the VOA entry of the OAC board and
1AA 00014 0004 (9007) A4 – ALICE 04.10
click again on Apply.
3AL 89062 AA AA 264 / 926
926
7.9.12 Board menu options of 1686WM
7.9.12.1 Board Configuration with added channel configuration area

For the WLAs, MCC and OADM boards, a typical dialog box to set the board is displayed.
In the upper part of the dialog box, the user selects the board to be placed on the slot. According the chosen
board, some parameters may be requested.
Figure 112. Create, Modify Equipments screen example
• A list of channels: the number of channels to be selected depends of the type of board.
value = 1 for WLA, Value = 4 for OADM4 Value = 8 for OADM8
For OADM4_200 the user enters values of the set of channels used in the board.
For OADM4 and OADM8 (generic), the user enters each channel successively.
Values of available channel frequency are displayed for each board type.
When the selected board does not require this list, this one is greyed or not visible.
– If the field ”Associated board” is enabled, (in OADM case only) the operator can enter a board loca-
tion with the following informations:
1AA 00014 0004 (9007) A4 – ALICE 04.10
• the Rack number identification

• the Subrack number identification
• the Slot number identification
3AL 89062 AA AA 265 / 926
926
These informations are mainly needed for WLA used in OADM Repeater configuration. They show
the direction channel. They are declared in comparison to the fiber.
From the confirmation dialog box that opens you can confirm or cancel the operation using the Ok


– Click on the OK push button to validate the choice.
– The board representation appears on the NE view in the slot when the board change is effective.
A lock representation appears over the boards (”in–service”, see para. 7.2.2.4 on page 222.)
– In the Create/Modify dialogue box, the Cancel push button cancels the operation and closes the
dialogue box. The Help push button opens a Help view giving information about the context.
7.9.12.2 Optical power level configuration
This option set a value for the optical output power level of a board. The main boards using that feature
are:
• OXA types amplifiers used as Booster, Preamplifier, In–Line amplifier

• Expansion board
• TRFEC_64
• REGEN_10G
N.B. For the WLA TRFEC_64 board, the selected value corresponds to the preamphasis
activated to the board.
For example:
0 selected value, corresponds to an Output power of –11 dBm
10 selected value, corresponds to an Output power of –1 dBm.
N.B. For the Regen_10G board two fields must be set for preamphasis value, one for each
transmission side.
Conventionally Tx refers to Client ––> WDM side, Rx refers to WDM

––> Client side.
Pre–emphasis channel (dB): Transmission toward aggregate side

(Tx side A)
Pre–emphasis channel client side (dB) Transmission towards client side
(Tx side B)
Set the optical power level configuration
1) Display the Board view of the board to be treated.
2) Choose the Board – Optical power level configuration menu option:

the Optical power level configuration dialog box appears.
3) set the value to be affected:
4) Click on OK to valid and terminate.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 266 / 926
926
When 0 is selected the Output power is about –11 dBm

When 10 is selected the Output power is about –1 dBm
Figure 113. Pramphasis value setting example
7.9.12.3 Current Instantaneous measures
Display the current meaure values of the specified points of the board*.
Beware: *The Current Instantaneous Measurement option menu is also available from
boards SMEC, SER+ and DCC–AUX. There is no measurement on such board.
Figure 114. Board menu displayed examples
7.9.12.4 Laser Control for test:
– From the WLAs board menu, a Laser Control for test menu is available
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 115. Laser Control For Test Menu option
3AL 89062 AA AA 267 / 926
926
The Laser Control for test options are mainly used for test of the WDM optical line. The following options
are available:
• Forced ON

• Normal

• Forced OFF
Click on a option to set it in activate state.
A Forced ON or Forced OFF command, send an Abnormal Condition (AC) alarm on the Craft Equipment.
After this operation, set the laser in Normal state.
When a WLA_TR_FEC64 is selected the Laser Control for test option is available for the RX and TX side.
Figure 116. Laser Control For Test Menu option on a WLA_TR_FEC64 board.
N.B. For the Regen_10G:

the side A refers to TX (Client towards multiplex WDM)
the side B refers to RX (demultiplex WDM towards Client)
Set the Laser Control for test option
1) Display the board view of a WLA, TRFEC_64 or REGEN_10G board.
2) Choose the Board – Laser Control for Test menu option:
3) Activate the chosen option Forced ON or Normal or Forced OFF option (click on it)
N.B. The REGEN_10G is never in Shutdown. The ”Forced ON, Forced OFF” options menu is
useless.
4) When selecting again this menu, the current configuration is indicated by a tick in front of the
declared option.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 268 / 926
926
8 DIAGNOSIS
8.1 Alarms Surveillance

In this paragraph is described the access to the Alarm Surveillance information of the NE.
It is possible to show all the Alarms or filter the alarms report.
Select the Diagnosis pull down menu. You can then select the following option from the Alarms pull down
menu (see Figure 117. ):
– NE Alarms: all the NE alarms are listed in the Alarm Surveillance report which is
activated
– Object Alarms: only the alarms of the selected object are listed in the Alarm Surveillance
report
– Subtrees Alarm: only the selected object and the associated objects alarms are listed
in the Alarm Surveillance report
– Synchronization Alarms:only the alarms of the synchronization management are listed in the Alarm
Surveillance report
– Equipment Alarms: only the alarms of the equipment management are listed in the Alarm
Surveillance report
– Transmission Alarms: only the alarms of the transmission management are listed in the Alarm
Surveillance report
– External Points Alarms: only the alarms of the input external point management are listed in the
Alarm Surveillance report (not available for OMSG)
Figure 117. Example of Alarms menu

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 269 / 926
926
Selecting the NE Alarms a report is displayed. See the example on Figure 118.
The AS (Alarm Surveillance) view shows at the top a NE alarm synthesis followed by a detailed list of all
NE alarms.

Figure 118. NE Alarm Surveillance
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 270 / 926
926
Filtered alarm information will be shown selecting “Object Alarm” option or the other alarm view options.
Figure 119. Example of object alarm window
The AS supplies many useful information: the board in which the alarm is detected, the status of the alarm,
the alarm type, the probable cause.
Detailed description is given in the AS Operator’s Handbook.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 271 / 926
926
8.2 Event Log / Log Browsing
From the Network Element context views, perform the following operations to have access to the Event
Log file:

– In the Diagnosis pull–down menu, select the Event Log ... or the Log Browsing option according
to the USM type. The following logs are proposed:
Figure 120. Event Log / Log Browsing option in Network Element context view
The number of proposed “logId” depends on the Logs defined in the NE. In Figure 120. the first log
is referred to the occurred alarms while the second to the notification events ( protection switching
events, board configurations, ... ).
– Select the Alarm Log option (Log Id # 1 ) to access the relative filtered Alarm Log file as shown in
Figure 121. The SH reads the NE alarm log in real time and provides to visualize the last current
version.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 121. Alarm log file example
3AL 89062 AA AA 272 / 926
926
– Select the Event Log option (Log Id # 2 ) to access the relative filtered Event Log file as shown
in Figure 122. The SH reads the NE event log in real time and provides to visualize the last current
version.
Figure 122. Event Log file example
– Software Trace Log option, if available, is reserved to Alcatel personnel only. Selecting the
Software Trace Log command with the required filter, Figure 123. opens. The trace log file is a file
transfer then the visualized file can be different from the current version. Take care of displaying the
last version before checking the visualized data.
Figure 123. Trace Log file example
A detail event log description can be find on the ALMAP – ELM 5.X User’s Guide [5]. There are described
the filter panels and the different fields to fill in.
1AA 00014 0004 (9007) A4 – ALICE 04.10
8.3 View Remote Inventory
The View Remote Inventory option has been described in the chapter 7.8.1
3AL 89062 AA AA 273 / 926
926
8.4 Abnormal Condition (not available for OMSG)
The abnormal condition provides the synthesis of NE “not normal conditions” listinig the events that
contribute to abnormal condition. Select Diagnosis–>Abnormal Condition List (Figure 124. ).

Figure 125. opens.

Figure 124. Abnormal condition menu option
Figure 125. Example of abnormal condition list

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 274 / 926
926
The abnormal condition types are the following:
• Loopback
• ALS is disable and the laser is forced on or off

• Protection units (in case of EPS, SNCP, MSP, MS–SPRING) are in lockout or in forced status
• Board (or sub–board) is placed in a not configured slot
Select an abnormal condition entry and click on “OK” to open the relative dialog window. Figure 126.
opens.
Figure 126. Example of loopback dialog window management
The other types of abnormal condition will open the corresponding management window or will open
the suitable window to navigate towards the management window.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 275 / 926
926
The abnormal conditions icon is present in the right column of the equipment views (see Figure 127. ).

Abnormal Conditions alarm icon
Figure 127. Abnormal Conditions alarm icon
This alarm is highlighted if at least one abnormal condition occurs in the NE and is cleared when all
abnormal conditions are cleared.
An AC event will be visualized with an blue color icon.
The abnormal conditions are also logged as NE events in an ”Events Log” OS file.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 276 / 926
926
9 EQUIPMENT PROTECTION MANAGEMENT
9.1 Introduction
It is unthinkable to launch a telecommunications system, handling millions of communications, without the

possibility of replacing equipment in a real time way, consequent to equipment failure. Everything must
be done so that the communications can continue smoothly and so that the equipment failure remains
transparent to the users. Protection management deals with this aspect of the SH Manager.
The protection is performed by switching the equipment supporting the protected service, when this
equipment fails, to a protecting equipment capable of supporting the same service. This protection is
realized according to a protection scheme.
An equipment protection scheme is composed of the following parameters which can be configured (see
Figure 139. ):
• Group type: 1+1 or 1+n

the group type specifies if one or more unreliable resources for protection can be assigned to
one or more reliables resources. 1+1 group type means that a working element is protected by
one protecting unit. 1+n group type means that n working elements are protected by only one
protecting unit.
• Protection priority:
A priority can be assigned to protected units in 1+n protection schemes. This priority can be be
1, 2, ... or n, 1 being the highest priority.
• Configuration type: revertive or non revertive

In revertive mode, a protected service will be switched back to its protected element when it has
recovered from its failure.
In non revertive mode, the switch to the protecting element is maintained even after a recovery
from failure.
• Protection wait time to restore :

Used when revertive mode is active, the “wait time to restore” protection prevents several
protection switches due to an intermittent failure. A protected element must not be affected by
any fault during this fixed period of time before a protected service is switched back to it.
Board duplication remains the easiest way to ensure equipment protection in a system.
The actions that can be undertaken are of the following type:
– EPS Management,
– EPS Configuration,
– EPS Switching
These actions are only possible from the NE view and the Board view. In board view, the board whose
contents is represented is considered as implicitly selected.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 277 / 926
926
9.2 EPS Status (only available for OMSG)
Instead of the EPS Management option the user can select on OMSG, the EPS Status. The EPS Status
option performs the following operations:

1) Navigate to the Equipment view.
2) Select the EPS pull down menu. Then select the EPS Status... option as shown in the following
figure.
EPS
EPS Status...
Management...
Configure...
Switch...
–or–
3) Select the Configuration pulldown menu.
4) Select the EPS Status... option as shown in the following figure.
Configuration
...
Port Details...
EPS Status...
MSP Status...
The EPS dialog box of Figure 128. is opened.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 278 / 926
926
Figure 128. EPS Status Dialog Box
To display EPS protection groups:
– Use the drag and drop utility: it is possible to drag racks or subracks from the equipment overview
into the EPS Status Dialog.
– By clicking the Add Eqp button, the Equipment Filter dialog is opened as shown below.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 279 / 926
926
Figure 129. Equipment Filter Dialog Box
For a detailed description of this dialog box, refer to Chapter 6.3.
Depending on the selected filtering criteria, a list of EPS Protection schemes is displayed in the EPS status
dialog box. An example is shown in Figure 130. .
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 280 / 926
926
Figure 130. Example of an EPS status Dialog Box
– left column (+/–)

A “+” in front of a group marks it as being expandable (and therefore is reduced). To mark that a group
is expanded (and therefore can be reduced), a “–” is displayed in front of the group.
– Group
The name of the Protection group (protected and protecting boards).
– Board
The name of the Board
– Role
The role of the board (Protecting or Protected).
– USt. (Unit Status)
• A (Active)
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
P (Passive)
• AF (Active-Faulty)
3AL 89062 AA AA 281 / 926
926
• PF (Passive-Faulty)
– Switch Type

• NR (No Request)

• DNR (Do Not Revert)
• Auto-Fail (Auto Switch Equipment Fail)
• Auto-WTR (Auto Switch WTR)
• Manual (Manual switch)
• Forced (Force switch)
• Lockout (Lockout from switch)
– Lo. Nb
A number counting the protected protection units of one group being in lockout state
The data in column Unit State appears in different colors. Their meaning is:
– green: OK
protected units being active, protecting units being passive
– red: critical
any protection unit (protected or protecting) being active-faulty
– orange: major
any protection unit (protected or protecting) being passive-faulty
– cyan: indicative
protected units being passive, protecting units being active
Displayed additional boards to a protection without protection states are extension boards.
The EPS Status dialog reacts on notifications. If the protection states change, the EPS status dialog will
be updated.
It is possible to perform several commands on one or more selected Protection schemes:
– Expand/reduce
Those Protection schemes marked by a “+” in the left column (+/–) will be expanded and those
marked by a “–” will be reduced by clicking this button.
– Delete All
All existing Protection schemes will be deleted, even if no scheme is selected.
– Delete
The selected Protection scheme(s) will be deleted.
– Preferences...
Clicking this button opens the User Preferences dialog box. A detailed description can be found in
Chapter 3.7.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Add Eqp...
By clicking the Add Eqp... button, the Equipment Filter dialog is opened as shown in Figure 129.
(see description above).
3AL 89062 AA AA 282 / 926
926
– EPS Commands...
Clicking this button opens the EPS Switch dialog box. A detailed description can be found in Chap-
ter 9.5.
– Close
The configuration will be saved and the dialog box closed.
9.2.1 Navigation between views in the EPS status dialog
From the EPS status dialog box it is possible to see the Protection schemes in different views.
To see a protection in Board view, first select the desired protection in the EPS status dialog box and then
click Board View...
The EPS status dialog box remains open and the selected board is displayed in board view.
The EPS functional state of a board selected in the Board view is displayed at the bottom of this view as
shown in the following figures.
– Protection Role
• protected: the selected board is a protected board
• protecting: the selected board is the protecting board within the EPS
– Protection Status
• active: the board is currently active
• standby: the board is in standby state
– Switch Type
• no request: there is no request for switching
• forced: transmission is currently forced to the protecting board
• locked: the board is locked for switching
Protection Role Protection Status Switch Type
Figure 131. EPS Functional State from Protected Active Board View
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 283 / 926
926
Figure 132. EPS Functional State from Protecting Active Board View (Forced Protection is Active)
To display a protection in subrack view, first select the desired protection in the EPS status dialog box and
then click Subrack View...
The EPS status dialog box remains open and the selected board is displayed in subrack view.
The EPS functional state of a board selected in the subrack view is displayed on the subrack and in the
Message area. For a detailed description of the view, refer to Chapter 7.4. The common / dedicated I/O
boards are listed at the end of next para. 9.3.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 284 / 926
926
9.3 EPS Management
In order to consult the EPS management, perform the following operations:

– Select a transmission board in the Equipment view.

– Select the EPS pull down menu. Then select the Management... option as show in the following
figure.
N.B. A message–box indicating “Are not configured spare boards” is displyed when there are
not spare boards . A confirmation dialog box is opened when an EPS protection schema
is removed.
Figure 133. Consulting EPS
The following dialogue box is opened.
Figure 134. Example of EPS Management dialogue box

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 285 / 926
926
The EPS Management dialogue box shows the current NE protection schemes in the left side. The
list gives for each protecting board the protected board(s).
The right side of the dialogue box allows to modify the EPS configuration.

The CRU protection for many W/OMSN is automatically presented in the left side of the
dialog box when the SPARE CRU is created in the Set option of the Equipment menu. It is
not created with the EPS menu described in this chapter. (The same statement is
applicable to the MATRIX or SYNTH1N or other boards (see the proper CT Operator’s
Handbook)
The protection type, the protected and protection boards and the associated slot are reported in the proper
CT Technical and Operator’s Handbook. The summary table shown in Table 6. has been only reported
to show an example of NE equipment using USM 5.x and 6.x.
This right side is divided into two parts.
The upper part provides a message field with the name of the Protecting board and a choose button to
display the list of boards available.
The lower part provides a list to display the Protected boards currently in the displayed scheme.
A choose button is provided to display the list of boards which could be added as protected.
A delete button enables user to remove a protected board from a scheme.
a) Scheme displaying
To display a specific scheme, user selects an item on the left list.

This operation fills the protecting element text field and the protected list with the board user name. If user
clicks where there is no item displayed, the right part is displayed empty.
The Cancel push button closes the dialog box.
b) Scheme creation
To create a new protection scheme, don’t click on item in the left list.
In this way the right part is displayed empty and the Choose Protecting button is sensitive.
Press this button to displays a window to choose a board in the “Board Selection” list (see Figure 135. on
page 287). The board are listed opening the NE>rack>subrack levels.
After that operation, Choose Protecting button becomes insensitive and Choose Protected becomes
sensitive .
The user can add, always using the same “Board Selection” list dialogue box presented, as many
protected bitributary boards as wanted .
When the right part of window is correctly filled, the OK button close the dialog box and create the scheme
(the new list is update re–opening the EPS Management dialogue box).
The Cancel push button cancels the creation and closes the dialog box.
c) Scheme deletion
To delete an existing protection scheme, the user selects a scheme in the left list. Using the Delete button,
user could delete the scheme.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 286 / 926
926
d) Scheme modification
To modify an existing protection scheme by adding or removing protection units, the user selects a scheme
in the left list. Using Choose button for protected elements, user could add protected boards.
By selecting a protected board and using the Delete Protected button, user could remove protected
elements from scheme. When the right part of window is correctly filled, the OK button close the dialog
box and modify the scheme .
The Cancel push button cancel the modification closes the dialog box.
Figure 135. EPS: board selection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 287 / 926
926
The EPS functional state of a board selected in the board view is displayed at the bottom of the view as
shown in the following figures.
– Protection Role

• protected: the selected board is a protected board
• protecting: the selected board is the protecting board within the EPS
– Protection Status
• active: the board is currently active
• standby: the board is in standby state
– Switch Type
• no request: there is no request for switching
• forced: transmission is currently forced to the protecting board
• locked: the board is locked for switching
Protection Role Protection Status Switch Type
Figure 136. EPS Functional State from Protected Active Board View
Figure 137. EPS Functional State from Protecting Active Board View (Forced Protection is Active)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 288 / 926
926
Table 6. Examples of EPS–W/OMSN protection
Equipment Unit Protection type Slot main Slot Spare

(Protected) (Protecting)
1650SMC P4ES1N N+1 (N<=2) 7, 8 6, 7

R.2.0A/2.1/2.1B Revertive
1650SMC P63E1 N+1 (N=1) 6 7

1650SMC P3E3/T3 N+1 (N<=2) 7, 8 6, 7

1650SMC (SYNTH1/1N) N+1 (N=1) 9 10

R.2.0A/2.1/2.1B COMPACT Not Revertive
ADM–1
1660SM P4ES1N N+1 (N<=15) from 25 to 39 from 24 to 38

1660SM P63E1 or P63E1N N+1 (N<=6) 24,27,30,33,36,39 32

1660SM P3E3/T3 N+1 (N<=15) from 25 to 39 from 24 to 38

1660SM MATRIX 1+1 23 40

R.2.0A/2.1/2.1B Not Revertive
1650SMC R.2.1B ATM MATRIX 4x4 1+1 not fixed not fixed
1660SM R.2.1B (max 2 units) Not Revertive
1660SM R.2.1B ATM MATRIX 8x8 1+1 not fixed not fixed
(max 2 units) Not Revertive
1670SM R.3.0B P4ES1N N+1 (N<=15) from 25 to 39 from 24 to 38

Revertive
1670SM R.3.0B HCMATRIX 1+1 22 41

Not Revertive
N.B. For P3E3/T3 and P4ES1N of 1650SMC only one protection group N+1 revertive can be
created, while for the same units of 1660SM more than one protection group N+1 revertive
can be created. That depends on the equipment configuration.
The spare board position can be assigned in a flexible way. The only constraint are the
following:
• the access card corresponding to the protecting board must be an HPROT card
• the HPROT card has to be plugged at the left side of the access card group
• the main/spare boards have to be adjacent.
• the protecting board has to be plugged at the left side of the protected group of boards
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
the protecting/protected group of ports have to be of the same type
N.B. Note about HCMATRIX (on 1670SM R.3.0B): after switching it is necessary to wait about 15
minutes before having the operative conditions restored
3AL 89062 AA AA 289 / 926
926
Dedicated I/O Boards for OMSG:
– 1+8 STM-1 electrical / MUX2

– 1+7 IOB2 in IOS2

– 1+6 IOB45 in IOS45

– 1+4 ETB/IOB in IOS34 and IOS140
– 1+2 ETB in IOS2
– 1+1 Matrix, Control and Clock Generation and Distribution
Common I/O Boards for OMSG:
– 1+14 STM-1 electrical I/O board

– 1 : 14 STM-1 electrical I/O board
– 1+6 2 Mbit/s I/O board
– 1+4 34 Mbit/s I/O board
Fot more detail info. see the proper CT Technical and Operator Handbook.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 290 / 926
926
9.4 EPS Configuration (not available for OMSG)
This functionality configure Revertive and Wait Time to Restore in a protection scheme.
In order to configure, perform the following operations:

– Select a Protected or Protecting board in the Equipment view.
– Select the EPS pull down menu. Then select the Configure option as show in the following figure.
Figure 138. EPS menu
Figure 139. Example of an EPS configuratiuo window

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 291 / 926
926
The dialog box shows the following EPS data configuration:
– the label name of the protecting element

– the Equipment type as a label of the protecting element

– a list displaying the protected elements owned by the scheme
– the setting Revertive Mode option: Revertive and Non Revertive.
– the setting wait time to restore value (steps of 30 seconds, from 60 to 600). Only for N+1 EPS. Fxed
to 5 minutes on OMSN of the current SH release.
When the configuration of the equipment protection scheme is completed confirm closing the dialog box
by clicking on the OK push button. The Cancel push button cancels the configuration and closes the dialog
box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 292 / 926
926
9.5 Switching EPS
This functionality enables to force a protecting board to work even if there is not failure.
The forced switch will fail if the other equipment is already forced switched or if the protecting equipment
has a failure condition.
N.B. During Port Switch Over, MSP protection operation and equipment protection, TPs get
re-located physically from one board to another. The name of the TPs are logical names as
defined by ITU standards and persist during their life time. As a consequence, the moved TP
still contains the address of the old containing board in its name. Therefore, the TP name cannot
be used to find out, on which board the TP is implemented for TPs involved in Port Switch Over,
MSP protection operation and equipment protection. To find out, on which board the TP actually
is implemented, mark the TP in the Port or Transmission view and navigate to the related board
with menu item Show supported board.
In order to switch an EPS, perform the following operations:
– Select a transmission board in the Equipment view.

– Zoom down to Board view.
– Select the EPS pull down menu. Then select the Switch option as show in the following figure.
EPS
Management...
Configure
Switch
Figure 140. Switching EPS

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 293 / 926
926

Figure 141. Example of EPS Switch dialogue box
This dialogue box displays in its left part the EPS of the selected board.
From this dialogue box the operator can configure, a Force to, a Manual to or a Lockout switch by clicking
on the desired radio button. The enabled commands (bold visualized) depend on the selected NE type.
– By clicking the button Force to Protecting, the protection board is forced to protect the selected
board regardless of any signal quality aspect. The button Force to Protected initializes the same
action, despite the contrary label.
– The Manual to command perform the “manual” switch, active only if the other board is not alarmed.
– The Lockout switch disables protection switching for the selected board.
– The Release radio buttons allow to cancel the force or the lockout action and re-enables automatic
protection.
Clicking on the OK push button initiates the switch and closes the dialog box. The Cancel push button
cancels the operation and closes the dialog box.
N.B. Operations which are not supported by the Q3NEs are rejected with the misleading error
1AA 00014 0004 (9007) A4 – ALICE 04.10
message “Due to a communication problem with this network element, the operation you
requested could not be completed. You may retry the operation later.”.
3AL 89062 AA AA 294 / 926
926
In the current SH release, only the Lockout and the Manual options can be applied to W/OMSN.
N.B. On 1670SM R.3.0B after switching of HCMATRIX board it is necessary to wait about 15
minutes before having the operative conditions restored.
The following restrictions has to be applied to OMSG for Force to Protecting:
– No forced switch is provided for Common I/O Boards. A switch can be triggered by unplugging the
related board, causing a traffic hit of about 500 msec.
– It is not possible to invoke a forced protection switch on P63E1 boards. Performing the action will be
rejected with the following error message:
Due to an invalid argument value, the operation you requested could not be completed.
– Before forcing traffic to the protecting Dedicated I/O Board, make sure there is no other protection
(e.g. an automatic switch from another board) active on the protecting board.
Otherwise the switch will fail, causing the following error message:
Due to an invalid argument value, the operation you requested could not be completed.
N.B. For OMSG supported in SH current release, a manual EPS of the Matrix board is hitless only
if the system is tracking an external timing source. If it is in holdover mode, the manual switch
may not be hitless.
N.B. For 1674 LG Square configuration, a manual EPS of the Matrix board is hitless only if the
system is tracking an external timing source. If it is in holdover mode, the manual switch may
not be hitless.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 295 / 926
926
9.6 EPS Overview (not available for OMSG)
EPS Overview allows to display as well as search for EPS states.

Selecting the EPS Overview option from the Configuration pull down menu Figure 142. opens

Figure 142. EPS overview
To Search the EPS groups two different ways of filtering are supported; a filtering for all protection units
located on a dedicated Board Type as well as a filtering for protection units carrying a specific Status.
The search criteria can be chosen with the help of a combo box:
– Board Type: allows to filter for the EPS protected boards; the following filters values should be
offered for 1650SMC (example):
• Ignore
• SYNTH1
• SYNTH1N
• P3E3/T3
• P63E1
1AA 00014 0004 (9007) A4 – ALICE 04.10
• P63E1N
• P4ES1N
3AL 89062 AA AA 296 / 926
926
– Status: allows to filter for all possible EPS protection states;the following filters values should be
offered (examples):
• Ignore
• Normal
• DNR
• Auto–Fail
• Auto–WTR
• Manual
• Force
• Lockout
After the filter selection click on Search button to start; the field below the Search button will be updated
(see Figure 143. )
Figure 143. EPS overview after Search (Example)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 297 / 926
926
Each protection unit is presented with the following information:
– Protection Group (example protection GroupId, 10)

– Board Id (example r01sr1/board#9 )

– Board Role:
• Ped (Protected)
• Ping (Protecting)
– B Status (board status):
• A (Active)
• S (StandBy)
• F (Faulty)
– Protection Status: defines the current state of the protection unit as follow
• Normal
• Auto–Fail (Autoswitch Equipment Fail)
• Auto–WTR (Autoswitch Wait Time to Restore)
• Force (Force switch)
• Lockout
The colors used for each row have the following meaning:
– Green (OK): for protected protection units active
– Red (Critical): for protected protection units in fail condition, protection unit in lockout or active
on autoswitch or commands
– Orange (Major): for protected units in standby after a command and protecting protection unit
in standby for autoswitch or commands
– Cyan (Indicative): for protecting protection unit active and no fail condition present in the schema
(Do Not Revert State)
At the bottom of the EPS Overview windows are available five button that allows to navigate through the
EPS management views and subrack view, board view.
In this way the operator has a quick link towards the views showing the correlation between the alarms
and the protection states.
N.B. Before to click on one of the five buttons select a row

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 298 / 926
926
The buttons available are:
– Open Subrack View: opens the Subrack view showing the protection states with icons on the
boards (see Figure 144. )
The possible protection states and the relevant symbols are explained in
the following:
Symbol EPS protection status
No Request
Do not Revert
Lockout
Auto Switch (WTR, Fail)

Manual
Forced
– Open Board View: opens the board view showing the alarm and the board administrative
states (see Figure 145. )
– Open Commands: opens the EPS Switch dialog box. See Figure 141. on page 294 and the
relevant description.
– EPS Management: opens the EPS Management dialog box. See Figure 134. on page 285
and the relevant description.
– EPS Parameters: opens the EPS Configuration dialog box. See Figure 139. on page 291
and the relevant description.
For more details see chapter 7.4
Click on Close button to exit from the EPS Overview window

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 299 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 145. Example of board view after “Open Board View” command
Figure 144. Example of subrack view after “Open Subrack View” command
300 / 926
10 MULTIPLEX SECTION PROTECTION MANAGEMENT
10.1 Architecture types

The Multiplex Section Protection is the connection between two NEs protected by a cable and port
duplication. At the source the signal is duplicated and sent to the sink via two independent cables. When
a multiplex section failure occurs, the system switches to the other cable and port.
The MS Linear Trail Protection can be applied to any Q3NEs ( W/OMSN and OMSG ) where it is possible
to configure a linear APS (single ended/dual ended) line protection. For these NEs the APS can be applied
only to STM–N optical ports (see Table 7. ).
The max number of (aggregates and tributary) ports that can be protected depends on the NE
configuration type.
Linear APS operates at line and unit level, software detecting hardware internal and line failures.
The switching criteria are : Signal Failure ( SF=Loss of Signal, Loss of frame, MS–AIS, Excessive BER)
and, with software setting, Signal Degrade ( SD ).
Linear APS can be revertive or not revertive. For the Q3NEs managed by the current SH release the
1+1 protection type is not revertive .
Architecture 1+1 or N+1 Standard

Described in ITU–T Rec. G783/G841. The refence switching criteria are SF and SD. It provides a
k1/k2 communication protocol thus this protection can be single or dual ended.
Architecture 1+1 Proprietary
The refence switching criteria are SF and SD. No k1/k2 communication protocol is provided thus
this protection can be only single ended.
Architecture 1+1 Optimized
This protection type uses the NTT protocol not the ITU / ETSI protocol. The role of protected and
protecting port is exchanged after a protection switch.
Architecture 1 : 1 Standard
Described in ITU–T Rec. G783/G841 as architecture 1 : n ( with n=1 ). The refence switching criteria
are SF and SD. It provides revertive mode managed by k1/k2 protocol and thus this protection can
be single or dual ended. The spare interface can be used to transport “low priority traffic” .
The APS 1 +1 feature permits a 1+1 protection in a linear link, where a path signal is protected by another
dedicated path carrying the same signal. The protection can be set both in single and in dual ended mode.
In single ended mode the protection is accomplished by switching only the signal affected by the failure.
In dual ended mode the protection is accomplished by switching both the affected and the unaffected
signals.
The switching signalling is carried over the APS channel (K1 and K2 bytes), using the K–byte protocol.
Figure 146. page 304 shows an example of linear single ended 1+1 protection and the case of signal
switching after an unidirectional failure on the main link (FERF=Far End Receive Failure, APS=Automatic
Protection Switching). Note: the FERF signal is actually called MS–RDI =Remote Defect Indication.
Figure 147. page 304 shows an example of linear dual ended 1+1 protection and the case of signal
switching after an unidirectional failure on the main link.
The WTR time represents the delay time, after a SF or a SD condition, before to confirm that the failure
indication has been restored. It is used to maintain the (alarm) state (or bridge/switch in a revertive
configuration) during the WTR period unless it is preempted by a higher priority command.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The WTR Time is editable from 0 sec. to ... secs. The WTR time functionality depend on the NE type: see
the NE CT relevant operator manual to get the correct info.
3AL 89062 AA AA 301 / 926
926
Signal Degrade (SD) software setting enables the MSP protection mechanisms when a SD is recognized
on the working port. The SD threshold reference value depend on the NE selected threshold on the MS
termination point. This threshold value is configured as explained in the “Port View” chapter.

NEs 1+1 N+1 1+1 1:1 1+1
Standard Standard Proprietary Standard Optimized
1664SM R.3.1
1664SM R.3.2
1664SM R.3.3
STM–N (N=1,4) trib
single, ended X
STM–16 Agg.
single ended X
STM–N (N=1,4)
trib dual ended X
STM–16 Agg.
dual ended X
1664SM R.3.2
1664SM R.3.3
STM–N(N=1,4)
trib dual ended X
1640SM R.2.1B
STM–N (N= 1,4)
single, dual ended X
1650SMC R.1.1
1650SMC R.2.0 /2.1/
2.1B
STM–N (N=1,4)
dual ended only X
1660SM R.1.1
1660SM R.2.0 /2.1/2.1B
STM–N (N= 1,4,16)
1670SM R.2.0/3.0
STM–N (N= 1,4,16,64)
1670SM 3.0.B
STM–N (N= 1,4,16,64)
single, dual ended X X
Table 7. APS for OMSN

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 302 / 926
926
The OMSG supports linear, non-revertive APS, only to ports of optical STM-N boards, with the following
protection schemas:
– 1+1 Standard (single and dual ended)

Described in ITU-T Rec. G783/G841. The refence switching criteria are SF and SD. It provides a
K1/K2 communication protocol.

– 1+1 Optimized (dual ended)
This protection type uses the NTT protocol not the ITU / ETSI protocol. The role of protected and
protecting port is exchanged after a protection switch.
N.B. If APS 1+1 Optimized is set for STM-1 signals of Common I/Os, an error message occurs.
With the scheme APS 1+1, it is possible that the ports are displayed with wrong labels (one
end of the same path is labeled working and the other is labeled protecting). This happens
when the schema is not started from the standard schema and both ends have different
labels at the start of the dual ended schema.

( *5 7 7 7
( *56 7 7 A
( *> 7 7 A
Table 8. APS for OMSG

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 303 / 926
926
Single ended 1+1

1

MAIN MAIN
2
1
SPARE SPARE
2
a) Normal conditions
APS SWITCH
1
MAIN MAIN
2
FERF
1
SPARE SPARE
2
b) Unidirectional failure
Figure 146. Linear 1+1 single ended protection
Dual ended 1+1
1
MAIN MAIN
2
1
SPARE SPARE
2
a) Normal conditions
APS
1 SWITCH
MAIN MAIN
2
APS
1
SPARE SPARE
SWITCH 2
b) Unidirectional failure
Figure 147. Linear 1+1 dual ended protection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 304 / 926
926
10.2 MSP Create (not available for OMSG)
Select the NE and click on the Equipment View.

Click on Rack–>Subrack and then select the Board to configure ( an aggregate or a tributary ).
Click on the Board to open the Port icon and on the Port icon to open the “Port” menu.
Select MSP icon to enable the MSP options and select the MSP Create command from the USM menu
commands reported on chapter 2.
Figure 148. Example of MSP Menu Options ( USM 3.1.. menu)
Select “MSP Create” to open the MSP Schema Creation ( Figure 149. ).
N.B. For 1670SM R.3.0B see para. 10.2.1

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 305 / 926
926
Figure 149. MSP Schema Creation on W/OMSN R.2.1B
Type the editing “Ports” fields or select the “Choose Port” button to define the Protected Port and
Protecting Port units. Clicking on the “Choose Port” buttons Figure 150. opens.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 306 / 926
926
Figure 150. TP Search
Select the Rack–Subrack and Board ( Protected / Protecting ) on the Equipment window to open the
TPs window. Choose the TP available in the termination points list (OpS/EIS, RST, MST, MSP) and then
click twice on the chosen TP or click on the OK button. The detail information of the TP search is reported
in the “Transmission View” chapter 14.4.
Click on the OK button and repeat the operation for “Protected” and “Protecting” ports both. If it has been
selected a Protected/Protecting port configured in a previously MSP schema protection an error message
of access denied will be appear on the screen.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Configure the MSP protection schema with the chosen protection schema and enter the related schema
parameters. At the end click on the OK button to configure the MSP protection schema. An error message
will be appear if the selected schema is not supported by the NE.
3AL 89062 AA AA 307 / 926
926
10.2.1 MSP creation on 1670SM R.3.0B
Select the MSP Create option from the Port –> MSP menu (see Figure 148. on page 305) to open the
MSP Schema Creation (see Figure 149. on page 306).

Figure 151. MSP Schema Creation on 1670SM R.3.0B
Are supported in this release two MSP Protection Schemas:
• MSP 1+1 standard

• MSP N:1 standard
Select one and then click on Add Port button in the Ports field to create a MSP schema.
Figure 152. on page 309 is opened.
Following steps are necessary:
• choose Port
• select a Port Role (protected or protecting)
• define Channel Id (mandatory for MSP N:1)
• define SDH Priority (type of traffic, High or Low)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 308 / 926
926
Figure 152. MSP schema creation – Port dialog
Select the Choose Port button to define the “Protected Port” and “Protecting Port” units.
Figure 150. on page 307 is opened.
Click on Rack–Subrack and select the Board (Protected / Protecting) on the “Equipment” window (left
side).
The “termination Points” list (right side) is available.
On this right side select the OpS TP of the chosen board and then click on the OK button. It is possible
to select the board through the “Board History” button selecting the board list menu.
The “Filter Section” is divided into different fields. It permits to visualize a reduced TP Class. If used, OpS
class must be selected. The complete TP research description is reported in the “Transmission View” para.
14.4 on page 508.
Click on the OK button and repeat the operation for both “Protected Port” and “Protecting Port”. If it has
been selected a Protected/Protecting port configured in a previously MSP schema protection an error
message of access denied will be appear on the screen.
In the dialogue of Figure 149. on page 306 also configure the MSP protection schema with the chosen
Protection Schema and enter the related Schema Parameters according the following rules:
• 1+1 Standard can be dual–ended or single–ended, Not Revertive

• N+1 Standard can be dual–ended or single–ended, Revertive
Decide if enable the MSP protection mechanisms when a Signal Degrade is recognized.
At the end click on the OK button to confirm the MSP protection schema configuration. An error message
will be appear if the selected schema is not supported by the NE.
In Figure 153. on page 310 and Figure 154. on page 310 are shown two examples of MSP schema
creation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 309 / 926
926
Figure 153. MSP 1+1 standard protection schema (example) on 1670SM R.3.0B
Figure 154. MSP N:1 standard protection schema (example) on 1670SM R.3.0B
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 310 / 926
926
10.3 MSP Management
The MSP Schema Configuration dialog shows the current state of the MSP schema, settings and state
(protected or protecting) of the current SDH-n port.
This dialog allows to set the configuration parameters for the designated multiplex section:
– Protection Schema reported in the previous para.10.1 (Table 7. and Table 8. )
– Dual Ended / Single Ended protection switch and directionality described in the previous para.10.1
– Revertive mode (not supported: always Non Reverted allows)
– enabling/disabling SD switch (disabling SD not supported on the OMSG).
• on OMSG, Signal Failure (SF) and Signal Degrade (SD) are specified as fixed criteria for MSP
and SNCP/N switching.
If the operator does not want to switch due to bit/block errors, he should configure the SD
detection threshold to a very high value (e.g. 500). For this configuration, the SD detection is
very unlikely. Normally for such bad signals a defect (LOP, LOF) is detected and will raise
switching.
• on OMSN, by default, SF is used as a switching condition. Use Enable Switch on SD to switch

also at a degraded signal.
Figure 155. MSP Schema Configuration on OMSG

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 311 / 926
926
Ports (on OMSG)
– Protected Port:
The location of the board hosting the protected port is displayed. The respective board is predefined:

boards 1–4 of IOS155-O are protected by boards 6–9 of the same subrack. In case of dual-ended

NTT MSP the protection role can change.
– Protecting Port:
The location of the board hosting the protecting port is displayed. The respective board is predefined:
boards 6–9 of IOS155-O are configured as protecting boards.
Figure 156. MSP Schema Configuration on OMSN
Protection Status (on W/OMSN)
This column displays the status of both the Protected and Protecting Port.
The following states are indicated:
– No Request (green)
– Do Not Revert (light blue)
– Forced (orange)
– Manual (orange)
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Lockout (orange)
– Auto. Switch (orange)
3AL 89062 AA AA 312 / 926
926
– Protection Fail (due to Failure Of Protocol) (orange)
Protocol Status (on W/OMSN)

Displays the Protocol Status.

– Uni/Bid Mismatch
Check if near end and far end communicate using the same protocol. Two different indications are
possible:
– OK (green color)
– n case of a mismatch, an Uni/Bid Mismatch (orange color) is displayed
– Plus/Colon Mismatch
Check of the MSP architecture type (Bit 5 of the K2-Byte). Two different indications are possible:
– OK (green color)
– In case of a mismatch, an FOP (Failure Of Protocol) (orange color) is displayed.This situation occurs
when a 1 + 1 architecture is connected to 1:1 architecture.
– The WTR Time (Wait To Restore) is the delay time for switching protection and protecting port after
recovery from failure / defect. In general this time is selectable in steps between 60 to 600 seconds
on OMSG but is fixed to 300 seconds on W/OMSN (see the proper NE–CT Manuals for the right
indication).
Configure the MSP protection Schema with the chosen protection schema (see Table 7. and Table 8. )
and enter the related schema parameters. At the end click on the OK button to configure the MSP
protection schema. An error message will be appear if the selected schema is not supported by the NE.
On OMSG (see Figure 155. )
– To configure more than only one TP, click on the Tp list button and open the Clipboard dialog. For
a description of this dialog see Chapter Clipboard. Press Apply to apply the parameters and leave
the dialog box open or OK to apply the parameters and close the dialog box or Cancel to close the
dialog without saving the changes.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 313 / 926
926
Figure 157. MSP Management view on 1670SM R.3.0B
10.3.1 MSP modification
The same MSP Management option can be used to modify the schema parameters of an active MSP
configuration.
Before changing a single ended schema into a dual ended one, all active switches must be cleared
(manual switch, lockout,... ). If the operator wants to change the protection schema architecture or the
ports involved in the MSP schema, the current schema must be removed and re–created.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 314 / 926
926
10.4 MSP Delete (not available for OMSG)

Click on Rack–>Subrack and then select the Board to delete the MSP Schema Configuration ( an
aggregate or a tributary ).
Select the MSP Delete command from the USM menu commands reported on chapter 2.
Figure 158. opens
Figure 158. MSP Schema Deletion example
Click on “OK” button to delete the selected MSP Schema Configuration
N.B. On 1670SM R.3.0B will be visualized the MSP window of Figure 157.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 315 / 926
926
10.5 Display of Protection State
The MSP protection state of a port is displayed at the bottom of the Port view. Some examples are reported
in Figure 159.

The following states are always displayed:
Port Status (on W/OMSN) or MSP State (on OMSG) – Active (red color) or Standby (orange color).
The active protection status is referred to a protected/protecting port ( where the traffic is
transported): when a failure is detected, the protecting port is ready to save the traffic (and becomes
active). The standby protection status is referred to a protecting/protected port that is ready to save
the traffic. If a low priority traffic is transmitted on the protecting port (1:1 configuration ) the protection
status becomes “Active” (red) also for this port. When a command is performed the Active status
indication shows where the command is applied.
N.B. For the NTT protocol (APS 1+1 Optimized available on OMSG) the display of the MSP State
is not correct in case of
– lockout after a forced switch to protecting
– lockout during wait to restore time
The working section is displayed as active although it is standby.
MSP Protection Role (on W/OMSN) or MSP Role (on OMSG) – Protected (green color) or
Protecting (ochre color). The protection role depends on the selected port type (Protected /
Protecting).
MSP Group (on OMSG) – (green color) Indicates the state of the protection group the currently
displayed port belongs to. The status indications are:
– Auto: traffic is currently switched automatically due to signal failure (SF), signal degraded (SD) or wait
to restore (WTR).
– Do Not Revert: there is no switch request, protection is active
– Forced: traffic is currently switched due to a forced switch request
– Lockout: the port is locked for switching
– Manual: traffic is currently switched due to a manual switch request
– No Request (default): there is no request for switching
– Protecting: Fail (due to a failure – SF indication – on the protecting unit)
– Protection Fail: switch was caused by SF / SD condition on the protection section (because the MSP
protocol is running on the protection section at all the so called “Failure of Protection” (FPS) has a
higher priority than the manual/forced switch).
The following states, on OMSG, are only displayed if their values differ from the default (NR) one:
MSP Group Status, MSP Own Unit and MSP Related Unit – (green color) Displayed if an automatic
switch is requested. “Own Unit” stands for the currently displayed unit in the port view, “Related Unit”
stands for the related unit of the same protection group . The status indications are:
NR: (abbreviation of No Request); normal, idle condition, the traffic is on the main port
DNR:(abbreviation of Do Not Revert); the SF or SD have been recovered but the traffic is
switched on the spare port
PF: a protection failure has been detected on the port
RF: a release command has been failed
FOP: a failure of protocol has been detected
1AA 00014 0004 (9007) A4 – ALICE 04.10
complete: = the bridge/switch actions are completed

pending: = the bridge/switch actions are pending
The “complete” and “pending” indications precede the following statuses:
3AL 89062 AA AA 316 / 926
926
AS: automatic protection switching enabled
MS: a manual local protection command has been activated
FS: a forced local protection command has been activated
LO: a lockout local protection command has been activated
SF/SD: Signal Failure or Signal Degraded has been detected

WTR: wait time to restore status
MSP Request Source – (green color) indicates where the operator commands (force/manual/lockout)
have been performed. Only present when a command is operative.
– Local: switch due to near end SD/SF or local user switch command
– Remote: switch due to received K1/K2 bytes.
A remote switch cannot be released locally, but can be overwritten by a switch with higher priority.
MSP Protocol Status
This parameter indicates the current APS Protocol status.

The following values are possible:
– OK (orange color)
– Failure (in case of FOP) (ochre color)
MSP statuses displayed in a normal conditions
MSP statuses displayed after an automatic protection switching
MSP statuses displayed after a forced command

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 159. MSP Protection Status Examples
3AL 89062 AA AA 317 / 926
926
Figure 159. represents a MSP configuration with a normal condition, with an automatic protection
switching and with a forced command. In any situation are represented the statuses displayed on both
protected/protecting Port views. The Active status indication, with a forced command on the protecting
group, shows where the forced command is applied.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 318 / 926
926
10.6 MSP Commands

Click on Rack–>Subrack and then select the Board involved in the MSP Schema Configuration ( an
aggregate or a tributary ).
Select the MSP Commands option from the USM menu commands reported on chapter 2. to open
Figure 160.
Protecting Port : the location of the board hosting the protecting port is displayed.
Protected Port : the location of the board hosting the protected port is displayed.
The lockout of protection command denies working channel access to the protection section (Protecting)
by issuing a “Lockout” of protection request (on the “Switch Type” of MSP Management).
The “Force to” command switches the working channel ( Protected port ) to the protection section
(Protecting port), unless an equal or higher priority switch command is in effect or SF condition exists on
the protection section, by issuing a “Forced” switch request for that port (on the “Protection Status” of
MSP Management). It is also possible to switch back to the working channel using again the “Force to”
Protected port command.
For 1+1 non–revertive system, forced switch command, applied on the working section (Protected port),
transfers the working channel back from protection section (Protecting port) to working section, unless an
equal or higher priority request is in effect. Since forced switch has higher priority than SF or SD on working
section, this command will be carried out regardless of the working section condition.
In single ended mode this command is executed unconditionally. In dual ended mode only when the “Force
to” conditions are respected.
The “Manual to” command switches the working section ( Protected port ) to the protection section
(Protecting port), unless a failure condition exists on the protection section or an equal or higher priority
switch command is in effect, by issuing a “Manual” switch request for that port (on the “Protection Status”
of MSP Management). It is also possible to switch back to the working section using again the “Manual
to” Protected port command.
For 1+1 non–revertive system, manual switch command, applied on the working section (Protected port),
transfers the working channel back from protection section (Protecting port) to working section, unless an
equal or higher priority request is in effect. Since manual switch has lower priority than SF or SD on working
section, this command will be carried out only if the working section is not in SF or SD condition
The Clear WTR comand cancel the wait to restore time after a failure/defect recovering. It is not operative
in the current SH release.
The “Exercise” command issues an exercise request for protection section (Protecting port) and checks
responses on MSP bytes, unless the protection section is in use. This check controls the k1/k2
communication protocol functionality to be sure that the protocol is right also on the protection section.
Actually the”Exercise” command is not operative in the current SH release.
The “Release” command clears all previously switching commands.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 319 / 926
926
Figure 160. MSP Commands
re-located physically from one board to another. The names of the TPs are logical names as
MSP protection operation and equipment protection.
To find out, on which board the TP actually is implemented, mark the TP in the Port or Transmission View
and navigate to the related board with the menu item Show supported board.
The priority levels for the MSP commands are (from the higher to the lower one): Lockout, Force to,
Auto–switch (SF), Auto–switch (SD), Manual to, WTR, Exercise, No Request. Table 9. gives the priority
rules when are occurred two different commands. The first column on the left and the first row at the top
report the switch protection and the external MSP commands. The row/column crossing gives the
command or protection result.
Table 9. MSP commands and Auto–switch protection priority
Lockout of Forced to Auto–switch Manual to

protection
Lockout of –––––––––– Lockout Lockout Lockout

protection
Forced to Lockout –––––––––– Forced Forced
Auto–switch Lockout Forced ––––––––––– Auto–switch
Manual to Lockout Forced Auto–switch –––––––––––

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 320 / 926
926
10.7 MSP overview (not available for OMSG)
MSP Overview allows to display as well as search for MSP states.

Selecting the MSP Overview option from the Configuration pull down menu Figure 161. opens
Figure 161. MSP overview
To Search the MSP groups two different ways of filtering are supported; a filtering for all protection units
located on a dedicated Board Type as well as a filtering for protection units carrying a specific Status.
The search criteria can be chosen with the help of a combo box:
– Board Type: allows to filter for the MSP protected boards; the following filters values should be
offered for 1660SM (examples):
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 321 / 926
926
Figure 162. Board examples
– Status: allows to filter for all possible EPS protection states;the following filters values should be
offered (examples):
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 163. Status examples
3AL 89062 AA AA 322 / 926
926
After the filter selection click on Search button to start; the field below the Search button will be updated
(see Figure 143. )
Figure 164. MSP overview after Search (Example)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 323 / 926
926
Each protection unit is presented with the following information:
– Protection Group (example protection GroupId, 121)

– Port Id (example r01sr1sl29/port#01–EIS )

– Role:
• Ped Protected
• Ping Protecting
– Status (board status):
• A (Active)
• S (StandBy)
• F (Faulty)
• ET Extra Traffic (Not operative)
– Protection Status: defines the current state of the protection unit as follow
• NR (Normal)
• Auto–SF (AutoSwitch Signal Fail)
• Auto–SD (AutoSwitch Signal Degrade)
• Auto–WTR (AutoSwitch Wait Time To Restore)
• Manual (Manual Switch)
• Force
• Lockout
• APS Invalid (Protection fail condition APS invalid)
• Bad channel (Protection fail condition Channel Mismatch)
The colors used for each row have the following meaning:
– Green (OK): for protected protection units active
– Red (Critical): for protected protection units in fail condition, protection unit in lockout or active
on autoswitch or commands
– Orange (Major): for protected units in standby after a command and protecting protection unit
in standby for autoswitch or commands
– Cyan (Indicative: for protecting protection unit active and no fail condition present in the schema
(Do Not Revert State)
At the bottom of the MSP Overview windows are available five button that allows to navigate through the
MSP management views and to open the Port View.
By clicking on Open Port View the operator has a quick link towards the view showing the correlation
between the alarms and the protection states.
N.B. Before to click on one of the five buttons select a row

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 324 / 926
926
The buttons available are:
– Open Port view: opens the port view showing the correlation between the alarm and the MSP
protection states. See Figure 165. on page 325.
– MSP Create: opens the MSP Create dialog box. See Figure 149. on page 306 and the
– MSP Delete: opens the MSP Delete dialog box. See Figure 158. on page 315 and the
– MSP Management: opens the MSP Management dialog box. See Figure 155. on page 311 and
the relevant description.
– MSP Commands: opens the MSP Commands dialog box. See Figure 160. on page 320 and the
Click on Close button to exit from the EPS Overview window

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 165. Port view after “Open Port View” command
3AL 89062 AA AA 325 / 926
926
10.8 MSP Status (only available for OMSG)
Port/Transmission

...
MSP > MSP Management...
...
MSP Commands...
MSP Status...
This dialog can also be displayed from the configuration pulldown menu. It allows to display and execute
protection commands on MSP ports.
Figure 166. MSP Browser
To display protection groups it is possible:
– to use the drag and drop utility: drag any rack, subrack or board from the Equipment Overview into
the MSP Status dialog.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– By clicking the Add Tp... button, the TP Search dialog is opened as shown below.
3AL 89062 AA AA 326 / 926
926
Figure 167. TP Search Dialog Box
For a detailed description of this dialog box, refer to Chapter 14.4.
Depending on the selected TP, a list of MSP Protection schemes is displayed in the MSP Browser dialog
box. An example is shown in Figure 168. .
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 327 / 926
926
Figure 168. Example of an MSP Browser Dialog Box
– left column (+/–)

A “+” in front of a group marks it as being expandable (and therefore is reduced). To mark that a group
is expanded (and therefore can be reduced), a “–” is displayed in front of the group.
– Group
The name of the Protection group (protected and protecting boards)
– Port
The name of the Port
– Role
The role of the board (Protecting or Protected)
– Unit State
• A (Active)
• P (Passive)
• AF (Active-Faulty)
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
PF (Passive-Faulty)
– Switch Type
3AL 89062 AA AA 328 / 926
926
• NR (No Request)

• Auto-SF (Auto Switch Signal Fail)

• Auto-SD (Auto Switch Signal Degrade)
• Auto-WTR (Auto Switch WTR)
• Forced (Force switch)
• Lockout (Lockout from switch)
• Fail (APS Invalid) (Protection Fail Condition APS invalid)
• Fail (Bad channel) (Protection Fail Condition channel mismatch)
– Lo. Nb
A number counting the protected protection units of one group being in lockout state
The data in column Unit State appears in different colors. Their meaning is:
– green: OK
protected units being active, protecting units being passive
– red: critical
any protection unit (protected or protecting) being active-faulty
– orange: major
any protection unit (protected or protecting) being passive-faulty
– cyan: indicative
protected units being passive, protecting units being active
It is possible to perform several commands on one or more selected Protection schemes:
– Expand/reduce
Those Protection schemes marked by a “+” in the left column (+/–) will be expanded and those
marked by a “–” will be reduced by clicking this button.
– Delete All
All existing Protection schemes will be deleted, even if no scheme is selected.
– Delete
The selected Protection scheme(s) will be deleted.
– Preferences...
Clicking this button opens the User Preferences dialog box. A detailed description can be found in
Chapter 3.7.
– Add Tp...
By clicking the Add Tp... button, the TP Search dialog is opened as shown in Figure 167. (see de-
1AA 00014 0004 (9007) A4 – ALICE 04.10
scription above).
3AL 89062 AA AA 329 / 926
926
– MSP Commands...
Clicking this button opens the MSP Commands dialog box. A detailed description can be found in
Chapter 10.6.

– Management...

Clicking this button opens the MSP Schema Configuration dialog box. A detailed description can
be found in Chapter 10.3.
– Port Details...
To see a Protection in the Port Details dialog box, click this button. A detailed description can be
found in Chapter 1 .
– Close
The configuration will be saved and the dialog box closed.
The MSP Browser reacts on notifications. If the protection states change, the MSP Browser will be up-
dated.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 330 / 926
926
10.9 Setting up linear MSP with SH–RM interworking
The sane description has been enclosed in the MSP Management chapter, Section 3.3 related to
“QB3*–NE Management”.
Scope
This document summarizes the main guidelines for the correct set up of linear MSP schemes, 1+1 and
1:1, in SDH Q3 NEs in NR5.0x, NR5.1A and 5.1B, i.e. in all the NRs where, according to the current
planning of 1354RM, the creation of the linear MSP scheme is provided only via 1353SH. The document
describes also the undesired behaviours (in any case, without loss of traffic) that may occur if those
guidelines are not followed.
Linear 1+1 MSP
Step 1: SH operator shall set up the protection scheme before RM establishes any physical connection
between the ports of the main and of spare sections. This operation shall be performed before RM takes
into charge the involved resources, or after a temporary deassignment by RM of the involved resources,
or within a privileged operator session.
Step 2: RM operator shall create the physical connection between the ports of the main section only. It has
to be noted that in this situation RM application prevents the creation of a physical connection between
the ports of the spare section.
What happens if this procedure is not followed: if RM operator sets up a physical connection between the
ports of the spare section before establishing the MSP scheme, there are two possibilities, both critical:
a) If also paths are defined over the spare section before the MSP scheme is set up via SH, the
establishment of the MSP scheme will fail.
b) If no paths are defined on the spare section, the establishment of the MSP scheme will succeed but
there will be an inconsistency between RM representation and the actual configuration. Moreover, if RM
operator tries setting up a path over the spare section after the MSP scheme is established, the path
implementation will succeed but the new path will be immediately alarmed. As a further side effect, there
will be an inconsistent representation of connectivity in SH (the path connections over the spare section
are shown in the cross–connection view but not on the corresponding port view, which will only display
the main section). The final result is that it will be difficult for an operator to understand that the path over
the spare section is alarmed because of a wrong configuration sequence.
Linear 1:1 MSP
Step 1: RM operator shall create in advance the physical connections both between the ports of the main
section and between the ports of the spare section. This operation is necessary to allow the set up of
extra–traffic paths on the spare section.
Step 2: SH operator (administrator) shall set up the protection scheme. This operation shall be performed
within a privileged operator session because the physical connections shall be left assigned to RM.
Once the protection scheme is established as described above, RM can set up paths, i.e. traffic, on both
the main (protected) and spare (extra–traffic) sections. It has to be noted that RM does not characterize
as low priority traffic the spare section.
What happens if this procedure is not followed: if steps 1 and 2 of the sequence are reversed, after the
1AA 00014 0004 (9007) A4 – ALICE 04.10
MSP is established the RM application will prevent to set up a physical connection between the ports of
the spare section. As a result, it will not be possible to set up extra traffic.
3AL 89062 AA AA 331 / 926
926
10.9.1 Alarm behaviour
Linear 1+1 MSP

By convention, RM represents the protected multiplex section as a single section between the main ports.

The spare resources are not shown. A MSP switch does not affect the supported paths provided there are
no failures in the protecting multiplex section.
The supported paths will be affected in case both the protected and protecting multiplex sections are failed
and there are no further protection schemes on a different layer (e.g. SNCP). It has to be noted that for
this situation RM affects the paths relying on SSF that should be generated autonomously by the NEs on
the impacted path layer TPs.
Linear 1:1 MSP
On RM, the main and the spare sections are handled as if they were independent. In case of MSP switch,
the low priority traffic will be lost and the related paths will then be alarmed. It is up to the human operator
to correlate this situation with a MSP switch.
Known issues
Failure on consistency audit
It has to be noted that, even if the above procedures are followed, in case RM performs a consistency audit
after the linear MSP scheme has been established, the spare ports will be marked as ”failed” (anyway,
without impacts on the traffic).
Degraded protection indication on RM
RM can not perform any real–time correlation between failures in the main/spare sections and the position
of the switch inside the NE to deduce the degree of availability of the protection.
When the linear MSP is set up on a QB3* NE, the real–time correlation is performed inside SH MIB to
generate a ”degraded protection” alarm on the port of the main (protected) section in case of a failure in
the spare (protecting) section. This alarm is then emitted by SH and represented at RM.
When the linear MSP is set up on a Q3 NE, neither SH (MIB–less for Q3 NEs ) nor the NE perform such
a correlation. As a consequence, the ”degraded protection” alarm is not generated.
Proper provisioning of low priority traffic in 1:1 MSP
RM does not characterize the traffic priority for the physical connections at MS level. It is the responsibility
of the human operator to define properly the high–priority traffic paths over the main (protected) multiplex
section and the low–priority ones over the spare section.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 332 / 926
926
11 RADIO MANAGEMENT
11.1 Radio protection management for UHR

The radio protection block diagram for 1+1 HST (Hot Standby) configuration, applicable to UHR is
represented on Figure 169. The same block diagram, without the TPSW switch, can be considered for
the radio protection 1+1 HET (Hetero) configuration.
0
LRST1 RRST1 MOD 1 TX 1
1
1
EPSW 2 A
TPSW
EPSW 2 B 0
1
LRST0 RRST0 MOD 0 TX 0
0
RRAEPS
RPSW A 0
LRST1 RRST1 DEM 1 RX 1
1
1
EPSW 2 A
0 EPSW 2 B
EPSW1
1
RPSW B 0
Figure 169. Example of radio equipment protection block diagram for 1+1 HST configuration
The RRAEPS (Radio Regeneration Adaptation EPS) functionality is allocated into the IDU subrack as
shown in Figure 170.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 333 / 926
926
1x V11; 1x V24; 1x EOW E1 Channel
2x G703 AUX Port1 and AUX Port2

SAM Unit RRAEPS
0 Cable1 PSU
LRST1 TxRRST1 MOD 1 Tx 4860
1
EPSW 2 A
SR
IDU RPSW A 0
LRST1 RxRRST1 DEM 1
1
Cable1
EPSW 2 A Rx
RMD128 (Main) Unit
EPSW 2 B
1 Cable2
LRST0 TxRRST0 MOD 0 Tx
0 FANS PSU
4860
EPSW 2 B
1
LRST0 RxRRST0 DEM 0
Cable2
RPSW B0 Rx
RMD128 (Spare) Unit
Cable1 Tx
TX 1
Main OSC
Cable1 Rx
RX 1
Local Oscillator
SR
ODU RT128LO Unit
Local Oscillator
Cable2 Rx
RX 0
OSC
Cable2 Tx Spare
TX 0
RT128LO Unit
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 170. IDU/ODU UHR Units in 1+1 HST configuration
3AL 89062 AA AA 334 / 926
926
In Figure 169. the units identified by “1” (i.e.LRST1) are the Main ( Protected ) units while the units
identified by “0” (i.e.LRST0) are the Spare ( Protecting) ones. In Figure 169. are represented the
following protection functional blocks:
– EPS LRST (Line regeneration section termination)

– This block, located in the IDU (indoor) unit, provides the EPS protection of the transmission and
receiving LRST units. It consists of EPSW1, EPSW2A and EPSW2B switches. The protection
switching is “Revertive” or “Not Revertive” depending on the EPS configuration type. The “Force
to protecting” command switches EPSW1–>0, EPSW2A–>1 and EPSW2B –>1. The EPS menu
(configuration and switching) can be opened selecting, in the RMD (Radio Modem/Demodem) unit,
the LRST port or the TxRRST (Transmission radio regeneration section termination) port or the MOD
port.
– EPS HST
– This block, located in the ODU (outdoor) unit, provides the EPS protection of the Radio transmission
side. It consists of TPSW switch. The protection switching is “Revertive” or “Not Revertive”
depending on the EPS configuration type. The “Force to protecting” command switches
TPSW–>0, the “Lockout” command switches TPSW–>1.
– RPS
– This block, located in the IDU (indoor) unit, provides the Hitless protection of the Radio receiving
side. It consists of RPSWA and RPSWB switches. The protection switching is “Not Revertive” by
default. The “Force to protecting” command switches RPSWA–>1 and RPSWB –>0, the”Lockout”
protecting command switches RPSWA–>0 and RPSWB –>1. The “Manual to protecting” command
and the “Manual to protected” command are similar to the previously two commands. The manual
priority is slower then the force one: the priority levels for the RPS (Radio Protection Switching)
command are (from the higher to the lower one): “Force”, “Auto”, “Manual”.
The UHR equipment view is shown in Figure 171. .

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 335 / 926
926
ODU
IDU
Figure 171. UHR equipment view
Zoom into the IDU and select the LRST board unit (see Figure 172. ). Now select the EPS and RPS (radio)
protection switching commands. Open the LRST port view to visualize the EPS/RPS protection statuses
(see para.11.4).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 336 / 926
926
LRST
Figure 172. LRST board view
Zoom into the ODU and select the TX board unit (see Figure 173. ). After selecting the EPS–TX protection
switching commands, open the ODU–TX port view to visualize the EPS protection statuses.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 337 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
TX
RX
LO
926
3AL 89062 AA AA
Figure 173. TX/RX and Local Oscillator ODU board view
338 / 926
11.2 UHRN equipment configurations
11.2.1 UHRN configuration

This section provides information on the allowed equipment types configurations. Any more detail is re-
ported in the CT. Operator’s Handbook UHRN Rel. 1/2.
The UHRN can be equipped up to 4 ( four ) radio channels:
• 1 : N Configurations ( where N is minor of 4 ). One Channel, among N main channels (

protected ), can be transmitted on the spare channel ( protecting ) by Hitless switch function;
moreover, the spare channel can be used to transmit an occasional Main Channel
( Extra Traffic ).
• N + 0 Configurations ( where N is minor or equal of 4 ). In this case all radio channels are inde-
pendent each other ( there is only a communality in terms of service channels management be-
tween channels 1 and 0 ), Hitless switching function is not provided.
• N + 1 Configurations ( where N is minor of 4. With N=1 the 1 + 1 Configuration will be provided).
In each configuration, only STM–1 signals are managed. Figure 174. , Figure 175. , Figure 176. ,
Figure 177. , Figure 180. , Figure 181. , display the UHRN equipment , rack and subrack at different NE
level.
Table 10. on page 342. shows the composition of UHRN 1 while Table 11. on page 344 shows the com-
position of UHRN 2.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 339 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
Figure 174. UHRN 1 Equipment Overview – NE. level.
3AL 89062 AA AA
340 / 926
Slot 7
Slot 1
Slot 2 Slot 9
Slot 3 Slot 10
Slot 4
Slot 11
Slot 5
Slot 6 Slot 12
Slot 8
Figure 175. IDU Equipment Overview – Rack level.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 176. IDU Equipment Overview – Subrack level.
3AL 89062 AA AA 341 / 926
926
Table 10. UHRN 1. Composition: two channels (RT) for any RKODU.
UHRN 1

RACK SUBRACK MODULES LABEL PORT / SUBMODULES LABEL

( DENOMINATION ) ( DENOMINATION )
SAM ( Slot 1 ) –
( New Service card )
RMD 128 – 0 or RMD 16 – 0 IS–1.1 or CMI–E.
( Slot 2 ) ( Daughter 1 )
( RRA / MODEM card )
LRST ( Daughter 2 )
RMD 128 – 1 or RMD 16 – 1
( Slot 3 ) TxRRST ( Daughter 3 )
RxRRST ( Daughter 4 )
RKIDU SRIDU RMD 128 – 2 or RMD 16 – 2
( Rack 1 ) ( Subrack 1 ) ( Slot 5 )
MOD ( Daughter 5 )
DEM ( Daughter 6 )
RMD 128 – 3 or RMD 16 – 3
( Slot 6 )
XPIC ( Daughter 7 ) N.B.
LOGIC ( Slot 4 ) –
( Logic card )
FANS ( Slot 7 – 8 ) –
( Fan Unit ) 0–1
PSU – 4860 ( Slot 9 –12 ) –
( Power Supply Unit ) 0 to 3
RT – 0 ( Slot 1 ) LO ( Daughter 1 )
RKODU SRODU ( Transceiver card ) Local Oscillator module
( Rack 2 ) ( Subrack 1 ) RT – 1 ( Slot 2 )
( Transceiver card ) RX ( Daughter 3 )
RT – 2 ( Slot 1 ) Receiver module
RKODU SRODU ( Transceiver card )
( Rack 3 ) ( Subrack 1 ) RT – 3 ( Slot 2 ) TX ( Daughter 2 )
( Transceiver card ) Transmitter module
N.B. The “ Cross Polar Interference Canceller “ ( XPIC ) is an optional module.
Any RMD is composed by the daughters (1 7) boards listed in the fourth column and any RT transceiver
card, of RKODU, contains the daughters (1 3) boards listed in the fourth column.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 342 / 926
926
Figure 177. UHRN 2 Equipment Overview– NE level
The UHRN 2 is similar to UHRN 1 but can be equipped with only one radio transiver channel for ODU and
with the new rack EPS. Then the NE equipment will be composed by one rack RKIDU, a new rack RKEIP
for EPS protection and four RKODU to insert the four radio transiver (see Figure 177. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 343 / 926
926
Table 11. UHRN 2. Composition: one channel (RT) for any RKODU
UHRN 2


SAM ( Slot 1 ) –
( New Service card )
RMD 128 – 0 or RMD 16 – 0 IS–1.1 or CMI–E.
( Slot 2 ) ( Daughter 1 )
LRST ( Daughter 2 )
RMD 128 – 1 or RMD 16 – 1
( Slot 3 ) TxRRST ( Daughter 3 )
RxRRST ( Daughter 4 )
RKIDU SRIDU RMD 128 – 2 or RMD 16 – 2
( Rack 1 ) ( Subrack 1 ) ( Slot 5 )
MOD ( Daughter 5 )
DEM ( Daughter 6 )
RMD 128 – 3 or RMD 16 – 3
( Slot 6 )
XPIC ( Daughter 7 ) N.B.
LOGIC ( Slot 4 ) –
( Logic card )
FANS ( Slot 7 – 8 ) –
( Fan Unit ) 0–1
PSU – 4860 ( Slot 9 –12 ) –
RT – 0 ( Slot 1 ) LO ( Daughter 1 )
RKODU SRODU ( Transceiver card ) Local Oscillator module
( Rack 2 ) ( Subrack 1 )
RX ( Daughter 3 )
( Rack 3 ) ( Subrack 1 ) TX ( Daughter 2 )
Transmitter module
RT – 3 ( Slot 1 )
1AA 00014 0004 (9007) A4 – ALICE 04.10

3AL 89062 AA AA 344 / 926
926
N.B. The “ Cross Polar Interference Canceller “ ( XPIC ) is an optional module.
Any RMD is composed by the daughters (1 7) boards listed in the fourth column and any RT transceiver
card, of RKODU, contains the daughters (1 3) boards listed in the fourth column.
Table 12. UHRN 2 EPS rack composition
UHRN 2 – EPS
EPS SPI – STM1 OPT / EIS
( Slot 1 ) (daughter 1)
SPI – STM1 EIS

EPS
(daughter 2)
( Slot 2 )
EPS
( Slot 3 )
RKEIP SREIP
EPS
( Slot 4 )
BOARD CONNECTION –
( Slot 5 )
PSU – 4860 –
PSU – 4860 –
Any EPS is composed by the SPI daughters (1 2) boards listed in the fourth column
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 345 / 926
926
11.2.2 EPS protection on UHRN 2
The EPS subrack protection is composed with four EPS boards, a Board connection module and one (or
two) power supply units. Taking in account the block diagram of Figure 178. and any RMD module is con-

nected to the RKEIP via two cables: the input “X” of Figure 178. connected to the output RMD “X” (X=

03) and the output “Y” of Figure 179. connected to the input RMD “Y” (Y=03).
Board Connection
EPS Module 0
AIS ”0”
PSU
EPS Module 1 power supply
SREIP ”1”
EPS Module 2
”2”
EPS Module 3
”3”
RMD
LRST RFCOH DEM RX
”0”
RMD
LRST1 RFCOH1 DEM 1 RX 1
”1”
RMD
LRST2 RFCOH2 DEM 2 RX 2
”2”
RMD
”3”
Figure 178. EPS RX (receiver) block diagram on UHRN 2 (3+1 conf.)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 346 / 926
926
Board Connection
”0”
EPS Module 0
PSU
power supply
EPS Module 1 ”1”
SREIP
RMD LRST RFCOH MOD TX

”0”
RMD LRST1 RFCOH1 MOD 1 TX 1

”1”

”2”

”3”
Figure 179. EPS TX (transmit) block diagram on UHRN 2 (3+1 conf.)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 347 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Board Connection
Figure 180. EPS Equipment Overview – Rack level
926
3AL 89062 AA AA
348 / 926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
Figure 181. EPS Equipment Overview – Subrack level
3AL 89062 AA AA
349 / 926
Figure 182. EPS module and OPT/EIS box setting dialog
The operator can configure the STM 1 EPS interface with an optical short haul interface. If the daughter
board is empty ( default setting ) the STM1 interface is an electrical EIS interface. Zooming into the EPS
module the EPS board view of Figure 183. is shown. On the EPS board are visulaized the electrical inter-
face SDH “B” (port#01–EIS) connected to RMD module (LRST board) via the Board Connection and the
optical or electrical interface SDH “A” (#01–EIS#02) connected to the line.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 350 / 926
926
Figure 183. EPS board view
Clicking on the SDH “A” (#01–EIS#02), Figure 184. opens. The SPI icon current selected shows the
board interface from which has been opened the port view: the first SPI interface corresponds to the line
interface SDH “A”, the second SPI interface corresponds to the SDH “B” (port#01–EIS) connected to the
Board Connection, while the third SPI interface corresponds to the LRST ( RMD ) STM1 board interface.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 351 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 184. EPS Port view window
926
3AL 89062 AA AA
352 / 926
11.2.2.1 Base Band
The RMD card comprises the RRA, Modulator, and Demodulator functional units. The RRA unit is con-
nected to the transmission line through one optical or electrical interface, placed inside the RRA unit itself,
if electrical interface protection is provided. The spare channel ( RMD 0 ) is equipped with this module (
electrical or optical ) only if extra traffic is supported.
The Optical and Electrical Interfaces are alternative to each other.
The New Service card ( called SAM in the following screens ), comprises a System Controller ( with an
Equipment Controller and a Radio Controller ) and Service units. This board comprises the memory de-
vices, the external connectors for the Q3 and F interfaces and for the auxiliary AUX./EOW service chan-
nels and 2Mbit/s WST.
The LOGIC card is composed of the TX and RX distributor and the switch logic for the RPS function used
in 1 : N Configurations; the unit is necessary also in N + 0 Configurations, where the RPS function is not
used.
Only in case of 128 QAM modulation in the RMD card can be present the “ Cross Polar Interference Can-
celler “ module ( XPIC ) . This module is used in the frequency reuse configurations.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 185. Selectable modules view.
3AL 89062 AA AA 353 / 926
926
From the screen above the operator can get access to each module ( Unit ) belonging to the BaseBand
Subrack ( SRIDU ).As example the module corresponding to RRA / MODEM ( RMD ) has been selected.
By clicking twice the selected module the next screen opens ( see Figure 186. on page 354 ).

Figure 186. RRA–MODEM card ( RMD 128 or RMD16 QAM ) screen.
Starting from the RRA–MODEM card screen the operator can get access to all the circuit parts
( Daughters ) RRA–MODEM consists of ( see Table 10. on page 342 and Table 11. on page 344).
By clicking twice on a selected circuit ( for example Electrical Interface ) the screen relative is opened (
see Figure 187. on page 355 ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 354 / 926
926
Figure 187. Electrical Interface module ( CMI–E ) screen ( Daughter 1 ).
The screen above shows the Electrical Interface unit. By clicking twice on the square in the high left posi-
tion ( SDH port ) the SDH port view screen of Figure 184. is opened.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 355 / 926
926
11.2.2.2 Transceiver
Every Transceiver card ( RT 0 to 3 ) is composed of the following modules:

• Local Oscillator module

• Transmitter module
• Receiver module.
There are two different types of transceiver cards:
– Transceiver card 128 QAM
– Transceiver card 16 QAM.
The Transceivers above are in alternative between them.
The same UHR ODU configuration reported in para. 11.1 on page 333 can be applied to UHRN 2 equip-
ment.
N.B. For detailed description,functionalities,equipping rules of the Transceiver and ODU Equipment,
refer to “ 9600USY/UHRN Technical Handbook “.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 356 / 926
926
11.3 LHR Equipment
The LHR equipment is composed by the SRBB (Subrack Banda Base) and STRI128 (Subrack Transiver
Radio Interface) (see Figure 188. ). The SRBB is equipped with SYSCO (system controller), SERVICE
to manage the 2Mbit/s and 64Kbit/s auxiliary channels and to distribute the switching protection com-
mands, RRA (Radio Regeneration Adapter) and its relative Modem (see Figure 189. ). The STRI128 is
equipped with TRI128 channels. The LHR equipment can be configured with 10 channels or with 9 + 1
protection channel. Any bidirectional channel is equipped with an RRA board, a Modem board and a
TRI128 board.
Figure 188. LHR equipment view
Zoom into the SRBB–N1 subrack to visualize Figure 189.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 357 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Zoom into the STRI128 subrack to visualize Figure 190.
Figure 189. SRBB–N1 subrack example
926
3AL 89062 AA AA
358 / 926
Figure 190. Transmission Radio Interface View example
In the LHR equipment here considered is shown a LHR with a configuration 2 + 1: three RRA + Modem
in the SRBB and three TRI128 boards ( Figure 190. ): the TRI128 stand–by channel “0”, the TRI128 chan-
nels1 and channel 2.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 359 / 926
926
11.3.1 BER Not Intrusive on LHR
“BER Not Intrusive” option allows to collect the BER measurement data, incoming on the RST TTP, and
to show them on the BER Not Intrusive box dialog. It is based on “B1” bit interleaving parity process that

for burst errors has been corrected by a multiplier factor.

Select the RST icon on the STM 1 port view and then from the port menu the Ber Not Intrusive option (see
Figure 191. ) to open .
Figure 191. BER Not Intrusive option

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 360 / 926
926
Figure 192. Ber Not Intrusive box dialog
Considering burst with 510 errors the minimum time to have a code violation (BIP–8) depending on the
noisy channel is:
– 1 sec. for BER between 10–3 and 10 –8

– 10 sec. for BER=10 –9
– 2 min. for BER=10 –10
– 20 min. for BER= 10 –11
– 200 min. for BER=10 –12
The box dialog allows to start/stop BER measurement data and to display them. The field “TP Name”
contains the user label of the RSTTP under measurement.
When the window opens, the “START” button is compliant with the current situation about BER measure-
ment:
1AA 00014 0004 (9007) A4 – ALICE 04.10
– sensitive if the BER measurement data collection is active
– not sensitive if the BER measurement data collection is not active
3AL 89062 AA AA 361 / 926
926
Click on the “START” button to start the BER measurement Data collection and then on the “STOP” button
to stop the BER measurement. The STOP button is sensitive only if a BER measurement is in progress.

Figure 193. BER Not Intrusive measurement example
The “REFRESH” button allows the operator to retrieve the update data.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 362 / 926
926
Figure 194. BER Not Intrusive window (Overflow condition)
The visualized information is:
violation number detected from the “Start” time
BER measurement and the elapsed time
The elapsed time is the period which the violations and the BER are related to
Figure 194. shows the Overflow condition when the violations and the elapsed time exceed the maximum
defined threshold (32 bits).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 363 / 926
926
11.4 EPS protection on UHR 1.0, UHR 2.0 and UHRN 2.0
Taking in account the EPS protection as described in para. 11.1 open the board view and select the EPS
menu option. For UHR 2 and UHRN 2 see also the EPS Overview option ( para. 9.6 on page 296 ).

Figure 195. EPS menu
– Configuration
Select the “Configure” option from the EPS menu. Figure 196. opens.
In the example of Figure 196. the EPS configuration concerns the ODU–TX radio equipment.
Figure 196. EPS configuration for ODU–TX radio equipment

1AA 00014 0004 (9007) A4 – ALICE 04.10
The user can select a revertive or non revertive configuration.
Select OK to apply the chosen configuration or Cancel to close the window.
3AL 89062 AA AA 364 / 926
926
– Switching
The following external switching commands can be provided: “Force to” Protecting when the protected
unit is active and the user wants to switch from the protected to the protecting unit; “Lockout” when the
protecting unit is active and the user wants to switch from the protecting to the protected unit; Release
to remove the current switching command.
N.B. When a switching command is applied, before to carry out another EPS switching, apply the
“Release” command to come back to the normal condition.
Figure 197. External switching commands for ODU–TX radio equipment
After having applied a command the “Abnormal Condition” AC is highlighted.
The “Manual to” and the “Exercise” commands are not implemented in current SH release.
When the EPS switching is applied, the protected unit is distinguished by a higher slot number. In the
example of Figure 198. , the protected port is indicated as r02sr1sl02, in the example of Figure 199. , the
protected port is indicated as r01sr1sl03.
After a ”Force to protecting” switching command , the functional EPS statuses change according to
Figure 198.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 365 / 926
926
Figure 198. EPS statuses after a “Force to protecting” switching command applied to ODU–TX
Select the IDU radio equipment and then the LRST (Line radio section termination). Consider the following
example of protecting status: protecting unit = active, protected unit = stand–by and Switch Type =
NoRequest. In this case, the only command that can be applied is the “Lockout” command to switch from
the protecting to the protected one. After this command the protection statuses change according to
Figure 199.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 366 / 926
926
Figure 199. EPS statuses with a “Lockout” switching command applied to the IDU (LRST)
The EPS statuses represented on port view are:
– “Ports” involved in a RPS Protection Schema

– “Protection “Role” of the current port: protecting, protected.
– “Status” of the current port: stand–by, active.
– “Switch Type” (current external protection command): NoRequest, ForcedSwitch, Lockout .
The EPS on UHRN 2 is dual ended then it has been added a new EPS label status to mark the switch
source generation (see Figure 200. ):
– “Request Source” : None, Local, Remote.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 367 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 200. EPS statuses on UHRN 2
926
3AL 89062 AA AA
368 / 926
11.5 RPS (Radio Protection Switching) Protection
11.5.1 RPS on UHR 1.0 and UHRN 1.0

The RPS parameters are displayed in the Radio menu of the menu bar ( see Figure 201. page 369 ),
providing access to:
• Configure ( Scheme: on UHRN )

• Configure Units (on UHRN only)
• Switch
• Synthesis
• Extra Traffic (on UHRN only)
These options are always available and display a secondary window.
Figure 201. RPS options on UHR 1 .
Figure 202. RPS options on UHRN 1.
The window is automatically refreshed for regular updating. The user can manually refresh the window
with the “Port” or with the “Views” menu “Refresh” option when for example a successful automatic switch
occurs and the new window state is not updated.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The RPS configuration scheme can be 1+1 on UHR 1 or 1+1 and 1:N on UHRN 1.
3AL 89062 AA AA 369 / 926
926
11.5.1.1 RPS Configure screen

Figure 203. RPS Configure dialogue box example
This dialogue allows to configure the parameters for RPS schemes.
In the Schemes field are reported the ports involved in the protection. Click on the Schemes ports to fill
in the Protecting/Protected Port fields. In the 1+1 configuration the protected port is distinguished by a
higher slot number. In the example of Figure 203. the protected port is indicated as r02sr1sl02 while the
protecting port is r02sr01sl01.
The “Protection Status” visualizes the current Protecting/Protected external switching commands (see
para.11.5.1.3). The following indications can be shown:
• Protecting Port: No Request, Lockout

• Protected Port: No Request, Force Switch
Select the “Schema Parameters” required taking into account that for these NEs can be applied the
following configurations:
• switching type is fixed to Single ended on UHR, Single / Dual ended on UHRN
• operation type is fixed to No Revertive on UHR, Revertive / Not Revertive on UHRN
• RPS protection scheme is fixed to 1+1 on UHR, 1+1 / 1:N on UHRN
• Wait to restore time only configured if the operation type is Revertive
• Hitless capability fixed to Supported on UHR, Supported / Not Supported on UHRN
1AA 00014 0004 (9007) A4 – ALICE 04.10
• Radio Hold Off Time fixed to 0 on UHR, configured if the hitless capability is not supported
To set the configuration parameters, the user shall modify the elements.
3AL 89062 AA AA 370 / 926
926
The Apply button starts the execution of the command and the wait cursor is presented until the operation
is completed, then the dialogue disappears.
The Apply button is enabled or disabled (” greyed “) according to the NE setting present in resource file.
If Apply button is disabled, the elements ( configuration parameters ) cannot be modified.
The Close button removes the dialogue.
The Help button provides some useful information on the dialogue capabilities.
11.5.1.2 Configure Units screen on UHRN 1
This dialogue allows the operator to configure the Priority for protected channels and if a protected
channel is Privileged Channel or not.
The Choose Schema button is sensitive only if more than one RPS scheme has been configured,
otherwise it is not sensitive and the information about the unique RPS scheme present are directly
displayed.
When more than one switch request are present, the highest priority is served.
For priority sequence of protected channels and other details refer to Technical Handbook.
The operator has to choose a line in the matrix, then using two option menus, may set or change the priority
and the privileged status of the selected channel.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 204. Configure Units dialogue box example on UHRN
3AL 89062 AA AA 371 / 926
926
11.5.1.3 RPS Switch screen

Figure 205. RPS Commands dialogue box example
This dialogue allows to apply the external protection commands on RPS ports.
In the Schemes field are reported the ports involved in the protection. Click on the Schemes ports to fill
in the Protecting/Protected Port fields. In the 1+1 configuration the protected port is distinguished by a
higher slot number. In the example of Figure 205. the protected port is indicated as r02sr1sl02 while the
protecting port is r02sr01sl01 ( it is mandatory to choose the protected port to start protection commands,
while the protecting port is determinate when protected port is chosen ) .
The “Exercise” commands is not implemented actually.
The available commands depend on the “Active” port condition status: if the Protected port is “Active”, the
applicable external command is “Force To” Protecting to switch from the protected port to the protecting
one (see Figure 206. ), if the Protecting port is “Active” the applicable external command is “Lockout”
Protecting to switch from the protecting port to the protected one. The Manual command switches from
Protected to Protecting or vice versa according to the activated current status
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 372 / 926
926
Figure 206. Protection status after a “Force To” command
N.B. Pay attention to “Release” a previous external command before to apply a second one.
When an external switching command is applied, the “Abnormal Condition” AC is highlighted.
When an Apply button is clicked, the operation is started, after a confirmation, and a wait cursor is
presented; at the end of the request, the dialogue will disappear.
If any errors arise during the request, an error dialogue is presented.
The Close button removes the dialogue.
The Help button provides some useful information on the dialogue capabilities.
The functional states of the involved ports in the RPS protection scheme are displayed in the Port view
when the RPS functional block is selected (see Figure 206. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 373 / 926
926
11.5.1.4 RPS Protection Status and Synthesis screen
The switching protection functional states are displayed on the small boxes of the port view bottom (see
Figure 207. ):

Figure 207. Protection switching statuses on the port view (Force to)
The same info is also reported on “RPS Synthesis” screen (see Figure 208. ).
Figure 208. RPS Synthesis dialogue box example

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 374 / 926
926
The information is:
– “Ports” involved in a RPS Protection Schema

– Protection “Role” of the current port: protecting, protected.
– “Status” of the current port: stand–by, active.

– “Switch Type” (current external protection command): NoRequest, ManualSwitch, ForcedSwitch,

Lockout, HwForcing .
– “Automatic Switch” (in the increasing priority order): NoOne, EarlyWarning, LowBer, HighBer,
SignalFail, WaitToRestore.
11.5.1.5 Extra Traffic screen on UHRN
The window allows the operator to suspend and resume extra traffic on a protecting channel.
A matrix allows the protecting channel choice, once selected the sensitivity of Enable, Disable buttons
is compliant with the selected channel status.
Only a single selection is allowed
The “Extra Traffic” field contains one of the following indication:
– Disabled
– Enabled
– the user label of the protected channel, if a switch has occurred
Pressing the two buttons: Enable, Disable it is possible to suspend and resume extra traffic.
Figure 209. Extra Traffic dialogue box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 375 / 926
926
11.5.2 RPS on UHRN 2.0, LHR 1.0 and UHR 2.0
The RPS parameters are displayed in the Radio menu of the menu bar ( see Figure 210. page 376 ), pro-
viding access to a secondary window. These windows are automatically refreshed for regular updating.

Figure 210. Example of Radio menu ( on LHR )
The user can manually refresh the windows with the “Port” or with the “Views” menu “Refresh” option.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 376 / 926
926
11.5.2.1 Configuration
The RPS parameters on LHR are related to a m : n protection schema while the RPS parameters for UHR
is provided for 1+1 protection schema. Select the RPS–>Configure –>Schema command from the Radio
menu as shown in Figure 210.

Figure 211. opens. This is a read only window. Select the channel number to visualize the schema config-
ured parameters.
In the upper part of the window a tree list provides all existing schema with protecting elements as root
nodes and the protected elements as leaves.
To display the configuration parameters, the user selects in the tree list a protecting port and/or a protected
port (the protected port is not mandatory to choose an RPS schema).
This operation fills the protecting and/or protected elements text fields with the selected ports and starts
a request for the configuration parameters to the NE.
When the operation is over, the following information is displayed to the user in this box:
– the protection status of the protecting and/or protected ports
– the configuration parameters for the selected RPS schema:
• switching type ( fixed to Single ended on LHR )
• operation type ( fixed to Revertive on LHR )
• RPS protection schema ( 1+1 on UHR; m : n on LHR )

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 211. RPS Configure Schema box example
3AL 89062 AA AA 377 / 926
926
N.B. The “Choose Schema” button is sensitive only if more than one RPS schema is present in the
NE.
The Close button close the window, the Help button provides some useful info. on the dialog capabilities.

On LHR the operator can configure a priority level on the m : n protection schema ( in Figure 211. , n=1

and the Channel “0” is the protecting channel). Click on RPS–>Configure–>Units command to open
Figure 212. Select the channel and assign a priority clicking on the pop down “Priority” button (9 priority
values are allowed). Click on the “Privil. Channel” to forward the protection channel to the selected one.
The above mentioned option is available if no “Extra Traffic” has been configured on the protection chan-
nel (see Figure 220. ).
Figure 212. RPS Configure Units box example (on LHR)
The “Priority” level has been configured, for all channels, to the default value “4” : that is, all the channels
have the same priority level.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 378 / 926
926
Figure 213. Example of Privilege Channel (channel “1”) on LHR
11.5.2.2 Static Delay
The static delay alignment is necessary in order to have the hitless switching of the channel from direct
way to indirect way. The operation allowed is:
• Automatic delay alignment (Rx side) both for direct way and indirect way
The alignment can be done on one channel at a time.

If one channel is not aligned, the automatic switching function is inhibited.
Click on RPS–>Static Delay–>Rx Side to open Figure 214.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 379 / 926
926
Figure 214. Static Delay on Rx Side box example
The dialogue box visualizes a matrix with five columns:
– the first column contains the channel number associated to a physical radio port
– the second column contains user label associated to a protecting or protected Ports
– the third column contains the value of static alignment (shift value) applied to signal coming from Di-
rect Way (0 to 255)
– the fourth column contains the value of static alignment (shift value) applied to signal coming from
Indirect Way (0 to 255)
– the fifth column contains the indication of actual Status (“No operation active”, “auto alignment”,
“manual alignment”).
Select the channel and click on the Manual button to open Figure 215.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 380 / 926
926
Figure 215. Static Delay Manual Configuration box
Enter the delay value, expressed in bit number, in the “Direct Way” field to configure the relative channel
or in the “Indirect way” field to configure the protection channel.
Click on Apply to modify the Static value or on Close to discard your entries and close the dialog box.
Figure 216. shows the Static Delay with the new entries: if the “Restore” button becomes enable then
clicking on Restore and on Apply, the last old data will be restored into the delay fields
Figure 216. Static Delay Manual Result box example
Select the first row “Channel 0” on the the Static Delay dialogue box and then click on the “Set” button
to start the static alignment procedure (see Figure 217. ). A warning message advices the user about the
consequent actions of the alignment command. Click on “OK” to apply the command or on “Cancel” to
close the window . The same operation has to be performed also on the second “Channel 1”.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 381 / 926
926
Figure 217. Setting the “Static Delay”
The Close button on Figure 217. closes the window .
The Help button provides some useful information on the selected option.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 382 / 926
926
11.5.2.3 Switch
Click on RPS–> Switch to open Figure 218. Select the channel in the “Schemes” field to enter the Protect-
ing Port / Protected Port strings. In the LHR m : n configuration ( the maximum m value is 9 while n value
is 1 ); in UHR is available the 1+1 configuration. The possible commands are: lockout, force and manual.
Figure 218. Example of switch Command box ( on LHR )
– The Lockout command disables the switching on the Protected / Protecting channel
– The Force To command executes a forced protection on the Protecting channel.
– The Manual To command is similar to Force To command but is at a lower priority level respect to
automatic protection. It executes the switching on the Protecting or Protected channel
– The Release command cancels the previously selected command and comes back to the previous
functionality
11.5.2.4 Synthesis
This feature allows to have a complete view of all NE resources involved in RPS protection schema.
Click on RPS–> Synthesis to open Figure 219. The synthesis window box info are:
– Port involved in RPS protection Schema.

– Protection role of the current port ( protecting, protected )
– Status of the current port (stand–by, active)
– Switch type (last operator command) (NoRequest, ManualSwitch, ForcedSwitch, Lockout,
HwForcing).
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Automatic Switch (NOne, WaitToRestore, EarlyWarning, LowBer, HighBer, SignalFail)
3AL 89062 AA AA 383 / 926
926
Figure 219. RPS Synthesis box example
11.5.2.5 Extra Traffic ( available on LHR )
Click on RPS–> Extra Traffic to open Figure 220. “Enable” or “Disable” the Protection channel to trans-
port the Extra traffic clicking on the relative buttons. If the Extra Traffic is Disable , the protection channel
can be used to transport a Privileged Channel (see Figure 212. )
Figure 220. Extra Traffic Enable / Disable box on LHR

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 384 / 926
926
11.6 RFCOH (Radio Frequency Channel Overhead) management on LHR
The STM1 Radio overhead has been modified to transport the WST (Way Side Traffic) 2Mbit/s stream
and the SCP (Service Channel Protection) 64Kbit/s stream.
Zoom into the SERVICE board to select the r01 sr2 sl02 daughter board as displayed in Figure 221.
Figure 221. Selecting the daughter board to configure the overhead protection
Set the overhead protection channel configuration with the Equipment–>Set command as shown in
Figure 222. and choose between SCP / SCPWP protection group and inside the group choose the protec-
tion and working channels module.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 385 / 926
926
Figure 222. Overhead Protection modules
Then the user with the RFCOH menu can manage the overhead channels ( see Figure 223. )
Figure 223. RFCOH menu

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 386 / 926
926
11.6.1 RFCOH Configuration
Click on RFCOH–> Configure command to open Figure 224.

Figure 224. RFCOH Configuration box
Select the “Choose Schema” button to open the Rfcoh Port and then the radio overhead port as shown
in the example of Figure 225.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 225. RFCOH Configuration box after “Choose Schema” Command
3AL 89062 AA AA 387 / 926
926
Figure 226. Rfcoh configuration window example
The Rfcoh configuration window is a read only box. In the example of Figure 226. has been displayed the
overhead of the channel “2” protected by the the overhead of the channel “1” (protecting). It is only possible
to protect 1 of 10 available channels with a 1+1 No Revertive Single Ended protection schema. In the
example of Figure 226. the protected port is the Channel 2 while the protecting port is the Channel 1: that
means to set the daughter board with CH12SCPWP module (see Figure 222. )
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 388 / 926
926
11.6.2 RFCOH Switch
Click on RFCOH –> Switch command to open Figure 227.

Figure 227. RFCOH Switch command box
Click on the Schemes ports to fill in the Protecting/Protected Port fields. In the 1+1 RFCOH configuration
the available commands depend on the “Active” port condition status: if the Protected port is “Active”, the
applicable external command is “Force To” Protecting, to switch from the protected port to the protecting
one (see Figure 227. ), if the Protecting port is “Active” the applicable external command is “Lockout” Pro-
tecting, to switch from the protecting port to the protected one. The “Release” command releases the pre-
vious command without affecting the protection switching.
N.B. Before applying a second external command releases the previous one.
When an external switching command is applied, the “Abnormal Condition” AC is highlighted.
When the “OK” button is clicked, the operation is started, after a confirmation, and a wait cursor is present-
ed; at the end of the request, the dialogue will disappear.
If any errors arise during the request, an error dialogue is presented.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 389 / 926
926
11.6.3 RFCOH Synthesis
Click on RFCOH–> Synthesis command to open Figure 228.

Figure 228. RFCOH Synthesis box
The following switching indication can be visualized:
Role:
– Protecting
– Protected
Status:
– Stand–by
– Active
Switch Type:
– No Request
– Forced
Automatic Switch :
– No one
– Early warning
– Low Ber
– Excessive Ber
– Signal Failure
The same indication will be displayed on the Protected / Protecting Port View window ( see Figure 206. )
N.B. The updating of the Port View is not automatic. Click on the “Refresh” option of the Port menu
or on the “Refresh” option of the Views menu.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 390 / 926
926
11.7 ATPC
11.7.1 ATPC Power Setting on UHR 1 and on UHRN 1

Click on the ATPC ( Automatic Transmitted Power Control ) /Power Setting menu option to open
Figure 230.
Figure 229. ATPC option offered by the RADIO menu bar .
The ATPC Power Setting is used to control the transmitting power level.
The ATPC dialog box displays three columns
The first column contains all the user label associated to physical radio port
The second column contains the indication about the ATPC status (possible value: Enable / Disable
/ Not Implemented
The third column contains the indication about the ATPC Manual operations status ( possible value:
Active, Not Active, Not Applicable).
Select a row to issue the ATPC configuration. The Enable / Disable functions enable / disable the ATPC
functionality. Click on the button to perform the operation on line.
The buttons changes sensitivity accordingly to the following conditions:
Set button is enable only if ATPC is different from “Enabled” .
The Enable / Disable buttons changes also the ATCP status: from Enable to Disable and vice versa. If
the ATPC status is “Enable”, the TX power control is automatically provided at the output radio port. If
the ATPC status is “Disabled”, the “Set” button can be selected to change the TX power level. When a
ATPC operation is performed, a confirmation box is always opened. (see Figure 230. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 391 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Click on “Set” button to open Figure 231.
Figure 230. ATPC dialogue box example
926
3AL 89062 AA AA
Figure 231. ATPC dialog box with the Set command example
392 / 926
Initially the “Pout Value” field shows the current TX power level. In this screen it is possible to modify Pout
level ( Pout Value ) by up arrows and down arrows with step of 0.1 dbm or by writing directly in the field.
The new value is considered when the Apply button is pressed after a confirmation box; value must be
inside the range values visible in the screen otherwise an error message box appears.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 393 / 926
926
11.7.2 ATPC on UHRN 2.0, LHR 1.0 and UHR 2.0
The ATPC Power and Threshold Setting item menu is always available and this option can be selected
even if the ATPC capability is not supported by the NE

Figure 232. ATCP menu on UHRN 2, LHR 1 and UHR 2
Select ATPC –>Power and Threshold Setting option of the Radio menu to open Figure 233.
Figure 233. ATPC management window example
The ATPC dialog box displays four columns: respect to the previous ATPC Power Setting on UHR 1 has
1AA 00014 0004 (9007) A4 – ALICE 04.10
been added a new first column with the user label associated to the physical radio port and two new op-
tions: Manual and Configure.
3AL 89062 AA AA 394 / 926
926
Select a row to issue the ATPC configuration. The Enable / Disable functions enable / disable the ATPC
functionality. Click on the button to perform the operation on line.
The buttons changes sensitivity accordingly to the following conditions:

Set button is enable only if ATPC is different from “Enabled” (as before on UHR 1).
Manual button changes accordingly of value of selected Manual field. (It can be selected in Enable
/ Disable status)
Configure button is enable if the radio port can be configured.
Figure 234. Set command on the enable ATPC channel with error indication
Click on Configure to open Figure 235.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 395 / 926
926
Figure 235. ATCP configuration dialog box example
The user can modify the ATPC functions ( min. Range, max .Range and Low Power Threshold level )
by up arrows and down arrows with step of 0.1 dbm or by writing directly in the field. The new value is
considered when OK button is pressed; value must be inside the range values visible in window otherwise
an error message box appears. Before the operation is performed, an explicit confirm is required by means
of a confirmation box.
Clicking on “Set” button is available the same dialog box of UHR 1 (see Figure 231. on page 392). This
function modifies the TX power level when Manual Operations are Not Active or Not Available. The cap-
ture of the Attribute Value Change message allows to update the fields of ATPC Configure screen of
Figure 235.
Click on “Manual” button to open Figure 236.
This function starts Manual Operation Session functionality, if not already in opened, and then opens the
ATPC Management screen in manual mode. If the start of Manual Operation Session is correctly per-
formed, the ATPC status is changed on line.
This function allows to modifies the TX power level when Manual Operation is Active.
Initially the TX Power Setting screen shows the current TX power for the Tp selected in previous window.
In this screen it is possible to modify TX power level ( Pout Value ) by up arrows and down arrows (with
step of 0.1 dbm) or by writing directly in the field. The new value is considered when Apply button is
pressed; value must be inside the range values visible in the screen otherwise an error message box ap-
pears. No confirm box is shown.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 396 / 926
926
Figure 236. ATPC Manual Power Setting window example
The four automatic apply buttons are provided for more quickly operations: pressing the buttons, the ptx
value is increased or decreased and immediately send to NE. However value must be inside the range
values visible in window otherwise an error message box appears.
The Stop Manual button closes the Manual Operation Session.
Click on “ATPC Identifier” option on the Radio menu to open Figure 237.
The ATPC Identifier item is always available, and it is sensitive only if the feature is supported by the NE.
The box contain the ATPC Single direction identifier ( Sent Identifier ) . The Operator may change the
number by means up arrows and down arrows. To activate the new number the operator has to press the
Ok button. The dialog disappears. To verify the success of the new setting, the operator has to reopen
the dialog.
If a mismatch between the Expected and Received ATPC identifier has been detached, the Power ATPC
control remains frozen on the last correct value.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 397 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 237. ATPC Single direction Identifier
926
3AL 89062 AA AA
398 / 926
11.8 Static Delay on UHR 1 and UHRN 1
The “Static Delay” is an alignment operation normally carried out during the equipment installation phase.
This procedure allows to realize the hitless switching between two different channels, during the normal
radio equipment activity, for protection purpose.

Figure 238. Static Delay menu option on UHR / UHRN
From the Radio menu select the “Static Delay” option. Figure 239. opens.
Figure 239. Static Delay dialog box example on UHRN.
– the first column contains user label associated to a protecting or protected Ports.
– the second column contains the value of static alignment ( shift value ) applied to signal coming from
Direct Way ( 0 to 255 ).
– the third column contains the value of static alignment ( shift value ) applied to signal coming from
Indirect Way ( 0 to 255 ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
– –the fourth column contains the indication of actual Status ( “No operation active”, “auto alignment”,
“manual alignment” ); the manual alignment is not available.
3AL 89062 AA AA 399 / 926
926
The operator may select an item of the scrolled matrix, that makes the entire row selected ( see
Figure 241. ).
If no selection is performed all buttons except “Close” and “Help” are insensitive.

Figure 240. Static Delay dialogue box on UHR 1
Select the first row “Channel 0” on the the Static Delay dialogue box and then click on the “Set” button
to start the static alignment procedure (see Figure 241. ). A warning message advices the user about the
consequent actions of the alignment command. Click on “OK” to apply the command or on “Cancel” to
close the window . The same operation has to be performed also on the “Channel 1”.
The “Manual” option is not applicable on these equipments.
Figure 241. Setting the “Static Delay” on UHR 1
The Close buttons close the window .
The Help button provides some useful information on the selected option.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 400 / 926
926
11.9 Frequency / Frequency Agility
From the Radio menu select the “Frequency” on LHR or the “Frequency Agility” on UHR and UHRN
menu option to open the relative Figure 243. or Figure 244.
Figure 242. Frequency Agility menu option
11.9.1 Frequency on LHR 1
The frequency box on LHR is a read only box with four columns:
– the first column contains the channel number associated to a physical radio port
– the second column contains the user label associated to a physical radio port
– the third column contains the value of TX frequency
– the fourth column contains the value of RX frequency
Figure 243. Frequency dialogue box on LHR

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 401 / 926
926
11.9.2 Frequency Agility on UHR and UHRN
The “Frequency Agility” option on UHR and UHRN allows to modify the transmission oscillator frequency
in the range of the possible frequency values (channelling). Select the radio port row in the list of

Figure 244. and click on the “Set” button. Figure 246. opens.

Figure 244. Frequency Agility dialogue box on UHR 1
If no selection is performed all buttons “except “Close” and “Help” are insensitive.
The new local frequency is applied in both transmission and receive sides then this operation can modify
the remote oscillators. On UHRN equipment the Frequency Agility modifies the Local Oscillator only. See
Figure 245. scheme for a 1+1 configuration.
1 + 1 CONFIGURATION
TX RX
Local
Oscillator
TX RX
Local
Oscillator
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 245. 1+1 Radio Configuration schema for “Frequency Agility”
3AL 89062 AA AA 402 / 926
926
Figure 246. Frequency set dialogue box example on UHR / UHRN
In this screen is possible to modify the frequency value by up–arrow and down–arrows (with step of 0.01
Mhz) or by writing directly in field.
The new value is considered when “Apply” button is pressed; value must be inside the range values
visible in window otherwise an error message box appears.
If the operation is correctly performed, a confirmed message box is shown. Immediately the new data
is sent to NE to update TX freq and RX freq in previous window (Figure 244. on page 402).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 403 / 926
926
– Frequency Agility on UHR 2
On UHR 2 has been added a new first column with the user label associated to the physical radio port and
a new “Set Range” command as shown in Figure 247.

Figure 247. Frequency Agility screen on UHR 2.
The operator can set the frequency configuration as for UHR 1. As before, if no selection is performed,
all buttons, “except “Close” and “Help” , are insensitive. Select an item of the scrolled matrix, that makes
the entire row selected and then click on the “Set Range” button to modify the Frequency Range Value.
Figure 248. opens.
Figure 248. Frequency Range Dialog box

1AA 00014 0004 (9007) A4 – ALICE 04.10
Initially the “ Frequency Range ” screen shows the present TX frequency range values.
3AL 89062 AA AA 404 / 926
926
In this screen is possible to modify TX frequency range values by up–arrow and down–arrows (with step
of 0.01 Mhz) or by writing directly in field.
The new values are considered when “Ok” button is pressed.

If the operation is correctly performed, a confirmed message box is shown. Immediately a new data is
sent to NE updating Min Freq (KHz) and Max Freq (KHz) in Figure 247.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 405 / 926
926
11.10 POWER MEASUREMENT
From the Radio menu select the “Power Measurement” on UHR 1 or the “Power Measurement”
–>“Graphic Power Meas” on LHR 1 and UHR 2 menu option to open Figure 251.

Figure 249. Power Measurement menu on UHR 1
Figure 250. Power Measurement menu on LHR 1 and UHR 2

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 406 / 926
926
Figure 251. Power Measurement dialog box example
Select the physical “Radio Port” on which the measurement has to be performed. Entry the new “Days:
0, Hours:0 , Minutes: 0” numbers editing the wished Days, Hours, Minutes values (this value has to be <=
to the maximum one= 7 days). In the “Sample Time” select the measurement sampling time wished among
2, 6, 30, 60 sec.
The user can memorize all the measurements sampled in a log file selecting “Create file”; the log file
records the measurement until a maximum dimension (7 days for 2 sec. sample time) . The “Log file” field
shows where the file is stored. The user can select, with the “Select file” button, a different directory and/or
a different creation file name.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 407 / 926
926
Figure 252. Power measurement dialogue box with the “Log file” indication
Clicking on “OK”, a warning with a confirmation message is shown (see Figure 253. ).
Figure 253. Warning/Confirmation message
After confirmation the Figure 254. opens.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 408 / 926
926
Figure 254. Example of Graphical power measurement window
The Power Measurement Graphic is available only if the USM is connected to NE.
The screen above shows the current TX and Rx performance related to the two linked NE. Every window
correspond to a single NE channel.
When the screen is showed the operator is able to see the curves following the real time values of power
transmitted by the local and remote transmitters (TX) and moreover, the values of power received by the
remote and locale receivers (Rx).
The top graphic screen size shows the TX curves (local and remote), while the bottom size shows the Rx
curves (local and remote). Note that the colors represent the linked end–point of the two NE; if the local
TX is blue, for example, the remote receiver has the same color.
The top of the screen offers all the characteristics present in the current measurement:
– the radio port item gives the symbolic name associated to the radio channel that you are analyzing
– the sample time item indicates the frequency used to send the measure requests to NE;
– the start time item is the first request time;
– the stop time item is the interval time selected in the previous parameters window, added to start time;
– time item is the current response time;
– Log File item is the complete pathname of the file where the received values are stored.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 409 / 926
926
By clicking on “show details” square, on the left side on Power Measurement Graphic ( see Figure 254.
on 409), a new table appears ( Figure 255. on page 411 ); this table shows the following relevant values
of the received and transmitted power:

– TxLoc

• max TX local value and date when this value was received for the first time.
• min. TX local value and his current date when this value was received for the first time.
• current TX local value and his current date.
– TxRem
• max TX remote value and date when this value was received for the first time.
• min. TX remote value and his current date when this value was received for the first time.
• current TX remote value and his current date.
– RxLoc
• max Rx local value and date when this value was received for the first time.
• min. Rx local value and his current date when this value was received for the first time.
• current Rx local value and his current date.
– RxRem
• max Rx remote value and date when this value was received for the first time.
• min. Rx remote value and his current date when this value was received for the first time.
• current Rx remote value and his current date.
– RxLocDiv
• max Rx local diversity value and date when this value was received for the first time.
• min. Rx local diversity value and his current date when this value was received for the first time.
• current Rx local diversity value and his current date.
– RxRemDiv
• max Rx remote diversity value and date when this value was received for the first time.
• min. Rx remote diversity value and his current date when this value was received for the first
time.
• current Rx remote diversity value and his current date.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 410 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 255. Details Dialog box example
926
3AL 89062 AA AA
411 / 926
11.11 Power Measurement File Reading
To read the measurement file select the “Power Meas File Reading” on UHR 1 or “Power Measurement”
–>”Power Meas File Reading” on LHR 1 and UHR 2 menu option to open Figure 257.

Figure 256. Power Meas. File Reading menu example ( on UHR 1 ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 257. File Chooser dialog box
3AL 89062 AA AA 412 / 926
926
Enter in the editing “Choice” field the file name and its path. To visualize all files of a directory enter in
the “Filter” field” the path address followed by an * (asterisk) . Moving to a new directory, select in the left
field, the directory name and the file name by selecting the corresponding file to open, in the right field.
Figure 258. File reading output
Click on “Apply” to open Figure 258. The user can move into the file reading with the arrows reported on
the bottom frame window ( see Figure 259. ).
Move to the end of graphical diagram following the arrow indication
Move to next page following the arrow indication
Move to next measurement following the arrow indication
Figure 259. Arrows navigation on the graphical file reading

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 413 / 926
926
11.12 Squelch Management on LHR
Select the Squelch option in the Radio menu to activate the squelch actions

Click on the “CooseRadioPort” button to open Figure 262. Select the channel radio port and click on OK

to fill in the “Channel” and the “Radio Port” information as shown in the example of Figure 260. Using this
dialog box the user can configure the squelch action in the Main, Diversity and Reused channel by clicking
on the relative square button. Select OK to confirm the operation
Figure 260. Squelch management dialog box
When the squelch has been activated the AC (abnormal condition) will be signalled on the NE–USM (see
para. 11.15).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 414 / 926
926
11.13 Gain Management on LHR 1.0, UHR 2.0 and UHRN 2.0
Select the Gain option on the Radio menu to open Figure 261.
Figure 261. Gain management box dialog
Click on the “ChooseRadioPort” button to open Figure 262.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 262. Choosing radio port
3AL 89062 AA AA 415 / 926
926
Select the radio port channel and click on OK to open Figure 263.

Figure 263. Gain box dialog with the selected channel
If a manual operation is active, “Stop Manual” button is enabled and the toggle “Manual Operation in Pro-
gress” is checked. The “0” value in “Gain Level” means that the related receiver is set in automatic gain
mode. The operator can modify the Gain Level value editing a new one. If the NE supports the “Space
Diversity” , also the Gain Level related to the diversity can be modified. If the Space Diversity is not sup-
ported the field Gain Level Diversity is not visible. Click on Apply to confirm the operation or select the
Stop Manual button to come back from manual to automatic gain mode. In manual operation the AC (ab-
normal condition) will be signalled on the NE–USM (see para. 11.15).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 416 / 926
926
11.14 Hop Trace Management on LHR
The function can be performed only if the RPS capability is supported by the NE.
Select the “Hop Trace” option of the Radio menu. The Hop trace function can be considered as a path
trace applied to the radio section.
Click on “ChooseRadioPort” button to open Figure 262. Select the channel radio port and click on OK
to fill in the Channel Radio Port information as shown in the example of Figure 264.
Both the “Expected” and the “Transmitted” fields are editable by the operator. if a mismatch is detected
an alarm is generated. Actually this functionality has not yet well defined.
Figure 264. Hop Trace dialog box with the selected channel
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 417 / 926
926
11.15 Radio Abnormal Condition on LHR 1.0, UHR 2.0 and UHRN 2.0
Select the Radio Abnormal Condition List option from the Radio menu and select the “Choose Radio
Port” button which allows to choose the radio port; then after pressing “ OK “ button the fields “ Channel:

” and “ Radio Port: ” are filled with the chosen radio port information and the related abnormal condition

list will be listed as shown in Figure 265.
Figure 265. Radio abnormal Condition list example
The Radio Abnormal Condition in Rx / Tx for manual operation are:
RX Manual Operation :
– No One
– Gain Control
– Main Rx Squelched
– Div Rx Squelched
– Reused Signal Squelched
TX Manual Operation :
– No One
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Power Control
– Unmodulated Carrier
– Tx Squelched
3AL 89062 AA AA 418 / 926
926
11.16 Frequency Reuse on LHR and Carrier Status on UHR and UHRN 2.0
This function is enabled only if the NE. supports the frequency reuse. That is if the radio modem (RMD
on UHR and UHRN) is equipped with the XPIC daughter board. In the frequency reuse two channels asso-
ciated transmit the signals at the same frequency but with a different polarization mode (main or reused)
Select the available Frequency Reuse / Carrier Status option on the Radio menu to open Figure 262.
Select ChooseRadioPort button which allows to choose the radio port ( see Figure 262. ) and click on OK
to fill in the Channel Radio Port information as shown in the example of Figure 266.
Figure 266. Frequency Reuse dialog box example
The Carrier Status dialog box displays the Carrier Status and the relative Channel: if the channel transmits
with a “main” polarization the associated one will transmit with a “reused” polarization.
The Frequency Reuse dialog box displays the following more other information:
– Associated Channel
– NE User Label
– NE Location Name
In the “Associated Channel” field the operator can enter the associated channel information, taking into
account that the Associated Channel has to be considered as the priority protection channel.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 419 / 926
926
11.17 Equalization Delay on LHR
Select the “Equalization Delay” command on the Radio menu to open Figure 262. Select the channel
radio port and click on OK to fill in the Channel Radio Port information as shown in the example of

Figure 267.

Figure 267. Equalization Delay box with the radio port channel
By means of this screen the operator can set equalization delays for the main, diversity and the reused-
channels either in automatic mode or in manual mode.
The automatic mode is performed by pressing the “Auto” button, in such a way the values in the fields
“Main” and “Reused“ are not taken into account and automatic delays are computed and shown in the
fields at the end of the procedure.
The manual mode is performed by setting the delays in the fields and pressing “Set”. In case of Frequency
Reuse the delay may by applied only to one way: main or reused, so if the two set delays are both different
from 0 the operation is refused.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 420 / 926
926
11.18 V.C.O. (Voltage Control Oscillator) Management
– On LHR 1.0
Select the “Voltage Control Osc. Status” option in the Radio menu to open Figure 268.
Figure 268. VCO Status window on LHR
This window is a read only dialog box with four columns:
– the first column contains the Channel number associated to a physical radio port .
– the second column contains the user label associated to a physical Radio Port .
– the third column contains the V.C.O. Role ( Master or Slave ).
– the fourth column contains the indication of actual Status ( Internal or External ). For the “Master”
the Status is always Internal
– On UHR 2.0 and UHRN 2.0
On UHR and UHRN NEs a different dialogue box appears ( see Figure 269. on page 421 ) with three col-
umns scrolled matrix:
– the first column contains the channel number associated to a physical radio port .
– the second column contains the user label associated to a physical radio port .
– the third column contains the V.C.O. Protection Status ( StandBy or Active ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 269. Voltage Control Oscillator screen
3AL 89062 AA AA 421 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
422 / 926
12 PORT VIEW
This section describes the operations necessary for the consultation, modification and configuration of
ports.
The Port View permits to set and show the transmission resources (i.e. the Termination Point, TP) referred
to the specific Port; it permits to check the detailed alarms presented by each TP of the Port, and the
available menu permits to configure the port (many setting options listed in the port menu are common
with the “Transmission” view).
There are different port view according to the considered TPs.
• SDH port view

with the TPs from the physical SDH interface up to AU4–CTP. This visualization permits to
check the TPs related to STM1/N signal before the HPC (high order path connection) matrix:
The considered TPs are:
Electrical or Optical SPI TTP, RS TTP, MST TTP, prot TTP (MSP TTP), AU4 CTP, Trail Monitor
(only with enabled POM)
• HOA port view

with the TPs from the HPC matrix up to TUxx, that is before the LPC (low order path connection)
matrix. The considered TPs are:
VC4 TTP, TUG3, TUG2, TU3, TU12, Trail Monitoring (only with enabled POM)
• PDH port view

with the TPs from the physical PDH interface up to VCxx–TTP. The considered TPs are:
PPI TTP, En CTP, VCn TTP
• ATM port view

missing the physical ATM interface the ATM signal has to be considered only for the its
incapsulated part into VCxx or 34 / 2 Mbit/s signal. The considered TPs are:
VC4C TTP, VC4 TTP, VC3 TTP, VC12 TTP, S31 TTP, E1 TTP
The Port View can be accessed from the Equipment or Transmission Views.
The “Port view” is reached selecting the Equipment option in the View pull down menu to present the
subrack view, as described in chapter 7.1 on page 211.
Double clicking on the selected board the relevant Board view is available presenting the ports).
By double clicking on a board view, the corresponding port view is opened (see Figure 270. ).
The “Port view” is also reached selecting the Transmission menu and then the Navigate to a port view
option.
The HOA port view can only be reached from the Transmission view, selecting a VC or TU TP.
The ATM TPs are not automatically created when the board is inserted in the subrack but must be created
using a dedicated procedure.
From the Port view it is possible to Navigate to Transmission view.
The messages displayed at the top view in the form of message boxes provide other information
concerning the physical port type. On the other hand the messages displayed at the bottom provide
information about MSP protection and ALS state ( if they are supported ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 423 / 926
926

)


Alarm icons
, )' )

Termination Point
Port functional state information message area
Figure 270. Example of a Port View
A message under the mouse facility provides the alarm name and the physical port type. This message
appears in the message area at the bottom left corner of the view.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 424 / 926
926
12.1 View Elements
The symbols of the TPs (see Figure 271. ) have the following meaning:
– Alarm Icon Area

The icon boxes represent alarms. The color of the boxes changes according to the alarm severity.
– Performance state
If the condition of the resource is under performance monitoring, an icon with a P appears below the
box.
– Loop state
If the condition of the resource is under loop, an icon with a L appears below the box.
– Cross-connected state
If the condition of the resource is cross-connected, an icon with a X appears below the box.
– Selected state
An orange frame around the box identifies a selection .
– TP identifier
The TP label within the port view that identifies the port functional block.
– TP Role
The icon boxes represent the function: Adaptation, Termination or Compound Adaptation and
Termination.
Alarm icon area
G.783 TP Role
(Termination)
TP identifier
Selection indication
Crossconnected state
TP under Performance monitoring
Figure 271. Example of a termination TP box.
Other additional elements using G783 TP icons can be visualized (see Figure 272. ):
– RX Alarm Icon Area

The icon boxes represent Rx alarms. The color of the boxes changes according to the alarm severity.
– TX Alarm Icon Area

The icon boxes represent Rx alarms coming from the opposite side . The color of the boxes changes
according to the alarm severity. The alarms CPB (Protection Blocked) and CCB (Connection
Blocked) are not updated when the alarm is cleared.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Internal Loopback active

the loopback is represented by an arc between the RX and the TX side of the functional block.
3AL 89062 AA AA 425 / 926
926
RX Alarm icon area

G.783 TP Role (Termination)
G.783 Functional block acronym
TX Alarm icon area
Crossconnected state
Figure 272. Example of G.783 Termination TP box.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 426 / 926
926
12.2 Port View Commands
The SDH telecommunication networks are Opto–electronic networks involving considerable optical
technology and in particular laser and fiber optic technology. The configuration of laser ports, managed
by the SDH Manager, is necessary for safety reasons.

The Port View chapter describes the following main options:
– Optical Laser Configuration / Show Optical Configuration

– Automatic Laser Shutdown Configuration
– Single Fiber Configuration
– Loopback
– AU4 Concatenation
– Ms Configuration
– PDH Line Length Configuration
– Set Retiming
Besides Port menu permits to “Show the supporting board” from any port type and to “Navigate to
Transmission View”. Particular port view commands concerning the 1540PO access interface and the
WDM NEs are also here reported. The remaining port view commands are described in other parts of the
handbook.
The available commands for the “Port View” menu are indicated, for the different USM types, in the “Menu
Commands” chapter 2.3 .
12.2.1 Optical Laser Configuration / Show Optical Configuration
This command permits to get detailed information on the optical characteristics of the port that is
visualized.
Firstly select an optical board and then click on Optical Laser Configuration option from the Port and
Physical media pull down menu to visualize the parameters of the selected optical port.
Figure 273. shows the parameters of the selected interface.
N.B. This dialogue box can only be read. You cannot write in the entry boxes.
In the SDH Manager, the laser ports are identified by three major characteristics:
– STM Level: describes the input/output optical interface types: STM1/4/16....
– The wavelength of the laser source: the units are nanometers (nm = 10–9 m).
– The use of the port: describes whether the laser port is used for intraoffice transmissions on long
distances (Long Haul 40 km) or for infraoffice transmissions on short distances (Short Haul
15 km).
The Colored Interface Parameters section is relative to the Colored Optical interface. The Channel is
the channel number: 195, 200, 205,... Any channel is associated to a frequency. So for example the
channel numbers 200, 205, 210,... are associated to 192.000, 192.050, 192.100,...THz.(Tera Herz
=1012 Herz). Grid is the distance between two channels. That value is normally expressed in Giga Herz
(106 Herz). Common values are 50, 100, 200 ,...Giga Herz. The FEC (Forword Error Correction), when
available, can be enabled (or disabled ) to improve the channel service.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 273. shows the parameters of the selected interface.
3AL 89062 AA AA 427 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
To close the dialogue box click on the Cancel push button.
Figure 273. Visualizing a port optical parameters
926
3AL 89062 AA AA
428 / 926
12.2.2 Automatic Laser Shutdown Configuration
The aim of this paragraph is to describe the optical port hence the laser sources.
Automatic laser shutdown (ALS) is useful in case of a loss of communication between two NEs due to
optical fiber breakdown. For security reasons it may be necessary to shutdown the laser to enable the
fixing of the communication link.
The automatic laser shutdown function can only be configured from the optical ports of the equipment.
Select the Port pull down menu and the SPI block in the port view. Select the Physical media option and
then from the cascading menu the Als Management option .
With the USM 3.x and 4.x, when the ALS function has not been created, the Automatic Laser Shutdown
State dialogue box (Figure 274. ) shows only the “Create” option available ( all the ALS commands are
greyed ). Select the Apply button to open Figure 275. With the new USM 5.x , 6.x and 7.x, selecting the
Als Management option, Figure 275. opens.
Figure 274. Automatic Laser Shutdown Configuration

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 429 / 926
926
Figure 275. Automatic Laser Shutdown Management
The dialogue box enables the Als Management and the Restart parameters. The following actions are
available:
a) Enabling Automatic Laser Shutdown (this is the default ALS function)
To enable the automatic laser shutdown functionality, select the ALS Enabled option of the ALS
Function: option button.
b) Forcing the Laser to start or stop.
When the laser is forced to ON or OFF, it is restarted or stopped and the Automatic Laser Shutdown
is disabled, if it was not already so.
5) Force laser ON.

To carry out a laser forced ON, select the Laser Forced ON option of the ALS Function: option
button.
From the confirmation dialogue box that opens you can confirm or cancel the operation using
the Apply or Close push buttons.
6) Force laser OFF.

To carry out a laser forced OFF, select the Laser Forced OFF option of the ALS Function: option
button.
From the confirmation dialogue box that opens you can confirm or cancel the operation using
the Apply or Close push buttons.
c) Delete
this option deactives the ALS function, returning to the state of Figure 275. with the “ALS Function”
1AA 00014 0004 (9007) A4 – ALICE 04.10
Create indication and all the other fields disabled (greyed).
3AL 89062 AA AA 430 / 926
926
d) Enabling or Disabling Automatic / Manual Laser Restart (only applicable to W/OMSN).
To enable (disable) an automatic laser restart following an automatic laser shutdown (restart), select
the Enabled (Disabled) option of the ALS Auto Restart. The laser will be periodically ON for 2 secs
and OFF for 70 secs.The same procedure is applicable for the ALS Manual restart : while the auto
restart is disabled, the manual restart permits to perform a laser restart for a single time period.
e) Wait to restart time (only applicable to W/OMSN)
The Wait To Restart Time: field indicating the delay period in seconds, occurring before an
automatic laser restart is launched (following an automatic shutdown). If the feature is supported,
this delay can be edited in the relative field (secs.). Actually the restart time period for ADM 1664
R.3.1/2/3 equipment is fixed to 70 secs.
f) ALS Manual restart
When the ALS Manual Restart is Enable it is possible to enter two different commands: Manual or
Test Restart. If the feature is supported, the manual command immediately activates a single laser
pulse of about 2 s. to trigger the laser at the far end. This command overrides the wait to restart
time. The test restart is similar to the manual restart but the laser remains “ON” for about 90 s. in
order to measure the sent optical power.
When all the different parameters have been configured, select the Apply button to confirm the setting
and close the dialogue box. The Close button allows you to cancel the choices made.
Note that the ALS procedure is activated ( if enable ) only when the fiber has been interrupted. The ALS
state has not to be confused with the laser state.
ALS states and Laser state (see example of Figure 276. ), displayed by the functional state message area
of the optical port, are:
ALS Current State:
Inactive or Off = The ALS has not been activated ( is Off ) or the laser has been Forced ON/OFF.
In test = The laser restart has been activated .
Active or On = The ALS has been activated ( is On ).
Undefined = The ALS is not present (not created).
Laser Current State:
On = all OK or the laser is” in test” or ALS not present (not created).
Off = Laser off (when ALS is created).
Forced On = Laser forced on by operator command.
Forced Off = Laser forced off by operator command.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 276. ALS and Laser current state (example)
3AL 89062 AA AA 431 / 926
926
12.2.3 Single Fiber Configuration (only available for W/OMSN)
The single fiber configuration can be realized with passive optical couplers (see Figure 277. )

The optical coupler must not loop the Tx signal onto the local Rx .

For this purpose and in general to avoid a low Tx/Rx decoupling also when the optical line is interrupted,
an identification label has been assigned to the local Tx side ; the Rx part in the remote receive side checks
the congruency between the received and the expected labels. If a signal label mismatch is recognized
on the received section, an alarm (AIS and RDI) will be generated. Example of Figure 277. shows that
is accepted the label “1” from Tx1 to Rx2 while is accepted label “2” from Tx2 to Rx1.
Tx1 Label : 1 Tx2 Label : 2
Tx1 Tx2
Single bidir
OPTICAL OPTICAL
PASSIVE PASSIVE
COUPLER COUPLER
Rx1 Rx2
Rx1: accepted label=2 Rx2: accepted label=1
Figure 277. Bidirectional Transmission on a single fiber

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 432 / 926
926
Select RST icon and click on SDH Single Fiber Configuration of the Port–Physical Media menu option.
Figure 278. opens. The following fields have to be considered:

• Allow Single Fiber – select the transmit mode on the single fiber (enable or disable).
• Transmitted Media Byte – assigned label to Tx (0–14).
• Transmitted Media Type – overhead byte used for the communication:
– S1 byte of Multiplex Section (the part not used for the SSM) or
– Media Dependent byte of Regeneration Section
• Received Section –
– Received label
– Expected label (0–14)
Figure 278. Single Fiber Configuration View

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 433 / 926
926
12.3 Loopback
Loopbacks provide maintenance facilities. The operator can measure the system capability of handling
the transmission signal. The system sends a signal to the port/TP via the transmission line and loops it

back via the same line. During the network installation or maintenance operation, the line/equipment

functionality is checked by detecting the transmission failure through the absence of the return signal. The
loopbacks can be applied at line (external to equipment) level or at internal equipment level. The loopback
architecture provides four configurations ( see Figure 279. ):
Line Loopback And Continue
Line Loopback And AIS
Internal Loopback And Continue
Internal Loopback and AIS
Initial Destination
Line Internal Line
Destination AIS Initial
Line Loop And Continue Line Loop And AIS
Destination Initial AIS
Line Internal Line
Initial Destination
Internal Loop And Continue Internal Loop And AIS

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 279. Loopback configurations
3AL 89062 AA AA 434 / 926
926
12.3.1 Line and internal Loopback
The line and internal loopback are only allowed, if there is no DCC channel connected to the
board, otherwise the SH may loose not only the traffic but also the network NE control
(...LAPD...).
For the “Line Loopback” the incoming signal of a line is transferred directly to the outgoing direction of the
I/O port on the same line. The objective is to minimize the equipment through which the signal passes.
Therefore, line loopback sometimes referred to external loopback, can be used to test the parts of the
system that transport a line signal between the system connector (station wiring panel) and the I/O board.
The internal loopback is a port-oriented type of transmission signal loopback. The whole transmission
signal coming from the I/O port through the matrix is looped back to the input side of the system by passing
as much of the I/O port equipment as possible.
N.B. Internal and line associated TP loopbacks are different for any considered Q3NEs. The user
has to follow the loopback procedure described in the proper CT Manual.
For the W/OMSN family the line/internal loopback are supported on the following associated TPs:
a) SDH STM1, STM4, STM16, STM64 Boards (EIS is only for electrical STM1 board)
– EIS / OpS for SPI –> Line Loopback
– MST for SDH TTP –> Internal Loopback
b) PDH Boards
– P for 2/34/45/140 Mbit/s PPI –> Line Loopback
– px for pxCTP (x=12 for 2Mbit/s Interface, x=3 for 34/45 Mbit/s Interface, x=4 for 140 Mbit/s
Interface) –> Internal Loopback
The loopback configuration (on new NEs equipment) can be done only on SDH ports
ending with “ N” (i.e. P4S1N, S–4.1N, L–4.1N, L–4.2N, SYNTHN, etc.)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 435 / 926
926
OMSG family
For OMSG the line/internal loopback are supported on the following Ports:


!
(>% B

A63
(>%C>" (

8" D;943 """#"#"#
(>% B

A56
(>%C>" $)
(>%
A3 "( B "(
(>%C>"
(>%
A5 "( B "(
(>%C>"
Table 13. OMSG SDH Loopback
Table 13. is valid for VC-4, VC-4-4c, VC-4-16c, VC-4-64c signals.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 436 / 926
926
"##

!
(>%
*56 $)
(>%C>"
(>%
*5 B
(>%C>"
(>% B

53< )
(>%C>" $)
(>% B

83 )
(>%C>" $)
(>% B

9 )
(>%C>" $)
Table 14. Supported Loopback Types Dedicated I/Os
a) The associated TP to SDH STM–N Board (see Table 13. and Table 14. ) is:
– EIS / OpS for SPI (except for dedicated STM16 I/Os)–> Line and Internal Loopback
b) The associated TP to PDH Board is:
– P for 2/34/45/140 Mbit/s PPI –> Line Loopback
– P for PPI (except for P63E1 I/Os)–> Internal Loopback

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 437 / 926
926
12.3.2 Loopback Configuration
Select a TP that supports the Loopback Configuration and from the port menu or the transmission menu
click on the “Port Loopback Configuration” option (see Chapter 2 “Menu Commands”) to open Figure 280.

Figure 280. Example of Port Loopbacks View on OMSG
Choose the TP clicking on the “Choose TP” button. Select the TP where to apply the loopback command.
For the TP selection procedure, follow the TP research description reported in the “Transmission View”
chapter. Only one termination point has to be entered, the second one is automatically inserted or
disabled.
Timed loopback cannot be configured in the current release. The default value “0” indicates that no timed
loopback has been configured. Click on “OK” and then click on the confirmation push button (USM 5.x
...) to apply the loop back configuration.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 438 / 926
926
To configure Loopbacks for more than only one TP, click on the TP list of Figure 280. (on OMSG) button
and open the Clipboard dialog. For a description of this dialog see Chapter Clipboard. Press Apply to
apply the parameters and leave the dialog box open. The Ok button invokes the commands according to
the user selections and the wait cursor appears until the operation is completed. The dialog then
disappears.
The Cancel button closes the dialog and discards any changes.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 439 / 926
926
12.3.3 Loopback Management
To manage the loopback configuration click on the “Loopback Management” option (see Chapter 2 “Menu
Commands”) to open Figure 281.

To display the loopback list and update it, click on the “Search” button.
The configured loopbacks are listed in the current loopbacks table. The commands utilized are: “Search”,
“Delete” and “Create”.
– To configure the filter select the “Loop and Continue” type (Yes= Loop And Continue, No= Loop And
AIS), then select the “Directionality” Internal or Line and edit the Initial TP Id (write: rack, subrack,
board, port# and the TP type ( see Cross–Connection Management chapter, “Search Criteria” para.).
For “Initial TP” has to be intended the outgoing signal while for “Destination TP” the incoming
signal. Enable the filter through the “Toggle Filter” Enable/Disable button. Click on the “Search”
button to start the configured loopback research into the current loopback table.
– The “Create” command permits to create a new loopback configuration: clicking on “Create” , the
previous figure ( Figure 280. ) opens. Follow the previously paragraph indications to create a new
loopback configuration.
– The “Delete” command permits to delete a loopback listed in the Current loopbacks Table: select a
loopback in the list and click on the “Delete” button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 281. Example of Loopback Management View (on OMSG)
3AL 89062 AA AA 440 / 926
926
N.B. For OMSG the Loop And Continue column could be empty even if a “loopback and continue”
has been created.
On OMSG the filter criteria can be saved by clicking Preferences. A detailed description can be found in
Chapter 3.7.
The Close button closes the dialog.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 441 / 926
926
12.4 Concatenation Procedure
The concatenation and deconcatenation functions are availabe in the Transmission view and Port view.

AU-4-4c:

AU-4-4c concatenation can only be performed according to a special schema: 4 AU-4 CTPs in a row
can be concatenated to one AU-4-4c CTP. Therefore, the concatenation function can only be applied
to AU-4 CTP#1, AU-4 CTP#5, AU-4 CTP#9 and AU-4 CTP#13, ... .
AU-4-16c:
AU-4-16c concatenation can only be performed according to a special schema: 16 AU-4 CTPs in a
row can be concatenated to one AU-4-16c CTP. Therefore, the concatenation function can only be
applied to AU-4 CTP#1, AU-4 CTP#17, AU-4 CTP#33 and AU-4 CTP#49 on STM-64 boards.
AU-4-64c:
AU-4-64c concatenation can only be performed according to a special schema: 64 AU-4 CTPs in a
row can be concatenated to one AU-4-64c CTP. Therefore, the concatenation function can only be
applied to AU-4 CTP#1.
The AU-4-4c , AU-4-16c and AU-4-64c CTP streams support the alarm synthesis, cross-connection
states and performance monitoring information as standard AU-4 CTP streams.
12.4.1 Concatenation on OMSG
Port / Transmission
...
AU4 Concatenation >

Concatenate 4
...
Concatenate 16
Concatenate 64
Deconcatenate
N.B. The following restriction apply to the concatenation function in the current release:
– The concatenation function is only available on the Common I/O boards of the 4/1 OMSG and
4/4 OMSG. Depending on the board type, it is possible to concatenate groups of four AU-4 CTPs to
AU-4-4c CTPs and to concatenate groups of 16 AU-4 CTPs to AU-4-16c CTPs (on STM-64 boards,
not supported in the current release), additionally one AU-4-16c on STM-16 and one AU-4-64c on
1AA 00014 0004 (9007) A4 – ALICE 04.10
STM-64.
– The AU-4 CTPs to be concatenated must not be cross-connected.
3AL 89062 AA AA 442 / 926
926
Procedure:
1) Select the first AU-4 CTP of the row to be concatenated (see above) in the Transmission or Port
view.
2) Select option “Concatenation -> Concatenate 4” or “Concatenation -> Concatenate 16” or

“Concatenation -> Concatenate 64” in the Transmission or Port menu. This menu option is only
enabled if the selected AU-4 CTP fulfills the above mentioned preconditions.
3) Update the view and, following successful concatenation, the concatenated AU-4 CTP icons
are deleted in the view and substituted by the new AU-4-4c CTP icon.
Deconcatenation
1) Select the AU-4-4c, AU-4-16c or AU-4-64c CTP in the Transmission or Port view.
2) Select option “Concatenation -> Deconcatenate” of the Transmission or Port menu.
3) Update the view and as a result of the successful deconcatenation, the AU-4-4c or AU-4-16c
CTP icon is deleted and the deconcatenated AU-4 CTPs are displayed again.
Figure 282. depicts an STM-16 interface with AU-4 CTP#9 to AU-4 CTP#12 and AU-4 CTP#13 to
AU-4 CTP#16 concatenated to two AU-4-4c CTPs. The AU-4-4c CTPs appear as single icons above the
AU-4 CTP row.
N.B. When a deconcatenation of an AU4–64c is ongoing, a superflous error message may pop up
though the operation will be completed successfully a couple of seconds later. The message
complains about a missing ’object instance’. Please ignore it and close the message box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 443 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 282. Example of AU-4-4c CTP in the Transmission View
444 / 926
12.4.2 Concatenation on W/OMSN
Select a STM4/16/64 optical interface to configure the AU4 concatenation structure. Click in to open the
port or the transmission view and then , If the NE equipment supports this feature (not grey), select the
AU4 Concatenation menu option. Figure 283. opens

Not all AU4s can be chosen as first AU4 but for a STM–64 only the following groups:
– AU4#1, AU4#5, AU4#9, AU4#13, AU4#17.....AU4#57, AU4#61 for AU4–4c
– AU4#1, AU4#17, AU4#33 and AU4#49 for AU4–16c
– AU4#1 for AU4–64c
If a STM16 board has been selected, the STM16 stream appears divided into the following groups:
AU4P#01, AU4P#05, AU4P#09, AU4P#13 for AU4–4c or AU4P#01 for AU4–16c. Therefore for
concatenated action of four AU4s in one AU4–4c or of sixteen AU4s in one AU4–16c these AU4 streams
are deleted and substituted by the new AU4–4c/AU4–16c component.
Select the supported concatenation Number =4 (or 16 or 64) to visualize the available group/groups then
select the group to concatenate and click on the Concatenate push button. Click on the Cancel key to
exit and come back to the previous window.
Figure 283. Example of AU4 concatenation groups for STM–16

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 445 / 926
926
Selecting a STM16 board the Figure 283. will visualize the 4 AU4P groups for AU4–4c or , if supported,
1 AU4P group for AU4–16c. Selecting a STM64 board the AU4 will visualize 16 AU4P groups for AU4–4c
or 4 AU4P groups for AU4–16c or 1 AU4P group for AU4–64c. The Concatenate button will be enabled
and the Deconcatenate button will be disabled when is selected a non concatenated AU4, viceversa

when is selected a concatenated AU4–4c / AU4–16c / AU4–64c.

Figure 284. Example of a AU4c in the port view
The port view represented in Figure 284. shows an STM16 interface with the first four AU4 concatenated
in one AU4c. The AU4c appears as a single icon that has the same position of the four AU4 blocks.
To deconcatenate a AU4c/AU16c/AU64c select again the “AU4 Concatenation” option and then select
the AU4c/AU16c/AU64c group to deconcatenate (see Figure 285. ). Click on the Deconcatenate push
button to apply the command or on Cancel to exit.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 446 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
Figure 285. Example of AU4 deconcatenated command
3AL 89062 AA AA
447 / 926
12.5 Ms Configuration
Port
Als Management

... Show Optical Configuration
Physical Media >
... Regenerator Section Management
MS Configuration
Set Domain
This dialog enables configuration of the Section Supporting Bit and Force AIS on MSTTPs ( on OMSG
this feature is only available for the Common I/O boards).
Section Supporting Bit
To enable SDH/SONET inter networking, different coding for the transmitted SS-Bits is provided (bit 5+6
of the H1 byte in the AU-4 pointer):
– SDH: provisioned with 10 code

– SONET: provisioned with 00 code
Select the MSP TP.
Click on Ms Configuration menu option of the Port menu. Figure 286. opens.
Configure SDH or SONET coding by enabling the related radio button.
N.B. If the port hardware does not support this feature, the area in the dialog is grayed out, while one
radio button is still selected.
N.B. All AU-4 CTPs or AU–4–4c CTPs of the same signal (e.g. of an STM-16 signal) are set together
to the same code.
Force AIS
Insert forced AIS on MSTTP by enabling the check button.
Ms Forced AIS is not supported in many NEs managed by the current SH release.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 448 / 926
926
Figure 286. MS Configuration Dialog displayed on OMSG
To configure the MS for more than only one TP, click on the TP list... button and open the Clipboard dialog.
For a description of this dialog see Chapter Clipboard. Press Apply to apply the parameters and leave
the dialog box open or OK to apply the parameters and close the dialog box or Close to close the dialog.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 449 / 926
926
12.6 PDH Line Length Configuration
To manage the Line Length configuration click on Line Length Configuration menu option of the
Physical Media menu. Figure 287. opens.

This dialog allows to configure the line length 0 ... 225 feet, 250 ... 450 feet for a PDH PPI TP of a 45
Mbit/s port.
Confirm the configuration with the OK button. Use the Cancel button to close the dialog without saving
changes to the current configuration.
The OK button validate the configuration and close the dialog box.
The Cancel button removes the dialog
Figure 287. PDH Line Length Configuration View

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 450 / 926
926
12.7 Set Retiming
The Retiming feature applies to the outgoing 2 Mbit/s and its purpose is to absorb the jitter /wander that
is transferred to the PDH signal when SDH pointer justification occur. The feature is set individually per
port
Select a 2Mbit/s port and zoom in to open the port view.
When the Retiming feature is disable, the color of the state information at the bottom of the window is brown
and the label “Retiming State Disable” is written.
Select the Set Retiming–>Enable option from the Port menu (see Figure 288. )
Figure 288. Set Retiming enable (before)
As result of this operation the state information color become green and the label “Retiming State Enable”
is written (see Figure 289. )
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 451 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 289. Set Retiming enable (after)
926
3AL 89062 AA AA
452 / 926
12.8 Show Supporting Board
Click on “Show Supporting Board” of the Port menu to navigate to the board that supports the selected
port view.
Figure 290. opens.
Administrative State:
In Service/
Receiver Failure Out of Service
Replaceable Card not
Unit Missing responding
Out Of Range Replaceable Unit
Laser Output Type Mismatch
Version Mismatch
High Laser Temperature
Figure 290. Board View Example.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Some board view supports the EPS management. In this case will be visualized the EPS: Protection Role,
Protection Status, Switch Type. Different alarm indications will be visualized on the boards of other NE
equipment.
3AL 89062 AA AA 453 /
22
12.9 Navigation Commands in Port View
12.9.1 Navigate to Transmission View

Select a TP.
Click on Navigate to Transmission View menu option of the Port menu to navigate to the corresponding
Transmission View that is related to the selected TP.
Navigation to the Transmission view permits to show a complete overview about the signal flow as for the
example of the following figure.
Figure 291. After “Navigate to Transmission view” selection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 454 /
22
12.9.2 Navigate to Equipment Overview (available on OMSG)
Select the port menu command to navigate to the Equipment Overview window.
12.9.3 Navigate to MSP Related Unit (available on OMSG)
Select the port menu command to navigate to the related MSP unit at the same Port view window.
12.9.4 Navigate to Msspring View (available on OMSG)
Select the port menu command to navigate to the Msspring Configuration for the selected TP in the Port
View.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 455 /
22
12.10 Port View Configuration for 1540 PO
The 1540PO Rel. 2.3 access equipment can be equipped with HLTCA / HLTCB boards (see Figure 292. )
each one containing two / four HDSL interfaces. The 1540 Rel.2.3 can be equipped with 11 HLTCA for

a maximum of 21 HDSL interfaces or 13 HLTCB boards for a maximum of 13x4=52 HDSL interfaces. Click

on the HLCTA/B and HDSL board to open the HDSL Port View (see Figure 293. ).
Figure 292. 1540 PO equipment view example

1AA 00014 0004 (9007) A4 – ALICE 04.10
The HDSL port view shows the Physical Media menu associated both to NE master and NE slave (NT
= network terminal ).
3AL 89062 AA AA 456 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Click on HDSL Configuration. Figure 294. opens
926
Figure 293. HDSL configuration menu for HLTCA board
3AL 89062 AA AA
457 / 926
Figure 294. HDSL port configuration
The Pairs Number is a pre–defined parameter: one, two or three pairs number could be used to send the
2320 Kbit/s data.
If the NE master supplies the power feeding to the NT equipment, the Power Feeder will be selected “On”
otherwise the power feeding is locally distributed and the Power Feeder will be selected “Off”. In this last
case the user can choose the “Wet Current” Absent / Present . The wet current can prevent the oxidization
contacts.
On the port view the physical HDSL termination icon reports the following power alarm indications:
OCPF: Over current on power feeder, UCPF: Under current on power feeder and VUTP: Voltage
unbalance on twisted pair.
Click on the “Twisted Pair Management” option of Figure 293. to open Figure 295.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 458 / 926
926
Figure 295. Twisted pair window
In the twisted pair window there are two banks: M1 and M2. All the Status fields are not editable. They
shown the HDSL alarms, line and driver statuses.. The “Refresh” button, after a while, updates the current
twisted pair window.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 459 / 926
926
12.10.1 NT Equipment
For NT creation see Vol.1, Section 1.4: EML Construction, “Create a remote NE” chapter.

Figure 296. Map with PO and NT equipments
On NT view equipment, select Equipment–>Set option. The Create/Modify Equipment box dialog is
shown (see Figure 297. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 460 / 926
926
Figure 297. NT creation board
If the PO is equipped with HLTCA boards the NT will be equipped with 1512... boards while if the PO is
equipped with HLTCB boards the NT will be equipped with HSNT... boards; any HLTCA / B board mixture
can be provided.
Selecting a port view of a NT equipment, according to NT type, different NT configuration are available.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 461 / 926
926
Figure 298. NT Physical Media menu
Selecting the NT G703/704 Configuration (see Figure 298. ). Figure 299. opens.
Figure 299. NT port configuration for 1512... boards

1AA 00014 0004 (9007) A4 – ALICE 04.10
Now the user can choose the “HDB3 / AMI” line code and for 1512... boards also the “Active / Inactive”
frame mode configuration.
3AL 89062 AA AA 462 / 926
926
If the NT has been configured with an X21 interface the window of Figure 300. is shown.
Figure 300. X21 interface configuration window
The following fields can be configured:
– Bit Rate = N x 64kbit/s (N= 1 32). Click on the arrows to select the right “N” number.
– Usage 105 / 107 = The 105 / 107 protocols can be configured as: Managed or Fixed On. In this last
case the related bit will be fixed to “1” or to “0”.
– V13Protocol = It has been activated if the related button is dark grey. Click on the button to select
the On / Off activation.
– V38Scramble = Select the scrambler– descrambler On / Off activation ( as above ).
– Loop Status = Activating the V13 Protocol the user can request the 2b / 3c loop back configuration
1AA 00014 0004 (9007) A4 – ALICE 04.10
option for the maintenance purpose. The local “Loop Status” points out the “Loop2b Requested /
Not Requested” indication while the remote “Loop Status” signals the “Loop2b / Loop3c” “Active or
Not Active” indication.
3AL 89062 AA AA 463 / 926
926
Selecting “Display XVPI Circuit Status” option Figure 301. opens.

Figure 301. Circuit status window
Seven rows represent seven protocol communication circuits. The last two ones are the loopback circuits.
For every circuit are displayed, on the columns, twenty champions. The champtions show some
communication data between the customer premises and the NT equipment.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 464 / 926
926
– New features for NT
Three other functional blocks, P12<–>VC12<–>Tu12 , have been inserted on the NT port view equipped
with HSNT... boards.
Figure 302. Port View on NT Rel.2.3
On VC12 the user can now configure the PM new feature as a normal NE equipment (see Figure 303. ).
Some restrictions concerning the Threshold table are here applied: the PM thrshold table can not be
created / modified on the NT but only on the PO equipment.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 465 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 303. PM configuration and threshold table window on NT
466 / 926
12.11 Optical Port Configuration for WDM
The screen boxes here following described are typical for 1640WM,OPS, 1686WM and 1696WM.
12.11.1 OGPI Port View Menu
Selecting the (Optical Generic Physical Interface) “Port” option in the menu bar, the complete pull down
Port menu is presented.
When a functional block is selected, some menu options become available in the Menu bar.
The Port view menu differs according the port type.
Figure 304. OGPI Port view Menu displayed (example)
12.11.2 Show Supporting Board
This menu allows to navigate to one of the boards which supports the selected TP.
Click on Show Supporting Board menu option of the Port menu to navigate to the board that supports
the selected port view.
12.11.3 Navigate to Transmission view
Click on Navigate to Transmission view menu option of the Port menu to navigate to the Transmission
view that is related to the selected TP.
12.11.4 FEC Enabled on 1640WM and 1686WM
This option allows the operator to select either Enabled and Disabled in the FEC state configuration of
the receive side of a TRB board.
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. The PM FEC counters on an OCHA port must be removed, before removing a Tributary board
in a WADM configuration.
3AL 89062 AA AA 467 / 926
926
Enable FEC
1) Display the Port view of the TRB board you want to configure.

2) Select a OGPI, an OCH or an OCHA port.

3) Choose the Port – FEC Enabled menu option.
A tick √ near the left of the option is displayed to show that the FEC is enabled.
Disable FEC
1) Display the Port view of the TRB board you want to configure.
2) Select a OGPI, an OCH or an OCHA port.
3) Choose the Port – FEC Enabled menu option.

The tick √ near the left of the option disappears to show that the FEC is inactive.
• Allow to enable or disable the FEC correction. This option menu is present only if FEC
application is supported and on a Line Terminal equipment. In OADM Repeater this functionality
is available from the Transmission menu.
12.11.5 Display channel Frequency on 1640WM and 1686WM
• This option displays a dialog box which allows to see the associated frequency in THz of the
selected channel.
To display the frequency value of a channel from a port view:
1) Select an OCH, OCHA or OGPI.
2) Choose the Port – Display Channel Frequency menu option:

the channel frequency is displayed in THz in the dialog box that appears.
To display the frequency value of a channel from a transmission view:
1) Select an OCH, OCHA or OGPI.
2) Choose the Transmission – Display Channel Frequency menu option:

the channel frequency is displayed in THz in the dialog box that appears.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 305. 1686WM – Channel number information dialog box
3AL 89062 AA AA 468 / 926
926
12.11.6 Current Counters Values Display (for 1686WM without PM)
If the PM configuration is not available, select in a TWLA with FEC functionality and activate the port view
menu.
Pull–down the Port menu and select the Current Counters Values option.
This option displays three types of error counters:
• Number of parity error on B1 Byte

• Number of Corrected blocks
• Number of Uncorrected blocks
The different counter values are displayed on the dialog box.
Figure 306. Transmit FEC counters displayed
N.B. Values displayed on the fields are those which are occurred from the last starting up of this
window. The operator have to know the real time to assess the exact value.
When this window is opened once, a reset of all counters is done,

When the window is opened twice, the counter values display errors for this time.
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. Limit of FEC errors counters

The FEC corrected errors counters and FEC uncorrected errors fields are 9 digit long. When
the counter limit is reached, then Craft Terminal displays erroneous values.
3AL 89062 AA AA 469 / 926
926
12.11.7 Payload configuration
This option has been described in the “Board configuration for WDM” 7.9.7 chapter. on page 259

12.11.8 Shutdown criteria configuration on 1640WM and 1686WM
This option allows to perform a shutdown as consequence of incoming alarm (TRFEC_64 or REGEN_10G
on 1686WM and TRB on 1640WM).
– This option is available from an OGPI port view
This option opens a dialog box which allows to choose a shutdown or AIS generation and propagation as
consequence of incoming alarm in the Receive side of the board.
The user can select one, two or no options.
• If no option at all is selected : LOS, LOF, AMS alarms generate an AIS which is propagated on
the line;
• If one or two options are selected, a shutdown is requested when one of these events (LOS,
LOF, AMS or Incoming AIS) occurs.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The user can select one, two or neither of them options.
3AL 89062 AA AA 470 / 926
926
• If no option at all is selected : LOS, LOF, AMS alarms generate an AIS which is propagated on
the line;
• If one, or two options are selected, a shutdown is requested when one of these events (LOS,
LOF, AMS or Incoming AIS) occurs.
On the TRB30x_stm16, it is not allowed to configure the AIS option and if the operator tries to
configure it, an error message is notified. An AIS signal is always transmitted.
On the TRB50x, it is not allowed to configure the AIS option and if the operator tries to configure
it, no error message is notified. Nevertheless, the AIS signal is always transmitted.
12.11.9 Performance option
The Performance Monitoring description for 1686WM, 1696MS and 1640WM equipments can be found
in the Performance 16.7 chapter on page 644.
12.11.10 SDH Section Monitoring – Trail Monitor
This option allows to display or hide the trail section monitoring function (only available on WLA
TRFEC_64) when a functional block is selected (OGPI or OCH).
This menu item is visible only if is supported by the Equipment.
On the OGPI port view the trail monitoring capability is represented by a simple graphical block (TM)
located on the left (OGPI) or on the right (OCH) of the concerned block.
From an OGPI port the user can create or delete a trail monitor.
• The Create command makes appear the (TM) functional block,

• The Delete command makes disappear the (TM) block.
The block
manages alarms The block
associated to SDH frame manages alarms
associated to WDM line
Figure 307. 1686WM – Trail monitor block view example

1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. See the Trail monitor procedures described in the “Performance Monitoring” 16.7 chapter on
page 644
3AL 89062 AA AA 471 / 926
926
12.11.11 Path trace configuration on 1686WM
This option is available only if a Trail monitor creation on 1686WM is enabled. This option allows to read
the received J0 and configure a J0 to send . It is divided in two parts:

– Introduction,
– Procedures.
The J0 path trace allows to read the received J0 and configure a J0 to send.
Path Trace configuration menu is available only for the TRFEC_64 board and if a Trail monitoring is
created.
12.11.11.2 Procedures
Path Trace configuration includes the following activities:
• Create a trail monitoring function on a TP

• Configure and start Path trace configuration option
Create a trail monitoring function on a TRFEC_64 (OGPI or OCH) TP
1) Display the port view of the corresponding WLA (TRFEC_64) board.
2) Select the OGPI or OCH block.
3) Choose the Port–Trail Monitor–Create menu option:

a trail monitor icon appears beside the selected port.
Configure and start the Path trace configuration option
4) Select a Trail Monitoring block:
5) Choose the Path trace Configuration menu option:

J0 Path Trace Configuration dialog box appears.
The Received field shows the Path Trace received by the NE. The first field displays the CRC7
received and the second one the 15 remaining bytes.
1AA 00014 0004 (9007) A4 – ALICE 04.10
6) In the Expected field, edit the Trace value to be compare to the received one.
3AL 89062 AA AA 472 / 926
926
7) Select mode 1 or One Repeated Byte.
a) When mode 1 is selected the right hand field requires 15 bytes to be filled. If a less number
is input before depressing the CRC7 button, the remaining bytes to reach 15 are asserted
to be 0.
8) One the required byte filled, depress the CRC7 button; then click on the OK button to send this
value.
b) When one Repeated byte is selected, enter the value to be send and click on the OK
button to send the value.
When the J0 received is different from the expected one, a trace identifier mismatch alarm
arises in the Trail Monitor block.
N.B. Disable/Enable TTI Mon button allows to enable or disable the command.
12.11.12 Cable configuration on 1696MS
The cable configuration feature is used to manage the connections between some of the boards. The
types of connections concerned by this feature are:
– Connection between an MCC board and a 4ANY board:

This type of connections can be displayed, declared and undeclared.
– Connections between an OPC board and two adjacent MCC boards (Optical Sub–network
Connection Protection):
This type of connections can only be displayed by the cable configuration feature.
They are automatically established and declared at the activation of the protection (see procedure:
Activate the protection of a connection, page 617)
They are automatically removed and undeclared at the deactivation of the protection (see procedure:
Deactivate the protection of a connection, page 617).
Display the existing connections
1) Choose the Views – Transmission menu option to display the Transmission view.
2) Choose the Transmission – Cable configuration menu option:

the Cable configuration dialog box appears.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 308. Cable configuration display
3AL 89062 AA AA 473 / 926
926
The example given in Figure 308. displays samples of the possible types of connections, which
can be displayed in the Cable configuration window:
– the two first lines show the connections that are automatically established at the activation

of an optical protection. These connections link two OgPI ports of an OPC board (slot #38)

to the OgPI port of two adjacent MCC boards (slots #14 and #15).
– the third line (the selected one) shows the connection between an MCC ogPi port and a
4xANY OpS port,
3) Click on Cancel to close the window.
Declare a connection between an MCC and a 4xANY
This type of connections is established by connecting the MCC OgPI port to the 4xANY OpS port.
1) Display the Port view of the MCC OgPI port.
2) Select the OGPI port block.
3) Choose the Port – Cable configuration menu option:

the Cable configuration window appears. The left port field is already filled by the friendly name
of the port that was selected in step 2 ).
4) Selection of the OpS port:
a) Click on the right TP Search button:

the Search for Cross Connection Input dialog box appears.
b) Display in the Termination Points area the OpS port of the 4xANY board, and select it.
c) Click on OK:
the right port field in now filled with the friendly name of the 4xANY OpS port.
5) Click on connect:
a new connection line appears in the list.
6) Click on OK to validate the declaration of the connection.
Undeclare a connection between an MCC and a 4xANY
1) Choose the Views – Transmission menu option to display the Transmission view.
2) Choose the Transmission – Cable configuration menu option:

the Cable configuration window appears.
3) Select in the list the connection to undeclare.
4) Click on disconnect:
the connection line disappears from the list.
5) Click on OK to validate.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 474 / 926
926
12.11.13 OTS/OMS port view
Figure 309. 1686WM – OTS port Menu view (example)
– For an OTS port the above optical menu option are available.
12.11.14 APSD Configuration on 1686WM
Automatic Power Shutdown (APSD) is used in case of loss of communication due to a break of an optical
fiber. For security reason it may be necessary to shutdown the laser to enable the fixing of the
communication link.
This procedure can also operate with a Front board command (by a switch on front board); in this case:
– Press a short time (up to 2 seconds): the laser restarts for some seconds and stops or
– Press a long time (about 12 seconds): the laser restarts for about 90 seconds and stops.
The APSD Configuration window displays the main WDM channel connected to the Mux part
(informations are transmit by the OTS).
Configure the APSD
From the OTS Port view:
1) Display the port view of the concerned OTS port.
2) Choose the APSD Configuration option in the Port menu:

The APSD configuration dialog box appears.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 475 / 926
926
Figure 310. 1686WM – APSD Configuration dialog box
The dialog box enables the following actions:
– APSD control: (Enable, Laser Forced on, Laser Forced off)

• To allow or inhibit the Automatic Power Shutdown functionality, select either the Enable or the
Laser Forced on or Laser Forced off option of the APSD control: option button.
– LASER Current State Display the laser current state (Laser on, Laser off, Test)
The status displayed on this window is not software refreshed; to do that the user has to refer to
the corresponding icon on the board that is always refreshed.
– APSD Auto restart: (Enable–Disable)

• Enable : the laser tries to restart every three minutes and shutdown if the link is cut–off
• Disable : the laser does not restart.
– APSD Manual restart: (Enable–Disable)
• Enable : either by the switch on the Expansion front board or by software command.
By Software (enable):
– MANUAL The laser restarts for some seconds and stops

– TEST The laser restarts for about 90 seconds and stops
3) Set the threshold value parameter by clicking on the corresponding option.
4) Click on OK to confirm the setting choice and terminate.
Hazard levels when +20 dBm output level of optical amplifiers are used:
1AA 00014 0004 (9007) A4 – ALICE 04.10
The ”APSD enable” must be the default configuration with (WB_OXA_P20_####) amplifiers
types .
3AL 89062 AA AA 476 / 926
926
In normal operation with ”APSD enable” configuration, the system operates in HAZARD LEVEL
1M.
When the APSD configuration is declared ”Forced on” or ”Manual Restart for test” the
system can operate in HAZARD LEVEL 3B (temporary in case of ”Manual Restart for test”
status or permanently in case of ”Forced on” status).

Consequently to these restricted values the system is declared in 1M Class.
To access the ”Forced on” or ”Manual Restart for test” command, a warning window appears
on the screen to show these commands imply to change from the HAZARD LEVEL 3A towards
the HAZARD LEVEL 3B hazard levels (if you validate that choice, you will no more be in
HAZARD LEVEL 1M, but you reach HAZARD LEVEL 3B). The user has to valid this request
before changing the APSD configuration mode.
Message in case of change from 1M to 3B class for all the amplifiers:
A message if the concerned optical amplifier is working at more than 17 dBm, ”Do you really
want to continue?” appears for all types of amplifiers (in case of ”FORCED ON” or ”RESTART
FOR TEST” status).
12.11.15 APS configuration on 1696WM
Automatic Power Shutdown (APSD) is used in case of loss of communication due to a break of an optical
fiber. For security reason it may be necessary to shutdown the laser to enable the fixing of the
communication link.
The APSD Configuration window displays all the declared channels and connected to the Mux part
(informations are transmit by the OTS).
From the OTS Port view:
• select the OTS icon,

• choose APSD Configuration option in the Port menu.
The operator can select one channel or All channels.
To select one channel, click with the mouse on the associated field.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 477 / 926
926
Then click on ”Configuration...” radio button
Figure 311. 1696M Span – APSD Configuration dialog box
The ”APSD control” dialog box enables the following actions:
– (Enable, Laser Forced on, Laser Forced off)
• To allow or inhibit the Automatic Power Shutdown functionality for the channel, select either the
Enable or the Laser Forced on or Laser Forced off option of the APSD control compo box.
Then valid the command or not by the ”OK” or ”Cancell” button.
When the operator select ”All channels” and click on ”Configuration..” radio button, the ”APSD
Configuration” displays a different dialog box as shown on Figure 312. The same dialog box is shown
for 1686WM
APS for 1696WM “All channels”
From the Port menu, select APSD Configuration option. For 1686WM Figure 312. opens
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 478 / 926
926
Figure 312. 1686WM – APSD Configuration dialog box
The dialog box enable the following actions:
– APSD control: (Enable, Laser Forced on, Laser Forced off)
• To allow or inhibit the Automatic Power Shutdown functionality, select either the Enable or the
Laser Forced on or Laser Forced off option of the APSD control: option button.
– LASER Current State Display the APSD current state (Laser on, Laser off, Test)
– LASER Auto restart: (Enable–Disable)
• Enable : the laser tries to restart every three minutes and shutdown if the link is cut–off
– APSD Manual restart: (Enable–Disable)
• Enable : either by the switch on the Expansion front board or by software command.
By Software (enable):
– MANUAL The laser restarts for some seconds and stops

– TEST The laser restarts for about 90 seconds and stops
The Cancel button allows you to cancel the choice made.
Front board command (operating by a switch on front board)
– Press a short time (up to 2 seconds): the laser restarts for some seconds and stops
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Press a long time (about 12 seconds): the laser restarts for about 90 seconds and stops.
When all parameters have been configured, valid the command by the OK button to confirm the setting
choice and close the dialog box.
3AL 89062 AA AA 479 / 926
926
12.11.16 OSC Synchronization Configuration on 1686WM
This menu item displays the current value (Local clock or Received signal clock from the supervision
channel ) and allows to define the NE (Local or Remote) for the OSC channel.

12.11.17 Cross Connection management on 1696MS
The cross connection management for 1696MS has been described in para.15.11 on page 610
12.11.18 Optical Add/Drop configuration on 1686WM and 1640WM
The OADM function is used to configure the OCH channels in Add/Drop or in Pass–Through configuration
mode. After the physical plugging and hardware setting, the optical Add/Drop configuration channels is
in Pass–Trough default configuration:
Add–Drop cross connection
This configuration, also called ”Drop/Insert”, connects a client signal to a WDM channel (i.e.: an WLA
board OCH port to an OADM board OCH–A port).
A cross–connection indicator appears under the graphical representation of the

cross connected OCHA ports.
Pass–through cross–connection
This configuration connects an OCH_A port to another OCH_A port.
To manage the cross connections use the following procedures:
– Display the optical Add/drop configuration

– Set Optical Add/Drop configuration
Display the Optical Add/Drop configuration
To display the optical add/drop configuration of an OCHA, proceed as follows:
1) Display the Port view of the chosen OTS port.
2) Select the chosen OCHA.
3) Choose the Port – Opt Add / Drop configuration menu, the Drop–Insert or on the
Pass–Through option appear.
The current configuration is indicated by a tick in front of one of the two options.
4) Click (or release the mouse button) outside the opened menu to close it.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 480 / 926
926
Figure 313. 1686 WM – OTS Port menu view– Optical Add/Drop configuration display (example)
– Set Optical Add/Drop configuration
1) Display the Port view of the chosen OTS port (selecting an In–Line Amplifier board in OADM
repeater).
2) Open the OTS port view (available from slot 2 or slot 4 of master shelf).
3) Select the OCHA icon block corresponding to the channel to be treated

When an OCHA icon block is selected, information concerning the channel and the associated
grid are displayed on the lower left side of the screen (i.e port#01c193300g100–Och).
4) Choose the Port – Opt Add / Drop Configuration – menu option:
5) Activate the chosen option Drop – Insert or Pass – Through option (click on it)
6) When selecting again this menu, the current configuration is indicated by a tick in front of the
declared options.
7) Proceed the same way for the others channels.
N.B. In the the Transmission view this information is also displayed from the Port – Opt Add
/ Drop Configuration – Drop – Insert or Pass – Through option menu when an OCHA
icon block is selected. It is only for consulting.
N.B. Before changing configuration from drop–insert to pass Through it is necessary to des
1AA 00014 0004 (9007) A4 – ALICE 04.10
active (on both OCH–A blocks) the Performance Monitoring on FEC which could have
been configured on the selected channel.
3AL 89062 AA AA 481 / 926
926
12.11.19 BER Threshold configuration on 1640WM and 1686WM
This option menu allows to configure the corrected error thresholds for the LTCER parameters (available
on WLA boards with FEC functionality).

Threshold configuration value parameter is selected by clicking on the corresponding option.

The LTCER threshold Set values are from 10E –4 to 10E –8 corresponding to an alarm arise event
Threshold Clear of the alarm is one decade below the threshold Set value.
When the value exceed the ”threshold Set”, the corresponding alarm is activated.
When the value is lower than the ”threshold Clear”, the corresponding alarm is cleared.
N.B. On WLAs types without FEC functionality LTCER icon alarm is present in the port view
representation, but not significant (never in activated state).
Set the BER Threshold configuration:
1) Select the OGPI port from the WLA (with FEC functionality) board view.
2) Choose the Port –> BER threshold configuration menu option of Figure 314. :
LTBER threshold configuration dialog box appears.
3) Set the threshold value parameter by clicking on the corresponding option.
4) Click on OK to terminate.
Figure 314. Threshold BER option selected
12.11.20 OSC BER Threshold configuration on 1686WM
From this menu option the operator set the threshold alarm value for the Optical Supervisory Channel. The
current threshold value is selected for an OMS or OTS TP block. Alarm Threshold OSM or (OTS) are
separately configurable.
A value set is a pair of thresholds corresponding to the SET and CLEAR of the alarm.
The OSC BER threshold values are: E–3/E–4, E–4/E–5, E–5/E–6
When the value exceed the ”threshold Set”, the corresponding alarm is activated.
N.B. E–4/E–5 means: the BER alarm in the OSC of the WDM line appears for a 10 E–4 (set) value
and disappears for a 10 E–5 (clear) value. It is the same principle for the other thresholds
configuration options.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Set the OSC BER Threshold configuration
1) Select an OMS or OTS icon block in the in an OTS port view.
3AL 89062 AA AA 482 / 926
926
2) Choose the Port –> OTS (or OMS) BER Threshold Configuration – menu option:
3) Set the threshold value parameter by clicking on the corresponding option

N.B. When this option menu is selected again a tick ahead the value enables it.
12.11.21 Show OCH port view

Allows the operator to navigate to the OCH port view, when an OCHA is selected.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 483 / 926
926
12.11.22 Loopback management for WDM
This section, which describes the WDM loopback management is applicable to 1696MS.

12.11.22.1 Loopback management

This section describes how to use the loopback feature. It divided in two parts:
– Introduction,
– Procedure.
The loopback feature allows to perform particular cross connections for test purpose. This feature is used
to test the transmission system during installation and maintenance operations.
The loopback feature is located in the 88 matrix of the MCC boards and has the following characteristics:
– There is two types of loopback:
• Local loopback
• Remote loopback
– A loopback can be applied on MCCs in the following cross connection configuration:
• No cross connection
• Drop insert cross connection
• Pass–through cross connection.
The possible loopback and cross connection configuration are given here after.
N.B. The maximum number of loopbacks by NE is 10.
Local loopback without cross connection
A local loopback is performed at the client signal interface (i.e.: User side, OGPI port). Inside the MCC
matrix, the User Rx receiver is connected to the User Tx transmitter.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 484 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
MCC
User Tx
WDM Rx
OGPI
8x8 Matrix
Client signal
User Rx
WDM Tx
Figure 315. Local loopback without cross connection
926
3AL 89062 AA AA
485 / 926
Remote loopback without cross connection
A remote loopback is performed at the WDM channel interface (i.e.: WDM side, OCH port). Inside
the MCC matrix, the WDM Rx receiver is connected to the WDM Tx transmitter.

MCC
User Tx User Rx
8x8 Matrix
OCH
WDM Rx WDM Tx
WDM
channel
Figure 316. Remote loopback without cross connection
Local loopback on MCC in Drop–insert
Inside the MCC matrix, the User Rx receiver is connected to the User Tx and to the WDM Tx optical
transmitters. The WDM Rx receiver is disconnected.
Client signal
MCC
User Tx User Rx
OGPI
8x8 Matrix
WDM Rx WDM Tx
WDM
channel
Figure 317. Local drop–insert loopback

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 486 / 926
926
Remote loopback on MCC in Drop–insert
Inside the MCC matrix, the WDM Rx receiver is connected to the WDM Tx and to the User Tx optical
transmitters. The User Rx receiver is disconnected
Client signal
MCC
User Tx User Rx
8x8
Matrix
OCH
WDM Rx WDM Tx
WDM
channel
Figure 318. Remote drop–insert loopback
Local loopback on MCC in Pass–through
Inside the MCC matrix, the User Rx receiver is connected to the User Tx transmitter. The pass–trough
cross connection is not modified.
Client signal
MCC MCC
User Tx User Rx User Tx User Rx
OGPI
8x8 8x8
Matrix Matrix
WDM Rx WDM Tx WDM Rx WDM Tx
WDM WDM
channel channel
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 319. Local pass–through loopback
3AL 89062 AA AA 487 / 926
926
Remote loopback on MCC in Pass–through
The WDM Rx receiver is connected to the WDM Tx transmitter of the board itself and to the WDM
Tx transmitter of the adjacent board via the back–panel links.

MCC MCC
User Tx User Rx User Tx User Rx
8x8 Matrix 8x8 Matrix
OCH
WDM Rx WDM Tx WDM Rx WDM Tx
WDM WDM
channel channel
Figure 320. Remote pass–through loopback

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 488 / 926
926
12.11.22.3 Loopback management procedures
You will find in this section the following loopback management procedures:
– Create a local loopback

– Create a remote loopback
– Display the existing loopbacks.
– Remove a loopback
Create a local loopback
1) Display the Transmission view of the OGPI port of the MCC board that will support the local loop-
back.
2) Select the OgPI icon.
3) Choose the Transmission – Port Loopback Configuration menu option:

The Port Loopback Configuration dialog box appears.
4) Click on OK.
5) In the Confirmation dialog box click on OK to create the loopback:

A loopback symbol appears beside the graphical representation of the port.
Loopback symbol
Figure 321. Local loopback symbol – Transmission view

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 489 / 926
926
Create a remote loopback
N.B. In case of a loopback applied on an MCC board involved in an optical protection configura-
tion, the absence of signal at the User Rx access may cause the shutdown of the WDM

Tx transmitter. To avoid that, ensure the presence of a signal at the User Rx access or set

the WDM Tx transmitter APSD to Laser force–on mode (see procedure: Configure the
APSD, see para. 12.11.15 on page 477).
1) Display the Transmission view of the OGPI port of the MCC board that will support the remote
loopback.
2) Select the OchTTP icon.
3) Choose the Transmission – Port Loopback Configuration menu option:

The Port Loopback Configuration dialog box appears.
4) Click on OK.
5) In the Confirmation dialog box click on OK to create the loopback:

A loopback symbol appears beside the graphical representation of the port.
Loopback symbol
Figure 322. Remote loopback symbol – Transmission view
Display the existing loopbacks
1) Choose the Configuration – Loopback Management menu option:

The Loopback Management dialog box appears.
2) Click on Search:
The existing loopbacks appears in the list.
3) Click on Close to close the dialog box.

The cross–connection appears in the list of the Cross Connection Management dialog box.
Remove a loopback
1) Choose the Configuration – Loopback Management menu option:

The Loopback Management dialog box appears.
2) Click on Search:
The existing loopbacks appears in the list.
3) Select the loopback.
4) Click on Remove.
1AA 00014 0004 (9007) A4 – ALICE 04.10
5) In the confirmation dialog box click on OK.

The loopback symbol disappears beside the graphical representation of the port.
3AL 89062 AA AA 490 / 926
926
13 PORT DETAILS DIALOG (ONLY AVAILABLE FOR OMSG)
The Port Details dialog can be used to monitor the detailed alarms and detailed states of a set of TPs
located in a sub tree. It offers the possibility to navigate comfortably between several TP views. These TP
views can be configured individually by:

– Adding defined TPs
– Setting the alarm severity of a TP
– Setting the alarm persistency of a TP.
For any other special TP configuration and modification functionalities the Port View must be used.
The Port Details dialog can be invoked from the Configuration menu via the Port Details... menu item:
Configuration
NE Time...
Performance >
Set ACD Level...
Loopback Management...
Port Details...
EPS Status...
MSP Status...
Furthermore the Port Details dialog is supported by some specific equipment views (Equipment Overview,
Board view, Transmission view, Port view) and can be invoke from the following menus:
– Equipment Overview menu
– Board menu
– Transmission menu.
Each menu entry is connected to one dialog. If a TP is selected, this TP is displayed in detail in the dialog.
13.1 Port Details Dialog Layout
The Port Details dialog consists of the following main parts:
– TP Notebook Pages
1AA 00014 0004 (9007) A4 – ALICE 04.10
– TP Area
– Port Functional State Information Message Area
3AL 89062 AA AA 491 / 926
926
– Button Area.
Figure 323. represents an example of a Port Details dialog.

The dialog is dynamically resizable. The state and button areas keep their size, only the notebook will be

resized.

)
)'

) #

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 323. Example of a Port Details Dialog
3AL 89062 AA AA 492 / 926
926
13.1.1 TP Notebook Pages
The top part of the dialog consists of a notebook containing a configurable number of pages. Each page
is able to display TPs of a different port and its states.
The full user label of the currently selected TP is displayed in the upper left corner of the page – the tab.
Moving the mouse pointer over an alarm will display the alarm’s full name in the status bar of the dialog.
The tabs of the notebook will be also used to visualize a kind of alarm synthesis. If any of the TPs of a page
is alarmed, the respective tab icon will have the corresponding background color of the alarm with the high-
est severity (e.g., if one major alarm and one minor alarm are present, the tab icon is colored orange).
13.1.2 TP Area
The TPs are displayed as an icon similar to the existing Port View including all their alarms and a user
label, as well as the icons for cross connections and PM.
The graphics for alarms, cross connections and PM are updated if a corresponding notification is received.
The TPs are positioned in a row/column layout sorted in ETSI order. If possible, the width of the rows is
kept smaller than the width of the visible area. So it is only necessary to scroll vertically. Only objects with
attached monitors (e.g., POM/SUT) may require the use of the horizontal scrollbar as closely related ob-
jects are not split over two rows.
For further information about the TP object design within the Port Details dialog refer to Chapter 13.2.
13.1.3 Port Functional State Information Message Area
This message area gives information on the protection state and the laser shutdown state of the port.
The information in the functional state message depends on the type of port e.g., electrical ports do not
have the laser shutdown information.
For more information about the EPS and MSP protection state refer to Chapter 9.2 and Chapter 10.5. For
information about the laser state refer to Chapter 12.2.2.
13.1.4 Status Bar
The status bar shows the description of the item states in the TP area and port functional state information
message area where the mouse pointer is moved over.
13.1.5 Button Area
The lower part of the dialog contains several buttons which have to be used to configure the Port Details
dialog.
The following buttons are available:
– Add TPs to add TPs.
– Add Alarmed to add alarmed TPs.

1AA 00014 0004 (9007) A4 – ALICE 04.10
– Remove TP to remove selected TP(s).
– Remove All to removes all TPs from the active page.
3AL 89062 AA AA 493 / 926
926
– Alarm Severities to set the alarm severities.
– Alarm Persistency to set the alarm persistency.

– Object Alarms to display object alarms (currently not supported).

– Subtree Alarms to display subtree alarms (currently not supported).
– PM Current Data to display the PM Current Data.
– Preferences to save and load user preferences dialog.
– Close empties all pages and closes the dialog.
– Help opens the online help of the Port Details dialog.
Due to the characteristics of the selected object, some commands are not available.
For more information about the Port Details dialog configuration and commands refer to Chapter 13.3.
13.1.6 The Pop-Up Menu
By clicking and holding the right mouse button in the TP area a pop-up menu appears offering a variety
of commands related to the selected TP.
Add TP...
Add Alarmed
Remove TP
Remove All
Alarm Severities...
Alarm Persistency...
Object Alarms
Subtree Alarms
PM Current Data...
Switch to MSP Related Unit
Preferences...
Due to the characteristics of the selected object, some commands are not available.
The available menu entries are identical to the commands supported by the button area (see Chapter
13.1.5), except the menu entry Switch to MSP Related Unit. It is only active, if the current notebook page
contains an MSP protected port.
For more information about the Port Details dialog configuration and commands refer to Chapter 13.3.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 494 / 926
926
13.2 TP Object Design
The symbols of the TPs within in Port Details dialog as shown in Figure 324. have the following signifi-
cance:
– Alarm Icon Area: The icon boxes represent alarms. The color of the boxes changes according to
the alarm severity. The alarm icons are identified by acronyms indicating the probable cause of the
alarm occurring.
For example, the acronym LOS on the SPI (SDH Physical Interface) functional block indicates a Loss
Of Signal at reception.
These alarm icons use the alarm severity color feature to indicate the severity of the alarm. You can
therefore determine the type and severity of the alarm occurring in a specific part of the port.
Further information on alarms is given in the Alarm Reference Guide.
– TP identifier: The icons within the Port Details dialog represent functional blocks that comprise the
port. The acronyms of the TPs identify the type of TP (in 15.1.4 the TPs are labelled AU4 signifying
Administrative Unit order 4). This helps to identify the type of signal that transits by the port.
– Cross-connected: If a TP is cross-connected, an x appears within the icon.
– Loopback active: An existing port loopback is represented by an arrow beside the TP object.
– PM active: If PM is active on a TP, a P appears within the icon.
– Selected state: A colored frame around the box identifies a selection.
)' $ "

*

$
0 $
Figure 324. Examples of TPs

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 495 / 926
926
13.3 Port Details Dialog Configuration
13.3.1 Adding TPs to the Port Details Dialog

TPs can be added to the Port Details dialog either via the TP Search dialog or from the equipment views
(Equipment Overview, Board view, Transmission view, Port view).
N.B. If a TP is added from another port (or several TPs of which the first one belongs to another port),
the dialog removes all current TPs and displays the TP(s) of the new port.
Adding TPs via TP Search
To add a TP to an empty Port Details Dialog via TP Search perform the following steps:
1) Open the Configuration menu.
2) Select Port Details.

An empty Port Details Dialog appears (see Figure 325. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 325. Port Details Dialog without any TPs
3AL 89062 AA AA 496 / 926
926
3) In the Button Area of the Port Details Dialog click Add TP.
It appears the TP Search Dialog as shown in Figure 326. . For detailed information about the TP
Search Dialog refer to Chapter 14.4.
Figure 326. TP Search Dialog
4) Select the corresponding TP Search Criteria and click Search to list available TPs.
5) Either
– Select a TP and click OK or
– Double-click the corresponding TP or
– Choose the TP via drag-and-drop.
The chosen TP appears in the Port Details Dialog (see Figure 327. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 497 / 926
926
Figure 327. Port Details Dialog with TP
Adding TPs from the Equipment Views
The following equipment views supports the Port Details dialog:
– Equipment Overview
– Board view
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Transmission view
– Port view.
3AL 89062 AA AA 498 / 926
926
If one of these views is active, a TP can be added to the Port Details dialog as follows:
Via Menu:
1) In the current view select the corresponding TP object.

2) Select Port Details from the Configuration menu or from the corresponding equipment view
menu.
The selected TP appears in the Port Details dialog.
Via Drag-and-Drop:
1) Open the Port Details dialog from the Configuration menu.
2) Drag the TP object to the Port Details dialog.

The chosen TP appears in the Port Details dialog.
Adding Alarmed TPs
The Port Details dialog provides the functionality to add alarmed TPs of a defined port:
1) Add the corresponding TP to a notebook page.
2) Click Add Alarmed.

All alarmed TPs of the current port will be added to the active notebook page.
13.3.2 Removing TPs from the Port Details Dialog
The Port Details dialog offers the possibility to remove only one TP object or to clear completely one note-
book page.
Removing only one TP object:
1) Select the corresponding TP object.
2) Click Remove TP.
Removing all TP objects from a notebook page:
1) Select the corresponding notebook page.
2) Click Remove All.
13.3.3 Alarm Severities
To set the alarm severities of a TP in the Port Details dialog perform the following steps:
2) Click Alarm Severities.

It appears the Set ASAP dialog. For a detailed description of the Set ASAP dialog refer to Chap-
ter 3.4.2.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 499 / 926
926
13.3.4 Alarm Persistency
To configure the alarm persistency time of a TP in the Port Details dialog perform the following steps:


2) Click Alarm Persistency.
It appears the Alarm Persistence Time Configuration dialog. For a detailed description of the
Alarm Persistence Time Configuration dialog refer to Chapter 14.8.
13.3.5 PM Current Data
To display the current performance monitoring data of a TP perform the following steps:
2) Click PM Current Data.

It appears the Current PM Data dialog. For a detailed description of the Current PM Data dialog
refer to Chapter 16.5.
13.3.6 Switching to MSP Related Unit
The Port Details details offers the possibility to display and switch between the MSP own unit (e.g., pro-
tected port) and the MSP related unit (e.g., protecting port) of a protection. It is only active, if the current
notebook page contains an MSP protected port.
1) Select/configure a notebook page with an MSP protected port.
2) Select the menu entry Switching to MSP Related Unit from the pop–up menu of the Port De-
tails dialog.
It removes the TP from the current page and adds the related MSP object.
3) To switch between the MSP related unit and the MSP own unit, select again the menu entry
Switching to MSP Related Unit from the pop–up menu of the Port Details dialog.
The user label of the MSP is displayed on the tab of the page. The MSP states are shown in the port func-
tional state information message area.
For details concerning the MSP states refer to Chapter 10.5.
13.3.7 Preferences
In order to save all currently displayed TPs of all pages or to load previously saved sets of TPs the function-
ality Preferences can be used.
Click Preferences. It appears the User Preferences dialog. For detailed description of the User Prefer-
ences dialog refer to Chapter 3.7.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 500 / 926
926
14 TRANSMISSION VIEW
The Transmission features are applied to OMSG, W/OMSN (WMSN and OMSN) and to many Alcatel
Q3NEs. In this chapter, these general NEs will be indicated with Q3NEs , otherwise they will be specified
with the indication “not available for/on ...” the family to which the Transmission features cannot be applied
or “only available for/on ...” the family to which the Transmission feature can only be applied
14.1 Overview
The generic Transmission View offers the possibility of displaying a single TP or a set of all kinds of TPs
(or collected functionality which is represented by one/several TPs). To display the termination points in
the Transmission View, either select specific TPs from a TP search dialog or access the view directly from
another view, e.g. by navigating from the Port View. The Transmission View provides the following
features:
– Brief overview regarding transmission resources.
• An overview concerning all TPs belonging to a port can be called in by activating the function
to expand the selected TP. TP names are listed in an additional information area if the mouse
pointer is positioned over it. The following states are indicated:
– the alarm state is indicated by the alarm synthesis icon
– the cross-connection state is indicated by a cross
– whether a TP can be structured is indicated by a circle
– activated PM is indicated by a “P” icon
– the user label of a selected TP is displayed in an additional information area below the left
alarm sub-panel. The information includes the full user label of the root TP and the full
name of the selected TP in brackets.
• An overview concerning signal flow can be requested by a user action. The user can select a
TP and apply the action Show Cross-connected TPs. The result is that the objects related to
the TP are displayed and lines indicate the connections. Expanding and hiding TPs that are
related to the currently selected TP (e.g. show all TPs that are above the TU-12 CTP) enables
all related TPs to be added to the view, thus providing a representation of the entire signal flow.
– Display of single or multiple termination points.
• Search for and select a termination point in a TP search dialog and display it in the Transmission
View.
• Pop-up the Transmission View from the board view. All TPs/compound TPs associated with the
physical port are displayed
(i.e. TPs down to AU-4).
– Provide the functionality to create/show cross-connections.
– Provide the possibility of configuring a selected TP. This functionality is accessed by calling the
configuration dialogs of the common Transmission/Port Views category.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Provide the possibility of showing a detailed view of a TP with alarms.
3AL 89062 AA AA 501 / 926
926
The available commands for the “Transmission” menu are reported for the different USM types in the
Chapter “Menu Commands”. The TPs description has been reported in chapter 15.1.3. In the following
the reported menu commands have to be considered only for the option command described. The menu
commands are properly represented but the menu list sometimes is not updated.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 502 / 926
926
14.2 View Elements
The Transmission View uses the symbols illustrated in Figure 328. . The layout for the graphical
cross-connections is similar to the layout in the chapter concerning cross-connection.
E3 ) = = =

=
" =
=
= ==" =
) =
* ) = = =* =
"= =

= = $ ==
)'= $ ==
/ == =)'1
Figure 328. Symbols Used in Transmission View (example)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 503 / 926
926
14.3 View Layout
The Transmission View provides views of specific areas, which display the transmission resources, and
the specific Transmission View pulldown menu which provides the Transmission View operations. The

definition of termination points (TPs) are reported in the “Cross–Connection” Management chapter (see

para.15.1.3)
14.3.1 View Description
Figure 329. illustrates the Transmission View area. TPs that are received from the network element are
displayed in the Transmission View with the respective TP and connection symbols described in
Figure 328. . The number of TPs presented initially depends on whether the Transmission View is
popped up from a board view, whether a TP has been selected in another view or whether it is called
without a selected TP.
14.3.2 Number of TPs Displayed in Transmission View
It is possible both to expand a VC-4, thus displaying all underlying TPs, and to hide TPs which are of no
interest. The objects initially displayed depend on the situation/definition.
14.3.3 Naming TPs
The following rules are applied in order to identify the TPs displayed:
– SPI (ElS, OpS) and PPI (P) TPs contain the full user label,
– the root TP (if not SPI or PPI object) contains a short label,
– all child TPs contain a short label indicating the position inside the tree.
In addition, the full user label of each object selected is indicated in the area below the left alarm sub-panel.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 504 / 926
926
Figure 329. Transmission View with Activated Panner
14.3.4 Show Panner (on OMSG)
When the “Show Panner” option is activated in the “Transmission – Preferences” menu option, an
overview of the complete transmission view structure appears in the lower left corner. This can be useful
in the case of large views that use scrolling bars.
A rectangle in the panner indicates the visible part of the view. To shift the rectangle (and the view) click
on an empty area inside the rectangle with the left mouse button and drag it keeping the mouse button
pressed.
Activate or deactivate the “Show Panner” option by selecting the option again.
14.3.5 Shifting Large Views (on OMSG)
To shift large views use the panner function, the scroll bars or click on an empty area inside the rectangle
1AA 00014 0004 (9007) A4 – ALICE 04.10
with the left mouse button and pull it keeping the mouse button pressed.
3AL 89062 AA AA 505 / 926
926
14.3.6 Dynamic View Behavior
The following section describes the view states and provides a short description of events that affect the
view.

Initial state of the view
In its initial state, the Transmission View contains no objects. Objects can be searched for and displayed
using the Add TP dialog.
Working state of the view
In its working state, the Transmission View already contains objects. If the operator searches for and
displays a TP using the TP Search dialog, the view is first initialized again and then the TP is displayed.
The same applies in the case of navigation from another view to the Transmission View – the Transmission
View is always initialized and the corresponding objects are then displayed in it.
Navigation to Transmission View from other views
If the Transmission View is popped up from the Port View, only the selected TP is displayed.
Alarm notification
Alarms concerning the TPs displayed are indicated graphically by the alarm synthesis icons of the TP
objects. The TP objects are updated accordingly.
Object creation/deletion – Active Updates
The user decides which objects are displayed inside the Transmission View. Structuring payloads and
concatenating or deconcatenating TPs are actions that delete and create objects.
If the “Active Updates” option is not activated in the “Transmission – Preferences” menu option:
Deleted objects are removed from the view but created objects are not automatically added, leaving it to
the user to decide whether to display them or not.
If necessary, a double click or a whole subtree request on the parent object is sufficient to display the newly
created objects.
If the “Active Updates” option is activated in the “Transmission – Preferences” menu option:
Deleted objects are removed from the view and created objects are automatically added.
Activate or deactivate the “Active Updates” option by selecting the option again.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 506 / 926
926
Entries manager and navigation to the Clipboard on OMSG
The window dialog box on OMSG can visualize, at the bottom side, the buttons of Figure 330. These
buttons can be used to navigate to the Clipboard box dialog and to manage the window box entries data.
Figure 330. Entries manager buttons on OMSG
The functioalities of these buttons are here described:
Click on the Tp list button to open the Clipboard dialog. As long as the clipboard is open, the buttons
Cancel, Apply, OK and Refresh are disabled. The Refresh button discards your entries, but leaves
the dialog box open, the Apply button, inserts the new entries and leaves open the dialog box, the
OK button performs the changes and closes the dialog box, the Cancel button discards the new
entries and closes the dialog box.
14.3.7 Popup Menu
By clicking and holding the right mouse button in the Transmission View appears a menu commands
depending of the USM type. In the following example the OMSG Transmission menu commands are
reported:
Add TP...

Expand All Lower TPs
Expand Next Level of Upper TPs
Expand All Upper TPs
Hide TPs

Navigate to Msspring view
Dynamic part of the menu

depending on the selected TP
Due to the characteristics of the selected TP object, some commands are not available.
The dynamic part of the menu provides a range of configuration commands related to the TP and,
therefore, varies according to the selected TP.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The commands are described in the following chapters.
3AL 89062 AA AA 507 / 926
926
14.4 Add TP
Transmission

Add TP
Expand >
Hide >
TP Configuration
Terminate TP
Disterminate TP
Cross Connection >
POM/SUT >
Performance >
Concatenation
Structure TPs >
Physical Media >

This menu item opens the TP Search dialog (see Figure 332. ). The TP Search dialog enables the user
to search for and add a TP to the Transmission View (e.g. search for all TPs on a board with PM enabled).
A similar dialog with almost the same funtionality is the Search for Cross-Connection Output dialog (see
Figure 341. ). It is opened from Choose button of the Main Cross-Connection dialog and is used to select
cross-connectable TPs.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 508 / 926
926
14.4.1 Default Mode
In this mode, the dialog displays the structure of the ETSI equipment tree. After double-clicking, e.g. on
a port, the contents of the port appear on the right-hand side of the dialog (TP list). To keep the number
of displayed items small they are displayed in a hierarchical order. Double-click again to recall the next
level (see Figure 332. ).
The following restrictions apply to the default mode:
– The similar Search for Cross-Connection Output dialog which can be opened from the Main
Cross-Connection dialog differs in its behaviour:
When opened from the output TP Choose button, only TPs that are cross-connectable with the
related input TP are displayed (same TP class). Therefore double-clicking on a port does only display
TPs matching this filter and not the entire port structure.
– If, after double-clicking on an adaptation subrack, each contained TU-12 CTP is displayed 4 times,
select another subrack or board in the dialog and then re-select the adaptation subrack. The TU-12
CTPs are displayed properly.
After double-clicking on an object, an Information Window appears (see Figure 331. ). The message text
corresponds to the object selected.
The search can be stopped with Cancel.
Figure 331. Information Window

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 509 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
The equipment is displayed with the following symbols:
926
Figure 332. TP Search Dialog on W/OMSN (example)
3AL 89062 AA AA
510 / 926
>%=% =/?1
C'=/ 1
C'=/ 1
)'
#

It is possible to select several individual TPs from the TP list by clicking on them while holding down the
Ctrl key on the keyboard. To select a block of TPs, click on the first TP and then click on the last TP in the
block while holding down the Shift key on the keyboard. But only the first TP selected in the list will be
shown in the Transmission View.
Figure 333. TP Search Dialog with Various TP Selections

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 511 / 926
926
Show Access (on OMSG)
After clicking on Show Access, the detailed TP list additionally displays (see Figure 334. ) TP access
information (ACD).

Figure 334. Cross-Connection Access Information
The symbols in the TP list have the following significance:
" =
" =
Figure 335. Cross-Connection Access Symbols

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 512 / 926
926
Show Cross Connection State,
After clicking on Show CC State, the detailed TP list displays information (see Figure 336. ) on the TP
status.
Figure 336. Cross-Connection State Information
The symbols in the TP list have the following significance:
> =
== =
= =
= ===
# =
> =
Figure 337. Cross-Connection State Symbols
The symbol in the TP list means, in the 1696MS, that a cross connection is active
1AA 00014 0004 (9007) A4 – ALICE 04.10
The background color of the symbols represents the status of the TP:
– grey = inactive
– green = active
3AL 89062 AA AA 513 / 926
926
Board History
An easy way to recall to previously displayed boards is to use Board History. Select the relevant board
from the list.

Figure 338. Board History Check List example on OMSG
14.4.2 Search Mode
In this mode the dialog is used as search tools. It displays the objects matching some requested filter
criteria in alphabetical order. Use the filtering options provided below the TP list (see Figure 339. ) together
with the TPSearch / Search button. The matching objects appear on the right-hand side of the dialog (TP
list).
re-located physically from one board to another. The name of the TPs are logical names as
The following filter options are available:
– Class
Select one of the TP classes: Ignore, ElS, OpS, PPI, ElS&OpS&PPI, RST, MST, MSP, AU4, VC4,
AU4&VC4, AU4-4c, AU4–16c, AU4–64c, TUG-3, TU3, VC3, TU3&VC3, TUG-2, TU12, VC12,
TU12&VC12, DS3&ExCTP&ExATTP.
N.B. There are some restrictions to this filter option:

– A search for TUG3 and TUG2 is only successful if the filter is applied to the whole NE
1AA 00014 0004 (9007) A4 – ALICE 04.10
(i.e. the top level object in the tree) and not only to lower level equipment (e.g. a board).
– For the 4/4 OMSG, 1674LG, 1670SM, the TP classes TU-3, TU-12, VC-3, VC-12 are not
available. The selection of these classes as filter option returns an empty query result.
3AL 89062 AA AA 514 / 926
926
– Connection State / XConn State (Current connectivity status)
Ignore, not connected, connected
– AlarmState
Ignore, critical, major, minor, warning, not alarmed

– Assign State
Ignore, NML, Craft
– Perf Monitoring Performance Monitoring condition

Ignore, enabled
– MSP State (on OMSG)
Ignore, No Request, DNR, Manual, Auto-WTR, Auto-SD, Auto-SF, Force, Lockout, Fail (APS invalid),
Fail (Channel mismatch)
If any of the following fields is empty, it is handled as a wildcard.
– TTI expect (not used on many USM types)

Insert the expected TTI value here
– TTI receive (not used on many USM types)

Insert the received TTI value here
– TTI transmit (not used on many USM types)

Insert the transmitted TTI value here
– Location
Insert Rack-Subrack-Board-Port location of the TP, e.g 2-5-7-1 for rack 2, subrack 5, board 7, port
1.
The format r<rack#>sr<subrack#>sl<slot#><port#> has to be also considered for
W/OMSN.
– Name
Insert the complete TP location and name:
e.g 02-5-07-01,01#AU4P for the first AU-4 CTP on rack 2, subrack 5, board 7, port 1.
Not supported for W/OMSN.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 515 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 339. TP Search Dialog with different filtering options example
516 / 926
After activating the search process with the Search TPs button, the following dialog box appears. The
search can be interrupted by clicking on Cancel.
Figure 340. “Information...” Dialog for Search Process
N.B. When searching for PM-enabled TPs on large NEs, Rack or Subrack, the time for the request
can be very high. It is recommended to search for PM-enabled TPs at the board level (a board
is selected for the search).
The Figure 341. shows the results of a “AU4 TPs” filtering.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 341. Results of a “AU4 TPs” filtering
3AL 89062 AA AA 517 / 926
926
14.4.3 Common Buttons
The following buttons are available in all modes:

Ok

Closes the dialog and opens the Transmission View containing the selected TP.
Close
Closes the dialog without updating the Transmission View.
Print
This command is used to generate and print a list of TPs according to the current filter selection (refer to
Figure 342. for an example of a printout). For more detalis see the print options described in 3.10 chapter.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 342. Example Printout
3AL 89062 AA AA 518 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
Help
01
This command opens the online help for the TP-Search dialog.
926
3AL 89062 AA AA
519 / 926
14.5 Navigation Commands in Transmission View
14.5.1 Expand

Transmission
Add TP
Expand > Next Level of Lower TPs
Hide > All Lower TPs
TP Configuration
All Upper TPs
Terminate TP
Disterminate TP
Cross Connection >
POM/SUT >
Performance >
Concatenation
Structure TPs >
Physical Media >

This menu item provides the possibility of displaying TPs that are related to the selected TP. These may
be TPs that are contained by the TP or TPs which belong to the physical port that is actually connected
to the TP.
– Show next level of lower TPs,
– Show all lower TPs,
– Show next level of upper TPs,
– Show all upper TPs.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 520 / 926
926
14.5.2 Hide
Transmission
Add TP
Expand >
Hide > Lower TPs
Preferences > Upper TPs
Selected TPs
...
Sibling TPs
This menu item provides the possibility of hiding all upper/lower TPs of a selected TP and the deletion of
a selected TP.
– Hide lower TPs,
– Hide upper TPs,
– Hide selected TPs,
– Hide sibling TPs.
14.5.3 “Port Details”, “Show Supported Board” and “Navigate to...” Commands
Transmission
Add TP
Expand >
Hide >
Preferences >
...
Port Details...
The Port Details command opens the Port Details dialog related to the selected object.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The Show Supported Board command provides the possibility of navigating directly to the board that
supports the TP.
3AL 89062 AA AA 521 / 926
926
The Navigate to... commands open the corresponding views (Equipment Overview and Port view) of
the selected object.

14.5.4 Show Supported Board
Transmission
Add TP
Expand >
Hide >
TP Configuration
Terminate TP
Disterminate TP
Cross Connection >
POM/SUT >
Performance >
Concatenation
Structure TPs >
Physical Media >

This menu provides the possibility of navigating directly to the board that supports the TP.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 522 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
The Board View appears:
Figure 343. Board View
926
3AL 89062 AA AA
523 / 926
14.5.5 Navigate to Port View
Transmission

Add TP
Expand >
Hide >
TP Configuration
Terminate TP
Disterminate TP
Cross Connection >
POM/SUT >
Performance >
Concatenation
Structure TPs >
Physical Media >

This menu provides the possibility of navigating to the corresponding Port View related to the selected
TP in order to access a detailed overview of alarms quickly.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 524 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
The Port View appears:
Figure 344. Port View
926
3AL 89062 AA AA
525 / 926
14.5.6 Navigate to Equipment Overview
Transmission

Add TP
Expand >
Hide >
TP Configuration
Terminate TP
Disterminate TP
Cross Connection >
POM/SUT >
Performance >
Concatenation
Structure TPs >
Physical Media >

This menu provides the possibility of navigating to the corresponding Equipment Overview related to the
selected TP in order to access a detailed overview quickly.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 526 / 926
926
14.6 TP Configuration
This command is also available in the Port view.

Port / Transmission
TP Configuration
TP Thresholds
N.B. The TP identifier field (TP Id) is provided only on OMSG.
14.6.1 J0 Configuration
Depending on the TP selected, a dialog appears for the configuration of the following object.
– RSTTP.
The main parameters are:
– J0 Path Trace
– Enabling Monitoring
– Enabling Generator
Figure 345. J0 Configuration on OMSG
J0 Path / Section Trace

1AA 00014 0004 (9007) A4 – ALICE 04.10
– Disabled:
no entry possible
3AL 89062 AA AA 527 / 926
926
– Enabled:
15 characters can be entered
– Enabled, 1 Repeated Byte:

1 character can be entered

The checksum is automatically calculated by clicking on OK and can be visualized by clicking on the CRC7
button (available only for OMSG).
If the Path Trace is shorter than 16 bytes, it is filled with zero bytes (”0” hexadecimal).
14.6.2 High Order TP Configuration
Depending on the TP selected, a dialog appears for the configuration of the main parameters of the
following objects appears:
– VC-4 TTP
– VC-3 TTP
– AU–4 CTP
– C2 Signal Label
– J1 Path Trace
– Enabling Monitoring
– Enabling Generator
The following dialogs appears:

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 528 / 926
926
Figure 346. High Order TP Configuration (on W/OMSN)
J1 Path Trace
If the Path Trace is 16 bytes long, the first byte is a CRC7 checksum. This checksum is automatically
calculated by clicking on OK and can be visualized by clicking on the CRC7 button. It can also be modified
to customized values in the CRC7 text field.
If the Path Trace is shorter than 16 bytes, it is filled with zero bytes (”0” hexadecimal). Expected and
Transmitted fields are editable by the operator. Received field is read only. With the relevant button it is
possible to enable or disable TTI Monitoring.
Received fields is read only.
With the relevant button the operator can set the Expected field as:
– TTI Enable
– TTI Disable
– TTI Repeated
The Transmitted field can be set with TTI Enable or TTI Repeated byte
Empty TTI button permits to send an all zeroes path trace.

1AA 00014 0004 (9007) A4 – ALICE 04.10
C2 Signal Label
Insert a number between 0 and 255. The G.707 recommendations for the C2 Signal Label are:
3AL 89062 AA AA 529 / 926
926
– 0: Unequipped
– 1: Equipped non-specific

– 2: TUG structure

– 3: Locked TU-n
– 4: Asynchronous 34/45Mbit
– 18: Asynchronous 140Mbit
– 19: ATM
– 20: MAN, DQDB
– 21: FDDI.
In the “Transmitted” field it is possible to select the values:

• Automatic: the C2 Signal Label value is automatically selected by the NE according the VC
structure (not supported on OMSG).
• Equipped not specific (it corresponds to number 1)
To replace modified values with the default, enter the default manually according to the following table.
Table 15. Default Values for C2/V5 Signal Label
$ %$ $ ' ()
"& "&
9 9 9 EF
)
9 54 3 9
$
If the Clipboard dialog is applied (only available on OMSG), consider the following notes (For a description
of this dialog see chapter 3.8 “Clipboard“):
N.B. The current TP configuration can be applied to a number of TPs at once. To define the TPs the
current configuration should be assigned to, click on the Tp list button and open the Clipboard
dialog. As long as the clipboard is open, the buttons Cancel, Apply, OK and Refresh are
disabled. The Refresh button discards your entries, but leaves the dialog box open, the Apply
button, inserts the new entries and leaves open the dialog box, the OK button performs the
changes and closes the dialog box, the Cancel button discards the new entries and closes the
dialog box.
N.B. The current TP configuration data is only applied to the TPs listed in the Clipboard dialog. If
the TP of the TP Configuration dialog is not listed in the Clipboard dialog then it is not
configured!
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 530 / 926
926
14.6.3 Low Order TP Configuration (only available on OMSG)
Depending on the TP selected, a dialog to configure the main parameters of the following objects:
– VC-12 TTP (only provided on OMSG).

– V5 Signal Label
– J2 Path Trace
N.B. On W/OMSN the TP Configuration window can be open but the entries are discarded
J2 Path Trace
This checksum is automatically calculated by clicking on OK and can be visualized by clicking on the CRC7
button.
If the Path Trace is shorter than 16 bytes, it is filled with zero bytes (“0” hexadecimal).
V5 Signal Label
Insert a number between 0 and 7. The G.707 recommendations for the V5 Signal Label are:
– 0: Unequipped
– 1: Equipped non-specific
– 2: Asynchronous
– 3: Bit Synchronous
– 4: Byte Synchronous
To replace modified values with the default, enter the default manually according to Table 15. .
N.B. The Automatic option button in the TX side signal label area is not supported on the OMSG.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 531 / 926
926
Figure 347. Low Order TP Configuration on OMSG
The current TP configuration can be applied to a number of TPs at once. To define the TPs the current
configuration should be assigned to, click on the Tp list button and open the Clipboard dialog. As long
as the clipboard is open, the buttons Cancel, Apply, OK and Refresh are disabled. The Refresh button
discards your entries, but leaves the dialog box open, the Apply button, inserts the new entries and leaves
open the dialog box, the OK button performs the changes and closes the dialog box, the Cancel button
discards the new entries and closes the dialog box.
configured!
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 532 / 926
926
14.7 PDH TP / TP Frame Mode – Configuration
Port / Transmission
TP Configuration
TP Thresholds
...
The Frame Mode Configuration dialog can be opened
– in the Synchronization view: Select the T2 PDH Reference Source and select the “Frame Mode
Configuration” option from the Synchronization menu.
– in the Transmission view: Select any of the below mentioned PDH TPs and select the “PDH TP or
the Frame Mode Configuration” option from the Transmission menu.
This menu item enables the configuration of the most important transmission parameters for a PDH TP.
Only the parameters supported by the object are displayed. Supported options include Enable Framed
Mode and Enable CRC4 Mode .
This command is available for:
– E1-CTP
– E31-CTP equiv. e3MonCTP
– E32-CTP
– E4-CTP
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 533 / 926
926
The following dialog appears for USM 3.x , 4.x and a similar one for OSM 7.x on OMSG:

Figure 348. PDH Port Configuration
Common I/O 34 Mbit/s does not support Framed Mode –> Error message
The CRC4 option can only be selected for the 2 Mbit/s boards.
Enable CRC4 Mode is only available when Enable Framed Mode is selected and the TP supports the
CRC4 Mode.
If the Clipboard dialog is applied, consider the following notes (see chapter 3.8, “Clpboard”):
The current TP configuration can be applied to a number of TPs at once. To define the TPs the current
configuration should be assigned to, click on the Tp list button and open the Clipboard dialog. As long
as the clipboard is open, the buttons Cancel, Apply, OK and Refresh are disabled. The Refresh button
discards your entries, but leaves the dialog box open, the Apply button, inserts the new entries and leaves
open the dialog box, the OK button performs the changes and closes the dialog box, the Cancel button
discards the new entries and closes the dialog box.
configured!
– TP Frame Mode Configuration
A different menu is available for W/OMSN using USM 5.x and 6.x. This command is available for e–CTP
and p12Mon (see chapter 15.1.3.)
If the user has selected e–CTP, the data concerning the PRA section are retrieved from p12Mon of the
same port; if the PRA is enabled, all the dialog field are loaded with the attribute values of the associated
p12Mon and the user has a read only access to the “TP Frame Mode Configuration” dialog; otherwise,
if the PRA is disabled, all the dialog field are loaded with the attribute values of the e–CTP and the items
“Framed Signal Mode” section, “Framed with PRA” and “Framed with leased line PRA” are disabled.
If the user has selected p12Mon and enables/disables PRA, the dialog “TP Frame Mode Configuration”
sets the configured values to the same attributes for both p12Mon and e–CTP.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 534 / 926
926
Figure 349. TP Frame Mode Configuration
The windows contains the following graphical objects:
– ”Framed Signal Mode” that allows to configure the attribute framed Signal Mode; the user can
choose one of the following value:
• ”Unframed” (G.703 interface): the PRA function cannot be activated ;
• “Framed without PRA” (G.704): the behavior according to ETS 300–233 is applied in the
handling of bits of Time Slot 0 in terms of state, defect detection and consequent action;
• ”Framed with PRA” : PRA function are activated
• ”Framed with leased line PRA” : a proprietary leased line behavior is applied.
– “CRC4 Mode“ that defines the monitoring capabilities applied to the signal with a CRC multiframe:
• “Enabling”: enable or disable the CRC–4 error counting
• ”Remote Indication”: read–only field that indicates if status of CRC–4 error counting
functionality of far–end NE is enabled or disabled
– “Frame Status” that reports an indication of the received signal:
• ”no indication”
• “the 2Mb/s signal is multi–frame”
Press Ok to apply the parameters or Cancel to close the dialog.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 535 / 926
926
14.8 Alarm Persistency Time Configuration (on OMSG)
Port / Transmission

TP Configuration
TP Thresholds
...
This dialog helps to suppress oscillating alarms. Oscillating alarms are alarms which occur and disappear
in short periodical distances. This leads to endless alarm messages with no useful information.
Figure 350. Alarm Persistence Time Configuration Dialog
This dialog allows the operator to set the:
– Clearing Time
The Clearing Time is the adjustable time between the physical disappearing of an alarm and its
1AA 00014 0004 (9007) A4 – ALICE 04.10
disappearance from the display of the system.
– Raising Time
3AL 89062 AA AA 536 / 926
926
The Raising Time is the adjustable time between physical appearance of an alarm an its displaying
on the system.
Both times can be set between 0.1 sec and 30 sec for each TP individually. Figure 350. displays the default
of both parameters.
N.B. The Clearing and Raising Time of the Loss Of Frame (LOF) alarm has to be set on RSTTP. The
concerning configuration on the ElSTTP/OpSTTP does not influence the LOF alarm reporting.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 537 / 926
926
14.9 Degraded Signal Threshold / TP Threshold Configuration
The Degraded Signal Threshold Configuration option is available for OMSG using the USM 4.x. The TP
Threshold Configuration option is available for W/OMSN using the USM 4.x, 5.x and for OMSG using the

USM 7.x, 8.x ...

Transmission
Add TP
Expand >
Hide >
TP Configuration
Terminate TP
Disterminate TP
Cross Connection >
POM/SUT >
Performance >
Concatenation
Structure TPs >
Physical Media >

14.9.1 Degraded Signal Threshold
The dialog box allows the operator to set the:
– Bursty Degrade Consecutive
Number of allowed errored seconds before SD is alarmed.
– Bursty Degrade Threshold
Number of errored blocks per second. To roughly evaluate this number from the relating BER:
BER value x bitrate of the payload = errored blocks per second
E.g. BER 10–6 150 errored blocks per second (on MSTTP).
Select a value between 1 and the listed max. value for the Bursty Degrade threshold.
Table 16. Max. Values for Bursty Degrade Thresholds
* $ ' () (

1AA 00014 0004 (9007) A4 – ALICE 04.10
0@ $ 8<<<< 4<<< 9<<< 9<<< 5<<<

@
3AL 89062 AA AA 538 / 926
926
– Signal Degrade Threshold
– Enable CRC Mode

Figure 351. Degraded Signal Threshold Configuration Dialog
14.9.2 TP Thresholds Configuration
Port /Transmission
TP Configuration
TP Thresholds
...
This dialog allows the operator to set the alarm thresholds for different signal layers.
The user can select one of two different error distributions (not involved parameters are greyed out):
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 539 / 926
926
– Poisson distribution
(only supported for MSTTP)
enables configuration of the Excessive Bit Error Ratio (ExBER) threshold and of the Signal Degrade
(SD) threshold of the TP’s related counted primitive (Bx). Only the B2 ExBer (10–3 to 10–5 ) and B2

Signal Degrade (10–9 10–5 ) are now configured on W/OMSN.

– Bursty distribution (default)
enables configuration of the maximum number of errored frames and the total amount of bad blocks
per frame.
Figure 352. TP Thresholds Configuration Dialog on OMSG–CL2

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 540 / 926
926
!

" "
#$
( *56

#9 8+<D9+<<<
( *3

#9 D64+<<<
( *5

#9 5;9+<<<
E*3E*8
#8 4+<<<
E*59
#(
*9 9+<<<
Table 17. Max. Values for Bursty Signal Degrade Threshold
Depending on the TP selected, the following thresholds can be configured:
– B2 ExBER threshold (Poisson) (supported only for W/OMSN):

Bit Error Ratio (BER) given as 10E–n, with n in the range of 3...5.
Excession of the ExBER threshold is indicated by an EBER alarm on the related TP.
– Enable Consequent Actions : fixed to enabled
– B2 Signal Degrade threshold (Poisson) (supported only for W/OMSN):

Bit Error Ratio (BER) given as 10E–n, with n in the range of 5...9. and set the consequent actions
when the chosen threshold TP ExBer is reached (MS–RDI and MS–AIS).
Excession of the SD threshold is indicated by an SD alarm on the related TP.
– Bursty Parameters – threshold :

Absolute values 1, 10, 100, 1000 of detected errored blocks that form a bad interval (interval is the
1 second period used for performance monitoring). In 1674LG R.1.0 the window box dialog
visualizes a percentage of detected errored blocks: move the slide to the required value or use the
arrow buttons to increase or decrease the values in step of 10%. The max. values for each TP type
are listed in table Table 17.
– Bursty Parameters – Consecutive Bad Seconds:

This parameter defines the threshold number of consecutive bad intervals to be detected (interval
is the 1 second period used for performance monitoring). An interval is declared bad if the percentage
of detected errored blocks in that interval > degraded threshold.
Select an integer in the range of 2...10.
Press OK to apply the parameters and close the dialog or Cancel to dismiss any changes and close the
dialog.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 541 / 926
926
14.10 Terminate / Disterminate TP
Transmission

Add TP
Expand >
Hide >
TP Configuration
Terminate TP
Disterminate TP
Cross Connection >
POM/SUT >
Performance >
Concatenation
Structure TPs >
Physical Media >

Only one command in the menu is available, depending on whether a TP is terminated or not.
N.B. Terminate/Disterminate TPs can only be executed in the transmission view.
14.10.1 Terminate TP
Use this action to terminate a path.
It can be performed on a AU-4 CTP.
A cross-connection between the selected AU-4 CTP (= aTP) and a modifiable VC-4 TTP (= bTP) is
created. Three TUG-3 and TU-3 are created.
A cross appears in the icon of the terminated TP:

1AA 00014 0004 (9007) A4 – ALICE 04.10
If the TP is already cross-connected an error message appears.
3AL 89062 AA AA 542 / 926
926
14.10.2 Disterminate TP
Use this action to disterminate a path.

It can be performed on an AU-4 CTP.

The related cross-connection is deleted.
N.B. The distermination of an AU-4 CTP is not possible if the corresponding lower TPs are hidden.
The action is only available if the connected VC-4 TTP is visible. This is to make sure that the
correct connection is disterminated. Expand the AU-4 CTP before distermination by double
clicking on it.
N.B. In the case that the Distermination of AU4 is not successful (the Crossconnected-Icons of AU4
do not go away) they are POM/SUT configured under TU3CTP and/or VC4TTP. Delete the
POM/SUT manually and repeat the Distermination action.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 543 / 926
926
14.11 POM/SUT
Port / Transmission

...
AU4 Concatenation >

Cross Connection >
POM/SUT > Creation/Deletion
... Configuration
The commands of this menu item are for the management of the POM/SUT (Path Overhead
Monitoring/Supervised Unequipped Termination).
This command is available for:
– AU-4 CTP
– AU-4-4c CTP
– AU-4-16c CTP
– AU-4-64c CTP
– TU-3 CTP
– TU-12 CTP
Either POM or SUT can be active on a TP. That means:
– the POM value TTI Expected is preferred in case that POM and SUT are active on one TP
– the SUT value TTI Sent is only transmitted as long as the related TP is not cross connected or
terminated.
Disabling POM or SUT (whichever is active) leads to clearance of the current and all history PM data of
the related TP.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 544 / 926
926
14.11.1 POM/SUT Creation/Deletion
The following dialog opens:

Figure 353. POM/SUT Creation/Deletion
The Path Overhead Monitoring has the following parameters:
– Before Matrix (available only on AU–4 CTP)
– After Matrix
The Supervisory Unequipped Termination has the following parameters:
– Sink (before matrix)
– Sink (after matrix)
– Source
– Bidirectional
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 545 / 926
926
Tandem Connection Monitoring
Not available on 1674LG Rel.1.1.

Tandem Connection Termination

Not available on 1674LG Rel.1.1.
N.B. In some cases it is not possible to delete AND create POM and SUT objects in the same dialog
session. To avoid the problem, delete the POM and SUT objects no longer needed, close the
dialog, open it again (with the updated configuration) and create the new objects.
If the Clipboard dialog is applied, consider the following notes (see chapter 3.8, “Clipboard”):
N.B. POM/SUT can be created for a number of TPs at once. To define the TPs for which POM/SUT
shall be created, click on the Tp list button and open the Clipboard dialog. As long as the
clipboard is open, the buttons Close and Ok are disabled.
N.B. POM/SUT is only created for TPs listed in the Clipboard dialog. If the TP of the POM/SUT
Creation dialog is not as well listed in the Clipboard dialog, then it is not created!
Press Ok to apply the parameters and close the dialog. Press Close to close the dialog and discard any
changes.
POM/SUT displayed in the Port View depends on USM type: then the icons shown in Figure 354. are only
examples (the created POM icon is located in the opposite side to the expected one):

= =
= = 0

= =
=) = 0
Figure 354. Example of POM/SUT in Port View
Figure 355. shows the POM/SUT icons visualized on 1674LG Rel.1.1.
N.B. POM/SUT blocks in Figure 355. are shown not correctly in the Port View if you add new
POM/SUT block(s) while deleting existing blocks, e.g., create SUT while deleting both POM
blocks. To correctly update the display open another port in this window before displaying the
initial port again.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 546 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01

= =
= = 0
Figure 355. POM/SUT displayed on 1674LG Rel.1.1
926
3AL 89062 AA AA

= =
=) = 0
547 / 926
14.11.2 POM/SUT Configuration
Depending on the parameters selected in the POM/SUT Creation/Deletion dialog, not all sections of the
dialog are available.

N.B. It is possible to open the POM/SUT Configuration dialog for a CTP even if neither Path
Overhead Monitor nor Supervised Unequipped Termination was created before. No changes
can be made in this case and the values displayed will be ignored.
Figure 356. POM/SUT Configuration example
In case of Path Overhead Monitoring (POM) configuration it is possible to monitor the trace on a CTP if
POM is enabled. The path trace is passed through. Therefore the received value is transmitted.
The Supervisory Unequipped Termination (SUT) configuration enables the functionality to verify pathes
even if there is no cross connection implemented up to now. It is possible to enter a transmitted value in
field TTI Sent.
1AA 00014 0004 (9007) A4 – ALICE 04.10
If there is no structure below the CTP, the value entered in the field TTI Sent is transmitted directly.
3AL 89062 AA AA 548 / 926
926
TTI Definition
The TTI (Trail Trace Identifier) has a maximum length of 16 characters.

Click on CRC7 to calculate the checksum of the identifier.

The following TTI Definitions are available:
– TTI Expected with CRC7
– TTI Received with / without the display of CRC7 (depending on the NE type)
– TTI Sent with CRC7
The following TTI Types are available:
– TTI Enabled
– TTI Disabled
– TTI Repeated Byte
Error Distribution
Poisson and Burst . Not available on 1674LG Rel.1.1.
Alarm Severities
It allows to “Change” the ASAP assigned to the specified POM/SUT. Not displayed on 1674LG Rel.1.1.
TCT Consequent Actions
Not available. Displayed on 1674LG Rel.1.1. instead of “Alarm Severities” feature.
Thresholds
Set the thresholds of the following parameters:
– Signal Degrade (not available on OMSG)
Poisson mode only: from 10–5 to 10–9 .
– Excessive Error (not available on OMSG)
Poisson mode only: fixed to10–3 also if presented a selection from 10–3 to 10–5 .
– Threshold Bursty Degrade
Select a value between 1 and the listed max. value for the Bursty Degrade threshold (see Table 18. )
For new USM types, the listed values are: 1, 10, 100, 1000.
– Bursty Consecutive / Consecutive Bad Seconds
Select a value between 2 and 10 sec for the Bursty Degrade Consecutive.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 549 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01

@
0@ $
4<<<
% $
Table 18. Max. Values of Bursty Degrade Thresholds
4<<<
'
9<<<
)
926
3AL 89062 AA AA
9<<<
()
550 / 926
Alarm Timing
Not available.
Unequipped Trail
Not available.
If the Clipboard dialog is applied, consider the following notes (see chapter 3.8, “Clipboard”):
The current POM/SUT configuration can be applied to a number of TPs at once. To define the TPs the
current configuration should be assigned to, click on the Tp list button and open the Clipboard dialog.
For a description of this dialog see Chapter Clipboard. As long as the clipboard is open, the buttons
Cancel is disabled. The Refresh button discards any changes, but leaves the dialog box open.
N.B. The current POM/SUT configuration data is only applied to the TPs listed in the Clipboard
dialog. If the TP of the POM/SUT Configuration dialog is not listed in the Clipboard dialog then
it is not configured!
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 551 / 926
926
14.12 Structure TPs
Transmission

...
TP Configuration
TP Threshold
Terminate TP
Disterminate TP
Clipboard
AU4 Concatenation >
Cross Connection >
POM/SUT >
Performance >
Structure TPs > TU3
Loopback > TU12
MSP > VC3/VC4
Physical Media > VC12
...
This menu item provides the possibility of structuring and destructuring a selected TP. The level that is
selected defines how the signal is to be structured, e.g. if a VC-4 TTP (modVC4 object) is selected and
the menu item “TU12” is chosen, the signal is structured down to 63 TU-12 CTPs.
Cross-connected TPs cannot be structured at all.
The following synchronous TPs can be structured:
– modifiable VC-4 TTP to TU-3, TU-12
– TUG-3 to TU-3, TU-12
– TUG-2 to TU-12 (this is performed automatically).
N.B. To structure an STM-1 signal, first terminate the AU-4 CTP. This action creates a
cross-connection between the selected AU-4 CTP and a modifiable VC-4 TTP.
The following plesiochronous TPs can be structured:
– PPI on an IOB140 to VC-4, VC-12
– PPI on an IOB34 or an IOB45 to VC-3, VC-12.
Restriction
1AA 00014 0004 (9007) A4 – ALICE 04.10
A PPI on a common 34 MBit/s I/O cannot be structured to VC-12.
3AL 89062 AA AA 552 / 926
926
Structuring a Single TP
To structure a single TP, select this TP in the Transmission view, and then choose menu item Structure
TPs and the aimed structuring level from the Transmission menu.
Structuring a Number of TPs (on OMSG)
To structure a number of TPs of the same type at once proceed as follows:
1) Select menu item Clipboard from the Transmission menu. The Clipboard dialog opens.
2) Select the required structuring level in the dialog.
3) Click on the Add TP button to open the TP Search dialog. Add all those TPs to be structured
to the clipboard list. For more detailed information refer to Chapter Structure TPs.
4) Click on Start to start the structuring process. The items are processed from top to bottom of
the list. The current processing status of each item is displayed in the clipboard list.
Use the Ok button to cancel the structuring process. Note that the cancellation only affects those
TPs not processed at the time of cancellation. TPs already configured remain in this state.
Use the Continue button of the clipboard to continue the previously cancelled structuring
process using the clipboard TP list.
For more detailed information on the Clipboard dialog, refer to Chapter 3.8 Clipboard .
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 553 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
554 / 926
15 CROSS-CONNECTION MANAGEMENT
The Cross.Connection features are applied to OMSG, W/OMSN (WMSN and OMSN) and to many Alcatel
Q3NEs. In this chapter, these general NEs will be indicated with Q3NEs, otherwise they will be specified
with the indication “not available for/on ...” the family to which the Cross–Connection features cannot be
applied or “only available for/on ...” the family to which the Cross–Connection feature can only be applied
15.1 Introduction
15.1.1 Overview
The available commands for the “Cross–Connection” menu are reported for the different USM types in
the Chapter “Menu Commands”. In the following the reported menu command have to be considered only
for the option command described. The menu commands are properly represented but the menu list
sometimes is not updated.
The following paragraphs provide the user with information concerning operations on cross-connections:
– Paragraph “Multiplex Structures for SDH”

gives an overview on the SDH technology
– Paragraph “Definition of Termination Points”

gives an overview about the termination points implemented on the Alcatel Q3NEs
– Paragraph “Cross-Connection Types”

provides information concerning cross-connection types supported by the Alcatel Q3NEs
– Paragraph “Cross-Connection Protection”

provides information concerning cross-connection protection supported by the Alcatel Q3NEs
– Paragraph “Cross-Connection Management”

deals with cross-connection lists and filtering criteria
– Paragraph “Create/Modify Cross-Connections”

describes the creation and modification of cross-connections
– Paragraph “Activate/Deactivate/Delete Cross-Connections”

describes the activation, deactivation and deletion of cross-connections
– Paragraph “Split and Join Cross-Connections”

describes how to split or join bidirectional cross-connections
– Paragraph “Protection Switching”

deals with switching actions on cross-connections
– Paragraph “Port Switch Over”

deals with switching ports
– Paragraph “Blocking Info”

deals with blocking alarms
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Paragraph “Show Cross-Connected TPs”

describes the possibility of showing connections between two or more TPs of different hierarchies,
e.g. connection between AU-4 and VC-4.
3AL 89062 AA AA 555 / 926
926
15.1.2 Multiplex Structures for SDH
By introducing the Synchronous Digital Hierarchy (SDH), a standardized optical interface and a standard
management structure of transmission have been created. The SDH signal structure contains an

extended overhead as well as a fixed pointer controlled assignment of the user signal elements, thus

improving the possibilities of the network management.
Signals of the Synchronous and Plesiochronous Digital Hierarchy (PDH) are packed by synchronous
multiplexers into Virtual Containers (VC). The STM-1 signal structure is achieved by using the multiplex
structure complying with ITU-T and ETSI, (see Figure 357. ). Each of the user channels (2 Mbit/s, 34
Mbit/s, 45 Mbit/s and 140 Mbit/s) is packed into a container synchronous to the STM-1 frame according
to a predefined structure.
To adjust the plesiochronous signals to the synchronous network clock, certain filling algorithms are
available. Fixed fill bits are inserted into synchronous signals. A byte column (9 Byte) as Path Overhead
(POH) is added to the Container (C) generated. Path Overhead and Container together form the Virtual
Container (VC). With the pointer pointing to the start of the VC, in respect of the STM-1 frame, an
Administrative Unit (AU) or – if several Containers of a group are to be combined – a Tributary Unit (TU)
is generated. Several TUs form a Tributary Unit Group (TUG) and TUGs again can be combined into a
VC. Finally, the AU of the signal, together with the Section Overhead (SOH) make up the STM-1 frame.
N.B. The 1674LG, 4x4OMSG and 1670SM only connect Higher Order SDH Signals. ( I.e. PDHTPs
and LoSDHTPs are not available.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 556 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
05 0>
53<=) A3 EA3 "A3 A5 A>
05 08
EA8 A8 ?A8 08
/3F=) 1
83=) A8 EA8 "A8
0D
05 0D
6=) A9 EA9 A9 ?A9
:
08
:=
9=) A59 EA59 A59
03 E :=E =
:=) =
/5+F=) 1 A55 EA55 A55 ? :=) = =?
" :=" $ =

=*

926
3AL 89062 AA AA
=
Figure 357. SDH Multiplex Structure according to ITU-T G.707

=" =5635=7
557 / 926
The STM-1 frame consists of:
– a Section Overhead (SOH)

– an AU Pointer area

– a payload area
)/0,+1,2
( 3 )/0
(
,
- #

&
'
$ %,.,
3,4 5 +#
,
- #

&
Figure 358. Frame Construction within the Synchronous Digital Hierarchy
The STM-1 frame has a basic bit rate of 155.520 Mbit/s. A single user channel is packed into a Virtual
Container. These Virtual Containers are of different size and may be nested or packed differently.
Virtual Containers for the European bit rates:
– the STM-1 frame contains a VC-4,
– a VC-4 may contain one C-4 or three TUG-3,
– each TUG-3 may contain one VC-3 or seven TUG-2,
– each TUG-2 contains three VC-12 or one VC-2.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 558 / 926
926
An STM-1 user signal can be constructed of:
– either 1 x VC-4
– or 3 x VC-3
– or 2 x VC-3 + 7 x VC-2
– or 2 x VC-3 + 21 x VC-12
– or 1 x VC-3 + 14 x VC-2
– or 1 x VC-3 + 7 x VC-2 + 21 x VC-12
– or 21 x VC-2
– or 14 x VC-2 + 21 x VC-12
– or 7 x VC-2 + 42 x VC-12
– or 63 x VC-12.
STM-N signals are constructed by integer multiples of the basic signal STM-1 of 155.520 Mbit/s. For
example an STM-16 signal of 2.488.320 Mbit/s is generated by combining sixteen STM-1 signals byte
interleaved.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 559 / 926
926
15.1.3 Definition of Termination Points (TP)
When ports are depicted on the user interface, the following abbreviations are used.

This section concerns the multiplex structure (see Figure 357. ) as well as the information model of

object-oriented programming which was used when forming the user interface. As a rule, a Termination
Point (TP) is the starting and terminating point of a transmission segment. A distinction is made between
the following types of TPs:
– CTP (Connection Termination Point)

The CTP represents the termination of a connection. The transmission signal is ”terminated”, i.e.,
the received signal is monitored and the error signaling evaluated, while own-code signaling is
inserted in the transmitted signal.
– TTP (Trail Termination Point)

The TTP represents the termination of a transmission segment. The signal is monitored and passed
on after modification in one form or another.
Both TP types exist on the SDH level and the PDH level.
– CTPs on SDH level

On SDH level (see Figure 359. ) a distinction is made between the following CTPs:
• AU-4, AU–4–4c, AU–4–16c, AU–4–64c (Connection Termination Point)

This CTP represents both the creation and termination of an electrical (Au4) or optical (Au4P)
STM-N connection. The High-order Connection Supervision (HCS) function is included.
• TU-x (Connection Termination Point), i.e. TU-12 CTP, TU-2 CTP, TU-3 CTP.
The TU-x CTP represents both the creation and termination of a VC-x connection. The
Low-order Connection Supervision (LCS) function is included.
– CTPs on PDH level

On PDH level (see Figure 360. ), a distinction is made between the following CTPs:
• E4 (Connection Termination Point)

The E4-CTP represents the non–intrusive monitoring of incoming 140 Mbit/s PPI.
• S4 (Connection Termination Point)

The S4-CTP represents the non–intrusive monitoring of outgoing 140 Mbit/s PPI .





The E1-CTP represents the non–intrusive monitoring of incoming 2 Mbit/s PPI. The
1AA 00014 0004 (9007) A4 – ALICE 04.10
Mon.(Monitorinr) label indicates that is possible to enable the CRC4 control signal.
3AL 89062 AA AA 560 / 926
926
The S1-CTP represents the non–intrusive monitoring of outgoing 2 Mbit/s PPI . The
Mon.(Monitorinr) label indicates that is possible to enable the CRC4 control signal.
– TTPs on SDH level

On SDH level (see Figure 359. ) a distinction is made between the following TTPs:
• ES (Electrical Section TTP)

An ESTTP displays the physical characteristics of a port with electrical access (level and code
monitoring and conversion).
• OS (Optical Section TTP)

An OSTTP displays the physical characteristics of a port with optical access (level and code
monitoring and conversion).
• RST (Regenerator Section TTP)

An RSTTP displays the creation and/or termination of an RSOH (Regenerator Section
Overhead), i.e., rows 1 to 3 of the first 9xN columns of an STM-N frame.
• MST (Multiplexer Section TTP)

An MSTTP displays the creation and/or termination of an MSOH (Multiplexer Section
Overhead), i.e., rows 5 to 9 of the first 9xN columns of an STM-N frame.
• VC-4 (Trail Termination Point)

A VC-4 TTP represents both the creation and termination of a VC-4 path.
– TTPs on PDH level

On PDH level (see Figure 360. ) a distinction is made between the following TTPs:
• PPI (Trail Termination Point)

On the PDH side, an PPITTP corresponds to the ESTTP of the synchronous side. Depending
on the type, it can either display the characteristics of a 140 Mbit/s, a 45MBit/s, a 34 Mbit/s or
a 2 Mbit/s port.
• E4 (Trail Termination Point)

The E4-TTP represents the creation and/or termination of a 140 Mbit/s connection.

The E3-TTP represents the creation and/or termination of a 34 Mbit/s connection.

The E2-TTP represents the creation and/or termination of an 8 Mbit/s connection.



1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 561 / 926
926
– MSP definition
Transmit side, the MSNP (AU4–CTP) input enters two different MSNP/MSN (unProtected CTP)
sources and then the MSN–TTP working and protection sources (to insert the K1–K2 bytes) are sent
to the own SPI interfaces. Receive side, the working and protection MSN/MSNP outputs (AU4–CTP)

enter in the switching selector. The MSNP–TTP terminates the selected signal and checks the SSF

and the MSP protocol failure.
%

C

"*3=
EA3=
?8 ?8 ?8
*8=
?9 ?9 ?9 ?9
?9 ?9 ?9
*9=
*59=
*59=
*59=
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 359. SDH Transport Level Diagram
3AL 89062 AA AA 562 / 926
926

(

53<=) 3F=# 83=) 9=)
%3*
%3*
%89A
%85A
%8*
%5*
3 3
E*3=
%8*
E*8=
E*8=
%9*
E*59=
3 3
%9*
%5*
%5*
E*59=
E*59=
>) ==)
Figure 360. PDH Transport Level Diagram

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 563 / 926
926
15.1.4 Mapping Tables: TP Names on OMSG and W/OMSN
The TP names on the Q3–NEs reflect the software model the user interface is based on. Therefore they
differ from the TP names given in the ITU-T recommendations. The following tables list the TP names

mapping conventions in the “Transmission” View.

Table 19. PDH TPs

Table 20. SDH TPs

! " "
1AA 00014 0004 (9007) A4 – ALICE 04.10
! " "

3AL 89062 AA AA 564 / 926
926

15.1.5 Cross-Connection Types
A cross-connection represents the logical connection between the input and output of the matrix, called
the matrix port.
The matrix only receives and transmits signals in GTI format. The Generic Transport Interface GTI,
Alcatel’s standardized signal format for internal interfaces, is similar to the STM-1 format. The incoming
signals are mapped or converted to GTI format on the plesiochronous and synchronous I/O boards. This
frame is based on the STM-1 frame specified by ITU-T Recommendation G.707. It enables the transport
of all signals in the US hierarchy and ETSI hierarchy levels 1 to 4 (1.5 Mbit/s to 140 Mbit/s) mapped to
Virtual Containers (VCs) (see Figure 357. ).
The VCs are sent from the I/O boards to both copies of the Matrix (A and B) via the GTI. The matrix
performs the cross-connection on the VC-4, VC-3, VC-2 or VC-12 level and transfers the VCs to the
relevant I/O boards via GTI. The configuration of both matrix copies is always identical. On the I/O boards,
one GTI signal is selected from Copy A or Copy B, based on quality.
The Alcatel Q3NEs supports unidirectional, bidirectional and broadcast connections unprotected as well
as protected (SubNetwork Connection Protection SNCP).
15.1.5.1 Unidirectional Connection
Information is transmitted exclusively from the input port to the output port (point-to-point); there is no
routing in reverse direction.
ÀÀÀÀ
ÀÀÀÀ "6
ÈÈÈÈ
ÈÈÈÈ

ÀÀÀÀ ÈÈÈÈ

Figure 361. Unidirectional Connection
15.1.5.1.1 Bidirectional Connection
ÀÀÀÀ ÈÈÈÈ
Information is transmitted between input port and output port in both directions (point-to-point).
ÀÀÀÀ
ÀÀÀÀ
"6 ÈÈÈÈ
ÈÈÈÈ

Figure 362. Bidirectional Connection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 565 / 926
926
15.1.5.1.2 Broadcast Connection (Multi-leg)
In contrast to a cross-connection between just two points (point-to-point), one source and one sink, a
broadcast connection consist of one source and several sinks, different ‘legs’ that share the same source

TP.

ÈÈÈÈ
In the example below, information is broadcasted from one input to outputs A, B and C on three legs.
ÈÈÈÈ
ÈÈÈÈ
"
=5
ÀÀÀÀ
ÀÀÀÀ "6 =9
ÈÈÈÈ
ÈÈÈÈ
#
ÀÀÀÀ ÈÈÈÈ
=8
ÈÈÈÈ
ÈÈÈÈ
ÈÈÈÈ

Figure 363. Example of Broadcast Connection with Three Legs
– For OMSG matrix dimension
• LMC 448
• A decisive factor for the broadcasting capacity of the system is the expansion ratio of the matrix
input stage. The switching capacity is optimized with a maximum ratio of 1416. Decreasing
the expansion ratio to 1216 (recommended), 1016 or 816 increases the broadcasting
capacity but decreases the switching capacity to 384, 320 or 256 STM-1 port equivalents,
respectively.
• LMC 960
• This matrix configuration offers a constant expansion ratio of 2430.
A warning box indicates when the resources available for broadcast connections are exhausted.
N.B. Non-intrusive Monitoring

Adding a protection leg to a unidirectional cross-connection offers the ability to perform
non-intrusive monitoring on this cross-connection. No errors are introduced to the original
cross-connection with applying or removing the protection leg.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 566 / 926
926
15.1.6 Cross-Connection Protection (SNCP)
15.1.6.1 Protected Unidirectional Connection

A unidirectional connection is routed from Input A to the Output (primary route). In case of a failure, the
system automatically switches to the protection path from protection Input B to the Output. This second
connection is permanently kept in hot standby operation (see Figure 364. ).
ÈÈÈÈ
ÈÈÈÈ
ÈÈÈÈ
"
"6
ÈÈÈÈ
ÈÈÈÈ
ÈÈÈÈ
ÈÈÈÈ @ = ==
ÈÈÈÈ
ÈÈÈÈ #
Figure 364. Protected Unidirectional Connection
15.1.6.1.1 Protected Bidirectional Connection
A bidirectional connection is routed from Input A to the Output C (primary route). Either Input A (input
protected – see Figure 365. ) or Output C (output protected – see Figure 366. ) can be protected:
ÈÈÈÈ
ÈÈÈÈ ÀÀÀÀÀÀÀ
ÀÀÀÀÀÀÀ "6
ÈÈÈÈ "
ÀÀÀÀÀÀÀ ÈÈÈÈ
ÈÈÈÈ
ÈÈÈÈ
ÀÀÀÀÀÀÀ
ÈÈÈÈ

ÈÈÈÈ #
ÀÀÀÀÀÀÀ
ÀÀÀÀÀÀÀ
= ==

Figure 365. Bidirectional Connection – Input Protected
ÀÀÀÀÀÀÀ
ÈÈÈÈ
ÈÈÈÈ
ÀÀÀÀÀÀÀ
"6

ÈÈÈÈ ÀÀÀÀÀÀÀ ÈÈÈÈ

ÈÈÈÈ
ÈÈÈÈ #
ÀÀÀÀÀÀÀ
ÀÀÀÀÀÀÀ = ==
ÈÈÈÈ "
ÈÈÈÈ ÀÀÀÀÀÀÀ

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 366. Bidirectional Connection – Output Protected
3AL 89062 AA AA 567 / 926
926
15.1.6.1.2 Protected Broadcast Connection
The protected broadcast is realized as a set of independent, protected, unidirectional connections using
the same pair of input termination points, as illustrated in Figure 367. . Each protection can be forced,

locked out or switched independently. Therefore, if a failure occurs at a certain input, it is possible that only

some of the protections of the protected broadcast actually switch to the protection input.
ÈÈÈÈ
ÈÈÈÈ "6 5 ÈÈÈÈ
ÈÈÈÈ
"
ÈÈÈÈ "

ÈÈÈÈ
ÈÈÈÈ
ÈÈÈÈ
9
ÈÈÈÈ
#
ÈÈÈÈ
@
# 8
ÈÈÈÈ
ÈÈÈÈ
= ==
ÈÈÈÈ

Figure 367. Protected Broadcast
Figure 367. shows a broadcast connection from input A to outputs A, B and C. Leg 2 and 3 are protected
via input B, whereas leg 1 is not protected.
15.1.6.2 Drop and Continue Connection
A Drop and Continue connection is a composed by: (see Figure 368. )
• a unidirectional broadcast connection routed from Input A to the Output C and to Output B.
• a unidirectional connection from Input protecting B to Output C.
• a unidirectional connection from Output C to Input A.
Output C is protected; when receive from Input main the connection is defined normal, when receive
from Input Protecting main the connection is defined inverse.
All the connections are created in a single step of configuration.
ÈÈÈÈÈ
ÈÈÈÈÈ A
ÈÈÈÈ
ÈÈÈÈ B
ÈÈÈÈÈ Input
ÈÈÈÈ
ÈÈÈÈ C
Prot. input
Output
Figure 368. Drop and Continue – Normal

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 568 / 926
926
15.1.6.3 Drop and Continue Insert Connection
An example of Drop and Continue Insert Connection is presented in Figure 369.

The connections are created in a double step of configuration: two cross connection will be presented,
composed in the following way:
– First connection:
• a unidirectional broadcast connection routed from Input A to Output B and C
– Second connection:
• a protected unidirectional connection routed from Output C to Input A, with protecting Input B
ÈÈÈÈ
ÈÈÈÈ A
ÈÈÈÈ
ÈÈÈÈ B
ÈÈÈÈ ÈÈÈÈ ÈÈÈÈ

Input
ÈÈÈÈ
ÈÈÈÈ C
Prot. input
Output
Figure 369. Drop and Continue Insert Connection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 569 / 926
926
15.2 Cross-Connection Management
A list of cross-connections can be displayed in the Cross-Connection Management dialog (see

Figure 371. ). The dialog can be accessed via the Configuration, Transmission or Port view (see the

USM menu commands in chapter 2) .

N.B. This dialog does not provide information if the board is in standby (i.e. a MSP command has
been occured changing an active board into a standby one).
Configuration
NE Time...
Performance >
Set ACD Level... >
If a Cross–Connected TP has been selected, in the “Port View”, are highlighted: Cross Connection
Management, Modify Cross Connections and Browse Cross Connections. If no Cross Connections exists
are highlighted: Cross Connections Management and Create Cross Connections.
Port
...
Cross Connection > Cross Connection Management
... Create Cross Connections
Browse Cross Connections
If a Cross–Connected TP has been selected, in the “Transmission View”, are highlighted: Cross
Connection Management and Show Cross Connected TPs. If no Cross Connections exists, only the Cross
Connections Management is highlighted.
Transmission
...
Port Switch Over
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 570 / 926
926
After selecting a port, the Cross-Connection Management dialog displays the existing
cross-connections list. Without selecting a port the Cross-Connection Management dialog is initially
empty (see Figure 370. ). The existing cross-connections list is displayed selecting the “Search”
command.
There are two possibilities of displaying a list of cross-connections:
– display a list of all cross-connections:

do not enter any search criteria and press the Search button,
– display a filtered list of cross-connections:

enter the filter criteria (one or more) and then press the Search button. Set Ignore for attributes not
to be used as filtering criteria.
Use button Cancel Search to cancel an active search request or close the dialog.
To allow a longer cross-connection list within the dialog, the filter area can be hidden (and redisplayed)
using the button Toggle Filter.
Figure 370. Cross-Connection Management Dialog – Filter Area on OMSG
15.2.1 Search Criteria
– Name (not available on W/OMSN)

Select the mode of operation and enter the cross-connection name.
• Substring
enter any string related to the cross-connection name
• Exact Match
enter the exact cross-connection name
– ACD
This filter option can only be used, if at least one ACD is defined on the OMSG and one or more
cross-connections are assigned to this ACD(s).
Select the cross-connection Access Control Domain consisting of NML assignment and resource
domain (for further information see Chapter “Security Check”).
Select the NML assignment using the option button:
• RM (Regional Manager)
1AA 00014 0004 (9007) A4 – ALICE 04.10
• SY Manager (Synchonization)
• NPOS
3AL 89062 AA AA 571 / 926
926
• EML Manager (OMSG)
• Not assigned

Enter the resource domain in the text field. Leaving this text field empty corresponds to the resource

domain “Empty Domain”.
– Type
Select the connection type:
• Unidirectional
• Bidirectional
• Multipoint (unidirectional connections from the same input to different outputs)
• Drop&Continue (not available on OMSG)
– TP Class
Select one of the TP types involved in the requested cross-connection.
If the TP classes are not available (i.e. for the 4/4 OMSG the TP classes TU-3, TU-12, TU-2, VC-3,
VC-12 are not available), the selection of these classes as filter option returns an empty query result.
– Admin. State
Select the connection state:
• Activated
• Deactivated (only available on OMSG)
– Op. State
Select protection functionality:
• Enabled
• Disabled
– Protection
Select protection functionality:
• Protected
• Not protected
– Prot. State
Select the protection state (for more detailed information, refer to “ Protection Switching “ Chapter
15.7 ):
• Forced to I ( Input)
• Forced to P (Protecting)
• Manual SW (Switch) to I (Input)

1AA 00014 0004 (9007) A4 – ALICE 04.10
• Manual SW (Switch) to P (Protecting)
• Auto. SW (Switch) to I (Input)
3AL 89062 AA AA 572 / 926
926
• Auto. SW (Switch) to P ( Protecting)
• Lockout
• Normal I
The protected connection carries traffic and there is no switch request (normal state).
• Normal P
The protecting connection carries traffic after a switch and there is no request to switch back,
i.e. do not revert.
– TP ID Prefix
Enter the TP type and physical location of the port, or only the physical location at least down to board
level, according to the following format (for OMSG):
<rack#>–<subr.#>–<board#>–<port#>,<port#>#TP
(format for W/OMSN):

r<rack#>sr<subr.#>sl<sot#>/port#<#>-<port#>-TP
The # within brackets identifies a number.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 573 / 926
926
15.2.1.1 Cross-Connection List
After a successful search, a read only list of cross-connections matching the search criteria appears
(see Figure 371. ). The number of matching cross-connections is displayed in the upper left corner of the

list. The list contains information concerning the following parameters for each cross-connection:

– Name
On OMSG the name corrispond to the cross-connection trailname .
On W/OMSN the name is substituted with a number (automatically) assigned by NE management
– Prot. State
detailed switching information in the format:
<protection state> <traffic ind> (<location>:<signal state>–<switch status>,
[<location>:<signal state>–<switch status>])
• <protection state>
Normal, Auto, Lockout, Forced or Manual.
• <traffic ind>
indicates the location of current traffic:
P (Protecting input) or I (Input).
• <location>
indicates the location of the errored signal:
P (Protecting input) or I (Input)
• <signal state>
indicates the signal state: SD (Signal Degrade) or SF (Signal Failure)
• <switch status>
status of the switch:
c (completed) or p (pending)
Example:
Auto I (P:SD-c)
An Automatic switch occurred from the protecting input to the Input where the traffic is currently
located. The reason for the automatic switch was Signal Degrade in the Protecting input. The switch
was completed.
– Admin. State
connection state indicating whether cross-connection is A(activated) or D(deactivated)
– Op. State
indicates whether the connection is enabled or disabled
– Type
Direction-related connection type:
uni(directional), bi(directional), mp (multipoint), DC_N (Drop&Continue_Normal) or DC_I
(Drop&Continue_Inverse).
– Input
signal source; contains the TP type and physical location of the port according to the format
1AA 00014 0004 (9007) A4 – ALICE 04.10

The # within brackets identifies a number
3AL 89062 AA AA 574 / 926
926
– Protecting Input
protecting source (for protected cross-connections only); contains the TP type and physical location
of the port according to the format

– Output
signal destination
for point-to-point cross-connections, the TP ID of the destination is specified according to the format
<rack#>–<subr.#>–<board#>–<port#>,<port#>#TP ; for multi–leg cross–connections, the

string “multipleLegs” appears instead
rack#>sr<subr.#>sl<sot#>/port#<#>-<port#>-TP ;for multi–leg cross–connections, the string

“multipleLegs” appears instead
– NML Assignment
shows the NML assignment of each cross connection
– Res. Domain
shows the resource domain of each cross-connection
N.B. It is possible that a cross-connection is displayed on a red background within the list. This may
have two possible reasons (CCF anly or CCB+CCF active).
If there is an active “Connection Failed” alarm, the operational state is set to “Disabled”. In this
case the cross-connection was created in the software but not in the hardware.
If a “Connection Blocked” alarm occurs, it causes a “Connection Failed” alarm. The operational
state is set to “Disabled”. In this case use the menu option “Blocking Info” for information on
available non-blocking TPs.
– FFP – Fast Facility Protection

This dialog provides information whether Fast Facility Protection (FFP) is active or not.
At the bottom of the dialog is a range of buttons to start actions on the listed cross-connections. Before
starting any action apart from creation or printing, mark at least one cross-connection.
To mark several cross-connections (multi-select) that are listed in succession, select the first
cross-connection of a block with a mouse click and the last one with a mouse click while pressing the
<Shift> key.
Otherwise mark a number of individual cross-connections by clicking the mouse button while pressing the
<Control> key.
Deselect cross-connections by clicking on the respective row while simultaneously pressing the <Control>
key. To deselect a number of cross-connections at a time, press the <Shift> key and hold it down while
moving the mouse pointer to the last entry.
All actions that may affect traffic must be confirmed. A confirmation dialog pops up in this case and the
user has to confirm the requested action.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The following actions are available:
– Create (see para. 15.3)
3AL 89062 AA AA 575 / 926
926
The Main Cross-Connection dialog (see Figure 376. ) is opened.
– Modify (see also para. 15.3)

Available if just one cross-connection is selected from the list. The Main Cross-Connection dialog

(see Figure 376. ) is opened.
– Activate (only available on OMSG, see para. 15.4.1)
Available if at least one cross-connection is selected from the list.
– Deactivate (only available on OMSG, see para. 15.4.2)
– Delete (see para. 15.4.3)
– Split a Cross–Connection (only available on OMSG, see para. 15.6.1)
Available if at least one bidirectional cross connection is selected from the list.
– Join two Cross–Connections (only available on OMSG, see para. 15.6.2)
Available if two cross connections are selected.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 371. Cross-Connection Management Dialog (After Search)
3AL 89062 AA AA 576 / 926
926
– Protect... / SNCP Cmds... (different name for different USM type– see Chapter 15.7)
Available if exactly one active and protected cross-connection is selected from the list. The Switching
protection commands dialog is opened.
– Set ACD...
Available if exactly one protected cross-connection is selected from the list. The Set Domain dialog
is opened.
– Print (see chapter 3.10.” Print Dialog” )
Prints the filtered list of cross-connections.
The dialog has to be closed explicitly.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 577 / 926
926
15.3 Create/Modify Cross-Connections
Creation and modification of cross-connections are performed in the Main Cross-Connection dialog. The
dialog can be accessed via the Transmission or Port view or by using the Create or Modify buttons in

the Cross-Connection Management dialog (see Figure 371. ). The available menu commands are

described at the previous para.
To prevent operation faults, the system is designed according to the following guidelines:
– All operations that may affect traffic must be confirmed. The subsystem provides a confirmation
dialog box before the operation can be executed.
– If the window displays an existing cross-connection, the OK button is insensitive when this
cross-connection is assigned to NML or it is not assigned to the user profile.
– The OK button is also insensitive if the Regional Manager RM is assigned to the OMSG, i.e. the RM
is present in the Manager List.
– If the window is used to create a new cross-connection, the system verifies that the relevant TPs can
be used (not assigned to NML and assigned to the user profile) after the OK button is pressed. If a
specified TP is not permitted, the corresponding message box appears.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 578 / 926
926
15.3.1 Cross-Connection Parameters
A cross-connection is defined through a set of parameters which depend on the connection and protection
type. Only those parameters which are permitted within the current context can be accessed. All others
are disabled (faded gray).

To create a cross-connection, one or more of those parameters must be defined according to the
cross-connection type. Table 21. gives an overview about the optional and mandatory input parameters
for the various cross-connection types. Activate the relevant entry boxes first of all by clicking on them with
the mouse.
Configurable Parameters
– Type
Select the connection type:
• Unidirectional
• Bidirectional
• Drop&Continue (not available on OMSG)
– D&C Topology (not available on OMSG)

Select the direction for Drop&Continue:
• Normal
• Inverse
– Protection
Define the protection state:
• Protected
• Not Protected
– Prot. Criteria (only available for protected connections)

In the Protection Criteria dialog, the user can display and configure the criteria for automatic
protection switching (see Figure 372. ).
The following SNCP Type are available:
• SNCP–I (Inherently monitored Sub–Network Connection Protection)
• SNCP–N (Non–intrusively monitored Sub–Network Connection Protection)
• SNCP–S (Sub–layer Sub–Network Connection Protection) (Not operative in current release)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 579 / 926
926
Figure 372. Example of “Protection Criteria” for OMSG
Figure 373. Example of “Protection Criteria” for W/OMSN
The following criteria are always present and cannot be changed by the user ( SNCP–I ) :
• AU–TU-AIS (Alarm Indication Signal).
• AU–LOP (Loss Of Pointer)

1AA 00014 0004 (9007) A4 – ALICE 04.10
Depending on the TPs involved, the user can additionally configure ( SNCP–N ) :
• HP/LP Degraded (on OMSG)
3AL 89062 AA AA 580 / 926
926
• Path Trace Mismatch (on OMSG)
• ExBer (Excessive Bit error rate) (on W/OMSN). This protection criteria can be also configured
with a different window dialog ( similar to Figure 372. ).
The last two criteria are defined in a configuration file according to the NE and the TPs involved and
can be changed or not accordfing with the NE type.
N.B. In the standard setting, Signal Degraded (SD) is not used as criterion for protection
switching.
N.B. In the W/OMSN , the SNCP/N can be selected if the relative TP–POM has been created.
The SNCP–S will be provided with the Tandem connection termination or Tandem connection monitoring
features. The protection switching criteria are:
• SSF: AU–AIS, AU–LOP
• UNEQ (unequipment), TIM ( mismatch identifier tandem )
• LTC (loss of tandem connection), DEG (signal degrade)
– WTR (available only for protected connections on W/OMSN)

This is used when Revertive mode is active. The Wait To Restore protection period prevents several
protection switches being initiated as a result of an intermittent failure. The protected element must
be error-free during this defined period of time before a protected service is switched back to it.
The Wait To Restore time period is not configurable but fixed to 5 minutes.
– Revertive (available only for protected connections) (not on OMSG)

Select whether protection is to be revertive or not.
In Revertive mode, a protected service is switched back to its initial, protected element when the fault
has been eliminated.
In Non-revertive mode, switchover to the protecting element is maintained even after the fault has
been eliminated.
– HOT (available only for protected connections) Not operative in current release
To enter the Hold Off Time expressed in msec. HOT is the time between declaration of Signal
Degrade or Signal Fail, and the initialization of the protection switching algorithm.
– Name
Enter a significant name for the cross-connection. Not supported in the NE that assignees a fixed
number to the connection.
– Create active CC
In its default state, this check button is preselected and the cross-connection is activated immediately
after creation. Deselect this button to create a cross-connection which is not automatically activated.
In this equipment the connections are created active as default when confirm the screen. This field
is then not consistent.
– Input
Enter the location of the input TP. Use button Choose to select a TP (see chapter 14.4.1) or type in
1AA 00014 0004 (9007) A4 – ALICE 04.10
the TP name.
3AL 89062 AA AA 581 / 926
926
– Prot. Input
Enter the location of the protecting TP. Use button Choose to select a TP (see chapter 14.4.1) or type
in the TP name.

– Output

Enter the location of the output TP. It is possible to enter one or more output TPs. Use button Choose
to select a TP (see chapter 14.4.1) or type in the TP name. The output TP type has to match the input
TP type.
To enter more than one output TP and create a broadcast connection, proceed as described
previously and press button Add afterwards. The previously chosen TP is then moved to the list box
located below. Click the Choose button and select the next TP in the TP Search dialog. Otherwise,
select the input field and enter the name of the TP directly. Repeat this procedure for each destination
TP. A list of all the selected output TPs is displayed in the list box located below it.
To delete a leg from the list, select the TP in the list box and click on the Delete Leg button.
N.B. Non-intrusive Monitoring

Adding a protection leg to a unidirectional cross-connection offers the ability to perform
non-intrusive monitoring on this cross-connection. No errors are introduced to the original
cross-connection with applying or removing the protection leg.
Table 21. Optional and Mandatory Configurable Parameters for Cross-Connection Creation
1 #+2#+ 2# 6

6
! # ! #
# #

)
B A A
/ ?1 $

A >
A( A >
A(

>
A> >
A>
/ A 0 A 0
$ 1

A A A A
C $ $ A 0 A A
/ ?1
> 0 0 0 0
/ G>1
$ 0 0 0 0
/ G>1
(

( A
A

1AA 00014 0004 (9007) A4 – ALICE 04.10
A $)
0
3AL 89062 AA AA 582 / 926
926
Non-configurable Parameters
– CC Topology
The topology of the cross-connection is indicated via two icons. The left-hand icon displays the
current topology and the right one displays a view of the topology following confirmation of the current
modifications.
In addition, the color of an icon indicates the connection state of the cross-connection:
green –> active
brown –> inactive
The icon is set according to the entries made in Type and Protection:
TPs not cross-connected
Unidirectional, not protected
Bidirectional, not protected
Unidirectional, protected
Bidirectional, protected
Broadcast, not protected
Protected Broadcast
Drop & Continue normal (only available on W/OMSN)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 583 / 926
926
Drop & Continue inverse (only available on W/OMSN)

Loopback connection
unidirectional, same input and output TP
Figure 374. Cross-Connection Icons
7+8
= : = = :

= = = +=* =*
Figure 375. Creation of a Unidirectional, Non-Protected Cross-Connection
– Input TTI (only available on OMSG)

The received Trail Trace Identifier of the far end signal is displayed.
– Output TTI (only available on OMSG)

The Trail Trace Identifier of the transmitted (near end) signal is displayed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 584 / 926
926
15.3.2 Create a Cross-Connection
This chapter lists the steps the user has to take to create a cross-connection. For a detailed description
of the single parameters, refer to the previous chapter, for information on cross-connection types, refer
to the introductory chapter.

After the creation of a cross-connection, the cross-connection list in the Cross Connection Management
dialog is not automatically updated. Use the button Search in this dialog to update the list.
N.B. After the creation of a cross-connection, check its actual state in the Cross Connection
Management dialog. A cross-connection that is displayed on a red background within the list
has an active “ConnectionFailed” alarm, i.e. the cross-connection was not physically created.
Using menu option “Blocking Info”, information on available non-blocking TPs can be obtained
(only available on OMSG).
15.3.2.1 Create a Point-to-Point Cross-Connection (uni- or bidirectional)
1) Type: select “unidirectional” or “bidirectional”.
2) Protection: select “protected” or “unprotected”.
3) Name: (only available on OMSG)

type in a significant name for the cross-connection. This step is optional, but recommended for
easy identification of the cross-connection.
4) Create active CC: (only available on OMSG)

in its default state, this check button is selected and the cross-connection is active immediately
after creation (the administrative state is “unlocked”). To create a cross-connection that is not
automatically active after creation, deselect this button.
5) Input : to enter the input TP, click the Choose button and select the TP in the Search for Cross
Connection Input dialog (see Chapter “Add TP” for a more detailed description).
This dialog offers the possibility to list TPs according to different filter criteria. E.g. to obtain a list of
all not connected AU-4 TPs of a rack, first select the rack in the right list box, then select the filter
criteria ConnectionState “not connected” and Class “AU-4” and click on button Search. The
matching TPs are listed in the right listbox (see Figure 377. ). Select the output TPs in the list and
confirm with Ok. Make sure that the selected output TP type matches the input one (e.g. VC4-VC4,
AU4-VC4, AU4–AU4, AU4–4c–AU4–4c, AU4–16c–AU4–16c, AU4–64c–AU4–64c).
Or select the input field and enter the name of the TP directly.
6) Output : select or type in the output TP as described in Step 5 ). Make sure that the selected
output TP type matches the input one (e.g. VC4-VC4, AU4-VC4, AU4–AU4, AU4–4c–AU4–4c,
...).
The following steps only apply to protected cross-connections:
7) Prot. Input: select or type in the protection TP as described in Step 5 ).
8) Configure the Revertive mode.
9) Prot. Criteria: configure the criteria for automatic protection switching.

1AA 00014 0004 (9007) A4 – ALICE 04.10
10 ) HOT (Hold time):fill the editing field to configure the hold time value. This time establishes a
delay before the protection input switching (actually not supported).
Press the button Ok to confirm the creation.
3AL 89062 AA AA 585 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 376. Create a Bidirectional Protected Cross-Connection
586 / 926
15.3.2.2 Create a Broadcast Connection
1) Type: select “unidirectional”.

2) Protection: select “unprotected”.


type in a significant name for the cross-connection. This step is optional, but recommended for
easy identification of the cross-connection.

after creation. To create a cross-connection that is not automatically active after creation,
deselect this button.
Connection Input dialog (see Chapter “Add TP” for a more detailed description of the dialog
or step 5 of “Create a Point-to-Point Cross-Connection”). Or select the input field and enter the
name of the TP directly.
Or drag the selected TP in the Search for Cross Connection Input dialog and drop it in the
output field of the Main Cross Connection dialog.
6) Output : Select or type in the output TPs.
Click the Choose button and open the Search for Cross Connection Output dialog (see Chapter
“Add TP” for a more detailed description or step 5 of “Create a Point-to-Point Cross-Connection”).
After having finished the selection, click OK to close the Search for Cross Connection Output
dialog.
Press the button Add Leg to move the TP to the list box below. TPs not listed in this box are not
selected as output TP.
To delete a leg from the list, select the TP and click on Delete.
Press the button Ok to confirm creation.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 587 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 377. Search for Cross-Connection Output on W/OMSN
588 / 926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 378. Create an Unprotected Broadcast Cross-Connection
589 / 926
15.3.2.3 Create a Protected Broadcast Connection
1) Type: select “unidirectional”.

2) Protection: select “protected”.

type in a significant name for the cross-connection. This step is optional, but highly
recommended for identification of the cross-connection as broadcast connection.

after creation. To create a cross-connection that is not automatically active after creation,
deselect this button.
Connection Input dialog (see Chapter “Add TP” for a more detailed description of the dialog
or step 5 of “Create a Point-to-Point Cross-Connection”). Or select the input field and enter the
name of the TP directly.
6) Output : select or type in the output TP as described in Step 5 ). Make sure that the selected
output TP type matches the input one (e.g. VC4-VC4, AU4-VC4). Press the button Add Leg
to move the TP to the list box below. TPs not listed in this box are not selected as output TP.
To delete a leg from the list, select the TP and click on Delete.
7) Prot. Input: select or type in the protection TP as described in Step 5 ). Select the protected
output TP in the list box and click on Protect Leg. The leg is then marked “protected”. Repeat
this for each protected output TP. To unprotect a leg from the list, select the protected TP in the
list box and click on Unprotect Leg.
8) Configure the Revertive mode.
9) Configure the Protection Criteria (Prot. Criteria)
10 ) The HOT (Hold Off TIme) is not operative in current release
Press the button Ok to confirm the creation.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 590 / 926
926
15.3.3 Modify a Cross-Connection
When modifying a cross-connection, note that some of the transformations involved may affect traffic
(because the system may have to destroy and re-create the cross-connection to perform the necessary
transformation). As mentioned at the beginning of this chapter, the user is required to confirm operations
affecting traffic, i.e. a confirmation window warns the user.
Within the Main Cross Connection dialog, modification of a cross-connection is restricted to the name
and the protection state and the parameters required by the protection. Refer to Table 22. for an overview
of the accessible parameter when the protection state has been changed from “not protected” to
“protected” and vice versa. For a description of the parameters, please refer to the previous chapter.
Table 22. Modifiable Parameters
1 *#

# #
# #
A A
B
/ $) ?1 $ $

0 A
/ $ 1 0 A
A 0

0 A
C $ $ 0 A
> 0 0
/ $)
G>1
$ A A
/ $)
G>1
( 0 0

( 0 A
0 0
A )
0 )
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 591 / 926
926
The following few facts should be taken into consideration when modifying connections.
– Unprotect a protected cross-connection:

When a protected cross-connection is being unprotected (protection changed to “not protected”), the

dialog displays the additional option button Unprotected. It offers the choice of whether to keep the

protected input TP (Input) or the protecting input TP (Prot. Input) as the only signal source of the new
unprotected cross-connection. Ensure that the active TP is selected (i.e. check the protection state
in the Cross-Connection Management dialog).
In addition, a question box appears, asking the user to confirm the unprotect action.
– Protect an unprotected cross-connection:

When an unprotected cross-connection is being protected, the dialog displays the additional option
button Protected. Select the port that has to be protected:
• Output
• Input
In the standard setting the protected cross- connections are output protected (see Chapter
Cross-Connection Protection). To protect the input port, select Input.
– Exchanging input and output of a protected, bidirectional cross-connection:

If the input and output of a protected cross-connection are switched, the dialog entry “Prot. Input” is
updated.
N.B. After modification of a cross-connection, the cross-connection list in the Cross Connection
Management dialog is not automatically updated. Use button Search in this dialog to update
the list.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 592 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 379. Unprotect a Unidirectional Cross-Connection
593 / 926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
Figure 380. Protect one Leg of a Broadcast Connection
3AL 89062 AA AA
594 / 926
15.4 Activate/Deactivate/Delete Cross-Connections
The Cross–Connection created on W/OMSN is automatically “Active”. Then the para. 15.4.1 and 15.4.2
are only applicable to OMSG.
15.4.1 Activate a Cross-Connection (only available for OMSG)
The Cross Connection Management dialog provides the possibility of displaying a selection of existing
cross-connections (see Chapter Browse Cross-Connections). The connection state (Act = A or D) is
indicated in this connection list.
To activate a cross-connection, select one from the connection list (see Figure 371. ) and then click on the
Activate button to initiate the process. A confirmation box appears in which to confirm the state change
request. The connection in the list is automatically updated to indicate the new connection state (Act = A).
If the set of cross-connections selected from the list includes both activated and deactivated
cross-connections, clicking the Activate button only initiates actions on the deactivated
cross-connections which were selected.
15.4.2 Deactivate a Cross-Connection (only available for OMSG)
After creation, a cross-connection is automatically in an active state. To deactivate a cross-connection,

select one or several from the connection list (see Figure 371. ) and then click on the Deactivate button
to initiate the process. A confirmation box appears in which to confirm the state change request. The
connection in the list is automatically updated to indicate the new connection state (Admin. State =
Deactivated).
If the set of cross-connections selected from the list includes both activated and deactivated
cross-connections, clicking the Deactivate button only initiates actions on the activated
cross-connections which were selected.
N.B. In the current release, for broadcast cross-connections it is only possible to activate or
deactivate all involved cross-connection legs or none.
15.4.3 Delete a Cross-Connection
Only deactivated cross-connections should be deleted. However, deletion of active cross-connections is

possible.
To delete a cross-connection, select the corresponding connection from the list and click on the Delete
button. To prevent operation errors, the user must confirm the deletion request.
The deleted cross-connection automatically disappears from the connection list when the operation is
successful.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 595 / 926
926
15.5 Operative Sequence to execute Cross-Connections (for W/OMSN)
This paragraphs list the complete procedure to realize cross-connection moving among the various
menus.

Three main cases have been considered:
• an high order signal cross connection (AU4)

• an high order concatenated signal cross connection (AU4c)
• a low order signal cross connection (example : TU12)
Procedure for high order signal (AU4)
– Select ”Transmission” option from the ”View” menu
– Select ”Transmission” → ”Cross Connection” →”Cross Connection Management”
– Click on ”Create” in the Cross Connection Management windows; a new window called ”Main Cross
Connection” is opened.
• Select the correct value in the fields ”Type” and ”Protection”
– Click on ”Choose” relative to the ”Input” field; a new window called ”TP search” is opened.
• On the ”Equipment” field select the Board, in the ”Termination Points” field select the AU4
– Click on ”OK”; the ”TP search” window is closed.
– In the ”Main Cross Connection” window repeat the same on the “Output” field and on the ”Prot. Input”
field for protected connections
– Click on ”OK” in the ”Main Cross Connection” window to terminate the creation and subsequently
click on ”Cancel” to go to the ”Cross Connection Management” window.
– Click on ”Search” in the ”Cross Connection Management” window to see the new cross–connection
created.
Procedure for AU4 concatenated (AU4c)
N.B. Before to create an AU4 concatenated cross–connection is necessary to define that the AU4s
on a STM–4 board are concatenated as explained in para 12.4 on page 442.
– Select ”Transmission” option from the ”Views” menu
– Select ”Transmission” → ”Cross Connection” → ”Cross Connection Management”
– Click on ”Create” in the Cross Connection Management window; a new window called ”Main Cross
Connection” is opened.
• On the ”Equipment” field select the Board, in the ”Termination Points” field select the
concatenated AU4c (syntax example: r01sr1sl08/port#01–#01AU4P–4c )
1AA 00014 0004 (9007) A4 – ALICE 04.10
– In the ”Main Cross Connection” window repeat the same on the “Output” field and on the ”Prot. Input”
field for protected connections
3AL 89062 AA AA 596 / 926
926
created.
Procedure low order signal (example TU12)
– Select ”Transmission” option from the ”View” menu
– Select ”Transmission” →”Add TP”; a new window called ”Tp search” is opened.
• On the ”Equipment” field select the Board, In the ”Termination Points” field select the AU4 and
click on ”OK”;
In the transmission window the AU4 block is displayed;
– Select ”Transmission” → ”Terminate TP” ; a cross is displayed on the AU4 block
– Click twice on the AU4 block and on the VC4 block that appears, then selecting the shownTUG3
– Select ”Transmission” → ”Structure TPs” → then selecting the structure
N.B. The AU4 is then terminated on a VC4 of the matrix circuit of the COMPACT ADM unit.
The VC4 is automatically choosed and indicated as “port # n”, where “n” is the VC4
number.
This connection will appear on the Cross Connection Management view in a independent
line.
– If TU12 (example) are selected, in the transmission window clicking twice on the TUG3 and TUG2
blocks the TU12 are displayed
– Select the TU12 to be cross–connected and check the corrispondent r#sr#sl#/port and Tu# types to
recognize the TUs in the matrix.
– Select ”Transmission” → ”Cross Connection” → ”Cross Connection Management”; a new window

called ”Cross Connection Management” is opened.
– In the ”Cross Connection Management” window click on ”Create” button; a new window called ”Main
Cross Connection” is opened.
• On the ”Equipment” field select the Board, In the ”Termination Points” and the TP “Class” in the
TP Search Criteria to find the TP previously recognized (example: TU12 1.1.1)
– Repeat the same on the “Output” field and on the ”Prot. Input” field for protected connections
1AA 00014 0004 (9007) A4 – ALICE 04.10
created.
3AL 89062 AA AA 597 / 926
926
15.6 Split and Join Cross-Connections
15.6.1 Split a Cross-Connection

Precondition
Only bidirectional cross-connections can be split.
Split
Select one or more bidirectional cross connections from the list in the Cross Connection Management
dialog and press Split. The cross-connections are split without further confirmation from the user.
The original cross connection(s) disappear from the list in the Cross Connection Management dialog
after a successful action. The user has to press Search to see the new cross connections.
Depending on the protection state of the original cross-connection, the split action has the following effect:
Unprotected Cross-Connection
An unprotected bidirectional cross-connection is split into two unidirectional cross-connections with the
input TP in one of them being the output in the other and vice versa (see Figure 381. ).
The new cross connection has the same name and activation status as the old bidirectional one.
ÀÀÀ
ÀÀÀ "
ÀÀÀ
ÀÀÀ #
ÀÀÀ ÀÀÀ
"6
H

/ 51
ÀÀÀ
ÀÀÀ " "6
ÀÀÀ
ÀÀÀÀÀÀ
ÀÀÀ # # "6
ÀÀÀ
ÀÀÀ "
Figure 381. Split/Join Unprotected Bidirectional Cross-Connection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 598 / 926
926
Protected Cross-Connection
Splitting a protected connection results in:

– one protected unidirectional cross-connection and

– one broadcast connection with two legs.
The input A of the original cross-connect is leg A in the broadcast. The protecting input B of the original
cross-connection is leg B of the broadcast. Port C is the input of the broadcast and the output of the original
protected cross-connection.
ÈÈÈ
ÈÈÈ ÀÀÀÀÀ
ÀÀÀÀÀ "6
ÈÈÈ "
ÀÀÀÀÀ ÈÈÈ
ÈÈÈ
ÈÈÈ #
ÀÀÀÀÀ
ÀÀÀÀÀ ÈÈÈ
ÀÀÀÀÀ
H
ÈÈÈ
ÈÈÈ ÀÀÀÀÀ
ÀÀÀÀÀ "6
ÀÀÀÀÀ
ÀÀÀÀÀ
/
91
"6
ÈÈÈ
ÈÈÈ
ÈÈÈ ÀÀÀÀÀ ÈÈÈ ÈÈÈÈ ÀÀÀÀÀ ÈÈÈ
" " "
ÈÈÈ
ÈÈÈ
# ÀÀÀÀÀ
ÀÀÀÀÀ ÈÈÈ ÈÈÈÈ ÀÀÀÀÀ
ÀÀÀÀÀ

#
ÈÈÈ
ÈÈÈ #
ÀÀÀÀÀ ÀÀÀÀÀ )

*
Figure 382. Split/Join to Protected Bidirectional Cross-Connection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 599 / 926
926
15.6.2 Join Two Cross-Connections
Precondition

Two cross-connections can be joined if they match the following characteristics:

– The connections are either
1) both unprotected, unidirectional and the input is the output of the other one, or
2) one of them is protected and unidirectional, and the other one a broadcast with two legs.
Restriction: the input of the broadcast connection has to be the output of the protected
connection and the legs of the broadcast match the input and the protection input of the
unidirectional connection, also refer to Chapter Split a Cross-Connection, effect b).
– Both cross-connections have the same connection state (activated or deactivated).
– Both cross-connections have the operational state “enabled”, i.e. they are listed in black color in the
Cross Connection Management dialog (in contrary the operational state “disabled” is indicated with
red background color).
N.B. If a protected cross connection is forced to either the source or the protecting input, or lockout
is active, a transmission hit occurs when transforming the original cross connections to a
protected bidirectional cross connection (with equivalent switch status). Therefore do not use
the join action for protected cross connections with forced switch or lockout active.
Join
Select exactly two cross connections in the Cross Connection Management dialog and press the Join
button. The cross-connections are joined without further confirmation from the user.
The original cross connection(s) disappear from the list in the Cross Connection Management dialog
after a successful action. Press Search to see the new cross-connections in the list.
The result is either a bidirectional (case 1, see Figure 381. ) or a protected bidirectional (case 2, see
Figure 382. ) cross-connection.
If the original cross-connections have different names, the new name is a concatenation of the names of
both of them.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 600 / 926
926
15.7 Protection Switching
The Protection Actions dialog is displayed after clicking on the Protect... / SNCP Cmds... button in the
Cross Connection Management dialog (see Figure 371. ).
Users can only switch protection on cross-connections belonging to them and not assigned to the NML.
A second condition to take in account is that the protection switching concerns the protected
cross-connection (protection parameter is set to “protected”).
The three protection actions Force, Lock and Manual Switch belong to different levels, whereby Lock
has the highest priority and Manual Switch the lowest.
Note that a protection state can only be changed within the same or from a higher priority level, e.g. Force
To Protecting can be reverted with Release but not with Manual Switch To Input.
Figure 383. Protection Actions Dialog
The dialog window enables the user to perform protection- related operations on protected
cross-connections. These are:
– Force to Input
The cross-connection is switched to the protected input regardless of signal quality. Automatic
protection is disabled.
– Force to Protecting (Input)
The cross-connection is switched to the protecting input regardless of signal quality. Automatic
protection is disabled.
– Release Force
1AA 00014 0004 (9007) A4 – ALICE 04.10
Forced switching is disabled and automatic protection switching re-enabled.
3AL 89062 AA AA 601 / 926
926
– Manual Switch to Input (only available on OMSG)
The user can switch over to the protected input manually. Switching over is not executed if the signal
quality on the protected path is worse than on the protecting path. Moreover the system switches

back to protecting, if the signal quality on the protected path requires a switch.

– Manual Switch to Protecting (only available on OMSG)
The user can switch over to the protecting input manually. Switching over is not executed if the signal
quality on the protecting path is worse than on the protected path. Moreover the system switches
back to protected, if the signal quality on the protecting path requires a switch.
– Release Manual Switch (only available on OMSG)
A manual switch is disabled and automatic protection switching re-enabled.
– Lock Out / Lockout of
The connection path is locked for protection switching, i.e. neither forced nor manual switching can
be performed.
– Release Lockout
The protection lock is disabled.
N.B. All the operations listed are context-dependent and are enabled or disabled (“grayed”)
accordingly.
After completion of protection switching, the list entry in the Cross Connection Management dialog is
updated automatically.
After clicking on an action button and completing the action initiated, the dialog disappears automatically.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 602 / 926
926
15.8 Port Switch Over (only available for OMSG)
relocated physically from one board to another. The name of the TPs are logical names as
To find out, on which board the TP actually is implemented, mark the TP in the Port or
Transmission view and navigate to the related board with menu item “Show supported board”.
Use this option to substitute one AU-4 CTP for another within an AU-4–VC-4 cross-connection. The dialog
supports only TPs of the type “modifiableVc4TTPBidirectional” (ModVc4).
The substitution AU-4 CTP must not be cross-connected.
Figure 384. Port Switch Over
Expand the terminated AU-4 CTP using menu item “Show Cross Connected TP” and select the VC-4 TTP
(see also Figure 384. ). Then choose item Port Switch Over from the Transmission menu.
1) Press the Choose... button in the Port Switch Over dialog.

1AA 00014 0004 (9007) A4 – ALICE 04.10
2) Select the new substitution AU-4 CTP in the TP-Search dialog (see Figure 385. ).
Otherwise,
3AL 89062 AA AA 603 / 926
926
1) Select the input field and enter the name of the TP directly.
2) Confirm your choice with Ok. A question box appears, asking the user to confirm the port switch
over.

If the user confirms with Ok, the existing cross-connection is deleted and a new one is created with the
new AU-4 CTP. The cross-connection name and the administrative state are adopted from the previous
cross-connection.
In the case of a successive port switch over, the substituted “old” AU-4 CTP in the transmission view looses
the “x” symbol because it is no longer cross-connected. Additionally, the new cross-connection between
the same modifiable VC-4 TTP and the new AU-4 CTP is listed in the Cross-Connection Management
dialog.
If the creation of the new cross-connection fails, an attempt to restore the previous one is carried out.
Figure 385. Port Switch Over Dialog

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 604 / 926
926
15.9 Blocking Information (only available for OMSG)
This menu option can be used to gather information about output TPs available to create a non-blocking
cross-connection.
Transmission
...
Port Switch Over
Blocking Info ...
This menu option is only enabled if a TP with active Connection Blocked (CCB) alarm or Protection
Blocked (CPB) alarm is selected in the Transmission view.
Selecting the menu option opens the Blocking Info TPs dialog.
This dialog displays the Id of the selected TP and the type of active alarm (in Figure 386. this is TP
09-6-04-01,01#Au4 with a CCB alarm) together with a list of output TPs available to create a non-blocking
cross-connection.
N.B. This dialog displays TPs that are non-blocking. It still has to be checked whether the TPs
displayed are already cross-connected or not.
The dialog has to be explicitly closed.
How to proceed
In most cases, the user gets informed about a cross-connection failed due to a blocking situation through
the Cross Connection Management dialog. There, the currently created cross-connection is displayed
on a red background.
In order to receive information on available non-blocking output TPs, perform the following steps:
1) Drag and drop the input TP from the Cross Connection Management dialog to the
Transmission view.
2) Display its cross-connected TP selecting menu option Show Cross Connected TP.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3) Select this TP which has an active CCB or CPB alarm and select the Blocking Info menu
option.
3AL 89062 AA AA 605 / 926
926
4) The Blocking Info TPs dialog displays TPs available to create a non-blocking
cross-connection.
5) Select the blocked cross-connection in the Cross Connection Management dialog and modify

the output TP in accordance with the recommended output TPs of the Blocking Info TPs

dialog.
Figure 386. Example of Blocking Info TPs Dialog

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 606 / 926
926
15.10 Show Cross Connected TPs / Show All Cross Connected TPs
N.B. The menu entry ”Show Cross Connected Tps” may not work in the current release. In this case,
no cross connected TPs will be shown. A double click on the cross connected TPs delivers the
expected results.
Transmission
...
Cross Connection > Cross Connection Management...
... Create Cross Connections...
Modify Cross Connections...
Port Switch Over...
Blocking Info ...
An overview of signal flow can be requested by means of a user action. The user can select a TP and de-
pending on the selected TP initiate the action Show Cross Connected TPs or Show All Cross Con-
nected TPs (if available) from the Transmission view. The result is that all other TPs connected to the
currently selected TP are displayed. A line indicates the connection.
– If the cross connected TPs to be shown are not yet part of the actual Transmission view, they are
added with a normal sized TP field.
– If the cross connected TPs to be shown are already part of the actual Transmission view, they are
added once more with a smaller sized TP field.
This functionality should only be applied selectively (either for a single TP or selected group of TPs). Ex-
panding and hiding TPs that are associated with the currently selected TP (e.g. show all TPs that are above
the TU-12 CTP) enables all the related TPs to be added to the view so that the complete signal flow can
be illustrated.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 607 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 387. Show Cross Connected TPs (TP 01#Au4P selected)
608 / 926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 388. Show All Cross Connected TPs (TP MSP selected)
609 / 926
15.11 Cross Connections for 1696MS
This section, which describes the WDM cross connection management is applicable to 1696MS.

15.11.1 Cross Connections management
This section describes how to use the cross connection feature. It divided in two parts:
– Introduction,
– Procedure.
After the physical plugging and hardware setting, the MCC boards are in the following default configura-
tion:
– The optical transmitters (User TX and WDM TX) are OFF

– The 88 matrix has no connection.
Laser OFF
User Tx User Rx
OGPI
Back panel HF 8x8

electrical links Matrix
OCH
MCC
WDM Rx WDM Tx
Laser
OFF
MUX
OCH–A
WDM Line
channel signal
DMUX
Figure 389. MCC default cross–connection configuration
The cross–connection function is used to configure the matrix and activate the optical transmitters.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 610 / 926
926
Add–Drop cross connection
This configuration, also called ”Drop/Insert”, connects a client signal to a WDM channel (i.e.: an MCC
board OCH port to an OMDX/OADM board OCH–A port). In this configuration the back panel HF electrical
links are not used. It is used in line terminal and in back to back terminal architecture.
Client signal
MCC
User Tx User Rx
8x8
Matrix
OCH
WDM Rx WDM Tx
MUX
Line
OCH–A
WDM
channel signal
DMUX
Figure 390. Add and Drop cross–connection – Line terminal architecture
Client signal Client signal
MCC MCC
User Rx User Tx User Tx User Rx
8x8 8x8
Matrix Matrix
OCH OCH
East
West WDM Tx WDM Rx WDM Rx WDM Tx
MUX MUX
Line WDM WDM Line
OCH–A
OCH–A
signal channel channel signal

DMUX DMUX
Figure 391. Add and Drop cross–connection – OADM / back to back architecture
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 611 / 926
926
Pass–through cross–connection
This configuration applies on OADM architecture; it needs two adjacent MCC boards. It connects an
OCH_A port to another OCH_A port, via the back panel electrical links. In this configuration, the User RX

and User TX accesses of both MCC boards are not used and can be not equipped.

MCC MCC
User Rx User Tx User Tx User Rx
8x8 Matrix 8x8 Matrix
WDM Rx WDM Tx WDM Rx WDM Tx East

West
DMUX Back panel HF MUX
OCH–A
OCH–A
Line WDM electrical links WDM Line
signal channel channel signal
MUX DMUX
Figure 392. Pass–through cross–connection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 612 / 926
926
Protected cross–connection (O–SNCP)
This particular type of cross–connection is declared in the Craft Terminal in three steps:
– The setting of the OPC board,

– The configuration of the protection mode (see procedure: Configure the protection mode of a connec-
tion, page 617),
– The activation of the protection (see procedure: Activate the protection of a connection, page 617).
It appears in the main dialog box of cross connection management but it is not managed from this dialog
box.
Client signal
OGPI OPC
OGPI OGPI
MCC User Rx User Tx User Tx User Rx MCC
8x8 8x8
Matrix Matrix
WDM Tx WDM Rx WDM Rx WDM Tx
MUX MUX
Line Line
signal signal
DMUX DMUX
Figure 393. Protected cross–connection – OADM architecture

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 613 / 926
926
To manage the cross connections use the following procedures:

– Display the cross connections

– Display the cross connection configuration of an OCHA
– Create an add–drop cross connection
– Create a pass–through cross connection
– Remove a cross connection
– Configure the protection mode of a connection
– Activate the protection of a connection
– Deactivate the protection of a connection.
Display the cross connections
1) Choose the Configuration – Cross Connection Management menu option:

The Cross Connection Management dialog box appears.
2) Click on Search:
The existing cross connections appear in the list.
3) Click on Close to achieve the procedure.
The meaning of each column is:
– Prot. State column (only when an OPC is associated to a cross–connection) gives the protection
state. The possible values are:
• Normal I: Main path active, no alarm,
• Normal P: Protect path active, no alarm,
• Auto I Pp: Main path active, alarm on Protect path,
• Auto I IpPp: Main path active, alarm on Main and Protect paths,
• Auto P Ic: Protect path active, alarm on Main path that caused the switch on Protect,
• AutoP Ic Pp: Protect path active, alarm on Main and Protect paths,
• Lockout I: lock on Main path, no alarm,
• Lockout I Ip: lock on Main path, alarm on Protect path,
• Forced P: forced switch on Protect path, no alarm,
• Forced P Pp: forced switch on Protect path, alarm on Protect path,
• Forced P Ip: forced switch on Protect path, alarm on Main path,
• Forced P Ip Pp: forced switch on Protect path, alarm on Main and Protect paths,
– State column gives the cross connection state:

• A: activated,
• empty: not activated.
– Dir. column gives the Direction-related connection type:

• uni: unidirectional,
• bi: bidirectional
– Input column gives the signal source. It contains the TP type and physical location of the port accord-
ing to the format:
r<rack#>sr<subr.#>sl<slot#>/port#<port#>-TP
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Protecting Input column gives the protecting source. It contains the TP type and physical location
of the port according to the format:
3AL 89062 AA AA 614 / 926
926
– Output column gives the signal destination. It contains the TP type and physical location of the port
according to the format:
Create an add–drop (drop–insert) cross connection
1) Display the port (or transmission) view of the corresponding OMDX/OADM board.
2) Select the OCH–A.
3) Choose the Port (Transmission – Cross Connection – Create Cross Connection menu op-
tion:
The Main Cross Connection dialog box appears. The Input field is already filled with the identifi-
cation of the OCH–A selected in step 2.
4) Click on the Choose button at the right of the Output field:

The Choose a cross connectable TP dialog box appears.
5) Select the OCHTTP in the list.
6) Click on OK.
7) Back to the Main Cross Connection dialog box click on OK:

A cross–connection indicator appears under the graphical representation of the cross con-
nected ports.
Cross connection
symbol
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 394. OCHTTP port implied in a cross connection
3AL 89062 AA AA 615 / 926
926
Create pass–through cross connection
1) Display the port(or transmission) view of one of the two OMDX/OADM boards to cross–connect.

2) Select the input OCH–A.

3) Choose the Port(Transmission) – Cross Connection – Create Cross Connection menu op-
tion:
The Main Cross Connection dialog box appears. The Input field is already filled with the identifi-
cation of the OCHTTP selected in step 2.
4) Click on the Choose button at the right of the Output field:

The Choose a cross connectable TP dialog box appears.
5) Select the output OCH–A in the list.
6) Click on OK.
7) Back to the Main Cross Connection dialog box click on OK:

A cross–connection indicator appears under the graphical representation of the cross con-
nected ports.
Remove cross connections

2) Click on Search:
3) Select in the list the cross connections to remove. You can select one or more cross connec-
tions.
4) Click on Delete.
5) In the confirmation dialog box click on OK.
6) Back to the Cross Connection Management dialog box, click on Close to terminate.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 616 / 926
926
Configure the protection mode of a connection

2) Click on Search:
3) Select the protected connection.
4) Click on Protect....
The Protection Actions dialog box appears.
5) Select the desired mode.
6) Click on OK to return to the Cross Connection Management dialog box.
Activate the protection of a connection
Preliminary conditions:
The corresponding OPC board must have declared (see procedure: Set an OPC board.
1) Display the shelf view that contains the OPC board.
2) Select the OPC board.
3) Choose the Board – Optical Protection Configuration – Activate Optical Protection menu
option.
Deactivate the protection of a connection
This procedure has to be done before the removal of an OPC board, in order to align the management
base and the reality.
1) Display the shelf view that contains the OPC board.
2) Select the OPC board.
3) Choose the Board – Optical Protection Configuration – Deactivate Optical Protection

menu option.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 617 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
618 / 926
16 PERFORMANCE MONITORING
The Performance Monitoring features are applied to OMSG, W/OMSN (WMSN and OMSN) and to many
Alcatel Q3NEs. In this chapter, these general NEs will be indicated with Q3NEs, otherwise they will be
specified with the indication “not available for/on ...” the family to which the Performance features cannot
be applied or “only available for/on ...” the family to which the Performance feature can only be applied
16.1 Introduction
Performance monitoring is part of the supervision process. Events are counted at Trail Termination Points
and Connection Termination Points and stored in registers afterwards.
The information derived from the counts can be used to sectionalize faults and locate sources of
intermittent errors, and/or to determine the quality of the service.
The available commands for the “Performance” menu are reported for the different USM types in the
Chapter “Menu Commands”. In the following the reported menu command have to be considered only
for the option command described. The menu commands are properly represented but the menu can be,
sometimes , not updated.
16.1.1 Overview
The following chapters provide information on the following topics:
– Chapter Configuration deals with the configuration of performance monitoring
– Chapter Display Current Data deals with displaying current performance data
– Chapter Display History Data deals with displaying history performance data
– Chapter PM Threshold Table Selection deals with the selection of threshold tables
– Chapter PM Threshold Table Creation/Modification/Display deals with the creation and

modification of threshold tables
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 619 / 926
926
16.1.2 Supported Performance Counters
Performance counters are used to count transmission errors. A set of performance counters is provided
according to the Termination Point (TP), where performance measurement occurs. The user can start

performance monitoring on one or more subsets of counters for each TP; it is not possible to start individual

performance counters.
Near end performance monitoring events are:
– Background Block Error (BBE): A BBE counter measures the number of errored blocks which do
not occur as part of an SES.
– Errored Second (ES): A one second period with one or more errored blocks or with a defect.
– Severely Errored Second (SES): A one second period which contains > 30% of errored blocks, or
at least one Severely Disturbed Period (SDP). An SES is also counted as an ES.
– Unavailable Second (UAS): An Unavailable Second is a second which is part of the Unavailable
Time.
The corresponding Far End (FE) performance monitoring events are:
– Far End Background Block Error (FEBBE): A far end errored block which does not occur as part
of an FESES.
– Far End Errored Second (FEES): Identifies, at a terminal, a one second period with one or more
errored blocks or with a defect which were received by the Far End Terminal.
– Far End Severely Errored Second (FESES): Identifies, at a terminal, a one second period which
contains > 30% of errored blocks, or at least one Severely Disturbed Period (SDP) which was
received/detected by the Far End Terminal. An FESES is counted as an FEES.
– Far End Unavailable Second (FEUAS): An Unavailable Second is a second which is part of the
Unavailable Time at the far end.
The Termination Point (TP) type determines which performance monitoring events can be counted:
– SDH TPs
Both near end and far end counters are supported in receive direction of the signal for all SDH path
layers and for the multiplex section layer. For the regenerator section, no far end information is
transmitted and, therefore, only near end counting is supported.
– PDH TPs
Only near end counters are supported in receive direction for all PDH path layers.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 620 / 926
926
Further definitions:
– Background Block Error Ratio (BBER): The ratio of Background Block Errors (BBE) to total blocks
in the available time during a fixed measurement interval. The count of total blocks excludes all blocks
during SESs.
– Errored Block (EB): A block in which one or more bits associated with the block are erroneous.
– Remote Error Indicator (REI) [formerly Far End Block Error (FEBE)] : Identifies, at a terminal,
the count of errored blocks that were received by the far end terminal.
– Remote Defect Indicator (RDI) [formerly Far End Receive Failure (FERF)]: indicates to a terminal
that the far end terminal has detected an incoming failure.
– Unavailable Time (UAT): A period of unavailable time begins at the onset of 10 consecutive SES
events. These 10 seconds are considered to be part of unavailable time. A new period of available
time begins at the onset of 10 consecutive non-SES events.
– Near End Unavailable Second (NEUAS): An Unavailable Second is a second which is part of the
Unavailable Time.
– Pointer Justification Event (PJE): A PJE is an inversion of the I– or D– bits of the pointer, together
with an increment or decrement of the pointer value to signify a frequency justification.
– Out of Frame Second (OFS) (only on OMSG): An OFS is defined as a second in which one or more
out of frame events have occurred. This event is identified by the A1/A2 byte of the SDH Frame.
The counting of OFS is only supported for the regenerator section termination. Please note that this
counter is deprecated by ETSI and will be removed from international standards.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 621 / 926
926
16.1.3 Far End Performance Counting
Far end performance monitoring parameters are derived from Remote Defect Indicators (RDI) and
Remote Error Indicators (REI) (refer to Figure 395. ).

Node A Node B
Source Sink
trans- signifi- signifi-
mission cant bits
cant bits
signal
RDI insertion far end far end

defect counter
Sink near end
near end near end
near end defect defect counter
counter
far end
far end defect RDI inser-
counter tion Source
signifi- signifi-
trans-
cant bits cant bits
mission
signal
Figure 395. Far End Performance Monitoring Principles
– At Node A, the near end information represents the performance of the unidirectional section/path
from B to A, while the far end information represents the performance of the unidirectional
section/path from A to B.
– At Node B, the near end information represents the performance of the unidirectional section/path
from A to B, while the far end information represents the performance of the unidirectional
section/path from B to A.
Near end performance data at Node A and far end performance data at Node B correspond as long as
neither direction is disturbed, and vice versa.
In compliance with ETSI and ITU-T standards, far end errors cannot be counted in the case of near end
failures.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 622 / 926
926
16.1.4 Bidirectional counting (24 h Bi) for QoS
As specified in G.826, G.784 and ETSI 300417, the bidirectional PM collection for Quality of Service has
been supported by combining the information on each direction of transport to assess a single
unavailability state: the bidirectional path is in the unavailable state if either one or both directions are in
the unavailable state.

PM data are collected by a single UAS plus two sets of three event counters (BBE,ES,SES) for NE–PM
and FE–PM respectively. When the path transports unidirectional payload just the four counters for the
NE–PM are activated (BBE, ES, SES and UAS).
Data collection is performed only on 24 hours registers and the NE maintains a buffer of two registers: the
24hours current registers and the historical one.
16.1.5 End to End (e–e 24h) Performance Counting
VCn trails can be monitored in intermediate node through the activation of performance monitoring
process on Monitoring function.
As the trails are often responsible of the end–to–end customer service, the end to–end monitoring can be
requested to provide monitoring for Quality of Service purposes and , in addition, for network Maintenance
applications.
If SNCP is configured the Quality of Service collection have to be enable in the monitoring functions after
the matrix .
End to end monitoring is achieved by activation of Performance monitoring on the two direction of path
and using far–end primitives. This process can be unidirectional (for Monitoring) or bidirectional process
(for QoS).
In case of unidirectional process one direction can be monitored end to end and both 15minute and 24
h collection can be activated 15min./ 24H FE_BBE, FE–ES, FE–SES, FE–UAS on incoming or egress
signal depending of the POM is enable. The TCA are also evaluated in both 15 minute and 24 H counters.
The bidirectional process needs the presence on the two Monitoring functions in the two directions in one
NE and among the two monitoring function a 24 hour collection can be activated with the collection of
incFE_BBE, incFE–ES, IncFE–SES, UAS, eFE–BBE, eFE–es, eFE–SES.
16.1.6 Performance Monitoring on AU–PJE
AU PJE (Administrative unit point justification event) is an optional parameters request in G.784.
For AU PJE counters , the positive and negative PJE shall be counted separately on one selectable AU
within an STM–N signal, after the AU has been resynchronized to the local clock. Refer to G.783.
The number of positive and negative outgoing PJE per second are collected in 15 minutes and 24 H
counters. A history of 16 x 15minutes counters and 2x 24H are stored in the NE for each AU selected.
No Threshold crossing mechanism is supported on AU–PJE counters.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 623 / 926
926
16.1.7 Performance Data Collection
Near end and far end performance monitoring events are counted over fixed monitoring periods of 15
minutes and 24 hours. The 24-hour monitoring periods start at 00 : 00 (UTC) and the 15-minute monitoring

periods start at xx : 00, xx : 15, xx : 30 and xx : 45. Performance monitoring can be enabled and disabled

at any time during a monitoring period. An entity of all near end or far end performance monitoring events
is always counted, it is not possible to start individual performance counters (e.g. SES only). BBE, ES and
SES counting is stopped during Unavailable Time.
Event Counting
The performance events (e.g. SES) are counted in a counter per event. These counters are called the
current registers. At the end of the monitoring period, the contents of the current registers are transferred
to the first of the recent registers, together with a time stamp to identify the period (including the day). Time
stamping is performed using UTC (as for all alarms). After that, the current register is reset. It is also
possible to reset an individual current register manually.
Suspect Flag
A suspect interval flag is set as an indication that the data of the corresponding register may be either
incomplete or invalid. It is dispayed as “(S)” attached to the elapsed time.
Zero Suppression
Zero suppression is a basic mechanism to remove irrelevant PM information and to reduce the amount
of PM reports in the system. A PM report is suppressed and hence no history record is created by the entity
which is responsible for PM reporting when all of the following conditions are true for the monitoring period:
– an interval is error-free (all PM counter values are zero)

– PM was enabled during the entire monitoring interval (the elapsed time equals its nominal value, i.e.
900 for 15 min. and 86400 for 24 h)
– PM was running properly (the suspect interval flag is not set)
– Number suppressed intervals:
The feature displays the number of consecutive intervals for which suppression has occurred
because no PM problems have been counted (zero records suppressed). It is reflected in the PM
history data dialog.
By default, zero suppression is active for all PM enabled TPs. The number of suppressed intervals is
indicated.
Data Collection on OMSG
The Common I/O boards are provided both for OMSG and for W/OMSN, while the Dedicated I/O boards
are only provided for OMSG. Due to system architecture data collection on Dedicated I/O boards and
Common I/O boards differs:
– On Dedicated I/O boards, the event counters are reset on boards that were plugged out or when
a protection switch occurred. This means PM data of the current monitoring period is lost on these
boards. In the case of a protection switch, no complete PM data can be provided for the protected
TPs and only the period between the last switch and the end of the counting window is monitored.
The interval is marked as suspect.
N.B. PM data is not counted on Dedicated I/O boards that were plugged out at the moment of
1AA 00014 0004 (9007) A4 – ALICE 04.10
enabling data collection (see

#$"%$
description). Nevertheless, PM data
is counted on Dedicated I/O boards that were plugged in at the moment of enabling data
collection, but were plugged out and back in at some time during data collection.
3AL 89062 AA AA 624 / 926
926
– On Common I/O boards, the counters are not reset in case the board is plugged out or a protection
switch occurs but continue counting in both cases. Hence, they reflect the entire monitoring
period.PM data for both 15m/24h is available in plugged out state.
16.1.8 Performance Monitoring History
Performance Monitoring history data is necessary to assess the recent performance of transmission
systems. Such information can be used to sectionalize faults and to locate the source of intermittent errors.
History data, in the form of performance monitoring event counts, is stored in registers in the NE. All the
history registers are time stamped.
In compliance with ETSI and ITU-T standards, the history registers operate as follows:
The history data is contained in a stack of registers. There are sixteen 15-minute period registers and three
24-hour period registers per monitored event. These registers are called the recent registers. At the end
of each monitoring period, the contents of the current registers are moved to the first of the recent registers.
When all recent registers are full, the oldest information is discarded.
16.1.9 Thresholds
For quality supervision purposes, the recorded errors through the performance counters can be compared
to threshold levels. If a counter value has crossed a threshold level, a Threshold Crossing Alarm (TCA)
is transmitted to the alarm manager.
The threshold values are defined in threshold tables together with a severity and a flag indicating whether
crossing this value should be notified by an alarm and logged or only stored in the current problem list.
The user can only modify such tables on W/OMSN and create, modify and delete such tables on OMSG.
Two threshold mechanisms are supported:
– For 24-hour (implicit clearance) monitoring periods, one threshold value is defined: if the event count
reaches or exceeds the threshold value during the monitoring period, a TCA is generated. To clear
a TCA, the alarm must be manually acknowledged by the user.
– For 15-minute (explicit clearance) monitoring periods, two threshold values (set, reset) are defined:
a TCA is generated during the monitoring period when the event count reaches or exceeds the set
threshold value the first time. This TCA is automatically cleared by the system at the end of a following
monitoring period in which the event count is less than or equal to the reset threshold value and there
was neither an unavailable nor a suspect period during this monitoring period.
The TCA only reports the value of the counter which has crossed the threshold, it does not provide a
complete set of all counters. Therefore, the user has to explicitly retrieve all current performance data after
receiving the alarm. The user can retrieve this information from the Current Performance Management
Data dialog.
Additionally an explicit clearance of TCAs for all granularity periods is executed if one of the following
events occurs during the current interval:
– deletion of the current data instance (TP),
– resetting of counters (only for 24 h),
– increased thresholds (higher than current value of counters) (only for 24h),
– input signal was error free again until midnight,
1AA 00014 0004 (9007) A4 – ALICE 04.10
– For W/OMSN with new USM ( 5.x and 6.x ) the TCA alarms are deleted when the crossing table
values associated to the TP type has been removed.
3AL 89062 AA AA 625 / 926
926
16.2 PM Configuration
Select a TP in the Transmission or Port view and open the PM Configuration dialog (see Figure 396. )
using the menu item Configure Monitoring (this option is reachable consulting the“Menu Commands”

of Chapter 2).

Transmission/Port
...
Performance >
... Configure Monitoring
N.B. To configure PM for AU-4 CTPs, AU–4–4c CTPs and TU-x CTPs, Path Overhead Monitoring
(POM) or Supervised Unequipped Termination (SUT) must be created first (see description in
Chapter “POM/SUT” 14.11).
As long as the PM Configuration dialog is open, a change in the POM/SUT configuration is
not automatically recognized and displayed. This may lead to rejections or confirmations of
forbidden PM configurations. Therefore, make sure to reopen the PM Configuration dialog
each time the POM/SUT configuration is changed.
The PM Configuration dialog contains a text field, to identify the selected TP, and a notebook.
The selected TP is indicated in the first box at the top of the screen: TP Identifier.
In case the selected TP is an AU–4 CTP, AU–4–4c CTPs or an TU–x CTP, the PM Configuration dialog
also contains a cascading menu that allows to configured the POM/SUT options as follow:
– PathOverhMon After Matrix

– PathOverhMon Before Matrix
– TP (Performance is made on AU–PJE )
When more than one of the above options is chosen, a Question dialog box is displayed (see Figure 397. );
click on Cancel to continue or OK to interrupt any action.
Each notebook page presents a set of options for every entity:
– on the OMSG entities of unidirectional near and far end monitoring periods (15 min or 24 h) are
supported:
– on other Q3-NEs entities of bi-directional 24-hours monitoring period and end to end (24 h) period,
enable only for HPOM, are additionally supported.
To select a special page, click on the top part of the label.
– TP monitoring location selection:

The PathOverhMon/SupUneqTerm selects the monitoring location. For Common I/O boards,
1AA 00014 0004 (9007) A4 – ALICE 04.10
monitoring before and after matrix in any combination can be selected and configured separately for
above TPs under POM.
3AL 89062 AA AA 626 / 926
926
N.B. Monitoring after matrix is not supported for dedicated HW. (The SSF alarm generation
after matrix needs the “after” button activated. This is why it is not greyed out in case of
dedicated HW.)
Figure 396. PM Configuration Dialog on OMSG
Each entity has to be configured independently. For AU-4 CTP and TU-x CTP, the main criterion is POM
and SUT. Therefore, select the POM or SUT option first and then configure the associated datasets.
Confirm the configuration with Apply before continuing with a different POM or SUT option.
Enable any option within a notebook page by selecting the respective button.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 627 / 926
926
Figure 397. PM question dialog box
Activate any item within the page label by selecting the respective radio button.
– PathOverhMon/SupUneqTerm
• PathOverhMon Before Matrix

Path Overhead Monitoring before Matrix
• PathOverhMon After Matrix (only available for Common I/Os)

Path Overhead Monitoring after Matrix
– Mode
• Data Collection
Select this button to activate performance monitoring. Disabling Data Collection leads to
clearance of the current and all history data of this entity.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 628 / 926
926
• Create History Data
If this item is selected, history data collection is performed in the selected entity for the
corresponding TP.
Note that on disabling this mode item, no history data is available. Nevertheless, datasets
collected prior to deactivation are not cleared and are displayed after re-enabling the item. The
number of displayed datasets in the NE does not exceed 16 for 15 min. granularity and three
for 24 hours granularity ( 1 for W/OMSN ).
• Lock Data Collection

If Lock is selected, PM remains enabled but data collection is stopped. All history performance
data remain available. All current values are set to zero.
– EML OS Monitoring (only accessible from SH)

Not available at the Craft Terminal. (see 16.2.1)
– Notifications
– UAT
UAT (UnAvailable Time) alarms are created if enabled. This notification results in an UAT alarm in
the AS alarm manager.
– Suppress Additional Thresholds

If enabled, a TCA is only sent for the first counter that crosses its threshold within a monitoring period.
Example: BBE threshold is crossed which is indicated by a TCA. If the SES threshold is subsequently
crossed during the same period, no additional alarm is emitted.
If disabled, threshold crossing of each single event counter is notified.
N.B. The UAT option can only be selected during creation and cannot be subsequently modified.
– Threshold Table
Assign a threshold table to the selected TP. Only assign threshold tables that match the granularity
period of the datasets (i.e. a 15 min. threshold table must not be assigned to a 24 h dataset).
Click on button Attach... to open the PM Threshold Table Select dialog (see Figure 400. ) and
configure the threshold table (see Chapter “PM Threshold Table Selection”). Also click this button,
if the PM Threshold Table Select dialog is already open and the Attach button there is faded grey.
N.B. A threshold table can only be attached if Data Collection is enabled.
Select button Remove to disassociate the threshold table from the entity.
– Set Alarm Severity UAT
The severity for the UAT alarm can be configured. The list contains all ASAPs available in the system. The
severity for the UAT alarm within an ASAP is displayed in brackets. The system shows the following labels:
• ASAP Id
This field shows the label of the ASAP pointer assigned to the UAT alarm
• Set ASAP
Allows to set a new ASAP pointer for the UAT alarm. The Set ASAP button opens the window
1AA 00014 0004 (9007) A4 – ALICE 04.10
displayed in Figure 36. on page 149.
3AL 89062 AA AA 629 / 926
926
Threshold Table
Assign a threshold table to the selected entity. Only assign threshold tables that match the monitoring
period of the entity (i.e. a 15-minute threshold table must not be assigned to a 24-hour entity).

N.B. For Monitoring behind and before matrix the same (default) threshold table is created, even if
it is not explicitely configured in the PM configuration dialog (see Figure 396. ). To check the
actual thresholds or to change them, reopen the PM configuration dialog.
Notes for OMSG:
N.B. The current PM configuration can be applied to a number of TPs at once. To define the TPs the
current configuration should be assigned to, click on the Tp list button and open the Clipboard
dialog. For a description of this dialog see the Clipboard Chapter on Q3–NE Management. As
long as the clipboard is open, the buttons Cancel and Apply are disabled.
N.B. The current PM configuration data is only applied to the TPs listed in the Clipboard dialog: TPs
with POM/SUT (all CTP’s, AU4CTP, TU12CTP, ...) and TPs without POM/SUT (all TTP’s,
RSTTP, MSTTP, ...) cannot be configured at the same time, for example only a mixture of
AU4CTP, TU12CTP or a mixture of only RSTTP, MSTTP is allowed. If the TP of the PM
Configuration dialog is not listed in the Clipboard dialog then it is not configured!
Confirm the configuration with the button Apply before closing the dialog. Otherwise the configuration is
lost.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 630 / 926
926
16.2.1 EML–OS Monitoring
SH provides an effective feature to create the historical PM data base: EML OS Monitoring. Enabling this
feature the user can select the no archiving, the archiving or the archiving on threshold crossed options
(see Figure 398. ). During the archiving time the PM15m. data are stored for a period of 1 month, while
the PM 24h. data for a period of 3 months. After that, the old data are lost and substituted with the new
ones. With the “no archiving” option the archiving operation is suspended: only the previously stored data
can be shown. With the “archiving on threshold crossed” option are stored the PM values higher with
respect to the chosen threshold table.
Figure 398. EML OS monitoring window

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 631 / 926
926
16.3 PM Threshold Table Creation / Modification / Display
16.3.1 Creation

To open the PM Threshold Table Create dialog (see Figure 399. ), click the Create button in the PM
Threshold Table Selection dialog (see Figure 400. ).
Carry out the following steps to create a threshold table:
1) Enter a table name in the Name field.

Leading and succeeding blanks are ignored. Leaving the input field blank or entering only
blanks is not allowed and rejected.
2) Granularity: Select a monitoring period of 15 min. or 24 h for the entity.
3) Enter the set (Value Up) and the reset (Value Down) threshold values. Note that the reset val-
ue, if is supported, will be available with 15 min. monitoring periods.
Table 23. and Table 24. show the maximum performance monitoring event values. The re-
spective value is automatically reset to the maximum if a larger figure is entered.
If the entered reset value is higher than the set value, both values are exchanged automatically
by the system.
4) Select the alarm Severity for each PM attribute in case a threshold is crossed.
5) Disable Send notification if no notification message should be sent in the case of a crossed
threshold.
Go to point 7) if the Monitored Entity Types are not displayed
6) Select the TP type (only available on USM 3.x, 4.x) to which the created threshold table can be
attached, in the Monitored Entity Types list (i.e. a threshold table which only contains, e.g. the
entity type “au4CTPBidir” cannot be assigned to a TU-12 CTP):
• Select the relevant entity type in the Supported entity types list on the left.
• Add the selected entity type to the Selected entity types list on the right by clicking on button
>>.
(Use << to remove an entity type from the list.)
Repeat the procedure to select more entity types.
If no Monitored Entity Type is selected, all entity types are assigned.
7) Confirm the entries with Apply / OK to create the threshold table. A number of threshold tables
can be created from the same window.
Explicitly close the window with button Close.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 632 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 399. Create / Modify PM Threshold Table (USM 3.x, 4.x)
633 / 926
16.3.2 Modification
The PM Threshold Table Modify dialog (similar to Figure 399. ) pops up if a threshold table is selected
in the PM Threshold Table Selection dialog (see Figure 400. ) and the Modify button is clicked.

Carry out the following steps to modify a threshold table:
1) Modify the upper threshold value (Value Up) and the lower value (Value Down)
Table 23. and Table 24. show the allowed maximum performance parameter values.
2) Modify the alarm Severity for each PM attribute in case a threshold is crossed.
3) Disable Send notification if no notification message should be sent in the case of a crossed
threshold.
Note that the Name, Granularity and Monitored Entity Types of a threshold table can not be
changed. Create a new threshold table instead.
4) Confirm the modifications with Apply.
5) To modify more than one threshold table, do not close the dialog, but select the next threshold
table in the PM Threshold Table Selection dialog and press the Modify button
(see Figure 400. ).
Explicitly close the dialog with button Close.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 634 / 926
926
16.3.3 Display
The PM Threshold Table Display dialog (similar to Figure 399. ) pops up if a threshold table is selected
in the PM Threshold Table Selection dialog (see Figure 400. ) and the Display button is clicked.
Refer to the previous chapter for a description of the attribute values and types.
Max. Value for 15-min.

Performance Parameter Max. Value for 24-h period
period
BBE, FEBBE on STM-64
138,239,100 13,270,953,600
boards
BBE, FEBBE on STM-16
34,559,100 3,317,673,600
boards
BBE, FEBBE on STM-4 boards 8,639,100 829,353,600
BBE, FEBBE on STM-1 boards 2,159,100 207,273,600
BBE, FEBBE on all other
539,100 51,753,600
boards
OFS, ES, UAS, FEES, 900 86,400
SES, FESES 810 78,760
PJC high, PJC low 1,800,000 172,800,000
Table 23. Maximum Performance Parameter Values on W/OMSN
*7: +1 (5 : *7: +1 )$

*9 - # #
##%+ ,%##% 9+53D+348+63D 9+53D+348+63D
%+ ,%% ;<< 46+3<<
%+ ,%% 45< DD+D6<
Table 24. Maximum Threshold Values on OMSG
The PM Threshold Table is layer-independent. Layer-dependent maximum threshold values can be found
in ETSI-Standard EN 300 417-7-1.
N.B. Threshold values are normally much smaller than the maximum values.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 635 / 926
926
16.4 PM Threshold Table Selection
The PM Threshold Table Select dialog (see Figure 400. ) pops up if the Attach button is clicked in the
PM Configuration dialog (see Figure 396. ).

In addition, this dialog can be accessed using the Configuration menu:
Configuration
...
...
Performance >
Threshold Tables
...
The dialog presents a list of all threshold tables.
The following maximum numbers can be considered for OMSG:
– The system supports a total of 500 tables for each granularity (15 min./24h).
– Each Common I/O shelf supports a maximum of 128 threshold tables for each granularity (15
min./24h).
The threshold tables can be filtered according to the filtering criteria granulatity. Select 15 Minutes or
24 Hours granularity. Select both to list all threshold tables.
Press Filter to activate the filter criteria. The filtering area can be hidden by clicking on Hide Filter.
The user can perform the following actions:
– Create / Modify / Display a threshold table (refer to the previous section).
– Delete a threshold table
Mark the table in the list and click on the Delete button.
Note that a threshold table cannot be deleted if it is assigned to a PM entity. An error message
indicates this.
– Attach a selected threshold table to a TP entity. It is only available entering from the PM
Configuration dialog (see Figure 396. ). Different threshold tables can be assigned (Attached)
regarding monitoring before/after matrix capable TPs.
The user has to close the dialog explicitly by clicking on the button Close.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 636 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 400. PM Threshold Table Select
926
3AL 89062 AA AA
637 / 926
Table 25. Example of a threshold table entities association
N layer TP’s ASSOCIATED granularity

1 STM16 RS 15 minutes
2 STM16 RS 24 hours
4 STM4 RS 24 hours
6 STM1 RS 24 hours
7 STM16 MS NE / FE 15 minutes
8 STM16 MS NE / FE 24 hours
13 VC4 Path Termination NE / FE 15 minutes
14 VC4 Path Termination NE / FE 24 hours

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 638 / 926
926
16.5 Display PM Current Data
Select a TP in the Transmission or Port view and open the PM Current Data dialog (see Figure 401. )
using the menu item Display Current Data (this option is reachable consulting the“Menu Commands”
of Chapter 2).
Transmission/Port
...
Performance >
... Configure Monitoring
The PM Current Data dialog on OMSG can also be accessed in the Port Details dialog if available: select
a TP and click PM Current Data in the button area of the dialog.
The dialog includes a text field identifying the selected TP , and a notebook.
In case of AU-4 CTP and TU-x CTPs, the dialog also contains an option button showing the configured
POM / SUT option (see Figure 401. ). This option is the highest PM criterium, i.e. select the POM or SUT
option first and then the subordinate granularity period, as follow:

supported:
– on other Q3-NEs entities of bi-directional 24-hours monitoring period and end to end (24 h) period
are additionally supported.
To select a special page, click on the label.
N.B. The retrieval of the current data may take some time, depending on the number of activated PM
(up to 10 minutes on an STM-16 HiCap I/O Board).
– Administrative State
Indicates whether the PM collection is locked for the local user or not.
– Operational State
Indicates whether PM is enabled or disabled.
– Suspect Data
1AA 00014 0004 (9007) A4 – ALICE 04.10
Indicates if collection errors occurred during the collection period.
– Threshold Table
3AL 89062 AA AA 639 / 926
926
Indicates which threshold table is assigned to the entity.
– Current Problem List

Indicates current UAT (“Unavailable”) and TCA (“ThresholdCrossed”) alarms.

N.B. The entry “Unavailable ThresholdCrossed” indicates, that both alarms are active. Since
the text field is too small to display the full text at a time, use the cursor to scroll the text
field in this case.
– ASAP
Displays which Alarm Severity Assignment Profile was selected for UAT.
– Elapsed Time
Indicates the time which has elapsed since the monitoring interval was started. This information tells
the user whether the data collection covers the whole period.
In addition, the contents of the current registers related to the selected entity are displayed.
Press Reset to reset the performance parameter counter. The reset button is only enabled when the
current data is in administrative state “unlocked” and in operational state “enabled”.
Using the Print button, PM data can be saved to a file or printed on paper. A more detailed description
is provided in para.3.10
N.B. If no printer is installed, there is no error message indication.
Press the Refresh button to update the window contents and display the latest data.
N.B. When local access is denied for the Craft Terminal (CT) due to a manager connected to the NE,
the Close button stays disabled after reset of current data.
Close dialog via close option in the window menu (in the upper left corner of the dialog).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 640 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 401. PM Current Data dialog box
926
3AL 89062 AA AA
641 / 926
16.6 Display PM History Data
Select the TP in the Transmission or Port view and open the PM History Data dialog (see Figure 402. )
using the menu item Display History Data (this option is reachable consulting the“Menu Commands” of

Chapter 2).

Transmission/Port
...
Performance >
...
Configure Monitoring
The dialog includes a text field, identifying the selected TP, and a notebook.
In case of au4CTP and tuxCTPs, the PM History Data dialog also contains a cascading menu that allows
to configured the POM/SUT options (see Figure 402. ). This option is the main PM criterion, i.e. first select
the POM or SUT option and then the subordinate monitoring period, as follow:

supported:
– on other Q3-NEs entities of bi-directional 24-hours monitoring period and end to end (24 h) period,
enable only for HPOM, are additionally supported.
All the available entities related to the selected TP display the contents of the recent registers. Use the
scroll bar to browse through the entire data set.
Additionally both near and far end PM history data can be displayed together in one overview by selecting
15m or 24h monitoring periods.
The history data is displayed containing information concerning
– Interval End Time

End of the monitoring interval in the format dd.mm.yyyy hh:mm:ss.
– The near and far end event counters of an entity are displayed in separate tables.
– Elapsed Time
Indicating the time which has elapsed since monitoring was started
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Suspect flag
Suspect records are marked with “(s)” in the column Elapsed Time (refer to the PM introduction
chapter).
3AL 89062 AA AA 642 / 926
926
When no errors have been counted in the current registers, only the number of intervals is stored, where
no errors have been counted. In the history data dialog a record is displayed containing the sum of the
intervals for which no errors have been counted and zero counter values.
The number suppressed intervals is displayed in two ways:

– dashes are used if some records were missing, e.g. PM had been disabled or administrative state
is locked
– zero entries are used in all other cases.
The limit of 16 datasets for 15 min. granularity and 3 datasets (1 on W/OMSN) for 24 h granularity has to
be considered related to the NE capacity: when this limit is reached, the oldest set in the list is cleared
and the new entry displayed. For SH point of view, the objective, on annual basis, is to cover the PM history
data related to 100% of the paths with 24 h. granularity and 5% of the paths with 15 min. granularity .
Using the Print button, PM data can be saved to a file or printed on paper. A more detailed description
is provided in para.3.10.
N.B. If no printer is installed, there is no error message indication.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 402. PM History Data Dialog
3AL 89062 AA AA 643 / 926
926
16.7 Performance Monitoring for WDM equipment
This description is applicable to 1686WM, 1696MS and 1640WM: some features have been just men-
tioned at beginning of the “Performance Monitoring” chapter and are also here reported for a better view

of the subject.

16.7.1 Performance monitoring
This section describes the use of the performance monitoring feature. It is divided in two parts:
– Introduction,
– Procedures.
The Performance Monitoring domain on the NE covers the monitoring of counter values for trail termina-
tion points and connection termination points.
The Performance Monitoring domain counts these errors during specified granularity periods (15 min,
24h) and stores the values in history data logs.
For the purpose of quality supervision, the values of the error counters can be compared to user-defined
threshold levels. If a counter value has crossed a threshold level, a notification (threshold crossing alarm)
is issued.
The principle performance management functions are:
– Configuration of the counting interval for each performance measurement point.
– Collection of the performance data.
– Configuration of the quality thresholds that generate alarms and log records when predefined values
are exceeded.
Supported Performance Counters for 1686WM
The NE uses performance counters to count transmission errors.
A set of performance counters is provided according to the Termination Point (TP), where performance
measurement occurs.
The user can start performance monitoring on one subset of counters for each TP; it is not possible to start
individual performance counters.
B1 counters
B1 counters are associated to the boards WLA _TFEC16, WLA_TFEC_L16_2, WLA _TRFEC64; the fol-
lowing PM are supported:
• Erroneous Second (ES): a number of seconds with at least one CV (code violation) or a DS.
Severely Erroneous Second (SES): A number of seconds which contains more than 2400 CV
(erroneous B1 bits) or a DS. An SES is also counted as an ES.
Background Block Error (BBE): A BBE counter measures the number of erroneous blocks
which do occur as part of an SES.
1AA 00014 0004 (9007) A4 – ALICE 04.10
FEC counters
3AL 89062 AA AA 644 / 926
926
FEC counters are associated to the boards WLA_RFEC16, WLA_RFEC_L16_2, WLA_TRFEC64, RE-
GEN 10G; the following PM are supported:
• Background Errors Corrected (BEC): number of Corrected Errors Count (CEC) not occurring
during an SCS event.

• Severely Corrected Second (SCS): a number of seconds with Uncorrected Blocks (UB) higher
than zero or one Defect Second DS (a second with LOF or LOS alarm).
Supported Performance Countersfor 1696MS
The following performance counters are supported:
– Erroneous Second (ES): A one second period with one or more erroneous blocks or with a defect.
– Severely Erroneous Second (SES): A one second period which contains > 30% of erroneous
blocks, or at least one Severely Disturbed Period (SDP). An SES is also counted as an ES.
– Background Block Error (BBE): A BBE counter measures the number of erroneous blocks which
do occur as part of an SES.
Supported Performance Counters for 1640WM
The Performance Monitoring is available on the following boards: TRB30x_stm16, TRB40x, TRB50x,
TRB60x.
For this release the PM process provides according to the board type:
– TRB301 and TRB302:

• partial (ES and SES only) B1 monitoring for STM16 signals in transmission
• partial (BEC and BBU only) FEC monitoring of STM16 signals
– TRB401/50x:
• partial (ES and SES only) B1 monitoring for STM64 signals in transmission and reception
• partial (BEC and BBU only) monitoring of STM64 signals
– TRB60x:
• full (ES, SES and BBE) B1 monitoring for STM64 signals in transmission and reception
• full (SCS, BEC) monitoring of the CEC counter.
The FEC PM digital counters give a direct information on the transmission quality.
The B1 PM digital counters give a direct information on the client signal quality at ingress and egress sides.
The NE uses performance counters to count transmission errors.
A set of performance counters is provided according to the Termination Point (TP), where performance
measurement occurs.
The user can start performance monitoring on one or more subsets of counters for each TP; it is not pos-
sible to start individual performance counters.
The following performance counters are supported:
– Errored Second (ES): A one second period with one or more errored blocks or with a defect.
– Severely Errored Second (SES): A one second period which contains > 30% of errored blocks, or
at least one Severely Disturbed Period (SDP). An SES is also counted as an ES.
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Background Blocks Errors (BBE): A BBE counter measures the number of errored blocks which
do not occur as part of an SES.
3AL 89062 AA AA 645 / 926
926
– Severely Corrected Second (SCS): One second period in which DS (Defect Second) is set. Ds oc-
curs when there is a LWVL or LOFEC or at least 1 UBC (Uncorrected Block Count).
– Background Block Uncorrected (BBU): is the count of UCB (Uncorrected Block Count) events not
occured during a Severely Uncorrected Second (SUS)

– Background Error Correted (BEC): is the count of Corrected Errors Count (CEC) events not oc-

cured during a Severely Corrected Second (SCS).
Granularity
A monitoring period of defined granularity is associated with each performance counter.
This NE supports unidirectional PM of 15 minute and 24 hour granularity. After the monitoring period has
elapsed, the performance data is stored in the associated history data log.
Time stamping of history records is performed using UTC (as for all alarms).
The measurement intervals start at 00 : 00 (UTC) for 24-hour periods and at xx : 00, xx : 15, xx : 30 and
xx : 45 for 15-minute periods.
Data Collection
N.B. PM data is not counted on boards that were plugged out at the moment of enabling data collec-
tion. Nevertheless, PM data is counted on boards that were plugged in at the moment of enab-
ling data collection, but were plugged out and back in some time during data collection.
Performance Monitoring can be started at any time.
As soon as Performance Monitoring is started on the USM, current PM data is collected on the I/O boards,
incrementing the performance counters each time an error is detected.
The performance data counted is evaluated every quarter of an hour or every 24 hours and stored there
in a history record.
When the user disables the monitoring of a TP within the first 10 minutes of a 15-minute period, it is pos-
sible that have still not been received the PM data of the previous monitoring interval.
Since PM data is not stored after monitoring is disabled, the PM data of the previous interval is lost in this
case.
If equipment or line protection switching occurs during a counting interval, the NE does not provide com-
plete performance measurement for the protected TPs.
Only the period between the last switch and the end of the counting window is counted.
The interval is marked for suspect data and the elapsed time indicates the length of the measured period.
Thresholds
For quality supervision purposes, the recorded errors through the performance counters can be compared
to threshold levels. If a counter value has crossed a threshold level, a Threshold Crossing Alarm (TCA)
is transmitted to the alarm manager.
The threshold values are defined in threshold tables together with a severity and a flag indicating whether
crossing this value should be notified by an alarm and logged or only stored in the current problem list.
The user can display and modify such tables.
Different thresholds can be assigned for granularity of 15 minutes and 24 hours.
The TCA only reports the value of the counter which has crossed the threshold, it does not provide a com-
1AA 00014 0004 (9007) A4 – ALICE 04.10
plete set of all counters. Therefore, the user has to explicitly retrieve all current performance data after
receiving the alarm. The user can retrieve this information from a dialog box.
3AL 89062 AA AA 646 / 926
926
The system behavior concerning the clearance of 15 min. and 24 h TCAs differs:
– 15 min. (explicit clearance):

A TCA is only indicated once in the alarm manager, even if the same threshold is crossed several
times a day.
TCAs are automatically cleared by the system after one error-free 15 min. interval.
– 24 h (implicit clearance):
A TCA is indicated for each interval in which the related threshold has been crossed. The system
implicitly clear TCAs, at the end of the 24 hours.
The following limitations apply for explicit clearance:

– The value of the low threshold is fixed to “0” (only a single threshold is provided by a threshold table).
– An SES threshold crossing is cleared at the end of the interval if no unavailability was detected and
SES had not reached the low threshold (low threshold equal to 0).
– Even in case of a suspect interval the TCA is cleared if no unavailability was detected and the low
threshold had not been reached.
Additionally an explicit clearance of TCAs for all granularity periods is executed if one of the following
events occurs during the current interval:
– deletion of the current data instance,

– resetting of counters,
– increased thresholds (higher than current value of counters).
N.B. For 1640WM
– For the TRB4xx and TRB5xx, the SES threshold is compliant with ANSI standard:
– OC 48 (STM–16): SES threshold = 2392
– OC192 (STM–64): SES threshold = 8854
– For the TRB6xx, the SES threshold is:

– OC192 (STM–64): SES threshold = 2400 (whatever the bit rate).
– For the TRB50x, when a LOW is generated on the received side of the board, the BBU and
the B1 counters are frozen, no BBU and SES counters are incremented.
– In order to avoid overflow on BEC counter, the value shall be presented at the Q3 interface
divided by a ”division factor”:
– 2.5Gb/s PM: BEC at the Q3 interface is divided by 128 (7 bits)
– 10Gb/s PM: BEC at the Q3 interface is divided by 512 (9 bits)
16.7.1.2 Performance Monitoring procedures
Performance monitoring includes the following activities:
– Management of the performance threshold tables:

• Display a threshold table
• Modify a threshold table
– Start and configuration of the performance monitoring:

• Create a trail monitoring function on a TP (B1 counter for 1686WM)
• Start performance monitoring on a TP (B1 counter for 1686WM)
•
1AA 00014 0004 (9007) A4 – ALICE 04.10
Start performance monitoring on FEC

• Stop performance monitoring of a Tp
• Delete a trail monitoring function on a Tp (B1 counter for 1686WM)
3AL 89062 AA AA 647 / 926
926
– Consultation of the performance data:
• Consult the performance current data
• Consult the performance history data.

Display a threshold table

1) Choose the Configuration–Performance–Threshold Tables.
The PM Threshold Table Select dialog box is displayed.
2) In the table list select the table you want to display:

– table #9 is for the 15 minutes FEC counters,
– table #8 is for the 24 hours FEC counters.
– table #3 is for the 15 minutes counters ( B1 for 1686WM),

– table #2 is for the 24 hours counters ( B1 for 1686WM).
3) Click on Display:
The PM Threshold Table Display dialog box is displayed.
4) Click on Close.
5) To see another table, go back to step 2 ).
Modify a threshold table
1) Choose the Configuration–Performance–Threshold Tables.

The PM Threshold Table Select dialog box is displayed.
2) In the table list select the table you want to modify:

– table #9 is for the 15 minutes FEC counters,
– table #8 is for the 24 hours FEC counters.
– table #3 is for the 15 minutes counters ( B1 for 1686WM),

– table #2 is for the 24 hours counters ( B1 for 1686WM).
3) Click on Modify:
The PM Threshold Table Modify dialog box is displayed.
4) Do the needed modifications:

– Type in the Value Up and Value Down columns the new values for the high and low thresh-
olds of each counter type. The table below indicates and the maximum threshold values.
Tables (9 / 8) available for FEC counters
Parameter Maximum Value Maximum Value

(15 minutes) (24 h)
SCS 900 86,400
BEC 22,499 ,100 2,159,913,600

1AA 00014 0004 (9007) A4 – ALICE 04.10
Tables (3 /2) available for B1 and Tp counters
3AL 89062 AA AA 648 / 926
926
Parameter Maximum Value Maximum Value
(15 minutes) (24 h)
ES 900 86,400
SES 810 78,760
BBE 2,159,100 207,273,600
Tables (3 /2) available for Tp (1640WM) counters
Performance Parameter Maximum Value Maximum Value

(15 minutes) (24 h)
BBE (a) 2,159,100 207,273,600
ES (b) 900 86,400
SES (c) 810 78,760
BBU (d) 9 000 000 864 000 000
US (f) 0 0
SUS (f) 0 0
BEC (e) 17 496 000 1 679 616 000
CS (f) 0 0
SCS (b) 900 86,400
(a): The regenerator section trail monitor process 8000 blocks/second. Therefore it can detect a maximum
of ((8000 X 30%) –1) = 2399 BBE per second.
(b): The worse case is all seconds errored.
(c): The worse case is 9 SES every 10 seconds.
(d): Corresponding to 10.000 uncorrected blocks per second (these values will probably never be
reached)
(e): Calculated with the hypothesis of 10–3 BER
(f): These counters are never incremented
– Set the alarm Severity you want to affect to the TCAs (threshold Crossing Alarms)
reached by each counter type,
– In the Send notification column choose yes or no to send or not a notification when a TCA
in reached.
5) Click on Apply.
Create a trail monitoring function on a TP ( B1 counter for 1686WM):
1) Display the port view of the corresponding board.

1AA 00014 0004 (9007) A4 – ALICE 04.10
2) Select the OGPI block.
3) Choose the Port–Trail Monitor–Create menu option:

a trail monitor icon appears beside the selected port.
3AL 89062 AA AA 649 / 926
926
Trail monitor on OGPI correspond to the Tx side (SDH)
Trail monitor on OCH correspond to the Rx side (WDM)

Tx
Trail monitor icon Rx

The block manages
alarms associated Trail monitor icon
to SDH frame The block manages
alarms associated
to WDM line
Start performance monitoring of a Tp ( B1counter for 1686WM):
1) Select the trail monitoring icon.
2) Choose the Port–Performance–Configure Monitoring menu option:

The PM Configuration dialog box appears.
3) Select the tab corresponding to the counters you want to configure;

– NE 15m to set the performance activity of the 15 minutes counters,
– NE 24h to set the performance activity of the 24 hours counters.
N.B. It allows you to configure the two types of counters independently. By default the
NE 15m page is displayed first.
4) In the Mode area for 1686WM:

– Tick the Create Current Data box to allow history data collection.
– Leave the Lock Data Collection box unticked. If this box is ticked, the data collection is
stopped.
5) In the Mode area for 1640WM:

– Tick the Existing box.
– Tick the Create History Data box to allow history data collection.
6) In the Mode area for 1696MS:

– Tick the Create History Data box to allow history data collection.
– Leave the Lock Data Collection box unticked. If this box is ticked, the data collection is
stopped.
7) In the Set Alarm Severity UAT area:

– Click on button Set ASAP to open the ASAPs Management window and choose in the list
the desired ASAP (All Alarms, No Remote Alarms, Primary Alarms, No Alarms). Click on
OK to validate the choice.
8) Click on Apply.
1AA 00014 0004 (9007) A4 – ALICE 04.10
This starts the performance monitoring. A ’P’ indicator appears under the trail monitoring icon.
3AL 89062 AA AA 650 / 926
926
Trail monitor icon
Performance activity
indicator
9) To attach a threshold table (optional):
a) Click on Attach:
The identification number of the table is displayed in the Threshold Table text field.
10 ) Repeat the actions of steps 3 ) to 9 ) of this procedure to start and configure the performance
monitoring on the other counters.
11 ) Click on Close to terminate.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 651 / 926
926
Start performance monitoring on FEC:
1) Display the port view of the corresponding WLA (R_FEC) board.

2) Select the OCHA icon block.

4) Select the tab corresponding to the counters you want to configure;

– NE 15m to set the performance activity of the 15 minutes counters,
– NE 24h to set the performance activity of the 24 hours counters.
N.B. It allows you to configure the two types of counters independently. By default the
NE 15m page is displayed first.
5) In the Mode area:

– Tick the Create Current Data box to allow history data collection.
6) Click on Apply. This starts the performance monitoring. A ’P’ indicator appears under the
OCHA icon.
Performance activity
indicator
7) To attach a threshold table (optional):
a) Click on Attach:
The identification number of the table is displayed in the Threshold Table text field.
8) Repeat the actions of steps 3 ) to 9 ) of this procedure to start and configure the performance
monitoring on the other counters.
Stop performance monitoring of a TP
1) Select the trail monitoring icon.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3) Select the tab corresponding to the counters you want to cancel:

– NE 15m to cancel the performance activity of the 15 minutes counters,
3AL 89062 AA AA 652 / 926
926
– NE 24h to cancel the performance activity of the 24 hours counters.
4) In the Mode area, untick the options previously selected

5) Click on Apply.
This ends the performance monitoring. The ’P’ indicator disappears under the trail monitoring
icon.
Delete trail monitoring function on a TP
1) Display the port view of the corresponding board.
2) Select the TP.
3) Choose the Port–Trail Monitor–Delete menu option:

the trail monitor icon beside the selected port disappears.
N.B. Before deleting a trail monitor icon block, the user has to check that PM measurement are
not started, otherwise the PM are stopped and the measurement are not significant.
Consult the current performance data (B1 or FEC)
1) Display the port view of the corresponding WLA board.
2) Select the TP icon block (OGPI for B1, OCHA for FEC).
3) Choose the Port–Performance–Display Current Data menu option:

The PM Current Data dialog box is displayed. it contains two tabs, one to access to the 15 min-
utes counter current data and the other to access to the 24 hours counters current data. For
each counter type, the following data are displayed:
– Administrative State:
Indicates whether the PM data collection is ’locked’ or ’unlocked’ for the local.
– Operational State:
Indicates whether PM is enabled or disabled.
– Suspect Data:
Indicates if during the current period, a data collection problem occurred (’Yes’ or ’No’).
– Threshold Table:
Indicates which threshold table is assigned to the entity.
– Current Problem List:

Indicates if counter value thresholds have been crossed during the current period.
– Elapsed Time:
Indicates the time which has elapsed since the monitoring interval was started. This infor-
mation tells the user whether the data collection covers the whole period.
– The current value of each counter:BBE, ES and SES for B1 counters data and SCS and
BEC for FEC counters data
4) To start a new counting period click on Reset.

1AA 00014 0004 (9007) A4 – ALICE 04.10
5) To bring up to date the counter values click on Refresh.
6) To print the date click on Print.
3AL 89062 AA AA 653 / 926
926
N.B. When the printer is not installed, the system does not generate a corresponding error
message.
Consult the performance history data

1) Display the port view of the corresponding WLA board.
2) Select the TP icon block (OGPI for B1, OCHA for FEC).
3) Choose the Port–Performance–Display History Data menu option:

The PM History Data dialog box is displayed. it contains two tabs, one to access to the history
data of the 15 minutes counters and the other to access to the history data of the 24 hours count-
er. For each counter type, the following data are displayed:
– Interval End Time: in the format dd.mm.yyyy hh:mm:ss.

– Elapsed Time: indicating whether the data collection was complete
– Susp: indicating suspect data where collection errors occurred during the collection peri-
od. Indicating also if the collection period is not full.
4) To bring up the date of the counter values click on Refresh.
5) To print the date click on Print.
N.B. When the printer is not installed, the system does not generate a corresponding error
message.
N.B. From the PM View application available on the SH, the data History (stored in a database) can
be displayed on a table or on a graphic form according to the type of counters.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 654 / 926
926
16.8 Show Performance Data
16.8.1 Performance monitoring visualization (PMV)

The performance counters visualization can be opened from the Network Topology views and from the
Equipment views.
a) Visualization from the Network Topology views (PNM)
To display the performance data of an NE which TPs are currently being involved in performance
measurement, select the NE from the current submap and select the Diagnose pull down menu. You
can then select the 15 minutes or 24 Hours or User Selection option from the Show Performance
Data cascading menu, in order to display performance data of 15 minutes or 24 hours counting window
or the generic User Selection.
Figure 403. Displaying performance data from a Network Topology view.
b) Visualization from the Equipment views (USM)
To display the performance data of an NE which TPs are currently being involved in performance
measurement, select the Diagnosis pull down menu. You can then select the 15 minutes or 24 Hours
option from the Show Performance Data cascading menu, in order to display performance data of 15
minutes or 24 hours counting window.
Figure 404. Displaying performance data from an Equipment view.

1AA 00014 0004 (9007) A4 – ALICE 04.10
The Performance Data options are described in SC.1.6 Performance Monitoring Visualization Manual
(PMV).
3AL 89062 AA AA 655 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
656 / 926
17 SYNCHRONIZATION MANAGEMENT
17.1 Introduction
All SDH NEs require timing in order to generate the necessary synchronization and frame phase reference
information. The timing can be provided by a source external to the NE or an internal timing generator.
The derived timing shall be used for all signals and interfaces in the NE that are related to the SDH frame
structure.
Herebelow is a brief description of the heart of the NE clock known as the Synchronization Equipment
Timing Source (SETS).
It can be divided into 2 parts:
– OSC: the internal oscillator.

– SETG: the Synchronization Equipment Timing Generator.
The SETG is responsible for the generation of the external timing source for the Frame structure and the
clock, whilst the internal oscillator is useful only in the abnormal functioning ”Free–running” mode that will
be explained later.
The simplified figure that follows represents the internal organization of the SETS.
Squelch Selector
Selector A T4/T5
C
A
T0_TEST
Squelch
B
T1
T2 Selector
SETG T0
T3/T6 B
OSC
SETS
S15 Y
Figure 405. SETS Internal organization. Dashed lines are for W/OMSN NEs
The internal sources (inputs) are:
– T1: Reference obtained from incoming STM–N signals,

– T2: Reference obtained from incoming 2 Mbits signals,
– T3/T6: Reference obtained from an external incoming 2.048 MHz (T3) or 2.048 Mbit/s (T6) signal.
– OSC: the internal oscillator.
The number of timing reference inputs depends on the NE configuration.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 657 / 926
926
The external sources (outputs) are:
– T0: is the reference timing for the clock and signal frames,
– T4: is the output timing reference for the external equipment synchronization.

– T5: is the 2 Mbit/s reference output for the external equipment synchronization.

– T0_TEST: is output timing reference for checking the internal signal T0 (only available for OMSG)
Other reference points:
– Y: is used for communication of Synchronization Status Message (SSM) between SETS and MST
functional blocks.
– S15: is used to provide notifications and loss of incoming timing reference reporting to the
Synchronous Equipment Management Function (SEMF).
Selector A provides the capability to select the timing reference from available T1 or T2 inputs, either
automatically based on the priority and quality level of the candidate sources (SSM algorithm), or manual
as a result of commands issued from the managing system.
Selector B is capable of selecting the timing reference from T1, T2, or T3/T6 inputs, according to the SSM
algorithm. The capability for manual selection of the timing source is also provided.
Selector C is only operated in manual mode, to switch between SETG output signal (T0) and a T1 timing
reference.
The squelch functions A and B mute the relevant timing references in the presence of failure condition,
or SSM threshold violation.
Two modes can be used for the timing reference selection:

– Automatically:
Following a particular algorithm based on the quality and the priority of the incoming timing signals.
The automatic selection is based either on the priority of the incoming timing source (Priority
algorithm) or on the priority and the quality level of the incoming sources (SSM algorithm).
– Manually:
Following an order from the OS.
N.B. The priority level is determined by the OS for each candidate timing source. It is static
information. On the other hand, the quality of the source is dynamic information, dependant
of the quality of the reference clock generating the timing.
In an SDH signal frame, the quality of the timing source is located in the Overhead Section .
The SETG has three operation modes:
– Locked mode:
The SETG output is fully controlled by the external timing references (T1, T2 and T3/T6).
– Hold–Over mode:
The external timing reference is malfunctioning. The SETG during normal functioning stores
regularly the value of the external timing reference. In this case the SETG output is controlled by this
memorized value.
– Free running mode:
This is not a normal operating mode. The external timing reference and the memorized timing
reference are malfunctioning. In this case the SETG output is controlled by the internal clock source.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 658 / 926
926
17.1.1 Displaying the Synchronization View
The synchronization view can be normally opened using the menu Views options (see Figure 406. ). Using
the menu options, select the Synchronization option from the Views pull down menu as shown in the
following figure.
Figure 406. Obtaining the synchronization view.
All the operations that can be performed on the timing sources are initiated from this view.
N.B. The modification of ASAPs is generally not possible in Sync View. To change the ASAPs of
synchronisation ports perform the following procedure:
– Select the port in Sync View.
– Click Show timing source from the Synchronization menu to display the port in port view.
– Change the ASAP in port view (select Configuration and then Set Alarm Severitys).
2MHz timing sources do not support the ASAP feature in the current SH release.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 659 / 926
926
17.1.2 Synchronization View
The Synchronization view shows the external timing reference sources and the T0, T4 or T5 generation.
The selection is based on the SSM algorithm or on the priority of the incoming timing sources. Activating

the SSM algorithm implies that the selection of the source is before done on the quality criteria and then

on the priority criteria for sources at the same quality level.
After selecting the Synchronization from the Views menu the Synchronization View is visualized in
Figure 407.
Selector B
T2 T1 T3 T3 OSC Squelch B
T6 T6
for 1641 SX and

1664 SX only)
or T5
T1 T2 Squelch A
Selector A
Figure 407. Example of the Synchronization View (on OMSG)
N.B. The Synchronization sources numbering depends on the related NE (The numbering of the
synchronization sources is 5 for 1674LG R.1.1, while the numbering is 6 for 1664SM R.3.2 )
1AA 00014 0004 (9007) A4 – ALICE 04.10
In case of alarm indication the operator can select Show Timing Source ( Figure 434. on page 694) to
visualize the alarm detail.
3AL 89062 AA AA 660 / 926
926
Synchronization View Description
The synchronization view provides two list of allowable timing references:

• one for T0 timing output; T0 list is always present;

• one for T4 or T5 timing output; the presence of the T4/T5 list is configurable using resource files.
T0 list contains :
– a timing reference associated to the Internal Oscillator timing source; it is always present
and it cannot be removed or redefined.
– 6 max. timing reference for candidate inputs belonging to the allowable timing reference
T1, T2 or T3/T6 configurable by the operator.
T4/T5 list contains :
– 6 max. timing reference for candidate inputs belonging to the allowable timing reference
T1 configurable by the operator.
The T0 and T4/T5 lists are used for the management of reference timing source protection; a 1:n protection
like mechanism is used for the selection of the timing source from T0 (T4/T5) list of the allowable timing
references, . The protection system chooses the timing reference to generate the output T0 (T4/T5) either
automatically, basing on the priority and quality level of the candidate sources according a selection
algorithm or manually under control of the managing system.
View elements description
Here in after, the basic component contained in the synchronization view are described:
– Timing source
Each allowable timing source, with the exception of the Internal Oscillator timing reference, is
represented by the graphical object displayed in Figure 408. ; the timing reference graphical object
displays the following information:
If the timing source has been declared by the user:
SETG or the name of the selected timing source, including its physical location (e.g.
rack-subrack-board-port )
The protection state of the timing source:
• Label Failure / Fail, if the source has a failure condition
• Label Automatic, if an automatic switch to this source has been completed
• Label Force, if a forced switch to this source has been completed
• Label Manual, if a manual switch to this source has been completed
• Label Lockout, if the timing source is locked out.
• No request / No label, if the timing source is not selected and has no failure condition
1AA 00014 0004 (9007) A4 – ALICE 04.10
The label of the quality level of the timing source: PRC (G.811), SSUA (G.812T), SSUB
(G812L), SEC (G.813), DNU (Don’t use) or Extracted.
the priority of the timing input source: 1 ... 6
3AL 89062 AA AA 661 / 926
926
On OMSG , an additional external reference clock T3 (T3add) if configured.
% ! % & '
9.8I" C J( 5"

9.8I# C J( 9#

For any reference source there are also two alarm indications:
DRIFT means that the Frequency Offset between the external signal source and the internal clock is higher
than the maximum tolerance value (typical value: 10 ppm.).
SSF means that the Server Signal Failure is sending a wrong reference signal to the NE.
In case of alarm indication the operator can select Show Timing Source ( Figure 434. ) to visualize the
alarm detail.
Figure 408. Example of Timing reference graphical object
The following information is associated to the Int. Oscillator / T0 ( Figure 409. ) and a general timing
generator name:
• the LOS/LOTS small box representing the alarm Holdover/Free Running; this box will be lighted
up when all the selected timing source are lost, indicating the Holdover or Free Running
operation mode;
• a label field representing the abnormal clock operation modes; one of the following strings can
be displayed in the label field:
– Label free running if the system operates with nominal frequency.
– Label holdover if the timing generator is selected and the clock system was before
tracking to an external valid clock source .
– Label empty, locked, tracking if the clock system selects an external clock source and
is running probably on that reference clock.
Acquisition status displayed only on OMSG
N.B. To ensure that the clock system is really driven by an valid external reference
clock this clock should be selected at least for 30 minutes. During this time the
clock system is in the Acquisition status. If the external clock is lost in a shorter
time it may happen that the clock system won’t fall into holdover mode, but in
free running mode.
1AA 00014 0004 (9007) A4 – ALICE 04.10
the listed strings are:

• a label empty or ”G.813...” label depends on SEC/SSU version representing the fixed quality
of the Internal Oscillator. The quality level can be also expressed with: PRC, SSUA, SSUB,
SEC, DNU.
3AL 89062 AA AA 662 / 926
926
• a label ”0” representing the Internal Oscillator priority.
Figure 409. Example of the Internal Oscillator graphical object
– Selectors
small ellipse Figure 410. are used to represent respectively:
• the selector A, B
• the selector C (only for W/OMSN)
– The SSM mode (only for OMSG): Enabled or Disabled
Squelch Status
a label field contained in a box is used to represent the squelch statuses T1/T4, T0 and T0_TEST
(only for OMSG). The box displays the configured quality level threshold and it is lighted up when the
output timing signal is inhibited.
Figure 410. Symbol used to represent a Squelch Status T1/T4 and the Selector C
The squelch function can be applied to different sources (T1 or T2). Then the T4 Configuration
command can squelch the T4 as well the T5 output signal.
The background color of this block is “green” if it’s output is enabled. The color changes to “red” if
the squelch block output is disabled (squelched).
The squelch block, on OMSG, provides also the Automatic or Forced information
– Output Signal
an arrow and a label field (Figure 411. ) are used to represent respectively:
• the output signal T0;
• the output signal T4/T5;
• the output signal T0_TEST for Cross–Connect equipment.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 663 / 926
926
T0

Figure 411. Symbol used to represent a Output Signal
– Line Type
the following different line types are used to link the output signals and the respective allowable
timing source:
• A solid line between an output signal and an allowable timing source means that the timing
source is currently used to generate that signal;
• A dashed line between an output signal and an allowable timing source means that the timing
source is not currently used as a timing source but will act as protection.
In the same way, a solid line between the T0 signal and T4/T5 signals (or T0_Test signal) box is
drawn when T0 signal is used to generate T4/T5.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 664 / 926
926
17.2 Synchronization commands
The operations that can be done on the synchronization sources are the following:
– Timing Source Configuration,

– Create Timing Source (only available for OMSG USM 8.x)
– Protection Commands,
– Synchronization configuration for T0 / T4 and T4 squelch criteria,
– Output configuration (only available for OMSG USM 8.x)
– SSU Configuration (only applicable to W/OMSN),
– Remove Timing Reference / Remove Timing Source,
– Set and remove T0 Equal T4 (only available for W/OMSN),
– Connect / Disconnect T0–>T4 (only available for OMSG),
– Change T4<–> T5,
– Change 2 MHz –> 2 Mbit (only available for W/OMSN)
– Frame Mode Configuration (only available for W/OMSN),
– T0 TEST Configuration (only applicable to OMSG),
– Transmission of SSM Quality Configuration,
– Show Timing Source.
Before any other operation the synchronization view has to be displayed.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 665 / 926
926
17.2.1 Timing Source Configuration
This functionality allows to configure the input synchronization sources and configure or modify the timing
source priority and quality.

N.B. Only for OMSG
If a Timing Reference object in the Synchronization view is empty, no reference clock is
configured in the database “physdb”. In this case do not use the Timing Source Configuration
dialog for configuration, because the timing reference is not available for the system at all.
Figure 412. Synchronization Menu
The menu options are greyed according to the current state of the dialogue box that can be opened by the
the user.
Firstly select the timing source, open the Synchronization menu ( Figure 412. ) and then the Timing Source
Configuration option from the cascading menu to open Figure 413.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 666 / 926
926
Figure 413. Example of synch. source configuration
The Timing source configuration dialogue box displays the extracted quality of the selected timing source.
It permits to configure the following timing source information:
– Quality level,
– Priority level
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 667 / 926
926
In the W/OMSN select an empty synch. source and click on Timing Source Configuration and then on the
Input Source Choose. Figure 414. shows the opened windows. Following the TP Search procedure
described in the “Transmission View” chapter enter the physical (SPI/PPI) board termination point (TP)
value ( rack, subrack, board, port ) these TP are : EIS for electrical SDH port, OpS for optical SDH port..

This operation can be repeated for all the available empty synch. sources both for T0 clock and for T4

clock.
Figure 414. Example of synch. source configuration for 1664SM equipment
Click on Input Quality Configuration to open the option menu in which to select the desired quality level.
1AA 00014 0004 (9007) A4 – ALICE 04.10
The timing source may have, in decreasing order, the following quality levels (where the highest quality
level to be selected is G.811/PRC).
3AL 89062 AA AA 668 / 926
926
SSM Code W/OMSN and 1641/1664SX 1674 Lambda Gate
0010 G.811 PRC

0100 G.812T SSU–A

1000 G.812L SSU–B
1011 G.813 SEC
1111 Do not use DNU
The notation on 1674 Lambda Gate is compliant to ITU-T G.781.
N.B. The OMSG does not accept assignment of G.813 to a timing source. Although the quality G.813
can be selected on the CT, this selection will be rejected by the system.
Quality “Extracted” refers to the actual quality retrieved from the line.
If the SSM quality is set to a value other than “Extracted”, the quality is forced to this value.
The effective quality (received SSM or forced quality) is displayed in the timing source icon.
If a non defined SSM code is received, it is displayed on OMSG as “INV n” with n being a number
equivalent to the received code value.
Click on the Priority: the option button opens the option menu to select the desired priority level.
The internal oscillator timing source will have the lowest priority (priority=0) and its priority can not be
changed. Priority 1 is the highest priority. Levels 6,...2 are intermediate levels between level 0 and 1, in
increasing order of priority (i.e. 0 6 5 4 3 2 1).
When the configuration of the timing source is completed, click on the OK push button to validate the
choice and close the dialogue box. The Cancel push button cancels the configuration and closes the
dialogue box.
The corresponding physical interface definition (rack–subrack–board–port) is directly written on the

configured synch. source box or by positioning the mouse on the source box the “Port#” name is displayed
on the window bottom left.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 669 / 926
926
17.2.2 Create Timing Source (only available for OMSG – USM 8.x)
This functionality is used to create and configure a new timing source.

Synchronization

Create Timing Source
Protection Commands
T0 Configuration
SSU Configuration
Change Output T4 –> T5
Connect T0 –> T4
Proceed as follows:
1) Select an empty block,
2) Open the Synchronization menu,
3) Select Create Timing Source from the cascading menu, as shown in the figure above. It appears
the Timing Source Configuration dialog (see Figure 415. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 670 / 926
926
Figure 415. Timing Source Configuration Dialog (Example)
The Timing Source Configuration enables the following timing source parameter to be configured:
– Type of timing source:
• Internal timing source,
• External timing source,
– Quality level,
– Priority level,
Creating an Internal Timing Source
To create an internal timing source (T1) perform the following steps:
1) Click Choose Int. The TP-Search dialog is displayed (see Figure 341. ).
2) Set the filter criteria to OPS and continue with Search.
3) Select one TP listed in the right box and close the TP-Search dialog with OK. The user label of the
chosen TP is now displayed in the timing source creation dialog.
4) If necessary configure the quality level and priority level.

1AA 00014 0004 (9007) A4 – ALICE 04.10
5) Confirm the settings with OK. The dialog is closed and the timing source is displayed with the
selected priority and quality. The Cancel button discards the entries and closes the dialog box.
3AL 89062 AA AA 671 / 926
926
Creating an External Timing Source
To create an external timing source (T3, T6) perform the following steps:

6) Click Choose Ext. The Choose External Timing Source dialog appears (see Figure 416. ).

All external timing references are listed in the Input Source field.
Figure 416. Choose External Timing Source Dialog (Example)
7) Select the corresponding timing source and close the dialog with OK. The label of the selected
timing source is displayed in the timing source creation dialog.
8) If necessary configure the quality level and priority level.
9) Confirm the settings by with OK. The dialog is closed and the timing source is displayed with
the selected priority and quality. The Cancel button discards the entries and closes the dialog
box.
Quality
Click on Input Quality Configuration to open the option menu in which to select the desired quality level.
The timing source may have, in decreasing order, the following quality levels (where the highest quality
level to be selected is G.811/PRC):
* # (;/$ # <

<<5<
C
<5<< *"
5<<< *#
5<55 %
5555 >
With 1674 LG the notation compliant to ITU-T G.781 is introduced.

1AA 00014 0004 (9007) A4 – ALICE 04.10
The quality “Extracted” refers to the actual quality retrieved from the line. If the SSM quality is set to a value
other than “Extracted”, the quality is forced to this value.
3AL 89062 AA AA 672 / 926
926
The effective quality (received SSM or forced quality) is displayed in the timing source icon. If a non defined
SSM code is received, it is displayed as “INV n” with n being a number equivalent to the received code
value.
Priority
Click Priority to open the option menu in which to select the desired priority level.
The internal oscillator timing source has the lowest priority (priority=0) and its priority cannot be changed.
1 is the highest priority. Other levels are levels between level 6 and 1, in increasing order of priority (i.e.
6, 5, 4, 3, 2, 1).
When the configuration of the timing source is completed, click OK to validate the choice and close the
dialog box. The Cancel button cancels the configuration and closes the dialog box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 673 / 926
926
17.2.3 Synchronization Protection Commands
Select the timing reference from the synchronization view. As in Figure 412. , select the Synchronization
pull down menu and then select the Protection Commands to open Figure 417. Menu options are greyed

according to the current state of the selected timing source.

Figure 417. Lockout, Force and Manual commands
a) Invoke/Release –Lockout: Locking or unlocking a timing source enables or disables the timing
source from being considered as a possible timing source for T0 or T4.
b) Invoke/Release –Force and Manual Selection of Timing Source
General selection
A timing source can be selected manually or automatically. Furthermore, the selection of a particular in-
coming timing source (except the internal oscillator) may be forced.
This selection is not related to the priority or quality of the timing source. If the timing source is lockout or
unavailable, this operation is impossible. A timing source is considered to be available if it is not lockout
and has not a failure condition or Priority level of 0 (internal clock) .
The forced switch mode is terminated by releasing the force switch or by invoking Lockout for that timing
source.
The manual selection option is only possible if the quality and priority of the selected timing source are
sufficient. Otherwise the automatic selection algorithm overrules the manual selection. If the previously
manual selected timing source becomes unavailable, the automatic selection is activated.
The “Status” indication describes the current synch. status (No Request, Automatic Switch, Failure, ...)
N.B. The internal oscillator cannot be forced or manually selected
From the dialogue box that opens, you can confirm or cancel the operation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 674 / 926
926
To perform or release a T0 or T4/T5 lockout, forced or manual selection, the following operations have
to be done:
– Select the T0 or T4/T5 source.

– Click on the Synchronization menu.
– Select the Protection Commands option, then invoke/Release, the Lockout, Forced or manual
Selection option.
– Click on Apply in the displayed confirmation box .
17.2.4 Synchronization Protection Commands for OMSG – USM 7.x
General
The implementation of the synchronization protection commands as inherited from previous releases is
not compliant to the requirements of the relevant standards.
Therefore, the functionality of manual and forced switch shall be emulated by using the allocation of the
quality level “Don’t use” / “DNU” to some of the timing sources. This method is described below.
For maintenance purposes (especially during upgrade from the previous release) the synchronization
protection commands are also available in the ”Administrator” Guide Manual.
The same emulation method can be applied to 1641SX R.6.3–1 / 1664SX R.2.3–1 and 1674LG R.1.0
and in general to all OMSG NE family with USM 7.x
Emulation of Synchronization Protection Commands
The functionality of the synchronization protection commands must be emulated as follows:
– Invoke lockout
Allocate the quality level “Don’t use” / “DNU” to the timing source. This works in both SSM enabled
and SSM disabled mode.
– Release lockout
Allocate the previous quality level again.
– Invoke forced switch
Allocate the quality level “Don’t use” / “DNU” to all timing sources other than the one which should
be forced. This works in both SSM enabled and SSM disabled mode.
– Release forced switch
Allocate the previous quality level configuration to all timing sources again.
– Invoke manual switch
Set the priority of the timing source which is to be manually selected to the highest value. If this does
not cause a switch, because the currently selected timing source has also highest priority, then tem-
porarily set the priority of the selected source to a lower value.
– Release manual switch
Set the priority of the manually selected timing source back to its previous value.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 675 / 926
926
17.2.5 Synchronization Protection Commands for OMSG – USM 8.x
There are two different Synchronization Protection Commands dialogs. If a timing source block was selec-
ted the dialog as shown in Figure 417. appears. If the internal oscillator was selected the dialog as shown

in Figure 418. appears.

Figure 418. Protection Commands Dialog – Internal Oscillator
Synchronization Protection Commands
The synchronization protection commands are defined as follows:
– Manual switch: The manual command allows to invoke the manual selection of the timing sources.
This operation is possible only if the quality and priority of the selected timing source are sufficient.
If this is not the case then the automatic selection overrules the manual selection. If the selected tim-
ing source is locked, forced or unavailable, the manual operation is not possible. The internal oscilla-
tor cannot be “manual” selected.
– Forced switch: The force command allows to invoke the force selection of the timing source. This
operation is independent on the priority or quality of the timing source. If the timing source is locked
or not available, this operation is not possible. The forced switch mode can be terminated by inhabit-
ing (locking out) the force selected timing source.
The protection force switch for the internal oscillator is extented with the holdover and freerunning
mode (see Figure 418. ). It is only available for CLOS-Matrix configuration.
– Lockout: The lockout command allows to disable the timing source from being considered as pos-
sible source of timing for T0 or T4/T5. The invoke (release) lockout button is greyed according to the
current state of the selected timing source. The internal oscillator cannot be “lockout” selected.
– Release: The release command releases a lockout, manual or forced switch.
– Status: The status indication shows the current protection state (No Request, Automatic Switch,
Failure, ...).
Use OK to confirm the selection and to close the dialog.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Use Apply to confirm the selection. The dialog box remains open.
Use Cancel to discard any entries and to close the dialog.
3AL 89062 AA AA 676 / 926
926
17.2.6 Synchronization Configuration for T0/T4 and T4 squelch criteria
Select the T0 or T4 Configuration command from the Synchronization menu to open the related T0 or
T4 Configuration dialog (see Figure 419. and Figure 420. ) which permits to select/deselect the SSM
algorithm , to enable the revertive procedure, to set the wait time to restore and to configure the squelch
criteria for T4 timing source, when these features are available .
SSM Enable / Disable Algorithm
Click on the SSM Algorithm Enabling button to enable/disable SSM algorithm.
N.B. OMSG works always in the SSM enabled mode. If necessary, SSM disabled mode must be
emulated.
– Enabled
The reference clock is selected with respect to the quality level of the incoming sources as first
selection criteria. If there are several timing sources of equally high quality, the priority determines
the selection.
– Disabled
The reference clock is selected with respect to priority. However, inputs of quality level “Don’t use” /
“DNU” are not selected.
N.B. ETSI standard EN 300 417-6 requires that each network element works in a single SSM
algorithm mode. This is implemented by jointly handling the SSM algorithm mode for the T0 and
T4 selectors although the SH offers a separate configuration facility. If the mode is set for one
of the two timing sources, the value is forwarded to the other. The last change of either of the
two determines the valid state.
Emulation of SSM disabled mode (on OMSG with USM 7.x)

(i.e. : for 1674LG R.1.0)
Allocate equal SSM quality different to “DNU” to all timing sources (refer to section “Timing Source
Configuration”). This causes the selection to be done on priority only. However, the STM-n outputs still
send the actual SSM quality level. If it is required to send “DNU” this must be configured for all STM-n ports
(refer to section “Transmission of SSM Quality Configuration”).
Wait To Restore
Click on the Wait To Restore Time button to set the required time.
The WTR default is set to 300 s. WTR may be modified in the range of 0–3600 s in steps of 60 seconds.
(i.e. :WTR=0 for 1674 Lambda Gate R.1.0). For more details on WTR, see the proper NE CT docs.
In Revertive mode the internal A/B selector (Figure 405. ) changes every time to the best reference clock
with the highest quality; on the same quality level basis the reference clock Source with the best priority
will be selected. The changing mechanism of the reference inputs is controlled by the wait time to restore:
this time sets a delay before changing the input source. In non revertive operational mode the A/B selector
can select a previous correct reference clock only when all the input reference sources are passed in a
failure condition.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 677 / 926
926
Figure 419. T0 Configuration dialog box on OMSG USM 8.x
Squelch Criteria
Selecting T4 Configuration, it is possible to set the T4 squelch criteria (see the bottom of the dialog in
Figure 420. ).
This functionality enables the external timing source (T4) squelch criteria to be configured. The squelch
function mutes the relevant timing source if the received quality level of the selected timing source T1 or
T2 is lower than the squelch criteria or if the selected timing source becomes unavailable.
Squelch may be forced by the OS or according to the squelch criteria which consists in a choice of quality
level.
Different squelch criteria may be applied:
• when T0 is selected to generate T4 (squelch B Figure 405. ): T0 may be squelched if all the
allowable timing references of Selector B have Quality Level lower than the programmable
threshold.
• when T1/T2 is selected to generate T4 (squelch A Figure 405. ) :T1/T2 may be squelched if
T1/T2 Quality Level is lower than the programmable threshold or if it becomes unavailable.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 678 / 926
926
Figure 420. Configuring the T4 SSM algorithm and the squelch criteria
Click on the T0: option button to open the option menu and select the desired quality level.
Click on the T4: option button to open the option menu and select the desired quality level.
The Force Squelch option button enables you to suppress the T4 output regardless the signal quality
configuration.
When the configuration of T0/T4 Configuration is completed, click on the OK push button to validate the
choice and close the dialogue box.
The Cancel push button cancels the configuration and closes the dialogue box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 679 / 926
926
17.2.7 Output Configuration (only available for OMSG – USM 8.x)
This functionality is used to set the synchronization output configuration.

Synchronization

Create Timing Source
Protection Commands
T0 Configuration
SSU Configuration
Change Output T4 –> T5
Connect T0 –> T4
Proceed as follows:
1) Open the Synchronization menu,
2) Select Output Configuration from the cascading menu, as shown in the figure above. It appears
the Synchronization Output Configuration dialog (see Figure 421. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 680 / 926
926
Figure 421. Output Configuration (Example)
SSM Algorithm
Click on the SSM Algorithm Enabling button to enable/disable SSM algorithm.

– Enabled: The reference clock is selected with respect to the quality level of the incoming sources
as first selection criteria. If there are several timing sources of the same high quality, the priority deter-
mines the selection.
– Disabled: The reference clock is selected only with respect to priority.
Wait To Restore Time
The internal selector A/B (Figure 405. ) always selects the reference clock with the highest quality. On the
same quality level basis the reference clock with the highest priority is selected.
The changing mechanism of the reference inputs is controlled by the Wait To Restore time.
If the previously failed reference clock is restored, it can be selected as timing source if the evaluated signal
is continuously available at least for the period of the Wait To Restore time.
This functionality is only supported by a Clos Matrix configuration.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 681 / 926
926
Squelch Criteria
The squelch function mutes the relevant timing sources in case of a failure condition.

The squelch can be forced either by the managing system or according squelch criteria via choosing the

quality level.
Force: Enable force squelch to suppress the output of the relevant timing source.
Threshold: Set the threshold to define the quality level. The following selections are available:
– PRC
– SSUA
– SSUB
– SEC
– Don’t use.
T5 Output
sa_SSM-Bit: This button is used to select the position of the Sa_SSM-Bit (4...8).
supress SSM: Insert SSM into T5 signal by enabling SSM or insert DNU by supressing SSM.
This button is currently not used.
N.B. To set the sa_SSM-Bit, the T5 Output must be activated. Otherwise the parameter is not avail-
able.
Use OK to confirm all entries and to close the dialog.
Use Cancel to discard any entries and to close the dialog.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 682 / 926
926
17.2.8 SSU Configuration (only applicable to W/OMSN)
The SSU configuration command allows either to configure the single NE or the NE with SSU. In the last
case the SSU quality has to be defined. Selecting SSU Configuration from the Synchronization menu is
presented Figure 422.

Figure 422. SSU Configuration

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 683 / 926
926
17.2.9 Remove Timing Reference / Remove Timing Source
This feature is available for W/OMSN and for OMSG with USM 8.x .

Select the synch. source to remove and click on the Remove Timing Reference option. To remove the

selected source click on “OK” button of the confirmation message
Figure 423. Synchronization source removing on W/OMSN

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 684 / 926
926
17.2.10 Set and Remove T0 Equal T4 (only available for W/OMSN)
To connect T0 internal synch. select a synch. source and click on “Set T0 Equal T4” menu option. The
connection between T0/T4 will pass from a shaped to a continue line as in the example of Figure 424.
Figure 424. T4 equal T0 setting
To separate T4 from T0 click on the “Remove T0 Equal T4” menu option. The T0/T4 connection will
become shaped while the connection between T1/T4 will pass from a shaped to a continue line.
17.2.11 Connect / Disconnect T0–>T4 (only available for OMSG)

1AA 00014 0004 (9007) A4 – ALICE 04.10
The same feature of previous para. 17.2.10 is available for OMSG USM 8.x with the Connect T0–>T4
or Disconnect T0–>T4 option.
3AL 89062 AA AA 685 / 926
926
17.2.12 Change T4 <–> T5
This option is available on W/OMSN USM 5.x, 6.x and OMSG USM 8.x.

This menu allows the change of the synchronization physical interface from 2Mhz (T4 ) to 2 Mbit/s (T5)

and viceversa.
This menu is enable only if the SERGI (1650SMC)/ SERVICE (1660SM) board is present in the subrack.
Select Change T4 <–> T5 from the Synchronization menu as shown in Figure 422.
Figure 425. Change T4 <–> T5 menu
A confirmation message appears (see Figure 426. on page 686)

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 426. Change T4 <–> T5 confirmation message
3AL 89062 AA AA 686 / 926
926
Click on ok to confirm; the new window display T4 instead of T5 (see Figure 427. on page 687)
Figure 427. Change T4 <–> T5: command execution

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 687 / 926
926
17.2.13 Change 2MHz –>2Mbit (only available for W/OMSN USM 5.x, 6.x)
This menu is enabled only if the operator selects a protection unit which have as source a 2 MHz or a 2
Mbit/s without traffic: that is a T3 timing source.

Select Change 2MHz –>2Mbit from the Synchronization menu as shown in Figure 428.
Figure 428. Change 2MHz –>2Mbit menu
A confirmation message appears (see Figure 429. on page 688)
Figure 429. Change 2MHz –>2Mbit confirmation message

1AA 00014 0004 (9007) A4 – ALICE 04.10
Click on ok to confirm;
3AL 89062 AA AA 688 / 926
926
The label of the protection unit will be changed depending on the kind of source selected (see Figure 430.
on page 689):
• If the selected protection unit is a 2 MHz, then the label will be changed into 2Mbit/s (port#01–P
in the example of Figure 430. )

• If the selected protection unit is a 2 Mbit/s, then the label will be changed into 2MHz
Figure 430. Change 2MHz –>2Mbit: command execution

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 689 / 926
926
17.2.14 Frame Mode Configuration (only available for W/OMSN)
Select the T2 PDH Reference Source in the Synchronization View ( Figure 407. ) hence the Frame Mode
Configuration is enabled. This selection allows to check the 2 Mbit/s input source before considering it as

a valid reference.

Click on Frame Mode Configuration of the Synchronization menu option. Figure 431. opens.
Figure 431. Frame Mode Configuration
The same frame mode configuration window can be also opened from any PDH board. Select the
Equipment Configuration then Port, PDH TP Configuration. The CRC4 option will be available only for the
2Mbit/s ports.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 690 / 926
926
17.2.15 T0 Test Configuration (only applicable to OMSG)
Synchronization
Timing Source Configuration

Protection Commands
T0 Configuration
T4 Configuration
SSU Configuration
Set T0 Equal T4
Show Timing Source
Select the T0_TEST Configuration command from the Synchronization menu to open the T0_TEST
Configuration dialog (for 1641 SX and 1664 SX only).
The operator can test the clock synchronization signal T0 at the CIB (Clock Interface Board) T0_TEST
output. T0_TEST may be squelched if all the permissible timing sources of Selector B have a quality level
lower than the defined threshold.
Click on the option button to select the desired quality level.
Enable Force Squelch to suppress the output of the T0_test signal regardless the signal quality value.
Use OK to confirm all configuration entries and close the dialog.
Use Cancel to discard any entries and close the dialog.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 691 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 432. T0_TEST Configuration
926
3AL 89062 AA AA
692 / 926
17.2.16 Transmission of SSM Quality Configuration
Select the T1 SDH Reference Source in the Synchronization View (Figure 407. ) hence the
Transmission SSM Quality Configuration is enabled. This selection allows, with the Inserted option,
to transmit the system internal T0 clock quality towards the external SDH interface. It is also possible to
transmit different quality level selecting a different value.
Click on Transmitted SSM Quality Configuration of the Synchronization menu option.

Figure 433. opens.
Figure 433. Transmission SSM Quality box dialog example
SSM Quality
Use the option button to select the transmitted SSM quality:

– Select the option Don’t use if the transmitted STM-N signal should not be used as the timing source
at the far end destination.
– Select the option Inserted to transmit the system internal T0 clock quality with the transmitted STM-N
signal.
– Select a Quality Value to insert it in the STM–N transmission signal.
This Transmission SSM Quality window can be also opened from MSTTP of any STM–N ports. Open the
Port / Transmission view. Select the Physical Media –>SDH TxSsm Quality Configuration or –>TX
Quality Configuration (see the USM Menu Commands, chapter 2).
Use OK to confirm the SSU configuration or Cancel to discard any entries and close the dialog.
On OMSG USM 8.x the user can also select the following buttons:
The Apply button to confirm the SSU configuration entries and leave the dialog box opens.
The Tp list... button to open the Clipboard Dialog (see Chapter 3.8).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 693 / 926
926
17.2.17 Show Timing Source
Select any T1 or T2 Reference Source in the Synchronization View (Figure 407. ) hence the Show Timing
Source is enabled. This selection allows to analyze the input source considering its payload structure and

the related alarms.

Click on Show Timing Source of the Synchronization menu option. Figure 434. opens.
Figure 434. Timing Source Example

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 694 / 926
926
18 MS–SPRING MANAGEMENT FOR W/OMSN
18.1 MS–SPRING Management for ADM Equipments

MS–SPRING is applicable for 1661 SMC,1664 SM, 1660SM and 1670SM. Different MS–SPRING
protections are provided: 2–Fiber, 4–Fiber and NPE ( see ITU–T Rec. G.841 ). At the end of 2–Fiber and
NPE sections are reported the advices to follow before to implement the MS–SPRing protection: there
are some limitations concerning the aggregate types or the AU4s cross–connections to be considered.
In Figure 445. is reported a 2–Fiber/4–Fiber and NPE protection mechanism comparison.
18.1.1 2–Fiber MS–SPRING description
This protection is foreseen for the ring network topology of which it withstands single failures only in dual
ended switching modality (use K1–K2 byte with appropriate algorithm).
Its operation mode is revertive. The same description is applicable for N x 2–Fiber architecture where “N”
is for the possible number “N” of 2–Fiber optical links connected to the same NE. The same description
is applicable to every 2–Fiber links, then the number “N” in the following description is not mentioned
(N=1).
A 2F MS–SPRING consists of a set (from 2 to 16) of Network Elements each equipped with a double
bidirectional (Tx and Rx) aggregate port.
The NEs are connected in a ring by means of two optical fibers, one for the clockwise direction and the
other for the counter–clockwise one.
The MS SPRING protection is an alternative with respect to SNCP. While MS SPRING allows the
connection at the same time on the clockwise and on the counterclockwise direction on the same AU4
that can be inserted and extracted in each span, on the contrary the SNCP connection engages the same
AU4 on both sides for the whole link.
The bandwidth of a 2F MS–SPRING, applied to STM16, is divided into two halves of equal capacity called
respectively ”working” (AU4# 1 to AU4# 8) and ”protection” (AU4#9 to AU4# 16). The AU4# 1 is
protected by AU4#9 up to AU4#8 that is protected by the AU4#16. The ”working ” capacity is used to carry
the ”high priority traffic”, while the ”protection” capacity can be used for ”low priority” traffic that is lost in
case of failure (see Figure 435. )
In this description the ”low priority” connections are not mentioned.
The MS SPRING algorithm starts as a consequence of the following Section alarms:
• LOS, LOF, MS AIS, EXBER (B2), SIGNAL DEGRADE (B2)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 695 / 926
926
TRIBUTARY
PROTECTED
SIGNAL

e w w

w e
1 2 3
6 5 4
e w
w e w e
TRIBUTARY
PROTECTED
SIGNAL
WORKING CHANNELS (AU4#1 TO AU4#8)
PROTECTION CHANNELS (AU4#9 TO AU4#16)
Figure 435. 2F MS SPRING Connection
APS in 2–fiber MS–SPRING
In case of fibre break 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 and
displaces ”working” (high priority) AU4s into ”protection” (low priority) AU4s.
Only the NEs adjacent to the failure are interested to the ”switch” and ”bridge” functions while for all other
NEs the final configuration is a ”pass through” of all ”protection” (low priority) AU4s.
The following Figure 436. and Figure 437. highlight how the connections are modified as a consequence
of a ”bridge ” or a ”switch” operation.
• The ”Bridge” operation on the East side for example in the cited figure, has the effect of routing
the outgoing ”high priority” West traffic also to the outgoing ”protection” East capacity.
The Bridge function adds a connection on the opposite transmission side and on the relevant
AU protection.
• When a ”Switch” operation is working on the West side, all the connections that have as a
source an AU4 belonging to the East working capacity are replaced by connections that have
as a source the incoming West protection traffic, maintaining the first destination of the signal.
The Switch function replaces the incoming flow with a protection one, coming from the opposite
1AA 00014 0004 (9007) A4 – ALICE 04.10
receive side.
The diagram of Figure 438. depicts the final effect of these synchronized steps of operations.
3AL 89062 AA AA 696 / 926
926
They are carried out via a protocol using the K1 and K2 bytes by means of which the failed span is replaced
with the capacity of the protection traffic of the span not affected by the failure.
W E W E
W E W E
protection
working
BEFORE AFTER
Figure 436. Effect of a BRIDGE EAST operation
W E W E
W E W E
protection
BEFORE working AFTER
Figure 437. Effect of SWITCH WEST operation

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 697 / 926
926
SWITCH BRIDGE
TRIBUTARY WEST WEST SWITCH
PROTECTED EAST BRIDGE

SIGNAL EAST

E W E W
W E
1 2 3
6 5 4
E W
(*) (*)
W E W E
WORKING CHANNELS TRIBUTARY

PROTECTED
PROTECTION CHANNELS SIGNAL
BRIDGE
SWITCH
(*) All protection AU4 are put in Pass–through in the 5th and 6th NEs
Figure 438. Line break recovering operations

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 698 / 926
926
An example of 2F MS–SPRING is given in Figure 439. on page 700.
In the example a ring of four nodes is protected with 2F MS–SPRING

AU4–1 carries the traffic of each span : C–B, B–A, A–D, D–C
AU4–2 carries the traffic D–B (pass–through in C)
AU4–9 protects AU4–1
AU4–10 protects AU4–2
After a failure in the section C–B, the following actions are taken on C and B nodes:
– node B : Tributary access 1 and 2, previously drop–inserted on AU4–1 and AU4–2

WEST, are switched respectively on AU4–9 and AU4– 10 EAST.
In this way, node C is reached by means of node A and D.
– node C: Tributary access 1, previously drop–inserted on AU4.1 EAST, is switched on

AU4–9 WEST
In this way, node B is reached by means of nodes D and A.
Rx AU4–2 WEST, previously in pass–through on Tx AU4–2 EAST, is looped on
Tx AU4–10 WEST. In this way, nodes D–A, allow to reach node B (Signal
transmitted D to B).
Rx AU4–2 EAST is no more received.
So, the Rx AU4–10 WEST is looped on Tx AU4–2 WEST.
In this way, signal transmitted by node B flows on nodes A–D–C and here is
looped reaching again node D.
– nodes A and D have no switching
From the example it is assumed that it is possible to re–use the bandwidth for some traffic patterns
(AU4–9 protects four connections on AU4–1) having the same protection for several connections (shared
protection).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 699 / 926
926
A
D A . AU4 1 A B : AU4 1

AU4.9–Prot. AU4.1
AU4.10 Prot. AU4.2
D B
C
D C : AU4 1 C B : AU4 1
D B : AU4 2
E
D B
W
W E
C B
WEST EAST WEST EAST

AU4 AU4 AU4 AU4
1 1 1 1
2 2 2 2
9 9 9 9
10 10 10 10
1 1 1 1
2 2 2 2
9 9 9 9
10 10 10 10
1 1 2
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 439. 2F MS–SPRING example of operation
3AL 89062 AA AA 700 / 926
926
SQUELCHING FUNCTION
The Squelching function is activated when a node that carries Tributary Drop/Insert, remains isolated
because of a double failure.
In this case to avoid misconnections on the AU4 involved in MS SPRING protection, an AIS signal will be
inserted on Low Priority streams transmitted from the nodes adjacent to the isolated one. See Figure 440.
Initially, before the double failure has isolated the Node 2, connections between Trib3 and Trib1 and
between Trib2 and Trib4 were both active on AU4 #1 in the example.
After the second failure and without the Squelch function the MS SPRING algorithm would activate the
Bridge and Switch functions on the nodes adjacent to the Node2 and would act a misconnection between
Trib3 and Trib4 by means of the protection AU4#9 in the example. In virtue of Squelching function the
Nodes adjacent to the isolated Node2 send AIS on Low Priority AU4#9 thus avoiding the misconnection
between Trib3 and Trib4.
After the failure has been removed, a similar reverse sequence of operations on the NEs adjacent to the
recovered span will be activated. The reverse procedure can start after a step configurable WTR ( 60 sec.
to 900 sec. ).
TRIB. 3 TRIB. 1 TRIB. 2 TRIB. 4
AU4 #1 AU4 #1 AU4 #1 AU4 #1

E W E W
BRIDGE SWITCH
WEST EAST
1 SWITCH
2 3
WEST BRIDGE
EAST
E
(SF/SD) (SF/SD)
W
AIS ON
AU4 # 9 AIS ON
AU4# 9
5 4
AIS ON AIS ON AIS ON

AU4 # 9 AU4 # 9 AU4 # 9
PASS–THROUGH PASS–THROUGH PASS–THROUGH
6
WORKING CHANNELS
PROTECTION CHANNELS
Figure 440. Squelching on isolated Node connection

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 701 / 926
926
MS – SPRING Interworking
When a 2f MS–SPRING is interworked with another ring (either SNCP OR MS–SPRING), the
interconnection of the two is performed by connecting two nodes per ring with HVC connections, as shown

in Figure 441.

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 by means the Primary Node Service Selector function, between the VC4 coming
from the SSN and the VC4 that can be locally inserted by means an STM–1 Tributary. The selection is
made on the Path–AIS basis (AU–AIS).
The main connection is towards the STM–1 Tributary
The protection mechanism works on the hypothesis that the other ring selects one of the two versions
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 SNCP ring).
Note that the PSN and the SSN need not to be adjacent and need not to be the same for all the VC4s
crossing the ring boundary: i.e. each crossing VC4 has two associated nodes that act as PSN and SSN.
In the Connection Configuration Applications this function is named: D/C IC W(E) that means Drop and
Continue, Insert Connection (protected) . The letter (W=West, E=East) indicates the insertion side of AU4
data stream coming from Tributary or from Line.
2F MS–SPRING
Secondary
Primary SS Service
Service Node
Node
SNCP or MS–SPRING
SS = Service Selector
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 441. MS SPRING Drop and Continue, Insert Continues (protected)
3AL 89062 AA AA 702 / 926
926
18.1.1.1 2–Fiber MS SPRING connection configuration advices
The following suggestions must be considered in the MS SPRING STM16 connection configuration:
• SNCP, 4 Fiber MS SPRING and (Aggregate) MSP protection connections cannot be installed
in a 2 Fiber MS–SPRING network. This leads to an unprotected connections installation.
• AU4s from #9 to #16 don’t have to be used for connections nor considered in any parameter
of ”Squelching table” provisioning. Only AU4s from #1 to #8 must be used and configured for
path installation.
• AU4 permutation ( change of AU4 allocation ) is not allowed. The AU4 allocated to
pass–through in HVC connections must be the same through the node.
• AU4 cross–connection (Aggregate) side, i.e. paths received from the (Aggregate) line and
looped–back to the ( same ) (Aggregate) line are not allowed.
• Follow the “Squelching Table Configuration” in order to define the ”Squelching Table HO” for
East and for West (Aggregate) sides describing, for each connection installed, as Source
Node, the Node Identifier of the node generating the considered AU4 and as Destination
Node, the Node Identifier of the node terminating the AU4.
18.1.2 4–Fiber MS–SPRING description ( not actually supported )
The 1353 SH 5.x provides this feature but the current ADM equipments don’t support it. As illustrated In
Figure 442. ,working and protection channels are carried over different fibers: two multiplex STM16
sections transmitting in opposite directions carry the working channels (AU4#1 to AU4#16) while two
multiplex sections, also transmitting in opposite directions, carry the protection channels ( the same
AU4#1 to AU4#16 working channels or low priority traffic ). The protection mechanism protects the whole
bandwidth ( AU4# 1 to AU4#16 ). It is possible to have span and ring protection as for NPE but the
bridge/switch operation are performed on the adjacent nodes where the failures are detected. Here is only
represented the general connection ring scheme reported in Rec. ITU–T G.841 for future application.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 703 / 926
926
TRIBUTARY
PROTECTED
SIGNAL

e w

w 1 2 e
4 3 w
e
w e
TRIBUTARY
PROTECTED
Protection Channels (AU4#1 to AU4#16) SIGNAL
Working Channels (AU4#1 to AU4#16)
Figure 442. 4 F MS–SPRING Connection
18.1.3 NPE ( 4 Fiber MS–SPRING transoceanic ) description
As described in ITU–T, Rec.G.841–Annex A, the approach of the general purpose MS–SPRING when
applied to very long transmission distances (more than 1500 km) as transoceanic links, is insufficient.
Due to the loop–backs and switchings occurring after particular failures in the general MS–SPRING, the
restored path would lead the signal to cross the ocean three times. The consequent delay will then result
in degraded performance.
In the MS–SPRING for very long transmission distances applications this problem is avoided by switching
only the affected AU–4 tributaries, at the relevant sources and destinations, onto the protection channels
that travel away from the failure. The protection system is realized by using the ring maps and the K–byte
protocol.
The extra channels not involved in the failure and not overlapping with the restored working channels will
still be continued also after the failure.
The four fibre ms–spring requires four fibres for each span of the ring, working and protection channels
are carried over different fibres. Four Aggregate Units are needed for each node.
The four fibre ms–spring supports ring switching as well as span switching.
Ring switching: the affected AU4 is switched at source/destination onto the relevant protection channel
travelling in opposite direction of failure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Span switching: the affected AU4 is switched onto the relevant protection channel travelling in the same
direction of failure, at the nodes adjacent the failure.
3AL 89062 AA AA 704 / 926
926
The ”dual node ring interworking” configurations between more 4F–MSSPRING rings , or between a
4F–MSSPRING and HO–SNCP ring, or between a 4F–MSSPRING and 2F–MSSPRING are supported.
Figure 443. illustrates a general example of a full capacity STM–16 node (NPE, Network Protection
Element), used in the 4F–MSSPRING systems, where all the 64 AU4 channels are terminated. Here HP
stands for High Priority traffic, LP for Low Priority, W for West side, E for East side; the working band is
shadowed and the protection band is blank.
An NPE island with 64 AU4 channels can be composed of four 1664–SM, each 1664–SM is equipped with
four aggregate units.
In the nodes where the drop/insert capacity is not fully used (or where AU4 channels are transited) the
equipment tributaries are in correspondence partially equipped, and also the number of 1664–SM for each
NPE can be reduced.
Figure 444. illustrates an example of a 4F–MSSPRING composed of six nodes. Case (b) shows an
example of ring switching, while case (c) is an example of span switching. The existing low priority traffic
will not be interrupted if the used channels are not overlapping with the restored working traffic.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 705 / 926
926
W E
NPE
1664–SM 1664–SM 1664–SM 1664–SM

W E W E W E W E
16HP 16HP
16HP 16HP
16LP 16LP
16LP 16LP
16W 16W 16E 16E 16W 16W 16E 16E

INS DROP INS DROP INS DROP INS DROP
WORK (HP) WORK (HP) EXTRA (LP) EXTRA (LP)
Figure 443. 4F–MSSPRING. Full capacity NPE (example)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 706 / 926
926
HP HP HP LP
A B C
F E D
WORKING BAND
PROTECTION BAND
LP HP
a) Normal routing configuration
HP HP HP LP
A B C
F E (*) D
LP HP
b) Re–routing configuration in case of double bidirectional failure (ring switching)
HP HP HP LP
A B C
(*)
F E D
LP HP
c) Re–routing configuration in case of single bidirectional failure (span switching)
Note (*): The extra traffic LP is not interrupted, if not overlapping with the restored working channels
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 444. 4F–MSSPRING. Example of routing in case of failures
3AL 89062 AA AA 707 / 926
926
18.1.3.1 NPE connection configuration advices
The following suggestions must be considered in the NPE ( 4 Fiber MS–SPRING transoceanic )
connection configuration:

• SNCP, 2 Fiber MS SPRING and (Aggregate) MSP protection connections cannot be installed
in a 4 Fiber MS–SPRING network. This leads to an unprotected connections installation.
• AU4 permutation ( change of AU4 allocation ) is not allowed in ”Traffic Map Configuration” (WT
/ PT Channels ). The AU4 allocated to pass–through in HVC connections, must be the same
through the node.
• AU4 cross–connection (Aggregate) side, i.e. paths received from (Aggregate) line and
looped–back to the ( same ) (Aggregate) line are not allowed.
• Follow the indication of “Traffic Map Configuration” in order to define the ”traffic map” for
Working and Protection AU4. In this way it is possible to define, in every node, the path of each
AU4 through the ring.
• Only ”New or Enhanced Aggregate” units can be used ( see the relevant ADM 1664 SM
Technical Handbook for Aggregate units ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 708 / 926
926
18.1.4 Different protection mechanisms
Figure 445. shows different protection mechanisms applied on the side West of the “A” node. In this
example it has to be considered a connection between “A” and “D” nodes. The same failure is applied to
a different architecture protection network: 2F MS–SPRing, 4F MS SPRing and NPE.

The adjacent nodes are “A” and “B” , the terminal nodes “A” and “D” and the intermediate nodes are “C
and “D” . When a signal fail clears the APS comes back to the idle status.
Span protection has a higher priority respect to ring protection.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 709 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
Span W Ring W
01
2F Conditions Failure between A–B points 1/2
4F Conditions Failure between A–B points 1/2 Failure between A–B points 1/2 and 3/4
Bridge / Switch mechanism on the head/tail A–B nodes

2F MS–SPRing Not provided the 1–2 links are substituted by 3–4 links but it is protected
only half bandwidth
APS for The 1–2 links are substituted by

4F MS–SPRing and The 1–2 links are substituted by the 7–8 links
the 3–4 links
NPE
4F MS–SPRing Bridge / Switch mechanism on the head/tail A–B nodes
NPE Bridge / Switch mechanisn on the drop/insert A–D nodes
W E W E W E W E W E W E
Figure 445. Protection mechanisms

1 5
1 3 2 6
C 3 7 C
B 2 A 4 B A
926
8
3AL 89062 AA AA
4
W E W E
w w
w/p w/p
w w
p p
w/p D w/p D
p p
710 / 926
18.2 MS–SPRING Management
The 1353SH supports the MS–SPRING protection as Terrestrial and Transoceanic application with a
2–Fiber or a 4–Fiber architecture. The available tables permit to visualize for the same NE the architecture
“N”x 2–Fiber ( “N”=1 for 1664SM 3.1, /3.2, /3.3 ; “N”>=1 for 1660SM ) and 1 x 4–Fiber Transoceanic (NPE
protection) for 1664SM and 1670SM. For the Transoceanic application a max. of 64 nodes are available
and a max. of 16 for the Terrestrial 2–Fiber application.
The MS–Spring configuration can be displayed from any 1664SM equipment, transmission and
synchronization views .
Figure 446. shows the MS–SPRing pull down menu. In the new equipment the MS–SPRing menu has
been represented with only the first option “Main Dialog for MS–SPRing management”.
Figure 446. Display MS–SPRing pull down menu
The first Main Dialog for MS–SPRing management option contains all the commands to configure and
manage the MS–SPRing. The same commands can be selected from the other menu options, then some
NEs visualize only this first option instead of the complete MS–SPRing menu. The following first three
commands Create ..., Set ..., Manage ..., configure any MS–SPRing protection type. The Configure
Squelch Table is only used for terrestrial application while the Configure Ring Traffic Map only for
transoceanic application. The View Protection Status parameters permit to manage the protection with
external commands ( force protection, lockout protection ...) and to check the behavior of the protection
mechanism.
In any dialog box is present the Cancel or Close buttons. When the user clicks on these buttons the dialog
box will close without starting any operation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 711 / 926
926
18.2.1 MS–SPRing Configuration
Select the MS–SPRing pull down menu. Then select the Main Dialog for MS–SPRing management
option from the pull down menu.

The following dialogue box is displayed ( Figure 447. ).
Figure 447. MS–SPRing Management dialogue box.
The only command available is “Create” . The name of Schema Selection is not editable but is fixed to
“New Schema”. For 1660SM, it is possible, to have many 2F MS–SPRing protection schemas. Hence
many different “New Schema” configurations can be created..
Click on Create to start the MS–SPRing configuration. Figure 448. opens. The same opens clicking on
“Create a MS–SPRing Schema” of the MS–SPRing pull down menu.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 712 / 926
926
Figure 448. Creation Schema dialog box.
The user can select the MS–SPRing Application and the Architecture types supported by the ADM
selected.
The Port Selection depends on the Architecture type: if the architecture is a 2F MS–SPRing, the working
and protection port on each side is the same. If the architecture is a 4F MS–SPRing, the working and
protection ports on each side are different. The label r(xx)s(y)b(zz)port#(hh) where r=rack, s=subrack,
b=board give the position of the physical port. In the same board it is generally possible to have different
port numbers. Only one port number (port#01) is available in the present generation.
Actually for 1664 SM the working and protection aggregate boards have a fixed location in the subrack.
In the new generation equipment the above mentioned positions are selectable from a list available
clicking on the “Choose Port” buttons.
The OK button will start the selected operation. The cursor is displayed busy up to receiving a reply. Then
the dialog window will be closed. Figure 449. opens and all commands are now available.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 713 / 926
926
Figure 449. Activated MS–SPRing Management
Click on Ring Map to configure the network node connection. Figure 450. opens. The same opens
clicking on “Manage Ring Map” of the MS–SPRing pull down menu.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 714 / 926
926
Figure 450. Node Id and associated ring node position.
The Ring Map sets the connection of the nodes within the ring. The matrix represents up to 64 nodes for
transoceanic application and up to 16 nodes for terrestrial application.
Enter Current NodeId in the box and push Change NodeId button.
Select Available NodeId in the pull down list (0 to 63 for transoceanic application; 0 to 15 for terrestrial
application) releasing the left mouse button or pushing the stepper arrows and enter keys to select the
NodeId value. This will be displayed in the Available NodeId box then click on Add Node button. Clicking
on the Add Node button the selected ring position will shift one step on the right starting from “1” position
and in the same time the Available NodeId will be updated to a new value. The default association for a
four node ring related to the first node (Current NodeId =0; Ring Position =1 ) is depicted in Figure 451.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 715 / 926
926
Figure 451. Ring map configuration
Repeat the procedure for all nodes of the ring selecting the different NEs (4_adm 1 to 4_adm 4) and edit
the different Current NodeId value.
To remove a node, select the node and click on Remove Node button. The following Ring Position of
the nodes on the right decreases by one and the erased NodeId is inserted into Available NodeId , so
it can be assigned to other nodes.
The OK button will start the selected operation, displaying the busy cursor up to receiving the reply to the
actions. Then the dialog window will be closed.
Click on the WTR Time button. Figure 452. opens. The same opens clicking on “Set WTR Time
parameters” of the MS–SPRing pull down menu.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 716 / 926
926
Figure 452. WTR dialog box.
Click on the push mouse button to open the pull down window to select the required delay. The step value
is 60 seconds. The range value accepted is from 60 seconds to 900 seconds. Adding values are 20, 30,
45, 60, 90 minutes and 2, 4, 12, 24, 48 hours (in some W/OMSN this time is fixed to 300 sec.). Click on
OK to apply the WTR Configuration.
N.B. The same WTR time must be set in each ring Node.
18.2.2 Squelching table with Terrestrial applications
With a Terrestrial application can be selected the Squelching Table while with a Transoceanic
application can be selected the Ring Traffic . If the operator tries to select a different table a error message
is visualized. Figure 453. shows the error message visualized when is selected the Ring Traffic with a
Terrestrial application.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 453. Example of error message
3AL 89062 AA AA 717 / 926
926
Click on Squelching Table to configure the AU4 (AU4#1 to AU4#8 for 2F Architecture, AU4#1 to AU4#16
for 4F Architecture ) connection between the different nodes. Figure 454. opens. The same opens
clicking on “Configure Squelch Table” of the MS–SPRing pull down menu.

Figure 454. Squelching table document, use and communication of its contents
When the window is opened for the first time the squelching table is N/A ( not available ) because the ADM
has never been configured. Point the mouse on the matrix position and click on the right mouse button
to open the node list menu. Select the node identification number (1 to 16 for 2F architecture, 1 to 64 for
4F architecture ) from the available list using the slider or the stepper arrows on the right scroll region.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 718 / 926
926
18.2.2.1 Squelching table example
Figure 455. is an example of ring traffic. Figure 456. shows how to configure the relative squelching table.
AU4#3 AU4#1
AU4#2
West A East West B East
AU4#1
AU4#2
AU4#3 AU4#3
D C
East West East West
Figure 455. Example of a ring traffic
The squelching table is now applicable only for HO–VC signals ( 1664SM and 1661SMC ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 719 / 926
926
AU west Node west
Number A B C D A
1 VC
2 VC
3 VC
4
5
6
Sample traffic routing for a four node ring
NODE A NODE B
West East West East
Tx Rx Tx Rx Tx Rx Tx Rx
Src/Dst LO Src/Dst LO Src/Dst LO Src/Dst LO Src/Dst LO Src/Dst LO Src/Dst LO Src/Dst LO
1 A B * B A * 1 B A * A B * B D D B
2 A D * D A * 2 D A * A D * A D * D A *
3 A C * C A * A C C A 3 C A A C A C C A
NODE C NODE D
West East West East
Tx Rx Tx Rx Tx Rx Tx Rx
Src/Dst LO Src/Dst LO Src/Dst LO Src/Dst LO Src/Dst LO Src/Dst LO Src/Dst LO Src/Dst
1 D B B D B D D B 1 D B B D
2 D A * A D * A D * D A * 2 D A * A D *
3 C A A C C A * A C * 3 A C * C A * C A * A C *
Src – node at which an HO VC enters the ring or is sourced

Dst – node at which an HO VC exits the ring or is terminated
All connections in this example are bidirectional.
* – indicates an LO VC organized AU
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 456. Squelching table of Figure 455.
3AL 89062 AA AA 720 / 926
926
18.2.3 Traffic Map with Transoceanic application
After having set the Schema Configuration, the WTR Time and the Ring Map for the transoceanic
application, the user has to configure the ”traffic maps”. That means to describe each path implemented
on the ring, in terms of cross–connections make up that path inside each node.
18.2.3.1 General information on Connection Configuration
Here are briefly described some parameters indicated in the configuration tables:
The main connection types are:
• Drop/Insert
Terminated connections between Tributaries and Aggregates (Trib. to Agg.)
• Pass–Through
Connection between Aggregate West and Aggregate East ( or vice versa ) through the matrix
• Point–to Multipoint, First–Point–to–Multipoint, Last–Point–to–Multipoint
Signal broadcasting from one aggregate/tributary to other Aggregates/Tributaries.
• Drop and Continue P (Working/Protection Channels)
Drop, insert through the switching service (SS) and bidirectional pass–through between the
aggregates through the Continue function ( Used in Primary node for dual–node ring
interconnection ).
• Last Drop Continue
Same as Drop/Insert, but used in Secondary node for dual–node ring interconnection.
• Continue
Bidirectional connection to the same side Aggregates. It can be applied to AU4 #k (working
channels i=1 to 16/64 and k=i+16/64) protection channels to realize the “Drop and Continue
P “ function (or working channels to realize the “Drop and Continue W “ function ). Continue
is only associated to the Drop and Continue function.
• No Connection
• Concatenation
It means:” same Cross–connections as the one of the first AU4 of the AU4–4c concatenation
signal” It is not a cross–connection type but a different AU4 configuration: each AU4 is
connected to the following increasing the total bandwidth (N x AU4) capacity (see Figure 473. ).
• Mixed configurations of previous connections
All the previous connections are possible on:
• AU–4
1AA 00014 0004 (9007) A4 – ALICE 04.10
can be referred to STM 16/64 interfaces
For each type of main connection is listed the available mode.
3AL 89062 AA AA 721 / 926
926
• Drop/Insert (see Figure 457. )
– Insert to West (or East)

The selected AU is transmitted from the tributary to only one Aggregate in the
corresponding West (or East) side. This cross–connection may be part of one
unidirectional path, or of one direction of a bidirectional path.
WEST AGGREGATES EAST

Rx Tx
Tx Rx
TRIBUTARY
Tx Rx
Figure 457. Insert to East
– Drop West (or East) (see Figure 458. )
The selected AU is received from only one Aggregate.
WEST AGGREGATES EAST

Tx
Rx
Tx Rx
TRIBUTARY
Tx Rx
Figure 458. Drop East

1AA 00014 0004 (9007) A4 – ALICE 04.10
– Pass–through (see Figure 459. )
With regard to pass–through traffic, if the path is bidirectional, the same AU must be used
for both directions, i.e., West to East, East to West).
3AL 89062 AA AA 722 / 926
926
Both modes can be selected, therefore, a bidirectional channel can be obtained by
selecting both modes using the same AU in the working or protection channels.
The pass–through can be distinguished in West to East or East to West by the direction
arrow
WEST EAST
Working Channel i Tx
Rx
Direction
Pass–Through Pass–Through
Matrix
AGGREGATES
Protection Channel k=i+16/64

WEST EAST
Direction
Tx Rx
Pass–Through Pass–Through
Matrix
Figure 459. Example of West to East Pass–through with its protection
• Point–to–Multipoint, First–Point–to–Multipoint, Last–Point–to–Multipoint
The allowed selection is the broadcast of the incoming signal towards the tributary and the
opposite aggregate
The Point–to–Multipoint path broadcasts the incoming signal to different nodes according
to the following rules: in the first drop node the cross–connection traffic is named “First
Point–to–Multipoint”, in the last drop node the same traffic is named “Last
Point–to–Multipoint”, in any intermediate drop node this traffic is named
“Point–to–Multipoint”. This convention allows to minimize the switching protection only for
not reachable nodes.
Tributaries Source First drop Intermediate Last

node node drop node drop node
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 460. Point–to–Multipoint path
3AL 89062 AA AA 723 / 926
926
West East

Working i Working i

Tx
Matrix
Rx
AGGREGATES:
i= working, k=i+16/64 = protection
Tributary
Protection k Protection k
Tx
Rx
Matrix
Figure 461. Point–to–Multipoint configuration and relevant protection channel
• Drop and Continue
The Drop&Continue architecture is applied for dual node ring interconnection.

Interworking between the transoceanic MS–SPRing and another ring shall be achieved
using two nodes (named Primary and Secondary nodes). The cross–connection on the
first node (the Primary node) is performed by the “Drop and continue” and the “Continue”
functions. The current configuration can be “Drop & Continue P” then are used the
protection channels or “Drop & Continue W” if are used the protection channels. The
Secondary node, that may not be adjacent, is the protection of the Primary node and
utilizes the “Last Drop Continue” connection.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 724 / 926
926
Working i Working i
Tx
Rx
0
Matrix
Tx Rx
SS
AGGREGATES i and k=i+16/64

Protection k
Tx
TRIBUTARY
Rx
Rx Tx
Drop and Continue Continue
Figure 462. Drop & Continue and Continue
Drop and Continue is associated to the Continue function. Figure 462. depicts the whole
functionality. The cross–connection provides the Drop and Continue P (Protection)
for1664SM and Drop and Continue W(Working) for 1670SM. This configuration is always
bidirectional.
• Last Drop & Continue
The second ring interconnection of the “Secondary” node is named Last Drop & Continue.
The “Secondary” node is the protection node. Actually “Drop and Continue” configuration
uses only the protection channels (k=i+16/64). Thus the “Last Drop and Continue” has to
utilize the protection channels.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 725 / 926
926
West East
AGGREGATES i and k=i+16/64
Working i Working i

Rx Tx
Tx Rx
Protection k Protection k
Rx Tx Rx
Tx Rx Tx
TRIBUTARY
Tx Rx
Figure 463. Example of Last Drop & Continue on West side (protection on East)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 726 / 926
926
18.2.4 Traffic map table description
The application lists to the operator a two–section matrix: one for working traffic (WTXC Map) the other
for the protection traffic (PTXCMap). Each section manages 64 x 2 columns with N x 2 rows; every two
column correspond to West and East side of a node (maximum node number=64) while N depends on
the STM–N level (for 1664 SM, N=16).
Click on Traffic Map, Figure 464. opens. The same opens clicking on “Configure Ring Traffic Map” of
the MS–SPRing pull down menu.
Figure 464. Example of Traffic table
Select the radio button related to the cross–connect (XC) type at the bottom of the window and then point
the mouse to a matrix position corresponding to a row/column crossing and push the left mouse button.
The possible traffic indications are:
1AA 00014 0004 (9007) A4 – ALICE 04.10
– PT for Pass–Trough
– D for Drop
3AL 89062 AA AA 727 / 926
926
– I for Insert
– PTM for Point–to–Multipoint

– FPTM for First Point–to–Multipoint

– LPTM for Last Point–to–Multipoint
– C for Continue
– D&CW for Drop & Continue Working for 1670SM
– LDC for Last Drop Continue
– CNC for Concatenated
– D&CP for Drop & Continue Protection for 1664SM
– NC for No Connection
For each node and any AU4# select the right XC(cross–connect) option.
In this way it is possible to configure the type of connection of each AU4 in all the 64 nodes of the ring.
Note that the node indications ( first row ) of the” traffic map” tables are referred to the node identification
and not to the physical position of the ”ring map”.
The meaning of the abbreviation is explained at the window bottom.
The symbol indicates the ” West Tx side” or the ”East Rx side”.
The symbol indicates the ”West Rx side” or the ”East Tx side”.
18.2.5 Symbolic representation
Drop=D, Insert= I ( Figure 465. ).
West East West East West East

D I D I
AU–4 #i I D
I D
Bidir. Bidir. Unidir. Unidir. Unidir. Unidir.

D/I West D/I East D West I East I West D East
Figure 465. Drop/Insert

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 728 / 926
926
Pass –Through = PT–PT ( Figure 466. )

PT PT PT PT
AU–4 #i
PT PT PT PT
unidirectional West to East bidirectional unidirectional East to West
Figure 466. Pass–Through
First–Point–to–Multipoint=FPTM–FPTM, Point–to–Multipoint=PTM–PTM,
Last–Point–to–Multipoint=LPTM
West East West East West

AU–4 #i FTPM FTPM PTM PTM LPTM
first node intermediate node last node
Figure 467. Point–to–Multipoint
Continue=C (protection AU4#k=i+16/64) and Drop and Continue P=D&CP (working AU4=i)
East West
D&CP D&CP
AU–4 #i D&CP D&CP
West East
C C
AU–4 #k
C C
Drop & Continue Drop & Continue

Continue West Continue East
Figure 468. Drop & Continue plus Continue

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 729 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
AU–4 #k
Last Drop Continue=LDC
East
LDC
LDC
Figure 469. Last Drop Continue
LDC
LDC
West
926
3AL 89062 AA AA
730 / 926
18.2.6 Ring Normal / Extra–Traffic Examples
The ring Normal/Extra–Traffic maps may be drawn up by giving the description of each installed path in
terms of the whole set of cross–connections set up inside each node traversed to the path itself.
AU–4 #i (working channel) i=1 to 16

AU–4 #k (protection channel) k=i+16
B F
C E
Figure 470. Traffic example in ring
For example (see Figure 470. ), the Normal bidirectional paths installed between A and D and between
D and F on the working AU–4 #i are described by the ring normal traffic map as depicted below:
A B C D E F
West East West East West East West East West East West East
I PT PT PT PT D I PT PT D
AU–4 #i
D PT PT PT PT I D PT PT I
path path
(working channel)
Figure 471. Ring normal traffic map
Likewise, the Extra–Traffic bidirectional path set up between A and B on the protection AU–4 #k are
described by the ring extra–traffic map as depicted below:
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 731 / 926
926
I D
AU–4 #i
D I

path
(protection channel)
Figure 472. Ring extra–traffic map
A contiguous concatenated path (AU–4–4c) may be represented ( Figure 470. ) by fully describing it only
in the first row (i.e., the one with the smaller channel number), and merely padding the next three ones
with a special marker to show that they are concatenated to the first and thus share the same
characteristics (see figure below).
A B C D E F
I PT PT PT PT D
AU–4 #i
D PT PT PT PT I
CNC CNC CNC CNC CNC CNC

AU–4
#i+1

AU–4
#i+2 CNC CNC CNC CNC CNC CNC
AU–4 CNC CNC CNC CNC CNC CNC

#i+3 CNC CNC CNC CNC CNC CNC
Figure 473. Ring Normal traffic map: concatenated path

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 732 / 926
926
The ring traffic map ( Figure 475. )represents the point–to–multipoint path of Figure 474. depicted
below:
C B A R Q
D P
E N
F G H L M
Figure 474. Point–to–multipoint
A B G H L M
West East West East West East West East West East West
I PT PT FPTM FPTM PTM PTM LPTM
AU–4 #1
(working channel)
Figure 475. Ring normal traffic map describing a point–to–multipoint unidirectional path
(node L knows that its drop connection is the farthest of a point–to–multipoint path because its preceding
node’s East outgoing path on the same time slot is a point–multipoint cross–connection).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 733 / 926
926
18.2.6.1 Dual ring interconnection examples
The ring figures show the working channels with blue lines, the protection channels with red lines. The
white pipes depict the working channels while the grey pipes the protection ones.

W E
A B C A B C
NPE
B NPE
F E D F E D
E W E W
A B C A B C
A NPE
NPE
F E D F E D
Figure 476. 2 NPE rings, bidir, D&C, no prot. in NPE
B C D E F
West East West East West East West East West East
I D&CP (working
AU–4 #i channel)
D D&CP
D E F
C LDC (protection
AU–4 #k LDC channel)
C
Figure 477. Path of Figure 476. B

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 734 / 926
926
A B C A B C
NPE
B NPE
F E D F E D
E W E W
W E W E W E
A B C A B C
A NPE
NPE
F E D F E D
E W
Figure 478. Bidir, D&C, no prot. in NPE, (add/drop node = Primary)
A B C E F
PT PT D&CP I (working
AU–4 #i
PT PT D&CP D channel)
A B C E F
PT PT C LDC (protection
AU–4 #k
PT PT C LDC channel)
Figure 479. Traffic map of Figure 478. A and Figure 476. A
A B D E F
C LDC (protection
AU–4 #k
C LDC channel)
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 480. Path of Figure 478. B
3AL 89062 AA AA 735 / 926
926
W E W E W E
A B C A B C

NPE
C NPE
F E D F E D
E W E W E W
W E W E W E
A B C A B C
D NPE
NPE
F E D F E D
E W
Figure 481. Bidir, D&C, no prot. in NPE
A B C D E F (working
West East West East West East West East West East West East channel)
I D&CP
AU–4 #i
D D&CP
(protection
channel)
PT PT PT PT PT PT LDC C
AU–4 #k
PT PT PT PT PT PT LDC C
Figure 482. Traffic map of Figure 481. C
A B C D E F (working
West East West East West East West East West East West East channel)
D&CP I
AU–4 #i
D&CP D
(protection
C PT PT LDC channel)
AU–4 #k
C PT PT LDC
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 483. Traffic map of Figure 481. D
3AL 89062 AA AA 736 / 926
926
W E W E W E
A B C
B
NPE
F E D
E W E W E W
Figure 484. Unidir, D&C, no prot. in NPE
A B C D E F
AU–4 #i (working
PT PT D&CP D&CP PT PT channel)
AU–4 #k (protection
C LDC LDC C channel)
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 485. Traffic map of Figure 484. B
3AL 89062 AA AA 737 / 926
926
18.2.7 Activate, Deactivate and Delete commands
The Main Activities commands ( Figure 447. ) manage the MS–SPRing configuration. The MS–SPRing
status can be Enable, Active, Disable and Inactive.

After having configured the protection schema by means of the Create button, the status becomes
Enable .
The Activate button selection enables the MS–SPRing protection mechanism on the selected schema
configuration.
To change from Active to Enable click on the Deactive button. This command starts the request to
deactivate the MS–SPRing protection mechanism.
When the selected protection schema is Enable the Delete button starts the request to remove it. The
delete action is started after confirming the window message (Figure 486. ).
Figure 486. Confirmation message
During the activation procedure on different ADMs some of these can be in Active status , others in Inactive
status. The statuses, the protocol request and the protocol protection errors are described in the chapters
describing the“MS–SPRing Protection Status and Commands” .
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 738 / 926
926
18.3 MS–SPRING Protection Status – Commands for NPE Application
18.3.1 4F MS–SPRing protection commands

If a protection schema is Active it is possible to select one of the above commands.
Click on the MS–SPRing pull down menu and select View Protection Status parameters. (the same
window opens from MS–SPRing –>Main Dialog for MS–SPRing management and select Prot.
Commands). Figure 487. opens.
Figure 487. Example of protection states and commands ”Idle” status (4F)
The working/protection span state boxes are available only for the 4Fiber MS–SPRing architecture.
The ring and span protections are depicted on Figure 488.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 739 / 926
926
W E W E
w w
w
X w

A B

p p
p p
Span Protection:
the working channels are
substituted by the protection
channels
W E W E
w w
X
w w
p A B p
p p
Ring Protection:
the working channels are substituted
by the ring protection channels ”p”
( B on East side )
( A on West side )
Figure 488. Span and Ring Protection (4F)
18.3.2 External commands (4F)
The external protection commands are : Lockout, Force, Manual, Exercise (if available), WTR.
The lockout commands disable the MS–SPRing management.
The lockout section presents six lockout commands ( Figure 489. ). Each lockout command is applicable
on different points where the lockout actions has to be performed ( Figure 490. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 740 / 926
926
Figure 489. Lockout commands (4F)
W E
w w
w w
p
A p
p p
Protection Span West Working Span West Protection Span East Working Span East
W E
w w
w w
p
A p
p p
Working Ring West Working Ring East
Figure 490. Protection and working channels where the lockout command can be activated (4F)
The protection events can be equipment/signal failure, signal degrade or external command or a
combination of them.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Hereinafter these events are named “Events” and the single event “Event”.
3AL 89062 AA AA 741 / 926
926
The “Events” will be served if some actions (B/S=bridges and switches) are executed and the network
has been updated.
The “Events” will be signalled if the K1/K2 protocol communicates to the network nodes what has

happened.

The ring traffic can be completely restored when there are also two or more span failures. A single ring
failure is completely restored but not two ring failures or a ring and a span failure. When are present
multiple ring failures the automatic B/S protection will try to maintain on all the possible connections.
The K1/K2 communication protocol MS–SPRing is generated from the two nodes adjacent to “Event” via
the protection communication channels. A node is defined tail –end when it firstly receives the “Event”,
the second node is defined head–end when it receives back the protocol answer. Figure 491. shows the
association of tail–end / tail–end or head–end / tail–end.
Some network protection mechanisms are accepted or rejected depending on the end type (tail/head)
(lockout command,...)
W E W E W E
w
B X p A X
w
p C
p p
Tail–end Tail–end/Head–end Tail–end
Figure 491. Tail–end / Head–end association
If the node is tail–end, the lockout working ring/span commands disable the protection MS–SPRing
mechanisms, while if the node is head–end, it serves the request node protection. With the lockout
protection span command and a ring failure, the ring protection is served if this ring failure occurred along
the same span ; the ring protection is disabled if this ring failure has occurred in another ring section.
Instead of a span protection a ring protection is attempted with a working span failure and a lockout
protection span (see Figure 492. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 742 / 926
926
Lockout protection
span
w failure
w
A
p
p
W E
ring protection
Lockout protection
span
failure
w
w
A p
p
W E
E
C
no ring protection
Lockout protection
span
w failure
w
A p
p
W E
ring protection
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 492. Ring protection with a lockout protection span and a ring failure (4F)
3AL 89062 AA AA 743 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
Lockout Working Lockout Working Lockout Working Lockout Working Lockout Protection Lockout Protection
01
Ring W Ring E Span W Span E Span W Span E
A Node A Node A Node A Node A Node A Node
Combinations
of non–served ”1” together ”2” ”3” together ”4” 1 3 signal degrade signal degrade
”1” together ”5” ”3” together ”6” detected in ”2” detected in ”4”
failures:
ring protection on ring protection on
the opposite side the opposite side
if the ring failure if the ring failure
occurs between occurs between
A–C or C–B nodes A–B or B–C nodes
W E W E W E
w w
w 3 w
p 1 p
B A C
5 4
p p
2 6
926
3AL 89062 AA AA
Figure 493. Lockout command and non–served failures (4F)
command disables the acknowledgment of the signal failure/degrade on the aggregate ports.
Figure 493. shows a ring with three nodes and the actions performed by the lockout commands. This
744 / 926
The Force command ( Figure 494. ) executes a forced protection. The Force Span command substitutes
the working channels onto the relevant protection channels between two adjacent nodes on the same
direction ( respectively East side and West side or vice versa ). The Force Ring command substitutes
the working channels with the protection channels between two adjacent nodes on the opposite direction
( Figure 495. ).
Figure 494. Forced and Manual commands (4F)
W E
w w
w w
A1 p
A B p
B1
p p
W. channels are substituted by P.channels

Span West on the same side for both adjacent nodes Span East
W E W E
w w
w w
p A1 A p p
B B1 p
p p p p
W. channels are substituted by P.channels

on the opposite side for both adjacent nodes
Ring West Ring East
Figure 495. Manual and Force Span/Ring command (4F)
The Manual command is similar to Force command but it is at a lower priority level with respect to
automatic MS–SPRing.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 745 / 926
926
When a force ring command is applied a next working span failure is not able to modify the forced
configuration applied. That is because force ring command has a higher priority respect to the “Automatic”
working span protection . But if the failure is detected on the protection channels the “Force” ring
command is not served because, in this case, the span protection priority is higher than the “Force” priority

(see Figure 496. ). Vice versa the “Manual” protection is exceeded by the “Automatic” protection.

Force Ring
failure
w w
w w
p
A
p
W E
w w
E
C B
W p p
Force Ring
w w
w w
p
A
p
failure W E
w w
E
C B
W p p
Figure 496. Examples of a “Force” command and a “Automatic” protection span (4F)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 746 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Signal fail/degrade Signal fail/degrade Signal fail/degrade Signal fail/degrade
Ring W Ring E Span Working W Span Protection W/E
A node A node A node A node
B/S actions 1–2 channels are 8–7 channels are 1–2 channels are The working channels 1–2
sobstituted by 5–6 channels sobstituted by 4–3 channels sobstituted by 3–4 (W) or 7–8 (E) remain active
W E W E W E
w w
1 8
B w 2 A 7
w
p p C
3 6
p 4 5 p
Figure 497. Automatic protection Bridge/Switch (4F)
926
3AL 89062 AA AA
747 / 926
The Exercise command has been provided to detect MS–SPRing failures until a protection switch is
made. In a MS shared protection ring the protection is shared among all the ring nodes. Thus an
undetected failure in one span makes ring switching impossible for all the spans on the ring. If a controller
failure is detected during the exercise operation command an alarm is generated and the ring protection

restoring procedure can be activated. The Exercise Span and Ring commands exercises the related

channel protection without completing the actual bridge and switch operations. The commands are issued
and the responses are checked but the normal traffic are not affected.
The Exercise commands simulate the same bridge/switch operation reported on Figure 495.
The general priority scale that can be applied to solve antithetical situations starting from the lowest priority
level is: exercise ring, exercise span, manual ring – manual span – automatic working ring – automatic
working span – force ring – force span – automatic protection span – lockout
Each command starts when the proper button is selected. A dialog box ( Figure 498. ) has to be confirmed
before the command is performed.
From each command exists its own Release button to cancel the previously selected command and come
back to normal MS–SPRing protection.
Figure 498. Example of confirmation dialog box

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 748 / 926
926
Clicking on the WTR command Figure 499. opens. If the WTR box, in the Local Condition, becomes red
a waiting time has been activated after repairing the ring/span failure. The waiting time, set in the
configuration menu, can be cleared selecting the appropriate clear command. A confirmation dialog box
opens and, if the operator clicks OK, the WTR box turns off and the protection status window is updated.
Figure 499. Clear WTR commands (4F)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 749 / 926
926
18.3.3 4F MS–SPRing dual protection commands
In general dual contemporary “Events” can be:

two external commands

an external command and a ring/span failure
two contemporary ring/span failures
Dual “Events” can appear on the same side W/W or E/E (SS= same side) or on the opposite side W/E
or E/W (OS= opposite site) of the ring network. In the SS or OS the “Events” can appear on the same node
(SN) or on the different nodes (DN), the different node can be an adjacent node (AN) or a remote node
(RN). Figure 500. depicts a clockwise ring network . The network propagation K1–K2 protocol signals
are according to the following legend :
C = served the column element
R = served the row element
B = served both row and column elements
Cs = signalled (not served) the column element
Rs = signalled (not served) the row element
Bs = signalled (not served) both row and column elements
B(ring) or Ring = the row and column elements combine to serve the ring protection
RMs /CMs= the row/column element cannot be neither served nor signalled (this is only for
“Automatic working ring ” ) ; only the row/column “Protection span ” is served.
when a command (Manual switch, Force switch) is neither served nor signalled that is erased ( it
is not pending at the node)
the “C” column is related to “Other points” indication, while the “R” row is related to the
“Reference point” indication.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 750 / 926
926
Reference point
clockwise
OS SN SS SN
W E
SS RN E W OS AN
4 2
W E W E
OS RN w w SS AN
w w
p 3
p
p p
SS RN OS RN
Figure 500. Ring network reference scheme for dual “Events” (4F)
In the reference scheme of Figure 500. the adjacent node (AN) is the node connected to the reference
point
The automatic protection for dual ring failures is represented in Figure 501.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 751 / 926
926
Column
Row Reference

Automatic

point

Protection Working
Other Span Ring Span

points
SN C Ring
SS AN R,CMs Node B isolated R,Cs
Ring
RN R,Cs B R,Cs
SN R,CMs Node A isolated R,Cs
OS AN C Ring Ring
Working
RN R,Cs Node B isolated R,Cs

SN Ring Ring
SS AN B C,Rs B
Automatic
RN B C,Rs B
Span
SN B C,Rs B
OS AN Ring Ring Work. Span
RN B C,Rs B
SN Prot. Span Ring Ring
SS AN
B C,RMs B
Protection
RN B C,Rs B
Span
SN B C,RMs B
OS AN Prot. Span Ring Ring
RN B C,Rs B
Figure 501. Automatic protection for double ring failures (4F)
Ring, Work. Span (Working Span) and Prot. Span (Protection Span) : the two failures combine to a single
failure and a single protection.
Figure 501. reports the failures network indications R,CMs and C,RMs in case of a tail–end/head–end
node mode. Hence the protection span indication will be served ( Figure 502. ) instead of having signaled
the ring failure indication ( Figure 503. ). The indications reported in the Figure 501. are in fact related to
a tail–end/head–end adjacent node mode. The same modality is applied on the table of Figure 504.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 752 / 926
926
ring failure Protection
span failure
w
w
A p
p
W E
E W
C B
E
W
Protection
span failure
w
w
A p
p
W E
E W
C B
E
W
ring failure
Figure 502. Protection span and ring failure with a tail–end/head–end node mode ( R,CMs)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 753 / 926
926
ring failure Protection
span failure

w
w
A p
p
W E
E W
C B
E
W
Protection
span failure
w
w
A p
p
W E
E W
C B
E
W
ring failure
Figure 503. Protection span and ring failure with a tail–end/tail–end node mode ( R,Cs)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 754 / 926
926
The same reference schema is applied to describe dual generic “Events” where is considered both the
ring/span failure and the external command.
The first row at the top of the protection table (Figure 504. ) shows the “Events” at the reference point. For
each of them the associated “Event” is listed on the first column at the left of the table. The first dual “Event”
is a “manual ring” command on the reference point associated to a “manual ring” on the same node at the
same side, that is the same command repeated two times: no double command.
A manual ring on the reference point and a manual ring SS–AN break the ring into two isolated sections,
no possible action only signalled “Events” : Bs. The same happens when is considered a manual ring
SS–RN or OS–RN. A manual ring on the reference point and on OS–SN are antithetical: Bs. A manual
ring on the reference point and on OS–AN don’t break the ring into two separated sections (”A” node is
connected to “B” through “D” and “C” nodes) : B .
Manual span has a higher priority with respect to manual ring thus the result is: C. The C,Rs indication
means that the column is served while the row is only signalled.
Force ring has a higher priority with respect to manual ring, thus the result is: C.
Manual (force) ring and lockout ring SS–SN are antithetical: the lockout ring command doesn’t consider
the k1/k2 protocol while the manual ring makes use of it (bridge and switch) to change the signal
transmission (same reason is for manual (force) span and lockout span SS–SN). In this case lockout ring
has a higher priority with respect to manual (force) ring and the result is: C. When manual (force) and
lockout commands are activated on separated points they coexist and are both served: B.
Manual (force) ring and lockout protection span follow the following role: both are served if related to
SS–SN or OS–AN. Otherwise the manual ring is disabled.
Manual span (second column) has a higher priority with respect to manual ring and the result is: R. Two
manual span commands on different points are accepted and served: B. A manual span and a Force ring
are antithetical, they break the ring into different sections. Force ring is priority respect to manual span:
C. Manual span and force span coexist if they don’t point to the same span. Manual span and force span
SS–SN or OS–AN point to the same span and the result is: C.
Manual (force) span and lockout working ring/span coexist if they don’t point to the same channels (lockout
working span SS–SN) and are served: B. Lockout working span has a higher priority with respect to
manual span thus for lockout working span SS–SN the result is: C. Manual (force) span and lockout
protection is the same as manual span and force span.
Automatic working ring and manual ring/span cannot be supported together, the automatic working ring
has a higher priority with respect to any manual command and the result is: R.
Similar consideration can be repeated for the other table results. The automatic protection span and
lockout protection span columns give the same results.
Automatic working ring and force span OS–SN: this situation is similar to the one described in Figure 502.
The network node failures are considered for automatic working ring column unidirectional failures
(tail–end head–end adjacent node mode). The ring failure cannot be signalled because the
communication protocol k1/k2 is busy to send the force command, it is only possible to serve the protection
span . The result is: C.RMs.
Force ring command and force span SS–SN / OS–AN point to the same signal and the final result is force
span: C. The others results can be easily deduced from the previously cited examples.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 755 / 926
926
Reference Manual Automatic Force Lockout
point Protection Working Protection Working
Other Ring Span Span Ring Span Ring Span Span Ring Span

points

SN R B R R R R B R B
SS
AN Bs R R R R R R R B B
Ring
RN Bs R,Cs R,Cs R R,Cs R R,Cs R,Cs B B

SN Bs R R R R R R R B B
OS
AN B R B R R R R B B B
Manual
RN R,Cs R,Cs R R,Cs R R,Cs R,Cs B B

Bs
C R R R R R R B R
SS SN
R B R B B B
AN C B B B
Span
RN C,Rs B B R B R B B B B
SN R B R B B B B
OS C B B
AN R R R R R R B B
C B
RN C,Rs B B R B R B B B B
SS SN B C C R B R B
C C
AN
C C R Bs C B R R B B
Ring
RN C C R,Cs Bs C B R,Cs R,Cs B B

OS SN C C R Bs C B R R B B
AN
C C B C C B R B B B
Force
RN
C C R,Cs Bs C B R,Cs R,Cs B B
SS SN C C R Cs C C R B R
AN
C B B C,Rs B C B B B B
Span
RN
B B B C,Rs B B B B
C,Rs C,Rs
OS SN C B B C,RMs B C B B B B
AN
C R Bs C C B R B B
C
RN C,Rs B B C,Rs B C,Rs B B B B
SN B
SS C B B C B C
Ring
AN B B
B B B B B
RN
B B B B B B B B
Lockout Working
SN B B
OS
B B B B B
AN B B
B B B B B
RN
B B B B B B B
SN B C
B C B B(ring) B
SS AN B B B B B B
B
RN B B
B B B B B B
SN B B B B B B
B
Span
AN B B B B B
B B(ring)
OS RN B B B B B B B
SS SN B(ring)
B C B B B C
Lockout Protection
AN
C B B C,RMs B C B
Span
RN
C,Rs B B C,Rs B C,Rs B B
SN C B B C,RMs B C B
OS AN B C B B B(ring) B C
1AA 00014 0004 (9007) A4 – ALICE 04.10
RN C,Rs B B C,Rs B C,Rs B
Figure 504. Dual “Events” Protection table (4F)
3AL 89062 AA AA 756 / 926
926
18.3.4 Main differences between 1660SM Rel.3.1/3.2/3.3 and 1670SM Rel.3.0
The new 1670SM Rel.3.0 equipment can transport high priority traffic on the working channels and low
priority traffic on the protection channels. The low priority traffics is lost when the protection channels have
to be used to protect the high priority traffic. Besides the 1670SM utilizes, in normal condition, the
Drop&Continue W (Working) channels while the 1664SM utilizes the Drop&Continue P (Protection)
channels. Only the 1670SM provides the Exercise external command while the new feature “Prot.
Unavailable” on 1664SM or “Prot. Failure” on 1670SM is common to both NEs.
The protection statuses visualized on the 1670SM have been simplified according to the ITU–T G.841
Rec.. A ring protection is automatically modified into a span protection when the span protection link has
been restored. In general “Intermediate” and “Pending” indications, at the same ring node, are substituted
with “Pending” ones; “Pending” and ”Served” indications, at the same ring node, are substituted with
“Served” ones (see para. 18.3.5. ).
– 1670SM Rel.3.0 Dual Exercise and Manual commands
The Exercise commands applied in the ring network scheme of Figure 500. simulate the bridge/switch
conditions according to the priority levels: exercise ring, exercise span, manual ring, manual span,.... In
Figure 505. has been reported dual command examples with exercise and manual commands. A similar
behavior would be found with “Force” or “Automatic protection” commands instead of manual.
Reference
point Exercise Manual
Other Span Ring Span Ring

points
SN R R R
SS AN R RsCs R R
Ring
RN RCs RsCs R,Cs R

SN R R R R
OS AN R R R R
Exercise
RN RCs RsCs R,Cs R

SN C R R
SS AN B C B R
RN B C,Rs B R
Span
SN B C B R
OS AN B C R R
RN B C,Rs B R
Figure 505. Examples of dual “Exercise” and “Manual” commands for 1670SM (4F)
Exercise span has a higher priority with respect to exercise ring, thus at the first column the results are:
R or RCs when exercise ring does not concern the same exercise span section (see Figure 522. ) or B
(both the commands are served) with dual exercise span commands that insist on different link sections
In the second column dual exercise ring commands are in pending (RsCs) or collapse into the same
command (R).
Manual span has a higher priority with respect to exercise: similar considerations valid for the first column
1AA 00014 0004 (9007) A4 – ALICE 04.10
can be applied to the third column.
Manual ring has a higher priority with respect to exercise then the result is R because it is not possible
to divide the ring in different link sections.
3AL 89062 AA AA 757 / 926
926
18.3.5 4F Protection Status Visualization
The protection statuses ring network indications are:

– 1 – Lockout Switching

– 2 – Forced Switching
– 3 – Automatic Switching ( MS–MSPRing protection for equipment/signal failure ).
– 4 – Manual Switching
– 5 – Idle ( regular operation without MS–SPRing protection )
These protection states are represented with the following color state boxes:
– Green: Active State, No Request condition.
– Red: Inactive State and any external or protection executed command ( that has been served ).
– Yellow: ordered but not executed command ( that has only been signalled= pending status ).
– Greyed: not available state box.
Automatic switching and external commands are revertive: then when the “Events” have been cleared
the MS–SPRing configuration comes back to its idle status.
The state boxes visualize the “Node Condition Request” as a consequence of the equipment/signal failure
or the external commands detected on the corresponding side (”Event”). The state boxes don’t describe
the protection actions provided on the NEs.
The served “Events” ( B/S=bridges and switches are executed and the network has been updated ) are
completed B/S actions visualized as red box indications
The signalled “Events” ( the K1/K2 protocol communicates to the network nodes what has happened )
are pending B/S visualized as yellow box indications.
Figure 506. visualizes the protection status with a served West manual ring command. The protection
status window is divided in different status fields: Schema description and status, Local Conditions, Node
Conditions and Protocol Exceptions. The first describes the network configuration and application type
and its status, the second gives the local external commands indications, the third the “Events” results
on the nodes and the fourth checks the k1/k2 ring protocol. The window is divided into three parts: West,
middle and East. On the West there are all the box indications corresponding to the West protections and
commands. In the middle “WTR–Ring” refers to West and East sides, “No Request” corresponding to “Idle
Status”, and “Intermediate Node” denotes that the protections and commands don’t concern the node
involved. Thus the Manual Ring command visualizes “Manual Ring” on the local node and “Request Node
Ring” in the “Local Conditions. The red color means that the command has been served. A regular protocol
“Exceptions” is represented with white boxes, a protocol alarm is signalled with red boxes.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 758 / 926
926
Figure 506. Protection Status with the Exercise Span command (4F)
Figure 507. reports the Protection Status for external “Force”, “Manual” and “Exercise Commands in a
3–node ring (A, B, C), Figure 508. shows the lockout statuses and Figure 509. the automatic protection
statuses.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 759 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Reference Force/Manual/Exer. Force/Manual/Exer. Force/Manual/Exer. Force/Manual/Exer.
node: A Ring W Ring E Span W Span E
A B C A B C A B C A B C
Force/ Force/ Force/ Force/

Local Conditions Manual Manual Manual Manual
Exercise Exercise Exercise Exercise
Ring Ring Span Span
W E W E
Request Request Request Request Request Request Request Request
Node Node Node Node Node Node Node Node
Node Conditions
Node
Node
Node
Node
Ring Ring Ring Ring Span Span Span Span

W E E W W E E W
Intermediate
Intermediate
Intermediate
Intermediate
W E W E W E
w w
w w
B p A p C
p p
926
3AL 89062 AA AA
Figure 507. Visualization of the Forced / Manual / Exercise protection Statuses (4F)
760 / 926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Reference Lockout Working Lockout Working Lockout Protection Lockout Protection
node: A Ring W Span W Span W Span E
Local Conditions
Lockout Lockout Lockout Lockout
Ring W Span W Prot W Prot E
Node Conditions
Node
Node
Intermediate
Intermediate
Prot. Failure
Prot. Failure
Prot. Failure
Prot. Failure
W E W E W E
w w
w w
B p A p C
p p
926
3AL 89062 AA AA
Figure 508. Visualization of the Lockout command Statuses (4F)
761 / 926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Reference Signal fail/degrade Signal fail/degrade Signal fail/degrade Signal fail/degrade
node: A Ring W Ring E Span Working W Span Protection W
Node Conditions Request Request Request Request Request Request

Ring Ring Ring Ring Span Span Prot. Prot.
W E E W W E Node Failure Failure
Node
Node
Node
Intermediate
Intermediate
Intermediate
Intermediate
W E W E W E
w w
w w
B p A p C
p p
firstly repairing the working link and after the protection one or vice versa
926
3AL 89062 AA AA
Figure 509. Visualization of Automatic Protection Statuses (4F)
The automatic protection and alarm clearing is visualized on Figure 510. The considered network failures
create on the adjacent nodes a tail–end/head–end node connection. The alarm clearing can be executed
762 / 926
Automatic Protection
Protection Working Working
Span Failure Ring Failure Span Failure
Alarm Clearing Alarm Clearing Alarm Clearing
”Prot. A B
Unavailable” on
adjacent
nodes + I A + WTR–ring B + WTR –S
After WTR time After WTR time
it comes back to it comes back to it comes back to
to the ”Idle” status the ”Idle” status the ”Idle” status
Figure 510. Automatic Protection and Alarm Clearing
Legend of Figure 510. :

A = “Request Node Ring” ( adjacent nodes ) + “I” ( remote nodes )
B = “Request Node Span” ( adjacent nodes ) + “I” ( remote nodes )
WTR = Wait Time to Restore
I = “Intermediate Node”: a remote node that does not serve a “Request Node Ring/Span”
Idle = “No Request” and “Active green indications only
A + WTR–Ring = If working span link is restored before the protection the status becomes “Idle”
without waiting the WTR time.
Reference point
clockwise
OS SN SS SN
1
W E
SS RN E W OS AN
2 4/6
W E W E
OS RN w w SS AN
w w
p 3/5 p
p p
SS RN OS RN
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 511. Dual “Events” Ring network reference scheme (4F)
3AL 89062 AA AA 763 / 926
926
In the reference scheme the adjacent node (AN) is the node connected to the reference point. The
adjacent node is the node 4/6 .
On 1664SM Rel.3.1/2/3 the NE nodes are named: 1=4_adm1, 2=4_adm2, 3=4_adm3,, 4=4_adm4.

On 1670SM Rel.3.0 the NE nodes are named: 1=1670_N1, 2=1670_N2, 5=1670_N5, 6=1670_N6.

OS RN SS RN OS SN SS SN OS AN SS AN
1 2 1 4/6
W E W E W E
2 2 1
4/6
W E W E W E
3 2 1 4/6
W E W E W E
4 2 1
4/6
W E W E W E
5 2 1 4/6
W E W E W E
6 2 1 4/6
W E W E W E
7 2 1 4/6
W E W E W E
8 2 1 4/6
W E W E W E
Figure 512. Considered cases on 1664SM /1670SM with different visualization statuses
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 764 / 926
926
Figure 512. shows eight cases where, considering the reference scheme of Figure 511. , there is a
different visualization statuses between 1664SM and 1670SM. Case 1 is similar to 4, case 2 is similar to
3, case 6 is similar to 7 and case 5 to 8. The same Protection Span failure indication is named “Prot.
Unavailable” on 1664SM and “Prot. Failure” on 1670SM.
– 1664SM Automatic Protection visualization statuses for dual ring failures
1664SM visualizes not only K1/K2 indications but also the incoming board alarm: then the “Request node”
pending and “Intermediate” indications can be shown at the same node.
The span protection failure turns on the “Prot. Failure “ indications on the adjacent nodes ( Figure 515. ).
Multiple span protection failures are always served and visualized as the couple of adjacent nodes
ADM1– ADM4 of Figure 515. The span working failure between ADM1 and ADM4 serves the “Request
Span” protection on the adjacent nodes ( Figure 516. ). When the working span failure is cleared the
WTR–S(span) box indication turns on (Figure 517. ): the previous automatic protection is frozen for the
WTR time. The operator can clear the WTR selecting “WTR” menu and the “Clear WTR” command. A
protection span failure and a working span failure on the same ADM side are equivalent to a ring failure
and hence served .
When there are a protection span failure and a ring failure on remote node ( RN ), the ring failure cannot
be served but only signalled ( Figure 518. ). With a working span failure and a ring failure the working span
protection has a higher priority with respect to the ring protection and only the working span is served
( Figure 519. ). Multiple ring failures are served ( Figure 520. ) but the isolation nodes can be only
signalled ( Figure 521. ).
Reference Automatic
point Protection Working

points
SN C Ring
SS AN R,Cs Node 4/6 isolated R,Cs
Ring
RN R,Cs B R,Cs
SN R,Cs Node 1 isolated R,Cs
OS AN C Ring Ring
Working
RN R,Cs Node 4/6 isolated R,Cs

SN Ring Ring
SS AN B C,Rs B 1
Automatic
RN B C,Rs B
Span
2
SN B C,Rs B 3
RN B C,Rs B 4
SS AN
B C,Rs B 5
Protection
RN B C,Rs B
Span
6
SN B C,Rs B 7
RN B C,Rs B 8
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 513. Automatic protection with double ring failures on 1664SM (4F)
3AL 89062 AA AA 765 / 926
926
Figure 513. resumes some of the common double ring failures. Ring , Working Span, Protection Span
failures have been considered as tail end / head end failures. The reference numbers 1, 2, 3 ...8 are related
to the cases of Figure 512.

Figure 513. failures are visualized as in the following:

B, C, R : “Request Node Ring/Span” on the adjacent nodes and “Intermediate Node” on the remote nodes
visualized as red boxes
Ring : Work. Span (Working Span) and Prot. Span (Protection Span); the two failures combine to a single
failure and a single protection. The Ring indication is visualized with red boxes as “Request Node Ring”
on the adjacent nodes and “Intermediate Node” on the remote nodes
Work. Span : “Request Node Span” on the adjacent nodes and “Intermediate Node” on the remote nodes
visualized as red boxes (Figure 516. ).
Prot. Span : “Prot. Unavailable” on the adjacent nodes and “Intermediate Node” on the remote nodes.
The last ones visualized as red boxes ( Figure 515. ).
Node 1 (4/6) isolated : the isolated node is visualized with two yellow “Request Node Ring” East and West
box indications, both the adjacent nodes with a red “Request Node Ring” box indication, the remote nodes
with the red “Intermediate Node” indication (see Figure 521. ).
Bs, Cs, Rs : “Request Node Ring/Span” on the adjacent nodes visualized as yellow boxes. The yellow
boxes are not visualized where is served Ring/Span” protection.
Working ring +working ring SS–RN are both served: “Request Node Ring” on the adjacent nodes
visualized as red boxes (see Figure 520. ).
In case of protection span failure + ring failure SS–RN the Protection span is only served : C,Rs (see
Figure 518. ).
Working ring + working span OS–SN : C,Rs (see Figure 519. ).
The same considerations can be applied for the visualization of dual generic “Events” of Figure 504.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 766 / 926
926
– 1670SM Rel.3.0 Automatic Protection visualization statuses
In multiple failures conditions the 1670SM does not utilize the board alarm indications but only the K1/K2
communication protocol. Then the visualized statuses are lightly different with respect to 1664SM.
Figure 514. reports the most common indications.

Reference Automatic
point Protection Working

points
SN C Ring
SS AN R,CMs Node B isolated R,CMs
Ring
RN R,Cs B R,CMs
SN R,CMs Node A isolated R,CMs
OS AN C Ring Ring
Working
RN R,CMs Node B isolated R,CMs

SN Ring Ring
SS AN B C,RMs B 1
Automatic
RN B C,RMs B
Span
2
SN B C,RMs B 3
RN B C,RMs B 4
SS AN
B C,RMs B 5
Protection
RN B C,Rs B
Span
6
SN B C,RMs B 7
RN B C,RMs B 8
Figure 514. Automatic protection for double ring failures on 1670SM (4F)
The reference numbers 1, 2, 3 ...8 are related to the considered cases of Figure 512. RMs and CMs note
the points where the span protection failure is served instead of the working ring one.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 767 / 926
926
18.3.5.1 1664SM Rel. 3.2 figures
N.B. All the protection status figures are applicable to 1664SM Rel. 3.3 but on this NE the three WTR
box windows have been moved in a different position and the “Prot Unavailable” has been

indicated as “Prot Failure”.

Figure 515. Protection Span failure between ADM 1 and ADM 4
The box color is white unless otherwise specified:
“Active” : green
1AA 00014 0004 (9007) A4 – ALICE 04.10
“Prot. Unavailable” ADM1–ADM4 : red
“Intermediate Node” ADM2–ADM3 : red
3AL 89062 AA AA 768 / 926
926
Figure 516. Working Span failure between ADM 1 and ADM 4
“Request Node Span” ADM4–ADM1 : red

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 769 / 926
926
Figure 517. Clearing of “Working Span failure” between ADM 1 and ADM 4
The WTR –S West box lights on red after having inserted the signal incoming on the ADM4 (working link).
If was first restored the signal incoming on ADM1 (working link) the ADM1–WTR–S East would be lighted
on.

1AA 00014 0004 (9007) A4 – ALICE 04.10
“Request Node Span” ADM4–ADM1 : red
ADM4 “WTR–S West” side : red
3AL 89062 AA AA 770 / 926
926
Figure 518. Protection span failure between ADM1–ADM2 plus ring failure between ADM4–ADM3
“Request Node Ring” ADM3 West side –ADM4 East side : yellow
“Prot. Unavailable” ADM1 West side and “Prot. Unavailable” ADM2 East side : red
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 771 / 926
926
Figure 519. Working span failure between ADM 1– ADM4 plus working ring failure between
ADM1–ADM2
According to ITU–T G.841 Rec. the pending “Request Node Ring” indication is not visualized on ADM1
node while the “Request Node Span” protection is served.
“Intermediate Node” ADM2–ADM3, “Request Node Span” ADM4–ADM1 : red

1AA 00014 0004 (9007) A4 – ALICE 04.10
“Request Node Ring” ADM2 East side : yellow
3AL 89062 AA AA 772 / 926
926
Figure 520. Ring failure between ADM1–ADM2 plus ring failure between ADM3–ADM4
“Request Node Ring” ADM1–ADM2 : red
“Request Node Ring” ADM3–ADM4 : red

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 773 / 926
926
Figure 521. Ring failure between ADM1–ADM4 and between ADM1–ADM2 (ADM1=isolation node)
“Request Node Ring” ADM4 West side, “Request Node Ring” ADM2 East side: red
“Request Node Ring” ADM1 West and East sides : yellow
“Intermediate” ADM3 : red

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 774 / 926
926
18.3.5.2 1670SM Rel. 3.0 figures
Exercise command examples

Figure 522. Exercise Span between 1670_N1–1670_N2 plus Exercise Ring between
1670_N6–1670_N5
Local condition: “Exercise Span”, 1670_N1 West side : red, “Exercise Ring”, 1670_N5 West side: yellow.
Node Conditions:
Exercise Span is priority with respect to Exercise Ring then “Request Node Span” 1670_N1 West side
1AA 00014 0004 (9007) A4 – ALICE 04.10
–1670_N2 East side : red
“Exercise Node Ring” West 1670_N5 –East 1670_N6 : Yellow
3AL 89062 AA AA 775 / 926
926
Figure 523. Double Exercise Span commands: between 1670_N1–1670_N2 and between
1670_N2–1670_N5
These double Exercise Span commands concern two different link sections then they are both served: B
Local condition: “Exercise Span” 1670_N1 West side : red ; “Exercise Span” 1670_N2 West side : red.
Node Conditions:
“Request Node Span” 1670_N1 West side – 1670_N2 East side : red
1AA 00014 0004 (9007) A4 – ALICE 04.10
1670_N6 Intermediate: red
3AL 89062 AA AA 776 / 926
926
Figure 524. Manual Span between 1670_N1–1670_N2 plus Exercise Ring between
1670_N5–1670_N6
Manual Span command is priority with respect to Exercise Ring one.
Local condition: “Manual Span” 1670_N1 West side : red, “Exercise Ring” 1670_N5 West side : yellow.
Node Conditions:
“Request Node Ring” 1670_N5 West side – 1670_N6 East side : yellow
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 777 / 926
926
Dual automatic protection failures examples
Case N1 of Figure 512. : Working ring plus Working Span =SS–AN failures. “Intermediate” indication on
1664SM disappears on 1670_N1

Figure 525. Ring failure between 1670_N1–1670_N6 plus Working span failure (SS–AN)
“Request Node Ring” 1670_N1 East side: yellow
1AA 00014 0004 (9007) A4 – ALICE 04.10
“Request Node Span” 1670_N6 East side, “Request Node Span” 1670_N5 West side : red
“Intermediate” 1670_N2 : red
3AL 89062 AA AA 778 / 926
926
Case N3 of Figure 512. : Working ring plus Working Span =OS–SN failures. Pending “Request Node Ring”
indication on 1664SM is substituted with Prot. Failure on 1670_N1 East side
Figure 526. Ring failure between 1670_N1–1670_N6 plus working span failure (OS–SN)
“Prot. Failure” 1670_N1 East side, “Prot. Failure” 1670_N6 West side : red
“Request Node Span” 1670_N1 West side, “Request Node Span” 1670_N2 East side : red
1AA 00014 0004 (9007) A4 – ALICE 04.10
“Intermediate” 1670_N5 : red
3AL 89062 AA AA 779 / 926
926
Case N4 of Figure 512. : Working ring plus Working Span =OS–RN failures. “Intermediate” with pending
“Request Node Ring” indications on 1664SM are substituted with pending one only.

Figure 527. Ring failure between 1670_N1–1670_N6 plus Working Span failure (OS–RN)
“Request Node Ring” 1670_N1 East side, “Request Node Ring” 1670_N6 West side : yellow
“Request Node Span” 1670_N5 East side, “Request Node Span” 1670_N2 West side : red
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 780 / 926
926
Case N5 of Figure 512. : Working ring plus Protection Span =SS–AN failures. “Intermediate” with pending
“Request Node Ring” indications on 1664SM are substituted with pending one only.
Figure 528. Ring failure between 1670_N1–1670_N6 plus Protection Span failure (SS–AN)
“Request Node Ring” 1670_N1 East side : yellow ; “Prot. Failure” 1670_N6 East side: red
“Prot. Failure” 1670_N5 West side: red

1AA 00014 0004 (9007) A4 – ALICE 04.10
“Intermediate” 1670_N2: red
3AL 89062 AA AA 781 / 926
926
Case N7 of Figure 512. : Working ring plus Protection Span =OS–SN failures. “Pending” “Request Node
Ring” indication on 1664SM is substituted with “Prot. Failure” on 1670_N1 East side.

Figure 529. Ring failure between 1670_N1–1670_N6 plus Protection Span failure (OS–SN)
“Prot. Failure” 1670_N1 West side, “Prot. Failure” 1670_N2 East side : red
“Prot. Failure” 1670_N1 East side, “Prot. Failure” 1670_N6 West side : red
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 782 / 926
926
18.3.6 Protocol Exceptions
The protocol error indications are three.

Wrong APS Code: the communication K1/K2 code works improperly. That is unexpected protocol signal
is received on the multiplex section protection links.
Node ID mismatch: the connection nodes don’t match the right identification sequence.
default K bytes: there is a wrong equipment/configuration provisioning and it is not possible to aim the
required MS–SPRing protection.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 783 / 926
926
18.4 MS–SPRING Protection Status – Commands for 2F Terrestrial Application
18.4.1 2F MS–SPRing protection commands

Click on the MS–SPRing pull down menu and select View Protection Status parameters. (the same
window opens from MS–SPRing –> ”Main Dialog for MS–SPRing management” and then Prot.
Commands). Figure 530. opens.
Figure 530. Protection states and commands “idle” status (2F).

1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. On 1664SM Rel. 3.3 the three WTR box windows have been moved in a different position and
the “Prot Unavailable” has been indicated as “Prot Failure”.
3AL 89062 AA AA 784 / 926
926
In the MSPRing 2 Fiber configuration, the 1–8 working channels are inserted into the 9–16 protection
channels in the opposite side of the failure event as shown in Figure 531.
W E W E
w/p w/p
A
w/p
X B
w/p
Ring Protection:
the working channels are substituted
by the ring protection channels ”p”
( B on East side )
( A on West side )
Figure 531. Ring Protection (2F)
18.4.2 External commands (2F)
The external protection commands are : Lockout, Force, Manual, Clear WTR.
The lockout commands disable the MS–SPRing management.
The lockout section presents four lockout commands ( Figure 532. ). Each lockout command is applicable
on different channels where the lockout actions have to be performed ( Figure 533. ) and any “Lockout
“ command is associated to a “Release” command to come back to the previous status.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 785 / 926
926
Figure 532. Lockout commands (2F)
West East
w w
p p
w A w
p p
Lockout Working–> 1–8 channels

Lockout Protecting–> 9–16 channels
Figure 533. Protection and working channels where the lockout command can be activated (2F)
The “Event/Events” served or signalled definitions mentioned for the 4–Fiber configuration can also
be applied for the 2 fiber configuration.
If the node is tail–end, the Lockout working ring command applied to this node disables the protection
MS–SPRing mechanisms. Otherwise if the node is head–end, it serves the request node protection (see
Figure 534. )
With the “lockout protection” command and a ring failure, the ring protection is served if the ring failure
has occurred along the same section ; the ring protection is disabled if the ring failure has occurred in
another ring section. With the “lockout working” command and a ring failure, the automatic ring protection
1AA 00014 0004 (9007) A4 – ALICE 04.10
is normally served (see Figure 535. ).
3AL 89062 AA AA 786 / 926
926
Lockout working
w/p
A
head w/p
W E failure
W
B
tail
E
ring protection
Lockout working failure

w/p
A
tail w/p
W E
W
B
head
E
no ring protection
Figure 534. Tail–end / head–end ring protection with a lockout working and a ring failure (2F)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 787 / 926
926
Lockout protecting
w/p failure
A
w/p

W E

W
B
E
ring protection
failure Lockout protecting
w/p
A
w/p
W E
E
C
W
no ring protection
Lockout working
w/p failure
A
w/p
W E
W
B
E
ring protection
Lockout working
w/p failure
A
w/p
W E
W Lockout working
B
E
no ring protection
failure Lockout working

w/p
A
w/p
W E
E
C
W
ring protection
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 535. Ring protection with a lockout and a ring failure (2F)
3AL 89062 AA AA 788 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
Lockout Working Lockout Working Lockout Protecting Lockout Protecting
01
Ring W Ring E Ring W Ring E
( Figure 538. ).
A Node A Node A Node A Node
Combinations
of non–served ”1” ”2”
ring protection on ring protection on
failures and the opposite side
external commands the opposite side
if the ring failure if the ring failure
occurs between occurs between
A–C or C–B nodes A–B or B–C nodes
W E W E W E
3 w/p 2 w/p
B A C
w/p 1 w/p 4
926
3AL 89062 AA AA
Figure 536. Lockout command and non–served failures (2F)
command disables the acknowledgment of the signal failure/degrade on the receiving ports.
Figure 536. shows a ring with three nodes and the actions performed by the lockout command. This
the working channels with the protection channels between two adjacent nodes on the opposite direction
The Force command ( Figure 537. ) executes a forced protection. The Force Ring command substitutes
789 / 926
Figure 537. Forced and Manual commands (2F)
Manual/force Ring East Manual/force Ring West
A A1 B1 B
W E W E
w1–8 W/P w1–8 w1–8 W/P w1–8
p9–16 p9–16 p9–16 p9–16
w1–8 W/P w1–8 w1–8 w1–8
p9–16 p9–16 p9–16 p9–16
W. 1–8 channels are substituted by P. 9–16 channels

on the opposite side for both adjacent nodes
Figure 538. Manual and Force commands (2F)
The Manual command is similar to Force command but it is at a lower priority level with respect to the
automatic MS–SPRing. The general priority scale that can be applied to solve antithetical situations
starting from the lowest priority level is: manual ring – automatic working ring – force ring – lockout
Working / Protection
When a force command is applied a next working failure, applied on a different section, modifies the forced
configuration. On the same section the priority is always respected even if sometimes only the protection
switching visualization is modified instead of the protection switching channels. This is because force
command has a higher priority with respect to the “Automatic” working protection . Vice versa the
1AA 00014 0004 (9007) A4 – ALICE 04.10
“Manual” protection is exceeded by the “Automatic” protection. Figure 539. visualizes the ring protection
with a Force/Manual command and a signal failure. FS–R is for “Force Switching Request”, SF–R is for
“Signal Failure Request”.
3AL 89062 AA AA 790 / 926
926
Force Ring East
w/p failure
A
w/p
W E
E W
C B
W E
ring protection for FS–R
failure Force Ring East

w/p
A
w/p ”A” node is isolated
W E
E W
C B
E
W
ring protection for SF–R and FS–R

Manual Ring East
w/p failure
A
w/p
W E
E W
C B
W E
ring protection for SF–R

failure Manual Ring East
w/p
A
w/p
W E
E
C
ring protection for SF–R

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 539. Ring Protection with Force and Manual commands (2F)
3AL 89062 AA AA 791 / 926
926
Signal fail/degrade Signal fail/degrade

Ring W Ring E

A node A node
B/S actions 1–2 w. channels are 3–4 w. channels are

sobstituted by 3–4 p. sobstituted by 1–2 p.
channels channels
W E W E W E
w/p w/p
1 4
B A C
w/p w/p
2 3
Figure 540. Automatic protection Bridge/Switch (2F)
Each command starts upon selecting the proper button. A dialog box ( Figure 541. ) has to be confirmed
before the command is performed.
A Release button is provided for each command to cancel the previously selected one and hence to come
back to normal MS–SPRing protection.
Figure 541. Example of confirmation dialog box (2F)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 792 / 926
926
Clicking on the WTR command, Figure 542. opens. If the WTR box in the Local Condition becomes red,
a waiting time has been activated after repairing the ring failure. The waiting time, set in the configuration
menu, can be cleared selecting the appropriate clear command. A confirmation dialog box opens and,
if the operator clicks OK, the WTR box turns off and the protection status window is updated.
Figure 542. Clear WTR commands (2F)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 793 / 926
926
18.4.3 2F MS–SPRing dual protection commands
In general dual contemporary “Events” can be:

two external commands

an external command and a ring failure
two contemporary ring failures
Dual “Events” can appear on the same side W/W (West/West) or E/E (East/East) (SS= same side) or on
the opposite side W/E or E/W (OS= opposite site) of the ring network. In the SS or OS the “Events” can
appear on the same node (SN) or on the different nodes (DN), the different node can be an adjacent node
(AN) or a remote node (RN). Figure 543. depicts a clockwise ring network . The network propagation
K1–K2 protocol signals are according to the following legend :
C = served the column element
R = served the row element
B = served both row and column elements
Cs = signalled (not served) the column element
Rs = signalled (not served) the row element
Bs = signalled (not served) both row and column element
when a command (Manual switch, Force switch) is neither served nor signalled, it is erased ( it is
not pending at the node)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 794 / 926
926
Reference point
clockwise
OS SN SS SN
W E
SS RN E W OS AN
4 2
E
W E W
OS RN w/p w/p SS AN
3
w/p w/p
SS RN OS RN
Figure 543. Ring network reference scheme (2F)
Figure 543. visualizes the ring reference scheme: the adiacent node (AN) is the node connected to the
reference point.
The automatic protection for dual ring failures is represented in Figure 545. Consider the network
reference scheme of Figure 544. with a tail–end / head–end alarm propagation. In this figure are depicted
the node switches for any reported double events.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 795 / 926
926
failure
w/p
1
w/p

W E

E W
4 2
E SS–AN
W E W
3 failure
failure
w/p
1
w/p
W E
E W
4 2
SS–RN
W E W E
3
failure
failure
w/p
1
w/p
failure W E
E W
4 2 OS–SN
W E W E
3
failure
w/p
1
w/p
W E
failure
E W
4 2 OS–AN
W E W E
3
failure
w/p
1
w/p
W E
E W
4 2 OS–RN
W E W E
3
failure
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 544. Examples of Double ring failure
3AL 89062 AA AA 796 / 926
926
Reference
point
Automatic Protection Ring
Other
points
SN
Automatic Protection Ring
Node 2 : isolated=Bs;Nodes 1–3 in switching for SF alarm=B;

AN Node 4=intermediate
SS
RN Nodes 1,2,3,4 in switching for SF alarm =B
SN Node 1 : isolated=Bs; Nodes 2,4 in switching for SF alarm=B; Node 3 =intermediate
AN Node 1,2 in switching for SF alarm =B, Nodes 3,4 = intermediate

OS
RN
Node 2:isolated=Bs; Nodes 1,3 in switching for SFalarm=B; Node 4 = intermediate
Figure 545. 2F Automatic protection (tail/head) for double ring failure visualization
The same reference Figure 543. and Figure 544. schemas are applied to describe dual generic “Events”
where both ring failures and external commands are considered.
The first row at the top of the protection table (Figure 546. ) shows the “Events” at the reference point. For
each of them the associated “Event” is listed on the first column at the left of the table.
Two manual ring commands can be only signalled: Bs (Manual SS–SN and OS–AN commands give the
same ring protection switching and then both can be served).
Two Lockout commands are both always served: B
Force command has priority with respect to the Manual one.
Automatic protection has priority with respect to the Manual command.
Force Ring and Automatic Protection (or two Force ring commands) are always served if they are not
applied on the SS–SN. In this last case has to be considered the priority level. The behavior is that seen
for two automatic protection switching ( Figure 544. )
Lockout working SS–SN has priority with respect to Manual, Automatic protection and Force commands.
In the other cases, both commands are served (B).
Lockout protecting SS–SN / OS–AN and Manual or Automatic or Force command are both served
because the switching SS–SN / OS–AN channels are not managed by the lockout protecting: B.
Lockout protecting SS–AN / OS–SN overrides the Manual or Automatic or Force command because the
lockout protecting controls the switching channels of the same Node.
Lockout protecting SS–RN / OS–RN and manual or automatic or force command: the lockout protecting
prevents the working 1–8 channels from being inserted into the protecting 9–16 ones. The lockout
protecting is served, because it has a higher priority, the ring protection will be only signalled (pending).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 797 / 926
926
Column
Reference Automatic
Row

point Force Lockout

Working

Manual
Other Ring Ring Ring Protection Working
points
SN R R B R
R R R
Manual Ring
SS AN Bs B
RN Bs R R RCs B
SN Bs R R R B
OS AN B R R B B
RN Bs R R RCs B
SN C C B R
SS AN C B B R B
Force Ring
RN C B B RCs B
SN C B B R B
OS AN C B B B B
RN C B B RCs B
SN C C C
Lockout Working
SS AN B B B
RN B B B B
SN B B B
OS
AN B B B
RN B B B
B B B
Lockout Protection
SN
SS AN C C C
RN CRs CRs CRs B
SN C C C
OS AN B B B
RN CRs CRs CRs
Figure 546. Tail / head dual “Events” Protection table (2F)

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 798 / 926
926
18.4.4 2F Protection Status Visualization
The protection statuses ring network are the same described for the MSPRing 4 Fiber configuration. They
are:
– 1 – Lockout Switching
– 2 – Forced Switching
– 3 – Automatic Switching ( MS–MSPRing protection for equipment/signal failure ).
– 4 – Manual Switching
– 5 – Idle ( regular operation without MS–SPRing protection )
These protection states are represented with the following color state boxes:
– Green: Active State, No Request condition.
– Red: Inactive State and any external or protection executed command ( that has been served ).
– Yellow: ordered but not executed command ( that has only been signalled= pending status ).
– Greyed: not available state box.
Automatic switching and external commands are revertive: then when the “Events” have been cleared,
the MS–SPRing configuration comes back to its idle status.
The state boxes visualize the “Node Condition Request” as a consequence of the equipment/signal failure
or the external commands detected on the corresponding side (”Event”). The state boxes don’t describe
the protection actions provided on the NEs.
The served “Events” ( B/S=bridges and switches are executed and the network has been updated ) are
completed B/S actions visualized as red box indications
The signalled “Events” ( the K1/K2 protocol communicates to the network nodes what has happened )
are pending B/S visualized as yellow box indications.
Figure 547. shows the protection status with a served East manual ring command. Any protection status
window is divided in different status fields: Schema description and status, Local Conditions, Node
Conditions and Protocol Exceptions. The first one describes the network configuration and application
type and its status, the second gives the local external commands indications, the third the “Events” results
on the nodes and the fourth one checks the k1/k2 ring protocol. The window is divided into three parts:
West, Middle and East. On the West there are all the box indications corresponding to the West protections
and commands. In the middle “WTR–Ring” refers to West and East sides, “No Request” corresponding
to “Idle Status”, and “Intermediate Node” denotes that the protections and commands don’t concern the
node involved. The Manual Ring command visualizes “Manual Ring” on the local node and “Request
Node Ring” in the both “Local Conditions adiacent East ADM1–West ADM2 nodes, while the 3 and 4
nodes are “Intermediate Node”. The red color means that the command has been served. A regular
protocol “Exceptions” is represented with white boxes, a protocol alarm is signalled with red boxes. The
“Prot. Unavailable” indications are activated when a lockout protection command is applied in a network
node.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 799 / 926
926
Figure 547. Manual command applied at the “Reference Point” ring network (Figure 543. )
Figure 548. reports the “Protection Status” for external “Force and “Manual” commands in a 3 –node ring
(A, B, C). Figure 549. shows the lockout statuses and Figure 550. the automatic protection statuses.
N.B. On 1664SM Rel. 3.3 the three WTR box windows have been moved in a different position and
the “Prot Unavailable” has been indicated as “Prot Failure”.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 800 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Reference Force/Manual Force/Manual
node: A Ring W Ring E
A B C A B C
Local Conditions Force/ Force/

Manual Manual
Ring Ring
W E
Request Request Request Request
Node Node Node Node
Node Conditions
Node
Node
Ring Ring Ring Ring

W E E W
Intermediate
Intermediate
W E W E W E
w/p w/p
B A C
w/p w/p
926
3AL 89062 AA AA
Figure 548. Visualization of the Forced / Manual protection Statuses (2F)
801 / 926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Reference Lockout Working Lockout Working Lockout Protecting Lockout Protecting
node: A Ring W Ring E Span W Span E
Local Conditions
Lockout Lockout Lockout Lockout
Ring W Ring E Prot W Prot E
Node Conditions
Node
Node
Intermediate
Intermediate
Prot. Unavailable
Prot. Unavailable
Prot. Unavailable
Prot. Unavailable
W E W E W E
w/p w/p
B A C
w/p w/p
926
3AL 89062 AA AA
Figure 549. Visualization of the Lockout command Statuses (2F)
802 / 926
Request
Reference Signal fail/degrade Signal fail/degrade
Ring
W
C
Ring E
Node
B
Intermediate
W
Request
Ring
w/p
E
A
w/p
Node
E
C
Intermediate
A
Request
Ring W
Ring
B
W
Request
w/p
w/p
Ring
A
W
Node Conditions
E
node: A
B
W
Figure 550. Visualization of Automatic Protection Statuses (2F)
The WTR status is visualized on the side where the link has been repaired. The considered network
failures are related to a tail–end/head–end node connection. The “WTR Clear” command can be executed
by the user without waiting the WTR setting time.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 803 / 926
926
18.4.4.1 Double ring failure
The double ring failure visualization of Figure 544. are here following reported.

N.B. All the protection status figures are applicable to 1664SM Rel. 3.3 but on this NE the three WTR

box windows have been moved in a different position and the “Prot Unavailable” has been
indicated as “Prot Failure”.
Figure 551. Protection status with double ring failure (reference point––SS–AN)
Figure 551. reports the protection status with double ring failure (reference point––SS–AN. The node 2
isolated, the nodes 2–3 in switching and the node 4 Intermediate. The box color is white unless otherwise
specified:
1AA 00014 0004 (9007) A4 – ALICE 04.10
“Active”: green
“Request Node Ring” West ADM3–East ADM1: red (served)
“Request Node Ring” West ADM2–East ADM2: yellow (pending); “Intermediate Node” ADM4: red
3AL 89062 AA AA 804 / 926
926
Figure 552. Protection status with double ring failure (reference point––SS–RN)
Figure 552. reports the protection status with double ring failure (reference point––SS–RN). The nodes
1,2,3,4 are being switched for signal failure alarm and both the two signal failures are served. The box
color is white unless otherwise specified:
“Active”: green
“Request Node Ring” East ADM3–East ADM1: red (switching for SF)
“Request Node Ring” East ADM4–East ADM2: red (switching of the opposite nodes)
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 805 / 926
926
Figure 553. Protection status with double ring failure (reference point––OS–AN)
Figure 553. reports the protection status with double ring failure (reference point––OS–AN). The nodes
1,2 are being switched for signal failure alarm and both signal failres are served: B. The box color is white
unless otherwise specified:
“Active”: green
“Request Node Ring” West ADM2–East ADM1: red (switching for SF)
“Intermediate Node ” ADM3–ADM4: red
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 806 / 926
926
Figure 554. Protection status with double ring failure (reference point––OS–AN) recovering to “idle”
Figure 554. reports the previous protection status with double ring failure (reference point––OS–AN)
while the ring protection comes back to its “idle” status. The “WTR (Wait To Restore) Ring” on ADM1 node
becomes red to signal that the SF disappears at the “reference point” . The box color is white unless
otherwise specified:
“Active”: green
“WTR Ring” : red (to signal the SF recovering)
“Request Node Ring” West ADM2–East ADM1: red
“Intermediate Node ” ADM3–ADM4: red
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 807 / 926
926
18.4.4.2 Double external command or an external command and a ring failure
Some more significative double events of Figure 546. are here following reported.

Figure 555. Double manual ring command (reference point––SS–AN)
Figure 555. reports the protection status with double manual command (reference point––SS–AN). Both
the commands can be only pending. The “Request ring” to 1,2,3 nodes becomes pending while the 4 node
is “Intermediate node”. The box color is white unless otherwise specified:
“Active”: green
1AA 00014 0004 (9007) A4 – ALICE 04.10
“Request Node Ring” East ADM1– West ADM2: yellow ( pending ) for Manual Ring East ADM1
“Request Node Ring” East ADM2– West ADM3: yellow ( pending ) for Manual Ring East ADM2
“Request Node Ring” West ADM1– East ADM3: yellow ( pending ) for switching of the opposite nodes
“Intermediate Node ” ADM4: red
3AL 89062 AA AA 808 / 926
926
Figure 556. Double manual ring command (reference point––OS–AN)
Figure 556. reports the protection status with double manual command (reference point––OS–AN). Both
the commands can be served. The “Request Manual ring” to ADM1 (East) and to ADM2 opposite side
(West) collapses in the same manual command. Both the manual commands are served. The box color
is white unless otherwise specified:
“Active”: green
“Request Node Ring” East ADM1– West ADM2: red ( served )
“Intermediate Node ” ADM3, ADM4: red
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 809 / 926
926
Figure 557. Manual ring and Lockout Protection (reference point––SS–SN)
Figure 557. reports the protection status with a manual command and a lockout protection (reference
point––SS–SN). Both the manual and the lockout commands are visualized to the same ADM1 node
(East). Both the commands are served because the bridge/switch points are different. The box color is
white unless otherwise specified:
“Active”: green
“Request Node Ring” East ADM1 – West ADM2: red ( served )
“Intermediate Node ” ADM3, ADM4: red
“Manual Ring and Lockout Prot.” commands East ADM1: red
1AA 00014 0004 (9007) A4 – ALICE 04.10
“Prot. Unavailable” East ADM1 : red .
N.B. The “Prot. Unavailable” is not propagated on West ADM2 node because on West ADM2 the
protection switching has been executed.
3AL 89062 AA AA 810 / 926
926
Figure 558. Manual ring and Lockout Protection (reference point––SS–RN)
Figure 558. reports the protection status with a manual command and a lockout protection (reference
point––SS–RN). The manual command is pending while the lockout command is served. The box color
“Active”: green
“Manual Ring” command East ADM1: yellow
“Request Node Ring” East ADM1 – West ADM2 : yellow ( pending )
“Request Node Ring” West ADM1 – East ADM2 : yellow ( pending ) for switching of the opposite nodes
“Lockout Prot.” command: East ADM3 : red
1AA 00014 0004 (9007) A4 – ALICE 04.10
“Prot. Unavailable” East ADM3 and West ADM4: red (served)
3AL 89062 AA AA 811 / 926
926
Figure 559. Automatic working ring and Manual Ring (reference point––OS–AN)
Figure 559. reports the protection status with a ring failure and a manual ring command (reference
point––OS–AN). The automatic protection has a higher priority with respect to the manual command and
then it has been served. The box color is white unless otherwise specified:
“Active”: green
“Request Node Ring” East ADM1 – West ADM2 : red (served)
“Intermediate Node” ADM3 – ADM4 : red
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 812 / 926
926
Figure 560. Automatic working ring and Force Ring (reference point––SS–AN)
Figure 560. reports the protection status with a ring failure and a force ring command (reference
point––SS–AN). The ADM2 is isolated and the force command is pending. The box color is white unless
otherwise specified:
“Active”: green
“Request Node Ring” East ADM1: red (served) the West ADM1 switching is applied for SF
“Request Node Ring” West ADM3: red (served) the East ADM3 switching is applied for the force command
“Request Node Ring” West ADM2, East ADM2: yellow (pending) the ADM2 is isolated
“Intermediate Node” ADM4 : red
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 813 / 926
926
Figure 561. Automatic working ring and Lockout working Ring (reference point––SS–SN)
Figure 561. reports the protection status with a ring failure and a lockout working command (reference
point––SS–SN). The Lockout command has a higher priority with respect to the automatic protection
switching and then only the lockout command has been served. The box color is white unless otherwise
specified:
“Active”: green
“Lockout Ring” command East ADM1: red
“Request Node Ring” East ADM1 – West ADM2 : red (served)
“Intermediate Node” ADM3 – ADM4 : red
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 814 / 926
926
Figure 562. Automatic working ring and Lockout Protection (reference point––OS–RN)
The lockout protection has a higher priority with respect to the automatic ring protection. The box color
“Active”: green
“Lockout Prot.” command West ADM3: red
“Prot. Unavailable” West ADM3 – East ADM2 : red (lochout protection is served)
“Request Node Ring” East ADM1 – West ADM2 : yellow (automatic protection is pending)
“Intermediate Node” ADM4 : red
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 815 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
816 / 926
19 MS-SPRING MANAGEMENT FOR OMSG
19.1 Introduction
MS-SPRing (Multiplex Section - Shared Protection Ring) is one of the Network protections defined for a
SDH network.
There exist two variants of MS-SPRing:
– one called the classic application
– the other one called the transoceanic application.
Additionally either 2-fiber or 4-fiber rings supporting MS-SPRing are known.
In the current release, the 2-fiber classic MS-SPRing at STM-16 is supported. The supported MS-SPRing
is compliant to the ITU-T Recommendation G.841.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 817 / 926
926
Figure 563. 2-Fiber MS-SPRing
A 2-fiber MS-SPRing consists of a set of NEs each equipped with two bidirectional ports, one for the clock-
wise and the other for the counter-clockwise. The MS-SPRing is called “2-fiber”, because each pair of adja-
cent NEs is linked by two fibers, one transporting the traffic in the western direction and the other one trans-
porting traffic in the eastern direction (in other words one in a direction and the other in the opposite direc-
tion). The stretch between two adjacent nodes in the ring is called span.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 818 / 926
926
On each fiber, half of the channels are used as working channels and half of the channels are used as
protection channels. Under normal conditions, the normal traffic is transported over the working channels
only. In case of failure or external request, the normal traffic is bridged and switched to the protection chan-
nels going on the opposite direction (even in case of unidirectional failure, both directions are switched
to the protection channels). Therefore, all spans share the protection capacity of the ring.
In general, up to 64 nodes may be part of a MS-SPRing, but in the current release only 2-fibre classic MS-
SPRing is supported, so maximum 16 nodes are possible.
For the ring protection mechanism the APS (Automatic Protection Switching) protocol is used; this protocol
is transmitted by the K1 and K2 bytes in the multiplex section overhead (MSOH).
N.B. To use the STM-16 board for MS-SPRing the accordingly shelf has to be configured as pro-
tected.
N.B. Extra traffic or non preemptible unprotected traffic is not supported in the current release.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 819 / 926
926
19.2 Create/Delete MS-SPRing
19.2.1 Navigation

From each other View, the MS-SPRing is reachable via:
Views
Previous
Room
MS–Spring
Equipment Overview
Transmission
Synchronization
Open Object
Open in Window
Refresh
Close
Exit
From Port/Transmission View for a port involved in an MS-SPRing scheme, select the MS-SPRing TTP
and via:
Port/Transmission
...
Navigate to Msspring View
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 820 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
19.2.2 Create MS-SPRing
A single dialog, accessible via
Figure 564. Default Mode of MS-SPRing
926
3AL 89062 AA AA
821 / 926
MS-SPRing
Management

enables to perform management operations and execute external MS-SPRing commands.
After clicking on Management the MS-SPRing Management appears (see Figure 565. ).
Figure 565. MS-SPRing Management
Clicking on Create... in the MS-SPRing Management (see Figure 565. ) opens a creation wizard, where
you have to facilitate the configuration of the main parameters (ring map and squelching table).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 822 / 926
926
19.2.2.1 First Step: Application Configuration and Port Selection
Figure 566. Ring Parameter Configuration
The ring parameter configuration is valid for one node.
Meaning of the parameters:
– Application
• Classic
• Transoceanic (not available with the current release)
– Architecture
• 2-Fiber
• 4-Fiber (not available with the current release)
– Port Selection
You can enter the MSTTP of the port in the entry field or click on Choose Port to get a list of all avail-
able MSTTPs of the ports. Select a MSTTP and either click OK to perform the selection and return
to the Ring Parameter Configuration dialog or drag the selected MSTTP from the Port/ Transmis-
sion view and drop it in the Protected West field.
1AA 00014 0004 (9007) A4 – ALICE 04.10
N.B. It does not matter if the protected or protecting unit (for the same MSP Group) is selected. The
fields for the Port Selection are then automatically set so that:
MSP protected is configured for the West side (protected port west) and
MSP protecting is configured for the East side (protected port east).
3AL 89062 AA AA 823 / 926
926
N.B. The port that will be involved in the creation of the scheme should be:
– structured on AU4-level/not terminated to lower level
– not involved in cross-connections
– on a board set in service.

Otherwise an error message will be displayed.

19.2.2.2 Second Step: Ring Map
The ring map configuration is valid for the whole MS-SPRing. Therefore it has to be unique on all nodes.
In the Ring Parameter Configuration dialog click Next > to configure the Ring Map in the Ring Map Con-
figuration dialog (see Figure 567. ).
Figure 567. Ring Map Configuration
The ring map specifies the topology of the protection ring:
– It is a table that contains all nodes within the ring.
– The topology is implicitly given by the position of the node inside this table.
The ring map configuration is mandatory.
The ring map sets the connection sequence of the nodes within the ring.
Enable the Change Node Id button and enter the Current Node Id (the NE where the operator is acting)
in the field.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Select Available Node Id in the pull down list (0 to 15). The selected Available Node Id will be displayed
after clicking on Add Node.
3AL 89062 AA AA 824 / 926
926
The ring map table has two rows:
– Pos. representing the position of a node in the ring going counterwise without gap.
– Node Id representing the identifier of the node. (If nothing is defined, the default value is N/A.)
The following example shows the ring topology in case of four nodes with the Node Ids 1, 2, 3 and 4.
Example:
Ring Topology:
Node Ids inserted in the ring map:
<= West East =>

Network Element Network Element Pos.: 0123
(node) 1 (node) 2 Node Id: 1234
Network Element Network Element

(node) 4 (node) 3
Different possibilities to insert or remove Node Ids:
1) If nothing is selected in the ring map itself, just select an Available Node Id and click on Add
Node, the Node Id will be automatically inserted under the Pos. 0 (replacing N/A), and each
time you click on the button after selecting a new Available Node Id, it will be inserted under
the next Pos. on the right (1, 2, 3, ...)
2) You can select a position in the table and choose an Available Node Id. When clicking on the
Add Node button, the Node Id will be inserted under the Pos. you have selected.
To insert another Node Id, you must select another position and repeat the same procedure.
3) To remove a Node Id from the table, select the corresponding position and click on the Remove
Node button: the default value N/A reappears, the Node Id is set back in the list of available
Node Id.
N.B. Because of an incorrect configuration the creation wizard won’t go to the next step :
– It is not possible to enter a Node Id in the field
if this Node Id is not defined in the ring map
– The Node Id cannot be bigger than 15 (range
from 0 to 15).
Click Next > to configure the Squelch Table (see Figure 568. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
19.2.2.3 Third Step: Squelch Table
The Squelch Table is needed to avoid trouble in case of node isolation.
3AL 89062 AA AA 825 / 926
926
The Squelch Table Configuration is optional, but all existing configurations must match with the other ones.

Figure 568. Squelch Table Configuration
The table for each side, West and East consists of a listbox with five columns:
– AU4
the channel number
– RX (input) Source
Source Node Id of the signal received by this port
– RX (input) Dest.
Destination Node Id of the signal received by this port
– TX (output) Source
Source Node Id of the signal transmitted by this port
– TX (output) Dest.
Destination Node Id of the signal transmitted by this port
Define for each connection installed as Source the node identifier of the node generating the considered
AU4 and as Destination (Dest) the node identifier of the node terminating the AU4. The definition must
be performed for the West and East side.
N.B. It is only possible to configure the first 8 AU4s. AU4 #9 to #16 must not be used for connections
1AA 00014 0004 (9007) A4 – ALICE 04.10
nor considered in any parameter for Squelching Table provisioning.
N.B. After having finished all entries in the Squelch Table, click on a free cell or press Return on the
keyboard to save all entries.
3AL 89062 AA AA 826 / 926
926
Click Next > to finish the MS-SPRing creation. A message informs you about the correct configuration of
all necessary parameters (see Figure 569. ).
N.B. The WTR time is set per default to 300 seconds at the creation of a scheme. It is possible to
change the WTR time (see chapter 19.4.4).

Figure 569. Finish Message
Click Finish to start the creation process. After successful execution of the creation process, the MS-
SPRing Management dialog shows the created MS-SPRing. An example is given in Figure 570. .
After finishing the creation the MS-SPRing is not activated automatically. The activation has to be per-
formed by the operator after configuring all nodes for MS-SPRing.
N.B. The MS-SPRing configuration includes the creation of the pass-through connections on all
nodes, where the traffic is transferred. These connections have to be created via the cross-con-
nection management for the accordingly AU4 containers from the protected port west to the pro-
tected port east.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 827 / 926
926
Figure 570. Example of created MS-SPRings
The upper part of the dialog presents the list of existing MS-SPRing schemes.
Meaning of the columns:
– Name
The name of the MS-SPRing (short form of the the Protected Port West)
– Type
The type of the MS-SPRing. In the current release, only 2-Fiber Classic Type is possible
– Status
• Active
The scheme is active means that the protection commands can be executed, a switch can be
performed.
• Enabled
The scheme is not active means that the protection protocol is not running yet, no switch can
be performed, no protection commands can be executed.
– Protected (W)
The name of the Protected Port West
– Protected (E)
The name of the Protected Port East
The default state after creating the MS-SPRing is “Enabled” to ensure that all involved nodes are config-
ured before activating the MS-SPRing.
1AA 00014 0004 (9007) A4 – ALICE 04.10
19.2.3 Delete MS-SPRing
Select the ring to be deleted from the MS-SPRing Management dialog (see Figure 571. ).
3AL 89062 AA AA 828 / 926
926
Figure 571. Example for deletion of a MS-SPRing
If the selected ring is in “Active” Status, first deactivate the ring. Only enabled rings can be deleted.
If the selected ring is in Status “Enabled”, click Delete to remove the ring.
The deleted MS-SPRing automatically disappears from the MS-SPRing Management list, if the operation
was successful.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 829 / 926
926
19.3 Activate/Deactivate MS-SPRing
To enable the protection mechanism, the MS-SPRing has to be activated. It should be done for all created
schemes. To activate a scheme, select it in the MS-SPRing Management dialog and click the Activate

button. Afterwards the status of the selected scheme should be updated to “Active”.

N.B. Before activating a MS-SPRing node, it must be configured to distribute the knowledge about
the ring topology and cross-connection configuration to the node. The ring map had to be config-
ured during the creation, but it can be changed via the Ring Map Configuration dialog (see
Figure 573. ). The squelch table configuration was not mandatory during the creation but can
be configured afterwards via the Squelching Table Configuration dialog (see Figure 574. ).
To disable the protection mechanism (without deleting a MS-SPRing scheme), the MS-SPRing has to be
deactivated. By clicking on the Deactivate button in the MS-SPRing Management dialog, the status of
the selected scheme should be updated to “Enabled”. The protection protocol is not running any more and
no switch is possible.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 830 / 926
926
19.4 Modify MS-SPRing
From the MS-SPRing Management dialog select the ring to be modified (see Figure 572. ).
Figure 572. Example for Different Modifications of a MS-SPRing
19.4.1 Ring Traffic Modification
The configuration of the Ring Traffic... is only supported for 4-fiber transoceanic MS-SPRing and there-
fore not supported in the current release (button always insensitive).
19.4.2 Ring Map Modification
For modification of the Ring Map click Ring Map.... The MS-SPRing Ring Map Configuration dialog
opens for the selected ring (for an example see Figure 573. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 831 / 926
926
Figure 573. Example for Modification of Ring Map Configuration
It is possible to modify the topology of a ring map in the same way as described in Chapter 19.2.2.2.
Selecting OK saves the modifications for the selected ring and closes the dialog. Cancel discards the
modifications and closes the dialog.
19.4.3 Squelching Table Modification
Modification or creation of a Squelch Table can be performed by clicking on Squelching... The squelching
table of the selected ring is displayed (for an example see Figure 574. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 832 / 926
926
Figure 574. Example for Modification of Squelching Table
It is possible to modify the transmission running through the MS-SPRing in the same way as described
in Chapter 19.2.2.3.
19.4.4 Wait to Restore Time Modification
For modification of the Wait to Restore (WTR) Time click WTR.... The MS-SPRing WTR Time Configura-
tion dialog opens for the selected ring (for an example see Figure 575. ).
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 833 / 926
926
Figure 575. Example for Modification of WTR Time Configuration
The default value for a new ring is 300 seconds WTR Time Ring. It can be changed from 0 to 720 seconds
by clicking the up/down arrows in 60 seconds step values.
N.B. The same WTR Time Ring must be set on each node of the ring.
The modification of WTR Time Span West and WTR Time Span East is not supported in the current relea-
se.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 834 / 926
926
19.5 Display MS-SPRing
19.5.1 Display MS-SPRing in MS-SPRing view

In the MS-SPRing Management dialog click Display selected ring in view to see the ring in the MS-
SPRing view.
The MS-SPRing view layout is separated in 2 parts:
1) Upper part:
logical representation of the current state of traffic flows between the East and West side. The
MS-SPRing block represents the sum of unprotected CTPs and protected TTPs on all west and
east boards participating in the protection scheme. For 2-fiber classic application, the traffic in
both directions is displayed by arrows in different directions (in each direction with different col-
or).
2) Lower part:
a set of current MS-SPRing states (Protection States) and the protocol exceptions (Protocol ex-
ceptions) are displayed. For a detailed description, refer to Chapters 19.6.3 and 19.6.4.
In the default mode (no MS-SPRing scheme selected, no navigation from Port or Transmission view), no
arrows are displayed, all states are greyed. The different colors of the protection states are explained in
Chapter 19.6.3.
An example for an existing MS-SPRing is given in Figure 576. .
Figure 576. Example of a MS-SPRing view

1AA 00014 0004 (9007) A4 – ALICE 04.10
A detailed description of the status can be found in chapter 19.6.
3AL 89062 AA AA 835 / 926
926
19.5.2 Display MS-SPRing in Transmission view
It is also possible to see the MS-SPRing in the Transmission view. An example is given in Figure 577. .

Figure 577. Example of a MS-SPRing in Transmission View
After configuring MS-SPRing the 16 AU4 containers are separated to 8 AU4 containers related to the pro-
tected port west and 8 AU4 containers related to the protected port east. In the Transmission view 8 AU4
containers are visible on both of them.
19.5.3 Display MS-SPRing in Port view
An example for a MS-SPRing in Port view is given in Figure 578. .

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 836 / 926
926
Figure 578. Example of a MS-SPRing in Port View
After configuring MS-SPRing the 16 AU4 containers are separated to 8 AU4 containers related to the pro-
tected port west and 8 AU4 containers related to the protected port east. In the Port view 8 AU4 containers
are visible on both of them.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 837 / 926
926
19.6 Protection States and Commands for 2-Fiber Classic MS-SPRing
19.6.1 Node States Representation

After creating and activating MS-SPRing the traffic should run only via the protected channels.
The node is in “Idle” state.
In the MS-SPRing view the field No Request is green on West and East side. On the upper part, the arrows
represent the traffic carried only over the protected channels from East to West and inverse.
This state can be changed through the following:
– externally initiated commands can be performed via the “User Commands” dialog on the West or the
East side of a MS-SPRing scheme.
– automatically initiated commands can be initiated according to the protection protocol when a failure
occurs in the ring (i.e. fiber cut, degraded signal, ...)
The MS-SPRing commands can lead to two kinds of switch: a ring switching and a span switching.
– During ring switching the normal traffic from the affected span is carried over to the protection channel
on the long path.
For example, there are 4 nodes in a ring: 1, 2, 3 and 4. A ring switch is performed on the West side
of node 1, the affected span is the span on West side of node 1, which is the span between the node
1 and node 2. The normal traffic on this span is switched on West side of node 1 and East side of
node 2 so that: the normal traffic will be carried from the protected channels on East side of node 1
over the protection channels on East side of node 1 so on the opposite direction. On node 2 it is the
inverse: the normal traffic is carried over the protection channels on West side.
– During span switching the normal traffic is carried over to the protection channels on the same span.
It is similar to linear MSP but applies only on 4-fiber MS-SPRing, which is not supported in the current
release.
N.B. Because 4-fiber MS-SPRing is not supported, the states corresponding to span switching
types are kept inactive and in the Management dialog (Span West... and Span East...).
When a MS-SPRing command leading to a switch (Forced, Manual, Automatic switch to SF or SD) was
initiated on a non-adjacent node, on the node observed no ring switch is performed but the protection
channels are used: the node is in “Pass-through” state. The upper part of MS-SPRing view is updating
the representation of the traffic flow: additionally to the arrows present, arrows lines directly joining the
protecting units are representing the traffic carried in addition over the protecting channels.
When the node is not in the “idle” nor the “pass-through” state, then it is in the “switching” state. And there
are two possibilities:
1) If the state is completed (the ring switch has been performed), the MS-SPRing view is updating
the representation of the traffic flow: the ring switch is logically represented so that the normal
traffic is carried over the protecting channels on the opposite direction. The state corresponding
to the command initiated is red.
2) If the state is pending (the ring switch cannot be performed), the MS-SPRing view is staying in
the Idle state: the traffic cannot be switched over the protection channels. The state(s) corre-
1AA 00014 0004 (9007) A4 – ALICE 04.10
sponding to the command(s) initiated is (are) yellow.
3AL 89062 AA AA 838 / 926
926
19.6.2 Externally Initiated Protection Commands
As said in the former section, only ring commands are available in this release.
To perform a command, click in the MS-SPRing Management dialog on the Ring, West... or Ring, East...
button depending on which side of the scheme the command should be performed (for an example see
Figure 579. ).
Figure 579. Example for MS-SPRing Protection Commands
The following commands are available:
– Clear WTR
– Manual to
– Force to
– Lockout Ring
– Lockout Span
To perform a command, select the corresponding radio button and click on Apply (without closing the dia-
log) or OK (the dialog will be closed). To release a former executed command, select the Release radio
button of the command and click on Apply (without closing the dialog) or OK (the dialog will be closed).
As long as a command was not performed, the Release radio button is insensitive. When a command is
1AA 00014 0004 (9007) A4 – ALICE 04.10
not available, because a command with higher priority was already performed, the corresponding radio
button is also insensitive.
The description of the externally initiated commands is listed in descending order of priority:
3AL 89062 AA AA 839 / 926
926
Lockout Span (Lockout of Protection – Span)
It prevents the usage of the span situated on the side where the command is performed (West –> West
span / East –> East span) for any protection activity and prevents using ring switches in that span. All lower

priority states or commands for that span will be dropped.

Lockout Ring (Lockout of working channels – ring switch)
It prevents that a ring switch is performed on the side where the command is performed. This command
has no impact on the use of protection channels for any other span in the ring: so for example, the node
can go into the pass-through mode.
For proper operation of this command, it should be performed on both sides of the span (for example: East
side of one node and West side of the adjacent node).
Force to (Forced switch to protection – ring)
It performs the ring switch of normal traffic from working channels to the protection channels for the span
on the side where the command was initiated. This switch is executed regardless of the state of the protec-
tion channels, unless they are satisfying a higher priority switch request.
The accordingly protection state is illustrated in Figure 580. .

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 840 / 926
926
Figure 580. Example of a “Forced Switch to Protection – Ring”
19.6.2.1 Manual to (Manual switch to protection – ring)
It performs the ring switch of normal traffic from working channels to the protection channels for the span
on the side where the command was initiated. This switch is executed regarding the state of the protection
channels, unless they are satisfying a higher priority switch request.
The accordingly protection state is illustrated in Figure 581. .

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 841 / 926
926
Figure 581. Example of a “Manual Switch to Protection – Ring”
19.6.2.1.1 Clear WTR
This command is available only if the WTR condition is present. It clears the WTR state so that the switch
back to the protected channels is performed immediately and is not waiting until the WTR time expires.
19.6.2.1.2 Release...
The commands Release Force to, Release Manual to and Clear WTR can only be executed on the node,
1AA 00014 0004 (9007) A4 – ALICE 04.10
which is the source of the request (local).
3AL 89062 AA AA 842 / 926
926
19.6.3 Protection State Representation
For each side, West and East, there are the following switch states (see Figure 581. ):
– General:
• No Request:
normal situation (no use of the protection channel)
• Lockout Prot:
a Lockout of Protection-Span was performed locally on this side
• Prot. Unavailable:
The protection is not possible because of a Lockout or a pending state
– Ring switching types (on the left)
• Lockout Ring:
The external command, Lockout of working channels – ring switch, was performed locally on
this side
• Forced Ring:
The external command, Forced Switch to Protection – Ring, was performed on this side (local)
or remote.
• Auto Ring:
An automatic switch request is present because of Signal Failure (SF) or Signal Degraded (SD)
was detected on the port of this side (local) or remote.
• Manual Ring:
The external command, Manual Switch to Protection – Ring, was performed on this side (local)
or remote.
• WTR Ring:
The automatically initiated command, WTR, was initiated because of Signal Failure (SF) or Sig-
nal Degraded (SD) was restored. The node is staying in this state as long as the WTR time was
configured local or remote.
Span switching (on the right) is not supported in the current release.
The Local/Remote indication is present: If the field L is highlighted, the external command was initi-
ated respectively the SF/SD condition is detected on the Local node. If the field R is highlighted, the
external command was initiated respectively the SF/SD condition is detected on a Remote node (ad-
jacent node).
In case of an automatic switch, there is no indication in MS-SPRing view if it’s because of a SF or

SD. Nevertheless, the alarm indicated in Port view is giving this information.
N.B. Lockout Ring can only be local. Lockout Prot. is highlighted together with Prot. Unavailable
when it is local. On the remote side, only the state “Prot. Unavailable” indicates that on the
concerned span, the protection channels cannot be used for protection.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 843 / 926
926
19.6.4 MS-SPRing Protocol Exceptions
In the frame “Protocol Exceptions” the current exceptions signalled are displayed. If an exception is occur-
ring the state will be highlighted red.

There are three types of exceptions:
– APS improper code: Error in the APS Protocol (K1/K2 bytes)
– Node Id mismatch: Incoherence in the K-byte Node Id field in different request received (typically
when there is incoherence between ring maps at different nodes)
– K default bytes: the K1/K2 bytes contain an equal source and destination Node Id. Nodes in the “En-
abled” status but not yet activated MS-SPRing emit default K bytes.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 844 / 926
926
20 ATM CONFIGURATION (ONLY AVAILABLE FOR W/OMSN)
20.1 Introduction
This Chapter describes the operations necessary for the ATM boards creation in the Equipment view
and the ATM TTPs creation; as a matter of fact ATM boards does not create TTPs when they are configu-
rated
The ATM board creation is performed (following the same rules of all the other SDH/PDH ports as ex-
plained in paragraph 7.2.2 on page 218) when a CT user sets an ATM board and then configure the IP
Address (as described in paragraph 23.13 on page 917).
For the TTPs creation refer to paragraph 20.2 where all the operation are explained.
For the ATM traffic configuration (creation of Hard / Soft cross connection, PNNI configuration etc.) refer
to the relevant ATM OPERATOR’S HANDBOOK if applicable to the software version, this manual will
be reported in the Handbook Guide for the product ’s software release of this Operator’s Handbook. Differ-
ent (Smart or USM) applications will be supported according to SH Release and Software Version.
The operational sequence to follow to manage ATM cross–connection is:
a) ATM board declaration (Equipment Set: see para. 7.2.2.1 on page 218).
b) ATM IP Address Configuration ( see ISA board IP Address: see para. 23.13 on page 917 ).
c) ATM board TTPs creation (VC4–4c TTP, VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP, E1 TTP).
d) TTPs cross–connection ( refer to paragraph 15.2 on page 570).
e) ATM traffic configuration supported by the ATM Operator’s Handbook.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 845 / 926
926
20.2 ATM board TTPs creation
In this paragraph will be explained how to create, delete and modify ATM TTPs.
On the ATM 4X4 board can be configurated up to 16 TPs (VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP, E1

TTP) with the following restriction:

– In this release it is not possible to manage structured and unstructured TPs on the same board
– the maximum throughput is 622 Mbit/s
On the ATM 8X8 board can be configurated up to 32 TPs (VC4–4c TTP, VC4 TTP, VC3 TTP, VC12 TTP,
s31 TTP, E1 TTP) with a maximum throughput is 1.2 Gbit/s.
Select Atm Configuration option from the Configuration menu to open the ATM ports Configuration (see
Figure 582. on page 846).
ATM 4X4 MATRIX ATM 8X8 MATRIX
Figure 582. ATM ports Configuration
The ATM ports Configuration window is filled with notebook pages (initially blank), each page is an ATM
board with 16 ports;
The user can “create” a new port, “delete” an existing one and “change” port associations (that means
modify the STM1 number and STM–1 Time Slot on ATM ports already created) via the three buttons con-
tained in the notebook page.
When the user want to create a new ATM port he can select an empty row, then in the “Selected Item”
section , he can fill the field ”Signal” choosing among the available options (SDH VC4–C only for ATM 8X8
MATRIX, SDH VC4, SDH VC3, SDH VC12, PDH 34M and PDH2M) and push the”Create” button.
The STM1 Number and the STM1 Time Slot are automatically assigned.
An example of ATM port creation is depicted in Figure 583. on page 847.

1AA 00014 0004 (9007) A4 – ALICE 04.10
If the user want to change the port attribute association he can select a filled row, then in the “Selected
Item” section he can change the fields ”STM1 number” and ”STM1 Time Slot” and than push the ”Time
Slot Sw.” button.
3AL 89062 AA AA 846 / 926
926
To delete a port the user can select a row and push ”Delete” button.
Figure 583. ATM ports Configuration (example)
To close the dialog box click on the “Close” push button.
It is possible to see the ATM Ports created as above explained by selecting the relevant ATM board in
the Equipment view and double clicking on it; Figure 584. on page 848 opens.
Subsequently select the PSEUDO SUBBOARD icon in the Equipment view and double click on it,
Figure 585. on page 848 opens showing the ATM ports.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 847 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Pseudo Subboard icon
Figure 584. ATM board view
926
3AL 89062 AA AA
Figure 585. ATM PSEUDO–SUBBOARD view (example)
848 / 926
21 SOFTWARE MANAGEMENT (NOT AVAILABLE FOR OMSG)
21.1 Generalities and descriptions

The 1353SH system provides a set of functions which allow software packages manipulation within NEs.
The downloading operation consists in the establishment of session between the NE and a software
server for the purpose of file transfer.
Actions can then be performed on the software version as update, delete, activation and commit
operations, or roll back to the previous software version operation. In this way the NE can follow the
product evolution with “in service” equipment.
The same function is used during maintenance phase, to update spare boards for substitution after
troubleshooting.
A backup/restore can be also done on the MIB of the NE. Indeed the MIB can be saved to or restored
from the mass storage of the 1353SH. The operator can use the NE simulator to prepare a configuration
of the NE MIB. This MIB is then saved in the NE MIB backup area, ready to be downloaded to the NE MIB.
The software download general principle is represented in the following figure.
Software Management
OPERATOR MANAGER Download

Control
Event
Report AGENT
NE
Transfer
CLIENT
Request
Software Downloading
Binary & Data

OPERATOR SERVER Files
Figure 586. Software Download general principle

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 849 / 926
926
21.1.1 Naming Conventions
The naming conventions used for the SDH Manager are the following:

– Software Package: Software Package stands for a piece of software which can be executed by an

NE of a particular type. It consists in one or more Software Units and a Descriptor File. A software
package is identified by its name, release, version and edition.
On the NE (i.e. once downloaded) a software package can be:
– the active version: the software package currently running on the NE
– the boot version: the software package to be used by the NE when re–booting
– a standby version: a software package which is neither the active version nor the boot
version
– Software Unit: A Software Unit is a part of a software package which can be either executable code
or a data segment of a particular board within an NE. A software unit is also identified by its name,
release, version and edition.
– Descriptor File: A Descriptor File contains information about the software package it belongs to and
lists the composing software units. Each software package must have a descriptor file otherwise it
would not be possible to interpret the content of the package.
– Software Management Function: The Software management function offers information about all
current software packages present in an NE. Indicators enable software management (running
package, activated package, etc...).
The following software version states are available:

• Active version: the software version currently running on the NE.
• Boot version: is the software version which is used to restore a platform valid configuration if
some action fails or if a crash occurs. This software version is used by the NE in the case of a
spontaneous re–boot or OS re–start command.
• Committed version: is similar to the boot version.
• Standby version: is a software version which has been downloaded on the NE but which is
neither in the active state nor in the boot state.
Two main functions are involved in the software downloading:

– Software Download Manager function
– Software Download Server function
The Software Download Manager function takes the downloading and management requests of the
operator and sends them to the NE. Thus, this function enables a download process to be initiated and
monitored by the operator. It manages the NE software releases and initiates software download
operations.
The Software Download Server is only responsible for fulfilling the requests received from NEs and
performing software package file transfer operations to the NE.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 850 / 926
926
21.1.2 Software Management functions
Usually the operator will first ask for the present status of the software on a selected NE. Provided that
the status allows a download operation (idle status), the operator selects the new software package in the
server and triggers the download process. Afterwards, he will activate the package. If everything works
well with the new activated package, the operator will do the commit operation. If problems are found with
the new activated package, he can use the de–activate (revert–back) operation to come back the previous
software package and data.
– display Software Download Information,

– set / get the server address,
– initiate / Abort Software Package Download,
– manage Software Packages within NEs.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 851 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
21.2 Software Download Management commands
Figure 587. Equipment view

All the software download operations are carried out from the EMLUSM.
926
3AL 89062 AA AA
852 / 926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
is displayed:
Figure 588. Download menu
926
3AL 89062 AA AA
To display the software management commands select the Download pull down menu. The following menu
853 / 926
21.3 Init download
You can request the NE to start / abort a software download operation. After selecting the desired NE you
must choose an available software package, set the required download / activation attributes and then

start the download process. All these operations can be performed from the SW downloading dialogue

box.
Select the Init download option from the Download cascading menu.
The Software download initiate dialogue box is opened.
Figure 589. SW Downloading dialogue box
The following fields are available to search a specific package:
– Server filter: to enter the server name selected,

– Package filter: to enter the package name selected.
To display the selection, push on Apply filter(s) button.
In the next field the list of the packages is displayed:
– Server: name of the server,

– Package: name of the package,
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Version: version number of package.
3AL 89062 AA AA 854 / 926
926
Click on Forced push button to set the forced download attribute: then all software units of the Descriptor
file have to be downloaded even if already present within the NE.
If you want stop the download, click on the Cancel push button of the Software download initiate dialogue
box to close it.

Click on the OK push button to start the download. From the confirmation dialogue box that opens, you
can confirm or cancel the download. If you confirm the operation, the SW Downloading dialogue box then
disappears and the Software download in Progress dialogue box is displayed (see Figure 590. ) from
which you can if necessary abort the software download.
Figure 590. Software download in progress
The Software download in Progress dialogue box displays the name and type of the NE and the SW
package name, the total of bytes, the current percentage and the current file which is being downloaded.
Click on the Abort push button to abort the complete download transaction. From the confirmation
dialogue box that opens you can confirm or cancel the abort.
Click on the Close push button to close the SWDL Work in Progress dialogue box at the end of the software
download.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 855 / 926
926
21.4 SW package Activation and Units information
This item permits to activate the downloaded software package and to get information about the software
of the various units of the equipment.

Operator is able to get information about the software package of the NE at any moment, even if no
download operations have been performed previously.
For this, select the Units info option from the Download pull down menu.
Figure 591. Software Package Information dialogue box
The SW Information dialogue box displays the name and type of the NE, and the respective package name
and status of the committed and (if existing) the uncommitted software.
You can select one software package by clicking on the name.
The following fields are displayed:
– Software package: name, release, version, edition of the package,

– Operational state: enabled or disabled,
– Activation date: date and hour of the last activation
– Vendor: the supplier of the product,
1AA 00014 0004 (9007) A4 – ALICE 04.10
– Current state\Action: commit or stand–by and with the option button; none/Force/Activate/Delete
current state = standby means the package is not active on the NE
current state = commit means the package is active on the NE
3AL 89062 AA AA 856 / 926
926
action = (none) means no action to do
action = activate serves to activate the selected SW package
action = force (item not operative)
Select the Activate option of the “CurrentState\Action” field, to activate the Software package.
The SW units det. button allows to give more informations about a selected software package.
Click on the SW units det. button, the following window is displayed:
Figure 592. Detail of units info
Then click on [+] on [–] symbol behind the software package to obtain more detail or to hide it .
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 857 / 926
926
Figure 593. Detail software package
When you click on Close the previous view is displayed (Figure 592. ).
In Figure 591. when you click on the:
– OK push button you close dialogue box,

– Cancel push button you close the SW Information dialogue box,
– Help push button you access to help on context.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 858 / 926
926
21.5 Servers Management
If the NE is reachable by a different SH OS connected to the local SH OS, the NE software downloading
can be launched with the “Serves Management “ command. Select from the “Download” menu the Servers
management option to open Figure 594.

Figure 594. Servers management window
Select the required Software server name to chosen the right SH OS address as shown in Figure 595. or
enter / update a new one. To enter a new server address fill in the fields of Figure 594. and push on the
“Enter” key of the keyboard to enable the “Add” button of Figure 594. The Network address has to termi-
nate with the software downloading NSAP (network service assess point) SEL= “10” instead of the NSAP
NE management SEL= 1d. Clicking on “Add” the new server name will be stored into the list server names.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 859 / 926
926
Figure 595. Example of server “remote1” data
Select the “Remove” push button to remove the Server data or click on “Update” to modified the Server
data indications. When the user select the “Init Download” command and the NE is not reachable by the
selected SH OS server, a warning info. is displayed as in Figure 596.
Figure 596. Chosen Server address does not match the relative NE
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 860 / 926
926
21.6 On Board Simulator
21.6.1 Generalities
An important change in NR5 is related to the introduction of the NEs simulators (so called on–board
simulator) within the SH system. The NE simulator is used to simulate the presence of the actual NE when
the latter is not reachable or does not exist (pre–deployment period). The simulator is manageable only
by SH (not by Craft Terminal). The services described in the document are provided only if a simulator
is present (see Figure 597. ).
Figure 597. Simulator inside SH environment
In Figure 597. , a functional scheme of the Simulator inside the SH environment describes which
functional blocks are involved with the Simulator.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 861 / 926
926
To simplify the figure, only the main functional blocks interacting the Simulator are shown, i.e.:
– USM: it is an operator interface and allows the SH operator to Start/Stop the Simulator, NE
Configuration, MIB Management, etc.;

– Q3EML–IM: it receives requests by USM and sends them to the Simulator (if the latter is active) or to
the NE (if the Simulator is not active);
– SIMCON: is a simulator controller and the functions carried out are:
1) to perform the internal communication address between Q3EML–IM and NE–SIMULATOR blocks;
2) starting and stopping the Simulator.
When the Simulator is started, SIMCON is not involved any more in the communication between
Q3EML–IM and NE SIMULATOR blocks until a new simulator stopping request will occur.
– NE SIMULATOR: Simulates the operations of the software related to the specific NE as described in
the following chapter.
In Figure 597. the symbols into parenthesis stand for:
– [M,P]: the related functional blocks are present in the Master WorkStation and/or in the Presentation
Workstation
– [M,E]: the related functional blocks are present in the Master WorkStation and/or in the EML Workstation
The simulator is used in the following cases:
– to prepare a configuration of the NE MIB before installing the NE (i.e. off line configuration mode).
This configuration (loaded in the simulator) will be downloaded towards the NE when the NE will be on
line (the NE is connected to SH application);
– to allow the operator to browse the simulator MIB when the NE communication is lost (i.e. Off–line
Navigation Mode). In this case the operator uses the NE simulator to navigate;
– to prepare the MIB restore operation, giving the possibility to synchronize the MIB contents against the
information stored in RM.
The on–board simulator can be used to simulate several different NE type: 1664SM, 1650SMC, UHR,
UHRC... , see the “List of NEs supported by 1353SH” (SC.1.1: Handbook Guide of Vol 1) to check the
NEs with OBS.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 862 / 926
926
21.7 Simulator operations
The operations that can be carried out by the Operator are described in the sections that follow.
21.7.1 Starting the simulator
The simulator is started manually on SH operator’s request in readOnly mode (off–line navigation use)
or in readWrite mode (off line configuration) depending on the state of the NEs (i.e. the NE is in
Supervisioned or not Supervisioned state). No automatic mechanism to start–up the simulator exists in
SH, neither to stop it.
To start the simulator select the Supervision pull down menu and the following window will be displayed:
Figure 598. Supervision Menu window
Select the Start option from the Supervision cascading menu.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 863 / 926
926
The confirmation box is then displayed (see Figure 599. ). Click on the OK button to start the simulator.

Figure 599. Start simulator confirmation box
The simulator cannot manage different NEs at the same time. Only one simulator can be active
at a time.
The start of the simulator can be launched if the NE is in Q3 isolation state, i.e.:
– the NE has just been created (declared state);
– the NE is supervised and has a loss of communication;
and after a stopping supervision operation.
Note: After clicking on the OK button in the Start simulator confirmation box, the operator has to wait until
the SIM icon will become a light–blue circle as displayed in Figure 601. Icon color changing indicates
that the simulator has been started.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 864 / 926
926
21.7.1.1 On–board simulator monitoring
The On–board simulator monitoring function is available on SMF menu: select from the main 1353SH
functionalities, the “Administration” icon–>System Management and then the On–board simulator
monitoring option. Figure 600. opens

Figure 600. On–board simulator monitoring window
N.B. If a change occurs, the window is not automatically updated: push the Refresh button in order
to know the on–board simulator current status.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 865 / 926
926
Figure 601. Start simulator confirmation icon window
Note: The simulator would stop automatically if EML–IM stops during a simulation. After stopping the
EML–IM, the following window will appear (see Figure 602. ).
Figure 602. EML–IM crash box
The operator would have to restart the simulator. However in case of loss of communication between the
EML–IM and the simulator, the simulator is considered as stopped. This means that the SH operator would
have to request again a start of the simulator if he wants to re–use it.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 866 / 926
926
21.7.2 Stopping the simulator
The simulator is also stopped manually on SH operator’s request. No automatic mechanism to stop the
simulator exists in SH. This operation is possible only if the simulator has been started before.
To stop the simulator select the Supervision pull down menu and the following window will be displayed
(see Figure 603. ):
Figure 603. Supervision menu and stop simulator window
From the confirmation box that opens (see Figure 604. ) the operator can confirm or cancel simulator
stopping.
Figure 604. Simulator stopping confirmation box

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 867 / 926
926
21.7.3 Functional description
The on–board simulator shall never be used during the normal activities in the SH systems but only in case
of very specific problems with the NEs as explained in the following sections.

Next section describes the functionalities provided by the simulator and how the operator can use them.
21.7.4 View of configuration during Q3 isolation
This functionality is provided when the NE is being supervised and there is a loss of communication
between the NE and the EML–IM (see Figure 598. ).
In such a condition (Q3 alarm active), if the operator wants to navigate through the last updated
configuration of the NE, he shall start the simulator
21.7.4.1 Off–line navigation mode operations
This operation can be performed by Presentation workstation (including RM) or by SH workstation.
The operator can use the simulator to navigate through the NE configuration but not to configure the NEs.
When the simulator is in off–line navigation mode, some functionalities are not available. It is possible only
to view the boards of the NEs (clicking on them) but they cannot be set.
If the operator clicks on the Equipment pull down menu, the following menu is displayed:
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 605. Off–line navigation mode Equipment menu window
3AL 89062 AA AA 868 / 926
926
The Set option is greyed as can be seen from Figure 605.
It can be noted that the Q3 icon is a red circle because the NE is not reachable.
Also the Align–up and Align–down options in the Supervision menu are not available. This is displayed
in Figure 606.
Figure 606. Off–line navigation mode Supervision menu window (NE not reachable)
Note: If during the off–line navigation mode operations the NE becomes again reachable then the Q3 icon
will became a green square, as displayed in Figure 607. Icon color changing indicates that the NE is again
reachable.
Therefore, the operator keeps on working on the NE database image stored in the SH.
During the NE unreachablity period, the alarms displayed to the operator refer to the last known alarm
situation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 869 / 926
926
Figure 607. Off–line navigation mode (NE reachable)
For details about the navigation description from the NE view and the board views please refer to specific
chapter in the handbook.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 870 / 926
926
21.7.5 Off–line configuration mode
21.7.5.1 Generalities
The off line configuration mode, provided when the NE is not being supervised, allows to modify and locally
store the MIB configuration of the NE without affecting the real NE. Then, the configuration entered during
the off–line configuration should be downloaded to the NE to take the modifications into account.
This operation is used when the operator wants to start configuring its network before having phisically
deployed and installed the actual NEs.
In this way, the operator can configure the NE (one at a time), and RM can be aware of NE ports even if
the NE is not yet in field.
RM can now start working on the whole network composed of not yet existing NEs. When working on the
transmission configuration, the RM does not need the NE simulators on SH to be active. Therefore, once
uploaded the ports onto RM, the relevant NE simulator shall be stopped.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 871 / 926
926
21.7.5.2 Off–line configuration mode operations
This operation can be performed by Presentation Workstation (including RM via navigation) or by SH

Workstation.

Basically, the off–line configuration mode allows the operator to set the NE boards using the NE on board
simulator.
By clicking on the Equipment pull down menu, the Set out service option will appear as displayed in the
following figure.
Figure 608. Off–line configuration mode: Set out of service window
First the operator has to click on the board to configure and then he has to click on the Set out of service
button from the Equipment pull down menu, as displayed in Figure 608.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 872 / 926
926
The Set option is now activated, as displayed in the following figure.
Figure 609. Set board window
Finally, by clicking on the Set button a new window will appear (see Figure 610. ) and the operator can
choose the board to set.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 610. Select board window
To have more details about the configuration description from the NE view and the board views, please
refer to the specific chapter in the handbook related to the download operations.
3AL 89062 AA AA 873 / 926
926
21.8 Mib management starting from SH5.5 for NE with OBS
This fonction allows to make a backup and/or a restore of the Mib.

The NE MIB management has been performed by the Simulator management. The previosly MIB Backup and

Restore have been substituted by the Simulator–> Align Up and the Simulator–> Align Down respectively
commands. Then starting from SH5.5 the MIB repository, of NE equipped with OBS, will contain only one
NE MIB, the last one on which the Align Up operation has been performed will sobstitute the old one.
21.8.1 Introduction
The SH system is able to manage the MIB file present in the Q3 NE. This file is used only as a backup copy
of the actual NE configuration, and it is not used, in any case, during normal network management
activities. Two main functions are provided by the SH system about the MIB management: the backup and
the restore of the NE MIB implemented with the align–up/align–down commands.
All these operations are launched manually by the SH operator. No automatic mechanism for all these
operations is provided.
Note: The SH system generates an alarm (warning severity) if the NE is supervisioned and no backed
up MIBs exists (because the simulator MIB and the NE MIB are misaligned). As soon as the SH operator
requests a new Align–up operation the alarm is automatically cleared. This alarm is generated also every
time the SH operator performs any NE configuration changes (i.e. set board and/or synchronization)
excluding changes in the transmission domain.
21.8.2 MIB align–up descriptions
The align–up function allows the operator to upload the copy of the MIB image from the real NE (in
supervised state) to the SH. The simulator will eventually use this copy, which is supposed to be the last
updated copy of the NE database. When performing an align–down operation, this MIB image will be
downloaded into the NE. If, by means of the simulator, the operator works on this image and then aligns
up the MIB again (hence a new image is created, i.e. the copy of the actual NE MIB), the last
modifications are lost.
Basically, the MIB database file contains the following inforrmation:
– all the persistent information of the NE except the “addressing information”, i.e. the not–static data
(history data, log records) and the dynamic values (state of protections, alarms) are not present into
the MIB backup file;
– the identifiers of the points related to the TPs under observation (i.e. where are activated the PM data)
but not the collected values.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 874 / 926
926
21.8.3 MIB align–up operations
The SH operator needs to perform periodically the align–up operation in order to provide the SH system
the last NE MIB in case of the NE failure.
To perform the align–up operation select the Supervision pull down menu and the following window will
be displayed:
Figure 611. Supervision menu and Align–up selection window
Select the Align–up option from the Supervision menu.
The confirmation box is then displayed (see Figure 612. ).

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 612. Align–up confirmation box
3AL 89062 AA AA 875 / 926
926
Click on the OK button to confirm the align–up operation.
When the align–up operation is completed, the following window is diplayed.

Figure 613. MIB alignment Information box
By clicking on the Cancel button, the operator closes the MIB alignment Information box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 876 / 926
926
21.8.4 MIB align–down and activate descriptions
The align–down function can be considered the reverse operation of the “align–up function” . It allows the
operator to download from SH to the real NE the modifications made by means of the simulator on the last
aligned–up MIB. The related NE has to be in the supervised state.

Then the downloaded MIB should be activated to take the modification into account. For this purpose an
Activate function is provided by SH system.
21.8.4.1 MIB align–down operations
To perform the align–down operation select the Supervision pull down menu and the following window
will be displayed:
Figure 614. Supervision menu and Align–down selection window
Select the Align–down option from the Supervision menu.
The confirmation box is then displayed (see Figure 615. ).

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 877 / 926
926
Figure 615. Align–down confirmation box
Click on the OK button to confirm the align–down operation.
21.8.4.2 MIB activate operation
The MIB activate operation can be executed from the Supervision pull down menu, selecting Simulator
–> Activate option (see Figure 614. )
Note: Before performing the activate operations, the operator has to be sure that the align–down
operation is successfully completed and so he has to verify that the Activate button in Figure 614. is not
greyed.
After pushing the Activate button the related NE shall restart itself therefore the SH operator
has to wait a few minutes until the NE will became aligned with the new MIB previously
downloaded . During this transitory period no actions on the NE are possible because the NE is
in Q3 isolation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 878 / 926
926
21.9 Mib management without OBS
This fonction allows to make a backup and/or a restore of the Mib if it is not provided the on board simulator
(OBS) functionality. The MIB database contains the same info file described in the previous para. 21.8.2.
This paragraph describes the different field option and the procedures to follow for the MIB Management
21.9.1 MIB backup and restore field options
Select the Mib Management option from the Download pull down menu. The first time, the following
window is displayed:
Figure 616. First NE MIB management window
After some backup, the window displayed is:

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 879 / 926
926
Figure 617. NE MIB management window
The displayed fields are:
– Available backups on local server: gives the list of the backups available on the NE,
– Backup name: to enter the new backup name.
Three push buttons allow to choose the action with click on:
– Backup: performs the backup except for the “Local Configuration” tables,
– Restore: this fonction allows the managing system to restore the NE configuration database of the
managed system. Only one restore operation can be performed at the same time on a given NE.
– Delete: this action allows to delete a backup of the NE database. The NE is not involved in this action.
The only effect is to delete the selected backup version stored in a specific directory of the FT server.
– Restore to simulator ( not applicable ).
To activate an already restored MIB, click on Activate push button.
After pushing the Activate button the related NE shall restart itself therefore the SH operator
has to wait a few minutes until the NE will became aligned with the new MIB previously
downloaded . During this transitory period no actions on the NE are possible because the NE is
1AA 00014 0004 (9007) A4 – ALICE 04.10
in Q3 isolation.
To exit of the NE MIB management window, you click on Close push button.
3AL 89062 AA AA 880 / 926
926
21.9.2 MIB backup, restore and delete procedures
The MIB backup procedure allows the operator to build up a repository of backup copies of NE MIB. Each
MIB image is characterized by the Operator using a user label that univocally identifies it.
Instead, the MIB restore procedure allows to download one of the MIB copies from the repository of backup
copies of the NE MIB into the NE. This copy may be an old copy of the NE MIB and not only the last copy
uploaded via a previous MIB backup procedure.
Perform the first backup
1) Choose the Download –> Mib management menu option.

The NE MIB management dialog box appears.
2) Type in the name of the backup under Backup name.

Example: 1696_TEST. The extension of the Backup file name is not required.
3) Click on Backup.
In the Question dialog box, answer Ok to the ”Do you confirm the backup operation?”
question
In the Backup dialog box displaying the ”Backup in progress” message, do not click on
Cancel.
4) When the backup is completed, an Information dialog box containing the following message:
Backup successfully, appears. Click on Cancel to return to the NE MIB management dialog
box.
The name of the new backup is automatically displayed under the entry Backup Name.
5) Click on the Close to terminate the backup session.
To perform further backups, you can either give the new backup a new name or overwrite the existing
backup file.
Restore a backup
The Restore function allows the management system to restore the NE configuration database (MIB) of
the managed system. Only a single restore operation can be performed at the same time on a given NE.
1) Choose the Download –> Mib management menu option:

2) In the Available backups on local server field, select the backup file to be restored,
the name of the backup file is displayed under the Backup name entry.
3) Click on the Restore button,

in the Question dialog box, answer Ok to the ”Do you confirm the backup restoration?”
question,
in the dialog box displaying the ”Restore in progress” message, do not click on Cancel.
4) When the restoration is completed, an Information dialog box containing the following message:
Restore completed, appears. Click on Cancel to return to the NE MIB management dialog
box.
When the restore operation is completed, the data are stored on NE, but not yet activated in
the Equipment. It is mandatory to activate the restored Mib.
1AA 00014 0004 (9007) A4 – ALICE 04.10
5) Select the restored Mib and click on Activate under the option To activate an already restored
MIB,
3AL 89062 AA AA 881 / 926
926
6) In the Question box, answer Ok to the ”Do you confirm the Mib activation?” question
7) When the activation is completed, an Information dialog box containing the following message:
Mib activation completed, appears. Click on Cancel to return to the NE MIB management

dialog box.

8) Click on Close to terminate the backup session.
9) If the automatic NE restart is not implemented, choose the Supervision –> Restart NE... menu
option.
Then wait until the NE has restarted.
Delete a backup
The Delete action is aimed at deleting a backup of the NE database. The NE is not involved in this action.
Only the selected backup version stored on SH will be deleted.
1) Choose the Download –> Mib management menu option.

2) Select the backup file to be deleted,

the selected backup file is highlighted and displayed under the Backup name entry,
3) Click on the Delete button.
4) In the Question box, answer Ok to the ”Do you confirm the backup deletion?” question
5) When the deletion is completed, an Information dialog box containing the following message:
Backup deleted, appears. Click on Cancel to return to the NE MIB management dialog box.
6) Click on the Close push button to exit the NE MIB management dialog box.
To save or load the Mib to/from an external disk follow the indication of the “Print Dialog” para.3.10 of the
Q3–NE Management.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 882 / 926
926
21.10 Restart NE
The restart operation in any case activates the boot version.

Select the Restart NE option from the Download or from the Supervision cascading menu.
Figure 618. Restart NE confirmation
Click on the OK push button to perform the restart NE.
Click on the Cancel push button to abort the restart NE.
In the dialog box displaying that the NE restart is in progress, if you click on the Cancel push
button, the process is not stopped, only the window is closed.
N.B. A restart operation cancels all the NE PM counters.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 883 / 926
926
21.11 ATM Installation notes
To install the NE software pachage see the specific doc. on the 1353SH Rel.5.5 Administration Guide [2]
Chapter 11.11 OMSN SWP merging tool. A similar description can be also found on the ATM Rel.1.1

Operator’s Handbook [7] ( Chapter 3.5 NE–atm package installation procedure).

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 884 / 926
926
22 OVERHEAD MANAGEMENT (NOT AVAILABLE FOR OMSG)
22.1 Introduction
The purpose of this set of dialogs is to handle the operations on the Overhead (OH) bytes of the NE.
The possible operations are:
• Overhead cross–connection
– Cross–connection between 2 or more OH bytes
– Termination of an OH byte onto an auxiliary port or vocal channel
– Total Pass–through of the MSOH bytes for some cards
– Definition of the Phone Parameters
There is a TP associated to every OH byte and to every auxiliary port, so TP could be used instead of OH
bytes or auxiliary port, depending on the context.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 885 / 926
926
22.2 OH Connection overview
Here are described the possible OH connections.

For the OH Phone Parameters directly refer to the para.22.7 on page 896.

– OH Cross–connection
The operator has to be able to cross–connect the OH bytes on the different boards.
The possible cross–connection types are:
• unprotected unidirectional point to point

• unprotected bidirectional point to point
• unprotected unidirectional multipoint
The steps an operator has to do in order to perform the cross–connection are the following:
• create the OH TPs involved in the operation

• create the OH cross–connection:
– select type of cross–connection
– select first OH TP involved in the operation
– select second OH TP involved in the operation
Multipoint cross–connections can be created by repeating a sequence of point–to–point

cross–connections, with the same starting point.
After having deleted an OH cross–connection, the involved TPs have to be deleted.
– OH Termination
The operator has to be able to terminate one OH byte onto an auxiliary port or vocal channel.
The steps an operator has to do in order to perform the OH bytes termination are the following:
• create the OH TP involved in the operation
• create the OH byte termination:
– select the created OH TP
– select the auxiliary port/vocal channel TP involved in the operation
After having deleted an OH byte termination, the involved TP have to be deleted.
– Total MSOH Pass–through
For STM ports it makes sense to allow the operator to perform a total pass–through of the MSOH bytes.
A total msoh pass–through connection (connection between msPassThroughCTP points) is set–up only
if no single msoh pass–through connection are set and if no single msoh cross–connection are set. If a
total msoh pass–through connection is set, a single msoh pass–through connection or a single msoh
cross–connection cannot be set.
The steps an operator has to do in order to perform the total MSOH pass–through are the following:
• create the msPassThroughCTP points involved in the operation
• create the total MSOH pass–through:
– select the first msPassThroughCTP point involved in the operation
– select the second msPassThroughCTP point involved in the operation
1AA 00014 0004 (9007) A4 – ALICE 04.10
After having deleted a total MSOH pass–through, the involved msPassThroughCTP points have to be
deleted.
3AL 89062 AA AA 886 / 926
926
22.3 Overhead views
The Overhead Views allows to perform the previously presented operations.

To access select Overhead option from the USM menu commands as indicated in chapter 2; the following
options are presented in the cascading menu:
• OH Cross Connection See next para.
• OH Phone Parameters See para.22.7 on page 896.
• OH TP creation See para.22.5 on page 894.
• OH TP deleting See para.22.6 on page 895.
Figure 619. Overhead options
The options are described in next paragraphs.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 887 / 926
926
22.4 OH Cross Connection
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu
the OH Cross Connection option.

The Cross-Connection Management for OverHead dialog opens (see Figure 620. on page 888 ) and

allows to start the configuration.
Figure 620. Cross Connection Management for OverHead dialog
It is similar to the dialog used for the cross–connection of the TP for paths, then the same
description and functions are valid.
Next configuration steps use the Main Cross-Connection for OverHead (see Figure 621. on page 889)
dialog and the TP Search dialog (see Figure 332. on page 510), also in this case already described for
path management.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 888 / 926
926
Figure 621. Main Cross-Connection for OverHead dialog
For all details, navigation and sequences on these views refer to chapter 15 on page 555.
There is one big difference between the OH TPs and the other kinds of TPs: the OH TPs have to be:
• created ONLY BEFORE a cross–connection/termination operation involving them has been
performed.
• deleted AFTER a cross–connection/termination deleting involving them has been confirmed.
The current implementation of the TP Search Dialog (TPSD) works only with created TPs.
In the following a description of the main functions and commands is given, also to list the Supported and
Not Supported operation.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 889 / 926
926
22.4.1 Cross-Connection Management dialog
See Figure 370. on page 571

– Supported operations

• Search cross connections/terminations according to one or more of the following filtering
attributes: name, type, class or one of the TPs involved. The operator can set the filtering
criteria, can start the search and select one or more crossconnections/terminations among
those presented in a read–only list as a result of the search operation. For each cross
connection/termination matching the filtering criteria, the following information is shown:
direction (bidirectional) and the input, output TPs involved.
After choosing one or more crossconnections/terminations, this dialog allows to:
• Delete the selected crossconnection/termination

• Go to the “Main Cross Connection” dialog and modify the existing crossconnection/termination
Note: this dialog disappears only when the user explicitly clicks on the close button.
Delete operations can be performed on several crossconnections/termination at the same time.

Modify operations can be performed only on single crossconnections/terminations.
The OH crossconnections are automatically active at the moment of their creation.
The operation buttons availability follows some rules:
• The Delete and Print buttons are enabled only if at least one item is selected from the list.
A special dialog will ask the user for a confirmation.
• the modify button is enabled if one (and only one) item is selected. It brings up the Main
crossconnection dialog.
• the create button is always enabled. It brings up the Main crossconnection Dialog.
When some operation may affect the existing traffic, the operator is warned about that, and a confirmation
dialog must be answered to carry on/cancel the operation. The choices for this dialog are: yes/no for
single items, yes to all/cancel for multiple items
– Not Supported operation
When used for OH purposes, the Cross-Connection Management dialog doesn’t support the following
functionalities:
• Protect cross connections/terminations: all the OH cross connections/terminations are

unprotected
• Activate/Deactivate cross connections/terminations: all the OH cross

connections/terminations are automatically active since their creation
• Split cross connection/termination
• Modify Cross Connection Termination

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 890 / 926
926
22.4.1.1 Main Cross-Connection dialog
See Figure 376. on page 586.

According to the philosophy of offering only meaningful operations to the user, and being the OH
crossconnection operations a subset of those applying to the general cross connections (e.g.:protections
are not allowed), some fields of this dialog are disabled.
By clicking on the proper portions of the dialog and on the proper buttons, the operator can perform the
operations hereafter listed:
• selection of the cross–connection type
• selection of the input TP involved in the cross–connection
• selection of the output TP involved in the cross–connection
In order to do that the operator can either type in the involved TPs ID or use the TP Search dialog.
– Supported operations
• When creating a new cross connection, some or all of the following operations are available,
depending on the NE type characteristics:
– Choose between unidirectional and bidirectional
– For unidirectional cross connections, choose one input TP and one or more output TPs.
It is possible to directly type in the TP name or to click on the Choose button to select a
TP from the TP Search dialog box
– For bidirectional cross connections, choose one input TP and one output TP. It is possible
to directly type in the TP name or to click on the Choose button to select a TP from the TP
Search dialog box
• When modifying an existing cross connection, the same operations are available. Some
changes, may be traffic–affecting, as they may imply a temporary cross connections
destruction. In these cases a proper dialog box forces the user to confirm the operation.
• Broadcast cross connections can be achieved by creating a series of point–to–point

connections, with the same source (input) TP and different destination (output) TPs.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 891 / 926
926
22.4.1.2 TP Search dialog
The TP Search dialog (see Figure 332. on page 510) currently offers:

• navigation rack/subrack/board/port

• a list of TPs to choose from
When used in the OH domain, this dialog is a subcase of the most generic TP Search.
The operator can choose among a list of:
• all the possible OH TPs belonging to a specified class: no board selected and MS, RS or VC4
class selected
• all the possible OH TPs belonging to a specified board/port: board/port selected and no TP
class selected
• all the possible OH TPs belonging to a specified board/port and class: board/port selected and
MS, RS or VC class selected
• all the OH TPs already connected (also accordingly to the connection type)
• all the OH TPs not yet connected
• a combination of the above options
On any Network Element to connect the auxiliary / vocal channels and the Overhead bytes
different actions have to be provided .
– the auxiliary and vocal channels TPs are in the AUX EOW (1664SM R.3.2) or SERVICE
(1660SM)or SERGI (1650SM) board depending on the NE type slot
The auxiliary available channels are described in the proper “CT Technical/Operator’s Handbook.
In the example of 1660SM 2.1B NE can be taken in account the following indication:
– the auxiliary and vocal channels TPs are in the SERVICE board of slot 11
The auxiliary channels are:
• 2 x G.703 2 Mbit/s (not operative in current release); in the screen are indicated as:
– r01sr1sl11/port#05–P
Expanding this TP, 31 referred TPs are presented
Expanding this TP, 31 referred TPs are presented
• 4 x G.703 64Kbit/s; in the screen are indicated as:
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 892 / 926
926
• 4 x V11; in the screen are indicated as:
– r01sr1sl11/port#01–#01–v11TTP
• 4 x V24; in the screen are indicated as:
• 1 x phonic interface (voice channel); in the screen are indicated as:
– r01sr1sl11/port#01–#01–q23TTP
Expanding this TP, four referred TPs are presented:
• r01sr1sl11/port#01–#001–q23TTP
These TPs permit to connect the voice channel toward four directions.
– The other boards used to terminate or cross–connect the OH bytes are the STM–n boards.
The OH TP are present in MS, RS and VC4 TP Class.
In these TPs the indication “......#0011 to 0099 (MS or RS) are referred to the coordinates of the
Section OverHead bytes on the SDH frame (1,1 to 9,9).
The voice channel are identified by the “ow” indication, the “FU” is for Future Use, the “NU” is for
National Use, “UC” is for User Channel and “Pass” is for Passthrough channel.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 893 / 926
926
22.5 OH TP creation
Select the Overhead option and then from the cascading menu the OH TP creation option.
The OH TP creation dialog opens (see Figure 622. ) and allows to create the OH TP to cross connect.

In detail, the dialog–box contains the following graphical object:

– a Choose button is used to display a list of OH Tps to be created. The Choose button starts
the TP Search ( see Figure 623. ) with predefined filtering; the TP Search dialog allows the
operator to visualize only not created OH Tps.
To visualize the OH TP in the TP Search view double click on the MS, RS or VC4 Tp.
• OH Tp field displays the label of the selected OH Tp to be created.
Apply button is used to perform a create request of the tp displayed in the OH Tp field. After having
performed the create request, the OH Tp field is set to empty.
Close button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
Figure 622. OH TP creation

1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 623. OH Search TP for creation
3AL 89062 AA AA 894 / 926
926
22.6 OH TP deleting
Select the Overhead option and then from the cascading menu the OH TP deleting option.
The OH TP deleting dialog opens (see Figure 624. ) and allows to delete the OH TP no more involved
in an OH cross–connection.
In detail, the dialog–box contains the following graphical object:
– a Choose button is used to display a list of OH Tps to be deleted. The Choose button starts
the TP Search with predefined filtering; this TP Search dialog allows the operator to visualize
only created and not cross–connected OH Tps.
– OH Tp field displays the label of the selected OH Tp to be deleted.
Apply button is used to perform a delete request of the tp displayed in the OH Tp field. After having
performed the delete request, the OH Tp field is set to empty.
Figure 624. OH TP deleting

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 895 / 926
926
22.7 OH Phone Parameters
The OH phone parameters option permits to configure the telephone number and to manage the
parameter “phonic extension”.

Select the Overhead option and then from the cascading menu the OH Phone Parameters option.
Figure 625. opens.
Figure 625. Phone Parameters dialog window
In the window are presented:
– the interface field (at the top) where can be selected the phonic interfaces to be configured.
It identifies a TP indicated as “q23TTP”, referred to the physical voice connection on the AUX/EOW
or SERVICE or SERGI unit (Considering the 1664SM Rel.3.2 the AUX/EOW is the slot “1” ).
– the phone number field, to set the telephone number for operator call on the phonic interface.
– The phonic extension field, where enable or disable the extension of the selected phonic interface.
If enabled the phonic signal is extended towards the external on the access panel of the NE.
Not operative in current SH release.
Apply button performs the configuration change of the modified phone parameters of the selected phonic
interface without close the dialog
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 896 / 926
926
23 ROUTING MANAGEMENT (NOT AVAILABLE FOR OMSG)
23.1 Overview on Communication and Routing Domain

The purpose of the communication and routing domain is to define configuration parameters concerning
the communication protocols for the local NE, the OS and each other related NE in order to provide a
global communication capabilities inside the network.
A brief description of basic concepts and terms involved in the communication and routing domain follows.
During the TMN design process, a network is partitioned into domains; each domain can consist of a
collection of two types of nodes:
• nodes supporting a link state routing protocol IS–IS; these nodes will be called adaptive
routers; IS–IS protocol floods the network with link state information in order to build a complete
consistent picture of the network topology. Use of IS–IS routing protocol in a TMN facilitates
installation and operation due to the ”self learning” capabilities of these protocols and automatic
network reconfiguration in case of failure; moreover the use of these standardized routing
protocols guarantees interoperability in a multivendor environment.
• nodes not supporting these protocols; these nodes will be called static routers;
Networks partitions consisting of the former type of node will be called adaptive routing domains;
networks partitions consisting of the later type of node will be called static routing domains.
Moreover, a node which has to take routing decisions must become Intermediate Systems, all others can
be made End Systems.
For the description of the following paragraphs use is made of Figure 626. on page 898. It is not a network
planning example, it is only used to describe L1 ,L2, RAP and MESA.
23.1.1 Partitioning into Routing Subdomains
In order to reduce the overhead associated with distributed adaptive routing, it may be useful to divide
an adaptive routing domain into smaller routing subdomains, called areas or level 1 subdomain. A level
1 subdomain should fulfill the following requirements:
• a level 1 subdomain should form a connected subnetwork; this subnetwork should have only
a few links to the outside world, compared with the number of internal links;
• each node must belong to exactly one level 1 subdomain;
• each node which is connected to a foreign level 1 subdomain must become a level 2
intermediate system; level 1 intermediate systems know how to communicate only with IS
in the same area; obviously, there must be at least one level 2 intermediate system per level
1 subdomain;
• Level 2 intermediate systems must form a connected network, because level 1 paths cannot
be utilized for level 2 communication. This network will be called level 2 backbone.
In the most simple case, all nodes within a level 1 subdomain share the same area address.
In general it is allowed to have multiple synonymous area addresses within a level 1 subdomain, even if
the usage of this feature should be checked with Alcatel engineers.
The synonymous list is used to ease partitioning in the future. There is a basic rule, which must be followed
by two neighboring level 1 intermediate systems within a subdomain: there must be at least one area
1AA 00014 0004 (9007) A4 – ALICE 04.10
address in common between their two synonymous list, otherwise they are not able to communicate with
each other.
3AL 89062 AA AA 897 / 926
926
23.1.2 Partitioning into separate Routing Domains
In certain situations it may be desirable to partition a given network into separate routing domains, where
no routing information is exchanged between these domains. The major benefits of this partitioning are

reduction of memory, processing and traffic overhead, because there is no exchange of routing

information between the domains. Communication between separate routing domains must be achieved
through the use of Reachable Address Prefixes (RAP).
A Reachable Address Prefixes represents static routing information. It can only be associated with a link
of a level 2 intermediate system, whereby this link crosses routing domain boundaries. A Reachable
Address Prefixes is handled in the same way as information about a foreign level 1 subdomain within the
own domain. The Reachable Address Prefixes indicates that any packet whose destination network
address NSAP matching the prefix may be forwarded via the link with which the prefix is associated.
For example, consider network which is split into two separate routing domains:
• routing domain A resides in a level 1 subdomain with area address ”a”
• routing domain B resides in a level 1 subdomain with area address ”b”
In order to enable the communication, the Reachable Address Prefixes in routing domain A must contain
the area address ”b” and the Reachable Address Prefixes in routing domain B must contain the area
address ”a”.
On the other hand, within a given level 1 subdomain, there can be some NEs not supporting IS–IS nor
ES–IS protocol (static routing). In such condition, the communication can be achieved through the use
of Manual End System Adjacencies (MESA).
A prerequisite for the use of manual end system adjacencies is that the area addresses of the connected
nodes must be the same; as a consequence the nodes must belong to the same level 1 subdomain.
Within a pure Alcatel network there is no need to use any kind of static routing. Therefore normally RAP
and MESA shall never be used.
AREA (subdomain) 1
L1
L1
L1 L1 L1
L1
L1 L1 L1 L1 L1
L1 L1
L2 L2
L1 L1 with MESA
ÉÉ
ÉÉ L2
AREA (subdomain) 2
L2
L2
L2 L1
with RAP L1
= NE
ÉÉ ÉÉ
L1
L1 with MESA
ÉÉ = NE not supporting IS–IS

ÉÉ L1 AREA (subdomain) 3
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 626. Routing subdomain organization example
3AL 89062 AA AA 898 / 926
926
23.1.3 IP over OSI tunneling for ATM/IP
This feature is applicable to NEs with ATM/IP board.

It consists in using QB3/QECC channels to carry IP link terminated on ATM/IP board (end–node). The
extraction/insertion of IP packets from QB3/QECC channels is performed by EC.

23.1.4 OSI over IP tunneling on QB3

This feature (not operative in current release) allows the Element Manager to reach the GNEs (and all the
relevant NEs behind them) by using IP networking.
This would permit to use an external DCN based on IP only. Hence, no OSI networking would be required
on the external DCN.
OSI over IP technique is used to meet the target. OSI packets leaving the SH are encapsulated into IP
packets within the SH system itself. Hence, packets leaving the SH are IP packets, containing the original
OSI packet.
Once the packet get the NE through a pure IP network, the GNE has to strip off the IP encapsulation,
extracting the OSI packet, and to route the OSI packet as it does today using a pure OSI networking.
Hence, the internal networking of the SDH network (DCCs) is still based on OSI. No IP packets shall flow
inside DCCs, because the GNE receives the IP packet containing the OSI packet, deletes the IP header,
and forwards only the OSI packet on DCCs.
The default OSI lower layers networking can be replaced by IP routing capability at the bottom of the
QB3/QECC communication protocol suite; the choice is software switchable at NE level. The
implementation adopts the RFC1006 standard to put the OSI upper layers on top of IP networking.
The application goal is to offer the TCP/IP transport (i.e. Internet compatibility) in alternative to the full
ISO/OSI communication protocols, in the complete DCN network or at least in a consistent portion of it.
Figure 627. depicts the protocol architecture.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 627. OSI over IP tunneling on QB3
3AL 89062 AA AA 899 / 926
926
23.2 Communication and routing views
To access select Comm/Routing option from the USM “Menu Commands” as indicated in chapter 2.
Here are described all the communication and routing options related to USM 6.x. The same description

can be applied to a reduced option number (different USM type).

The Communication and Routing Views allows to perform, in the USM 6.x, the following operations:
• Local Configuration: definition of the local NE addresses
• OS Configuration: addressing of the main and spare OSs connected to the local NE
• NTP Server Configuration:addressing of the main and spare NTP servers connected to the
local NE
• Interfaces Configuration subdivided in:

– LAPD Configuration: definition of the LAPD port parameters for each LAPD channel
on the local NE
– Ethernet Configuration: definition of configuration parameters needed to manage a

local NE which provides a LAN ethernet interface
• OSI Routing Configuration subdivided in:

– RAP Configuration: configuration of parameters necessary to the addressing of NE
connected by Reachable Address Prefixes in a domain different
from the one of the local NE. These information are stored in
RAP table.
– MESA Configuration: configuration of parameters necessary to the addressing of non

IS–IS NE in the same domain as the one of local NE.
These information are stored in MESA table.
• IP Configuration subdivided in:

– IP Static Routing Configuration: definition of Host/Network destination address for IP
static routing
– OSPC area Configuration: definition of Open Shortest Path First address
– IP Address Config. of Point–to–Point interfaces: definition of the Equipment Controller IP

address
– ISA board IP address: definition of the ISA board IP address
• Tunneling Configuration subdivided in:

– IP over OSI: definition of destination NSAP address and type of IP routing for
IP over OSI tunneling
All the previously cited operation can be entered choosing the relevant menu option.
N.B. Before starting any dialog with OS, the local configuration data must be loaded onto the
NE, directly connecting the SH to the equipment to be configured.
The options are described in next paragraphs.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 900 / 926
926
23.3 Local Configuration
Select the Comm/Routing option and then from the cascading menu the Local Configuration option.
The dialog–box opens (Figure 628. ) and allows to configure the local address of the NE.
The following fields are present:
– a Local Address section contains the following graphical object:
• a Presentation Selector (P.Sel) identifies a presentation entity at the location identified by the
NSAP Address. The presented value must not be modified.
• a Section Selector (S. Selector) identifies a section entity at the location identified by the NSAP
Address. The presented value must not be modified.
• a Transport Selector (T. Sel) identifies a transport entity at the location identified by the NSAP
Address. The presented value must not be modified.
• a Network Service Access Point (NSAP) Address identifies a location in the network. The first
field of the NSAP address, AFI, determines the NSAP format.
The AFI field is 2 characters long (2 exadecimal digits) and, depending on the its value, the
length of NSAP address is variable from 16 characters to 40 characters:
– the value of AFI 49 identifies the local format of variable length (from 16 characters to 40
characters).
– the value of AFI 39 identifies the ISO–DCC format up to 40 characters long.
– the value of AFI 47 identifies the GOSIP–V2 format up to 40 characters long.
In all cases the last two fields of the NSAP address are:
– System Id: uniquely identifies a NE in an area and is 12 characters long.
It might be the equipment MAC Ethernet address, level 2, inserted in the NE (check the
value in the para. 23.7 on page 907) or it might be selected by the operator.
– Network Selector: provides the distinction among users of the network service and is 2
fixed characters long (value is “1D”).
In the view, the NSAP is managed as simple strings of characters without any pre–formatting
because of the variable format:
– a first string of two characters that identifies the AFI field
– a second string of variable length that identifies the remaining NSAP address
– Synonymous Area Addresses section allows to have multiple synonymous area addresses within a
level 1 subdomain. The compilation of the two network addresses is optional and if they are inserted,
the last two fields, System Id and Network Selector, of the mandatory address and of the synonymous
addresses must be the same.
– System Type section determines whether the local NE acts as a “intermediate system level 1” or as
a “intermediate system level 2” or as a “End System”. Note that a level 2 intermediate system
performs functions of a level 1 too. End System is not operative.
Ok button is used to perform a configuration change of the data contained in the dialog–box and closes
it; the dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 901 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 628. Local Configuration
926
3AL 89062 AA AA
902 / 926
23.4 OS Configuration
Select the Comm/Routing option and then from the cascading menu the OS Configuration option.
The dialog–box opens (Figure 629. ) and allows to configure the addresses of the Main and Spare OSs
connected to the local NE.
– Main OS Address section contains the same graphical object of the Local Address Section in the
Local Configuration dialog–box.
– Spare OS Address section contains the same graphical object of the Local Address Section in the
Local Configuration dialog–box.
Figure 629. OS Configuration

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 903 / 926
926
23.5 NTP Server Configuration
Alcatel NTP is a sytem management for the date and time distribution in an Alcatel Network.
Only one NE has to give date and time to all other NE of the network, this is the ”Server”.

Other NE ask this ”Server”; they are ”Clients”. ”Clients” can ask gradualy the ”Server”.

Likewise, it possible to declare a Main NE which is linked to one SH.
Each NE may be ”Server” or ”Client”; and the ”Server” answers to a ”Client”.
The SH is always ”Server”.
Select the Comm/Routing option and then from the cascading menu the NTP Server Configuration
option.
The dialog–box opens (Figure 630. ) and allows to configure the addresses of the Main and Spare NTP
(Network Protocol synchronization Time) Servers connected to the local NE, used for time distribution in
the network.
– Enabling NTP Protocol section allows to enable or disable the NTP Protocol.
– Main NTP Server Address section contains the same graphical object of the Local Address Section
in the Local Configuration dialog–box. In the N Sel. field, leave the default value (mandatory) ”7B”.
– Spare NTP Server Address section contains the same graphical object of the Local Address Section
in the Local Configuration dialog–box. In the N Sel. field, leave the default value (mandatory) ”7B”.
If the NTP server is coincident with the OS (same hardware), the same NSAP address of the
OS must be assigned.
If there are one or two SH connected towards the NE, the ”Server” address is the one of SH
Main and SH Spare. In this case, that is the SH which synchronizes the network, but it is not
mandatory.
When all fields are validated, ANTP Protocol manages automatically the time adjustment.
All information are reported in the NE Time screen.
The OS time can be the SH time.
The ”Client” requests the ”Server” to be adjusted on the reference time.
When the field NTP Protocol is set on enabled (Managed), the Set NE Time with OS Time
function is not operative and the user cannot set manually the NE Time.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 904 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 630. NTP Server Configuration
926
3AL 89062 AA AA
905 / 926
23.6 LAPD Configuration
Select the Comm/Routing option and then ( Interfaces Configuration with USM 6.x and then ) from the
cascading menu the LAPD Configuration option. The same command can applied selecting Port–>

Physical Media menu.

The dialog–box opens (Figure 631. ) and allows to configure a LAPD port of each LAPD channel on the
NE.
The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing
device (upper part of the figure); each page represents a particular LAPD port of Multiplex or Regeneration
Section and the respective pointing device displays the complete user label of the MS/RS TTP’s
associated to the port.
The display of the view can be required directly by the ”port” view containing ”MS/RS” functional blocks;
in this way only the LAPD configuration parameters of the selected MS/RS TTP are displayed
In detail, each page contains the following data:
– LAPD Interface field allows to define or remove a LAPD Port on the selected MS/RS TTP.
– LAPD Role field indicates the role of a defined LAPD Port (User/Network) according the LAPD
protocol.
This connection is a must to establish connection between two NE’s: if one is configured with User
role, the other one connected must be configured with Network role.
Apply button performs a configuration change of the data contained in the selected page.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 631. LAPD Configuration
3AL 89062 AA AA 906 / 926
926
23.7 Ethernet Configuration
Select the Comm/Routing option and then ( Interfaces Configuration with USM 6.x and then ) from the
cascading menu the Ethernet Configuration option.
The dialog–box opens (Figure 632. ) and allows to define the parameters needed to manage a NE which
provide a LAN ethernet interface .
The following fields and data are present:
– Ethernet Interface field allows to define or remove a Local Area Network Port for the access to the
Data Communication Network.
– MAC Address section allows to display the address of the Network Element in the Ethernet LAN;
it is a read–only field.
– OSI Section:
• L2 only Parameter field indicates if the port shall be used for level 2 traffic only, thus avoiding
transmitting L1 packets. Note that the flag shall be set to No if some other nodes (NEs or OSs)
of the same area of the relevant NE are connected to the Ethernet.
One example is indicated in Figure 633. on page 909.
• L1 Default Metric is a not modifiable field , Priority field can be set ( default value for ethernet
is 64)
• L2 Default Metric is a not modifiable field , Priority field can be set ( default value for ethernet
is 64)
– IP Section section allows to define the “node” IP Address, IP Mask and the Routing IP Protocol used;
If “OSPF” or “Both” options of Routing IP Protocol field are selected, also the “Associated OSPF
Area” must be set.
Apply button performs a configuration change of the data.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 907 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
Figure 632. Example of Ethernet Configuration window (USM 6.x)
908 / 926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
LAN
01
No
NE
L2
No
NE
L2
AREA 2
OS
NE
Yes
L2
AREA 1
926
Figure 633. Ethernet Configuration – L2 only parameter
3AL 89062 AA AA
AREA 3
909 / 926
23.8 Reachable Address Prefixes Configuration
Select the Comm/Routing option and then ( OSI Routing Configuration with USM 6.x and then ) from the
cascading menu the RAP option.

The dialog–box opens (Figure 634. ) and allows to configure the Reachable Address Prefix table.

Each element of the RAP table allows to link a LAPD port or a LAN port of the local NE to a separate
domain; the separate domain is selected by the address Prefixes. If the addressed element is the OS, the
LAN port will be used.
device (upper part of the figure); each page represents a particular element of the RAP table and the
respective pointing device displays the element counter.

– Physical Interface button
• if the element is empty, displays the ”none” value and allows to select a LAPD ports or a LAN
port which will be used to reach the addressed area.
• if the element isn’t empty, displays the selected port and allows to change it.
– Area Address Prefix section allows the user to address the separate domain. The Area Address
Prefix represents a NSAP address without the fields System Id and Network Selector.
– MAC Address section allows to address the element of a domain to be reached the Ethernet LAN;
the field is managed as a simple strings of 12 digit.
Apply button is used to perform a configuration change of the data contained in the complete RAP table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 910 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 634. RAP Configuration
926
3AL 89062 AA AA
911 / 926
23.9 Manual ES Adjacencies Table Configuration
Select the Comm/Routing option and then ( OSI Routing Configuration with USM 6.x and then ) from
the cascading menu the MESA option.

The dialog–box opens (Figure 635. ) and allows to configure the Manual ES Adjacencies table.

Each element of the MESA table allows to link a LAPD port or a LAN port of the local NE to a End System
element; the ES element must be in the same area as the one of the local NE. If the addressed element
is the OS, the LAN port will be used.
device (upper part of the figure); each page represents a particular element of the MESA table and the
respective pointing device displays the element counter.

– Physical Interface button
• if the element is empty, displays the ”none” value and allows to select a LAPD ports or a LAN
port which will be used to reach the End System element.
• if the element isn’t empty, displays the selected port and allows to change it.
– System Id section represents the System Id of the ES element.
– MAC Address section allows to address the element in the Ethernet LAN; the field is managed as
a simple strings of 12digit.
Apply button is used to perform a configuration change of the data contained in the complete MESA table
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 635. MESA Configuration
3AL 89062 AA AA 912 / 926
926
23.10 IP Static Routing Configuration (USM 6.x)
Select the Comm/Routing–>IP Configuration and then from the cascading menu, the IP Static Routing
Configuration option.
The dialog–box opens (Figure 636. ) and allows to configure the parameters for IP Static Routing
Configuration.
[1] Destination Host IP Address: allows to define the IP address necessary to reach a specific Host
[2] Destination Network: it is alternative to Destination Host IP Address; allows to define the
IP Address and IP Mask to reach a network.
[3] Default Gateway IP Address: allows to define the address of the next hop gateway
[4] CLNP (Connection Less Network Protocol): allows to use a pre–define IP over OSI tunnel towards
a gateway.
[5] IP Point–to–Point Interface Id: allows to use point to point interfaces made available by EC
N.B. Points from [3] to [5] are alternative
Apply button is used to perform a configuration change of the data contained in the complete table and
close the view; the view is visible until the end of the operations and a wait cursor is displayed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 913 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 636. IP Static Routing Configuration
926
3AL 89062 AA AA
914 / 926
23.11 OSPF Area Table Configuration (USM 6.x)
Select the Comm/Routing–> IP Configuration and then from the cascading menu, the OSPF Area
Table Configuration option.
The dialog–box opens (Figure 637. ) and allows to configure the parameters for OSPF (Open Shortest
Path First) Area Table Configuration.
– OSPF Area IP Address
– OSPF Area Range Mask
Both fields gives a synthetical information that includes all the addresses (specific to a NE and to a
Network) in an Area.
Apply button is used to perform a configuration change of the data contained in the complete RAP table
Figure 637. OSPF Area Table Configuration

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 915 / 926
926
23.12 IP Address Configuration of Point–to–Point Interfaces (USM 6.x)
Select the Comm/Routing –>IP Configuration and then from the cascading menu, the IP Address
Configuration of Point–to–Point Interfaces option.

The dialog–box opens (Figure 638. ) and allows to set the Equipment Controller IP Address used to

communicate with the ISA board.
Figure 638. IP Address Configuration of Point–to–Point Interfaces

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 916 / 926
926
23.13 ISA board IP Address (USM 6.x)
Select the Comm/Routing–>IP Configuration and then from the cascading menu, the ISA Board IP
Address option. The same option can be opened selecting the ISA board in the subrack view and then
“Equipment” and, as before, the ISA Board IP Address option.

The dialog–box opens (Figure 639. ) and allows to set the IP Address of the ISA Board that communicate
with the Equipment Controller (EC).
Figure 639. ISA Board IP Address

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 917 / 926
926
23.14 IP over OSI (USM 6.x)
Select the Comm/Routing–>Tunneling Configuration and then from the cascading menu, the IP over
OSI option.

The dialog–box opens (Figure 640. ) and allows to configure the Destination NSAP Address and the IP

Routing Type.
– Destination NSAP Address:
a Network Service Access Point (NSAP) Address identifies a location in the network. The first
field of the NSAP address, AFI, determines the NSAP format.
The AFI filed is 2 characters long (2 exadecimal digits) and, depending on the its value, the
length of NSAP address is variable from 16 characters to 40 characters:
– the value of AFI 49 identifies the local format of variable length (from 16 characters to 40
characters).
– the value of AFI 39 identifies the ISO–DCC format of 40 characters long.
– the value of AFI 47 identifies the GOSIP–V2 format of 40 characters long.
In all cases the last two fields of the NSAP address are:
– System Id: uniquely identifies a NE in an area and is 12 characters long
It might be the equipment MAC Ethernet address, level 2, inserted in the NE (check the
value in the para. 23.7 on page 907 ) or it might be selected by the operator.
– Network Selector: provides the distinction among users of the network service and is 2
characters long (value is “1d”).
In the view, the NSAP is managed as simple strings of characters without any pre–formatting
because of the variable format:
– a first string of two characters that identifies the AFI field
– a second string of variable length that identifies the remaining NSAP address
– IP Routing:allows to choose the type of IP routing supported as follows;

– OSPF (Open Shortest Path First)
– RIP (Routing Information Protocol)
– Both
– None
If “OSPF” or “Both” options are selected, also the “Associated OSPF Area” must be set.
Apply button is used to perform a configuration change of the data contained in the complete table and
close the view; the view is visible until the end of the operations and a wait cursor is displayed.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 918 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
Figure 640. IP over OS
926
3AL 89062 AA AA
919 / 926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
926
3AL 89062 AA AA
920 / 926
24 EXTERNAL POINTS MANAGEMENT (NOT AVAILABLE FOR OMSG)
This chapter describes how to display and set the input/output environmental alarm (housekeeping alarm),
An external input point is an environmental alarm (also called house keeping alarm). It corresponds to
an external event which is monitored by the NE. Number of relays on the NE are dedicated to check
modification of the environment as for example a fire, a flood, .....
An external output point is used to manage a NE contact (i.e relay) connected to detector. There will be
one instance for each output point supported by the managed element. An external output point is
independent from external input point.
– Displaying external points,

– Expanding or reducing external points list,
– Configuring input and output external points.
24.1 Displaying external points
Select the External Points option from the Views pull down menu as shown in the following figure.
Figure 641. External points option.
Figure 642. opens.

1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 921 / 926
926
Figure 642. Example of external points view (USM 4.x)
The external points view displays a list of all input and output points. The following information is given
for each point:
– the external point type: Input or Output.

– the user label: a user–friendly label associated by the operator to the external point. Some user labels
are configurable (see further the paragraph External points configuration).
– polarity: is used to relate the state of the physical output to the External State attribute. Two types
of output are considered : contact closure and logic level outputs (High = High logic level –or contact
open– or Low = Low logic level –or contact closed–) (available only for some NE types ( i.e. USM
3.x, USM 4.x, 1696MS,...).
– the external state: represents the alarm state. ”On” when the alarm is raised, else ”Off”. If the
external point is active (On), a little flag is represented near the status of the concerned point.
The following information can be available only for “Output” external point types (see further the
1AA 00014 0004 (9007) A4 – ALICE 04.10
paragraph External points configuration):
3AL 89062 AA AA 922 / 926
926
– output criteria: automatic or manual control of the external output points. In automatic control the
external output points are driven by defined events. In manual control the external output points are
driven by the operator.
24.1.1 Expanding or reducing external points list.
The external points view displays a complete list of the external points but it can also be restricted to the
input or to the output points.
To see either the input points, the output points or all the external points, select the appropriate option from
the External Points pull down menu as shown in the following figure.
Figure 643. Expanding or reducing the external points list.
24.2 External points configuration
The configuration operations available on external points are:
• user labels configuration

• polarity configuration (Low or High= default configuration)
• external state. Can be set for output points (ON or OFF=default configuration)
• change of the associated Output Criteria. Only for External Output point
• change of associated Probable Cause. Only for External Input points (fixed to ”Housekeeping
Alarm”).
To configure an external point, click on the concerned row and then select the Configuration option from
the External Points pull down menu as shown in the following figure.
1AA 00014 0004 (9007) A4 – ALICE 04.10
Figure 644. Configuring external points.
3AL 89062 AA AA 923 / 926
926
The following dialogue box is then opened, displaying information about the selected external point (Input
or Output).

Figure 645. External input point configuration dialogue box example.
Figure 646. External output point configuration dialogue box example.

1AA 00014 0004 (9007) A4 – ALICE 04.10
Opening the dialog the current state of the selected External Point is shown.
3AL 89062 AA AA 924 / 926
926
The External Point Configuration dialogue box enables you to give a name to the external point by entering
the user–friendly label in the User Label:
in input this field can be indicate the associated event that must be taken under check (for example
precence of water or fire in the room where the Equipment is placed) entry box.
in output this field can indicate the alarm detected or the action that must be executed if a specific event
occur (for example a “Pump” activation when water is present in the room where the equipment is placed).
External state can be set for output points, and force the output to ON (alarm) or OFF value.
The Probable Cause field, used for the External Input Point, is fixed to “Housekeeping Alarm” .
The Output Criteria option menu presents the criteria to associate to the External Output point.
Possible options are the following:
• Manual: associated to an output command, that can be forced to ON or OFF

For example the output contact could be used to “Manually” activate a pump to drain water
from the room where the equipment is placed ; in this case is also necessary to set the option
“On” in the field “External State”.
• Flexible: It is possible to define from SH the couple event/CPO#, where the event is chosen
between a set of Output Criteria (LOS, RDI, LOF,...) and to specify the STM–N interface which
the Output Criteria refers to by clicking on Choose button; subsequently the TP search dialog
box will be opened.
When the configuration of the external point is completed, click on the OK push button to validate the
choice and close the dialogue box. The Cancel push button cancels the configuration and closes the
dialogue box.
1AA 00014 0004 (9007) A4 – ALICE 04.10
3AL 89062 AA AA 925 / 926
926
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
END OF DOCUMENT
926
3AL 89062 AA AA
926 / 926
LABELS AND ASSEMBLY INSTRUCTIONS
TARGHETTE E INFORMAZIONI PER IL CENTRO STAMPA
QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
COD.MANUALE HDBK P/N: 3AL 89062 AAAA Ed.01
1350NM
1353NM
Release 7.0 on NR5 EQP. SPEC. OPERATOR’S HDBK
VOL.1/3
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
– No PAGINE TOTALI PER ARCHIVIAZIONE: 940+6=946
– DIMENSIONE BINDER SORGENTE (du –ks): 446.681 KBytes
INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

AVVERTENZA – WARNING
IL MANUALE COMPLETO È COSTITUITO DA TRE VOLUMI – QUESTO È IL VOL.1/3
THE COMPLETE HANDBOOK IS COMPOSED BY THREE VOLUMES – THIS IS VOL.1/3
– STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
– COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:

HANDBOOK COMPOSITION AND ASSEMBLY:
No pagine numerate
fase
(facciate) numbered
step
No pages da from a to
1 TARGHETTE VOL.1/3 - LABELS VOL.1/3
2 PRIMO FRONTESPIZIO VOL.1/3 - FIRST FRONT VOL.1/3 2
3 INSERIRE SEPARATORE ’1’ - INSERT REGISTER ’1’
4 SC.1.1: HANDBOOK GUIDE 12 1/12 12/12
5 INSERIRE SEPARATORE ’2’ - INSERT REGISTER ’2’
6 SC.1.2: Q3–NE MANAGEMENT 88 1/88 88/88
7 ASSEMBLARE VOL.2/3 e 3/3 – ASSEMBLE VOL.2/3 and 3/3
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 940

1AA 00014 0004 (9007) A4 – ALICE 04.10
TOTALE FOGLI A4 TOTAL A4 SHEETS: 470
ED 01 VOL.1/3 RELEASED
3AL 89062 AAAA TQZZA Y 1/ 6
6
WARNING FOR A-UNITS OTHER THAN A-ITALY
• Labels are done according to A-Italy binder format.

• Source files: ALICE 6.10

INFORMAZIONI EDITORIALI
– ORIGINALE SU FILE: ALICE 6.10

• sistemazione ’figlist’
SE SI RIFÀ IL tocustom: ELIMINARE I BODY INDEX E IL LORO RIFERIMENTO NEI toc
3AL 89062 AAAA

Ed.01
1350NM
1353NM
Release 7.0 on
Equipment mgmt for Alcatel NE supported by 1350 in NR 5.x

NR5 EQP. SPEC. OPERATOR’S HDBK
1AA 00014 0004 (9007) A4 – ALICE 04.10
6
QUESTA PAGINA NON VA INSERITA NEL MANUALE
THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
Site
VIMERCATE FCG
Originators 1353RM
V.Porro
H.Hottenbacher NR5 EQP–SPEC. OPER.HDBK
RELEASE 7.0 ON
Domain : OND
Division : NM
Rubric : 1353NM
Type : 1353NM NR5 EQP–SPEC. OPERATOR’S HANDBOOK
Distribution Codes Internal : External :
Approvals
Name V.Scortecci
App.
Name L.Foresta
App.
1AA 00014 0004 (9007) A4 – ALICE 04.10
6
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
VOL.1/3 RELEASED
6
3AL 89062 AAAA TQZZA
Y
4/ 6
1350NM
1353NM

Release 7.0 on
VOL.1/3
1350NM
1353NM
Release 7.0 on

VOL.1/3
1350NM
1353NM
Release 7.0 on
3AL 89062 AAAA Ed.01 NR5 EQP. SPEC. OPERATOR’S HDBK VOL.1/3
1350NM 1353NM
Equipment mgmt for Alcatel NE supported by 1350 in NR 5.x Release 7.0 on
1350NM
1353NM
Release 7.0 on
1AA 00014 0004 (9007) A4 – ALICE 04.10
6
1AA 00014 0004 (9007) A4 – ALICE 04.10
ED
01
VOL.1/3 RELEASED
6
3AL 89062 AAAA TQZZA
Y
FINE DEL DOCUMENTO INTERNO – END OF INTERNAL DOCUMENT
6/ 6

1353NM Equipment Specific - Operator's Handbook Vol.1 - 3

Caricato da

Informazioni sul documento

Titolo originale

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

1353NM Equipment Specific - Operator's Handbook Vol.1 - 3

Caricato da

Copyright:

Formati disponibili

NR5 Equipment Specific Operator’s Handbook

3AL 89062 AAAA Ed.01

3 LIST OF NES SUPPORTED BY 1353NM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 1353NM NR5 EQUIPMENT SPECIFIC HANDBOOK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

01 040130 V.SCORTECCI ITAVE V.PORRO ITAVE

ED 01 SC. 1.1: HANDBOOK GUIDE

1.1 General information

1.2 Handbook applicability

PRODUCT ANV P/N

PRODUCT RELEASE VERSION (N.B.) ANV P/N

N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS

ED 01 SC. 1.1: HANDBOOK GUIDE

VERSIONS AS INTERNAL DOCUMENTS

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

ED Creation Scope Archived

01 January 2004 Creation YES

1.3.1 Notes on Ed.01

ED 01 SC. 1.1: HANDBOOK GUIDE

2.1 Handbooks related to the product’s software

REF HANDBOOK ANV Part No.

[1] 1353NM Rel.7.0 Operator’s Handbook 3AL 89061 AAAA

[2] 1353 NM NE LIST Handbook 3AL 89063 AAAA

ED 01 SC. 1.1: HANDBOOK GUIDE

Refer to WS supplier handbooks.

not permitted without written authorization from Alcatel.

All rights reserved. Passing on and copying of this

• Harmful optical signals

• Moving mechanical parts

• Heat–radiating Mechanical Parts

– ELECTROSTATIC DISCHARGERS (ESD)

ED 01 SC. 1.1: HANDBOOK GUIDE

4 1353NM NR5 EQUIPMENT SPECIFIC HANDBOOK

4.1 Contents of Volume 1/3

SECTION 1.1: HANDBOOK GUIDE (This document)

4.1.1 Q3 NEs Management Part 1

SECTION 1.2: Q3 NEs Management (2nd generation Q3 NEs)

ED 01 SC. 1.1: HANDBOOK GUIDE

4.2.1 Q3 NEs Management Part 2

not permitted without written authorization from Alcatel.

SECTION 2.2: 1674 LAMBDA GATE ALARM REFERENCE Manual

4.2.2 QB3* NEs Management – ADM & Microwave

SECTION 2.3: QB3* NE MANAGEMENT Manual

SECTION 2.4: QB3* NE TRANSMISSION MANAGEMENT Manual

SECTION 2.5: QB3* NE SYNCHRONIZATION MANAGEMENT Manual

SECTION 2.6: QB3* NE PERFORMANCE MONITORING MANAGEMENT Manual

SECTION 2.7: QB3* NE SOFTWARE MANAGEMENT Manual

SECTION 2.8: ADM MANAGEMENT Manual

SECTION 2.9: OAS AND OA-TPD MANAGEMENT Manual

ED 01 SC. 1.1: HANDBOOK GUIDE

SECTION 2.11: SDH MICROWAVE MANAGEMENT Manual

SECTION 2.12: PDH MICROWAVE MANAGEMENT Manual

ED 01 SC. 1.1: HANDBOOK GUIDE

4.3.1 1st generation terrestrial WDM and Submarine NEs

not permitted without written authorization from Alcatel.

SECTION 3.2: WDM 2.x TERRESTRIAL MANAGEMENT Manual

SECTION 3.3: WDM SUBMARINE PFE Manual

SECTION 3.4: WDM SUBMARINE OALW16 AND OALW40 Manual

SECTION 3.5: WDM SUBMARINE OALW40 (TERA10) Manual

SECTION 3.6: WDM SUBMARINE OALW40 (TERA10) Alarms Manual

SECTION 3.7: WDM SUBMARINE URW 1666UT / OA Manual

SECTION 3.8: SNMP MELODI Manual