1662smc 2.7 Oper - HDBK

Operator Handbook
Alcatel 1662SMC
STM4/16 Compact Multiservice Node
1662SMC Rel.2.7
3AL 98325ADAA Ed.02

3AL 98325ADAA Ed.02
Alcatel 1662SMC Rel2.7 Operator Handbook
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization.
Alcatel 1662SMC Rel2.7
Handbook Guide
02 09/01/2009 Creation Chen Yu
ED DATE CHANGE NOTE APPROVED BY PREPARED BY
Distribution: Internal External

√
ED 02 SC 1: HANDBOOK GUIDE
3AL 98325 ADAA 1/15
1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK ································································3
1.1 General information ························································································································3
1.2 Handbook applicability···················································································································3
1.3 Purpose of the handbook···············································································································3
1.4 Handbook configuration check ·····································································································4
1.4.1 Notes on Ed.01 ·····························································································································4
2 PRODUCT-RELEASE HANDBOOKS ······································································································5

3 SAFETY NORMS AND LABELS ··············································································································8

3.1 First aid for electric shock ·············································································································8
3.2 Norms and labels ····························································································································8
4 HANDBOOK DESCRIPTION ····················································································································9
5 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION ································································12

5.1 Products, product-releases, versions and Customer Documentation····································12
5.2 Handbook supply to Customers··································································································12
5.3 Aims of standard Customer Documentation··············································································12
5.4 Handbook Updating ······················································································································12
5.4.1 Changes introduced in the same product-release (same handbook P/N) ·································13
5.4.2 Supplying updated handbooks to Customers·············································································13
5.4.3 Changes due to a new product-release······················································································13
5.5 Customer documentation supply on CD-ROM···········································································14
5.5.1 Contents, creation and production of a CD-ROM·······································································14
5.5.2 Use of the CD-ROM····················································································································14
5.5.3 CD-ROM identification ················································································································15
5.5.4 CD-ROM updating ······················································································································15
3AL 98325 ADAA 2/15
1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK
1.1 General information
WARNING
ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims the implied
warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liable for errors
contained herein or for damages, whether direct, indirect, consequential, incidental, or special, in connection
with the furnishing, performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for information purposes
only and are subject to change without notice. They do not represent any obligation on the part of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied, reproduced or
disclosed to a third party without written consent.
1.2 Handbook applicability
This handbook applies to the following product-releases:
PRODUCT ANV P/N FACTORY P/N

1662SMC 3AL 98001 AAAA --
PRODUCT RELEASE VERSION(N.B.) ANV P/N FACTORY P/N
1662SMC 2.7 3AL 98002 ALAA --
For further information on the Alcatel software product and its physical distribution support refer to the
“Introduction” section.
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.
1.3 Purpose of the handbook
This handbook describes the operations concerning commissioning, operation and maintenance that the
operators must carry out as indicated by the specific software application(s) referred to in this handbook
This handbook must be used together with the associated Technical Handbook (see Table 1.) and the
1320CT associated documentation (see Table 5.) does not replicate information contained into it.
In particular, all cautions relevant to safety, rules for EMC and ESD, as well as warnings regarding
operations that may cause damages to the equipment, are not duplicated here, but must be retrieved from
the Technical Handbook.
3AL 98325 ADAA 3/15
When using this handbook it is assumed that the Operators know:
• The structure (hardware composition) and all the possible operating modes of the equipment
(product-release) this handbook refers to.
• How to use a PC and the Windows ambient applications
1.4 Handbook configuration check
This handbook is a collection of documents (each contained in a specific section) that can have
editions different from one another.
The Edition of the whole handbook is that of section 1 (HANDBOOK GUIDE).
The edition of the enclosed documents indicated in the following table is that of the corresponding original
internal document.
HANDBOOK EDITION 01 02 03 04 05
REGISTER AND SECTION TITLE SECTION EDITION
1 HANDBOOK GUIDE n
2 INTRODUCTION MANUAL n
3 NE MANAGEMENT MANUAL n
4 MAINTENANCE MANUAL n
5 SIBDL MANUAL n
1.4.1 Notes on Ed.01

Ed.01 issued on Mar 2009 is the first released and validated version of the handbook.
.
3AL 98325 ADAA 4/15
2 PRODUCT-RELEASE HANDBOOKS
The list of handbooks given here below is valid on the issue date of this Handbook and can be
changed without any obligation for ALCATEL to update it in this Handbook.
Some of the handbooks listed here below may not be available on the issue date of this
Handbook.
The standard Customer Documentation in the English language for the equipment whose product-release-
version is stated in para.1.2 consists of the following handbooks:

Table 1. Handbooks related to the specific product hardware
REF HANDBOOK ANV Part No. FACTORY THIS HDBK

Part No.
1662SMC Rel.2.7 Technical 3AL 98325 AAAA
Handbook
[1]
Provide information regarding Equipment description, Maintenance, Hardware
setting documentation
1662SMC Rel.2.7 Installation 3AL 98325 ABAA
Handbook
[2]
Provide information regarding Equipment Installation
1662SMC Rel.2.7 Turnup & 3AL 98325 ACAA

Commissionig Handbook
[3] Provide information regarding Equipment Turn-On, Test and Operation
Table 2. Handbooks related to the specific product SW management and local product control

Part No. Or note
1662SMC Rel.2.7 3AL 98325 ADAA --
CT Operator’s Handbook
[4] Provides 1662SMC “SDH” Craft Terminal screens and operational procedures
3AL 98325 ADAA 5/15
Table 3. Handbooks related to ATM specific product SW

Part No. Or note
[5] ATM Rel.1.0 Operator’s Handbook 3AL 80730 AAAA 957.140.552 J
[6] ATM Rel.1.2 Operator’s Handbook 3AL 80814 AAAA 957.140.652 W

Provides ATM SMART Terminal screens and operational procedures

Table 4. Handbooks related to IP specific product SW

Part No. Or note
[7] IP Rel.1.0 3AL 81062 AAAA 957.140.722 L
Operator’s Handbook
Provides ATM SMART Terminal screens and operational procedures
Table 5. Handbooks common to Alcatel Network Elements using 1320CT platform

Part No.
1320CT 3AL 79186 AAAA 957.130.542 E
[8] Basic Operator’s Handbook
Provides general information and operational procedures common to all 1320CT
(Craft terminal) of Alcatel InfoModel Network Elements.
1330AS Rel.5.1 Operator’s 3AL 71079 AAAA 957.130.442 A
Handbook
Provides detailed information and operational procedures regarding the alarm

Surveillance software embedded in the 1320CT software package. Information
[9]
about Historical Alarms and Network Element Symbols Management (Physical
Network Management) are not valid for Craft Terminal. They are only used by
Network Management.
ELM Rel.5.0 Operator’s Handbook 3AL 71081 AAAA 957.130.462 E
[10] Provide detailed information and operational procedures regarding the Event
Log Management software embedded in the 1320CT software package.
3AL 98325 ADAA 6/15
Table 6. Documentation on CD-ROM
REF CD-ROM TITLE ANV Part No. FACTORY Part No.
1662SMC Rel.2.7 CD-ROM-DOC 3AL 98326AAAA

EN
[11]
Contains, in electronic format, the following handbooks: REF. [1] to [4] Envisaged after the
release of all handbooks
1320CT BASIC CD-ROM-DOC EN 3AL 79549 AAAA 417.100.031
[12] Contains, in electronic format, the following handbooks: REF. [8] to [10]
ATM Rel.1.1 CD-ROM DOC EN 3AL80739 AAAA 417.100.060

[13]
Contains, in electronic format, the following handbooks: REF. [5] Envisaged after the release of
all handbooks
[14] ATM 1.2 CD-ROM-DOC EN 3AL 80815 AAAA 417.100.068
Contains, in electronic format, the following handbook: REF. [6]
[15] IP 1.0 CD-ROM-DOC EN 3AL 81063 AAAA 417.100.084

Contains, in electronic format, the following handbook: REF. [7]
Table 7. Optional handbooks common to 16xxSM

Part No.
S9-16xxSM 3AL 78901 AAAA 955.100.692 N
[16] System Installation Handbook
Provides general installation rules necessary to install the Optinex family
equipment in the S9 Rack.
Optinex RACK-16xxSM System 3AL 38207 AAAA 955.110.202 L
Installation Handbook
[17]
Provides general installation rules necessary to install the Optinex family
equipment in the Optinex Rack.
N.B. Handbooks REF. [16] and [17] are available only on paper support
3AL 98325 ADAA 7/15
3 SAFETY NORMS AND LABELS
3.1 First aid for electric shock
Do not touch the patient with bare hands until the circuit has been opened.
Open the circuit by switching off the line switches. If that is not possible, protect yourself with dry material
and free the patient from the conductor.
ARTIFICIAL RESPIRATION
It is important to start mouth-to-mouth resuscitation at once and seek doctor help immediately.
TREATMENT OF BURNS
This treatment should be used after the patient has regained consciousness. It can also be employed while
the artificial respiration is being applied (in this case there should be at least two persons present).
WARNING:
• Do not attempt to remove his clothing from the burnt parts;
• Apply dry gauze on the burns;
• Do not apply ointments or other oily substances.
3.2 Norms and labels
Refer to the Technical Handbook associated to ALCATEL’s designed and manufactured equipment to
obtain the following information:
- 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
Identical or similar information on Personal Computer, Work-Station etc., other than ALCATEL’s, loaded
with software applicative described in this Handbook, is supplied in the Constructor’s technical
documentation.
3AL 98325 ADAA 8/15
4 HANDBOOK DESCRIPTION
This handbook is composed of the following Manuals:

SECTION 1: HANDBOOK GUIDE (This document)
The Handbook Guide gives general information on the application and use of the Handbook. The
Handbook Guide includes the following chapters:
- Chapter 1:Handbook structure and configuration check. This chapter gives information on the whole
handbook application, composition and evolution.
- Chapter 2: Product-release handbooks. This chapter lists the handbooks the Operator should have
in order to carry out the tasks allowed by the specific product-release this handbook refers to.
- Chapter 3: Safety norms and labels

- Chapter 4: Handbook description
- Chapter 5: General on Alcatel Customer Documentation
SECTION 2: INTRODUCTION Manual
The Introduction Manual describes the main features of the graphical interface and provides a general
overview of the system architecture and the different functionalities provided by the Craft Terminal. The
Introduction Manual includes the following chapters:
- Chapter 1: Introduction. This chapter gives the structure of this manual.
- Chapter 2: General description of the Craft Terminal. The Craft Terminal is introduced and the
software product listed. The Craft Terminal main functionality in the NE management (EML-USM)
are listed and briefly described.
- Chapter 3: Acronyms and abbreviations. The acronyms used in all the operator manuals are listed.
- Chapter 4: Glossary of terms. Definitions concerning the acronyms.
SECTION 3: NETWORK ELEMENT MANAGEMENT Manual
The aim of this document is to describe the Craft Terminal view, inserting operative information.
The Network Element Manual includes the following chapters:
- Chapter 2: General introduction on views and menus. The view organization is presented and the
menus available listed and briefly described.
- Chapter 3: NE management supervision. This chapter is dedicated to the NE states and NE access.
- Chapter 4: NE management general configuration. In this chapter general configuration referred to
the equipment management are described (CT access, NE Time, Alarm Configuration etc).
- Chapter 5: Security Management. In this chapter configuration referred to the Security management
are described (ACD level and Manager list).
- Chapter 6: External input and output points management. This chapter describes how to display and
set the input/output environmental alarm (housekeeping alarm).
- Chapter 7: Diagnosis management. In this chapter are specified: access to the Alarm Surveillance to
show the alarm condition, abnormal condition list (as result of operator’s command), access to the
Event and Alarm Log file and Internal Link Monitor.
- Chapter 8: Communication and Routing management. In this chapter are presented the
communication and routing parameters, concerning the OSI and IP communication protocols for the
3AL 98325 ADAA 9/15
local NE, the OS and each other related NE in order to provide a global communication capabilities
inside the network
- Chapter 9: Equipment management. This chapter deals mainly with the setting and changing of the
boards present on the Equipment and undertaking board protection operations.
- Chapter 10: Board view. This chapter permits to show the physical port available in a specific board
(alarm synthesis and port symbol), to access the port and to change the physical interface.
- Chapter 11: Port view. This chapter permits to set and show the transmission resources referred to
the Port.
- Chapter 12: Equipment protection management. This chapter permits to manage the EPS protection,
setting the relevant configuration.
- Chapter 13: Multiplex Section protection management. This chapter permits to manage the MSP
protection.
- Chapter 14: Transmission view. This chapter permits to show and set the Termination Point of the
equipment, thus having an overview of the complete signal flow of the various port.
- Chapter 15: Cross connection management. This chapter permits to manage the connection of the
paths.
- Chapter 16: Overhead management. This chapter permits to manage the Overhead, setting the
relevant configuration.
- Chapter 17: Performance Monitoring management. This chapter permits to set and show
Performance Monitoring parameters and data.
- Chapter 18: Synchronization management. This chapter permits to set and show Synchronization
parameters and status.
- Chapter 19: MS–SPRing Management. This chapter permits to set the MS–SPRing protection of the
NE
- Chapter 20: ISA/IP/ETH Configuration. This chapter describes the operations necessary for the ATM
boards creation and the ATM/IP/ETH TTPs creation.
- Chapter 21: Software management. This chapter permits to update the NE by means download
procedure and to manage NE software.
SECTION 4: NETWORK ELEMENT MAINTENANCE Manual
This document aims at introducing the Maintenance procedure, inserting information useful to identify alarms
and troubleshoot the NE. The Maintenance Manual includes the following chapters:
- Chapter 2: Maintenance introduction. List the maintenance steps.
- Chapter 3: Maintenance of the Personal Computer. The Personal Computer manual is referred.
- Chapter 4: Problems with Craft terminal. Shut Cdown and restart of the PC is indicated.
- Chapter 5: Troubleshooting (Corrective Maintenance). Detection location and correction of failure are
presented.
- Chapter 6: Unit replacement with spare. The replacement procedure is detailed.
- Chapter 7: Upgrading with New Hardware. The Hardware upgrading procedure is detailed.
SECTION 5: SIBDL Manual
This document describes the download procedure with SIBDL. The SIBDL Manual includes the following
chapters:
3AL 98325 ADAA 10/15
- Chapter 1: Introduction
- Chapter 2: Download with SIBDL configuration
- Chapter 3: Configuration for SIBDL
3AL 98325 ADAA 11/15
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.
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.
5.4 Handbook Updating
The handbooks associated to the “product-release” are listed in para.2.

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),
3AL 98325 ADAA 12/15
- The handbook issue date. The date on the handbook does not refer to the date of print but to the
date on which the handbook source file has been completed and released for the production.
5.4.1 Changes introduced in the same product-release (same handbook P/N)

The edition and date of issue might change on future handbook versions for the following reasons:
- Only the date changes (pointed out in the Table of Contents) when modifications are made to the
editorial system not changing the technical contents of the handbook.
- The edition, hence the date, is changed because modifications made concern technical contents. In
this case:
• The table in para.1.4 on page 5 indicates the section(s) edition change;
•
In each section, the main changes with respect to the previous edition are listed;
•
In affected chapters of each section, revision bars on the left of the page indicate
modifications in text and drawings (this is done after the first officially released and validated
version).
Changes concerning the technical contents of the handbook cause the edition number increase (e.g. from
Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition of a
version character (e.g. from Ed.02 to Ed.02A).
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operator’s Handbooks) are not modified
unless the new software “version” distributed to Customers implies man-machine interface hanges
or in case of slight modifications not affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the product-release’s
“version” marking, they are not replaced in the handbooks related to a subsequent version, if the
screen contents are unchanged.
5.4.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 change the handbook P/N and the edition start from 01. In this case the modified
parts of the handbook are not listed.
3AL 98325 ADAA 13/15
5.5 Customer documentation supply on CD-ROM
In the following “CD-ROM” means Customer Documentation on “CD-ROM”
5.5.1 Contents, creation and production of a CD-ROM

In most cases, a “CD-ROM” contains the documentation of one product-release(-version) and for a certain
language.
In some other cases, the same “CD-ROM” can contain the documentation of different Product-release (-
version) s for a certain language.
As a general rule:
CD-ROMs for Network Management products do not contain:

The Installation Guides

The documentation of system optional features that Customers could not buy from Alcatel together with the
main applicative SW.
CD-ROMs for Network Elements products do not contain the documentation of system optional features (e.g.
System Installation Handbooks related to racks that Customers could not buy from Alcatel together with the
main equipment).
A CD-ROM is obtained collecting various handbooks and processing them by
Interleaf-World-View-Press after the manual addition of some hyperlinks that make the navigation through
the various handbooks easier. No additional information is added to each handbook; so that the
documentation present in the CD-ROMs is exactly the same the Customer would receive on paper.
The files processed in this way are then transferred on a PC where the viewer (Interleaf-World-View) is
added and a master CD-ROM is recorded.
Suitable checks are made in order to have a virus-free product.
After a complete functional check, the CD-ROM image is electronically transferred to the archive of the
Production Department, so that the CD-ROM can be produced and delivered to Customers.
5.5.2 Use of the CD-ROM

The CD-ROM can be used both in PC and Unix WS environments.
The minimum configuration for World View (Rel.2.2.2) utilization on a PC is:
- Operative System: Windows 95 or Windows NT 4
- Processor: Pentium
- RAM: 32 Mbyte
- Disk space: 20Mbyte
The set-up procedure is present in the booklet included in the CD-ROM box.
After the set-up procedure, which installs the viewer in the PC or Unix WS environment, the Customer is
allowed to read the handbooks on the PC/WS screen, using the navigation and zooming tools included in the
viewer, and to print selected parts of the documentation through a local printer.
N.B. Copyright notification
WorldView: Copyright 1981-1996

INTERLEAF Inc.
3AL 98325 ADAA 14/15
All rights reserved.
The use of WorldView is permitted only in association with the files contained
in the CD-ROMs officially supplied by Alcatel.
Alcatel documents: All rights reserved.
Passing and copying of documents and files contained in the CD-ROMs
officially supplied by Alcatel, use and communication of its contents are not
permitted without written authorization from Alcatel.
5.5.3 CD-ROM identification

Each CD-ROM is identified:

1) By the following external identifiers, that are printed both on the booklet and the CD-ROM upper
surface:
- The name of the “product-release(s)” (and “version” when the CD-ROM is applicable to the
versions starting from it, but not to the previous ones),
- A writing indicating the language(s),
- The CD-ROM P/N (Factory P/N 417.xxx.xxx x and ANV P/N),
- The CD-ROM edition (usually first edition=01)
2) And, internally, by the list of the source handbooks and documents (P/Ns and editions) by whose
collection and processing the CD-ROM itself has been created.
5.5.4 CD-ROM updating

The list of source handbook/document P/Ns-editions indicated in previous para.5.5.3 point 2), in association
with the CD-ROM’s own P/N-edition, is also loaded in the Alcatel-Information-System as a structured list.
Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive system, the
Alcatel-Information-System automatically rises a warning toward the Customer Documentation department,
indicating the list of CD-ROMs that must be updated to include the new editions of these
handbooks/documents.
This causes the planning and creation of a new edition of the CD-ROM.
Updating of CD-ROMs always follows, with a certain delay, the updating of the single handbooks composing
the collection.
END OF DOCUMENT
3AL 98325 ADAA 15/15
Introduction

√
ED 02 SC.2:Introduction
3AL 98325 ADAA 1/15
LIST OF FIGURES AND TABLES ....................................................................................................................3
1 INTRODUCTION .......................................................................................................................................4
1.1 Scope················································································································································4
1.1.1 Document scope...........................................................................................................................4
1.1.2 Target audience............................................................................................................................4
1.2 Reading rules ··································································································································4
1.2.1 Menu options ................................................................................................................................4
2 GENERAL DESCRIPTION OF THE CRAFT TERMINAL ........................................................................5

2.1 Introduction ·····································································································································5

2.2 Alcatel software product and licence delivered to the customer ··············································5
2.2.1 Software product and licences description ...................................................................................5
2.2.2 Software products and licences list and part numbers.................................................................6
2.3 Craft Terminal main functionalities in the NE management·······················································6
2.3.1 Network Element management supervision .................................................................................6
2.3.2 Network Element general configuration........................................................................................7
2.3.3 Security Management...................................................................................................................7
2.3.4 External input and output point management...............................................................................7
2.3.5 Diagnosis management ................................................................................................................7
2.3.6 Communication and routing management....................................................................................7
2.3.7 Equipment and board management .............................................................................................8
2.3.8 Port management .........................................................................................................................8
2.3.9 Protection management................................................................................................................8
2.3.10 Transmission management ......................................................................................................8
2.3.11 Cross Connection management...............................................................................................9
2.3.12 Performance monitoring management .....................................................................................9
2.3.13 Synchronization management..................................................................................................9
2.3.14 ISA port Configuration ..............................................................................................................9
2.3.15 Software management .............................................................................................................9
3 ACRONYMS AND ABBREVIATIONS ....................................................................................................10
4 GLOSSARY OF TERMS .........................................................................................................................12
3AL 98325 ADAA 2/15
LIST OF FIGURES AND TABLES
TABLES
Table 1. Software products part numbers ..........................................................................................................6
Table 2. Software licence part numbers.............................................................................................................6
3AL 98325 ADAA 3/15
1 INTRODUCTION
1.1 Scope
1.1.1 Document scope

The Introduction Manual presents the Craft Terminal main functions and provides a general overview of the
different functionalities provided by the ELM–USM of the Craft Terminal for Info Model NE.
1.1.2 Target audience

The Introduction Manual is intended for all users.
The documents that should be read before starting this document are:
– 1320CT Basic Operator’s Handbook
1.2 Reading rules
1.2.1 Menu options

All the manuals describe menus, but not necessarily all the options of these menus. When a menu option is
not detailed in a manual, the information is surely given in another manual.
3AL 98325 ADAA 4/15
2 GENERAL DESCRIPTION OF THE CRAFT TERMINAL
2.1 Introduction
The Craft Terminal is a project in charge of the local management of single network elements, providing
ITU– compliant Information Model Interface to the Network Element.
Multiple NE management up to 32 Network elements is possible obtaining a remote Craft Terminal
application.
The general information of the Craft Terminal are presented in the Basic Craft Terminal Operator’s
Handbook, which the operator has to read before this Handbook.
In the Basic Craft Terminal Operator’s Handbook are described all the general description of use, navigation,
rules, etc, common to all the NE using the same Craft Terminal.
Further, the same handbook contains the detailed description of common operations as “Installation” and
common screens as “Network Element Synthesis view”.
The Network Element Synthesis view is the first view presented to the operator entering the application.
Starting from this view it is possible login the NE and than enter the EML–USM views.
This Operator’s Handbook deals with the EML–USM views of the Craft Terminal, which directly
permit to manage the Network Element.
The management main functions of the EML–USM are inserted at para. 2.3.
A detailed description of the EML–USM screens is given in Section Ne Management of this handbook.
From the Craft Terminal is possible to run another Specific Software application. This application is in charge
of the ATM and IP management inside the NE such as ATM/IP cross–connection, Backup and Restore
configuration files etc.
Details information about Specific Application are described in the relevant Operator’s Handbook (see
Section 1 HANDBOOK GUIDE for the code).
The list and part numbers of the SDH software products distributed by Alcatel is inserted in para.2.2.
The Craft Terminal characteristic (computer configuration) are listed in the Basic Craft Terminal Operator’s
Handbook.
2.2 Alcatel software product and licence delivered to the customer
2.2.1 Software product and licences description

The software products are distributed by Alcatel in a CD–ROM.
In this CD–ROM are contained:
Software packages for NE management by means of the craft terminal
Software package of the NE, to be installed in the NE or update the NE (by means of download function)
The software package used for management permits the dialogue between craft terminal and NE, to realize
all the functions of the NES and EML–USM.
The software package used for updating the NE must be installed on the PC and then downloaded on the
NE, thus following product evolution.
Alcatel typically offers several software licenses on the software product (only one for this equipment)
They are referred both to the Network Element software features and to the Craft Terminal software features.
3AL 98325 ADAA 5/15
2.2.2 Software products and licences list and part numbers
Every Software Product is identified by a denomination and a part number, listed on the following table.
Table 1. Software products part numbers
Name ANV Part Number N.B.

DCP 1662SMC R 2.7 CD–ROM 3AL 98326 AAAA
Every Software licence is identified by a denomination and a part number, listed on the following table.
Table 2. Software licence part numbers

Name ANV Part Number N.B.

SWL-UPGRADE NODE 1662SMC TO REL 2.7 3AL98312ACAA
SWL-OMSN METRO VERS. "A" ATM LP 8DG15540AAAA
SWL-OMSN METRO VERS. "A" ETH LP 8DG15540ABAA
SWL-OMSN METRO VERS. "A" TDM LP 8DG15540ACAA
SWL-OMSN METRO VERS. "A" WDM LP 8DG15540ADAA
SWL ENH ETH (ES1): OAM, LAG, IGPM 8DG15540AEAA
SNOOP, PORT MIRROR
SWL ENH ETH (ES4): OAM, LAG, IGMP 8DG15540AFAA
SNOOP, POT MIRROR
SWL ENH ETH (ES16): PING OAM, EPS, FX I/F 8DG15540AGAA
SWL ENH ETH (ES16): OAM, LAG, SRV 8DG15540AHAA
DELIMITING, PORT MIRROR
2.3 Craft Terminal main functionalities in the NE management
In this chapter, are described the main functionalities of the Craft Terminal, referred to the Network Element
management views, obtained by means EML–USM. The functionalities constitute the heading of each of the
paragraphs below.
2.3.1 Network Element management supervision

Deals with the NE state and access.
3AL 98325 ADAA 6/15
2.3.2 Network Element general configuration
Deals with the general configuration of the equipment.
– Craft Terminal access state (allow or inhibit)
– NE Time management
– Alarms Configuration
Alarm Severity Assignment Profile management,
Allow/Inhibit alarm notification,
Alarm re-synchronization.
– Restart NE
2.3.3 Security Management

Deals with the security configuration of the equipment.
– Set Manager list
– Set ACD level
2.3.4 External input and output point management

Deals with housekeeping signals input from the external (station alarms) or forwarded (output) towards the
external.
– Display External points
– Configure External points
2.3.5 Diagnosis management

For real time alarm reporting and subsequent fault localization and correction.
– Alarm Surveillance
The alarms concerning a particular managed entity will be represented in a synthetic way in all the views
concerning the entity.
Alarms information are detailed in the Alarms Surveillance Manual
– Abnormal Condition list (as result of operator’s commands)
– Event log Manager
Permits to have access to the Event Log file.
– Remote Inventory (”upload” and “view” remote inventory)
–Internal Link Monitor
2.3.6 Communication and routing management

This deals with the configuration parameters concerning the communication protocols for the local NE, the
OS and each other related NE. Different types of protection can be managed:
– Local NE and OS addresses
– NTP configurations
– LAPD, Ethernet, MESA, RAP configurations
3AL 98325 ADAA 7/15
– IP Configuration
– Tunneling Configuration
2.3.7 Equipment and board management

Deals with the presentation of the equipment and the hierarchical tree structure, permitting to define the
types of boards present. The Board view permits to access the Port view.
– Set / modify / remove boards
– Software information of the selected board.
– Remote Inventory
2.3.8 Port management

This permits to set and show the transmission resources (TP) referred only to the port (SDH, PDH, HOA
ATM and IP).
It is used to check the detailed alarm of each TP and to configure them (many options are the same of the
Transmission view).
For each port a specific menu is available where various configuration of the specific port can be set, for
example:
– Automatic Laser Shutdown
– MSP protection
– Loopback management and configuration
– Single fiber configuration
– TP Frame Mode Configuration
– Retiming
– Ethernet Port Configuration
Port view is also the entry point of other “management functions”:
– Performance Monitoring management
– Cross Connection management
For each port are presented:
– The various ITU–T functional blocks (i.e. PPI, RST, VC4).
– Details of alarm and state condition
– TP role, connection, etc. information
2.3.9 Protection management

This deals with the protection mechanism that is possible to configure in the NE. Different types of protection
can be managed:
– Equipment protection switching
– Multiple Section Protection
2.3.10 Transmission management

This permits to cover the management of the transmission resources, opening the views of all the specific
ports of the NE (SDH and PDH).
3AL 98325 ADAA 8/15
It supplies an overview of the complete signal flow.
For all the ports are presented:
– The various ITU–T functional blocks (i.e. PPI, RST, VC4).
– Synthesis of alarm and state condition
– TP role, connection, etc. information
For each port a specific menu is available similar to the Port view where various configuration of the specific
port can be set.
Also Transmission view is than the entry point of other “management functions” .
2.3.11 Cross Connection management

This deals with the connection of all the Termination Point (TP), which are the starting and terminating points
of a transmission segment. In this way the multiplex structures are created, managing the traffic flow. Similar
operation are made on the Overhead cross connections.
– Create / modify cross connections
– Activate / deactivate / switch cross connections
2.3.12 Performance monitoring management

This function deals with the set up, collect, log and display performance data associated with the managed
NE according ITU–T G.826.It consists of a set of functions that evaluate and report on the behavior of the
NEs and their effectiveness relating to the communications taking place on the Network.
– Set up the Performance Monitoring thresholds
– Collect and display Performance Monitoring data
– Performance monitoring history
2.3.13 Synchronization management

Deals with the management of the timing.
– Timing source, SSU, T0, T4, T5 and T6 configuration
– Protection commands
2.3.14 ISA port Configuration

Describes the operations necessary for the ATM/PR_EA/ETH, DVB-ASI and ISA BCE boards and the
ATM/PR_EA/ETH, DVB-ASI and ISA BCE TPs creation.
2.3.15 Software management

Deals with the manipulation of the software package within NE.
– Software download refers to the NE software, permitting to charge the software in the relevant NE to
upgrade the NE software, thus following product evolution, or as a consequence of substitution with a spare.
– Back–up and restore on the MIB of the NE.
3AL 98325 ADAA 9/15
3 ACRONYMS AND ABBREVIATIONS
AIS: Alarm Indication Signal

APS: Automatic Protection Switching
ASAP: Alarm Severity Assignment Profile
ASI: Asynchronous Serial Interface
ATM: Asynchronous Transfer Module
BNC: Bayonet Not Coupling
CD–ROM: Compact Disc Read Only Memory
CCITT: Telegraph and Telephone International Consultative Committee

CT: Craft Terminal

DCN: Data Communications Network
DVB: Digital Video Broadcast
ECC: Embedded Communication Channels
EML: Element Management Layer
EPS: Equipment Protection Switching
FAD: Functional Access Domain
Gbit/s: Gigabits per second
GNE: Gateway Network Element
HMI: Human Machine Interface
IEEE: Institute of Electrical and Electronics Engineers
IM: Information Manager
Kbit/s: Kilobits per second
LAN: Local Area Network
LVC: Lower Order Virtual Container
MAC: Media Access Control
Mbit/s: Megabits per seconds
MIB: Management Information Base
MS: Multiplex Section
MSP: Multiplex Section Protection
NAD: Network Access Domain
NAP: Network Access Point
NE: Network Element
NML: Network Management Layer
NTP: Network Time Protocol
OS: Operation System
3AL 98325 ADAA 10/15
PI: Physical Interface
SD: Signal Degrade
SF: Signal Failure
TMN: Telecommunications Management Network
TN: Telecommunications Network
TP: Termination Point
USM: User Service Manager
XC: Cross–Connection
3AL 98325 ADAA 11/15
4 GLOSSARY OF TERMS
Acknowledgment:
When an alarm is taken into account by the application, the operator has to acknowledge it to point out that
he has seen it and that he will react in the right way. During alarm configuration it is possible to set a
maximum delay for alarm acknowledgement. The operator can decide whether or not the alarm clear has to
be acknowledged.
Administrator:
A user who has access rights to all the Management Domains of the Craft Terminal product. He has access
to the whole network and to all the management functionalities.
Alarm:
An alerting indication to a condition that may have an immediate or potentially negative impact on the state
of an equipment or the CT. An alarm is characterized by an alarm begin and an alarm end.
Alarm Severity Assignment Profile:
Function allowing the assignment of severities to the alarms depending on their probable causes.
Alarm Status:
Identifies the type and severity of an occurring alarm.
Board:
A board is part of an NE. They are electronic cards that fit into slots in the NE.
Compact Disk Read Only Memory:
Data saving support from which the information can only be read. Is useful for stocking data due to its
available memory space.
Craft Terminal:
Workstation or Personal computer (PC) from which local address to an NE is possible. It can be used to
configure or perform monitoring tasks on the NE.
Cross–connection
Cross–Connections provide the network with the Routing Capabilities, this is the possibility of routing one
signal to a particular destination.
Digital Communication network:
Communication Network in which the transmission of data is done in a digitized format.
Embedded Communication Channel:
Communication channel used in conjunction with packet commuting networks (X25) to manage distant SDH
networks. These communication channels are related to the QECC* protocols.
Element Management Layer:
This application is responsible for the configuration and management of Network Elements.
Equipment Protection Switching:
Used to provide protection for cards within an equipment to protect traffic in the event of card failure.
Filter:
They are related to the alarms or events generated on an NE or internally within the OS itself. They can be
configured by an operator to reject specified types of notifications and limit the processing that is applied to
3AL 98325 ADAA 12/15
them.
Flushing:
This deals with logs. When a log is flushed, all its records are deleted.
Functional Access Domain:
It defines the range of functions which are available to a specified user.
Gigabits per second:
Unit that corresponds to the transmission of 10 9 bits every second.
Gateway Network Element:
It is a Network Element devoted to the control, from the OS, of those NEs providing a QECC* interface. To
do this it uses a QB3* interface and performs the conversion QB3* .QECC*.
Human Machine Interface:

It is the graphical user interface application through which the operators interact with the system.
History Report:
This function enables operators to get information concerning performances, security or alarms on entities
composing the network, or on the network itself. The operator specifies the time period for which he requires
the report.
International Telegraph and Telephone Consultative Committee:
Standard organization for telecommunications. Now called the ITU–T (International Telecommunication
Union).
Kilobits per second:
Unit that correspond to the transmission of 10 3 bits every second.
Line Terminal:
A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can
undertake signal conversion functions (adapting a signal to two different transmission media) or
multiplexing/demultiplexing functions.
Logs:
Logs are files used to store history data concerning the incoming notifications, operator commands and
system alarms. The size of the log can be configured.
Management Domain:
The Craft Terminal product is partitioned into management domains for functional proposes. Each
management domain is associated with functionalities that enable the operators to manage the NEs.
Media Access Control Address:
Represents the Level 2 address for Local Area Networks.
Megabits per second:
Unit that corresponds to the transmission of 10 6 bits every second.
Multiplexer:
Equipment used to combine several signals to produce a single signal at a higher transmission rate and to
decompose it back to the smaller rate signals.
Multiplex Section:
3AL 98325 ADAA 13/15
In general, represents the section containing the multiplexed signals.
Network Access Domain:
Defined as a set of Network Elements. NADs are used to define the set of Network Elements that a user can
manage.
Network Element:
Either a telecommunication equipment or groups parts of a Telecommunication Network. Have
characteristics compliant with CCITT recommendations.
Network Management Level:
Designates the management functions performed on networks elements assembled in a network.
Notification:
Spontaneous data received by the system concerning an NE.

Operation System:
A system dedicated to the supervision of NEs in a standard way, using protocols and interfaces. it offers to
the operator a set of functions necessary to supervise the NEs. The 1353SH is an Operation System.
Operator:
The end–user of the Craft Terminal. He supervises a part of the network that is dependant on his user profile.
Physical Interface:
Electrical or Electrical/Optical transformers that decouples the line signals and adapt the form of signal for
further transmission. This functional block also manages clock extraction, signal loss monitoring and
loopback functions.
Port:
A physical point at which the Network Element can be attached to a transmission medium. A port is either a
termination point or an origination point.
Repeater:
Equipment used to regenerate a signal when it has travelled a long distance.
Severity:
Linked to alarms, severities indicate the magnitude related to the failure.
Telecommunication Management Network:
Defines the concept of interoperable management of TNs. They provide an organized network structure to
achieve the interconnection of the different components of the TN and the services to process the
information.
Telecommunication Network:
Describes the network to be managed. Provides the transmission, the transport and the switching supports
to the interconnected Network Elements.
Terminal Point:
Describes either the origin or the termination of a signal in equipment. Is related to a port.
Thresholding:
This is the assignment of a specified value to monitored parameters (for example Bit Error Rates) that, when
exceeded, generate trouble indications.
3AL 98325 ADAA 14/15
User Profile:
Identifies the functionalities of the Craft Terminal to which a user has access. A finite number of predefined
user profiles is determined by a fixed set of FADs. To give user access to Craft Terminal functionality, the
administrator must assign a profile to a UNIX user account by choosing one among the predefined profiles
installed with Craft Terminal.
User Service Manager:
These are presentation processes used by the Craft Terminal to manage the Human Machine Interface and
facilitate the interaction with the product.
Wrapping:
Wrapping is the technique that enables the most recent entries in a file to replace the oldest when a file is full.
END OF DOCUMENT
3AL 98325 ADAA 15/15

NE Management

√
ED 02 SC.3: NE MANAGEMENT
3AL 98325 ADAA 1/386
1 INTRODUCTION .....................................................................................................................................21
1.1 Scope··············································································································································21
1.1.1 Document scope.........................................................................................................................21
1.1.2 Target audience..........................................................................................................................21
1.2 Terminology···································································································································21
1.2.1 Acronyms and abbreviations ......................................................................................................21
1.2.2 Glossary of terms........................................................................................................................21
2 GENERAL INTRODUCTION ON VIEWS AND MENUS.........................................................................22

2.1 EML--USM view organization ·······································································································22

2.2 Introduction on the EML--USM menu options············································································23
2.2.1 Views menu introduction.............................................................................................................25
2.2.2 Configuration menu introduction.................................................................................................25
2.2.3 Diagnosis menu introduction ......................................................................................................26
2.2.4 Supervision menu introduction ...................................................................................................27
2.2.5 MS-SPRing menu introduction ...................................................................................................27
2.2.6 Download menu introduction ......................................................................................................27
2.2.7 Equipment menu introduction .....................................................................................................27
2.2.8 Board menu introduction.............................................................................................................28
2.2.9 Port menu introduction................................................................................................................28
2.2.10 EPS menu introduction...........................................................................................................30
2.2.11 Transmission menu introduction ............................................................................................30
2.2.12 Synchronization menu introduction ........................................................................................32
2.2.13 External Points menu introduction..........................................................................................33
2.3 Advices on Navigation principles ·······························································································37
3 NE MANAGEMENT SUPERVISION .......................................................................................................40

3.1 NE management states·················································································································40
3.2 NE supervision and login ·············································································································40
4 NE MANAGEMENT GENERAL CONFIGURATION ..............................................................................42

4.1 Access state (allow or inhibit NE Craft access)·········································································42
4.1.1 Switching from the OS to the Craft Terminal access state.........................................................42
4.1.2 Switching from the Craft Terminal access state back to the OS access state ...........................43
4.2 NE Time management···················································································································43
4.3 Alarm Configuration ·····················································································································45
4.3.1 Procedure to modify an ASAP ....................................................................................................45
4.3.2 Alarm Severity Assignment Profile Management (ASAP) ..........................................................45
3AL 98325 ADAA 2/386
4.3.3 Set SdhNE Alarms Severities .....................................................................................................49
4.3.4 Allow/Inhibit Alarms Notifications................................................................................................50
4.3.5 Alarms re—synchronization........................................................................................................51
4.3.6 Alarms persistency Configuration ...............................................................................................52
4.4 Restart NE······································································································································53
5 SECURITY MANAGEMENT ...................................................................................................................54

5.1 Set Manager list·····························································································································54
5.2 Set ACD level·································································································································54
6 EXTERNAL INPUT AND OUTPUT POINTS MANAGEMENT ...............................................................56

6.1 Displaying external points ···········································································································56

6.1.1 Expanding or reducing external points list..................................................................................58
6.2 External points configuration ······································································································58
7 DIAGNOSIS MANAGEMENT .................................................................................................................61

7.1 Alarms surveillance ······················································································································61
7.2 Abnormal Condition List ··············································································································63
7.3 Internal Link Monitor·····················································································································64
7.4 Log Browsing ································································································································66
7.5 Remote Inventory··························································································································66
7.5.1 Upload remote Inventory ............................................................................................................66
7.5.2 View Remote Inventory...............................................................................................................68
8 COMMUNICATION AND ROUTING MANAGEMENT............................................................................70

8.1 Overview on Communication and Routing Domain ··································································70
8.1.1 OSI Protocol on QB3/Qecc.........................................................................................................70
8.1.2 Partitioning into separate Routing Domains ...............................................................................71
8.1.3 IP over OSI tunneling for ATM/IP ...............................................................................................72
8.1.4 OSI over IP tunneling on QB3 ....................................................................................................72
8.2 Communication and routing views ·····························································································73
8.3 Local Configuration ······················································································································75
8.4 OS Configuration ··························································································································76
8.5 NTP Server Configuration ············································································································77
8.6 LAPD Configuration······················································································································79
8.7 DCC Cross Connection ················································································································82
8.8 Ethernet Configuration ·················································································································87
8.9 Reachable Address Prefixes Configuration ···············································································89
8.10 Manual ES Adjacencies table Configuration··············································································90
8.11 IP Configuration ····························································································································91
3AL 98325 ADAA 3/386
8.11.1 IP routing configuration for ATM/IP boards management ......................................................91
8.12 IP Static Routing Configuration···································································································91
8.13 OSPF Area Table Configuration ··································································································92
8.14 IP Address Configuration of Point-to-Point Interfaces ·····························································93
8.15 ISA board IP Address ···················································································································94
8.16 OSI over IP ·····································································································································95
8.17 IP over OSI ·····································································································································95
9 Equipment Management .......................................................................................................................97

9.1 Introduction and navigation·········································································································97
9.2 Set and change or remove board/subrack ···············································································100

9.3 Connect Fan to CONGI board ····································································································106

9.4 Board administrative state ·········································································································107
9.4.1 Setting a board in service .........................................................................................................107
9.4.2 Setting a board out of service ...................................................................................................107
9.4.3 Consulting a Board's Administrative state ................................................................................108
9.5 Software description···················································································································108
9.6 Remote Inventory························································································································109
9.7 Digital Diagnostic Monitoring (DDM) ························································································111
9.8 Show supporting equipment······································································································112
10 BOARD VIEW........................................................................................................................................113
10.1 Introduction ·································································································································113
10.2 Board View Menu ························································································································115
10.2.1 Port Access ..........................................................................................................................115
10.2.2 Change Physical Interface ...................................................................................................116
10.2.3 Show supporting equipment.................................................................................................117
11 PORT VIEW...........................................................................................................................................118
11.1 Introduction ·································································································································118
11.2 Port View: elements on the TP ··································································································119
11.3 Port View Menu ···························································································································121
11.4 Set Retiming ································································································································121
11.5 AU4 Concatenation ·····················································································································123
11.6 Physical Media option menu······································································································125
11.6.1 Automatic Laser Shutdown Configuration............................................................................126
11.6.2 Show Optical Configuration..................................................................................................128
11.6.3 Single Fibber Configuration..................................................................................................129
11.6.4 Ms Configuration ..................................................................................................................130
3AL 98325 ADAA 4/386
11.6.5 Line Length Configuration ....................................................................................................131
11.6.6 Ethernet Port Configuration..................................................................................................131
11.6.7 Ethernet Mapping Protocol...................................................................................................134
11.6.8 Control Path Activation.........................................................................................................134
11.6.9 LCAS Configuration..............................................................................................................136
11.7 TP Frame Mode Configuration···································································································140
11.8 Show Supporting Board ·············································································································143
11.9 Navigate to Transmission View ·································································································144
11.10 Navigate to Monitoring View ······································································································146
11.11 Port Mode Overview····················································································································147

12 Equipment Protection management (EPS) .......................................................................................149

12.1 Introduction ·································································································································149
12.2 Management: consulting and modifying EPS··········································································149
12.3 Configuration: revertive and WTR for EPS···············································································154
12.4 Switching EPS ·····························································································································155
12.5 EPS Overview ······························································································································156
13 Multiplex Section Protection Management .......................................................................................161

13.1 Architecture types·······················································································································161
13.2 MSP Options Introduction··········································································································161
13.3 MSP Create ··································································································································162
13.4 MSP Management ·······················································································································165
13.4.1 MSP modification..................................................................................................................166
13.5 MSP Delete···································································································································167
13.6 Display of Protection State ········································································································168
13.7 MSP Commands··························································································································170
13.8 MSP overview ······························································································································172
14 TRANSMISSION VIEW .........................................................................................................................177

14.1 Overview ······································································································································177
14.2 View elements ·····························································································································178
14.3 View Layout ·································································································································178
14.3.1 View Description...................................................................................................................178
14.3.2 Number of TPs Displayed in Transmission View .................................................................179
14.3.3 Naming TPs..........................................................................................................................179
14.3.4 Dynamic View Behaviour .....................................................................................................180
14.4 Transmission view access and menu·······················································································180
14.5 Add TP··········································································································································181
14.5.1 TP Search.............................................................................................................................181
3AL 98325 ADAA 5/386
14.6 TP Configuration ·························································································································188
14.6.1 High Order TP Configuration................................................................................................188
14.6.2 J0 Section Trace management ............................................................................................190
14.6.3 Low Order TP Configuration.................................................................................................190
14.7 TP Frame Mode Configuration···································································································193
14.8 TP Threshold Configuration·······································································································194
14.9 Terminate/Disterminate TP·········································································································195
14.9.1 Terminate TP........................................................................................................................195
14.9.2 Disterminate TP....................................................................................................................195
14.10 Monitoring Operations················································································································196

14.10.1 Creation/Deletion..................................................................................................................196
14.10.2 Configuration ........................................................................................................................198
14.11 Structure TPs·······························································································································200
14.12 Loopback ·····································································································································200
14.12.1 Loopback Configuration .......................................................................................................200
14.12.2 Loopback Management........................................................................................................203
14.13 Physical Media ····························································································································205
14.13.1 Set Domain...........................................................................................................................206
14.14 Navigation Commands ···············································································································207
14.14.1 Expand .................................................................................................................................207
14.14.2 Hide ......................................................................................................................................207
14.14.3 Show Supported Board ........................................................................................................208
14.14.4 Navigate to Port View...........................................................................................................208
14.14.5 Navigate to HOA Port...........................................................................................................210
15 Cross-Connection Management.........................................................................................................211
15.1 Introduction ·································································································································211
15.1.1 Overview...............................................................................................................................211
15.1.2 Multiplex Structures for SDH ................................................................................................211
15.1.3 Definition of Termination Points (TP) ...................................................................................214
15.1.4 Mapping Tables: TP Names.................................................................................................218
15.1.5 Cross-Connection Types......................................................................................................219
15.1.6 Cross-Connection Protection ...............................................................................................221
15.2 Operative Sequence to execute Cross-Connections ······························································223
15.3 Cross-Connections management······························································································227
15.3.1 Search Criteria......................................................................................................................228
15.3.2 Cross-Connection List ..........................................................................................................230
3AL 98325 ADAA 6/386
15.3.3 Actions available...................................................................................................................232
15.4 Create/Modify Cross-Connections ····························································································232
15.4.1 Cross-Connection Parameters .............................................................................................233
15.4.2 Create a Cross-Connection..................................................................................................237
15.4.3 Modify a Cross-Connection ..................................................................................................241
15.5 Activate/Deactivate/Delete Cross-Connections ·······································································243
15.5.1 Activate a Cross-Connection................................................................................................243
15.5.2 Deactivate a Cross-Connection............................................................................................243
15.5.3 Delete a Cross-Connection ..................................................................................................243
15.6 Split and Join Cross-Connections ····························································································244

15.6.1 Split a Cross-Connection......................................................................................................244

15.6.2 Join Two Cross-Connections ...............................................................................................245
15.7 Protection Switching ··················································································································246
15.8 Print ··············································································································································247
15.9 Show Cross-Connected TPs ······································································································248
16 OVERHEAD MANEGEMENT ...............................................................................................................250

16.1 Introduction ·································································································································250
16.2 OH Connection overview············································································································250
16.3 Overhead views···························································································································251
16.4 OH Cross Connection·················································································································252
16.5 OH TP creation ····························································································································256
16.6 OH TP deleting ····························································································································258
16.7 OH Phone Parameters ················································································································259
17 Performance Monitoring .....................................................................................................................260

17.1 Introduction ·································································································································260
17.1.1 Overview...............................................................................................................................260
17.1.2 Supported Performance Counters........................................................................................260
17.1.3 Far End (FE) and Near End (NE) Performance Counting....................................................261
17.1.4 Bidirectional Counting (24 h Bi) for QoS ..............................................................................262
17.1.5 End to End (e-e 24h) Performance Counting.......................................................................262
17.1.6 Performance Monitoring on AU-PJE ....................................................................................263
17.1.7 Tandem Connection Termination (TCT) and Monitoring (TCM) ..........................................263
17.1.8 Performance Monitoring on 2 Mbit/s ISDN–PRA .................................................................263
17.1.9 Performance Data Collection ...............................................................................................263
17.1.10 Data Collection .....................................................................................................................264
17.1.11 Performance Monitoring History...........................................................................................265
3AL 98325 ADAA 7/386
17.1.12 Thresholds............................................................................................................................265
17.2 Configuration ( SDH Port ) ·········································································································266
17.3 Performance Monitoring on ETHRNET port ·············································································269
17.3.1 Overview...............................................................................................................................269
17.3.2 Ethernet physical interface counters ....................................................................................270
17.3.3 Aggregate counter ................................................................................................................270
17.3.4 Flow counter .........................................................................................................................271
17.4 Display Current Data ( SDH Port ) ·····························································································272
17.5 Display History Data ( SDH Port )······························································································274
17.6 PM Threshold Table Selection ( SDH Port )··············································································276

17.7 PM Threshold Table Creation / Modification / Display ( SDH Port )·······································278

17.7.1 Creation ................................................................................................................................278
17.7.2 Modification ..........................................................................................................................280
17.7.3 Display..................................................................................................................................280
17.8 Configuration (Ethernet port)·····································································································281
17.9 Display current Data (Ethernet port) ·························································································282
17.10 Display history Data (Ethernet port) ·························································································284
17.11 PM Overview································································································································285
18 Synchronization management............................................................................................................288
18.1 Introduction ·································································································································288
18.2 Synchronization Management ···································································································290
18.2.1 Displaying the Synchronization View ...................................................................................290
18.2.2 Synchronization View ...........................................................................................................291
18.2.3 Timing Source Configuration................................................................................................293
18.2.4 Synchronization Protection Commands ...............................................................................296
18.2.5 Synchronization Configuration for T0/T4 and T4 squelch criteria ........................................297
18.2.6 SSU Configuration................................................................................................................298
18.2.7 Remove Timing Reference...................................................................................................299
18.2.8 Change T4 <-> T5 ................................................................................................................299
18.2.9 Change 2MHz ->2Mbit .........................................................................................................301
18.2.10 Set and Remove T0 Equal T4 ..............................................................................................302
18.2.11 Transmission of SSM Quality Configuration ........................................................................302
18.2.12 Show Timing Source ............................................................................................................303
19 MS-SPRING MANAGEMENT ...............................................................................................................304

19.1 MS-SPRING introduction············································································································304
19.2 MS-SPRING connection configuration advices ·······································································304
3AL 98325 ADAA 8/386
19.2.1 2-Fiber MS-SPRING connection configuration advices .......................................................304
19.3 Operative sequence to configure MS-SPRING·········································································304
19.3.1 Operative sequence to configure 2-Fiber MS-SPRING .......................................................304
19.4 MS-SPRING Management···········································································································305
19.4.1 MS-SPRing Main Configuration ...........................................................................................306
19.4.2 Squelching table with 2 fiber Terrestrial applications ...........................................................309
19.4.3 Activate, Deactivate and Delete commands ........................................................................315
19.5 MS-SPRING Protection Status and Commands for 2 fiber terrestrial application ···············316
19.5.1 2F MS-SPRing protection commands ..................................................................................316
19.5.2 External commands (2F) ......................................................................................................317

19.5.3 2F MS-SPRing dual protection commands ..........................................................................324

19.5.4 2F Protection Status Visualization........................................................................................328
20 ISA Port Configuration ........................................................................................................................349

20.1 Introduction ·································································································································349
20.2 ATM/PR_EA/Ethernet board TTPs creation··············································································349
20.2.1 ATM boards ..........................................................................................................................349
20.2.2 PR_EA boards......................................................................................................................352
20.2.3 10/100 Mbit/s fast ETHERNET board ..................................................................................354
20.2.4 Gigabit/s ETHERNET board.................................................................................................357
20.2.5 ES1-8FE boards ...................................................................................................................358
20.2.6 ES4-8FE boards ...................................................................................................................360
20.2.7 ISA-ES16 board....................................................................................................................363
20.2.8 DVB-ASI board .....................................................................................................................366
20.2.9 BCE-ETH board....................................................................................................................369
20.2.10 Interworking Configuration ...................................................................................................372
21 Software Management.........................................................................................................................374
21.1 Generalities and descriptions····································································································374
21.1.1 Naming Conventions ............................................................................................................374
21.2 Software download operative sequence ··················································································375
21.2.1 Software Download upgrade ................................................................................................375
21.2.2 NE Software package installation procedure .......................................................................376
21.2.3 Procedure .............................................................................................................................376
21.3 Software Download Manager menu ··························································································381
21.4 Init download ·······························································································································382
21.5 SW package Activation and Units information ········································································383
21.6 Mib management·························································································································385
3AL 98325 ADAA 9/386
FIGURES
Figure 1. EML--USM main view organization ............................................................................................23
Figure 2. Menu options flow chart -- 1 .......................................................................................................34
Figure 3. Menu options flow chart – 2........................................................................................................35
Figure 6. NE EML-USM Main view ............................................................................................................41

Figure 7. NE management: setting the access state. ................................................................................42

Figure 8. Consulting and/or setting the local NE time................................................................................43
Figure 9. NE Time dialogue box ................................................................................................................44
Figure 10. Configuring Alarm Severity Assignment Profile..........................................................................46
Figure 11. ASAPs Management dialogue box.............................................................................................46
Figure 12. ASAP Edition dialogue box.........................................................................................................47
Figure 13. Set ASAP dialogue box. .............................................................................................................48
Figure 14. Set SdhNE Alarms Severities .....................................................................................................50
Figure 15. Inhibit alarm notification ..............................................................................................................50
Figure 16. Allow alarm notifications .............................................................................................................51
Figure 17. Alarm re--synchronization...........................................................................................................51
Figure 18. Alarms persistency Configuration Menu option ..........................................................................52
Figure 19. Alarm persistency Time Configuration........................................................................................52
Figure 20. Restart NE confirmation..............................................................................................................53
Figure 21. Set Manager list..........................................................................................................................54
Figure 22. Set ACD level..............................................................................................................................55
Figure 23. Opening the external points view................................................................................................56
Figure 24. External points view....................................................................................................................57
Figure 25. Expanding or reducing the external points list............................................................................58
Figure 26. Configuring external points. ........................................................................................................58
Figure 27. External input point configuration dialogue box..........................................................................59
Figure 28. External output point configuration dialogue box (MANUAL) .....................................................59
Figure 29. External output point configuration dialogue box (FLEXIBLE) ...................................................60
Figure 30. Alarm Surveillance Menu............................................................................................................61
Figure 31. Alarm Surveillance......................................................................................................................62
Figure 32. Abnormal condition menu option ................................................................................................63
Figure 33. Example of abnormal condition list.............................................................................................63
3AL 98325 ADAA 10/386
Figure 34. Example of loopback dialog window management.....................................................................64
Figure 35. Internal Link Monitor ...................................................................................................................65
Figure 36. Internal Link Monitor for stand-by Matrix when not synchronized ..............................................65
Figure 37. Log Browsing option in Network Element context view..............................................................66
Figure 38. Remote Inventory confirmation request......................................................................................67
Figure 39. Remote Inventory completed......................................................................................................67
Figure 40. View Remote Inventory...............................................................................................................68
Figure 41. Routing sub domain organization example ................................................................................71
Figure 42. OSI over IP tunneling on QB3 ....................................................................................................73
Figure 43. Comm/Routing options ...............................................................................................................74

Figure 44. Local Configuration.....................................................................................................................76

Figure 45. OS Configuration ........................................................................................................................77
Figure 46. NTP Server Configuration...........................................................................................................78
Figure 47. Creation LAPD Interface.............................................................................................................80
Figure 48. TP search dialog.........................................................................................................................80
Figure 49. LAPD Configuration dialog .........................................................................................................81
Figure 50. Confirmation to change LAPD Role............................................................................................81
Figure 51. Select DCC Cross Connection ...................................................................................................82
Figure 52. Cross Connection Management for DCC dialog ........................................................................83
Figure 53. Main Cross Connection for DCC dialog......................................................................................84
Figure 54. Search for DCC Cross Connection Input view ...........................................................................85
Figure 55. Complete searching for input and output TP ..............................................................................86
Figure 56. Update DCC Cross Connection list by clicking Search icon ......................................................86
Figure 57. Ethernet Configuration................................................................................................................88
Figure 58. Ethernet Configuration -- L2 only parameter ..............................................................................88
Figure 59. RAP Configuration ......................................................................................................................89
Figure 60. MESA Configuration ...................................................................................................................90
Figure 61. IP Static Routing Configuration...................................................................................................92
Figure 62. OSPF Area Table Configuration .................................................................................................93
Figure 63. IP Address Configuration of Point-to-Point Interfaces ................................................................93
Figure 64. ISA Board IP Address.................................................................................................................94
Figure 65. OSI over IP Tunneling configuration...........................................................................................95
Figure 66. IP over OS ..................................................................................................................................96
Figure 67. Equipment Overview -- Subracks levelz.....................................................................................98
Figure 68. Equipment Overview -- Rack level (without Fans subrack)........................................................98
Figure 69. Equipment Overview- Rack level (with Fans subrack) ...............................................................99
3AL 98325 ADAA 11/386
Figure 70. Equipment Overview - NE level ..................................................................................................99
Figure 71. Equipment menu.......................................................................................................................100
Figure 72. The list of different boards relative to an NE slot (example).....................................................101
Figure 73. Modify the module ....................................................................................................................103
Figure 74. The list of different types of optical module (example1) ...........................................................103
Figure 75. The list of different types of optical module (example2) ...........................................................104
Figure 76. Connect FAN to CONGI ...........................................................................................................106
Figure 77. Remove FAN connection from CONGI.....................................................................................107
Figure 78. Consulting a board’s administrative state.................................................................................108
Figure 79. Software Description dialogue box. ..........................................................................................109

Figure 80. Remote Inventory menu ...........................................................................................................109

Figure 81. Remote Inventory dialogue box ................................................................................................110
Figure 82. Select Printer ............................................................................................................................110
Figure 83. Select Output Format for file.....................................................................................................110
Figure 84. select the DDM option ..............................................................................................................111
Figure 85. Digital Diagnostic Monitoring dialog box...................................................................................112
Figure 86. Equipment Overview -- Subrack level ......................................................................................112
Figure 87. Equipment view: select the SDH port on a board.....................................................................113
Figure 88. Example of a Board View .........................................................................................................114
Figure 89. Example of a Port identification and alarm synthesis ...............................................................114
Figure 90. Board menu options..................................................................................................................115
Figure 91. After “Port Access” selection (example) ...................................................................................116
Figure 92. Change Physical Interface........................................................................................................116
Figure 93. Change Physical Interface dialog box ......................................................................................116
Figure 94. Subrack level ............................................................................................................................117
Figure 95. Example of a SDH Port View....................................................................................................119
Figure 96. Termination TP box. .................................................................................................................120
Figure 97. G.783 Adaptation TP box. ........................................................................................................120
Figure 98. Examples of port menu options (SDH, PDH and ATM port) ....................................................121
Figure 99. Set Retiming enable (before)....................................................................................................122
Figure 100. Set Retiming enable (after) ..................................................................................................122
Figure 101. AU4 concatenate/deconcatenate commands ......................................................................123
Figure 102. Example of a concatenated AU4 transmission view ............................................................124
Figure 103. Example of a concatenated AU4c ........................................................................................124
Figure 104. Physical media menu (SDH port example) ..........................................................................125
Figure 105. Automatic Laser Shutdown Management ............................................................................126
3AL 98325 ADAA 12/386
Figure 106. Automatic Laser Shutdown Management (after ALS Function delete) ................................127
Figure 107. ALS and Laser current state (example)................................................................................128
Figure 108. Visualizing a port optical parameters ...................................................................................128
Figure 109. Bidirectional Transmission on a single fiber.........................................................................129
Figure 110. Single Fiber Configuration View ...........................................................................................130
Figure 111. Ms Configuration ..................................................................................................................130
Figure 112. PDH Line Length Configuration View...................................................................................131
Figure 113. Ethernet Port Configuration options .....................................................................................131
Figure 114. Ethernet Port Configuration Dialog.......................................................................................132
Figure 115. Information dialog .................................................................................................................132

Figure 116. Gigabit Ethernet port view (example) ...................................................................................133

Figure 117. Ethernet Mapping Protocol (EXAMPLE) ..............................................................................134
Figure 118. Control Path Activation (example on Fast Ethernet board)..................................................135
Figure 119. Control Path Activation: Range Path mode..........................................................................135
Figure 120. LCAS Configuration..............................................................................................................138
Figure 121. LCAS Monitoring ..................................................................................................................138
Figure 122. TP Frame Mode Configuration .............................................................................................141
Figure 123. Board View Example ............................................................................................................143
Figure 124. “Navigate to Transmission view” selection...........................................................................144
Figure 125. After “Navigate to Transmission view” selection ..................................................................145
Figure 126. View of Monitoring Operations (example) ............................................................................146
Figure 127. Port Mode Menu Option .......................................................................................................147
Figure 128. Port Mode Overview Dialog..................................................................................................147
Figure 129. set the selected port mode ...................................................................................................148
Figure 130. Consulting EPS ....................................................................................................................150
Figure 131. EPS Management dialogue box...........................................................................................150
Figure 132. EPS: board selection ............................................................................................................153
Figure 133. EPS: choose protected.........................................................................................................153
Figure 134. EPS functional state from protected active board view........................................................154
Figure 135. EPS functional state from protecting active board view .......................................................154
Figure 136. Configure EPS......................................................................................................................154
Figure 137. EPS Management dialogue box...........................................................................................154
Figure 138. Switching EPS ......................................................................................................................155
Figure 139. EPS Switch dialogue box .....................................................................................................156
Figure 140. EPS overview .......................................................................................................................156
Figure 141. EPS overview after Search (Example) .................................................................................157
3AL 98325 ADAA 13/386
Figure 142. Subrack view after “Open Subrack View” command............................................................159
Figure 143. Board view after “Open Board View” command...................................................................160
Figure 144. MSP Create Option ..............................................................................................................162
Figure 145. MSP Schema Creation.........................................................................................................162
Figure 146. MSP schema creation Port dialog ........................................................................................163
Figure 147. TP Search.............................................................................................................................164
Figure 148. MSP 1+1 standard protection schema (example)................................................................165
Figure 149. MSP Management Option ....................................................................................................165
Figure 150. MSP Management View.......................................................................................................166
Figure 151. MSP Delete option................................................................................................................167

Figure 152. MSP Schema Deletion .........................................................................................................167

Figure 153. MSP Protection Status Examples ........................................................................................169
Figure 154. MSP Commands option .......................................................................................................170
Figure 155. MSP Commands ..................................................................................................................171
Figure 156. MSP overview.......................................................................................................................172
Figure 157. MSP overview after Search (Example) ................................................................................174
Figure 158. Port view after “Open Port View” commands .......................................................................176
Figure 159. Symbols Used in Transmission View ...................................................................................178
Figure 160. Transmission View Area.......................................................................................................179
Figure 161. Transmission menu options .................................................................................................181
Figure 162. TP Search Dialog, Initial State .............................................................................................182
Figure 163. Information Window..............................................................................................................182
Figure 164. TP Search Dialog with Various TP Selections .....................................................................183
Figure 165. TP Search Dialog with Status Information Displayed...........................................................184
Figure 166. Symbols in TP Search..........................................................................................................184
Figure 167. Board History Check List......................................................................................................184
Figure 168. TP Search Dialog with Different Filtering Options................................................................186
Figure 169. “Information...” Dialog for Search Process ...........................................................................186
Figure 170. Print to Printer.......................................................................................................................187
Figure 171. Print to File ...........................................................................................................................187
Figure 172. Example Printout ..................................................................................................................187
Figure 173. High Order TP Configuration................................................................................................188
Figure 174. J1 hexadecimal editor (example) .........................................................................................189
Figure 175. J0 Configuration ...................................................................................................................190
Figure 176. Low Order TP Configuration.................................................................................................191
Figure 177. J2 hexadecimal editor ..........................................................................................................191
3AL 98325 ADAA 14/386
Figure 178. TP Frame Mode Configuration .............................................................................................193
Figure 179. Degraded Signal Threshold selection ..................................................................................194
Figure 180. Monitoring Operations ..........................................................................................................196
Figure 181. Monitoring Operations Creation/Deletion .............................................................................197
Figure 182. Display of POM and TCM in Port View (example) ...............................................................198
Figure 183. Display of POM and TCM/TCT in Port View (example) .......................................................198
Figure 184. Monitor Configuration ...........................................................................................................198
Figure 185. Structure TPs option.............................................................................................................200
Figure 186. Loopback configurations ......................................................................................................201
Figure 187. Port Loopback Configuration................................................................................................202

Figure 188. Port Loopbacks View............................................................................................................202

Figure 189. Loopback Management view................................................................................................203
Figure 190. Loopback Management........................................................................................................203
Figure 191. Loopback Port View..............................................................................................................204
Figure 192. Loopback Transmission View...............................................................................................204
Figure 193. Physical Media options.........................................................................................................205
Figure 194. Set Domain...........................................................................................................................206
Figure 195. Expand option.......................................................................................................................207
Figure 196. Hide option ...........................................................................................................................207
Figure 197. Board View ...........................................................................................................................208
Figure 198. Port View ..............................................................................................................................209
Figure 199. Navigate to HOA Port...........................................................................................................210
Figure 200. SDH Multiplex Structure according to ITU-T G.709 .............................................................212
Figure 201. Frame Construction within the Synchronous Digital Hierarchy............................................213
Figure 202. SDH Transport Level Diagram .............................................................................................217
Figure 203. PDH Transport Level Diagram .............................................................................................218
Figure 204. Unidirectional Connection ....................................................................................................220
Figure 205. Bidirectional Connection.......................................................................................................220
Figure 206. Example of Broadcast Connection with Three Legs ............................................................220
Figure 207. Bidirectional Connection - Input Protected...........................................................................221
Figure 208. Bidirectional Connection - Input Protected...........................................................................221
Figure 209. Protected Broadcast.............................................................................................................221
Figure 210. Drop and Continue - Normal ................................................................................................222
Figure 211. Cross connection management cascade menu ...................................................................227
Figure 212. Cross-Connection Management Dialog (Initial State) ..........................................................229
Figure 213. Cross-Connection Management Dialog (After Search)........................................................231
3AL 98325 ADAA 15/386
Figure 214. Create Cross-Connections ...................................................................................................233
Figure 215. Protection Criteria.................................................................................................................234
Figure 216. Cross-Connection Icons .......................................................................................................237
Figure 217. Creation of a Unidirectional, Non-Protected Cross-Connection...........................................237
Figure 218. Create a Bidirectional Protected Cross-Connection.............................................................238
Figure 219. Search for Cross-Connection Output ...................................................................................239
Figure 220. Create an Unprotected Broadcast Cross-Connection..........................................................240
Figure 221. Create a Protected Broadcast Cross-Connection ................................................................240
Figure 222. Unprotect a Unidirectional Cross-Connection ......................................................................242
Figure 223. Protect one Leg of a Broadcast Connection ........................................................................242

Figure 224. Split/Join Unprotected Bidirectional Cross-Connection........................................................244

Figure 225. Split/Join to Protected Bidirectional Cross-Connection........................................................244
Figure 226. Protection Actions Dialog .....................................................................................................246
Figure 227. Select Printer ........................................................................................................................247
Figure 228. Select Output Format ...........................................................................................................247
Figure 229. Show Cross Connected TPs view ........................................................................................248
Figure 230. Show Cross Connected VC4 of an AU4 ..............................................................................249
Figure 231. Overhead options .................................................................................................................251
Figure 232. Cross Connection Management for Overhead dialog ..........................................................252
Figure 233. Main Cross-Connection for Overhead dialog .......................................................................253
Figure 234. OH TP creation.....................................................................................................................256
Figure 235. OH Search TP for creation ...................................................................................................257
Figure 236. OH TP deleting .....................................................................................................................258
Figure 237. Phone Parameters dialog window........................................................................................259
Figure 238. Far End Performance Monitoring Principles ........................................................................262
Figure 239. Configure Monitoring. ...........................................................................................................266
Figure 240. PM Configuration Dialog (example) .....................................................................................267
Figure 241. PM question dialog box (example) .......................................................................................267
Figure 242. Counter directionality: network centric view .........................................................................269
Figure 243. Counter subdivision ..............................................................................................................270
Figure 244. Ethernet aggregate counter..................................................................................................271
Figure 245. Display Current Data view....................................................................................................272
Figure 246. Current PM Data Dialog (example) ......................................................................................274
Figure 247. PM History Data view ...........................................................................................................274
Figure 248. PM History Data Dialog (example) .......................................................................................276
Figure 249. PM Configuration dialog .......................................................................................................276
3AL 98325 ADAA 16/386
Figure 250. PM Threshold Table Select ..................................................................................................277
Figure 251. PM Port View........................................................................................................................278
Figure 252. PM Transmission View .........................................................................................................278
Figure 253. Create PM Threshold Table .................................................................................................279
Figure 254. Modify PM Threshold Table .................................................................................................281
Figure 255. PM Configuration dialog .......................................................................................................281
Figure 256. Create Ethernet counter .......................................................................................................282
Figure 257. Display Current Data ............................................................................................................282
Figure 258. Display current data..............................................................................................................283
Figure 259. PM History Data dialog.........................................................................................................284

Figure 260. Display History Data .............................................................................................................284

Figure 261. PM Overview Menu item ......................................................................................................285
Figure 262. PM Overview ........................................................................................................................285
Figure 263. Add TP for PM Overview......................................................................................................286
Figure 264. PM Overview after add TP ...................................................................................................287
Figure 265. Internal organization of the SETS. .......................................................................................288
Figure 266. Obtaining the synchronization view......................................................................................290
Figure 267. Synchronization View Example ............................................................................................291
Figure 268. Synchronization Menu..........................................................................................................293
Figure 269. Timing source configuration for cross-Connect equipments................................................294
Figure 270. Synch. Source configuration for ADM equipment ................................................................295
Figure 271. Lockout, Force and Manual commands ...............................................................................296
Figure 272. Configuring the T0 or T4 SSM algorithm and the squelch criteria .......................................298
Figure 273. SSU Configuration................................................................................................................298
Figure 274. Synchronization source removing ........................................................................................299
Figure 275. Synchronization source removing confirmation ...................................................................299
Figure 276. Change T4 <-> T5 menu ......................................................................................................300
Figure 277. Change T4 <-> T5 confirmation message............................................................................300
Figure 278. Change T4 <-> T5: command execution..............................................................................300
Figure 279. Change 2MHz -->2Mbit menu ..............................................................................................301
Figure 280. Change 2MHz ->2Mbit confirmation message .....................................................................301
Figure 281. Change 2MHz -->2Mbit: command execution......................................................................302
Figure 282. T4 equal T0 setting...............................................................................................................302
Figure 283. Transmission SSM Quality ...................................................................................................303
Figure 284. Timing Source Example .......................................................................................................303
Figure 285. Display MS–SPRing pull down menu...................................................................................305
3AL 98325 ADAA 17/386
Figure 286. MS-SPRing Management dialog box ...................................................................................306
Figure 287. Creation Schema dialog box ................................................................................................306
Figure 288. Activated MS-SPRing Management.....................................................................................307
Figure 289. Node Id and associated ring node position ..........................................................................308
Figure 290. Ring map configuration ........................................................................................................308
Figure 291. WTR dialog box ....................................................................................................................309
Figure 292. Example of error message ...................................................................................................309
Figure 293. Squelching table ...................................................................................................................310
Figure 294. Example of a ring traffic........................................................................................................310
Figure 295. Connections of the ring ........................................................................................................311

Figure 296. Squelching table of Node A, West side ................................................................................311

Figure 297. Squelching table of Node A, East side .................................................................................312
Figure 298. Squelching table of Node B, West side ................................................................................312
Figure 299. Squelching table of Node B, East side .................................................................................313
Figure 300. Squelching table of Node C, West side................................................................................313
Figure 301. Squelching table of Node C, East side.................................................................................314
Figure 302. Squelching table of Node D, West side................................................................................314
Figure 303. Squelching table of Node D, East side.................................................................................315
Figure 304. Confirmation message .........................................................................................................315
Figure 305. Protection states and commands "Idle" status (2F) .............................................................316
Figure 306. Ring Protection (2F) .............................................................................................................317
Figure 307. Lockout commands (2F).......................................................................................................317
Figure 308. Protection and working channels where the lockout command can be activated (2F) ........318
Figure 309. Tail-end / Head-end association...........................................................................................318
Figure 310. Tail-end / head-end protection with a lockout working and a one direction failure (2F).......319
Figure 311. Ring protection with a lockout and a ring failure (2F)...........................................................320
Figure 312. Lockout command and non-served failures (2F)..................................................................321
Figure 313. Forced and Manual Commands (2F) ...................................................................................322
Figure 314. Manual and Force Span/Ring command (2F) ......................................................................322
Figure 315. Ring Protection with Force and Manual commands (2F) .....................................................323
Figure 316. Automatic protection Bridge/Switch (2F)..............................................................................324
Figure 317. Example of confirmation dialog box .....................................................................................324
Figure 318. Clear WTR command (2F) ...................................................................................................324
Figure 319. Ring network reference scheme (2F) ...................................................................................325
Figure 320. Examples of Double ring failure ...........................................................................................326
Figure 321. Automatic protection (tail/head) for double ring failure visualization....................................327
3AL 98325 ADAA 18/386
Figure 322. Tail / head dual "Events" Protection table (2F) ....................................................................328
Figure 323. Manual command applied at the "Reference Point" ring network........................................330
Figure 324. Visualization of the Forced / Manual protection Statuses (2F) ............................................331
Figure 325. Visualization of the Lockout command Statuses (2F) ..........................................................332
Figure 326. Visualization of Automatic Protection Statuses (2F) ............................................................333
Figure 327. Protection status with double ring failure (reference point -SS-AN).....................................334
Figure 328. Protection status with double ring failure (reference point-SS-RN) .....................................335
Figure 329. Protection status with double ring failure (reference point-OS-AN) .....................................336
Figure 330. Protection status with double ring failure (reference point-OS-AN) recovering to "idle" ......337
Figure 331. Double manual ring command (reference point-SS-AN)......................................................339

Figure 332. Double manual ring command (reference point-OS-AN) .....................................................340

Figure 333. Manual ring and Lockout Protection (reference point-SS-SN).............................................341
Figure 334. Manual ring and Lockout Protection (reference point-SS-RN).............................................343
Figure 335. Automatic working ring and Manual Ring (reference point-OS-AN) ....................................344
Figure 336. Automatic working ring and Force Ring (reference point-SS-AN) .......................................345
Figure 337. Automatic working ring and Lockout working Ring (reference point-SS-SN).......................346
Figure 338. Automatic working ring and Lockout Protection (reference point-OS-RN)...........................347
Figure 339. ATM 4X4 MATRIX (initial empty fields) ................................................................................350
Figure 340. ATM 4X4 MATRIX (with defined TPs)..................................................................................350
Figure 341. Navigate to ATM port view (example) ..................................................................................351
Figure 342. PR_EA MATRIX (initial empty fields) ...................................................................................352
Figure 343. PR_EA MATRIX (with defined TPs) .....................................................................................353
Figure 344. MPLS port view example......................................................................................................354
Figure 345. ETH–MB (initial empty fieds)................................................................................................355
Figure 346. ETH–MB (with defined TPs).................................................................................................355
Figure 347. Control Path activation window (example) ...........................................................................356
Figure 348. ETHERNET port view example ............................................................................................357
Figure 349. ES1-8FE MATRIX (initial empty fields) ................................................................................359
Figure 350. ES1-8FE MATRIX (with defined TPs) ..................................................................................359
Figure 351. Navigate to ETH port view (example)...................................................................................360
Figure 352. ES4-8FE MATRIX (initial empty fields) ................................................................................362
Figure 353. ES4-8FE MATRIX (with defined TPs) ..................................................................................362
Figure 355. ISA-ES16 MATRIX (initial empty fields) ...............................................................................364
Figure 356. ISA-ES16 MATRIX (with defined TPs) .................................................................................364
3AL 98325 ADAA 19/386
Figure 358. Example of DVB-ASI TPs creation.......................................................................................366
Figure 360. ASI-ABNC access card view example .................................................................................368
Figure 361. Example of BCE-ETH TPs creation .....................................................................................369
Figure 363. BCE-ETH access card view example...................................................................................371
Figure 364. DCC Interworking configuration ...........................................................................................372
Figure 365. Software Download general principle...................................................................................374
Figure 366. Software Administration menu .............................................................................................376
Figure 367. Software Package Administration view ................................................................................377

Figure 368. SDH software package installation.......................................................................................377

Figure 369. ATM software package installation (example) .....................................................................378
Figure 370. OMSN enhanced software package creation (part A)..........................................................379
Figure 371. OMSN enhanced software package creation (part B)..........................................................379
Figure 372. Enhanced software package (SDH + ATM) .........................................................................380
Figure 373. Equipment view ....................................................................................................................381
Figure 374. Download menu....................................................................................................................381
Figure 375. SW Downloading dialogue box example..............................................................................382
Figure 376. Software download in progress (example)...........................................................................383
Figure 377. Software Package Information dialogue box (example).......................................................384
Figure 378. Detail software package (example) ......................................................................................385
Figure 379. NE MIB management ...........................................................................................................386
TABLE
Table 1. DWDM SFP module wavelength corresponding channel number................................................105
Table 2. MSP commands and Auto-switch protection priority ....................................................................171
Table 3. Default value for C2/V5 Signal Label ............................................................................................189
Table 4. PDH TPs .......................................................................................................................................218
Table 5. SDH TPs .......................................................................................................................................219
Table 6. Optional and Mandatory Configurable Parameters for Cross-Connection Creation.....................235
Table 7. Modifiable Parameters ..................................................................................................................241
Table 8. Threshold table entities association..............................................................................................278
Table 9. Maximum Performance Parameter Values ...................................................................................280
3AL 98325 ADAA 20/386
1 INTRODUCTION
1.1 Scope

The aim of this document is to help the operator understand, configure and manipulate Network Elements
(NEs) easily, using the Craft Terminal (CT). 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.

This document is intended for the operators whose role is to manage the Network Elements.
--- 1320CT Basic Operator’s Handbook
The documents of this Handbook that should be read before starting this document are:
--- Introduction manual
1.2 Terminology
1.2.1 Acronyms and abbreviations

Refer to the Section Introduction manual.
1.2.2 Glossary of terms

3AL 98325 ADAA 21/386
2 GENERAL INTRODUCTION ON VIEWS AND MENUS
In this chapter the organization of the EML--USM screen, presented after the NE login, is described.
First is introduced the view organization, then the accessible menu options are listed.
At the end some further advice are given for Navigation principles.
2.1 EML--USM view organization

The EML--USM view (see Figure 1) is the first window presented to the operator after the login.
It contains the following fields, which provide you with information needed to manage the NE:
z Severity alarm synthesis,

z Domain alarm synthesis,
z Management status control panel
z View title,
z View area
z Message/state area
The Menu bar and the View area contained in the same NE view permits to perform all the configuration and
supervision and display the specific selected item.
The view organization is detailed in the Basic Craft Terminal Operator Handbook to which refer for the
description, except for the following information, that differs according the NE type:
-- Domain alarm synthesis
The different alarm domain type in which can be subdivided the NE is: Synchronization, External Point,
Equipment, and Transmission.
Information about the alarms and status is given in the Maintenance section of this handbook.
3AL 98325 ADAA 22/386
Figure 1. EML--USM main view organization
2.2 Introduction on the EML--USM menu options

The menu bar allows performing configuration and supervision functions on the Network Element.
This paragraph lists all the menu options and then more details on the relevant contained entries.
For each of them the relevant operative functions are briefly introduced.
The flow charts of Figure 2., Figure 3., Figure 4., Figure 5., summarize the menu options.
From chapter 3 on details and operative information on the all the views are given. They are not presented
according the menu option sequence but according a functional subdivision.
In the menu bar there are permanent menu items always displayed. Staring from the left, the menus are:
• Permanent Menus
• Views (first column).
To navigate among the views and set TMN and Overhead parameters.
• Configuration (second column).
3AL 98325 ADAA 23/386
To set general configuration of the NE, set TMN and Overhead parameters
and to show or modify some parameters (performance monitoring,
ATM/IP/ETH creation, MSP, EPS and cross-connection).
• Diagnosis (third column).
To get information about the NE (alarms, performance monitoring, remote
inventory internal link monitor).
• Supervision (fourth column).
To set the supervision states (i.e. Craft Terminal enabling).
• MS_SPRing (fifth column)
To manage the 2-fiber MS_SPRing protection, setting the relevant configuration.
• Download (sixth column).

To manage the NE software (download, MIB management).

• Help (last column).
To activate the help.
Further, in the menu bar there are other menus, presented as an alternative, only when a particular object or
option is selected.
• Other Menus
• Equipment (eighth column).
To manage the NE as a whole, setting the boards, which compose it. From
the Equipment view the Board view can be accessed.
From the Equipment menu is also possible to start the Specific Terminal
application for the ATM/IP traffic configuration.
• Board (eighth column).
To show the physical port available in a specific board. It is the entry point
for the Port view.
• Transmission (seventh column).
It permits to show and set the Termination Point of the equipment, thus
having an overview of the complete signal flow of the various port.
The menu permits to define all the Cross Connections and manages the
transmission resources, setting the relevant configuration.
Further access the Performance Monitoring and permits navigation to the
Board view.
It also permits to manage the MSP protection setting the relevant
configuration.
• Port (seventh column).
To set and show (detailed alarm view) the transmission resources referred
to the Port.
It also permits to manage the MSP protection setting the relevant
configuration.
• EPS (seventh column).
To manage the EPS protection, setting the relevant configuration.
3AL 98325 ADAA 24/386
• Synchronization (seventh column).
To show and modify synchronization parameters.
• External Points (seventh column).
To show and modify housekeeping (environmental) alarms.
2.2.1 Views menu introduction

This menu permits to navigate among the views and set some parameters, by means of the following entries:
• Backward: Go back to the previous view.
• Forward: Go to the next view.
• Equipment: Open the Equipment view. The "Equipment" menu and the "EPS" menu are
then available on the menu bar.
• External Points: Open the External Point view. The "External Point" menu is then available
on the menu bar.
• Transmission: Open the Transmission view. The "Transmission" menu is then available on
the menu bar.
• Synchronization: Open the Synchronization view. The "Synchronization" menu is then
available on the menu bar
• Refresh: The aim of the refresh feature is to avoid a misalignment between the CT
and the managed NE. This misalignment is due to a loss of notifications coming from the NE.
• Open Object: Navigate and show the contents of the selected object: the current view
change. It is equivalent to a double click on the selected object in the view area.
• Open in Window: Navigate and show the contents of the selected object. The current view
doesn't change but a new window with a new view is opened.
• Close: Close the EML-USM view, without stopping the supervision of the NE
2.2.2 Configuration menu introduction

This menu permits to set general configuration of the NE and to show or modify some parameters, by means
of the following entries:
• Alarm Severities: Manage the Alarm Severity Assignment Profile.
• Set Alarm severities: Send the Alarm Severity Assignment Profile to the selected object
• Set SdhNe Alarm severities: Send the Alarm Severity Assignment Profile referred to the equipment
level.
• NE Time: Display and set the NE local time.
• Performance: Manage the Performance Monitoring domain. Used to define the PM
parameters, opening the following menu options:
- Threshold table
• EPS overview: Allows displaying as well as search for EPS states.
• Set ACD level:
• Cross Connection Management: Manage the connection of the paths.
• Loopback Management: Enter the loopback management. Used to configure the loopback command
for commissioning or maintenance purposes.
3AL 98325 ADAA 25/386
• Comm/Routing: Enter the Communication and Routing management. Used to define the parameters
for NE and OS in the TMN, opening the following menu options:
• Local configuration
• OS Configuration
• NTP Server Configuration
• Interfaces Configuration
- - LAPD Configuration
- - Ethernet Configuration
• OSI Routing Configuration
- - RAP Configuration
- - MESA Configuration
• IP Configuration
- - IP Static Routing Configuration
- - OSPC Area Configuration
- - IP Address Configuration of point-to-point interfaces
- - ISA board IP address
• Tunneling Configuration
- - OSI Over IP
- - IP over OSI
• Overhead: Handle the operation on the Overhead bytes. Used to define the parameters in the following
menu options:
- - OH Cross Connection
- - OH Phone Parameter
- - OH TP creation
- - OH TP deleting
• MSP overview: Allows displaying as well as search for MSP states.
• PM overview: Allows displaying performance overview.
• ISA Port Configuration: It allows to create the TPs for the ISA and DVB-ASI connections
• Interworking Configuration: It allows to manage the interworking between this NE and the 1850TSS-3
equipments (Ethernet in-band management).
2.2.3 Diagnosis menu introduction

This menu permits to get information about the NE, by means of the following entries:
• Alarms: Display the Alarms Surveillance information of the NE. It opens the following menu options:
- - NE alarms
- - Object alarms
- - Subtree alarms
- - Equipment alarms
3AL 98325 ADAA 26/386
- - Transmission alarms
- - External Points alarms
• Log Browsing: Manage the events stored in the NE. It opens the following menu options:
- - Alarm Log
- - Event Log
- - Software Trace Log
• View Remote Inventory: Display the remote inventory data, previously stored in the Craft Terminal by
means the "upload remote inventory" performed in the "Supervisory" menu.
• Abnormal Condition list Display the list of the object class (Loopback, ALS Handler, protection board)
and the name of the boards that are in abnormal condition.

• Internal Link Monitor: Indicates the preference of failure on Rx or Tx side for the signal
incoming/outgoing from/to the active/standby MATRIX board.
• Dataflow Analyzer.
2.2.4 Supervision menu introduction

This menu permits to set the supervision states of the NE, by means of the following entries:
• Access State: Manage the supervision access to the NE, with CT or OS. It opens the following menu
options:
- - OS
- - Requested
• Alarms: Manage the alarms supervision of the NE. It opens the following menu options:
- - Resynchronize.
- - Allow / Inhibits Notifs.
• Upload Remote Inventory: Store the Remote Inventory data in the Craft Terminal.
• Set Manager list
• Restart NE: Reset the NE software.
2.2.5 MS-SPRing menu introduction

This menu permits to age the 2-fiber and 4-fiber MS-SPRing protection (the last is not operative in current
release), setting the relevant configuration, by means of the following entries:
Main dialog for MS-SPRing management: Contains all the command to set and manage the MS-SPRing
2.2.6 Download menu introduction

This menu permits to manage the NE software, by means of the following entries:
• Init download: Manage the software download, upgrading the NE.
• Units info: Show the status of the software package installed in the NE memory banks.
• Mib management: Permits backup of NE software configuration and restore of backup file.
2.2.7 Equipment menu introduction

This menu permits to manage the NE as a whole, setting the boards, which compose it, by means of the
following entries:
3AL 98325 ADAA 27/386
• Set: Add or change the board type (a list is proposed).
• Modify: Change the board type without previously remove it. It is only possible between compatible
board or modules (ex. it is possible to change from an Long and Short 1.1 optical module)
• Remove: Remove the board.
• Set in service: Insert a lock symbol in the board.
• Set out of service Delete the lock symbol in the board, enabling changes.
• Reset: Not operative.
• Software description: Show information on the software of the board.
• Remote Inventory: Show the Remote Inventory data inserted in the equipment. It opens the following
menu options:
- - Subrack level
- - Board level
• ISA Board IP Address: Used to define the ISA board IP address
N.B. This option is available only at Subrack view level.
• Show supporting equipment: Navigate to the upper equipment level.
• Connect FAN to CONGI #1: Enable the management of the Fan subrack alarms on CONGI inserted
in slot 1.
N.B. This option is available only after having selected a CONGI board at Subrack level view.
• Connect FAN to CONGI # 20: Enable the management of the Fan subrack alarms on CONGI
inserted in slot 20.
N.B. This option is available only after having selected a CONGI board at Subrack level view.
2.2.8 Board menu introduction

This menu permits to show the physical port available in a specific board (alarm synthesis and port symbol)
and to access the port view, by means of the following entries:
• Port Access: Access the "Port view".
• Change Physical Interface: Change the SPI or PPI object into PPI or SPI (and vice versa) on the bi-
mode port (140Mbit/s / STM-1 switch able).
• Show supporting equipment: Navigate to the upper subrack level.
• ISA Port Configuration: It allows creating the TPs for the ATM/IP/ETH connections.
N.B. This menu is available only if an ATM/IP/ETH board has been
equipped in the subrack.
2.2.9 Port menu introduction

This menu permits to set and show the transmission resources (TP) referred to the Port, by means of the
entries indicated in the following list.
The menu differs according the port type (SDH, PDH, HOA, ATM, IP and ETHERNET).
The "Port view" is reached by means the Equipment menu and Board view to check the detailed alarms
presented, but the available menu permits to configure the port (many setting options listed in the port
menu are common with the "Transmission" view).
In these views are presented only the TP specific of the port.
3AL 98325 ADAA 28/386
It permits navigation to the Transmission view.
• TP configuration: Set parameters for the Overhead (Signal Label and Path Trace) on Synchronous
TP's.
• TP Threshold Configuration: Set B2 excessive BER and Signal Degraded parameter.
• TP Frame Mode Configuration: Set parameters for 2Mbit/s G.703/704 or ISDN-PRA management.
• Set Retiming: Set the retiming feature applies to the outgoing 2Mbit/s. It opens the following options:
- - Enable
- - Disable
• AU4 Concatenation: Only for SDH ports views.
• Cross Connection: Manage the connection of the paths. It opens the following options:
- - Cross Connection Management

- - Create Cross Connection
- - Modify Cross Connection
• Monitoring Operation: Set parameters for POM, SUT . Not available for PDH port. It opens the
following menu options:
- - Creation / Deletion
- - Configuration
• Performance: Set and show Performance Monitoring parameters and data. It opens the following
menu options:
- - Configure Monitoring
- - Display Current Data
- - Display History Data
• Loopback: Enter the loopback management. Used to configure the loopback command for
commissioning or maintenance purposes:
- - Port Loopback Configuration
- - Loopback management
• MSP: Manage the Multiplex Section Protection of the NE. Only for SDH ports view. It opens the
following menu options:
- - MSP Create
- - MSP Management
- - MSP Commands
- - MSP Delete
• Physical Media: Manage the physical setting of the TP of the ports. Not applicable to HOA port. It
opens a menu which differs according the port type:
• SDH port:
- - ALS Management
- - Show Optical Configuration
- - TX Quality Configuration
3AL 98325 ADAA 29/386
- - Single Fiber Configuration
- - LAPD Configuration
- - Ms Configuration
• PDH port:
- - Line Length Configuration
- - HDSL Configuration
- - NT G703/704 Configuration
- - NT X21 Configuration
• ETHERNET port:
- - Remote Laser Management

- - ALS Management
- - Ethernet Port Configuration
- - Ethernet Mapping protocol
- - ISA Port Configuration
- - Control Path Activation
• Show supporting board: Navigate to the upper board level.
• Navigate to Transmission view: permit to show a complete overview about the signal flow, opening
all TP's
• Navigate to monitoring view: permit to show for a selected TP the related POM/SUT/TCM and TCT
object if present.
2.2.10 EPS menu introduction

This menu permits to manage the EPS protection, setting the relevant configuration, by means of the
following entries:
• Management: Set EPS protections.
• Configure: Set revertive / not revertive and WTR parameters.
• Switch: Manage the EPS operator commands (Force, Manual, Lockout)
2.2.11 Transmission menu introduction

This menu permits to show and set the Termination Point of the equipment, thus having an overview of the
complete signal flow of the various port.
The menu permits to define all the Cross Connections and manages the transmission resources, setting the
relevant configuration.
Further access the Performance Monitoring and manage Multiplex Section Protections and Loopbacks
functions.
It permits navigation to the Port view.
The menu lists the following entries:
• Add TP: Search and add TP to the transmission view, than presented in the screen.
• Expand: Display the TP's related to a selected TP. It opens the following menu options:
- - Next level of lower TP
3AL 98325 ADAA 30/386
- - All lower TP
- - Next level of upper TP
- - All upper TP
• Hide: Remove the TP from the screen of the Transmission view. It opens the following menu options:
- - Lower TP
- - Upper TP
- - Selected TP
• TP configuration: Set parameters for the Signal Label and Path trace.
• TP Frame Mode Configuration: Set parameters for 2Mbit/s G.703/704 or ISDN-PRA management.
Only for PDH ports views.

• TP Threshold configuration: Set B2 Ex BER and Signal Degrade threshold.

• Terminate TP: Terminate the AU4-CTP paths.
• Disterminate TP: Disterminate the AU4-CTP paths.
• Cross Connection: Manage the connection of the paths. It opens the following menu options:
- - Cross Connection Management
- - Create Cross Connection
- - Modify Cross Connection
- - Port Switch Over
- - Show Cross Connected TP's
• Monitoring Operation: Set parameters for POM, SUT. It opens the following menu options:
- - Creation / deletion
- - Configuration
• Performance: Set and show Performance Monitoring parameters and data. It opens the following
menu options:
- - Configure Monitoring
- - Display Current Data
- - Display History Data
• Structure TP's: Define the structure of a selected TP (TU2, TU3, TU12, VC3/VC4, VC12)
• Loopback : Enter the loopback management. Used to configure the loopback command for
commissioning or maintenance purposes: It opens the following menu options:
- - Port Loopback Configuration
- - Loopback management
• Physical Media: Manage the TP physical setting. It opens the following menu options:
- - ALS Management
- - Show Optical Configuration
- - TX Quality Configuration
3AL 98325 ADAA 31/386
- - Single Fiber Configuration
- - Extra traffic
- - Regeneration Section management
- - Line Length Configuration
- - Set Domain
- - HDSL Configuration
- - NT Configuration
- - X21 Configuration
• MSP: Manage the Multiplex Section Protection of the NE. It opens the following menu options:
- - MSP Create
- - MSP Management
- - MSP Commands
- - MSP Delete
- - NE MSP synthesis
• Show supported board: Navigate to the board supporting the selected TP
• Navigate to Port view: Navigate to the port supporting the selected TP
2.2.12 Synchronization menu introduction

This menu permits to set and show the Synchronization parameters and status, setting the relevant
configuration, by means of the following entries:
• Timing Source Configuration: Set timing source priority and quality for the selected input reference.
• Protection Command: Manage commands (force, manual, lockout) for the selected timing reference.
• T0 Configuration: Enable/disable SSM and WTR on the T0 synchronization source.
• T4 Configuration: Enable/disable SSM, WTR and Squelch Criteria on the T4 synchronization source.
• T0 TEST Configuration: Not used.
• SSU Configuration: Set NE single or with SSU.
• Remove Timing Reference
• Change T4<->T5: Change the synchronization physical interface from 2MHz (T4) to 2Mbit/s (T5)
without traffic” and vice versa.
• Change 2MHx->2Mbit: Change the source of a protection unit from 2Mhz to 2Mbit and vice versa.
• Set T0 Equal T4
• Remove T0 Equal T4
• Transmitted SSM Quality Configuration: Set SSM quality transmitted on the selected T1 SDH timing
reference.
• Frame Mode Configuration: Set parameters for 2Mbit/s G.703/704 or ISDN-PRA management. Only
for PDH ports views.
• Show Timing Source: Show the "port view" related to the selected timing reference.
3AL 98325 ADAA 32/386
2.2.13 External Points menu introduction
This menu permits to display and set the input/output environmental alarm (housekeeping alarm), by means
of the following entries:
• Configuration: Set the input/output environmental alarm.
• Display: Show the list of the input/output environmental alarm. It opens the following menu options:
- - Show external Input Points
- - Show external Output Points
- - Show all external Points
3AL 98325 ADAA 33/386
ED
02
Figure 2.
SC.3: NE MANAGEMENT
Menu options flow chart -- 1
3AL 98325 ADAA

34/386
ED
02
Figure 3.
SC.3: NE MANAGEMENT
Menu options flow chart – 2
3AL 98325 ADAA

35/386
ED
02
Figure 4.
SC.3: NE MANAGEMENT
Menu options flow chart – 3
3AL 98325 ADAA

36/386
Figure 5. Menu options flow chart – 4
2.3 Advices on Navigation principles

Navigation rules are the same for all the NE using the same Craft Terminal Info Model.
This general rules are described in the "Basic Craft Terminal Operator Handbook".
In this paragraphs are instead inserted menu options typical for this NE involved in Navigation and example
of Navigation.
To reach a particular view of the NE there are several ways (navigation is also possible mixing the different
ways):
• Double click on the selected object
• Select the object and use the Open object or Open in Window option of the View pull down menu
• Use the Menu option tree structure. The View pull down menu permits to show the following menus:
3AL 98325 ADAA 37/386
- - Equipment
- - Transmission
- - Synchronization
- - External Points
The menu structure permits to open the same window following several menu paths.
EXAMPLE: to obtain the "Create Cross Connection" window:
• First navigation path:
Open View - Transmission pull down menu
Open Transmission - Cross Connection - Cross Connection Management pull down menu Select Create
option in the presented window

• Second navigation path:

Open View - Equipment pull down menu
Double click on Board
Select the Board to access the Board view
Open Board - Port Access pull down menu
Open Port - Cross Connection - Create Cross Connection pull down menu
• Third navigation path:
Open Configuration - Cross Connection Management pull down menu
Select Create option in the presented window
The menu structure also permits to pass from a view menu to another (i.e. from "port view" to “board view" or
to "transmission view") thus facilitating the operators activity.
Views Navigation
The first level of the "Equipment view" representation will be displayed directly into the current window,
immediately after the NE login.
The Equipment view enables a fast navigation through all levels of the equipment hierarchy.
Navigation is done from higher to lower levels. The NE hierarchy is generally organized in the following way:
Subrack > board > port > TP.
Double clicking on the objects performs the navigation through different levels of the NE hierarchy:
• The first level shows the subrack level of the Equipment view
• 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;
It is also possible to:
- - Go back to the previous view, by selecting the Backward option from the views menu
- - Go to the next view, by selecting the Forward option from the view menu.
3AL 98325 ADAA 38/386
N.B. Selecting in the first level of the Equipment view the Show supporting equipment option from the
Equipment menu, the Rack level view (Example) is presented.
In the Rack Level view two subrack are presented:
- At the top the 1662SMC subrack, named SR62C (Example)
- At the bottom the Fans Subrack, named SRFAN (Example)
The Fans Subrack presence is managed with the Set option as for the boards of the 1662SMC
Subrack. (Example)
Further, selecting in the Rack level view the Show supporting equipment option from the Equipment
menu, the Equipment level view is presented.
3AL 98325 ADAA 39/386
3 NE MANAGEMENT SUPERVISION
This chapter is dedicated to the NE states and NE access.
3.1 NE management states

The elementary building blocks of any telecommunication network are the Network Elements (NEs).
Operating with the Craft Terminal the NE can present different management states according to the
condition of the connection (supervision, local access, connection state, etc). Also general Alarm status is
presented.
Management states are present at Network Element Synthesis view level and at USM--EML view level.
All the information referred to the management states are inserted in the Basic Craft Terminal Operator’s
Handbook.
Any disruption in the communication link between the CT and the NE results in an update of the
management states when the CT has detected the communication failure.
3.2 NE supervision and login

The Network Element Synthesis views enable you to get access to the current NE EML-USM view described
in this handbook.
The Network Element Synthesis views enable you to work on local or remote NE, selecting it and activating
"Supervision" and "Login", as described in the Basic Craft Terminal Operator's Handbook.
The EML-USM Main view is presented as for the following figure.
3AL 98325 ADAA 40/386
ED
02
Figure 6.
SC.3: NE MANAGEMENT
NE EML-USM Main view
3AL 98325 ADAA

41/386
4 NE MANAGEMENT GENERAL CONFIGURATION
In this chapter general configuration referred to the equipment management are described (Craft Terminal
access, NE Time, Alarms configuration, etc).
4.1 Access state (allow or inhibit NE Craft access)

The Craft Terminal can manage by the OS or the NE. To control the competition of the OS and the CT, a
Local Access Control (LAC) is available.
If the LAC is "granted" that means the CT is allowed to manage the NE. In the view the icon with a key
symbol has a rectangular shape.

If the LAC is "access denied" that means the OS manages the NE and the CT is not allowed to modify NE
configuration (it can only "read"). In the view the icon with a key symbol has a circular shape.
If the LAC is "requested" that means the CT has requested permission from the OS and is waiting for a
replay.
However the OS does continue to provide a certain number of services. 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 two types of views:
4.1.1 Switching from the OS to the Craft Terminal access state

Select the Supervision pull down menu. Then select the Requested option from the Access State
cascading menu as shown in the following figure.
Figure 7. NE management: setting the access state.
From the confirmation dialogue box that opens you can confirm or cancel the "Craft access" operation using
the Yes or No push buttons. The request is up to the OS, which accept or refuse it.
If the OS doesn't answer in a predefined time it is assumed that the NE is in the Craft access state and can
be managed from a Craft Terminal.
3AL 98325 ADAA 42/386
4.1.2 Switching from the Craft Terminal access state back to the OS access state
Select the Supervision pull down menu. Then select the OS... option from the Access State.
From the confirmation dialogue box that opens you can confirm or cancel the "OS access" operation.
The OS now manages the NE.
N.B. The key symbol icon on the management states of the NE view indicates whether the OS manages by
a craft terminal or the NE.
N.B. Local Craft Terminal access is denied on recovery phase after a loss of communication of the NE.
When communication is lost with the NE, the OS automatically recovers the communication and put the state
that was set before the loss of communication (therefore the Craft Terminal access can be denied or
granted).
4.2 NE Time management

The NE local time of a selected NE can be visualized and/or re-aligned on the OS time basis.
In this view the OS indication identifies the Craft Terminal.
The status of the Network Time Protocol can be checked
Select the NE Time... option from the Configuration pull down menu.
Figure 8. Consulting and/or setting the local NE time

The following dialogue box is opened from which you can get and/or set the local NE time and check the
NTP Status.
3AL 98325 ADAA 43/386
Figure 9. NE Time dialogue box
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) or disabled or empty (grey).
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 and OS Time
It displays (read only) the time of the Network Element and of the OS (Craft Terminal).
Set NE Time With OS Time
It permits to align the NE time with the time of the Craft Terminal.
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
3AL 98325 ADAA 44/386
In this case, the NTP Main and NTP Spare are empty (grey); 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 do not 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 push button to validate or on the Close push button to cancel and close the dialogue box.
The OS time comes from the PC date configuration that corresponds to the legal GMT time.
N.B. When the NTP is not present, the OS 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.
4.3 Alarm Configuration

The operations described in this chapter, mainly related to alarm setting, are:
• Alarm Severity Assignment Profile management,
• Allow/Inhibit alarm notification,
• Alarm re-synchronization
4.3.1 Procedure to modify an ASAP

a) Select the TP (or board/port/etc…) whose ASAP is to be changed
b) From the menu click on “Configuration” -> “alarms Severities….”
c) Select one of the “user” profile (#10001 or #10002) and click on “Modify”
d) 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) Click on “Close”
i) Select the relevant TP and then “Configuration” -> “Set Alarms Severities…”
j) In the box that appears select the just modified ASAP (eventually check it by means of “Detail”)
k) Click on “OK”
4.3.2 Alarm Severity Assignment Profile Management (ASAP)

Managed entities yield alarms when they malfunction. This section deals with the configuration of ASAPs. An
ASAP is a list of Alarm probable causes to which Severities Profiles are assigned, predefined or settable by
the operator.
Three important notions are:
• The Probable Cause of the alarm,
• The Severity of the alarm.
• The Alarm Type (communication alarm, equipment alarm).
4.3.2.1 Alarm Severities
This option permits to configure and display the ASAP.
3AL 98325 ADAA 45/386
Select the Alarm Severities... option from the Configuration pull down menu.
Figure 10. Configuring Alarm Severity Assignment Profile
The ASAP Management dialogue box is displayed.
Figure 11. ASAPs Management dialogue box.
The default presented profiles is:

• Profile “No alarms”. Whit this profiles all the alarms are enabled (only Software Download Failure
is not alarmed). This ASAP enables the emission of all alarms.
• Profile “No Remote Alarms” shows the alarm criterion configuration defined for "path alarms" (only
AIS and RDI and Software Download Failure are not alarmed). This ASAP enables the emission of
all:
- - Communication Alarms (i.e. the AIS & RDI alarms are not alarmed)
3AL 98325 ADAA 46/386
- - Environmental
- - Error Processing (i.e. Software Download Failure is not alarmed)
• Profile “Primary alarms” with this profile the AIS, Battery Degraded, Software Download Failure,
SSF and RDI alarms are not alarmed. This ASAP enables the emission of all:
- - Communication Alarms (i.e. the AIS, SSF & RDI alarms are not alarmed)
- - Environmental
- - Error Processing (i.e. Software Download Failure is not alarmed)
• Profile “All Alarms” (i.e. all alarms disabled). This ASAP inhibits the emission of any potential
alarm.
• The user can set profile 10001. Each single alarm can be classified with a criterion selected by the
operator. A default standard configuration is set. (Battery Degraded, Battery Failure, Communication
Subsystem Failure, Path Trace Mismatch are not alarmed).
NOTE: if this profile is not already present in the list, it is necessary to create it, selecting
one existing profile and then clicking on the Clone button.
You can select an ASAP.
For ASAP "10001" it is then possible to choose Detail, Modify, Clone or Delete buttons.
For ASAP “No Alarms”, “Primary alarms”. “No Remote Alarms” and “All Alarms” it is only possible to choose
Detail, or Clone buttons.
Clone selection can be used to create new ASAP.
Click on Detail, Modify, or Clone button, the ASAP edition dialogue box is displayed.
Figure 12. ASAP Edition dialogue box.
3AL 98325 ADAA 47/386
The alarm severity assignment profile dialogue box displays a list of probable causes and a list of alarm
severity.
The Probable cause family checks buttons allows filtering the probable causes that will appear in the
Probable cause name list. NOTE: it is necessary to choose one or more of these filters to have the list.
To find a particular probable cause, enter its name in the Search entry box at the bottom.
ASAPs are already defined in the system with default values for the assigned severities.
You can modify the severity associated with each probable cause. To do this, select the probable cause
whose severity level you wish to modify.
Then click on the option button: Service Affecting (not protected probable cause), and then Non Service
Affecting (protected probable cause) and then Service Independent (don't used, it is not operative). For each
the severity can be chosen from "Critical", "Major", "Minor", "Warning", "Non-alarmed" or "Not used". A "Non-
alarm" probable cause corresponds to no alarm emitted for this probable cause.
When selecting Details the assigned severity are only shown and it isn't possible to modify.
When you have finished configuring 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.
When Clone an ASAP the created one is identified with next number (10002,).
The max number of ASAP is six.
N.B. The number of severities and the number of probable causes is fixed. The ASAP function only enables
the modification of the severities assigned to the probable causes, it does not allow the addition, removal or
modification of 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 NE emits the modified or new alarms.
4.3.2.2 Set Alarm Severities
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 13. Set ASAP dialogue box.
3AL 98325 ADAA 48/386
Within 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 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 this 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-4CTPs are no subordinates of MSTTPs. Therefore, if
the AU-4 CTP should be included as subordinate, select the related OSTTP (OpS) or
ESTTP (EIS) as main object.
Choose Class (es)
Enabled if one the scopes "Network Element" or "Selected object and subordinates" is selected.
• All classes (es)
• 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 the 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 Ok to confirm the ASAP assignment and close the dialog. Press Close to close the dialog and discard
any changes.
4.3.3 Set SdhNE Alarms Severities

Selecting the Set SdhNE Alarms Severities option from the Configuration pull down menu only the alarms
at Equipment level (FF, BKF, SHD and ABF) are managed.
3AL 98325 ADAA 49/386
Figure 14. Set SdhNE Alarms Severities

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.
Press Ok to confirm the ASAP assignment and close the dialog. Press Close the dialog and discard any
changes.
4.3.4 Allow/Inhibit Alarms Notifications

The system provides the possibility to allow/inhibit the spontaneous incoming alarm notifications.
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.
Figure 15. 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 grey out.
3AL 98325 ADAA 50/386
N.B. Inhibiting the alarms notification means that they are not forwarded to the CT but alarms are still
generated by the NE.
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 as shown in the following figure.
Figure 16. Allow alarm notifications

4.3.5 Alarms re—synchronization

The system provides the possibility to recover alarms present on the NE and to update the current problem
list of the NE. After this operation CT and NE current alarms are consistent.
To re--synchronize the alarms, select the Supervision pull down menu. You can then select the
Resynchronize option from the Alarms pull down menu as shown in the following figure.
Figure 17. Alarm re--synchronization

N.B. This functionality has to be used only if there is any perturbation. Never use this operation during a
correct behavior.
3AL 98325 ADAA 51/386
4.3.6 Alarms persistency Configuration
Figure 18. Alarms persistency Configuration Menu option
Figure 19. Alarm persistency Time Configuration
3AL 98325 ADAA 52/386
4.4 Restart NE
The restart operation is a software reset and can be executed in normal traffic conditions.
The restart operation in any case activates the Commit (active) version.
Select the Restart NE option from the Supervision cascading menu.
The following dialogue box is opened.
Figure 20. Restart NE confirmation

Click on the Cancel push button to abort the restart NE.
3AL 98325 ADAA 53/386
5 SECURITY MANAGEMENT
In this chapter are inserted setting options referred to the Security management:
5.1 Set Manager list

This option is referred to the Security management and allows the user to set the Manager list and the
Access Control Domain of the NE.
Select the Set Manager list option from the Supervision pull down menu.
The dialog-box contains the following fields:
• Manager list: each connected manager to the NE is highlighted in the list. The user can set a
manager clicking on the denomination.

Several managers can be enabled contemporaneously, having in charge the NE.
The Manager List contains the list of managers (i.e. RM, SY, NPOS, EML) that work on the NE. The
EML-USM administrator (SH or Craft Terminal) should set the Manager List only to remove a
manager in case of emergency (i.e. the Manager misses the NE connection).
• NE Domain field allow selecting the domain among that displayed in the list, assigning it to the NE.
The different domains could be assigned to different operators.
OK button is used to validate the selection.
Cancel button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
Figure 21. Set Manager list
5.2 Set ACD level

This option allows the user to select the level of the Access Control Domain.
The ACD manage the concurrence of access among several different managers (i.e. RM and EML).
This only acts on the functions that can be used by different manager.
3AL 98325 ADAA 54/386
Select the Set ACD level option from the Configuration pull down menu.
• Current ACD level
Show the Access Control Domain level currently set.
• The Access Control Domain check level
Permit to set one of two level checks. By the way, this is an operation that should be performed only
during the EML-USM installation phase:
• NE level, the ACD is performed on all the NEs
• No Check, the ACD is not managed
The default value is NE level. If it is changed, it is necessary to restart the EML-USM.


Close button close the dialog without changes of the data.
Figure 22. Set ACD level
3AL 98325 ADAA 55/386
6 EXTERNAL INPUT AND OUTPUT POINTS MANAGEMENT
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 housekeeping alarm). It corresponds to an
external event, which is monitored by the NE. Number of relays on the NE is 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. An external
output point is independent from external input point.
The operations that can be undertaken in this section are:
-- Displaying external points,

-- Expanding or reducing external points list,

-- Configuring input and output external points.
6.1 Displaying external points

Select the External Points option from the Views pull down menu.
Figure 23. Opening the external points view

After selecting this menu option the external points view is displayed into the current window instead of the
current view.
3AL 98325 ADAA 56/386
Figure 24. External points view

The external points view displays a list of all input and output points.
The following information is given for each external point:
• The external point type: Input or Output.
• The user label: a user-friendly label associated to the configurable external point (see further the
paragraph External points configuration).
• 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.
Only for the “Output” external point there is the following information:
• The Output criteria: if configured, display the alarm event and the board effected associated to the
Output point (see further the paragraph External points configuration)
3AL 98325 ADAA 57/386
6.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 25. Expanding or reducing the external points list.
6.2 External points configuration

The configuration operations available on external points are:
• "User labels" configuration
• "External state". Can be set for output points (ON or OFF)
• "Output criteria" associated to the External output point
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.
Figure 26. Configuring external points.

The following dialogue box is then opened, displaying information about the selected external point (Input or
Output).
3AL 98325 ADAA 58/386
Figure 27. External input point configuration dialogue box
Figure 28. External output point configuration dialogue box (MANUAL)
3AL 98325 ADAA 59/386
Figure 29. External output point configuration dialogue box (FLEXIBLE)

Opening the dialog the current state of the selected External Point is shown.
1) External Input Point Configuration
• User Label: this field can be filled by the user with a Label that indicate the associated event that
must be taken under check (for example presences of water of fire in the room where the Equipment
is placed)
• External State: this field is set to off and can't be changed by the operator
• Probable Cause: the field is set to housekeeping and can't be changed by the operator
2) External Output Point Configuration
• User Label: this field can be filled by the user with a Label that 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 to "on" (alarm) or "off" (non alarm) only if "Manual" option has been
selected in the "Output Criteria" field.
• Output Criteria can be configured as:
• Manual (forced). The output contact is set in a fixed way, not depending on a particular event.
• For example the output contact could be used to "Manually" activate a pump 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 CT the couple event/CPO#, where the event is chosen between
a set of Output Criteria (LOS, RDI and LOF) and specifies 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.
3AL 98325 ADAA 60/386
7 DIAGNOSIS MANAGEMENT
Alarms are always present on the operator's workspace. The different types of alarms, their number and their
severity level, are represented in all Equipment views (NE views, Board views and Port views). An icon
representation is used, which change color when the relevant alarm is active. Thus, at all times, you know
the number of alarms and their severity relating to the equipment.
Access to the Alarm Surveillance to show the alarm condition is detailed in the following paragraph.
Than is presented the abnormal condition list (as result of operator's command such us loop, laser forced on
etc.).
At the end the Event log access is introduced.

Information about the significance of equipment alarms and status is given in the Maintenance
section.
7.1 Alarms surveillance

In this chapter 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:
• 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 alarms of the selected object and of the relevant subtrees 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
Figure 30. Alarm Surveillance Menu

Selecting any of the previously seen options, the Alarm surveillance report is displayed as for the example of
the following figure.
This view shows first a synthesis of the NE alarms (Counter Summary) with the sum of all alarms, then a
detailed list of alarms of the selected filter (Alarms Sublist).
3AL 98325 ADAA 61/386
Figure 31. Alarm Surveillance

Detailed information for each alarm is supplied.
For example the board in which the alarm is detected, the status of the alarm, the alarm type, the probable
cause.
The information supplied helps the operator, typically during troubleshooting operation, presented in next
section. (Maintenance section, where more details about alarms is given).
Detailed description is given in the AS Operator's Handbook.
3AL 98325 ADAA 62/386
7.2 Abnormal Condition List
The abnormal condition provides the synthesis of NE "not normal conditions" listing the events that
contribute to abnormal condition. Select Diagnosis->Abnormal Condition List.
Figure 32. Abnormal condition menu option
Figure 33. Example of abnormal condition list

The abnormal conditions are the following:
• Loopback
• ALS is disable and the laser is forced on or off
• Protection units (in case of EPS, SNCP and MSP if supported) are in lockout or in forced status
• Board (or sub-board) is placed in a not configured slot
Select an abnormal condition and click on “OK” to open the relative dialog window. Figure below is opened.
3AL 98325 ADAA 63/386
Figure 34. Example of loopback dialog window management

The other abnormal condition types will open the corresponding management window or will open the
window to navigate towards the management window.
7.3 Internal Link Monitor

This function improves, at the user interface level, the diagnostic associated to the hardware failure.
The presence of a failure on RX or TX side for the signal incoming/outgoing from/to the MATRIX is detected;
Internal Link Monitor displays a detailed localization of the link failure: a graphical representation of all NGI
link status, for the active and standby MATRIX is shown.
Select the Internal Link Monitor option of the Diagnosis menu.
As shown in Figure below. The first page displays the link status for the main MATRIX, the second one
concern the spare MATRIX.
In detail, each page contains the following functional blocks and graphical objects:
• The tab of the page displays the user label of the MATRIX board;
• The left side of the page displays the block representing the MATRIX board;
• The right side of the page displays the list of blocks representing the equipped boards; each block
displays a string contained the user label of the associated board;
• Two arrows are displayed between the MATRIX block and each board block; the two arrows
represent the link status in RX and TX side:
- A red arrow indicates a "link failure"
- A green arrow indicates a "working link"
• The Refresh button allows performing an explicit refresh of all the displayed information.
3AL 98325 ADAA 64/386
In order to indicate all the possible roots of the "link failure", all boards that detect the link failure are
represented by a red block in the page of the MATRIX main:
• a” port" board in represented by a red block if a link problem is detected in the NGI Rx from the
active MATRIX.
• A red block represents the MATRIX if a link problem is detected in one of the NGI Tx from one of the
possible "port" board.
Figure 35. Internal Link Monitor
Note: when either the system is not locked for at least 15 min or the system is in free-running /
holdover state, the information detected by the stand-by matrix is “not reliability”. As in this
condition, the red arrows from every port cards to Stand-by Marix (if exist) won’t trigger “link failure”
alarm.
Figure 36. Internal Link Monitor for stand-by Matrix when not synchronized
3AL 98325 ADAA 65/386
7.4 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 Log Browsing option.
Figure 37. Log Browsing option in Network Element context view

The Proposed option:
• Select the Alarm Log option (Log Id # 1) to access the Event Log file.
• The Configuration and Log Browsing ELM Windows open, permitting to analyze all alarms stored in
the NE.
• Refer to the "ELB Operator's Handbook"
• Select the Event Log option (Log Id # 2) to access the Event Log file.
• The Configuration and Log Browsing ELM Windows open, permitting to analyze all events stored in
the NE.
• Refer to the "ELB Operator's Handbook"
• Software Trace Log option is reserved to Alcatel personnel only.
7.5 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 etc.
The options used are:
• Upload Remote Inventory: store the Remote Inventory data in the Craft Terminal.
• View Remote Inventory: display the remote inventory data, previously stored in the Craft Terminal
by means the "upload remote inventory" performed in the "Supervision" menu.
Remote Inventory option of the Equipment.
7.5.1 Upload remote Inventory

This command stores the Remote Inventory data in the Craft Terminal.
Select the Upload Remote Inventory option of the Supervision pull down menu.
A confirmation dialog box is opened.
3AL 98325 ADAA 66/386
Figure 38. Remote Inventory confirmation request
Clicking on OK after a while an information dialog box is presented.
Figure 39. Remote Inventory completed
3AL 98325 ADAA 67/386
7.5.2 View Remote Inventory
This command displays the remote inventory previously stored in the Craft Terminal by means the Upload
remote inventory.
Select the View Remote Inventory option of the Diagnosis pull down menu.
The Remote inventory data appears.
Figure 40. View Remote Inventory

Data is displayed in specific fields:
• Company
It indicates the Company's (Alcatel's branch) which designs the unit.
Refer to Alcatel for the abbreviation's meaning (four characters).
• Unit Type
It indicates the units' acronym
• Unit Part Number
It indicates Alcatel or Factory product's Part No. The number indicated is that printed on the labels or on the
units' front cover plate.
• Software Part Number
It indicates the id. of the unit's resident software
• CLEI Code
It indicates the CLEI code according to Belle core specs. TR-ISD-325
3AL 98325 ADAA 68/386
• Manufacturing plant
It indicates the Company's manufacturing plant id. Within the company, producing the unit.
Refer to Alcatel for the abbreviation's meaning (four characters).
• Serial Number
It indicates the product's serial number as specified by the NR 130 Norm.
• 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 products 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- - - - "
3AL 98325 ADAA 69/386
8 COMMUNICATION AND ROUTING MANAGEMENT
8.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.
8.1.1 OSI Protocol on QB3/Qecc

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 MultiFinder 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 have to take routing decisions must became Intermediate Systems, all others can
be made End Systems
For the description of the following paragraphs use is made of Figure below. It is not a network-planning
example; it is only used to describe L1, L2, RAP and MESA.
8.1.1.1 Partitioning into Routing Sub domains

In order to reduce the overhead associated with distributed adaptive routing, it may be useful to divide a
adaptive routing domain into smaller routing sub domains, called areas or level 1 sub domain. A level 1 sub
domain should fulfill the following requirements:
• A level 1 sub domain should form a connected sub network; this sub network 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 sub domain;
• Each node which is connected to a foreign level 1 sub domain 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 sub domain;
• Level 2 intermediate systems must form a connected network, because level 1 path cannot be
utilized for level 2 communications. This network will be called level 2 backbones.
In the simplest case, all nodes within a level 1 sub domain share the same area address.
In general it is allowed to have multiple synonymous area addresses within a level 1 sub domain even if the
usage of this features 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 sub domain: there must be at least one area
address in common between their two synonymous list, otherwise they are not able to communicate with
each other.
3AL 98325 ADAA 70/386
8.1.2 Partitioning into separate Routing Domains
In certain situations it may be necessary 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 systems, whereby this link crosses routing domain boundaries. A Reachable Address
Prefixes is handled in the same way as information about a foreign level 1 sub domain within the own
domain. The Reachable Address Prefixes indicates that any packet whose destination network address
NSAP matches the prefix may be forwarded via the link with witch the prefix is associated.
For example, consider network, which is split into two separate routing domains:
• Routing domain A resides in a level 1 sub domain with area address "a"
• Routing domain B resides in a level 1 sub domain 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 sub domain, 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 sub domain. 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.
Figure 41. Routing sub domain organization example
3AL 98325 ADAA 71/386
8.1.3 IP over OSI tunneling for ATM/IP
This feature is applicable to NEs equipped with ATM/IP boards.
It permits to create a tunnel over OSI systems, to communicate IP management messages through an OSI
network; it encapsulates the SNMP messages of the TCP/IP protocol stack over the OSI stack, using CLNP,
LAPD, ECC protocols, and an OSI address. In this way the message reaches its final destination
8.1.4 OSI over IP tunneling on QB3

This feature 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 gets 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 below depicts the protocol architecture.
3AL 98325 ADAA 72/386
Figure 42. OSI over IP tunneling on QB3
8.2 Communication and routing views

To access select Comm/Routing option from the Configuration pull down menu as shown in the following
figure.
The Communication and Routing Views allows to perform 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
• Interface 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. This
information is stored in RAP table.
3AL 98325 ADAA 73/386
MESA Configuration: configuration of parameters necessary to the addressing of non IS-IS NE
in the same domain as the one of local NE. This information are stored in MESA table.
• IP Configuration Subdivided in:
IP Static Routing Configuration: definition of Host/Network destination address for IP static
routing
OSPF 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:
OSI over IP: definition of destination IP address for IP for OSI over tunneling
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 option of the menu, as shown in the
figure.
The options are described in next paragraphs.
Figure 43. Comm/Routing options
3AL 98325 ADAA 74/386
8.3 Local Configuration
Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading
menu the Local Configuration option.
The dialog-box opens and allows configuring 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 filed is 2 characters long
(2 hexadecimal digits) and, depending on the its value, the length of NSAP address is variable
from 16 characters to 40 characters:
o The value of AFI 49 identifies the local format of variable length (from 16 characters
to 40 characters).
o The value of AFI 39 identifies the ISO-DCC format of 40 characters long.
o 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:
o 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 or the operator
might select it.
o 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:
o a first string of two characters that identifies the AFI field

o a second string of variable length that identifies the remaining NSAP address
• Synonymous Area Addresses section allows having multiple synonymous area addresses within a
level 1 sub domain. 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 systems
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.
3AL 98325 ADAA 75/386
Figure 44. Local Configuration
8.4 OS Configuration
menu the OS Configuration option.
The dialog-box opens and allows configuring 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.
3AL 98325 ADAA 76/386
Figure 45. OS Configuration
8.5 NTP Server Configuration

menu the NTP Server Configuration option.
The dialog-box opens and allows configuring 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 enabling or disabling the NTP Protocol.
• Main NTP Server Address section contains the same graphical object of the Local Address Section
in the Local Configuration dialog-box.
• Spare NTP Server Address section contains the same graphical object of the Local Address Section
in the Local Configuration dialog-box.
If the NTP server is coincident with the OS (same hardware), the same NSAP address of the OS must be
assigned.
3AL 98325 ADAA 77/386
ED
02
Figure 46.
SC.3: NE MANAGEMENT
NTP Server Configuration
3AL 98325 ADAA

78/386
8.6 LAPD Configuration
Select the Configuration pull down menu. Select the Comm/Routing-> Interface Configuration option
and then from the cascading menu the LAPD Configuration option.
The "LAPD Configuration" dialog opens.
It contains the following functional block and graphical objects:
- A section named LAPD Interfaces List that allows the user:
• To display the list of configured LAPD Interfaces using a graphical table;
• To change the role of the LAPD Interface selected in the LAPD Interface List;
• To delete the LAPD Interface selected in the LAPD Interface List;

• To create a new LAPD Interface

- This section contains the following graphical objects:
• The number of LAPD interface displayed in the LAPD Interface List;
• The LAPD Interface List that lists all the configured LAPD Interfaces; for each LAPD Interfaces, the
table displays:
- The user label of the TTP containing the configured LAPD Interface (MS/RS/E1A TTP);
- The LAPD role that contains one of the following value:
• User
• Network
• Delete button that allows to delete the LAPD Interface selected in the LAPD table;
• Change Role button that allows too change the role (User or Network) of the LAPD Interface
selected in the table;
• Create button that allows to create a new LAPD Interface; this button starts a new dialog. Named
Create LAPD Interface; it is disabled when the maximum number of LAPD Interface has been
configured.
This Create LAPD Interface dialog contains the following functional blocks and graphical objects:
• A Choose button that allows the operator to select the superior TTP of the LAPD Interface to
be created; this button starts the TP Search dialog; the TP Search dialog will be configured in order
to display in the right tree only the allowed TTP of the LAPD Interface;
• A section LAPD Role that allows configuring the role (User or Network) of the LAPD Interface to be
created.
• 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.
- a section named Search Criteria that allows the user to display only the LAPD's of the selected type in
the LAPD Table; the section contains the following graphical objects:
• The field Interface Type that allows to select the type of the LAPD's to be displayed in the LAPD
Table; the field will manage both ADM and WDM DCC type; the value "Ignore" will allow to display
all the LAPD types;
• The Search button starts the search of the selected LAPD type; this buttons can be used to refresh
the LAPD table too.
3AL 98325 ADAA 79/386
The LAPD Interface List will be updated on reception of the Delete/Create/Change DCC CTP notification. If
no LAPD Interface is configured in the equipment, the message "No LAPD Interface" will be displayed near
LAPD Interface counter (that it is at zero)
Figure 47. Creation LAPD Interface
Figure 48. TP search dialog
3AL 98325 ADAA 80/386
Figure 49. LAPD Configuration dialog

Figure 50. Confirmation to change LAPD Role
3AL 98325 ADAA 81/386
8.7 DCC Cross Connection
DCC Cross Connection function is used in the LAPD management information by non Alcatel NE carried by
rs and ms DCC has to pass Alcatel Network for reaching a remote non Alcatel NE.
After configure DCC Cross Connection, it allows the non Alcatel LAPD pass-through. The solution is to route
transparently LAPD carried by rs and ms DCC.
N.B.The choice of RS or MS DCC to be terminated must be consistent through-out the network (i.e. in all the
Alcatel nodes it must be the MS to be terminated and the RS to be transparent – or vice versa)
This paragraph list the complete procedure to realize the example of DCC cross connection moving among
the various menus.
In the following example a LAPD carried by RS will be cross connected with another LAPD; the LAPD have
been created in the LAPD Configuration (refer to 8.6 LAPD Configuration).
– Select the Configuration pull down menu. Select the DCC Cross Connection option. The "Cross
Connection management for DCC" dialog opens
Figure 51. Select DCC Cross Connection
3AL 98325 ADAA 82/386
Figure 52. Cross Connection Management for DCC dialog

The following description lists the steps the user has to take to create a cross–connection using The “Cross
Connection management for DCC".
–Click the Create icon; the Main Cross Connection for DCC view will be opened.
N.B.After creation of a DCC cross–connection, the DCC cross–connection list in the Cross Connection
Management for DCC dialog is not automatically updated.
Use button Search in this dialog to update the list.
Create a DCC Cross–Connection
1)Select or type in the Input TP.
To enter the TP, click the Choose button and select the TP in the Search for DCC Cross Connection Input
dialog (see Figure 54.), or select the input field
and enter the name of the TP directly.
The Search for DCC Cross Connection Input dialog offers the possibility to list TPs according to different
filter criteria. First select the rack in the left list box, then select the filter criteria
Class "RS or MS" and click on button Search. The matching TPs are listed in the right listbox. Select the
input TPs in the list and confirm with Ok.
2)Select or type in the Output TP as described in Step 1).
3AL 98325 ADAA 83/386
ED
02
Figure 53.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Main Cross Connection for DCC dialog
84/386
ED
02
Figure 54.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Search for DCC Cross Connection Input view
85/386
Figure 55. Complete searching for input and output TP
Figure 56. Update DCC Cross Connection list by clicking Search icon
3AL 98325 ADAA 86/386
8.8 Ethernet Configuration
Select the Configuration pull down menu. Select the Comm/Routing-> Interfaces Configuration option
and then from the cascading menu the Ethernet Configuration option.
The dialog-box opens (figure below) and allows defining the parameters needed to manage a NE, which
provide a LAN Ethernet interface.
The following fields and data are present:
• Ethernet Interface field allows defining or removing a Local Area Network Port for the access to the
Data Communication Network.
• MAC Address section allows displaying the address of the Network Element in the Ethernet LAN; it
is a read-only field.
• OSI Section:
o 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.
o L1 Default Metric is a not modifiable field, Priority field can be set (default value for
Ethernet is 64)
o L2 Default Metric is a not modifiable field, Priority field can be set (default value for
Ethernet is 64)
• IP 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.
3AL 98325 ADAA 87/386
ED
02
Figure 58.
Figure 57.
SC.3: NE MANAGEMENT
Ethernet Configuration
3AL 98325 ADAA

Ethernet Configuration -- L2 only parameter
88/386
8.9 Reachable Address Prefixes Configuration
Select the Configuration pull down menu. Select the Comm/Routing -> OSI Routing Configuration option
and then from the cascading menu the RAP Configuration option.
The dialog-box opens and allows configuring 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.
The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing
device; each page represents a particular element of the RAP table and the respective pointing device
displays the element counter.

In detail, each page contains the following data:

• Physical Interface button
o 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.
o 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 addressing the element of a domain to be reached the Ethernet LAN;
the field is managed as a simple string of 12 digits.
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.
Figure 59. RAP Configuration
3AL 98325 ADAA 89/386
8.10 Manual ES Adjacencies table Configuration
Select the Configuration pull down menu. Select the Comm/Routing -> OSI Routing Configuration option
and then from the cascading menu the MESA Configuration option.
The dialog-box opens and allows configuring the Manual ES Adjacencies table.
Each element of the MESA table allows linking 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.
The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing
device; each page represents a particular element of the MESA table and the respective pointing device
displays the element counter.

In detail, each page contains the following data:

• Physical Interface button
o If the element is empty, displays the "none" value and allows selecting a LAPD ports
or a LAN port, which will be used to reach the End System element.
o If the element isn't empty, displays the selected port and allows changing it.
• System Id section represents the System Id of the ES element.
• MAC Address section allows addressing the element in the Ethernet LAN; the field is managed as a
simple string of 12 digits.
Apply button is used to perform a configuration change of the data contained in the complete MESA table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
Figure 60. MESA Configuration
3AL 98325 ADAA 90/386
8.11 IP Configuration
The options listed in the menu Configuration –> Comm/Routing –> IP Configuration and also in
Configuration –> Comm/Routing –> Tunneling Configuration is relevant to the configuration of
messages communications for the management of ATM or IP boards (ISA) inside the equipment and in the
network.
8.11.1 IP routing configuration for ATM/IP boards management

In order to manage the ATM/IP boards inserted into the equipment, the following operations are to be done:
• “IP Address Configuration of Point–to–Point Interface” defines the IP address for the
Equipment–Controller (EC). This should be the first addressing operation

•
Routing configuration, by means of the options:

– “IP Static Routing Configuration” if using static routing
– “OSPF Area Configuration” if using the automatic OSPF routing
• “ISA Board IP Address” it defines the IP address for the ATM or IP boards (ISA); it is to be defined
for every ISA board hosted by the equipment.
NOTE: if the ISA boards are in EPS 1+1 configuration, they must have the same address)
• “IP over OSI Tunneling” it defines the OSI address (NSAP) of the destination node to be reached
(for instance the GNE connected to the TMN), when the ATM/IP management message passes
through an SDH/OSI network; i.e. it is to be done for every SDH–NE of the network, if equipped with
ATM/IP boards.
NOTE: this addressing must be carried out at both end nodes of the tunnel, so that they can see each
other.
• “OSI over IP Tunneling” it defines the IP address of the destination node to be reached (for
instance the IP router where the TMN is connected), when an OSI management message passes
through an IP network. It is to be defined on a a Gateway Network Element (GNE) equipped with the
QB3 interface, where the QB3 is connected to a LAN/IP network.
NOTE: this addressing must be carried out at both end nodes of the tunnel, so that they can see each
other.
8.12 IP Static Routing Configuration

Select the Configuration pull down menu. Select the Comm/Routing -> IP Configuration and then from
the cascading menu, the IP Static Routing Configuration option.
The dialog box opens and allows configuring the parameters for IP Static Routing Configuration.
[1] Destination Host IP Address: allows defining the IP address necessary to reach a specific Host
[2] Destination Network: it is alternative to Destination Host IP Address; allows defining the IP Address IP
Mask to reach a network.
[3] Default Gateway IP Address: allows defining the address of the next hop gateway
[4] CLNP (Connection Less Network Protocol): allows to use a pre-define IP over OSI tunnel to 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
3AL 98325 ADAA 91/386
Apply button is used to perform a configure change of the data contained in the column of the table and
Figure 61. IP Static Routing Configuration
8.13 OSPF Area Table Configuration

Select the Configuration pull down menu. Select the Comm/Routing -> IP Configuration and then from
the cascading menu, the OSPF Area Table Configuration option.
The dialog-box opens and allows configure the parameters for OSPF (Open Shortest Path First) Area Table
Configuration.
• OSPF Area IP Address
• OSPF Area Range Mask
Both fields gives a synthetically information that includes all the addresses (specific 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 and
close the view is visible until the end of the operations and a wait cursor is displayed.
3AL 98325 ADAA 92/386
Figure 62. OSPF Area Table Configuration
8.14 IP Address Configuration of Point-to-Point Interfaces

Select the Configuration pull down menu. 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 and allows setting the Equipment Controller IP address used to communicate with the
ISA board.
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.
Figure 63. IP Address Configuration of Point-to-Point Interfaces
3AL 98325 ADAA 93/386
8.15 ISA board IP Address
Select the Configuration pull down menu. Select the Comm/Routing->IP Configuration and then from the
cascading menu, the ISA Board IP Address option.
The dialog-box opens and allows setting the IP Address of the ISA Board that communicate with the
Equipment Controller (EC).
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
Figure 64. ISA Board IP Address
3AL 98325 ADAA 94/386
8.16 OSI over IP
Select the Configuration pull down menu. Select the Comm/Routing->Tunneling Configuration and then
from the cascading menu, the OSI over IP option.
The dialog-box opens (Figure below) and allows configuring the Remote Destination IP Address of the
Equipment Controller.
Figure 65. OSI over IP Tunneling configuration

Apply button is used to perform a configuration change of the data contained in the complete table and
8.17 IP over OSI

Select the Configuration pull down menu. Select the Coo/Routing->Tunneling Configuration and then
from the cascading menu, the IP over OSI option.
The dialog-box opens and allows configuring the Destination NAPS Address and the IP Routing Type.
• Destination NAPS 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 field is 2 characters long (2 hexadecimal digits) and, depending on the its value, the
length of NSAP address is variable 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:
3AL 98325 ADAA 95/386
• 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 or the operator might select it.
• 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 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
Figure 66. IP over OS
3AL 98325 ADAA 96/386
9 Equipment Management
9.1 Introduction and navigation

This section deals mainly with the setting and changing of the boards present on the Equipment and
undertaking board protection operations.
Using the menu options, select the Equipment option from the View pull down menu.
The first level of the "Equipment Overview" representation will be displayed directly into the current window
The Equipment Overview enables a fast navigation through all levels of the equipment hierarchy. Navigation
is done from higher to lower levels.

The NE hierarchy is organized in the following way: subrack > board > port > TP.
Double clicking on the objects performs the navigation through different levels of the NE hierarchy:
• The first level shows the subrack level of the Equipment view;
• 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;
It is also possible to:
• Go back to the previous view, by selecting the Backward option from the views menu
• Go to the next view, by selecting the Forward option from the view menu
N.B. Selecting in the first level of the Equipment view (subrack level)
The Show supporting equipment option from the Equipment menu, the Rack level view is presented;
further, selecting in the Rack level view the Show supporting equipment option from the Equipment menu,
the Equipment level view is presented.
In the Rack level view, two subrack are presented:
• At the top the 1662SMC Subrack, named SR62C
• At the bottom the Fans Subrack, named SRFAN
The Fans Subrack presence is managed with the Set option as for the boards of the 1662SMC Subrack
Further, selecting in the Rack level view the Show supporting equipment option from the Equipment
menu, the Equipment level view is presented.
3AL 98325 ADAA 97/386
Figure 67. Equipment Overview -- Subracks levelz
Figure 68. Equipment Overview -- Rack level (without Fans subrack)
3AL 98325 ADAA 98/386
Figure 69. Equipment Overview- Rack level (with Fans subrack)
Figure 70. Equipment Overview - NE level
3AL 98325 ADAA 99/386
In the Subrack view it is possible use the options offered by the Equipment menu clicking on it in the menu
bar.
Alarms indications are present at every NE level.
Details about these alarms indication are given in the Maintenance section.
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.
Board administrative state that decides on the "in/out of service" of the board is also described.
Figure 71. Equipment menu

Equipment setting operation are defined according the following sequences:
- Configuration of a new board
• Configure the board using the option "Set"
- Change of board type
• "Set out of service" the board
• Configure the board using the option "Set"
- Remove a board
• "Set out of service" the board
• "Remove" the board
9.2 Set and change or remove board/subrack

The boards can be set, changed or removed using the menu options of the Equipment view.
a ) Setting or changing a board/subrack
A new board/subrack may be created in either an empty slot or it may replace an existing Out of Service
board/subrack (without the lock symbol). In fact, the Set option is available only after selecting an empty slot
or an Out-of-service board.
• Click on the empty slot in which a board/subrack has to be added, or on an existing Out of Service
board in order to change it. The contour becomes highlighted to show that operations can be done
on it.
• Select the Set option of the Equipment pull down menu.
• The following example of dialogue box containing a list of the different types of boards/subrack is
displayed.
3AL 98325 ADAA 100/386
Figure 72. The list of different boards relative to an NE slot (example)
N.B. The list of boards/subrack displayed during a "Set Board" operation is restricted to those, which the
equipment may accept in the selected slot. Therefore the list will vary depending on which slot has been
selected.
For details on the board/subrack identified by acronyms and NE physical composition please refers to the
Technical Handbook.
3AL 98325 ADAA 101/386
• Choose the board/subrack/access card 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.
Note: In case of 4xANY Modules it is also necessary to choose the type of user supported as shown
in Figure 64.
• The board/subrack 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 a Help view giving information about the context.
b) Removing a board/subrack
•
Click on the board/subrack 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.

• If the slot you are working on is already empty no name appears under the slot.
• Select the Remove option of the Equipment pull down menu.
• From the confirmation dialogue box that opens you can confirm or cancel the "Remove" operation.
N.B. It is possible remove a board only if it is not involved in any type of cross connection (OH bytes
included) or Performance monitoring.
c) Modify a board
N.B. This procedure can be done to replace an existing optical module with another of different type
without previously remove it.
• 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 option of the Equipment pull down menu.
3AL 98325 ADAA 102/386
Figure 73. Modify the module

• A dialog box containing a list of different types of optical module is displayed.
Figure 74. The list of different types of optical module (example1)
3AL 98325 ADAA 103/386
ED
02
Figure 75.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
The list of different types of optical module (example2)
104/386
ED
Table 1.
02
SC.3: NE MANAGEMENT
3AL 98325 ADAA
DWDM SFP module wavelength corresponding channel number
105/386
Chose the optical module type required by clicking on the corresponding item in the list; the name of the
module is highlighted.
• Click on OK push button to validate the choice.
• The board representation appears on the N.E. view in the slot when the board change is effective. A
padlock representation appears over the board.
Note: Slot 6 is auto set SYNTH16, when slot 6 is equipped with SYNTH4, the following procedures
need be done:
• When inserting the SYNTH4 in subrack slot 6, on Craft terminal a RUTM (unit type mismatch) alarm
will be present.
• On Craft Terminal in the Subrack level view select the SYNTH4 unit in slot 6
• Select the Modify option from the Equipment menu and select the SYNTH4 acronym from the list
then click on ok.

• Verify that the RUTM alarm disappear
9.3 Connect Fan to CONGI board

This command enable the Fan Subrack alarms management from CONGI in slot 10 or slot 12 according to
the option selected in the Equipment menu.
Figure below. Shows an example
Select the CONGI board
To enable this function select the Connect Fan to CONGI#1 option (or as alternative Connect Fan to
CONGI#20) of the Equipment menu if the supervision Fan Subrack cable is connected to CONGI unit
inserted in slot 1.
Figure 76. Connect FAN to CONGI
3AL 98325 ADAA 106/386
It is possible to disable this function by selecting the relevant CONGI board and then choosing the Remove
Fan connection from CONGI#1 option of the Equipment menu.
Figure 77. Remove FAN connection from CONGI
9.4 Board administrative state

The operator decides to set a board in service or out of service, if the NE allows it.
N.B. In the equipment view, a lock representation appears over the boards which are in "in service" state.
9.4.1 Setting a board in service

• In the Subrack NE view, click on the board in order to select it.
• Select the Set in service option of the Equipment pull down menu.
A lock representation appears over the boards.
9.4.2 Setting a board out of service

• In the Subrack NE view, click on the board in order to select it.
• Select the Set out of service option of the Equipment pull down menu. Select the Ok push button
in the confirmation window that appears.
A lock representation disappears, substituted by the symbol over the boards..
3AL 98325 ADAA 107/386
9.4.3 Consulting a Board's Administrative state
The board's administrative ("in service" or "out of service") state is indicated on the board view as shown in
the following figure.
Figure 78. Consulting a board’s administrative state
9.5 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 in which the software is wanted to know (COMPACT ADM unit). 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 Software description option of the Equipment pull down menu.
Opened dialogue box contains as many folder sheets as there is software in the selected board.
Click on the Close push button to close the dialogue box.
3AL 98325 ADAA 108/386
Figure 79. Software Description dialogue box.
9.6 Remote Inventory

This command displays the remote inventory data present in the Subrack and Boards.
• Select the Remote Inventory option of the Equipment pull down menu.
Two options are available:
• Subrack level: prints or write on a file the remote inventory data of the subrack.
• Board level: show the remote inventory data of the selected board
Figure 80. Remote Inventory menu

For the Board level a dialog similar to Figure below. Appear.
3AL 98325 ADAA 109/386
Figure 81. Remote Inventory dialogue box

The remote inventory data of the Subrack level can be printed on the default printer or to a file in postscript
or ASCII format.
Figure 82. Select Printer

N.B. If no printer is installed, there is no error message displayed to indicate this.
Figure 83. Select Output Format for file
3AL 98325 ADAA 110/386
9.7 Digital Diagnostic Monitoring (DDM)
In the new families of pluggable optical interfaces SFP, provides an extended set of information called Digital
Diagnostic Monitoring (DDM).
Such information reports the characteristic parameters of the interface; they are not static but dynamically
updated and directly pursued by the hardware component itself.
They are useful for indicating the performance of the optical interface and for monitoring a possible degrade
of the component.
Click the SFP module, select the Digital Diagnostic Monitoring option from the Equipment pull down menu.
Figure 84. select the DDM option

Then the Digital Diagnostic Monitoring dialog box is opened, the relevant parameters to be reported are:
– temperature, with 1/256 Celsius degrees as unit measure with range (-128, 128);
– power supply voltage, with 100microVolt as unit measure with range (0, 6.5V);
– transmitter laser bias current, with microAmpere as unit measure;
– transmitter output power, with dBm as unit measure;
– receiver input power, with dBm as unit measure
3AL 98325 ADAA 111/386
Figure 85. Digital Diagnostic Monitoring dialog box
9.8 Show supporting equipment

Click on Show Supporting Equipment menu option of the Equipment menu to navigate to the equipment
that supports the selected board.
Figure 86. Equipment Overview -- Subrack level
3AL 98325 ADAA 112/386
10 BOARD VIEW
10.1 Introduction
The Board View permits to show the physical port available in a specific board and to access the Port view.
The "Board view" is reached selecting the Equipment option in the View pull down menu, then double
clicking on the selected board to show the relevant Board view, presenting the ports.
In case of board with multi access SDH another view permits to select the SDH port.
An example of "board view" with the presented port is in Figure 88.
Alarms and Status indications referred to the board level are present at the bottom of the view, as indicated
in the example (Administrative State and Board Alarms/Status).

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.
In the Maintenance section details on this indication are given.
Figure 87. Equipment view: select the SDH port on a board
3AL 98325 ADAA 113/386
Figure 88. Example of a Board View

A port type is described with a board rectangular view and port identification.
The port identification is usually internal to the rectangular board (see Figure below. one example of optical
port)
(SDH) (ATM or IP) (PDH) (GBit ETHERNET)
Figure 89. Example of a Port identification and alarm synthesis

The following information is available:
• Type of port (name)
• State of port (alarm status synthesis)
• Symbol of the port
The operator is provided with a representation of the port alarm synthesis on each port.
The messages displayed at the top view provide port denomination.
The messages displayed at the bottom provide information about Board alarms.
3AL 98325 ADAA 114/386
A message under the mouse facility provides the name and the port type or the alarms name. A message
appears in the message area in the bottom left corner of the view.
By double clicking on a board view, it is also possible open the corresponding port view.
10.2 Board View Menu

Selecting the "Board" option in the menu bar the complete pull down Board menu is presented:
• Port Access: Access the "Port" view.
Note: this option is accessible after the selection of a port contained in the view.
• Change Physical Interface: Change the SPI or PPI object into PPI or SPI (and vice versa) on the bi-
mode port (140Mbit/s / STM-1 switchable).
• Show supporting equipment: Navigate to the upper subrack level.

• ISA Port Configuration: It allows configuring the TPs for the ATM connections.
Figure 90. Board menu options

These options are described in next paragraphs.
10.2.1 Port Access

Click on Port Access menu option of the Board menu to access the "Port View"
Navigation to the Port view permits to show a detailed alarm presentation of the port and to set the relevant
configurations.
3AL 98325 ADAA 115/386
Figure 91. After “Port Access” selection (example)
10.2.2 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
Select the Symbol of the port in the "Board view".
Click on Change Physical Interface menu option of the Board menu.
Figure 92. Change Physical Interface

The following dialog box is opened:
Figure 93. Change Physical Interface dialog box
3AL 98325 ADAA 116/386
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.
10.2.3 Show supporting equipment

Click on Show Supporting Equipment menu option of the Board menu to navigate to the subrack that
supports the selected port view.
Figure 94. Subrack level
3AL 98325 ADAA 117/386
11 PORT VIEW
11.1 Introduction
This section describes the operations necessary for the consultation, modification and configuration of each
port.
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).
In these views are presented only the TP specific of the port.

The menu differs according the port type (SDH, PDH, HOA, ATM/IP/ETH).
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 then double clicking
on the presented rack/subrack to present the subrack view, as described in chapter "Show supporting
equipment"
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.
The "Port view" is also reached selecting the Transmission option in the View pull down menu.
Then the Add TP option of the Transmission menu permits to select and confirm a TP.
On the transmission view, which appears, select the TP and on the Transmission menu select 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/IP/ETH TPs are not automatically created when the board is inserted in the subrack but must be
created as explained in chapter ATM/IP/ETH Configuration
From the Port view It is possible to Navigate to Transmission view.
The port types contain the following TP:
• SDH port: Electrical or Optical SPI TTP, RS TTP, prot TTP (MSP TTP), AU4 CTP, Trail Monitor (only
with enabled POM)
• PDH port: PPI TTP, En CTP, VCn TTP
• HOA port: VC4 TTP, TUG3, TUG2, TU3, TU12, Trail Monitoring (only with enabled POM)
• ATM port: VC4C TTP, VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP and E1 TTP
• PR_EA port: VC4 TTP, VC3 TTP and VC12 TTP
• Fast ETHERNET port: MAU, PTC, VC3XV, VC12XV, VC4 TTP, VC3 TTP and VC12 TTP
• Gigabit ETHERNET port: MAU, PTC, VC4XV, VC4 TTP, VC3 TTP and VC12 TTP
3AL 98325 ADAA 118/386
Figure 95. Example of a SDH Port View

On the port view, the messages displayed at the top view in the form of message boxes provide more
information concerning the type and the alarms of the port.
On the other hand the messages displayed at the bottom provide information about MSP protection and ALS
state (if they are supported).
A message under the mouse facility provides the name and the port type. A message appears in the
message area in the bottom left corner of the view.
11.2 Port View: elements on the TP

The symbols of the TPs have the following meaning:
• Alarm Icon Area
The icon boxes represent alarms. The color of the boxes changes according to the alarm severity.
• TP Role
The icon boxes represent the function: Adaptation, Termination or Compound Adaptation and
Termination.
• Cross-connected state
If the condition of the resource is cross-connected, an icon with a x appears beneath the box.
• Performance State
3AL 98325 ADAA 119/386
If the condition of the resource is under performance monitoring, an icon with a P appears beneath
the box.
• Loop state
If the condition of the resource is under loop, an icon with a L appears beneath the box
• Selected state
An orange frame around the box identifies the TP selection, so port menu refers to the selected TP.
Figure 96. Termination TP box.
Figure 97. G.783 Adaptation TP box.
3AL 98325 ADAA 120/386
11.3 Port View Menu
Selecting the "Port" option in the menu bar the complete pull down Port menu is presented.
The menu differs according the port type (SDH, PDH, HOA and ATM), and is introduced in the following:
• TP configuration: Set parameters for the Signal Label and Path Trace overhead on Synchronous
TP's.
• TP Threshold Configuration: Set B2 excessive BER and Signal Degraded parameter
• TP Frame Configuration: Set parameters for 2Mbit/s G.703/G.704 or ISDN-PRA management.
• Set Retiming: Enable/disable the retiming feature on the outgoing 2 Mbit/s signal.

• Cross Connection: Manage the connection of the paths.

• Monitoring Operations: Set parameters for POM/SUT and TC (Tandem Connection) TPs. Not
available for PDH port.
• Performance: See and Show Performance Monitoring parameters and data.
• Loopback: Manage the loopback commands, for commissioning or maintenance purposes
• MSP Manage the Multiplex Section Protection of the NE.
• Physical Media: Manage the physical setting of the TP of the port. Not applicable to HOA port. It is
described in the following paragraph.
• Show supporting board: Navigate to the upper board level. It is described in this chapter.
• Navigate to Transmission view: permit to show a complete overview about the signal flow, opening
all TP's
• Navigate to Monitor view: permit to show an overview about the monitoring operation (POM, SUT,
TC) all TP's.
Figure 98. Examples of port menu options (SDH, PDH and ATM port)
11.4 Set Retiming

The Retiming feature applies to the outgoing 2 Mbit/s and its purpose is 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.
3AL 98325 ADAA 121/386
When the Retiming feature is disabling, 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.
Figure 99. Set Retiming enable (before)

As result of this operation the state information color become green and the label "Retiming State Enable" is
written.
Figure 100. Set Retiming enable (after)
3AL 98325 ADAA 122/386
11.5 AU4 Concatenation
Select a STM-16 or STM-4 optical interface to configure as AU4 concatenation structure.
Zoom in to open the board and then the port view menu.
Select the AU4 Concatenation option from the Port menu to open Figure below. (In this example a STM-16
view is shown)
The STM-16 stream appears divided into different groups: not all AU4s can be chosen as first AU4 but only
AU4#1 AU4#5, AU4#9, AU4#13 for AU4c. Therefore for concatenated action of for AU4s in one AU4c these
AU4 streams are deleted and substituted by the new AU4c component.
Select the supported concatenation Number =4 (selection 64 is not operative) 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 101. AU4 concatenate/deconcatenate commands

The Concatenate button will be enabled and the Deconcatenate button will be disabled when is selected a
non concatenated AU4, vice versa when is selected a concatenated AU4.
3AL 98325 ADAA 123/386
Figure 102. Example of a concatenated AU4 transmission view

The port view represented in Figure up. Shows an STM4 interface with four AU4 concatenated in one AU4c.
The AU4c appears as a single icon that has the same size of the actual AU4 blocks. The AU4c streams
support the Alarm synthesis, Cross-Connection states and Performance Monitoring information as standard
AU4 streams.
To deconcatenate an AU4c select again the "AU4 Concatenation" option in the Port View menu and then
select the AU4c to deconcatenate. Click on the Deconcatenate push button to apply the command or on
Cancel to exit.
Figure 103. Example of a concatenated AU4c
3AL 98325 ADAA 124/386
11.6 Physical Media option menu
The Port -> Physical Media options permit to set physical configuration of each TP of the port.
The Physical Media options are also accessible from the Transmission menu.
It opens a menu that differs according the port type:
• SDH port:
- ALS Management
- Show Optical Configuration
- Tx Quality Configuration
- Single Fiber Configuration

- LAPD Configuration
- Ms Configuration
• PDH port:
- Line Length Configuration.
- HDSL Configuration. Not operative
- NT G703/704 Configuration. . Not operative
- NT X21 Configuration. . Not operative
• ETHERNET port:
- Remote Laser Management. Not operative
- ALS Management. Not operative
- Ethernet Port Configuration
- Ethernet Mapping Protocol.
- ATM/IP/ETH Configuration
- Control Path Activation.
These options are described in next paragraphs except the previously referenced.
Figure 104. Physical media menu (SDH port example)
3AL 98325 ADAA 125/386
11.6.1 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 safety 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 SPI block in the port view and then select the Port pull down menu.
Select the Physical media option and then from the cascading menu the ALS Management option.
The Automatic Laser Shutdown State dialogue box opens.
Figure 105. Automatic Laser Shutdown Management

The dialogue box enables the ALS Management and the Restart parameters. The following actions are
available
a) Allow Automatic Laser Shutdown.
To allow 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.
1) Force laser ON.
3AL 98325 ADAA 126/386
To carry out a laser forced ON, select the Laser Forced ON option of the ALS Function
then click on Apply and then or close push button to close the dialogue.
2) Force laser OFF.
To carry out a laser forced OFF, select the Laser Forced OFF option of the ALS Function
then click on Apply and then or close push button to close the dialogue
c) Delete: this option deactivates the ALS function, returning to the state.
From this window it is only possible to create the ALS function (all ALS commands are grey)
Figure 106. Automatic Laser Shutdown Management (after ALS Function delete)
d) Enabling or Disabling Automatic / Manual Laser Restart.
To enable (disable) an automatic laser restart following an automatic laser shutdown
(periodic restart), select the Enabled (Disabled) option of the ALS Auto Restart. The laser
will be ON for 2 secs and OFF for 70 secs, in periodic mode. The same procedure is
applicable for the ALS Manual restart: while the ALS auto Restart is disabled, the manual
restart permits to permits to perform a laser restart for single time period.
e) Wait to restart time
The Wait To Restart Time: field indicating the delay period in seconds, occurring before an
automatic laser restart is launched (following an automatic shutdown). The restart time
period for this equipment is fixed to 70 secs.
f) ALS Manual restart
When the ALS Manual Restart is Enabling it is possible to enter two different commands:
Manual or Test Restart. The manual command immediately activates a single laser restart:
this command overrides the wait to restart time. The test restart is similar to the manual
restart but the laser remains "ON" for a longer time in order to make a measurement of the
received optical power.
When all the different parameters have been configured, select the Apply button to confirm the setting and
close the dialogue box.
Selecting only 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 and the ALS
state has not to be confused with the laser state.
ALS states (see example of), displayed by the functional state message area of the optical port, are:
ALS states:
Inactive = No ALS has been activated (Off) or the laser has been Forced ON/OFF.
3AL 98325 ADAA 127/386
In test = the laser restart has been automatically activated.
Active = The ALS has been activated (On).
Undefined = The ALS is not present (not created).
Laser state:
On = all OK or ALS not present (not created).
Off = Laser off (when ALS is created).
Forced on = ALS forced on by operator command.
Forced off = ALS forced off by operator command.
Figure 107. ALS and Laser current state (example)
11.6.2 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 the SPI block, then click on Show Optical Configuration option from the
Physical media pull down menu to visualize the parameters of the selected optical port.
Shows an example of the parameters of the selected interface.
N.B. This dialogue box can only be read. You cannot write in the entry boxes.
Figure 108. Visualizing a port optical parameters

The laser ports are identified by three major characteristics:
• STM Level: describes the input/output optical interface types: STM1/STM4
• The wavelength of the laser source: the units are nanometers (nm = 10-9 m).
3AL 98325 ADAA 128/386
• The use of the port: describes whether the laser port is used for interoffice transmissions on long
distances (Long Haul) 40 km) or for interoffice transmissions on short distances (Short Haul ] 15
km).
The Colored Interface Parameters section is not applicable in the current release
To close the dialogue box click on the Cancel push button.
11.6.3 Single Fibber Configuration

The single fiber configuration can be realized with passive optical couplers.
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 below. Shows that are
accepted the label "1" from Tx1 to Rx2 while is accepted label "2" from Tx2 to Rx1.
Figure 109. Bidirectional Transmission on a single fiber

Select the Physical media option and then from the cascading menu the SDH Single Fiber Configuration
option.
In the figure that opens, the following fields have to be considered:
• Allow Single Fiber - select the transmit mode on the single fiber (enable or disable).
• Transmitted Section:
⎯ Transmitted Media Byte - assigned label to Tx (0-14)
⎯ Transmitted Media Type - overhead byte used for the communication:
- Media Dependent byte of Regeneration Section or
- S1 byte of Multiplex Section (the part not used for the SSM)
• Received Section:
⎯ Received label
⎯ Expected label (0-14)
3AL 98325 ADAA 129/386
Figure 110. Single Fiber Configuration View
11.6.4 Ms Configuration
The Ms Configuration menu allows the SS bit provisioning for Multiplex Section Object (MSTTP) in
SONET/SDH network interworking.
Select the MSP TP.
Click on Ms Configuration menu option of the Port menu.
This dialog allows selecting between SDH or SONET networks. After the selection click on Apply and then
on Close to close the dialog.
Ms Forced AIS is not supported in the current release.
Figure 111. Ms Configuration
3AL 98325 ADAA 130/386
11.6.5 Line Length Configuration
To manage the Line Length configuration click on Line Length Configuration menu option of the Physical
Media menu.
This dialog allows configuring the line length for a PDH PPI TP of a 45 Mbit/s port.
The OK button validates the configuration and closes the dialog box.
The Cancel button removes the dialog
Figure 112. PDH Line Length Configuration View
11.6.6 Ethernet Port Configuration

To set Ethernet port parameters, select the Ethernet Port Configuration option of the Port -> Physical
Media menu as shown in Figure below.
Figure 113. Ethernet Port Configuration options
Subsequently Figure below. Will be opened.
3AL 98325 ADAA 131/386
Figure 114. Ethernet Port Configuration Dialog

For the Fast Ethernet (10/100 Mbit/s) port it is possible to choose between two “Configuration Type”:
1. Auto navigation “: enable allows to configure the "Rate" to be negotiated (10 or 100 Mb/s). The
"Directionality" (Full Duplex) and the "Flow Control" (Activated) are always enabled and can't be
changed.
2. "Manual”: allows forcing the "Rate" at 10 or 100 Mb/s.
The "Directionality" is always Full Duplex.
Moreover It is possible to Restart the “Auto Negotiation” by depressing the relevant button; if parameters
has been changed before pressing the Restart button, a question dialog is displayed to advice that the user
has changed data but not applied them.
Figure 115. Information dialog

In read only mode there are indication if the Auto negotiation on remote side is activated (Remote Auto
Negotiation) and what parameters are allowed on remote (Remote Allowed Parameters).
In both cases is possible to check the “Auto negotiation Current State” with the possible massage:
– Completed OK
– Completed KO
– Configuring
– Deactivated
– Parallel Defect Fail
– Other
At the bottom of the port view are displayed the following indications:
3AL 98325 ADAA 132/386
– The “Interface Type”:
• S1000 Base SX (only for Gigabit Ethernet board)
• S1000 Base LX (only for Gigabit Ethernet board)
• S1000CX (only for Gigabit Ethernet board)
• S100BaseTX
• S100BaseFX
• Unknown
• S10BaseT
– The “Bit Rate” (only for fast Ethernet board):
• 10 Mb/s
• 100 Mb/s
Figure 116. Gigabit Ethernet port view (example)
3AL 98325 ADAA 133/386
11.6.7 Ethernet Mapping Protocol
Select a VC TP.
Click on Port Ethernet Mapping Protocol option of the Port–> Physical Media menu. Figure below opens.
Figure 117. Ethernet Mapping Protocol (EXAMPLE)

This dialog aims to show the actual Ethernet mapping protocol used and allowing the user to change it. The
options available are the following:
– FAST ETHERNET boards:
⎯ GFP null extension Header with FCS
⎯ GFP null extension Header without FCS
⎯ GFP for packed concatenation extended
– GIGABIT ETHERNET boards:
⎯ GFP null extension Header with FCS
⎯ GFP null extension Header without FCS
11.6.8 Control Path Activation

This dialog allows modifying the state of the Ethernet and DVB-ASI port virtualTPs.
Select a TP in the Ethernet port view window.
Click on Control Path Activation option of the Port–> Physical Media menu.
A new window will be opened; a similar window is display when a new concatenated VCX is created in the
“ISA/IP/ETH configuration” window.
This dialog aims to show the activation state of the virtualTPs present in the Ethernet Port View and to
change the number of virtualTPs active.
The Active state is reached by choosing the number of “Virtual TPs to be active” and click on the Apply
button.
3AL 98325 ADAA 134/386
Figure 118. Control Path Activation (example on Fast Ethernet board)

On the contrary to change in Idle the Active state of a TP decrease the “Virtual TPs to be active” field and
then and click on the Apply button.
Click on the Refresh button to update the changes.
Click on Close button to close the Control Path Activation window.
Example figure below is the Active state.
Figure 119. Control Path Activation: Range Path mode
3AL 98325 ADAA 135/386
11.6.9 LCAS Configuration
11.6.9.1 LCAS Introduction

The LCAS protocol is supported since R. 2.1 in ISA Ethernet Switch board at STM-1 ES1-8FE/8FX and since
R.2.2 in ISA Ethernet switch at STM-4. Board and ISA Gigabit Ethernet (GETH-MB).
11.6.9.1.1 LCAS parameters

The indication that LCAS protocol can be activated on a virtual concatenation group is represented by the
instantiation of the conditonal package lcasControlPackage on vc-nXVritualTTP (n=12, 3, 4). The following
conditonal packages have to be instantiated on vcnXVirtualTTP (n=12, 3, 4) for supporting lcas specific
parameter:
• MaxDifferentialDelayPackage for reporting the max supported (by the board) differential delay and
for configuring the maximum tolerated differential delay; the default value has been chosen at
48(ms).
• RsAckTimeoutPkg for configuring the timeout of re-sequence acknowledge; the default value has
been chosen at 512 (ms).
Note: the conditional packages tsdContributionPkg, holdOffTimeAndWTRPackage have not to be
instantiated.
3AL 98325 ADAA 136/386
11.6.9.1.2 LCAS operations
The action control Path Activation allows to activate (ADD) more than one member (vc-nVirtualTTP) with a
single manager request.
Similarly is possible to de-activate (REMOVE) more than one member (vc-nVirtualTTP) with a single
manager request.
The capability of de-activating (REMOVE) specific members ( vc-nVirtualTTP) is supported, this
functionality is not working if LCAS protocol is not activated, but it’s possible to de-activate from last active
member. Symmetrically the capability of activating (ADD) specific members ( vc-nVirtualTTP) is supported.
The activation of LCAS protocol on a virtual concatenation group already working is possible, but it’s a traffic-
affecting operation since it requires to de-activate all members before LCAS enabling.
The symmetrical operation (even if not meaningful) of de-activing the LCAS protocol on a virtual
concatantion group already working is possible, such operation impacts the traffic bandwidth transmission
since it requires of remaining with only the vc-VirtualTTP with ID=1 as active member.
11.6.9.1.3 LCAS protocol information

For monitoring the LCAS protocol the LCAS Monitor action is provided; some parameters returned by the
action are defined as Optional, the following ones are expected to be anyway returned: the number of
working members in tx, the number of working members in Rx, the member identifier reference for MST
(TBC), the received rs-ack bit (TBC), the transmitted rs -ack bit (TBC), the differential delay of each member.
11.6.9.1.4 Alarm indications

If the LCAS protocol is activated the following alarm indications can be raised:
At virtual path level (vc –n Virtual TTP, n=12, 3, 4)
• Member Not De-skew-able (probable Cause excessive Differential Delay): when the virtual path has
a differential delay which can’t be compensated; if LCAS is not activated this alarm corresponds to
Loss Of Alignment alarm raised at virtual group level (virtual PTC). at virtual concatenation group
level (vc-nX Virtual TTP, n=12, 3, 4):
• Loss Of Partial (probable Cause bandwidth Reduced): when one of active members vc-n Virtual TTP)
is affected by SSF, TIM, UNEQ, L OM or Excessive Differential Delay.
• Loss Of Total (probable Cause server Signal Failure): when all the active members are affected by
SSF,TIM, UNEQ, LOM or Excessive Differential Delay.
• LCAS protocol failure (probable Cause communications Protocol Error) raised when inconsistent
sequence numbering of the members is received or the CRC error control fails on LCAS multiframed
packet.
11.6.9.2 LCAS Configuration

This dialog allows modifying the state of the Ethernet port.
Select a TP in the Ethernet port view window.
Click on LCAS Configuration option of the Port–> Physical Media menu.
A new window will be opened; a similar window is display when a new concatenated VCX is created in the
“ISA Port configuration” window.
This dialog aim is LCAS (Link Capacity Adjustment Scheme) protocol management of the TPs present in the
Ethernet Port View.
The button "Apply" will set the configuration if the LCAS protocol is enabled.
3AL 98325 ADAA 137/386
In the following picture we can note that are managed all the attributes described before and the two actions
are managed by means of the two buttons (Enable/Disable and Monitoring...).
Figure 120. LCAS Configuration
The "Monitoring..." button start the "LCAS protocol monitoring" view like the figure below.
Figure 121. LCAS Monitoring
3AL 98325 ADAA 138/386
The LCAS Monitoring window is divided in two section, the first reports information concerning the Virtual
Concatenation Group Monitoring Parameters, the second reports the Channels Monitoring Parameters.
Virtual Concatenation Group Monitoring Parameters fields description:
– Active Channel Number: display the number of Vcs active on Source and Sink read on Node A.
– Acknowledge Bit (Re–Sequence Acknowledge) Source and Sink: when a renumbering of the
sequence numbers of the members sending in CTRL field NORM, DNU, EOS, or when a change of
the number of these members is detected at the Sk, a notification to the So per VCG has to be
performed by toggling (i.e. change from ’0’ to ’1’ or from ’1’ to ’0’ ) the RS–Ack bit.
– MST Channel Ref.: indicates wich channel of the VCG is the reference one for MST information;
MST information report the member status from Sk to So with two states: OK or FAIL (1 status bit
per member).OK = 0, FAIL = 1.
– VCG Master: indicates wich channel is the reference channel for the Differential Delay calculation.
Channels Monitoring Parameters fields description:
– The first column contains the channel identifier inside the VCG (called Sequence Number) .
– Tx CTRL Packet: Message sent (ADD, DNU, IDLE, NORM, EOS, FIXED), relative to a traffic flow
from Node A to Node B; it provides the status of the individual member of the group as reported in
the following:
• Fixed: this is an indication that this end uses Fixed bandwidth (non–LCAS mode)
• Add: this member is about to be Added to the group
• Norm: Normal transmission
• Eos: End of Sequence indication and Normal transmission
• Idle: this member is not part of the group or about to be removed
• Dnu: Do Not Use (the payload) the Sk side reported FAIL status
• Unknow
– Rx Channel State: MST indication (OK/FAIL) relative to a traffic flow Node B to Node A;
– Rx CTRL Packet: Message received (ADD, DNU, IDLE, NORM, EOS, FIXED), relative to a traffic
flow from Node B to Node A; it provides the status of the individual member of the group as reported
in the following:
• Fixed: this is an indication that this end uses Fixed bandwidth (non–LCAS mode)
• Add: this member is about to be Added to the group
• Norm: Normal transmission
• Eos: End of Sequence indication and Normal transmission
• Idle: this member is not part of the group or about to be removed
• Dnu: Do Not Use (the payload) the Sk side reported FAIL status
• Unknow
3AL 98325 ADAA 139/386
– Tx Channel State: MST indication (OK/FAIL) relative to a traffic flow Node A to Node B;
– Differential Delay: it is calculated respect to the Virtual Concatenation group Master channel,
relative to a traffic from Node B to Node A .
– TxVC: contains the sequence number assigned to a specific member from Node A to Node B. Each
member of the same VCG is assigned a unique sequence number, starting at 0.
– RxVC: contains the sequence number assigned to a specific member from Node B to Node A. Each
member of the same VCG is assigned a unique sequence number, starting at 0.
The Refresh button refreshes the values displayed.
11.7 TP Frame Mode Configuration

This menu item enables the configuration of the most important transmission parameters concerning the
Primary Rate Access (PRA) and G.703/G.704 frame management.
PRA management
The PRA functionality performs termination bi–directional function for Time Slot 0 on framed with CRC–4 2
Mbit/s signal.
In detail, it extracts in sink direction and writes in source direction particular bits (E, Sa5, Sa6 and A) of the
Time Slot 0.
Moreover, it generates substitution frames in case of detection of LOS on the signal coming from a
Terminal Equipment.
The PRA functionality has been extended in order to manage proprietary handling of the bits of Time Slot 0
(Framed with leased line PRA option) in terms of state, defect detection and consequent actions.
G.703/G.704 management
This functionality allows to activate the adaptation function to process a framed (G.704 interface) or not
framed (G.703 interface) 2Mbit/s signal.
This TP Frame Mode Configuration option is available for: – P12–CTP
Select the desired P12–CTP and then the Port –>TP Frame Mode Configuration option.
TP Frame Mode Configuration can also be accessed from the “Transmission” and “Synchronization” view
menu.
The following dialog appears:
3AL 98325 ADAA 140/386
Figure 122. 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:
• ”Not Framed” (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 is activated
• ”Framed with leased line PRA”: a proprietary leased line behavior is applied.
– “CRC4 Status“ that defines the monitoring capabilities applied to the signal with a CRC multiframe:
•“Operation”: allows configuring the CRC–4 processing modalities; the possible value is:
• “Disabled” that disables the CRC–4
• “Forced” that configures CRC–4 with consequent actions
• “Automatic” that triggers the CRC–4 algorithms in order to allow interworking of pieces of equipment
with and without a CRC4 capability.
• Monitoring 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.
– “Loss of Synch Consequent Action” allows to perform the consequent action on the transmitted
3AL 98325 ADAA 141/386
2M/s signal with retiming when the CRU is in Holdover or Free running mode; the consequent action is
performed only if PRA or leased line application ha been configured on the associated P12–CTP.
– “Frame Status” is a read–only field 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.
3AL 98325 ADAA 142/386
11.8 Show Supporting Board
Select a TP.
Click on Show Supporting Board menu option of the Port menu to navigate to the board that supports the
selected port view.
Figure below. (Example) opens.
Figure 123. Board View Example
3AL 98325 ADAA 143/386
11.9 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 124. “Navigate to Transmission view” selection
3AL 98325 ADAA 144/386
ED
02
Figure 125.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
After “Navigate to Transmission view” selection
145/386
11.10 Navigate to Monitoring View
Select a TP where are configured some Monitoring Operations (POM, SUT, TC)
Click on Navigate to Monitoring View menu option of the Port menu to navigate to the corresponding
Monitoring View that is related to the selected TP.
Navigation to the Monitoring view permits to show a complete overview about the Monitoring Operations
(POM, SUT, TC) as for the example of the following figure.
In figure below is shown an example of Monitoring View of a TP with POM and TCM both before and after
matrix.
Figure 126. View of Monitoring Operations (example)
3AL 98325 ADAA 146/386
11.11 Port Mode Overview
Click on Port mode option of the Configuration–> Port mode menu. Figure below.
Figure 127. Port Mode Menu Option
Figure 128. Port Mode Overview Dialog

You can select the port type you want to see, and click the search button to list them. As below, then you can
click the port you want to set at the found port list table. And set the port mode.
Port Mode Overview Dialog allows a centralized mechanism for:
– System wide search for Port Mode settings
– Change of Port Mode setting
– Change of Port Mode default.
3AL 98325 ADAA 147/386
System wide search capability is offered in order to show port mode value representation for all ports in a NE
or in a port subset.
The subset is defined according to the filtering capabilities on Port Type (all ports, SDH port Only, PDH port
Only, Ethernet port only, CWDM port only) and to the Port Mode set (Ignore, Mon, Auto).
To prevent alarms from being raised and failures being reported during trail provisioning actions, trail
termination functions have the ability to enable and disable fault cause declaration.
This is controlled via their termination point mode or port mode parameter.
The termination point mode can be either “monitored” (MON) or “not monitored” (NMON). The state can be
MON if the termination function is part of a trail and provides service and NMON if the termination function is
not part of a trail or is part of a trail which is in the process of set-up, breakdown or re-arrangement.
In physical section layers, the termination point mode is called the port mode. It has three modes: MON,
AUTO, and NMON (the last is not supported).

The AUTO mode is like the NMON mode with one exception: if the LOS defect clears, the port mode is
automatically changed to MON. This allows for alarm-free installation without the burden of using a
management system to change the monitor mode.
Change of Port Mode setting can be done on the selected ports in the matrix gadget. Multiple selection is
allowed. The user can choose the new Port Mode (in the Define Port Mode Values field) and can start the
change on the selected ports (Set Mode).
Change of Port Mode System Default can be done in the related frame Current system default is visualized
in the combo box current value. Port Mode Overview dialog is available both at Configuration menu and Port
View menu and Transmission View as well. Using it at Configuration menu the “multi port” working mode is
enabled with full support for search and filtering. Using it in Port View or Transmission View enable the
“single port” functionality and the search capability is greyed out.
Figure 129. set the selected port mode
3AL 98325 ADAA 148/386
12 Equipment Protection management (EPS)
12.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 EML-USM.
Switching the board supporting the protected service when this board fails to a protecting board capable of
supporting the same service performs the protection. This protection is realized according to a protection
scheme.
An equipment protection scheme is composed of the following parameters, which can be configured:
• 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 reliable resources. 1+1 group type means that one protecting unit protects a working element.
1+n group type means that only one protecting unit protects n working elements.
• Protection priority:
A priority can be assigned to protected units in 1+n protection schemes. This priority can 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 to restore time:
Used when revertive mode is active, the protection wait to restore time prevents several protection
switches due to an intermittent failure. A protected element must be fault free 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:
• Consult and modify an Equipment Protection Scheme (EPS),
• Manual Switch EPS,
In Board view, the board whose content is represented is considered as implicitly selected.
The functional state message area of the boards involved in an equipment protection scheme displays EPS
protection states.
12.2 Management: consulting and modifying EPS

In order to consult EPS, perform the following operations:
The "Port view" is reached selecting the Equipment option in the View pull down menu to present the
subrack view.
• Select the Equipment option in the View pull down menu.
3AL 98325 ADAA 149/386
• Select the EPS pull down menu. Then select the Management...
Figure 130. Consulting EPS

Figure 131. EPS Management dialogue box

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 available protection schemes are coherent with the NE type and release.
The right side of the dialogue box allows modifying the EPS configuration.
The current release of this NE fixes the following protection:
• N+1 (with N ≤ 3) "P63E1 or P63E1N" protection
- Board of slot MAIN (protected): P63E1 or P63E1N, slots 7 to 14.
- Board of slot SPARE (protecting): P63E1 or P63E1N, slot 7 to 14..
• N+1 (with N≤7) "P3E3/T3" protection
- Board of slot MAIN (protected): P4E3/T3, from slot 7 to 14.
- Board of slot SPARE (protecting): P3E3/T3, from slot 7 to 14..
• N+1 (with N ≤7) "P4ES1N" protection
- Board of slot MAIN (protected): P4ES1N, from slot 7 to 14.
- Board of slot SPARE (protecting): P4ES1N, from slot 7 to 14..
3AL 98325 ADAA 150/386
N.B. For P3E3/T3 and P4ES1N more than one protection group N+1 revertive can be created, depending
on the equipment configuration. The spare board position can be assigned in a flexible way. The only
constraint is 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
- The protecting/protected group of ports have to be of the same type
• 1+1 “DVB-ASI” pretection

The DVB-ASI boards can be protected in 1+1 equipment protection scheme.

In the configuration the DVB-ASI and all indirect interfaces connected to it are protected against
module failure. It does not apply to the local interface so the traffic on it is lost.
A maximum of four protection groups 1+1 not revertive can be created.
The spare card 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 ISA-HPROT card
- the ISA-HPROT card has to be plugged in the left side of the ASI-ABNC access card
- the main/spare ASI-MB boards have to be adjacent
- the protecting board has to be plugged in the left side of the protected board.
• 1+1 "ATM MATRIX 4x4" protection

The ATM MATRIX board can be protected in 1+1 equipment protection scheme. In this configuration
the ATM MATRIX and all indirect interfaces connected to it are protected against ATM module failure.
This does not apply to the local STM-1 interface so the traffic on it is lost. A maximum of two
protection group 1+1 not revertive can be created. The spare card position can be assigned in a
flexible way; no restriction for position of main and spare ATM MATRIX is present.
• 1+1 "ATM MATRIX 8x8" protection
The ATM MATRIX board can be protected in 1+1 equipment protection scheme. In this configuration
the ATM MATRIX and all indirect interfaces connected to it are protected against ATM module failure.
A maximum of two protection group 1+1 not revertive can be created. The spare card position can
be assigned in a flexible way; no restriction for position of main and spare ATM MATRIX is present.
• 1+1 ISA PR_EA (PREA4ETH, PREA1GBE)” protection
The ISA PR_EA boards can be protected in 1+1 equipment protection scheme. In this configuration
the ISA PR_EA and all indirect interfaces connected to it are protected against module failure. This
does not apply to the local interface so the traffic on it is lost. A maximum of two protection group
1+1 not revertive can be created. The spare card position can be assigned in a flexible way; no
restrictions for position of main and spare ISA PR_EA are present.
• 1+1 ISA ES-16 protection
The ISA ES-16 boards can be protected in 1+1 equipment protection scheme.
In this configuration the ISA ES-16 and all indirect interfaces connected to it are protected against
module failure.
A maximum of four protection group 1+1 not revertive can be created.
3AL 98325 ADAA 151/386
The spare card 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 ISA PROT card
• the ISA PROT card has to be plugged at the left side of the GETH-AGR or ETH-AFX
access card
• the main/spare ISA ES-16 boards have to be adjacent.
• the protecting board has to be plugged at the left side of the protected boards
• 1+1 "COMPACT ADM" protection
- Board of slot 6, COMPACT ADM main (protected)
- Board of slot 15, COMPACT ADM spare (protecting)
N.B. For each type of failure on the MATRIX main board (CRU, Shelf Controller) a switch is performed to
the spare boards
The COMPACT ADM protection is automatically presented in the left side of the dialog box when
the SPARE COMPACT ADM is created in the Set option of the Equipment menu. It is not created with
the EPS menu described in this chapter. In current release SYNTH16 can not protecte SYNTH4, and
vice versa. It means when SYNTH16 is inserted in slot6, slot 15 must be equipped with SYNTH16 but
not SYNTH4. For SYNTH4, the rule is same.
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. 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
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
3AL 98325 ADAA 152/386
To delete an existing protection scheme, the user selects a scheme in the left list. Using the Delete button,
user could delete the scheme.
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 cancels the creation and closes the dialog box.
Figure 132. EPS: board selection
Figure 133. EPS: choose protected
3AL 98325 ADAA 153/386
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.
Figure 134. EPS functional state from protected active board view
Figure 135. EPS functional state from protecting active board view
12.3 Configuration: revertive and WTR for EPS

This functionality configures Revertive and Wait Time to restore in a protection scheme.
In order to configure, perform the following operations:
• Select a transmission board in the Equipment view.
• Select the EPS pull down menu. Then select the Configure.
Figure 136. Configure EPS

Figure 137. EPS Management dialogue box

The dialog box provides configuration for elements such as:
• The name of the protecting element as a label
• The Equipment Type (board) of the protecting element as a label
• A list displaying the protected elements owned by the scheme
3AL 98325 ADAA 154/386
• The Revertive Mode flag as an option menu. The available values are revertive and non revertive
• The wait time to restore time value (steps of 30 seconds, from 60 to 600). Only for N+1 EPS.
Notes: in the current release the Wait Time to Restore is fixed to 5 minutes.
For this NE:
• 1+1 ATM MATRIX 4x4 is Not Revertive only
• 1+1 ATM MATRIX 8x8 is Not Revertive only
• 1+1 PR_EA is Not Revertive only
• 1+1 ES-16 is Not Revertive only
• 1+1 ISA DVB-ASI is Not Revertive only
• 1+1 COMPACT ADM is Not Revertive only

• N+1 63 x 2 Mbit/s (P63E1 or P63E1N) protection is Revertive

• N+1 3x34/45 Mbit/s (P3E3/T3) protection is Revertive
• N+1 4xSTM-1 ELECTRICAL port (P4ES1N) protection is Revertive
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.
12.4 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 board is already forced switched or if the protecting board has a failure
condition.
In order to switch an EPS, perform the following operations:
• Select a transmission board in the Equipment view.
• Select the EPS pull down menu. Then select the Switch.
Figure 138. Switching EPS

3AL 98325 ADAA 155/386
Figure 139. 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, in the current release, only the Lockout options, by
clicking on the relevant radio button.
The Manual to command perform the "manual" switch, active only if the other board is not alarmed.
Clicking on the OK push button will initiate the switch and close the dialogue box. The Cancel push button
cancels the operation and closes the dialogue box.
12.5 EPS Overview

EPS Overview allows displaying as well as search for EPS states.
Selecting the EPS Overview option from the Configuration pull down menu Figure below. Opens:
Figure 140. 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:
3AL 98325 ADAA 156/386
- Board Type: allows filtering for the EPS protected boards; the following filters values should be offered
(examples)
• 1+1 ATM MATRIX 4x4 is Not Revertive only
• 1+1 ATM MATRIX 8x8 is Not Revertive only
• 1+1 PR_EA is Not Revertive only
• 1+1 ES–16 is Not Revertive only
• 1+1 ISA DVB-ASI is Not Revertive only
• 1+1 COMPACT ADM is Not Revertive only
• N+1 63 x 2 Mbit/s (P63E1 or P63E1N–M4) protection is Revertive
• N+1 3x34/45 Mbit/s (P3E3/T3) protection is Revertive

• N+1 4x STM–1 ELECTRICAL port (P4ES1N) protection is Revertive

• N+1 16x STM–1 ELECTRICAL port (P16S1–4E) protection is Revertive
- Status: allows filtering for all possible EPS protection states; the following values should be offered
(examples):
• Ignore
• Normal
• DNR
• Auto-Fail
• Auto-WTR
• Manual
• Lockout
After the filter selection click on Search button to start; the field below the Search button will be updated
(see Figure below.)
Figure 141. EPS overview after Search (Example)
3AL 98325 ADAA 157/386
Each protection unit is presented with the following information:
- Protection Group (example protection Groupld, 15)
- Board Id (example r01sr1/board#15)
- 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 follow
• Normal
• DNR (Do Not Revert)
• Auto-Fail (Auto switch Equipment Fail)
• Auto-WTR (Auto switch Wait Time to Restore)
• Manual (Manual switch)
• Force (Force switch, not supported in current release)
• 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 auto
switch or commands
- Orange (Major): for protected units in standby after a command and protecting protection unit in standby
for auto switch or commands
- Cyan (Indicative) for protecting protection unit active and no fail condition present in the schema (Do Not
Revert State)
At the button of the EPS Overview windows are available five buttons that allows navigating 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
The buttons available are:

- Open Subrack View: opens the Subrack view showing the protection states with icons on the boards
(see Figure below.)
The possible protection states and the relevant symbols are explained in the following:
3AL 98325 ADAA 158/386
Symbol EPS protection status
No Request
Do not Revert
Lockout
Auto Switch (WTR, Fail)

Manual
- Open Board View: opens the board view showing the alarm and the board administrative states
- Open Commands: opens the EPS Switch dialog box, and the relevant description.
- EPS Management: opens the EPS Management dialog box, and the relevant description.
- EPS Parameters: opens the EPS Configuration dialog box, and the relevant description.
Clock on Close button to exit from the EPS Overview window
Figure 142. Subrack view after “Open Subrack View” command
3AL 98325 ADAA 159/386
ED
02
Figure 143.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Board view after “Open Board View” command
160/386
13 Multiplex Section Protection Management
13.1 Architecture types

The Multiplex Section Protection in the connection between two NEs protected by cable and port duplication.
At the source the signal is duplicated and sent to the sink via two independent cables. When occurs a
multiplex section failure, the system switches to the other cable and port.
The MS Linear Trail Protection can be applied to any NE where it is possible to configure a linear APS
(single ended/dual ended) line protection. For this NE is applicable the APS 1+1 Proprietary, m the APS 1+1
Standard and the APS 1:1 Standard dual ended.
The APS 1+1 (not revertive) 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 (unidirectional)
and in dual (bidirectional) ended mode.
In single ended mode (unidirectional) the protection is accomplished by switching only the signal affected
by the failure.
In dual ended mode (bidirectional) the protection is accomplished by switching both the affected and the
unaffected signals.
Architecture 1+1 or N+1 Standard
Described in ITU-T Rec. G783/G841. The reference 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 (not used)
The reference 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 (not used)
Architecture 1 : 1 Standard (not used)
Described in ITU-T Rec. G.783/G841 as architecture 1 : n (with n=1). The reference 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 WTR time is used with revertive mode.
Signal Degrade (SD) software setting enables the MSP protection mechanisms when a SD is recognized on
the working port. The SD threshold reference values depend on the NE selected threshold on the MS
termination point.
13.2 MSP Options Introduction

All the MSP options are available starting from the Port View following the step explained below:
- Select Equipment from the Views menu
- Double click on the SDH optical board to configure to open the port icon
- Double click on the port icon to open the port view
- Select the MSP block in the port view and then choose the MSP options by clicking on Port -> MSP
menu; the possible choice are:
• MSP Create
3AL 98325 ADAA 161/386
• MSP Management
• MSP Commands
• MSP Delete
MSP Create, MSP Management, MSP Commands and MSP Delete can also be accessed from the
Transmission-> MSP menu
13.3 MSP Create

Select the MSP Create option from the Port -> MSP menu (see Figure below.) to open the MSP Schema
Creation.
Figure 144. MSP Create Option
Figure 145. MSP Schema Creation
3AL 98325 ADAA 162/386
In this release two MSP Protection Schemas are supported:
- 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 below. 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)
Figure 146. MSP schema creation Port dialog

Select the Choose Port button to define the "Protected Port" and "Protecting Port" units.
Figure below is opened.
3AL 98325 ADAA 163/386
Figure 147. TP Search

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".
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 below. 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, No revertive
• N+1 Standard can be only dual-ended Revertive.
At the end click on the OK button to confirm the MSP protection schema configuration. An error message will
be appear if the NE does not support the selected schema
3AL 98325 ADAA 164/386
Figure 148. MSP 1+1 standard protection schema (example)
13.4 MSP Management

Select the MSP Management option from the Port -> MSP menu (see Figure below) to open the MSP
Schema Configuration.
Figure 149. MSP Management Option

The MSP Schema Configuration dialog shows the current state of the MSP schema, setting and state
(protected or protecting) of the current SDH-n port.
This dialog allows setting the configuration parameters for the designated multiplex section:
- Protection Schema reported in the previous paragraph Architecture Types
- Schema Parameters:
• Dual Ended / Single Ended protection switch and directionality.
• Revertive/Non Revertive mode
• The WTR Time (Wait to Restore) is the delay time for switching protection and protecting port after
recovery from failure / defect.
• Enable Switch on SD is not operative in current release.
- Ports area display the current MSP schema:
3AL 98325 ADAA 165/386
• Port Id: identify the location of the board
• Role: identify the role of the board ("Protecting" or "Protected")
• Channel Id: mandatory for MSP N:1 (max. value is 14)
• Priority: type of traffic, High or Low
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 in not supported by the NE.
Figure 150. MSP Management View
13.4.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 (unidirectional) schema into a dual ended (bidirectional), 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.
3AL 98325 ADAA 166/386
13.5 MSP Delete
Select the MSP Delete option from the Port->MSP menu (see Figure below.) to open the "MSP Schema
Deletion".
Figure 151. MSP Delete option
Figure 152. MSP Schema Deletion

Click on "OK" button to delete the selected MSP Schema Configuration
3AL 98325 ADAA 167/386
13.6 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 below.
The following states are always displayed:
Port Status - 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.
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 has 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
Complete: = the bridge/switch actions are completed
Pending: = the bridge/switch actions are pending
The "complete" and "pending" indications precede the following statuses:
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
- Failure (in case of FOP)
3AL 98325 ADAA 168/386
Figure 153. MSP Protection Status Examples

Figure up. Represent a MSP configuration with a normal condition, with an automatic protection switching
and with a forced command. In any situation are represent 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.
3AL 98325 ADAA 169/386
13.7 MSP Commands
Select the MSP Commands option from the Port -> MSP menu (see Figure below) to open the "MSP
Command window".
Figure 154. MSP Commands option

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 by issuing a
"Lockout" of protection request (on the "Protection Status" of MSP Management). It is possible to "Lockout
the Protecting Port" or "Lockout the Protected Port"; to remove the lockout commands select Release Ping
(for the protecting) and Release Ped (for the protected).
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 exits 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 "Forced to" Protected port command.
For 1+1 non-revertive system, forced switch no working channel transfer the working channel back from
protection 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.
The Manual to command switches the working channel (Protection port) to the protection section (Protection
port), unless a failure condition exits 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). Is also possible to switch back to the working channel using again the "Manual to" Protected
port command.
For 1+1 non-revertive system, manual switch no working channel transfers the working channel back from
protection 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 command cancels the delay time for switching protection and protecting port after recovery
from failure/defect.
The Exercise command issues an exercise request for protection channel and checks response on MSP
bytes, unless the protection channel 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.
3AL 98325 ADAA 170/386
Not operative in current release.
The Release command clears all previously switching commands.\
Figure 155. MSP Commands

The priority levels for the MSP commands are (from the higher to the lower one)_ Lockout. Force to, Auto-
switch (SF&SD), Manual to.
Table 1. 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 (i.e.: if an "Auto-switch" and a "Manual to" command are
present, "Auto-switch" is operative.
Table 2. MSP commands and Auto-switch protection priority
Forced to Auto--switch Manual to

Lockout of
Protection
Lockout Lockout Lockout

Lockout of ______________
Protection
Forced to Lockout Forced Forced
______________
Auto--switch Lockout Forced Auto--switch

______________
Manual to Lockout Forced Auto--switch

______________
3AL 98325 ADAA 171/386
13.8 MSP overview
MSP Overview allows displaying as well as search for MSP states.
Selecting the MSP Overview option from the Configuration pull down menu Figure below opens.
Figure 156. MSP overview

To Search the MSP groups two different ways of filtering are supported; a filtering foe 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 filtering for the MSP protected boards; the following filters values should be offered
(example):
• Ignore
• P4ES1N
• P4S1N
• P4E4N
• P4S4N
• P8S1-4E
• S-41N
• L-41N
• L-42N
3AL 98325 ADAA 172/386
• S-161
• S-161N
• S-161ND
• L-161
• L-161N
• L-161ND
• L-162
• L-162N
• L-162ND
• SYNTH16
• SYNTH16N
- Status: allows to filter for all possible EPS protection states; the following filters values should be offered
(example):
• Ignore
• NR (Normal)
• DNR
• Auto-SF
• Auto-SD
• Auto-WTR
• Manual
• Force
• Lockout
• APS Invalid (Fail)
• Bad channel (Fail)
After the filter selection click on Search button to start; the field below the Search button will be update (see
Figure below.)
3AL 98325 ADAA 173/386
Figure 157. MSP overview after Search (Example)

Each protection unit is presented with the following information:
- Protection Group (example protection Groupld, 160)
- Port Id (example r01sr1sl9/port#01-OpS)
- 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)
• DNR (Do Not Revert)
• Auto-SF (AutoSwitch Signal Degrade)
• Auto-SD (AutoSwitch Signal Degrade)
• Auto-WTR (AutoSwitch Wait Time To Restore)
3AL 98325 ADAA 174/386
• 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 on 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 buttons 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
The buttons available are:
- Open Port view: opens the port view showing the correlation between the alarm and the MSP protection
states. (See Figure below)
- MSP Create: opens the MSP Create dialog box.
- MSP Delete: opens the MSP Delete dialog box
- MSP Management: opens the MSP Management dialog box
- MSP Commands: opens the MSP Commands dialog box
Click on Close button to exit from the MSP Overview window
3AL 98325 ADAA 175/386
ED
02
Figure 158.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Port view after “Open Port View” commands
176/386
14 TRANSMISSION VIEW
14.1 Overview
This section describes the operations necessary for the consultation, modification and configuration of TPs,
providing a representation of the entire signal flow.
The generic Transmission View, described in this chapter, 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 synthesis icon indicates the alarm state
- A cross indicates the cross-connection state
- A circle indicates whether a TP can be structured
- Whether a TP is under Performance Monitoring indicated by a blue "P" letter
- Whether a TP is involved in a loop action, an arrow indicates it
• 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 functionality to create/show Multiplex Section Protection (Not operative in the current
release)
• Provide the functionality to create/show Loopback commands.
• Provide the possibility of configuring a selected TP. Calling the configuration dialogs of the common
Transmission/Port Views category accesses this functionality.
• Provide the possibility of showing a detailed view of a TP with alarms, navigating to the Port view.
• Provide the possibility of showing and setting Performance Monitoring parameters and data.
3AL 98325 ADAA 177/386
14.2 View elements
The Transmission View uses the symbols illustrated in Figure below.
Figure 159. Symbols Used in Transmission View
14.3 View Layout

The Transmission View is a main view. It provides views of specific areas, which display the transmission
resources, and the specific Transmission View pull down menu, which provides the Transmission View
operations.
14.3.1 View Description

Figure below. 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 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.
When the "Transmission view" is reached selecting the Transmission option in the View pull down menu in
its initial state contains no objects.
3AL 98325 ADAA 178/386
Figure 160. Transmission View Area
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:
• The root node contains the full user label,
• All child nodes contain a short label indicating the position inside the tree.
3AL 98325 ADAA 179/386
14.3.4 Dynamic View Behaviour
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
The alarm synthesis icons of the TP objects indicate alarms concerning the TPs displayed graphically. The
TP objects are updated accordingly.
Object deletion
The TP objects indicate all kinds of object deletion events related to TPs displayed. The graphical objects
are removed accordingly from the Transmission View. Example: modification of the payload structure from
63 TU-12 to 3 TU-3.
14.4 Transmission view access and menu

The "Transmission view" can be reached selecting the Transmission option in the View pull down menu. In
this case, in its initial state, the Transmission View contains no objects.
In the case of navigation from another view (example the "Port view") to the Transmission View, the
Transmission View is always initialized and the corresponding objects are then displayed in it.
Selecting the "Transmission" option in the menu bar the complete pull down Transmission menu is
presented
The following menu items are available:
• Add TP Select the TP to show on the Transmission view.
• Expand Display TPs that are related to the selected TP.
• Hide Hide TPs that are related to the selected TP or the selected TP.
• TP Configuration Set parameters for the Overhead on Synchronous TP's.
• TP Frame Mode Configuration Set parameters for 2Mbit/s G.703/G.704 or ISDN-PRA
management
• TP Threshold Configuration Set B2 ExBER and Degraded Signal parameters.
• Terminate TP Terminate a path on a AU-4 CTP
• Disterminate TP Disterminate a path on a AU-4 CTP
• AU4 Concatenation
• Cross-Connection Manage the connection of the paths.
3AL 98325 ADAA 180/386
• Monitoring Operations Create, configure and delete POM/SUT and TC TP's.
• Performance Set and show Performance Monitoring parameters and data.
• Structure TPs Provides the possibility of structuring and destructuring selected
TP
• Loopback Manage the loopback commands, for commissioning or
maintenance purposes
• Physical Media Manage the physical TP setting.
• MSP Manage the Multiplex Section Protection of the NE. Not available
for PDH port. See MSP Management. In this paragraph is not described the MSP>NE MSP
synthesis option of the Transmission menu, not used in this NE.
• Show Supported Board Navigate to the upper board level.

•
Navigate to Port View Permit to show the detailed alarm of the TP.
These options are described in next paragraphs except the previously referenced.
Figure 161. Transmission menu options
14.5 Add TP
Select the Transmission -> Add TP option.
14.5.1 TP Search
This menu item opens the TP Search dialog. 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).
3AL 98325 ADAA 181/386
Default Mode
In this mode, the dialog displays the structure of the 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
itemsdisplayed small, they are displayed in a hierarchical order. Double-click again to recall the next level.
Figure 162. TP Search Dialog, Initial State

After double-clicking on an object, an Information window appears (see). The message text corresponds to
the object selected.
Figure 163. Information Window
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
3AL 98325 ADAA 182/386
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 164. TP Search Dialog with Various TP Selections
After clicking on Show CC State, a more detailed TP list is displayed containing TP cross connection status
information.
3AL 98325 ADAA 183/386
Figure 165. TP Search Dialog with Status Information Displayed

The symbols in the TP list have the following significance:
Figure 166. Symbols in TP Search

The background color of the symbols represents the status of the TP:
• Grey = inactive
• Green = active
An easy way to recall to previously displayed boards is to use Board History. Select the relevant board from
the list.
Figure 167. Board History Check List
3AL 98325 ADAA 184/386
Search Mode
Use Search Mode together with the filtering options provided below the TP list. The following options are
available:
• Class:
Ignore, E1S, OpS, PPI, AU-4, VC-4, AU-4+VC-4, TU-3, TU-3+VC-3, TU2, TU-12, VC-12,
TU-12+VC12, AUX, MS, RS, OGP, GMAU.
• Connection State (Current connectivity status):
Ignore, not connected, connected
• Alarm State (Path Trace):
Ignore, critical, major, minor, warning, not alarmed

• Assign State:
Ignore, NML, EML
• Perf. Monitoring (Performance Monitoring condition):
Ignore, enabled
• TTI expect: not used
• TTI receive: not used
• TTI transmit: not used
• Location:
Permits to insert the location of the TP in the following format:
r<rack#>sr<subrack#>sl<slot#><port#>
• Name: not supported
3AL 98325 ADAA 185/386
Figure 168. TP Search Dialog with Different Filtering Options

After activating the search process with the Search TP button, the following dialog box appears. Clicking on
Cancel can interrupt the search.
Figure 169. “Information...” Dialog for Search Process

N.B. When searching for PM-enabled TPs on NE, 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).
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.
3AL 98325 ADAA 186/386
Print
This command is used to generate and print a list of TPs according to the current filter selection.
The command opens the following dialog:
Figure 170. Print to Printer

Select the desired printer from the list box and click on Ok to start the print job or abort with Cancel.
The dialog changes after clicking on File:
Figure 171. Print to File

Enter the name of the output file in the input field or select a file name from the File Select dialog by clicking
on Select file. Select if the output format should be Postscript or ASCII.
The output file is generated after clicking on Ok. Use Cancel to stop the process.
Figure 172. Example Printout
3AL 98325 ADAA 187/386
Help
This command opens the online help for the TP-Search dialog.
14.6 TP Configuration
Select the Transmission -> TP Configuration option.
TP Configuration can also be accessed from the "Port" view menu.
14.6.1 High Order TP Configuration

Depending on the TP selected, a dialog appears for the configuration of the main parameters of the objects.
Example:
• VC-4 TTP (140 Mbit/s PDH)

• VC-3 TTP (34 and 45 Mbit/s PDH)

• Mod VC-4 TTP (matrix resource)
The main parameters are:
• C2 Signal Label: "Automatic" (decided by the NE) or "Equipped not specific".
• J1 Path Trace.
The dialogs of the following figure appears:
Figure 173. High Order TP Configuration
14.6.1.1 J1 Path Trace

Operative only on VC-4 in current release.
If the Path Trace is 16 bytes long, the first byte is a CRC7 checksum calculated by NE.
3AL 98325 ADAA 188/386
If the Path Trace is shorter than 16 bytes, it is filled with zero bytes ("0" hexadecimal).
Received fields are 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.
To replace modified with the default, enter the default manually according to the following table .
Table 3. Default value for C2/V5 Signal Label

TP VC-4 TTP / AU4 CTP VC-4 TTP VC3-TTP VC-12 TTP

(SDH) (PDH)
Significant Byte C2 C2 C2 V5
Default value 2 18 4 2
Click on Hex button will be opened displaying in hexadecimal code the same value reported in Transmitted
and received field.
Figure 174. J1 hexadecimal editor (example)
14.6.1.2 C2 Signal Label

Received, Expected and Transmitted fields are read only.
They can display the following number, according the G.707 recommendations for the C2 Signal Label:
• 0: Unequipped
• 1: Equipped non-specific
3AL 98325 ADAA 189/386
• 2: TUG structure
• 3: Locked TU-n
• 4: Asynchronous 34/45Mbyte
• 18: Asynchronous 140Mbyte
• 19: ATM
• 20: MAN, DQDB
• 21: FDDI.
In the Transmitted field it is possible to select the values:
• Automatic: the NE according the VC structure automatically selects the C2 Signal Label value.
• Equipped not specific (it corresponds to number 1)

14.6.2 J0 Section Trace management

Select RST block and then select Port -> TP Configuration
The fields of the following figure appears:
Figure 175. J0 Configuration

This function is implemented in order to manage the J0 Trace configuration.
This dialog shows the current values for received, expected and transmitted trail trace and it allows the
operator to change only the values of expected and transmitted trail trace.
The received trail trace is read-only.
Expected and Transmitted fields are editable by the operator.
With the relevant button it is possible to enable or disable TTI Monitoring.
and received field.
14.6.3 Low Order TP Configuration

Depending on the TP selected, a dialog to configure the main parameters of the following objects:
• VC-12 TTP.
The main parameters are:
• V5 Signal Label. "Automatic" (decided by the NE) or "Equipped not specific".
3AL 98325 ADAA 190/386
• J2 Path Trace. Not operative in current release.
The following dialogs appears:
Figure 176. Low Order TP Configuration

and received field.
Figure 177. J2 hexadecimal editor
3AL 98325 ADAA 191/386
14.6.3.1 J2 Path Trace
Not operative in current release.
If the Path Trace is 16 bytes long, the first byte is a CRC7 checksum calculated by the NE.
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.
Mode1 enable the 16 bytes long sequence for Path trace
One repeated byte allows setting one byte that will be repeated
Received fields are read only.
With the relevant button it is possible to enable or Disable TTI Monitoring.

Empty TTI send an all zeroes path trace.
14.6.3.2 V5 Signal Label

Received, Expected and Transmitted fields are read only.
They can display the following number, according the G.707 recommendations for the V5 Signal Label:
• 0: Unequipped
• 1: Equipped non-specific
• 2: Asynchronous
• 3: Bit Synchronous
• 4: Byte Synchronous
In the Transmitted field it is possible to select the values:
• Automatic: the NE according the VC structure automatically selects the C2 Signal Label value.
• Equipped not specific (it corresponds to number 1)
To replace modified with the default, enter the default manually according to the value reported in Table 2.
3AL 98325 ADAA 192/386
14.7 TP Frame Mode Configuration
This command is available for:
- P12
Select the Transmission -> TP Frame Mode Configuration option
TP Frame Mode Configuration can also be accessed from the "Port" and "Synchronization" view menu.
This menu item enables the configuration of the most important transmission parameters concerning the
Primary Rate Access and G.703/G.704 frame management.
The following dialog appears:
Figure 178. 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:
• "Not Framed" (G.703 interface): the PRA function cannot be activate;
• "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 a 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": red-only field that indicates if status of CRC-4 error counting functionality of far-
end NE is enabled or disabled
3AL 98325 ADAA 193/386
- "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
14.8 TP Threshold Configuration

This menu allows the operator to set the alarm thresholds for MST and VCi layer.
Select the MST or the VCi block
Select the Transmission -> TP Threshold Configuration option.
Figure below. Will be opened.

The user can select one of the two different Defect distributions:
- Poisson distribution enable configuration of the Excessive Bit Error Ratio (ExBER on MST, VCi)
threshold and of the Signal Degrade (SD on MST, VC) threshold of the TP's related counted primitives.
- Burst distribution enable configuration of the maximum number of error frames and the total a amount
of bad block per frame.
- ExBER - Threshold: 10-3 to 10-5
-
Enable Consequent Actions: fixed to enables
- Signal Degrade - Threshold: 10-5 to 10-9
- Burst Parameters - Threshold: 1 or 10 or 100 or 1000
- Burst Parameters - Consecutive Bad Seconds: 2 to 10
Figure 179. Degraded Signal Threshold selection

Click on OK to confirm the chosen parameters.
3AL 98325 ADAA 194/386
14.9 Terminate/Disterminate TP
Select the Transmission -> Terminate TP or Disterminate TP option.
Only one command in the menu is available, depending on whether a TP is terminated or not.
14.9.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 if the modifiable VC-4 TTP was not already structured.
A cross appears in the icon of the terminated TP:
If the TP is already cross-connected a error message appears.
14.9.2 Disterminate TP
Use this action to disterminate a path. It can be performed on a AU-4 CTP. The related cross-connection is
deleted.
NOTE: the “Disterminate” action is not possible in the case that is still existing any
operation/connection/termination on the underlying signals, such as:
• Performance Monitoring on lower or higher TPs
• POM / HPOM operations
• Lower order Connections
• Higher order Connections
• Lower/Higher order Path Terminations
• Loop–backs on lower TPs
Thus the deletion of every operation/connection/termination is necessary, in the same order as above listed,
before disterminating a TP.
A box message will be presented, in order to confirm the TP distermination.
3AL 98325 ADAA 195/386
14.10 Monitoring Operations
Select the Transmission -> Monitoring Operations option as for the following figure.
Creation/Deletion and Configuration options are present.
Figure 180. Monitoring Operations

Monitoring Operations can also be accessed from the "Port" view menu.
The commands of this menu item are for the management of the POM/SUT /TC (Path Overhead
Monitoring, Supervised Unequipped Termination and Tandem Connection).
This command is available for:
• AU-4 CTP
• TU-3 CTP
• TU-12 CTP
14.10.1 Creation/Deletion
The dialog allows multiple object creation/deletion.
The dialog shown in the following Figure below opens
3AL 98325 ADAA 196/386
Figure 181. Monitoring Operations Creation/Deletion

The Path Overhead Monitoring has the following parameters:
• Before Matrix (available only on AU-4 CTP)
• After Matrix
The Supervisory Unequipped Termination, not operative in current release, has the following parameters:
• Sink (before matrix)
• Sink (after matrix)
• Source
• Bidirectional
The Tandem Connection has the following configurable parameters:
• Tandem Connections Monitoring (TCM):
- TCM Before Matrix
- TCM After Matrix
• Tandem Connection Termination (TCT):
- TCT Bidirectional Before Matrix

- TCT Bidirectional After Matrix
Press Ok to apply the parameters or Close to close the dialog and discard the not with Ok applied changes.
When select and apply the Path Overhead Monitoring, the changes will be displayed in the Port View in the
following manner:
3AL 98325 ADAA 197/386
Figure 182. Display of POM and TCM in Port View (example)
When select and apply the Tandem Connection Monitoring / Tandem Connection Termination, the changes
will be displayed in the Port View in the following manner:
Figure 183. Display of POM and TCM/TCT in Port View (example)
14.10.2 Configuration
Depending on the parameters selected in the Monitoring Operations Creation/Deletion dialog, not all
sections of the dialog are available.
N.B. It is possible to open the POM and TCT/TCM Configuration dialog for a CTP even if neither Path
Overhead Monitor nor Tandem Connection was created before (SUT isn't available in this release). No
changes can be made in this case and the values displayed can be ignored.
Figure 184. Monitor Configuration
3AL 98325 ADAA 198/386
TTI Definition
The TTI (Trail Trace Identifier) has a maximum length of 16 characters.
The following TTI Definitions are available:
• TTI Expected
• TTI Received without the display
• TTI Sent
The following TTI Types are available:
• TTI Enabled
• TTI Disabled
• TTI Repeated Byte

Error Distribution
Poisson and Burst error distribution are supported
TCM/TCT Cons Actions
It is needed to support explicit consequent action activation (AIS insertion) for TCT sink and bidirectional.
Thresholds
Set the thresholds of the following parameters:
• Signal Degrade
Poisson mode only: from 10-5 to 10-9.
• Excessive Error
Poisson mode only: from 10-3 also if presented a selection from 10-3 to 10-5
• Burst Degrade
Select a value between 1 and 1000 errors/sec for the Burst Degrade threshold.
• Burst Consecutive
Select a value between 2 and 10 sec for the Burst Degrade Consecutive.
Alarm Timing
Rising and Clearing Timing are not supported by OMSN.
Unequipped Trail
Not available
3AL 98325 ADAA 199/386
14.11 Structure TPs
Select the Transmission -> Structure TPs option.
Figure 185. Structure TPs option

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 is selected and the menu item TU-12
is chosen, the signal is structured down to 63 TU-12 CTPs. The following menu items represent all those
possible:
• TU-2. Not supported.
• TU-3.
• TU-12.
• VC-3/VC-4. Not supported.
• VC-12. Not supported.
The following items are available for synchronous TPs:
• Modifiable VC-4 TTP: TU-3, TU-12
• TUG-3: TU-3, TU-12
• TUG-2: TU-12.
14.12 Loopback
The commands of this menu item are for the management of the loopback commands, for commissioning or
maintenance purposes.
14.12.1 Loopback Configuration

The loopback can be applied at line (external to equipment) level or at internal equipment level. The
loopback commands are used to separate the communication network into independent part checking the
line/equipment functionality during the network installation or maintenance operation.
3AL 98325 ADAA 200/386
The loopback architecture provides four configurations.
Line Loopback And Continue
Line Loopback And AIS
Internal Loopback And Continue
Internal Loopback and AIS
Figure 186. Loopback configurations

Select a TP that supports the Loopback Configuration
Loopback act on the following TPs:
• PDH board (only from the Port View):
- Line loopback performed on:
⎯ P for 2/34/45/140 Mbit/s PPI
- Internal loopback performed on:
⎯ P12 for 2Mbit/s CTP
⎯ P31 for 34/45Mbit/s CTP
⎯ P4 for 140Mbit/s CTP

• SDH board:
The loopback configuration can be done only on SDH ports with the acronym ending with a
"N" letter (i.e. P4S1N, S-4.1N, L-4.1N, L-4.2N, etc.)
- Line loopback performed on:
⎯ EIS for electrical STM-1 SPI
⎯ OpS for optical STM-1, STM-4, STM-16 SPI
- Internal loopback performed on:
⎯ MsT TTP for STM-1, STM-4, STM-16 ports
3AL 98325 ADAA 201/386
Select the Transmission -> Loopback -> Port Loopback Configuration option.
Port Loopback Configuration can also be accessed from the "Port" view menu.
Figure 187. Port Loopback Configuration
Figure below. Opens.
Figure 188. Port Loopbacks View
Choose the TP clicking on the "Choose TP" button. Select the TP where to apply the loopback command.
For this NE the "Timed Loopbacks" field is not managed and thus Start/Stop loopbacks time is not editable.
3AL 98325 ADAA 202/386
14.12.2 Loopback Management
To manage the loopback configuration select the Transmission -> Loopback -> Loopback Management
option.
Figure 189. Loopback Management view

Loopback Management can also be accessed from the "Port" view menu and from the "Configuration
menu”
Figure below. Opens.
Figure 190. Loopback Management
3AL 98325 ADAA 203/386
The configured loopback are listed into the current loopback table. This table can be managed by the
"Search" criteria, "Delete" and "Create" commands.
• Search Criteria (operative): 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: EIS (SPI/PPI Electrical), OpS (SPI/PPI
Optical), MST and so on. 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 "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.
• The "Create" command permits to create a new loopback configuration: clicking on "Create" the
previous figure opens. Follow the previously paragraph indications to create a new loopback
configuration.
The activated loopbacks are signaled in the Port view and in the Transmission view as for the following
figures:
Figure 191. Loopback Port View
Figure 192. Loopback Transmission View
3AL 98325 ADAA 204/386
14.13 Physical Media
Select the Transmission -> Physical Media option.
Figure 193. Physical Media options

The Physical Media options permit to set physical configuration of each TP.
It opens a menu in which the various options will be available according the TP's type (for the option
common with the "Port view" reference is made to the relevant paragraph):
- ALS Management.
- Show Optical Configuration.
- TX Quality Configuration.
- Single Fiber Configuration.
- Extra traffic Not operative
- Regeneration Section management Not operative
- Line Length Configuration.
- Set Domain.
- HDSL Configuration Not operative
- NT Configuration Not operative
- X21 Configuration Not operative
3AL 98325 ADAA 205/386
14.13.1 Set Domain
This option is referred to the Security management and allows the user to set the Manager list and the
Access Control Domain of the selected TP.
Select the block: EIS for Electrical SDH port, OpS for Optical SDH port, P (PPI) for PDH port.
Select the Set Domain option from the Physical Media cascade menu to present the following view:
• NML Assignment: each connected manager to the TP is highlighted in the list. The user can set a
manager clicking on the denomination.
Several managers can be enabled contemporaneously, having in charge the TP.
The Manager List contains the list of managers ( i.e. RM, SY, NPOS , EML) that work on the NE.
The EML-USM administrator (SH or Craft Terminal) should set the Manager List only to remove a
manager in case of emergency (i.e. the Manager misses the NE connection).
• Resource domain field allow selecting the domain among that displayed in the list, assigning it to
the TP.
The different domains could be assigned to different operators.
Figure 194. Set Domain
3AL 98325 ADAA 206/386
14.14 Navigation Commands
14.14.1 Expand
Select the Transmission -> Expand option.
Figure 195. Expand option

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.
14.14.2 Hide
Select the Transmission -> Hide option.
Figure 196. Hide option
3AL 98325 ADAA 207/386
This menu item provides the possibility of hiding all upper/lower TPs of a selected TP and the deletion of a
selected TP.
• Lower TPs,
• Upper TPs,
• Selected TPs.
14.14.3 Show Supported Board

Select the Transmission -> Show Supported Board option.
This menu provides the possibility of navigating directly to the board that supports the TP.
The Board View appears.
Figure 197. Board View
14.14.4 Navigate to Port View

Select the Transmission -> Navigate to Port View option.
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.
The Port View appears.
3AL 98325 ADAA 208/386
ED
02
SC.3: NE MANAGEMENT
Figure 198.
Port View
3AL 98325 ADAA

209/386
14.14.5 Navigate to HOA Port
After selected a structured VC or TU, then click on Transmission –> Navigate to Port View option.
The HOA port displays the internal structure of the payload, as for the following figure:
Figure 199. Navigate to HOA Port
3AL 98325 ADAA 210/386
15 Cross-Connection Management
15.1 Introduction
15.1.1 Overview
The purpose of this domain is to manage the connection of the high and low level path.
The following chapters provide the user with information concerning operations on cross-connections:
• "Multiplex Structures for SDH" gives an overview on the SDH technology
• "Definition of Termination Points" gives an overview about the termination points implemented on the
NE
• "Cross-Connection Types" provides information concerning cross-connection types supported by the

NE
• "Cross-Connection Protection" provides information concerning cross-connection protection
supported by the NE
• "Operative sequence to execute Cross-Connections" details the complete procedure to realize
cross-connection
• "Cross-Connections Management" details the contents of the main cross-connections view
• "Create/Modify Cross-Connections" describes the creation and modification of cross-connections
• "Activate/Deactivate/Delete Cross-Connections" describes the activation, deactivation and deletion
of cross-connections. Activation and deactivation not supported in current release.
• "Split and Join Cross-Connections" describes how to split or join bidirectional cross-connections. Not
supported in current release.
• "Protection Switching" deals with switching actions (force, manual, lockout protection) on cross-
connections
• "Print" deals with printing out list entries on printers or into files
• "Port Switch Over" not operative.
• "Show Cross-Connected TPs" describes the possibility of showing connections between two or more
TPs of different hierarchies, e.g. connection between AU4 and VC4.
15.1.2 Multiplex Structures for SDH

By introducing the Synchronous Digital Hierarchy (SDH), a standardized transmission has been created,
matching the European with the American standard. 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.
Synchronous multiplexers into Virtual Containers (VC) pack signals of the Synchronous and Plesiochronous
Digital Hierarchy (PDH). The STM-1 signal structure is achieved by using the multiplex structure complying
with ITU-T and ETSI. 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. Fix 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
3AL 98325 ADAA 211/386
TUs form a Tributary Unit Group (TUG) and TUGs again can be combined into a VC. The AU of the signal,
together with the Section Overhead (SOH), finally makes up the STM-1 frame.
Figure 200. SDH Multiplex Structure according to ITU-T G.709

The STM-1 frame consists of:
• A Section Overhead (SOH)
• An AU Pointer area
• A payload area
3AL 98325 ADAA 212/386
Figure 201. 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.
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.
3AL 98325 ADAA 213/386
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 as well as on 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 a distinction is made between the following CTPs:
⎯ AU4 (au4 Connection Termination Point)
The AU-4CTP represents both the creation and termination of an STM-1 connection. The High-order
Connection Supervision (HCS) function is included.
⎯ TU-x (Connection Termination Point), e.g. TU-12CTP, TU-2CTP, TU-3CTP
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 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 E32-CTP represents represent the non-intrusive monitoring of incoming 45 Mbit/s PPI

The E31-CTP represents represent the non-intrusive monitoring of incoming 34 Mbit/s PPI
3AL 98325 ADAA 214/386
The E1-CTP represents the non-intrusive monitoring of outgoing 2 Mbit/s PPI. The Mon.
(monitoring) label indicates that is possible to enable the CRC4 control signal.
The S1-CTP represents the non-intrusive monitoring of outgoing 2 Mbit/s PPI. The Mon.
(Monitoring) label indicates that is possible to enable the CRC4 control signal.
• TTPs on SDH level
On SDH level 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 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 45
Mbit/s, a 34 Mbit/s or a 2 Mbit/s port.
⎯ P (PPI Trail Termination Point)
On the PDH side, a 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)
3AL 98325 ADAA 215/386
The E4-TTP represents the creation and/or termination of a 140 Mbit/s connection.

• 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.
3AL 98325 ADAA 216/386
ED
02
Figure 202.
SC.3: NE MANAGEMENT
SDH Transport Level Diagram
3AL 98325 ADAA

217/386
Figure 203. PDH Transport Level Diagram
15.1.4 Mapping Tables: TP Names

The TP names on the 1662SMC 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 4. PDH TPs
ITU-T TP names on 1662SMC

P
PPITTP
E4 CTP eCTP
S4 CTP p4
E31 CTP eCTP
S31 CTP p31
E32 CTP eCTP
S32 CTP p32
E1 CTP eCTP
S1 CTP p12Mon
E4 TTP not supported
not supported
E3 TTP
3AL 98325 ADAA 218/386
not supported
E2 TTP
VC-4 TTP Vc4
VC-3 TTP Vc3
VC-12 TTP Vc12
Table 5. SDH TPs

ESTTP ElS
OSTTP OpS
RSTTP RST
MSTTP MST
MSP MSP
AU-4 CTP Au4/Au4P
AU-4-4c CTP Au4P-4c
VC-4 TTP Vc4
TUG-3 Tug3
TUG-2 Tug2
TU-3 CTP Tu3
TU-2 CTP Tu2
TU-12 CTP Tu12
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).
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 NE supports unidirectional, bidirectional and broadcast connections unprotected as well as protected.
3AL 98325 ADAA 219/386
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.
Figure 204. Unidirectional Connection

15.1.5.2 Bidirectional Connection

Information is transmitted between input port and output port in both directions (point-to-point).
Figure 205. Bidirectional Connection
15.1.5.3 Broadcast Connection (Multi-leg / Multipoint)

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 broadcast from one input to outputs A, B and C on three legs.
Figure 206. Example of Broadcast Connection with Three Legs

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.
3AL 98325 ADAA 220/386
15.1.6 Cross-Connection Protection
15.1.6.1 Protected Unidirectional Connection

A unidirectional connection is routed from Input A to the Output (primary route). In the 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.
Figure 207. Bidirectional Connection - Input Protected
N.B. By means of this connection are created links with SNCP protection.
15.1.6.2 Protected Bidirectional Connection

A bidirectional connection is routed from Input A to the Output C (primary route). Input A (input protected)
can be protected:
Figure 208. Bidirectional Connection - Input Protected

N.B. By means of this connection are created links with SNCP protection.
15.1.6.3 Protected Broadcast Connection

The protected broadcast is realized as a set of independent, protected, unidirectional connections using the
same pair of input termination points. 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.
Figure 209. Protected Broadcast
3AL 98325 ADAA 221/386
Figure up. 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.
In current release only one out of N legs can be protected.
15.1.6.4 Drop and Continue Connection

A Drop and Continue connection is a composed by:
• A unidirectional connection routed from Input A to the Output C and also to Input protecting 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.
Figure 210. Drop and Continue - Normal
3AL 98325 ADAA 222/386
15.2 Operative Sequence to execute Cross-Connections
This paragraph lists general procedure to realize cross-connection moving among the various menus.
Three main cases have been considered:
• High order signal cross connection (AU4s between SDH ports);
• High order concatenated signal cross connection (AU4–xc between SDH ports)
• Low order signal cross connection (TU12 cross connected with VC–12; ports involved: SDH and
PDH )
• 4XANY TPs cross connection (ports involved: 4XANY and SDH)
• ISA board TPs cross connection (ports involved: ISA, SDH or PDH)
• DVB-ASI TPs cross connection (TU12/TU3 unidirectional cross connection with VC-12XVVC-3XV;
ports involved DVB-ASI and SDH)
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.
• 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.
• 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
concatenated AU4c (syntax example: r01sr1sl08/port#01-#01AU4P-4c)
• Click on "OK"; the "TP search" window is closed.
3AL 98325 ADAA 223/386
• In the "Main Cross Connection" window repeat the same on the "Output" field and on the "Prot.
Input" field for protected connections
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 showed TUG3
• 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 choose 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 used
• 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.
• 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 structured
TP (example: TU12 1.1.1)
• Click on "OK"; the "TP search" window is closed.
• Repeat the same on the "Output" field and on the "Prot. Input" field for protected connections
created.
Procedure 4XANY TPs cross connection
Note: before to create a cross connection the following step must be executed:
• configure the 4xANY board with the Equipment –> Set menu
• configure the 4xANY MODULES with the Equipment –> Set menu and choose the traffic type that
must be supported by the module (e.g. FICON, FDDI etc.); after having selected the traffic type,
3AL 98325 ADAA 224/386
automatically a number of TPs (VC–4) are generated for this port and can be viewed in the port view.
All the TPs must be used when the cross– connection will be created.
For details on 4xANY board refer to the Technical Handbook.
– In the subrack view click twice on the 4xANY board; the” board view” will be opened .
– Click twice on the module to be used; the daughter view will be opened.
– Click twice on the daughter board icon; the port view will be opened with all the relevant TPs.
In the following will be explained how to connect one TpP of the 4XANY; repeat the same sequence for
all the TPs that has been generated when the traffic type has been defined.
– Select the VC–4 TP and then choose the Port –>Cross Connection –> Create Cross Connection
option of the menu bar; a new window called ”Main Cross Connection” is opened.
• Select the correct value in the fields ”Type” and ”Protection”

• The “Input field” is automatically filled in
• Click on ”Choose” relevant to the ”Output” field; a new window called ”Search for Cross Connection
Output” is opened.
• On the ”Equipment” field select the Board to be used for the connection with the 4XANY board (for
example S4.1N), in the ”Termination Points” field select the AU4
– Click on ”OK”; the ”Search for Cross Connection Output” window is closed.
– Click on ”OK” in the ”Main Cross Connection” window to terminate the creation.
– repeat the same procedure for all the VC–4 generated for the specific traffic type associated to the 4xANY
module.
– To check the presence of the new cross–connection select the Port –>Cross Connection –> Cross
Connection Management option of the menu bar; a new window called ”Coss connection Management” will
be opened
• Click on the “Search” button; all the cross connected TP will be displayed in the “Cross Connection
in list” field.
Procedure ISA board TPs cross connection
Note: before to create a cross connection the following step must be executed:
• configure the ISA board with the Equipment –> Set menu
• define the TP that must be created on the ISA board by selecting the Configuration –> ISA Port
Configuration menu (refer to Chapter 20 for details)
– The ISA board TP cross– connection is similar to that described for the 4xANY board.
Procedure for DVB-ASI signal
In the following example a VC-12XV will be unidirectionally cross connected with a TU-12; the boards
P4S1N has been taken like reference board for this example.
Note 1: before to create a cross connection the following step must be executed:
configure the ISA board with the Equipment → Set memu
define the TP that must be created on the DVB-ASI board by selecting the Configuration → ISA
Port Configuration memu
Note 2: the P4S1N STM-1 port payload must be terminated as TU-12
3AL 98325 ADAA 225/386
In order to create the cross connection from DVB-ASI to SDH:
– In the subrack view select Configuration → Cross Connection Management the “Cross Connection
Management” window will be opened.
– Click on the Create button, a new window called “Main Cross Connection” is opened.
• Select the correct value in the fields “Type” (only UNIDIRECTIONAL) and “Protection”
• Click on “Choose” relevant to the “Input” field, a new window called “Search for Cross Connection
Input” is opened.
• On the “Equipment” field select the Equipment Subrack, in the ”TP Search Criteria” field select the
VC12XV, and then click on search.
• In the Termination Point Field select the VC12XV to be connected and subsequently click on OK
button, the “Search for Cross Connection Input” window will be closed.
• Click on “Choose” relevant to the “Output” field and repeat the same sequence as above description
for the input point but instead of TU12 select now the VC12XV to be connected in the Termination
Point Field; click on OK button and the “Search for Cross Connection Output” window will be closed.
– Click on “OK” in the “Main Cross Connection” window to terminate the creation.
– To check the presence of the new cross connection select the Port →Cross Connection →Cross
Connection Management option of the menu bar, a new window called “Cross Connection Management”
will be opened.
• Click on the “Search” button, all the cross connected TP will be displayed in the “Cross Connection
in list” field.
3AL 98325 ADAA 226/386
15.3 Cross-Connections management
A list of cross-connections can be displayed in the Cross-Connection Management dialog. The dialog can
be accessed via the Transmission or Port view or via Configuration menu.
Transmission view is presented with the View " Transmission pull down menu.
Port view is presented with the View " Equipment pull down menu, then clicking on the presented objects
with the sequence board>port.
Figure 211. Cross connection management cascade menu
3AL 98325 ADAA 227/386
The Cross-Connection Management dialog is initially empty.
A list of cross-connections is displayed in the Cross-Connection Management dialog after selecting the
Search command.
There are two possibilities of displaying a list of cross-connections:
• Do not enter any search criteria and press the Search button to display a list of all existing cross-
connections,
• Enter Search Criteria (one or more) and then press the Search button to display a selection of
cross-connections. 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.
15.3.1 Search Criteria

• Name (not supported.)
Number of the cross-connection (automatically assigned)
• ACD (not supported.)
Enter the Access Control Domain of the relevant cross-connections: E= connection made with
1353SH, M= connection made with 1354RM, empty= connection made with CT.
This filter option can only be used, if at least one ACD is defined on the NE and one or more cross-
connections are assigned to this ACD(s).
• Type
Select the connection type:
• Unidirectional
• Bidirectional
• Multipoint
• Drop Continue
• Protection
Select protection functionality:
• Protected
• Not protected
• TP Class
Select one of the TP types involved in the requested cross-connection.
• State
Select the connection state:
• Activated
• Deactivated (not operative in current release, the connection state is always Activated)
• Prot. State
Select the protection state:
• Forced to Input
3AL 98325 ADAA 228/386
• Forced to Protecting
• Manual Switch to Input
• Manual Switch to Protecting
• Auto. Switch to Input
• Auto. Switch to Protecting
• Lockout
• Normal I
• Normal P
•
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:

R<rack#>s<subr.#>b<board#>/port#<port#>-TP.
The # within brackets identifies a number.
Figure 212. Cross-Connection Management Dialog (Initial State)
3AL 98325 ADAA 229/386
15.3.2 Cross-Connection List
After a successful search, a read only list of cross-connections matching the search criteria appears. 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:
• 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 error 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)
There has been an Automatic switch 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.
• State
Connection state indicating whether cross-connection is A (activated) or D (deactivated)
• Dir.
Direction-related connection type:
uni (directional), bi(directional) or 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
<Rack#>-<subr. #>-<Board#>-<port#>, <port#>#TP
• Protecting Input
3AL 98325 ADAA 230/386
Protecting source (for protected cross-connections only); contains the TP type and physical location
of the port according to the format
r<rack#>s<subr.#>b<board#>/port#<port#>-TP.
• Output
Signal destination
for point-to-point cross-connections, the TP ID of the destination is specified according to the format
r<rack#>s<subr.#>b<board#>/port#<port#>-TP ; for multi-leg cross-connections, the string "multiple
Legs" appears instead.
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.
Or, 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.
Figure 213. Cross-Connection Management Dialog (After Search)
3AL 98325 ADAA 231/386
15.3.3 Actions available
The following actions are available:
• Create a cross-connection.
The Main Cross-Connection dialog is opened.
• Modify a Cross-Connection.
Available if just one cross-connection is selected from the list. The Main Cross-Connection dialog
is opened.
• Activate a Cross-Connection.
Available if at least one cross-connection is selected from the list. Not operative.
• Deactivate a Cross-Connection.
Available if at least one cross-connection is selected from the list. Not operative.
• Delete a Cross-Connection.
Available if at least one cross-connection is selected from the list.
• Split a Cross-Connection.
Available if at least one bidirectional cross connection is selected from the list.
• Join Cross-Connections.
Available if two cross connections are selected. Not operative.
• Protection Switching.
Available if exactly one protected cross-connection is selected from the list. The Protection Actions
dialog is opened.
• Print.
Prints the filtered list of cross-connections.
The dialog has to be closed explicitly.
15.4 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 as for the following menus example or by using
the Create or Modify buttons in the Cross-Connection Management dialog.
The dialog box of Figure below is presented ( “Main Cross Connection” view).
3AL 98325 ADAA 232/386
Figure 214. Create Cross-Connections

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.
• 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.
15.4.1 Cross-Connection Parameters

The "Main Cross Connection" permits to create the cross connections.
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).
3AL 98325 ADAA 233/386
To create a cross-connection, one or more of those parameters must be defined according to the cross-
connection type. Table 1. 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
• D&C Topology
Select the direction for Drop Continue:

• Normal
• Inverse
• Protection
Define protection state:
• Protected
• Not Protected
• Prot. Criteria (only available for protected connections)
Clicking on the Prot. Criteria button, for the Protection Criteria dialog is opened, where the user can
display and configure the SNCP Type Protection. No protection criteria for automatic protection
switching can be configured.
The following SNCP Type is 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)
Figure 215. Protection Criteria
3AL 98325 ADAA 234/386
• Revertive (available only for protected connections)
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.
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 fixed to 5 minutes.
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.
• Input
To enter the input TP, click the relevant Choose button and select the TP in the TP Search dialog.
Otherwise, select the input field and enter the name of the TP directly.
• Prot. Input
To enter the protecting TP, click the relevant Choose button and select the TP in the TP Search
dialog. Otherwise, select the input field and enter the name of the TP directly.
• Output
It is possible to enter one or more output TPs.
To enter one output TP, click the relevant Choose button and select the TP in the TP Search dialog.
Otherwise, select the input field and enter the name of the TP directly.
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 6. Optional and Mandatory Configurable Parameters for Cross-Connection Creation
Input Parameters Unidirectional/Bidirectional Cross Broadcast Cross Connection

Connection
Not Protected Protected Not Protected Protected
Type Unidirectional/Bidirectional Unidirectional
D&C Topology Normal/inverse _ _
Protection Not Protected Protected Not Protected Protected
Protection _ SNCP-1 _ SNCP-1
3AL 98325 ADAA 235/386
Criteria SNCP-N SNCP-N
HOT (NOT _ X _ X
operative)
Protected _ _ _ _
Revertive _ X _ _
Input One TP One TP One TP One TP
Protecting Input _ One TP _ One TP
Output One TP One TP One or more TPs One or more TPs
_ not available
x configuration optional
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
3AL 98325 ADAA 236/386
Broadcast with one protected leg
Drop & Continue normal
Drop & Continue inverse

Loopback connection: unidirectional, same input and output TP

Figure 216. Cross-Connection Icons

Example:
Figure 217. Creation of a Unidirectional, Non-Protected Cross-Connection

-- Input TTI
The received Trail Trace Identifier of the far end signal is displayed. Not operative in the current Release.
-- Output TTI
The Trail Trace Identifier of the transmitted (near end) signal is displayed. Not operative in the current
Release.
15.4.2 Create a Cross-Connection

This chapter lists the steps the user has to take to create a cross-connection using The "Main Cross
Connection"
For a detailed description of the single parameters.
For information on cross-connection types.
N.B. After creation 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.
Create a Point-to-Point Cross-Connection (unit- or bidirectional)
1) Select the cross-connection type.
2) Select the protection state.
3) Select or type in the input TP.
To enter the TP, click the Choose button and select the TP in the Search for Cross Connection
Input dialog, or select the input field and enter the name of the TP directly.
The Search for Cross Connection Input 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 left list box,
3AL 98325 ADAA 237/386
then select the filter criteria Connection State "not connected" and Class "AU-4" and click on button Search.
The matching TPs are listed in the right list box. Select the input TPs in the list and confirm with Ok.
For a more detailed description on the Search for Cross Connection.
4) Select or type in the output TP as described in Step 3).
The following steps only apply to protected cross-connections:
5) Select or type in the protection TP as described in Step 3).
6) Configure the Revertive mode
7) Configure the Protection Criteria (Prot.Criteria)
8) The Hot (Hold Off Time) is not operative in current release
Press the button Ok to confirm the creation.

Figure 218. Create a Bidirectional Protected Cross-Connection

Create a Broadcast Connection
1) Select the cross-connection type "unidirectional"
2) Select the protection state.
3) Select or type in the input TP.
To enter the TP, click the Choose button and select the TP in the Search for Cross Connection Input dialog
or select the input field and enter the name of the TP directly.
3AL 98325 ADAA 238/386
This dialog offers the possibility to list TPs according to different filter criteria. E.g. to obtain a list of all TU12
TPs of a board, first select the board in the left list box, then select the filter criteria Connection State "Ignore"
and Class "TU12" and click on button Search TPs. The matching TPs are listed in the right list box. Select
the input TPs in the list and confirm with Ok.
For a more detailed description on the Search for Cross Connection.
4) Select or type in the output TPs as described in Step 3 )
Press the button Add Leg in the Main Cross Connection dialog and all output TPs are displayed in
the list box under the output field.
To delete a leg from the list, select the TP in the list box and click on the Delete Leg button.
The following steps only apply to protected broadcast connections:
5) Select or type in the protection input TP. Note that each single protected leg of the broadcast has to be
assigned to the same protecting input.
Proceed as described in Step 3 ). Afterwards, select the protected output TP in the output list box and
click button Protect Leg. The leg is then marked as "protected" in the list box. Repeat this procedure
for each protected output TP (only one protected leg is supported in current release).
To unprotect a leg from the list, select the protected TP in the list box and click on the Unprotect Leg
button.
6) Configure the criteria for automatic protection switching.
7) Configure the Protection Criteria (Prot.Criteria)
8) The HOT (Hold Off Time) is not operative in current release
Press the button OK to confirm creation.
Figure 219. Search for Cross-Connection Output
3AL 98325 ADAA 239/386
Figure 220. Create an Unprotected Broadcast Cross-Connection
Figure 221. Create a Protected Broadcast Cross-Connection
3AL 98325 ADAA 240/386
15.4.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 protection
state and the parameters required by the protection. Refer to Table 2. 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 Para. 1.1.1.
To modify a cross connection selects one from the connection list and then click on the Modify button.
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.
Table 7. Modifiable Parameters
Input Parameters Modification

Not Protected to Protected Protected to not Protected
Type _ _
D&C Topology Normal/inverse Normal/inverse
Protection Protected Not Protected
Protection Criteria X _
HOT (NOT operative) X _
Unprotected _ X
Protected X _
Revertive X _
Input X X
Protecting Input X _
Output X X
_ Not available
X configuration optional
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).
An example is in the following Figure.
In addition, a question box appears, asking the user to confirm the unprotect action.
3AL 98325 ADAA 241/386
Figure 222. Unprotect a Unidirectional Cross-Connection

• Protect an unprotected cross-connection:
When an unprotected cross-connection is being protected, the Prot. Input button is available to
select the protection input connection to insert.
An example is in the following Figure.
Figure 223. Protect one Leg of a Broadcast Connection
3AL 98325 ADAA 242/386
15.5 Activate/Deactivate/Delete Cross-Connections
15.5.1 Activate a Cross-Connection

Not supported in current release.
The Cross Connection Management dialog provides the possibility of displaying a selection of existing
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) 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.5.2 Deactivate a Cross-Connection

After creation, a cross-connection is automatically in an active state. To deactivate a cross-connection, select
one from the connection list 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 (Act = D).
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.
15.5.3 Delete a Cross-Connection

Only deactivated cross-connections should be deleted. However, deletion of active cross-connections is
possible.
NOTE: the “Delete cross–connection” action is not possible in the case that is still existing any
operation/connection/termination on the underlying supported signals, such as:
• Performance Monitoring on lower or higher TPs
• POM / HPOM operations
• Lower order Connections
• Higher order Connections
• Lower/Higher order Path Terminations
• Loop–backs
• LAN/LAPD (and any comm/routing channel)
• Auxiliary channels
Thus the deletion of every active operation/connection/termination is necessary, in the same order as above
listed, before the deletion of a cross–connection.
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.
3AL 98325 ADAA 243/386
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:
a) 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 below.).
The new cross connection has the same name and activation status as the old bidirectional one.
Figure 224. Split/Join Unprotected Bidirectional Cross-Connection

b) Protected Cross-Connection
Splitting a protected connection results in one protected unidirectional cross-connection and one
broadcast with two legs. The input of the original cross-connection is one of the legs in the broadcast.
The other leg in the broadcast is the protecting input. The input of the broadcast is the output of the
original protected cross-connection.
Figure 225. Split/Join to Protected Bidirectional Cross-Connection
3AL 98325 ADAA 244/386
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.
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 or a protected bidirectional cross-connection.
If the original cross-connections have different names, the new name is a concatenation of the names of
both of them.
3AL 98325 ADAA 245/386
15.7 Protection Switching
The Protection Actions dialog is displayed after clicking on the Protection button in the Cross Connection
Management dialog.
Users can only switch protection on cross-connections belonging to them and not assigned to the NML. A
second condition is that protection is enabled for the cross-connection concerned (protection parameter is
set to "protected").
The three protection actions Force, Lock Out 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 226. Protection Actions Dialog
The dialog window enables the user to perform protection- related operations on protected cross-
connections. These are:
• Force to Input (not operative in current release)
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
Forced switching is disabled and automatic protection switching re-enabled.
• Manual Switch to Input (not operative in current release)
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.
• Manual Switch to Protecting Input (not operative in current release)
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.
• Release Manual Switch (not operative in current release)
A manual switch is disabled and automatic protection switching re-enabled.
3AL 98325 ADAA 246/386
• Lock Out to Invoke
The connection path is locked for protection switching, i.e. neither forced nor manual switching can
be performed.
• Release Lock
The protection lock is disabled.
N.B. All the operations listed are context-dependent and are enabled or disabled ("grey") 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.
15.8 Print
This option is used to print the currently filtered cross-connection list and the related filter settings on the
default printer or to a file in postscript or ASCII format.
Figure 227. Select Printer

Figure 228. Select Output Format
3AL 98325 ADAA 247/386
15.9 Show Cross-Connected TPs
An overview of signal flow can be requested by means of a user action. The user can select a TP and initiate
the action Show Cross Connected TPs from the Transmission view.
Figure 229. Show Cross Connected TPs view

The result is that all other TPs connected to the currently selected TP are displayed. A line indicates the
connection.
This functionality should only be applied selectively (either for a single TP or selected group of TPs).
Expanding and hiding TPs that are associated with the currently selected TP (e.g. show all TPs that are
above the TU12CTP) enables all the related TPs to be added to the view so that the complete signal flow
can be illustrated.
3AL 98325 ADAA 248/386
ED
02
Figure 230.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Show Cross Connected VC4 of an AU4
249/386
16 OVERHEAD MANEGEMENT
16.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.
16.2 OH Connection overview

Here are described the possible OH connections
• OH Cross-connection
The operator has to be able to cross-connect 2 or more OH bytes on 2 different boards.
The possible cross-connection types are:
• Unprotected bidirectional point to point
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 the input OH TP involved in the operation
- Select the output OH TP involved in the operation
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
3AL 98325 ADAA 250/386
For STM ports it make 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 input msPassThroughCTP point involved in the operation
- Select the output msPassThroughCTP point involved in the operation
After having deleted a total MSOH pass-through, the involved msPassThroughCTP points have to be
deleted.
16.3 Overhead views

The Overhead Views allows performing the previously presented operations.
To access select Overhead option from the Configuration pull down menu; the following options are
presented in the cascading menu.
• OH Cross Connection.
• OH Phone Parameters.
• OH TP creation.
• OH TP deleting.
Figure 231. Overhead options

The options are described in next paragraphs.
3AL 98325 ADAA 251/386
16.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 and allows to start the configuration.
Figure 232. 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 dialog and the TP Search dialog,
also in this case already described for path management.
3AL 98325 ADAA 252/386
Figure 233. Main Cross-Connection for Overhead dialog

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.
Cross-Connection Management for Overhead dialog
• Supported operations
Search cross connections/terminations according to one or more of the following filtering
attributes: type, TPs . The operator can set the filtering criteria, can start the search and select
one or more cross connections/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 cross connections/terminations, this dialog allows to:
• Delete the selected xconnection/termination
• Go to the "Main Cross Connection for Overhead" dialog and modify the existing cross
connection/termination
3AL 98325 ADAA 253/386
Note: this dialog disappears only when the user explicitly clicks on the close button.
Delete operations can be performed on several cross connections/termination at the same time.
Modify operations can be performed only on single cross connections/terminations.
The OH xconnections 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 cross
connection dialog.
• The create button is always enabled. It brings up the Main cross connection 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
16.4.1.1 Main Cross-Connection for Overhead dialog

See Figure up.
According to the philosophy of offering only meaningful operations to the user, and being the OH cross
connection 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 one input TP
Choose 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
3AL 98325 ADAA 254/386
16.4.1.2 TP Search dialog
The TP Search dialog 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 VC 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
In this Network Element to connect the auxiliary / vocal channels and the Overhead bytes the following
operative indication must be observed:
- The auxiliary and vocal channels TPs are in the SERVICE board of slot 20
The auxiliary channels are:
• 1 x G.703 2Mbit/s (not operative in current release); in the screen are indicated as:
- R01sr1sl20/port#03--#01-eOCTP
Expanding this TP, 31 referred TPs are presented
• 2 x G.703 64Kbit/s; in the screen are indicated as:
- R01sr1sl20/port#04-#01-aux
- R01sr1sl20/port#05-#01-aux
• 2 x V11; in the screen are indicated as:
- R01sr1sl20/port#01-#01-v11CTP
• 2 x V24; in the screen are indicated as:
• 1 x phonic interface (voice channel); in the screen are indicated as:
- R01sr1sl20/port#01-#01-q23TTP
Expanding this TP, four referred TPs are presented
3AL 98325 ADAA 255/386
- The other boards used to terminate or cross-connect the OH bytes are the STM-n boards.
The OH TP is 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 Pass through channel.
The examples of the figure in this OH connection chapter can be helpful to the operator
16.5 OH TP creation
the OH TP creation option.

The OH TP creation dialog opens 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 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 clicks 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.
Figure 234. OH TP creation
3AL 98325 ADAA 256/386
ED
02
Figure 235.
SC.3: NE MANAGEMENT
OH Search TP for creation
3AL 98325 ADAA

257/386
16.6 OH TP deleting
the OH TP deleting option.
The OH TP deleting dialog opens and allows deleting 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; the 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 236. OH TP deleting
3AL 98325 ADAA 258/386
16.7 OH Phone Parameters
The OH phone parameters option permits to configure the telephone number and to manage the parameter
"phonic extension".
the OH Phone Parameters option. Figure below. Opens.
Figure 237. 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.
• The phone number field, to set the telephone number for operator calls 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 release
Apply button performs the configuration change of the modified phone parameters of the selected phonic
interface without close the dialog
3AL 98325 ADAA 259/386
17 Performance Monitoring
17.1 Introduction
The Performance Monitoring domain on the NE covers the monitoring of counter values for trail termination
points and connection termination points.
Examples of these counters are Error Seconds (ES) and Severely Error Seconds (SES).
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.
On the ETHERNET boards a set of performance counters are foreseen, for future releases ,for QoS and
maintenance purpose. By selecting the GMAU TP and subsequently the Transmission >Performance menu,
the following options are available:
– Configure Performance Monitoring. Not operative in current release.
– Display Current Data. Not operative in current release.
– Display Maintenance Counter. Not operative in current release.
17.1.1 Overview
These functionalities are described in the following chapters in addition to general information concerning
performance monitoring on the NE.
• 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 Modification/Display deals with the modification of threshold tables
and permits or display the same
17.1.2 Supported Performance Counters

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 possible
to start individual performance counters.
Near end performance monitoring events are:
3AL 98325 ADAA 260/386
• Background Block Error (BBE): A BBE counter measures the number of error blocks, which do not
occur as part of an SES.
• Error Second (ES): A one second period with one or more error blocks or with a defect.
• Severely Error Second (SES): A one second period which contains > 30% of error blocks, or at
least one Severely Disturbed Period (SDP). An SES is also counted as an ES.
• Near End Unavailable Second (NEUAS): 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 error block, which does not occur as part of
an FESES.
• Far End Error Second (FEES): Identifies, at a terminal, a one second period with one or more error
blocks or with a defect, which were received by the Far End Terminal.
• Far End Severely Error Second (FESES): Identifies, at a terminal, a one second period which
contains > 30% of error blocks, or at least one Severely Disturbed Period (SDP) which was
received/detected by the Far End Terminal. An FESES is counted as an FEE.
• 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.
Further definitions:
• Error 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 error 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.
• Pointer Justification Event (PJE): A PJE is an inversion of 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): An AFS 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 sonly supported for the regenerator section termination. Please note that this
counter is deprecated by ETSI and will be removed from international standards.
17.1.3 Far End (FE) and Near End (NE) Performance Counting
Far end performance monitoring parameters are derived from Remote Defect Indicators (RDI) and Remote
Error Indicators (REI).
3AL 98325 ADAA 261/386
Figure 238. 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.
17.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 (BEE, 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 (BEE, 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.
17.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 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.
3AL 98325 ADAA 262/386
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 24h
collection can be activate 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 24H counters.
The bidirectional process need 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.
17.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 2 x 24H are stored in the NE for each AU selected.
No Threshold crossing mechanism is supported on AU-PJE counters.
17.1.7 Tandem Connection Termination (TCT) and Monitoring (TCM)

TCM allows monitoring within the operator domain. The quality within the operator's on domain can be
proven regardless of the received quality of the signal at the entry point of the network. At the input point the
reference value is set to zero by using the TCM feature.
Tandem Connection Monitoring is applicable to VC-4-nc (n=1,4,16...), VC-4, VC-3 and VC-12 layers.
TCM provides:
- Incoming error count (IEC)
- TC_REI to indicate error blocks within the TC to the far end;
- OEI to indicate error blocks of the engrossing VC-n;
- TC_API as access point identifier complying with generic 16-byte string format;
- TC_RDI indicating to the far end that defects have been detected within the TC at the near end TC sink;
17.1.8 Performance Monitoring on 2 Mbit/s ISDN–PRA

The feature provides PM data collection at the 2 Mbit/s ISDN–PRA terminations.
The performance monitoring capabilities (applied on p12Mon TP) support both the standard data collection
modes:
– G. 826 bidirectional for QoS
– M2120 unidirectional near–end / far–end for maintenance
17.1.9 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: oo,
xx : 30 and xx : 45.
Performance monitoring can be enable and disables 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.
3AL 98325 ADAA 263/386
Event Counting
The performance events (e.g. SES) are counted in a counter per event. These counters are called the
current register. 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.
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 enable enabled during the entire monitoring interval (the elapsed time equals its nominal value,
i.e. 900 for 15 min. and 86400 for 24 h<9.
- PM was running properly (the suspect interval flag is not set)
By default, zero suppression is active for all PM enabled TPs. The number of suppressed intervals is
indicated.
17.1.10 Data Collection

N.B. PM data is not counted on boards that were plugged out at the moment of enabling data collection (see
PM Configuration dialog). Nevertheless, PM data is counted on boards that were plugged in at the moment
of enabling 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 Craft Terminal, 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 possible
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 complete
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.
3AL 98325 ADAA 264/386
17.1.11 Performance Monitoring History
Performance monitoring history data is necessary to assess the recent performance of transmission system.
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 one
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 the first of the recent registers. When
all recent registers are full, the oldest information is discarded.
17.1.12 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 modify and delete such tables.
Different thresholds can be assigned for near end and far end and 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
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..
Two thresholds mechanism 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 the 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 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) (only for 24 h)
3AL 98325 ADAA 265/386
17.2 Configuration ( SDH Port )
Use menu item Add TP to display a special TP in the Transmission menu.
Select the TP and open the PM Configuration dialog by clicking on the menu item Configure Monitoring.
Figure 239. Configure Monitoring.

This "PM Configuration" dialog serves as the main interface to all PM services. Every configuration
of all monitoring intervals is defined using this dialog.
It is possible to access the same "PM Configuration" dialog selecting a TP in the "Port view" and opening the
same Performance > Configure Monitoring option in the Port pull down menu.
N.B. To configure PM for au4CTPs and tuxCTPs, Path Overhead Monitoring (POM) or Supervised
Unequipped Termination (SUT, not supported) or Tandem Connection (TCT, TCM) must be created first.
The PM Configuration dialog is designed as a notebook consisting of a text field, to identify the selected TP,
and page labels.
The selected TP is indicated in the first box at the top of the screen: TP Identifier.
In case of au4CTP and tuxCTPs and VcxCTP, the PM Configuration dialog also contains an option button
showing the configured POM and SUT options as follow.
- PathOverhMon After Matrix
- PathOverhMon Before Matrix
- TP (Performance is made on AU-PJE)
- TCM After Matrix
- TCM Before Matrix
When more than one of the above options is chosen, a Question dialog box is displayed; click on Cancel to
continue or OK to interrupt any action.
N.B. As long as the PM Configuration dialog is open, a modified POM/SUT/TC configuration is not
automatically recognized and displayed. This may lead to rejections or confirmations of forbidden PM
configuration. Therefore make sure to reopen the PM Configuration dialog each time the POM/SUT
configuration is changed.
Each page label presents a range of parameters for one near end or far end granularity period (15 min. or 24
h), which together form a dataset. To select a special page label, click on the top part of the label:
3AL 98325 ADAA 266/386
• NE15, near end 15 minutes page
• NE24, near end 24 hours page
• FE15, far end 15 minutes page
• FE24, far end 24 hours page
• 24hBi, near and far end 24 hours page bidirectional (UAS is the sum of far end near end)
• e-e-24h, end to end 24 hours page (enable only on HPOM)
Each dataset has to be configured independently. For AU-4 CTP and TU-x CTP the highest criteria are POM
and SUT. I.e. select the POM or SUT option first and then configure the different associated data sets.
Confirm the configuration with Apply before you continue with a different POM or SUT option.
Figure 240. PM Configuration Dialog (example)
Figure 241. PM question dialog box (example)
3AL 98325 ADAA 267/386
Activate any item within the page label by selecting the respective radio button.
• 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.
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, as long as the
number of displayed datasets does not exceed 16 for 15 min. granularity.
Lock Data Collection. Not supported

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 for Craft Terminal.
• Notifications
UAT (only available for 24 h granularity)
For 24 h granularity, UAT (Unavailable Time) notifications are created if enabled. This notification
results in an UAT alarm in the Alarm Surveillance.
N.B. This parameter can only be selected during creation and cannot be subsequently modified.
Suppress Additional Threshold
Disabled: the alarm is generated every time the value exceed the upper threshold (value up).
Enabled: after a first alarm generation, the alarm is generated again when the value exceeds the
upper threshold (value up) after the lower threshold (value down) has been exceeded.
• Threshold Table
Attach 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).
Otherwise the Transmission view is blocked and only released by closing and reopening the PM
Configuration window and the Transmission view.
Click on button Attach... to open the PM Threshold Table Select dialog (see) and configure the
threshold table.
Select button Remove to disassociate the threshold table from the entity.
N.B. A threshold table can only be attached if Data Collection is enabled.
• Set Alarm Severity UAT
ASAP Id
This field shows the label of the ASAP pointer assigned to the UAT alarm
Set ASAP
Allows to set new ASAP pointer for the UAT alarm. The Set ASAP button opens the window
displayed.
3AL 98325 ADAA 268/386
Confirm the configuration with the button Apply before closing the dialog. Otherwise the configuration is lost.
17.3 Performance Monitoring on ETHRNET port

Performance Monitoring on Ethernet port, are described in the following paragraph:
– Paragraph 17.8 Configuration (Ethernet port) deals with the configuration of performance monitoring.
– Paragraph 17.9 Display Current Data (Ethernet port) deals with displaying current performance data.
– Paragraph 17.10 Display History Data (Ethernet port) deals with displaying history performance data.
An Ethernet link can be defined between two 10/100 Ethernet interfaces, or between two Gb Ethernet
interfaces, or also between a Fast Ethernet and a Gb Ethernet interface.
At the terminations of Ethernet link, it s possible to monitor the Ethernet frames and to collect information
about the Ethernet traffic by means of some counters.

Definitions of incoming and outgoing counter direction
[1] Incoming (network centric view): it refers to the direction starting from Ethernet domain toward SDH
domain (see Figure 242.). The traffic arrives to the board from an Ethernet link and goes out from an SDH
link.
[2] Outgoing (network centric view): it refers to the direction starting from SDH domain toward Ethernet
domain (see Figure 242.). The traffic arrives to the board from an SDH link and goes out from an
Ethernet link.
Figure 242. Counter directionality: network centric view
17.3.1 Overview
Ethernet counters can be distinguished from different points of view as depicted in Figure 230.
They can be:
– Physical interface counters
– aggregate counters
– flow counters
At physical interface level, the working status of transceiver is controlled.
3AL 98325 ADAA 269/386
At aggregate level, all Ethernet traffics passing through the same port can be viewed as an aggregate.
At flow level, each single flow is managed.
Besides this classification, some counters can be of Quality of Service, others only of maintenance.
Figure 243. Counter subdivision
17.3.2 Ethernet physical interface counters

Ethernet physical interface counters are used to test Ethernet interface working state.
They are:
– Symbol Error : for an interface operating at 100Mb/s, the number of times there was as invalid data symbol
when a valid carrier was present. For an interface operating in full–duplex mode at 1000 Mb/s, the number of
times the receiving media is non–idle carrier event for a period of time equal or greater than min Frame Size,
and during which there was at least one occurrence of an event that causes the PHY to indicate Data
reception error on the GMII. The count represented by an instance of this object is incremented at most once
per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment
if a collision is present.
– Media Available Exits : number of times that if Mau Media Available for this MAU instance leaves the state
available. Discontinuities in the value of this counter can occur at re–initialization of the management system,
and at other times as indicated by the value of if Counter Discontinuity Time.
– Jabber State : number of times that mau Jabber State for this MAU instance enters the state jabbering.
This counter will always indicate zero for MAUs of type dot1MauTypeAUI and those of speeds above
10Mbps. Discontinuities in the value of this counter can occur at re–initialization of the management system,
and at other times as indicated by the value if Counter Discontinuity Time.
– False Carrier: number of false carrier events during IDLE in 100BASE–X and 1000BASE–X links.
For all other MAU types, this counter will always indicate zero. This counter does not increment at the
symbol rate. It can increment after a valid carrier completion at a maximum rate of once per 100 ms for
100BASE–X and once per 10　s for 1000BASE–X until the next Carrier Event. Discontinuities in the value of
this counter can occur at re–initialization of the management system, and at other times as indicated by the
value of if Counter Discontinuity Time.
They are only maintenance counters.
17.3.3 Aggregate counter

Aggregate counters count frames that pass through the same port. Single flows are hidden inside the
aggregate.
Aggregate counters are (refer to :
– TRCO (Total Received Correct Octets): total number of octets of Ethernet frames received correctly by the
Virtual Ethernet Interface , including Ethernet header characters.
3AL 98325 ADAA 270/386
– TRCF (Total Received Correct Frames): total number of Ethernet frames received correctly by the Virtual
Ethernet Interface
– TTO (Total Transmitted Octets): total number of octets of Ethernet frames transmitted out by the Virtual
Ethernet Interface , including Ethernet header characters.
– TTF (Total Transmitted Frames): total number of Ethernet frames transmitted out by the Virtual Ethernet
Interface
– TDF (Total Discarded Frames): total number of Ethernet frames which were chosen to be discarded due to
buffer congestion. – TRSEF (Total Received Service Errored frames): it is the sum of three contributions.
They are Quality of Service counters.
Figure 244. Ethernet aggregate counter
17.3.4 Flow counter

Flow frames can be coloured Red Green or Yellow depending if flow is in compliance or not with SLA
parameters.
So flow counters definitions take in consideration frames colours.
Counters definitions are:
– TRCO_G (Total Received Correct Green Octets): total number of octets of green Ethernet frames received
correctly, including Ethernet header characters.
– TRCF_G (Total Received Correct Green Frames): total number of green Ethernet frames received
correctly.
– TRCO_Y (Total Received Correct Yellow Octets): total number of octets of yellow Ethernet frames
received correctly, including Ethernet header characters.
– TRCF_Y (Total Received Correct Yellow Frames): total number of yellow Ethernet frames received
correctly
– TRCO_R (Total Received Correct Red Octets): total number of octets of red Ethernet frames received
correctly, including Ethernet header characters.
3AL 98325 ADAA 271/386
– TRCF_R (Total Received Correct Red Frames): total number of red Ethernet frames received correctly.
– TDF_G (Total Discarded Green Frames): total number of green Ethernet frames which were chosen to be
discarded due to buffer congestion.
– TDF_Y (Total Discarded Yellow Frames): total number of yellow Ethernet frames which were chosen to be
discarded due to buffer congestion.
– TTO_G (Total Transmitted Green Octets): total number of octets of green Ethernet frames transmitted out,
including Ethernet header characters.
– TTF_G (Total Transmitted Green Frames): total number of green Ethernet frames transmitted out.
– TTO_Y (Total Transmitted Yellow Octets): total number of octets of yellow Ethernet frames transmitted out,
including Ethernet header characters.
– TTF_Y (Total Transmitted Yellow Frames): total number of yellow Ethernet frames transmitted out.
17.4 Display Current Data ( SDH Port )

Use menu item Add TP to display a special TP in the Transmission view.
Select the TP and open the Current PM Data dialog by clicking on the menu item Display Current Data.
Figure 245. Display Current Data view

This "Current PM Data" dialog serves to show the results and status of the Performance Monitoring
counters.
It is possible to access the same "Current PM Data" dialog selecting a TP in the "Port view" and opening the
same Performance > Display Current Data option in the Port pull down menu.
The Current PM Data dialog is designed as a notebook consisting of a text field, to identify the selected TP,
and page labels.
In case of au4CTP and tux CTPs, the Current PM Data dialog also contains an option button showing the
configured POM and SUT options to display as follow:
- Path Overh Mon After Matrix
- Path Overh Mon Before Matrix
- TCM After Matrix
3AL 98325 ADAA 272/386
- TCM Before Matrix
Each page label presents a range of parameters for one "near end and far end" granularity period (15min. or
24h) which together form a dataset. To select a special page label, click on the top part of the label:
• 15 min, near end and far end 15 minutes page
• 24 h, near end and far end 24 hours page
• 24hBi, far end 24 hours page bidirectional (UAS is the sum of far end and near end)
• e-e 24h, end to end 24 hours page (enable only on HPOM)
All datasets available, which are related to the selected TP and recorded in the current monitoring interval,
are displayed in this dialog.

The following items are indicated for each entity:
• 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
Indicates if collection errors occurred during the collection period.
• Threshold Table
• Indicates which threshold table is assigned to the entity.
• Current Problem List
Indicates current UAT ("Unavailable") and TCA ("Threshold Crossed") alarms.
N.B. The entry "Unavailable Threshold Crossed" 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.
• 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.
At the bottom the PM results are listed.
Reset button is used to restart the counting period. Two buttons are present for near-end and far-end
periods.
Press the Refresh button to update the window contents and display the latest data.
Using the Print button, PM data can be saved to a file or printed on paper.
3AL 98325 ADAA 273/386
Figure 246. Current PM Data Dialog (example)
17.5 Display History Data ( SDH Port )

Select the TP and open the PM History Data dialog by clicking on the menu item Display History Data.
Figure 247. PM History Data view
3AL 98325 ADAA 274/386
This "PM History Data" dialog serves to show stored Performance Monitoring counting.
It is possible to access the same "PM History Data" dialog selecting a TP in the "Port view" and opening the
same Performance > Display History Data option in the Port pull down menu.
The PM History Data dialog is designed as a notebook consisting of a text field, to identify the selected TP,
and page labels.
In case of au4CTP and tuxCTPs VCxCTPs, the PM History Data dialog also contains a cascading menu
that allows choosing the POM and SUT options to display follow:
- PathOverhMon After Matrix
- PathOverhMon Before Matrix


- TCM After Matrix
- TCM Before Matrix
Each page label presents a range of parameters for one "near end and far end" granularity period (15min.,
24h, 24h bidirectional). To select a special page label, click on the top part of the label.
All available datasets (entities), which are related to the selected TP, are displayed in the table:
• 15 min, near end and far end 15 minutes page
• 24 h, near end and far end 24 hours page
• 24hBi, far end 24 hours page bidirectional (UAS is the sum of far end and near end)
• e-e 24h, end to end 24 hours page (enable only on HPOM)
The PM data is displayed containing information concerning:
• Interval End Time
In the format dd.mm.yyyy hh:mm:ss.
• The number of recorded events concerning an entity is divided into near end and far end data
• Elapsed Time
Indicating whether the data collection was complete.
• Susp
Indicating suspect data where collection errors occurred during the collection period.
In case of 15 min. entities, a maximum of 16 datasets can be displayed simultaneously for each counter; the
24h entities display a maximum of one dataset. The user cannot change these figures.
If the limit of 16 datasets for 15 min. granularity and 3 datasets for 24 h granularity is reached, the oldest set
in the list is cleared when the next data set arrives.
Using the Print button, PM data can be saved to a file or printed on paper.
3AL 98325 ADAA 275/386
Figure 248. PM History Data Dialog (example)
17.6 PM Threshold Table Selection ( SDH Port )

The PM Threshold Table Select dialog pops up if the Attach button is clicked in the PM Configuration
dialog.
Figure 249. PM Configuration dialog

In addition, this dialog can be accessed using the Configuration menu:
N.B. Do not open several dialogs at the same time using both possibilities. Since those dialogs are not
synchronized, they could display different contents.
The dialog presents a list of existing threshold tables.
3AL 98325 ADAA 276/386
The tables are individually indicated with a number.
Each table is dedicated to specific entities, as reported in each table can be modified according the operator
selections.
The filtering criteria are not operative.
The user can perform the following actions:
• Create / Modify / Display a threshold table.
• Delete an existing 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 attached to a PM entity. An error message
informs the user of this situation.

• Attach the selected threshold table to a TP entity. It is only available entering from the PM
Configuration dialog.
The user has to close the dialog explicitly by clicking on the button Close.
Figure 250. PM Threshold Table Select
3AL 98325 ADAA 277/386
Table 8. Threshold table entities association
N Layer TP’s ASSOCIATED Granularity

1 STM4 RS 15 minutes
2 STM4 RS 24 hours
3 STM1 RS 15 minutes
4 STM1 RS 24 hours
5 STM4 MS NE / FE 15 minutes
6 STM4 MS NE / FE 24 hours
7 STM1 MS NE / FE 15 minutes
8 STM1 MS NE / FE 24 hours
9 VC4 Path Termination NE / FE 15 minutes
10 VC4 Path Termination NE / FE 24 hours
After the activation of a PM on a TP, it will be signaled in the Port view and in the Transmission view as for
the following figures:
Figure 251. PM Port View
Figure 252. PM Transmission View
17.7 PM Threshold Table Creation / Modification / Display ( SDH Port )
17.7.1 Creation
The PM Threshold Table Create dialog pops up when the Create button is clicked in the PM Threshold
Table Selection dialog.
Carry out the following steps to create a threshold table:
1) Enter the table name in input field Name.
3AL 98325 ADAA 278/386
Leading and succession blanks are ignored. Leaving the input field blank or entering only blanks is not
allowed and rejected.
2) Select a Granularity of 15 min. or 24 h for the entity.
3) Enter the set (Value Up) and the reset (Value Down) threshold values. Node that the reset value if
supported, will be available with 15 min. monitoring periods.
Table 1 shows the maximum performance monitoring event values.
The respective value is automatically reset to the maximum if a larger figure is entered.
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.
6) Confirm the entries with Apply to create the threshold table. A number of threshold tables can be created
from the same window.
Explicitly close the window with button Close.
Figure 253. Create PM Threshold Table
3AL 98325 ADAA 279/386
17.7.2 Modification
The PM Threshold Table Modify dialog (see) pops up if a threshold table is selected in the PM Threshold
Table Selection dialog (see) 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 1. Shows 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 (really "number") cannot be changed.

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).
Explicitly close the dialog with button Close.
17.7.3 Display
The PM Threshold Table Display dialog pops up if a threshold table is selected in the PM Threshold Table
Selection dialog and the Display button is clicked.
Refer to the previous chapter for a description of the attribute values and types.
Table 9. Maximum Performance Parameter Values
Performance Parameter Max. Value for 15-min period Max. Value for 24-h period
BBE, FEBBE on STM-4 8,639,100 829,353,600
BBE, FEBBE on STM-1 2,159,100 207,273,600
BBE, FEBBE on all the other board 539,100 51,753,600
OFS, ES, UAS, FEES, 900 86,400
SES, FESES 810 78,760
PJC high, PJC low 1,800,000 172,800,000
3AL 98325 ADAA 280/386
Figure 254. Modify PM Threshold Table
17.8 Configuration (Ethernet port)

Use menu item Add TP to display a special TP in the Transmission menu.
Select the TP (Gmau) and open the PM Configuration dialog (see Figure 255.) by clicking on the menu item
Transmission –>Performance –>Configure Performance Monitoring.
Figure 255. PM Configuration dialog
3AL 98325 ADAA 281/386
The Create Ethernet Counter window is opened
Figure 256. Create Ethernet counter

In that dialog the operator will be allowed to create/delete the current Data by checking/un–checking the
corresponding checkbox for the incoming and outgoing direction.
17.9 Display current Data (Ethernet port)

Select the TP and open the Current PM Data dialog (see Figure 257.) by clicking on the menu item
Display Current Data.
Figure 257. Display Current Data

This “Current PM Data” allows the operator to send a request in order to retrieve the maintenance counters.
The layout of the dialog ”maintenance counters” is depicted in Figure 258.
3AL 98325 ADAA 282/386
At startup the dialog displays an empty table; the dialog allows to choose the polling time and how many
times the action will be done; the default values for those entries are 0 for polling time and 1 for number of
retries, with that default configuration if the ”Start polling” button allows to perform the configured request. If
the number of retries is bigger than 1, several actions are performed on the NE.
During the polling interval the label of the button ”Start polling” will be changed to ”Stop polling”, and for
every response arrived a row is added to the table. Every time the operators push the ”Start polling” button
new lines will be added to the lines already present in the table.
Figure 258. Display current data
3AL 98325 ADAA 283/386
17.10 Display history Data (Ethernet port)
Select the TP (Gmau) and open the PM History Data dialog (see Figure 259.) by clicking on the menu item
Display History Data.
Figure 259. PM History Data dialog

The menu item ”Display History Data” will be opened:
– In case of one hour history data, the showed values are the hourly historic data collected by NE.
If the NE has collected only one history data, the dialog shows directly counter values.
If the NE has collected more than one history data, the displayed counter values are calculated as a
difference from the older available history data value.
The older one will be added in the first line with the label ”– –” and for each cell a tool tip will show the history
value received.
Figure 260. Display History Data
3AL 98325 ADAA 284/386
17.11 PM Overview
MSP Overview allows displaying performance overview.

Selecting the PM Overview option from the Configuration pull down menu figures below open.
Figure 261. PM Overview Menu item
Figure 262. PM Overview
3AL 98325 ADAA 285/386
Figure 263. Add TP for PM Overview

You can click “Add TP” button to see the PM data about the selected TP. Like the figure below.
3AL 98325 ADAA 286/386
ED
02
Figure 264.
SC.3: NE MANAGEMENT
PM Overview after add TP
3AL 98325 ADAA

287/386
18 Synchronization management
18.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.
Follows 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.
Figure 265. Internal organization of the SETS.

The internal sources (inputs) are:
• T1: Reference obtained from incoming STM-N signals,
• T2: Reference obtained from incoming 2 Mbit signals,
• T3/T6: Reference obtained from an external incoming 2.048 MHz signal,
• OSC: the internal oscillator.
The number of timing reference inputs depends on the configuration of the NE.
The external sources (outputs) are:
• T0: is the reference output signal for the clock and signal frames,
• T4: is the reference output for the external equipment synchronization.
• T5: is the 2 Mbit/s reference output for the external equipment synchronization
3AL 98325 ADAA 288/386
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 timing reference from available T1 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 timing reference from T1, T2, or T3 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.
The choice of the timing reference is done in two ways:
• 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 Operator.
N.B. The Operator for each candidate-timing source determines the priority level. 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 Section Overhead.
The SETG has 3 modes of operation:
• Locked mode:
The SETG output is fully controlled by the external timing references (T1, T2 and T3).
• 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.
3AL 98325 ADAA 289/386
18.2 Synchronization Management
The operations that can be done on the synchronization sources are the following:
• Timing Source Configuration,
• Protection Commands,
• T0 Configuration,
• T4 Configuration,
• T0 TEST Configuration (not operative in current release)
•
SSU Configuration,
• Remove Timing Reference,

• Change T4<-> T5
• Set T0 Equal T4
• Change 2 MHz -> 2 Mbit (available only if T3 has been configured as timing source)
• Remove T0 Equal T4,
• Transmitted SSM Quality Configuration,
• Frame Mode Configuration
• Show Timing Source.
Before any other operation the synchronization view has to be displayed.
18.2.1 Displaying the Synchronization View

The synchronization view can be normally opened using the menu Views options.
Using menu options, select the Synchronization option from the Views pull down menu as shown in the
following figure.
Figure 266. Obtaining the synchronization view
Selecting this menu option the synchronization representation will be displayed directly into the current
window instead of the current view. All the operations that can be done on the synchronization sources are
performed from this synchronization view.
3AL 98325 ADAA 290/386
18.2.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 option from the Views menu the Synchronization View is visualized.
Figure 267. Synchronization View Example
Synchronization View Description

The synchronization view provides two lists of allowable timing references:
• One for T0 timing output; T0 list is always present;
• One for T4 timing output; the presence of the T4 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 list contains:
3AL 98325 ADAA 291/386
- 6 timing reference for candidate inputs belonging to the allowable timing reference T1 configurable by the
operator.
The T0 and T4 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) list of the allowable timing references,
The protection system chooses the timing reference to generate the output T0 (T4) 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 after, the basic component contained in the synchronization view are described:
• Timing reference
Each allowable timing reference, , is represented by the graphical object displayed in the view; the timing
reference graphical object displays (with the exception of Internal Oscillator timing reference) the following
information (if the timing source has been declared by the user):
- The name of the selected timing source
- The status of the synchronization source: (lockout, manual switch, force switch, automatic switch, no
request, failure)
- The label of the quality level of the timing input source
- The priority of the timing input source
- 2 small boxes representing the SSF (Los) and DRIFT alarms detected on the timing source;
DRIFT means that the Frequency Offset between the external signal source and the internal clock is high
then the maximum tolerance value.
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 to visualize the alarm detail.
In the timing reference graphical object associated to the Internal Oscillator the following information are
displayed:
- The name of the timing source: Internal Oscillator
- A small box representing the LOS alarm; the small 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:
- Holdover, displayed when the clock operates in Holdover mode;
- Free running, displayed when the clock operates in Free Running mode;
- Empty string is displayed when the clock operates in Lock;
- A label "0" representing the priority of the Internal Oscillator
• Selectors
Small ellipse are used to represent respectively:
- The selector A;
- The selector B;
- The selector C;
• Squelch Status
3AL 98325 ADAA 292/386
Boxes contained a label field are used to represent the squelch statuses T0/T4 and T4. The box displays the
configured quality level threshold and it is lighted up when the output-timing signal is inhibited.
• Output Signal
An arrow and a label field are used to represent respectively:
- The output signal T0;
- He output signal T4/T5;
• Line Type
The following different line type are used to link the output signals and the respective allowable timing
reference:
- A solid line between an output signal and an allowable timing reference means that timing reference is
currently used to generate that signal;
- A dashed line between an output signal and an allowable timing reference means that timing reference is
not currently in use as timing source but will act in the protecting role.
In the same way, a solid line between T0 signal and T4/T5 signal (or T0_Test signal) box is drawn when T0
signal is used to generate T4/T5
18.2.3 Timing Source Configuration

This functionality allows configuring the input synchronization sources and configuring or modifying the
timing source priority and quality.
Figure 268. Synchronization Menu

The menu options are grey according to the current state of the dialogue box that the user can open.
Firstly select a synchronization source reference and after the Synchronization menu to open the
Synchronization Option List. Then select the Timing Source Configuration option from the cascading menu,
as shown in the above figure.
3AL 98325 ADAA 293/386
Figure 269. Timing source configuration for cross-Connect equipments

The Timing source configuration dialogue box which opens, displays the extracted quality of the selected
timing source. It permits to configure the following timing source information:
• Quality level,
• Priority level
Extracted Quality is the actual Rx quality retrieved from the signal received from the line.
Select an empty synch. Source reference and click on Timing Source Configuration and then on the Input
Source Choice. Figure below shows an example of the opened windows.
Following the TP Search procedure (rack, subrack, board, port) enter the physical board termination point
(TP) value; these TP are: EIS for electrical SDH port, OpS for optical SDH port.
This operation can be repeated for the entire available empty synch. Sources both for T0 clock and for T4
clock.
3AL 98325 ADAA 294/386
Figure 270. Synch. Source configuration for ADM equipment

Click on the Input Quality Configuration: the option button opens the option menu to select the desired
quality level.
Timing source may have, in increasing order, five quality levels: G.811, G.812T, G.812L, G.813, Q. Don't use
(where the highest quality level is G.811).
If Input Quality Configuration is set to a value other than "Extracted", Rx quality is forced to this 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 cannot be
changed. The other timing sources will have a priority of 1 to n.
Priority of 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.
Positioning the mouse on the synch. Source box "Port#" test, the corresponding physical interface
denomination (rack-subrack-board-port) is written on the window bottom left.
3AL 98325 ADAA 295/386
18.2.4 Synchronization Protection Commands
Select the timing reference from the synchronization view. Select the Synchronization pull down menu. You
can then select the Protection Commands to open the view. Menu options are grey. According to the
current state of the selected timing source.
Figure 271. 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
incoming timing source (except the internal oscillator) may be forced.
This selection is independent of 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.
Releasing terminates the forced switch mode or inhibiting the force selected 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.
To perform or release a T0 or T4 lockout, forced or manual selection, the following operations have to be
done:
• Select the T0 or T4 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.
Manual selection is not operative in the current release
3AL 98325 ADAA 296/386
18.2.5 Synchronization Configuration for T0/T4 and T4 squelch criteria
Select the available T0 or T4 synchronization sources and then the T0 or T4 Configuration... command.
This command permits to select/deselect the SSM algorithm, to set the wait time to restore and to enable the
revertive procedure if all these features are available.
In this NE revertive mode is hardware set, with fixed WTR.
In Revertive mode the internal selector A/B 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 to change the input source.
Selecting the T0 or T4 Configuration set the SSM algorithm and the Wait To Restore Time in the dialog box
upper part.
Click on the SSM Algorithm to select/deselect it.

Wait To Restore Time button and Revertive option button are disabled
Selecting T4 Configuration it is possible to set the T4 squelch criteria in the bottom dialog box.
This functionality allows configuring the external timing reference (T4) squelch criteria. The squelch function
mutes the relevant timing references in the presence of a failure condition.
Squelch may be forced by the Operator or according to 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 ): T0 may be squelched if all the allowable timing
references of Selector B have Quality Level lower than the programmable threshold.
• When T1 is selected to generate T4 (squelch A ) :T1 may be squelched if T1 Quality Level is lower
than the programmable threshold or if it becomes unavailable.
The T0/T4 and T1/T4 squelch fields enables you to configure the quality level of the T0 or T4 timing source,
opening the relevant option menu.
When the configuration of T0/T4 Configuration is completed, click on the OK button to validate the choice
and close the dialogue box.
The T5 output field allows selecting the bit used (from #4 to #8) for SSM.
The Cancel push button cancels the configuration and closes the dialogue box.
The T4 squelch configuration dialogue box enables you to configure the quality level of the T4 timing
source.
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 T4 Force Squelch enables you to activate the T4 forced squelch.
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.
3AL 98325 ADAA 297/386
Figure 272. Configuring the T0 or T4 SSM algorithm and the squelch criteria
18.2.6 SSU Configuration

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.
Figure 273. SSU Configuration
3AL 98325 ADAA 298/386
18.2.7 Remove Timing Reference
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 274. Synchronization source removing
To remove the selected source click on "OK" button of the confirmation message.
Figure 275. Synchronization source removing confirmation
18.2.8 Change T4 <-> T5

This Menu allows the change of the synchronization physical interface from 2Mhz (T4) to 2 Mbit/s (T5) and
vice versa
This menu is enabling only if the SERGI board is present in the subrack
Select Change T4 <-> T5 from the Synchronization.
3AL 98325 ADAA 299/386
Figure 276. Change T4 <-> T5 menu
A confirmation message appears
Figure 277. Change T4 <-> T5 confirmation message

Click on ok to confirm; the new window display T5 inserted of T4
Figure 278. Change T4 <-> T5: command execution
3AL 98325 ADAA 300/386
18.2.9 Change 2MHz ->2Mbit
This menu is enabled only if the operator selects a protection unit, which has as source a 2 MHz or a 2
Mbit/s without traffic
Select Change 2MHz -> 2Mbit from the Synchronization
Figure 279. Change 2MHz -->2Mbit menu
A confirmation message appears
Figure 280. Change 2MHz ->2Mbit confirmation message
Click on ok to confirm
The label of the protection unit will be changed depending on the kind of source selected:
• If the selected protection unit is a 2 MHz, then the label will be changed into 2Mbit/s.
• If the selected protection unit is a 2 Mbit/s, then the label will be changed into 2MHz
3AL 98325 ADAA 301/386
Figure 281. Change 2MHz -->2Mbit: command execution
18.2.10 Set and Remove T0 Equal T4

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 below.
Figure 282. 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.
18.2.11 Transmission of SSM Quality Configuration

Select the T1 SDH Reference Source in the Synchronization View 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.
3AL 98325 ADAA 302/386
Click on Transmitted SSM Quality Configuration of the Synchronization menu option.
Figure 283. Transmission SSM Quality

This Transmission SSM Quality window can be also opened from any SDH boards. Select the Equipment
option of the View menu, then access the Board view> Port view> Physical Media> SDH Tx Quality
Configuration; it is also possible to open the window selecting the Transmission option of the View menu,
then access the Physical Media> SDH Tx Quality Configuration option.

In both cases select the MST block
18.2.12 Show Timing Source

Selecting any T1 or T2 Reference Source in the Synchronization View hence the Show Timing Source is
enabled. This selection allows analyzing
the input source considering its payload structure and the related alarms (Port view is presented) .
Click on Show Timing Source of the Synchronization menu option.
Figure 284. Timing Source Example
3AL 98325 ADAA 303/386
19 MS-SPRING MANAGEMENT
19.1 MS-SPRING introduction

Different MS-SPRING protections architectures are provided: 2-Fiber (Terrestrial), and 4-Fiber NPE
(Transoceanic).
See ITU-T Rec. G.841.
The description of the MS-SPRING protections is inserted in the Technical Handbook.
4 Fiber MS-SPRING is not operative in this release.
19.2 MS-SPRING connection configuration advices

In the following paragraphs 2-Fiber and NPE advices are reported, 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.
19.2.1 2-Fiber MS-SPRING connection configuration advices

The following suggestions must be considered in the MS-SPRING 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 aggregates 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.
19.3 Operative sequence to configure MS-SPRING

In the following paragraphs 2-Fiber and NPE operative sequence to follow during configuration are inserted.
19.3.1 Operative sequence to configure 2-Fiber MS-SPRING

Next paragraphs lit the operative sequence according the type of produce to obtain.
- Activation procedure
a. Create an MS-SPRING schema with WTR, Node Identifier, Ring map and the related Squelching
Table for each node of the ring, in the desired order. WTR Ring must be same in all the nodes.
b. In the Main dialog for MS-SPRing management select "ACTIVATE" in each node of the ring, in the
desired order. Consider that, in this step, "Default K byte West or East" detection by View Protection
Status Parameter (under MS-SPRing label -> " Protocol exception"), will occur on those Aggregate
of the activated nodes connected to the nodes just deactivated.
3AL 98325 ADAA 304/386
c. Verify in the View Protection Status Parameter screen, at the end of the provisioning update, that all
the nodes of the ring are in "MS-SPRing activate" and "No request" state.
- Deactivation procedure
a. In the Main dialog for MS-SPRing management select "DEACTIVATE" in each node of the ring.
Consider that, in this step, "Default K byte West or East" detection by View Protection Status
Parameter (under MS-SPRing label -> "Protocol exception"), will occur on those Aggregate of the
activated nodes connected to the nodes just deactivated.
b. In the Main dialog for MS-SPRIng management select "DELETE" in each node of the ring.
- Removing a node
a. In the Manage ring Map view select the node and click on the "Remove Node" button
b. Modify the table in the Configure Squelch Table view according the new Ring Map.
c. Opening the View Protection Status Parameter screen, send "Force Ring" command to both NE's
adjacent to the node to be removed.
d. Physical remove the node
e. Connect the fibers and send the "Release" command of the relevant "Force Ring" to both NE's
adjacent to the removed node.
- Adding a node
a. In the Manage ring Map view insert the node in the selected position. Next nodes are automatically
shifted.
b. Modify the table in the Configure Squelch Table view according the new Ring Map.
c. Opening the View Protection Status screen, send "Force Ring" command to both NE's adjacent to
the node to be added.
d. Physical add the node and configure with 2-Fiber MS-SPRING activated with the right configuration
(Ring Map, Squelching table, WTR, node Identifier).
e. Connect the fibers and send the "Release" command of the relevant "Force Ring" to both NE's
adjacent to the added node.
19.4 MS-SPRING Management

In the NE current release the NE supports the MS-SPRING protection as "Terrestrial architecture".
The Transoceanic application with 4-Fiber is not supported in current release.
For the 2-Fiber Terrestrial application a max. of 16 nodes are available.
The available tables permit to visualize for the same NE the architecture 2 x 2-Fiber.
Figure below shows the MS–SPRing pull down menu.
Figure 285. 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.
3AL 98325 ADAA 305/386
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.
19.4.1 MS-SPRing Main 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 when no protection have been previously configured
Figure 286. MS-SPRing Management dialog box

The only command available is Create. The name of Schema Selection in not editable but is fixed to "No
Schema".
Click on Create to start the MS-SPRing configuration. Figure below opens
Figure 287. Creation Schema dialog box
3AL 98325 ADAA 306/386
The user can select the MS_SPRing Application and the Architecture types supported by the Network
Element.
Terrestrial MS-SPRing Application is a 2Fiber architecture.
Transoceanic MS-SPRing is a 4 Fiber architecture.(not supported in current relese)
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 and the "Protecting West and East" fields are disabled (greyed).
If the architecture is a 4F MS-SPRing, the working and protection ports on each side are different.
The label r(xx)sr(y)sl(zz)port#(hh) where r=rack, sr=subrack, sl=slot give the position of the physical port. In
the same board it is generally possible to have different port numbers.
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 below opens and all commands are now available.
The Holdoff Time command is not operative in current release.
Figure 288. Activated MS-SPRing Management

Click on Ring Map to configure the network node connection. Figure below opens
3AL 98325 ADAA 307/386
Figure 289. Node Id and associated ring node position

The Ring Map sets the connection sequence of the nodes within the ring. The matrix represents up to 64
nodes for transoceanic application and up to 16 nodes for terrestrial application.
Select Current Nodeld (it means the NE where the operator is acting) in the box and enable Change
Nodeld button (Id means Node Identifier)
Select Available Nodeld 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
Nodeld value.
This will be displayed in the Available Nodeld box then click on Add Node button.
Clicking on the Add Node button the selected "Ring position" will shift one step on the righ starting from "1"
position and in the "Nodeld" field the Available Nodeld values is inserted. In the same time the Available
Nodeld will be updated to a new value.
The default association for a four node node ring related to the fourth node (Nodeld=3; Ring Position=4) is
depicted in Figure below.
Figure 290. Ring map configuration
3AL 98325 ADAA 308/386
Repeat the procedure for all nodes of the ring selecting the different NEs and edit the different Current
Nodeld 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 Nodeld is inserted into Available Nodeld, so it can be
assigned to other nodes.
The OK button will start the selected operation, displaying the busy cursor up to receiving the replay to the
actions. Then the dialog window will be closed.
Click on the WTR Time button. Figure below opens
Figure 291. WTR dialog box

Click on the push mouse button on the p/down Seconds arrows to select the required delay for the relevant
WTR. The step value is 60 sec. The range value accepted is from 60 sec. to 900 sec. Click on OK to apply
the WTR Configuration.
WTR Time Span is used only for 4-fiber architecture; it is disable (grey) for 2 fiber architecture.
The same WTR Time Ring must be set on each Node of the ring.
19.4.2 Squelching table with 2 fiber Terrestrial applications

With a 2 fiber Terrestrial application can be selected the Squelching Table while with a 4 fiber
Transoceanic application can be selected the Ring Traffic
If the operator tries to select a different table a error message is visualized. Figure below shows the error
message visualized when is selected the Ring Traffic with a Terrestrial application.
Figure 292. Example of error message

Click on Squelching Table to configure the AU4 (Au4#1 to AU4#8 for 2F Architecture) connection between
the different nodes. Figure below opens. The same opens clicking on Configure Squelch Table of the MS-
SPRing pull down menu.
3AL 98325 ADAA 309/386
Figure 293. Squelching table

When the window is opened for the first time the squelching table is N/A (not available) because the NE 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 ( 0 to 15 ) from the available list using the slider or
the stepper arrows on the right scroll region.
19.4.2.1 Squelching table example
Figure 294. Example of a ring traffic
3AL 98325 ADAA 310/386
The squelching table is applicable only for OH-VC signals.
Figure 295. Connections of the ring
Figure 296. Squelching table of Node A, West side
3AL 98325 ADAA 311/386
ED
02
Figure 298.
Figure 297.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Squelching table of Node A, East side
Squelching table of Node B, West side
312/386
ED
02
Figure 300.
Figure 299.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Squelching table of Node B, East side
Squelching table of Node C, West side
313/386
ED
02
Figure 302.
Figure 301.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Squelching table of Node C, East side
Squelching table of Node D, West side
314/386
Figure 303. Squelching table of Node D, East side
19.4.3 Activate, Deactivate and Delete commands

The Main Activates commands 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 set "in service" the MS-SPRing protection mechanism on the selected schema
configuration.
To change from Active to Enable click on the Deactivate 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 304. Confirmation message

During the activation procedure on different ADMs some of these can be Activate status, others in Inactivate
status. The statuses, the protocol request and the protocol protection errors are described in next chapters
describing the "MS-SPRing Protection Status and Commands".
3AL 98325 ADAA 315/386
19.5 MS-SPRING Protection Status and Commands for 2 fiber terrestrial application
19.5.1 2F MS-SPRing protection commands

If a protection schema is Active it is possible to select one of the above commands.
Clicking on the Prot. Commands button in the MS-SPRing -> Main Dialog for MS-SPRing management
Figure below is opened.
Figure 305. Protection states and commands "Idle" status (2F)

The working/protection span state boxes are not available (grey) for the 2Fibwer MS-SPRing architecture.
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 below.
3AL 98325 ADAA 316/386
Figure 306. Ring Protection (2F)
19.5.2 External commands (2F)

The external protection commands are: Lockout, Force, Manual, Exercise (not operative in current release).
Manual. WTR.
The lockout commands disable the MS-SPRing management.
The lockout section present six lockout commands, four operative. Each lockout command is applicable on
different points where the lockout actions has to be performed and any "Lockout" command is associated to
a "Release" command to come back to the previous status.
Term "Span" identifies the section interested by the command; it doesn't assume the Span meaning of the
four-fiber protection.
Figure 307. Lockout commands (2F)
3AL 98325 ADAA 317/386
Figure 308. Protection and working channels where the lockout command can be activated (2F)
The protection events can be equipment/signal failure, signal degrade or external command or a
combination of them.
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 signaled if the K1/K2 protocol communicates to the network nodes what has happened,
without execute actions.
A single ring failure is completely restored but not two ring failures. 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 below shows the
association of tail end / tail end or head-end / tail end.
Some network protection mechanisms are accepted or rejected depending on the type (tail/head) (lockout
command.)
Figure 309. 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. (Protection not disable).
With the lockout protection span command and a ring failure, the ring protection is served if this ring failure
occurred the same section; the ring protection is disable if this ring failure has occurred in another ring
section. On the contrary, with the lockout working ring command failure and a ring failure along a different
section, the ring protection is served (protection non disable)
3AL 98325 ADAA 318/386
ED
02
Figure 310.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Tail-end / head-end protection with a lockout working and a one direction failure (2F)
319/386
Figure 311. Ring protection with a lockout and a ring failure (2F)
Figure below shows a ring with three nodes and the actions performed by the lockout commands. This
command disables the acknowledgment of the signal failure/degrade on the aggregate ports.
3AL 98325 ADAA 320/386
Figure 312. Lockout command and non-served failures (2F)

The Force command executes a forced protection. The Force Ring command substitutes the working
channels (AU4 1 to 8) with the opposite direction protection channels (AU4 9 to 16) between two adjacent
nodes.
The Force Span command is not operative in " fiber MS-SPring.
3AL 98325 ADAA 321/386
Figure 313. Forced and Manual Commands (2F)
Figure 314. Manual and Force Span/Ring command (2F)

The Manual command is similar to Force command but it is at a lower priority level with respect to 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 ring - lockout
protection span.
When a force ring command is applied a next working 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
protection. In this condition the ring can be split according the location of command and event. Vice versa
the "Manual" protection is exceeded by the "Automatic" protection. Figure below 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 98325 ADAA 322/386
ED
02
Figure 315.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Ring Protection with Force and Manual commands (2F)
323/386
Figure 316. Automatic protection Bridge/Switch (2F)

Each command starts when the proper button is selected. A dialog box 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 317. Example of confirmation dialog box

Clicking on the WTR command next figure opens. If the WTR box, in the Local Condition field of Figure
(Protection states and commands "Idle" status (2F)), 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 Clear
WTR Ring 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 318. Clear WTR command (2F)
19.5.3 2F MS-SPRing dual protection commands

In general dual contemporary "Events" can be:
Two external commands
3AL 98325 ADAA 324/386
An external command and a ring/span failure
Two contemporary ring/span 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 below 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 = signaled (no served) the column element

Rs = signaled (not served) the row element

Bs = signaled (not served) both row and column elements
When a command (Manual switch, Force switch) is neither served nor signaled that is erased
(it is not pending at the node)
Figure 319. Ring network reference scheme (2F)

Figure up visualizes the ring reference scheme: the adjacent node (AN) is the node connected to the
reference point.
The automatic protection for dual ring failure is below. Consider the network reference scheme with a tail end
/ head-end alarm propagation. In this figure are depicted the node switches for any reported double events.
3AL 98325 ADAA 325/386
ED
02
Figure 320.
SC.3: NE MANAGEMENT
Examples of Double ring failure
3AL 98325 ADAA

326/386
Figure 321. Automatic protection (tail/head) for double ring failure visualization
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 shows the "Events" at the reference pint. For each of them the
associated "Events" is listed on the first column at the left of the table.
Two manual ring commands can be only signaled: 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.
Lockout working SS.SN has priority with respect to Manual or Automatic protection and Force commands. In
the other cases. both commands are served (B).
Lockout protection 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 protection: B.
Lockout protection SS-AN/OS-SN overrides the Manual or Automatic or Force command because the
lockout protection controls the switching channels of the same Node.
Lockout protection SS-RN/OS-RN and manual or automatic or force command. The lockout protection
prevents the working 1-8 channels from being inserted into protecting 9-16 ones. The lockout protection is
served, because it has a higher priority, the ring protection will be only signaled (pending).
3AL 98325 ADAA 327/386
Figure 322. Tail / head dual "Events" Protection table (2F)
19.5.4 2F Protection Status Visualization

The protection statuses ring networks are:
- 1 - Lockout Switching
- 2 - Forced Switching
- 3 - Automatic Switching (MS-SPRing 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 signaled = pending status)
- Grey: 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 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.
3AL 98325 ADAA 328/386
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 signaled "Events" (the k1/k2 protocol communicates to the network nodes what has happened) are
pending B/S visualized as yellow box indications.
Figure below 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" result 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 adjacent 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 signaled with red boxes. The "Prot.
Unavailable" indications are activated when a lockout protection command is applied in a network node.
3AL 98325 ADAA 329/386
ED
02
Figure 323.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Manual command applied at the "Reference Point" ring network
330/386
Figure below reports the "Protection Status" for external "Force and Manual" commands in a 3 -node ring (A,
B, C). Figure below shows the lockout statuses and Figure below the automatic protection statuses.
Figure 324. Visualization of the Forced / Manual protection Statuses (2F)
3AL 98325 ADAA 331/386
ED
02
Figure 325.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Visualization of the Lockout command Statuses (2F)
332/386
Figure 326. 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.
3AL 98325 ADAA 333/386
19.5.4.1 Double ring failure
The double ring failure visualization Figures (Example of Double ring failure) are here following reported.
Figure 327. Protection status with double ring failure (reference point -SS-AN)
Figure up 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:
3AL 98325 ADAA 334/386
"Active”: green
"Request Node Ring" West ADM3-East ADM1: red (served)
"Request Node Ring" West ADM2-East ADM2: yellow (pending)
"Intermediate Node" ADM4: red
Figure 328. Protection status with double ring failure (reference point-SS-RN)
3AL 98325 ADAA 335/386
Figure up 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-Eas ADM1: red (switching for SF)
"Request Node Ring" East ADM4-East ADM2: red (switching of the opposite nodes)
Figure 329. Protection status with double ring failure (reference point-OS-AN)
3AL 98325 ADAA 336/386
Figure up 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 failures 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
Figure 330. Protection status with double ring failure (reference point-OS-AN) recovering to "idle"
3AL 98325 ADAA 337/386
Figure up 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
3AL 98325 ADAA 338/386
19.5.4.2 Double external command or an external command and a ring failure
Figure 331. Double manual ring command (reference point-SS-AN)

Figure up report 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.
3AL 98325 ADAA 339/386
"Active": green
"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
Figure 332. Double manual ring command (reference point-OS-AN)
3AL 98325 ADAA 340/386
Figure up 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
"Active”: green
"Request Node Ring" East ADM1-West ADM2: red (served)
"Intermediate Node" ADM3, ADM4: red
Figure 333. Manual ring and Lockout Protection (reference point-SS-SN)
3AL 98325 ADAA 341/386
Figure up 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
"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 98325 ADAA 342/386
Figure 334. Manual ring and Lockout Protection (reference point-SS-RN)

Figure up 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 is white
"Active”: green
"Manual Ring" commands 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
3AL 98325 ADAA 343/386
"Lockout Prot." command: East ADM3: red
"Prot. Unavailable" East ADM3 and West ADM4: red (served)
Figure 335. Automatic working ring and Manual Ring (reference point-OS-AN)
Figure up 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)
3AL 98325 ADAA 344/386
Figure 336. Automatic working ring and Force Ring (reference point-SS-AN)
Figure up 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
3AL 98325 ADAA 345/386
"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
Figure 337. Automatic working ring and Lockout working Ring (reference point-SS-SN)
Figure up reports the protection status with a ring failure and a lockout working command (reference point-
SS-SN). The lockout command has a higher with respect to the automatic protection switching and then only
the lockout command has been served. The box color is white unless otherwise specified:
3AL 98325 ADAA 346/386
"Active”: green
"Lockout Ring" commands East ADM1: red
"Request Node Ring" East ADM1 - West ADM2: red (served)
"Intermediate Node" ADM3 - ADM4: red
Figure 338. 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 is
white unless otherwise specified:
"Active": green
"Lockout Prot." commands West ADM3: red
3AL 98325 ADAA 347/386
"Prot. Unavailable" West ADM3 - East ADM2: red (lockout protections served)
"Request Node Ring" East ADM1 - West ADM2: yellow (automatic protection is pending)
3AL 98325 ADAA 348/386
20 ISA Port Configuration
20.1 Introduction
This Chapter describes the operations necessary for the ISA boards (ATM/PR_EA/Ethernet，ES,ISA BCE
and DVB-ASI boards) creation in the Equipment view and the ATM/PR_EA/Ethernet TTPs creation; as a
matter of fact ATM/PR_EA/Ethernet boards does not crate TTPs when they are configured.
The ISA board creation is performed when CT users sets an ATM/PR_EA/Ethernet board and then configure
the IP Address. Not for DVB-ASI boards.
For the TTPs creation refer to paragraph 20.2 where all the operation are explained.
For the ISA traffic configuration (for example creation of Hard/Soft cross connection, PNNI configuration etc.)
refers to the relevant OPERATOR’S HANDBOOK (ATM, PR_EA, ES or ISA BCE) where “Specific Terminal”
application is explained in details. Not for DVB-ASI boards.
The operational sequence to follow to manage ATM/PR_EA/Ethernet cross–connection is:
a) ATM/PR_EA/Ethernet board declaration (Equipment Set)
b) ATM/PR_EA/Ethernet IP Address Configuration (Called ISA board IP Address) (not needed for ISA-PR,
ETHERNET and DVB-ASI boards)
c) ATM/PR_EA/Ethernet board TTPs creation (VC4XV, VC12XV, VC3XV, VC4–4c TTP, VC4 TTP, VC3 TTP,
VC12 TTP, s31 TTP, E1 TTP)
d) TTPs cross–connection.
e) ATM/PR_EA/Ethernet traffic configuration with “Specific Terminal” application. Not for DVB-ASI board.
20.2 ATM/PR_EA/Ethernet board TTPs creation

In this paragraph will be explained how to create, delete and modify ATM/IP/ETH TTPs.
20.2.1 ATM boards

On the ATM 4X4 board can be configured up to 16 TPs (VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP, E1TTP)
with a maximum throughput of 622 Mbit/s.
On the ATM 8X8 board can be configured up to 32 TPs (VC4–4c TTP, VC4 TTP, VC3 TTP, VC12 TTP, s31
TTP, E1 TTP) with a maximum throughput of 1.2 Gbit/s.
Select ISA/IP/ETH Configuration option from the Configuration menu to open the ISA/PR_EA/Ethernet
ports Configuration.
3AL 98325 ADAA 349/386
ED
02
Figure 339.
Figure 340.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
ATM 4X4 MATRIX (with defined TPs)
ATM 4X4 MATRIX (initial empty fields)
350/386
The ATM/IP/Ethernet ports Configuration window is filled with notebook pages (initially blank), each page is
an ATM, Ethernet or PR_EA board with relevant 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/IP/Ethernet ports already created) via the three
buttons contained in the notebook page.
When the users want to create a new ATM port he can select an empty row, then in the “Selected Item”
sections, he can fill the field ”Signal” choosing among the available options and push the” Create” button.
The STM1 Number and the STM1 Time Slot are automatically assigned.
If the users 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.
To delete a port the user can select a row and push ”Delete” button.
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 row in the
ATM/IP/Ethernet configuration window and then click on the “Navigate” button.
Figure 341. Navigate to ATM port view (example)
3AL 98325 ADAA 351/386
20.2.2 PR_EA boards
On the PR_EA boards can be configured the following TPs:
– PREA4ETH: up to 59 TPs (SDH VC4, SDH VC3, SDH VC12) with a maximum throughput of 622 Mbit/s.
– PREA1GBE: up to 62 TPs (SDH VC4, SDH VC3, SDH VC12) with a maximum throughput of 622 Mbit/s.
Select ISA/IP/ETH Configuration option from the Configuration menu to open the
ATM/PR_EA/Ethernet ports Configuration.
Figure 342. PR_EA MATRIX (initial empty fields)
3AL 98325 ADAA 352/386
Figure 343. PR_EA MATRIX (with defined TPs)

When the users want to create a new PR_EA port he can select an empty row, then in the “Selected Item”
sections, he can fill the field ”Signal” choosing among the available options and push the “Create” button.
If the users 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.
It is possible to see the PR_EA Ports created as above explained by selecting the relevant row in the
ATM/IP/Ethernet configuration window and then click on the “Navigate” button.
3AL 98325 ADAA 353/386
Figure 344. MPLS port view example
20.2.3 10/100 Mbit/s fast ETHERNET board

On the FAST ETHERNET boards can be configured up to 11 TPs (VC4 TTP, VC3 TTP, VC12 TTP, C12XV
and VC3XV) on the port card (ETH–MB) and up 14 TPs (VC4 TTP, VC3 TTP, VC12 TTP, VC12XV and
VC3XV) on the relevant access card (ETH–ATX).
Select ISA/IP/ETH Configuration option from the Configuration menu to open the ATM/PR_EA/Ethernet
ports Configuration.
3AL 98325 ADAA 354/386
ED
02
Figure 345.
Figure 346.
SC.3: NE MANAGEMENT
ETH–MB (with defined TPs)
ETH–MB (initial empty fieds)
3AL 98325 ADAA

355/386
When the user want to create a new TPs he can select an empty row, then in the “Selected Item” sections,
he can fill the field ”Signal” choosing among the available options and push the” Create” button.
Note: in case of concatenated VC TP creation (example VC12XV or VC3XV), before to push on ”Create”
button it is also necessary to choose the Concatenation Level value; after creation command new fields and
a new button appear.
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.
The Ctrl Path Act. button allows to change the state of the concatenated virtual VCs (example VC12XV or
VC3XV) that could be “Idle” or “active”.; Click on Ctrl Path Act. button a new window will be opened.
Figure 347. Control Path activation window (example)

It is possible to see the VCs created on the ETHERNET board as above explained by selecting the relevant
row in the ATM/IP/Ethernet configuration window and then click on the “Navigate” button.
3AL 98325 ADAA 356/386
Figure 348. ETHERNET port view example
20.2.4 Gigabit/s ETHERNET board

Three architectures are possible to provide Gigabit Ethernet ports:
[1] 10/100Mbit/s Ethernet board (ETH–MB)+GBIT Access (GETH–AG).
With this architecture can be configured up to 2 TPs (VC4XV TTP Type concatenation level=1) on
the GETH–AG access card and up to 11 TPs (VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP, E1 TTP Type) on
the ETH–MB main board taking into account that the maximum throughput must not exceed 622 Mbit/s.
[2] GIGABIT board (GETHMB) stand–alone.
With this architecture can be configured up to 4 TPs (VC4XV Type) on each board taking into account that
the maximum throughput must not exceed 622 Mbit/s (for example it is possible to configure 1 port VC4XV
with a max. concatenation level equal to 4 or as alternative 4 ports VC4XV with concatenation level equal to
1).
The same rules above described are applicable to 1662SMC when the GIGABIT board (GETHMB) is
equipped in normal slot (i.e. slot with a throughput of 622 Mbit/s).
If the GIGABIT board (GETHMB) is equipped in one of these slots it is possible to reach a max
concatenation level equal to 7 per port. Of course this means that there is only one VC4XV with
concatenation level =1 available for another port and no resources for the last two ports present on the board.
3AL 98325 ADAA 357/386
For more details read the Gigabit Ethernet description reported in the Technical Handbook.
[3] GIGABIT board (GETH–MB) + GBIT Access (GETH–AG).
With this architecture can be configured up to 4 TPs (VC4XV Type) on the GETH–AG access card and up to
4 TPs (VC4XV TTP Type) on the GETH–MB main board taking into account that the maximum throughput
for the “couple” must not exceed 1.2 Gbit/s.; the concatenation level per port can be from 1 to 7.
The Gigabit Ethernet TPs creation follows the same rules described for the 10/100Mbit/s Ethernet Board.
20.2.4.1 Configuration of the auto-negotiation protocol on Gigabit Ethernet interface

In order to inter-working both with Gigabit Ethernet interfaces supporting the auto-negotiation protocol and
with Gigabit Ethernet interfaces not supporting it, the configuration of the auto-negotiation protocol has to be
managed also for the Gigabit Ethernet board, since R2.2.
The conditional package auto-Negotiation Package has to be instantiated by GMAU TTP Bid created at
Gigabit Ethernet SFP configuration of the board Gigabit Ethernet rate adaptive (GETH-MB); it has to be
confirmed if the auto-Negotiation Package has not to be instatiated also by GMAU TTP Bid of SFP of Gigabit
Ethernet access card (GETH-AG) in case of Gigabit Ethernet Stop Gap solution, since it doesn’t support the
protocol. The default value for auto-negotiation Status is disabled, for backward compatibility reasons, since
in the previous releases the protocol was not supported on Gigabit Ethernet interfaces.
Because of the Gigabit Ethernet application in OMSN doesn’t negotiate nothing: it works only at Gigabit rate
full duplex with Asimmetric pause mode, the only mainingfull attribute to be managed is auto-negotiation
Configuration, which enables or disables the protocol; the attributes auto Negotiation Configuration Par, auto
Negotiation Current Status, auto Negotiation Remote Signalling are auto Negotiation Remote Status have
not to be managed and in case of manager request, the NE replies “service Not Supported”. The action auto
Neg Restart has been requested in order to trigger the activation of the protocol when it has been enabled.
20.2.5 ES1-8FE boards

The Alcatel Reference ISA-ES NE can integrate:
• Local Ethernet Interface
__ 8 local Ethernet 10/100 BaseT interface;
• Remote Ethernet interface
__ Remote Ethernet 10/100 interface mapped into a single VC12, VC3, VC4, VC12 nv[n=1..63],
VC3-nv [n=1.3];
__ Remote Gigabit Ethernet interface mapped into a SDH VC4.
3AL 98325 ADAA 358/386
ED
02
Figure 349.
Figure 350.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
ES1-8FE MATRIX (with defined TPs)
ES1-8FE MATRIX (initial empty fields)
359/386
Figure 351. Navigate to ETH port view (example)
20.2.6 ES4-8FE boards

ES4-8FE board is supported from R.2.2 and it supports up to 8 100MB optical interfaces
ES4-8FE doesn’t foresee any access cards.
ES4-8FE supports up to 16 trunks between the SDH mapper and the L2 switch, in detail we can use up to 12
vc3 Groups (vc3Xvirtual), or up to 16 vc12 Groups (vc12Xvirtual) for a total maximum backplane capacity of
622 Mbit/s.
Furthermore ES4-8FE supports up to 4 vc4 terminations (vc4TTP), or up to 12 vc3 terminations (vc3TTP), or
up to 252 vc12 terminations (vc12TTP), for a total maximum backplane capacity of 622 Mbit/s.
Each vc3 groups can contains up to 3 vc3 (vc3Virtual) and each vc12 Group can contain up to 50 vc12
(vc12Virtual).
According to the port configuration two different operation modes are available for ISA ES-4-8FE as
explained in the table below:
XV type XV container supported

SMII operating mode GMII operating mode
VC12-xv (x = 1 to 50) (x = 1 to 63)
3AL 98325 ADAA 360/386
VC3-xv (x = 1 to 3) (x = 1 to 12)
VC4-xv (x = 1 ) (x = 1 to 4 )
LCAS protocol is supported on these VCs.

3AL 98325 ADAA 361/386
ED
02
Figure 352.
Figure 353.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
ES4-8FE MATRIX (with defined TPs)
ES4-8FE MATRIX (initial empty fields)
362/386
Figure 354. Navigate to ETH port view (example)
20.2.7 ISA-ES16 board

ISA Ethernet Switch at STM-16 (ISA-ES16), the detailed management description is present on [41], it has to
be managed since Rel. 2.3.
ISA-ES16 can integrate 14 local Ethernet 10/100 Base T via ISA ETH access board. And it can integrated 4
local GE 1000Base SX/LS(SFP module) via ISA GbE access board.
LCAS protocol is supported on these vc.
3AL 98325 ADAA 363/386
ED
02
Figure 355.
Figure 356.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
ISA-ES16 MATRIX (with defined TPs)
ISA-ES16 MATRIX (initial empty fields)
364/386
ED
02
Figure 357.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
Navigate to ETH port view (example)
365/386
20.2.8 DVB-ASI board
On the AS-ABNC access card can be configured up to 8 TPs (VC12XV and VC3XV).
Select ISA Port Configuration option from the Configuration menu to open the ISA ports Configuration.
ASI-ABNC (initial empty fields) ASI-ABNC (with defined TPs)
Figure 358. Example of DVB-ASI TPs creation

The ISA ports Configuration window is filled with notebook pages (initially blank), each page is an AIS-ABNC
access card with relevant ports.
The user can “create” a new port, “delete” an exiting one and “change” port associations (that means modify
the STM-1 number and STM-1 Time Slot on ISA ports already created) via the three button contained in the
notebook page.
When the user want to create a new TPs he can select an empty row, then in the “Select Item” sections and
fill the field “Signal” choosing among the available options.
Then it is also necessary to choose the Concatenation Level value (63 max VC12XV and 3 max VC3XV) and
push the “Create/Change” button; after creation command new fields and a new button appear.
The STM-1 Number and the STM-1 Time Slot are automatically assigned,
If the user wants to change the port attribute association he can select a filed row, then in the “Selected Item”
section he can change the fields “STM-1 number” and “STM-1 Time Slot” and than push the “Time Slot Sw”
button.
3AL 98325 ADAA 366/386
The Ctrl Path Act button allows changing the state of the concatenated virtual VCs (example VC12XV or
VC3XV) that could be “Idle” or “Active”.
Click on Ctrl Path Act button a new window will be opened; for details about the meaning of the field refer to
paragraph 11.6.8.
To delete a port the user can select a row and push “Delete” button.

It is possible to see the VCs created on the board as above explained by selecting the relevant row in the
ISA configuration window and then click on the “Navigate” button, the following figure shows an example.
3AL 98325 ADAA 367/386
ED
02
Figure 360.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
ASI-ABNC access card view example
368/386
20.2.9 BCE-ETH board
On the BCE-ETH access card can be configurated up to 8 TPs (VC12XV).
Select ISA Port Configuration option from the Configuration menu to open the ISA ports Configuration.
Figure 361. Example of BCE-ETH TPs creation

The ISA ports Configuration window is filled with notebook pages (initially blank), each page is a BCE-ETH
card with relevant 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 ISA ports already created) via the three buttons
contained
in the notebook page.
When the user want to create a new TPs he can select an empty row, then in the “Selected Item" sections,
he can fill the field "Signal" choosing among the available options.
Then it is also necessary to choose the Concatenation Level value (4 max VC12XV) and push
the"Create/Change" button; after creation command new fields and a new button appear.
In the ISA BCE Eth the Time Solt is in relation one to one with the board physical port (1 to 8).If the user
want to change the port attribute association he has to follow the following procedure:
• By the Ctrl Path Act. button that allows to change the state of the concatenated virtual VCs
(example VC12XV) that could be “Idle" or “active", set in "Idle" the VCs.
• 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.
• Move the board physical link in the new configuration.
3AL 98325 ADAA 369/386
• By the Ctrl Path Act. button set in “active" the VCs.
The Ctrl Path Act. button allows to change the state of the concatenated virtual VCs (example VC12XV) that
could be “Idle" or “active".;
Click on Ctrl Path Act. button a new window will be opened; for details about the mening of the field refer to
paragraph 11.6.8.
To delete a port the user can select a row and push "Delete" button.
To close the dialog box click on the “Close" push button.


It is possible to see the VCs created on the board as above explained by selecting the relevant row in the
ISA configuration window and then click on the “Navigate" button.
3AL 98325 ADAA 370/386
ED
02
Figure 363.
SC.3: NE MANAGEMENT
3AL 98325 ADAA
BCE-ETH access card view example
371/386
20.2.10 Interworking Configuration
Select Interworking Configuration option from the Configuration menu to open the DCC Interworking
configuration management.
Each screen is relevant to an ISA ES board and the fields are:
• Port: number of port of the ISA ES selected
• Interf. Index: index of the interface
• TSS3 Label: name of the TSS-3 equipment
• Remote MAC (TSS3): MAC address of the remote TSS-3 equipment

• Remote IP (TSS3): IP address of the remote TSS-3 equipment

• L2IKKMode: interworking mode
Figure 364. DCC Interworking configuration
See example shown in Figure 364 on page 372 and proceed as follows:
3AL 98325 ADAA 372/386
• select the row clicking on Port number (05 in the example);
• digit in the field ‘Selected Item’ the parameters relevant to the interworking (Ethernet in-band
management) and select ‘woppp’ option in the scroll menu;
• click on Create/Change button to confirm.
Create/Change button can be used to modify an existing configuration and the Delete button cancel the
selected configuration.
Click on Close button to finish the configuration.

3AL 98325 ADAA 373/386
21 Software Management
21.1 Generalities and descriptions

The Craft Terminal 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 NE software version as update and activation operation, 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.
The operations that can be undertaken in this section are:
• Display Software Download Information,
• Initiate / Abort Software Package Download,
• Manage Software Packages within NEs, activating the downloaded Software Package or coming
back to the previous condition.
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 Craft Terminal.
The software download general principle is represented in the following figure.
Figure 365. Software Download general principle
21.1.1 Naming Conventions

The naming conventions used for Download Management are the following:
3AL 98325 ADAA 374/386
• 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
- 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:
• Commit (active) version: the software version currently running on the NE.
• Standby version: is a software version which has been downloaded on the NE but which is not in
the active 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.
21.2 Software download operative sequence

Two main different operative condition are defined for this Equipment:
First installation of a 1662SMC
The NE is received without the relevant software install. The software download must be done
As described in the SIBDL section of this Handbook.
Updating a 1662SMC with already installed software.
Follow the operative indications.
21.2.1 Software Download upgrade

N.B. In order to migrate from Release 1.1A to a Higher Release, the download procedure requires
Two steps. The first is from 1.1A to 1.1X (intermediate package) and the second is from 1.1X
To the Higher Release (e.g. 1.1B1).
In order to update the following procedure is to be done as explained in the next steps:
a) Install the CD ROM with the NE Software Package on the PC.
3AL 98325 ADAA 375/386
b) Open a session on Craft Terminal application (start-up of the application, start supervision and NE login)
c) Check the present status of the software on a selected NE.
Download should not be performed in presence of unstable alarms

d) Open the Download menu.
e) Select the new software package in the server and triggers the download process, A message will indicate
the completed download.
f) Activate the package as presented at para.21.5 on page 383.
g) Check that the activated package is in the “Commit” status.
h) If problems are found with the new activated package, activate the previous software package
(Revert--back operation) to come back to the previous condition and then try to repeat the procedure.
21.2.2 NE Software package installation procedure

The following procedure allows the NE software package installation. According to the customer
Requirement two types of installation are possible:
[1] If only SDH software package installation is required follow the instruction from point a) to point e) and
than download the software package SDH (example 662SMC 2.1B.09) from the EML—USM (refer to
paragraph 21.4 on page 382 for details).
[2] If SDH+”Specific Software” package installation is required follow the instruction from point a ) to point o ).
In the example that follows will be described the ATM specific software installation; following the same rule
will be possible to install also the IP specific software.
21.2.3 Procedure
a) Install from CD ROM the NE Software Package on the Personal Computer, as explained in the
“1320CT Basic Operator Handbook”.
b) Run the 1320CT V.x platform
c) From Network Element Synthesis (NES) choose the Software Administration option of the Supervision --
> File Administration menu.
Figure 366. Software Administration menu
3AL 98325 ADAA 376/386
After the selection Figure below. Will be opened.
Figure 367. Software Package Administration view

d) Select the <SDH/WDM> tag
e) Press the <INSTALL> button to install the relevant software package
In the window that opens select the directory where the NE software package file has been installed
(Typically is Alcatel/usm/ect/swdw/<equipment name>/<version>/<descriptor file>) and execute.
Figure 368. SDH software package installation
3AL 98325 ADAA 377/386
f) Insert the ATM CD ROM in the computer
g) Select the <SERV. SPEC.> tag
h) Press the <INSTALL> button to install the ATM software package present on the ATM CD ROM In the
window that opens select the directory where the ATM software package file has been installed (typically is
/ect/swdw/<atm>/<version>/<descriptor file>) and execute.
Figure 369. ATM software package installation (example)

i) Select the <SDH/WDM> tag
j) Select the SDH software package base onto which ATM software package has to be merged
k) Press <Create Enhanced> to launch the software merging process and create the SDH+ATM
Software package The New Software package will be created.
3AL 98325 ADAA 378/386
Figure 370. OMSN enhanced software package creation (part A)
Figure 371. OMSN enhanced software package creation (part B)
3AL 98325 ADAA 379/386
The originated “Enhanced” software package has a new label as follows:
OMSN name = is the SDH name + “E” letter
OMSN version = is the SDH version
Example: Starting from SDH SWP 662SMC ver. 3.xy.wz will be created the OMSN SWP
662SMCE ver. 3.xy.wz
l) Select the <OMSN> tag.
m) Select the previously created software package (example 662SMCE 3.1.08)
n) Select the ATM software package (in the right view) (example ATM 1.01.07)
o) Press the <ADD> button
Figure 372. Enhanced software package (SDH + ATM)

It is now possible to download the enhanced software package (SDH + ATM) from the EML-USM
(Refer to paragraph 21.4 on page 382 for details).
3AL 98325 ADAA 380/386
21.3 Software Download Manager menu
All the software download operations are carried out from the software download manager.
Figure 373. Equipment view
To display the software download manager menu from the main view, select the NE on which you want to
perform download operations, then select the Download pull down menu. The following menu is displayed:
Figure 374. Download menu
3AL 98325 ADAA 381/386
21.4 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 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 375. SW Downloading dialogue box example

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 use the filter and display the selection, push on Apply filter(s) button. The SW packages existing on the
Craft Terminal are displayed.
In the next field the list of the packages is displayed:
• Server: name of the server,
• Package: name of the package,
• Version: version number of package.
Click on Forced push button to set the forced download attribute: then all software units of the Descriptor file
have to be downloaded. Otherwise only the units with different software version will be loaded.
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 from which you can if
necessary abort the software download.
3AL 98325 ADAA 382/386
You can monitor the download progress by means of the Software in Progress dialogue box, which also
enables you to possibly abort the current download.
Figure 376. Software download in progress (example)

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.
21.5 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.
The 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.
3AL 98325 ADAA 383/386
Figure 377. Software Package Information dialogue box (example)

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,
• Service Specific Components: name, release, version, edition of the Service Specific Components
(example ATM, IP etc.)
• Operational state: enabled or disabled,
• Activation date: date and hour of the last activation
• Vendor: the supplier of the product,
• 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
Action = (none) means no action to do
3AL 98325 ADAA 384/386
Action = activate serves to activate the selected SW package
Action = force (item not operative)
Select the Activate option of the "Current State\Action" field, to activate the Software package
The Sw units Det. button allows giving more information about a selected software package.
Clicking on it, the following window is displayed:
Figure 378. Detail software package (example)

Clicking on [-] symbol behind each software package all details disappear.
When you click on Close the previous view is displayed
In 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.
21.6 Mib management

This function allows to make a backup and/or a restore of the Mib.. (MIB is a data base pertaining the
configuration of the equipment).
Select the Mib management option from the Download pull down menu. The following window is displayed:
3AL 98325 ADAA 385/386
Figure 379. NE MIB management
The following fields are displayed:

• Available backups on local server: gives the list of the backups available on the Craft Terminal,
• Backup name: to enter the new backup name.
Three push buttons allow choosing the action with click on:
• Backup: performs the backup on the CT of the Mib present on the NE,
• Restore: this function 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 deleting 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.
To activate an already restored MIB you click on Activate push button. Only at this point it becomes
operative on the NE.
To exit of the NE MIB management window, you click on Close push button.
To save or load the Mib to/from an external disk follow the indication of the "Basic 1320CT Operator's
Handbook" using the menu options of the Network Element Synthesis.
END OF DOCUMENT
3AL 98325 ADAA 386/386
NE Maintenance
ED DATE CHANGE NOTE APPROVED BY PREPARED

BY

√
ED 02 SC.4 : NE MAINTENANCE
3AL 98325 ADAA 1/59
1 INTRODUCTION .......................................................................................................................................5
1.1 Scope················································································································································5
1.1.1 Document scope...........................................................................................................................5
1.1.2 Target audience............................................................................................................................5
1.2 Terminology·····································································································································5
1.2.1 Acronyms and abbreviations ........................................................................................................5
1.2.2 Glossary of terms..........................................................................................................................5
2 MAINTENANCE INTRODUCTION............................................................................................................6
2.1 Introduction ·····································································································································6
3 MAINTENANCE OF THE PC ....................................................................................................................7

3.1 Introduction ·····································································································································7
4 PROBLEM WITH CRAFT TERMINAL...................................................................................................8

4.1 Purpose of the procedure ··············································································································8
5 CORRECTIVE MAINTENCE (TROUBLESHOOTING).............................................................................9

5.1 Purpose of the procedure ··············································································································9
5.2 Troubleshooting organization ·······································································································9
5.3 On site Troubleshooting···············································································································11
5.4 Troubleshooting by means of the Craft Terminal.·····································································13
5.4.1 Preliminary Concepts and Definitions.........................................................................................14
5.4.2 Alarms/states view Organization (subrack view) ........................................................................15
5.4.3 Alarm synthesis indication ..........................................................................................................16
5.4.4 Alarm Surveillance (AS)..............................................................................................................19
5.4.5 Port View alarms.........................................................................................................................26
5.4.6 Board view alarms and states.....................................................................................................29
5.4.7 Subrack and Rack view alarms ..................................................................................................30
5.4.8 Fans Subrack alarms view..........................................................................................................32
5.4.9 Equipment View alarms ..............................................................................................................33
5.4.10 External Points alarms (Housekeeping) .................................................................................34
5.5 SYNTH16 Field Debug Form ········································································································36
5.5.1 Fault Description .........................................................................................................................36
5.5.2 Field Debug Guide......................................................................................................................36
5.5.3 Inside Failure or Internal Link .....................................................................................................36
5.5.4 RUP Alarm ..................................................................................................................................37
6 UNIT REPLACEMENT WITH A SPARE.................................................................................................39
3AL 98325 ADAA 2/59
6.1 COMPACT ADM migration procedure·························································································39
6.2 COMPACT ADM unit replacement·······························································································44
6.3 ATM MATRIX 4X4 unit replacement ····························································································49
6.4 IP MATRIX unit replacement ········································································································50
7 UPGRADING WITH NEW HARDWARE.................................................................................................51

7.1 SYNTH16 substitution with SYNTH16N ······················································································51
7.2 P4S1, S-41, L-41, L-42 substitution with P4S1N, S-41N, L-41N, L-42N ····································55
8 Flash Card Substitution ........................................................................................................................56

8.1 Flash card substitution procedure······························································································56

FIGURES
Figure 1. General Flow-chart for on site troubleshooting...........................................................................12
Figure 2. Power supply alarm ....................................................................................................................13
Figure 3. Transmission network level structure .........................................................................................15
Figure 4. Alarms/status view Organization (subrack view) ........................................................................16
Figure 5. Alarm pull down menu ................................................................................................................19
Figure 6. Alarm Surveillance......................................................................................................................20
Figure 7. Example of SDH Port View alarms (with MSP schema).............................................................27
Figure 8. Example of ATM Port View alarms .............................................................................................28
Figure 9. Example of Ethernet Port View alarms.......................................................................................28
Figure 10. Example of SDH Board View alarms and status ........................................................................29
Figure 11. Example of PDH Board View alarms and status ........................................................................30
Figure 12. Example of Subrack view alarms and status..............................................................................31
Figure 13. Example of Rack view alarm and status.....................................................................................32
Figure 14. Fans subrack alarms view ..........................................................................................................33
Figure 15. Example of Equipment View alarms and status .........................................................................34
Figure 16. Example of External Points alarms and status ...........................................................................35
Figure 17. Detail of Internal Link ..................................................................................................................37
Figure 18. Select modify from Equipment menu..........................................................................................41
Figure 19. Modify to SYNTH16 ....................................................................................................................41
Figure 20. Modify SFP module ....................................................................................................................42
Figure 21. Select corresponding STM-16 SFP module ...............................................................................42
Figure 22. COMPACT ADM unit replacement (EPS protected) ..................................................................45
Figure 23. COMPACT ADM unit replacement (EPS not protected) ............................................................46
Figure 24. Consulting and/or setting the local NE time................................................................................47
3AL 98325 ADAA 3/59
Figure 25. NE time dialogue box..................................................................................................................48
Figure 26. ATM MATRIX 4X4 unit replacement without EPS protection.....................................................49
Figure 27. ATM MATRIX 4X4 unit replacement with EPS protection..........................................................50
Figure 28. Upgrading with a new SYNTH16N EPS not protected...............................................................52
Figure 29. Upgrading with a new SYNTH16N EPS protected .....................................................................54
Figure 30. FLASH CARD substitution (COMPACT ADM EPS protected)...................................................57
Figure 31. FLASH CARD substitution (COMPACT ADM EPS not protected).............................................58
TABLES
Table 1. Alarms colors and Severity association ..........................................................................................17

Table 2. Alarm Synthesis indication ..............................................................................................................17
Table 3. Domain Alarm Synthesis indication ................................................................................................18
Table 4. Management States Control Panel. ................................................................................................18
Table 5. Alarm Surveillance information general description........................................................................21
Table 6. General aspect of alarms meaning and relevant maintenance actions..........................................21
Table 7. Board Alarm ....................................................................................................................................23
Table 8. Module Alarm ..................................................................................................................................26
Table 9. RUP specific number ......................................................................................................................37
3AL 98325 ADAA 4/59
1 INTRODUCTION
1.1 Scope

The aim of this document is to help the operator understand, configure and manipulate Network Elements
(NEs) easily, using the Craft Terminal (CT). 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.

This document is intended for the operators whose role is to manage the Network Elements.
--- 1320CT Basic Operator’s Handbook

The documents of this Handbook that should be read before starting this document are:
--- Introduction manual
1.2 Terminology


3AL 98325 ADAA 5/59
2 MAINTENANCE INTRODUCTION
2.1 Introduction
The maintenance procedures consist of the following steps:

• Maintenance of the PC.
• Problems with Craft Terminal (shut-down and restart of the PC).
• Corrective Maintenance (Troubleshooting).
• Unit replacement with a spare.
3AL 98325 ADAA 6/59
3 MAINTENANCE OF THE PC
3.1 Introduction
With regard to maintenance PC, refer to the constructor's documentation.

3AL 98325 ADAA 7/59
4 PROBLEM WITH CRAFT TERMINAL
4.1 Purpose of the procedure
This procedure describes the Shutdown and restarts the PC should the Craft Terminal Software Product not
be working properly or not responding to the operator's commands.
In order to shut down the PC execute the command: start>shut down
A window (Windows NT Security user dialog) is displayed. It permits to shut down the computer or restart it.
The same window is displayed pressing he keys <Ctrl> + <Alt> + <Del> simultaneously.
3AL 98325 ADAA 8/59
5 CORRECTIVE MAINTENCE (TROUBLESHOOTING)
Troubleshooting involves the detection, location and correction of failures in the equipment and the
replacement of the defective parts.
5.2 Troubleshooting organization
The troubleshooting procedure is carried out with the help of some flow-charts and tables, reported
hereinafter. Anyway this method does not deal with the following aspects (which are to be deduced in other
ways):
• Faulty electronic alarm indication, processing and detection circuits

• Faulty wiring (back-panel, connectors, etc.)

The following interfaces are present to troubleshoot the equipment:
• Q3 interface for Telecommunication Management Network
• F interface for Craft Terminal (Local or Remote)
• Remote Alarm for Supervisory Center
• LEDs on the units of the NE
Usually maintenance is firstly done via software (TMN or Remote Craft Terminal) to locate the faulty
equipment and the faulty unit or the faulty path and then on site to physically solve the trouble.
The Maintenance can be done:
• From a TMN network management center
• From a Remote Craft Terminal (RCT) management center
• From a station supervisory center
• On site
TMN network management center: by means of the TMN the maintenance technician can see the alarms
sent by each equipment of the managed network (see the relevant TMN handbooks).
Remote craft terminal: the operator, connected to a local NE, can remotely manage and troubleshooting a
network composed of max 32 NEs included itself. This handbook is used.
Station supervisory center: the maintenance technician refers to the Remote Alarms received from the
equipment in a centralized office of the station i.e.:
• T URGENT (MAJOR and CRITICAL), T NOT URGENT (MINOR): remote alarms pertaining to the
urgent, not urgent alarm type.
• TOR, TAND: remote alarms respectively due to the decrease or loss of one or both station power
supply DC voltages.
• INT: Remote alarm pertaining to the local (internal) alarm type
When a second CONGI unit is used the following remote alarms are added:
• TORC, TANC: remote alarms respectively due to the loss of +3,3V generated by the on board
converter in of one or both the CONGI units.
• IND: Indeterminate alarm synthesis. Indicates synthesis of alarms not associated to others severities.
Not operative.
3AL 98325 ADAA 9/59
• TUP: remote alarm due to microprocessor fault in the COMPACT ADM unit
• LOSQ2: remote alarm due to loss of communication with Mediation Device. Not operative.
Depending on the supervisory center organization, it is possible to locate the equipment in troubles and to
detect the failure type and source.
On site: the operator is on site in case:
1) The equipment is not managed by a TMN or by a Remote Craft terminal (RCT)
2) The equipment is not reachable by the remote manager (TMN or RCT) and is therefore isolated
3) Link problems are present
4) The trouble has been located and a substitution is necessary
In case 1), 2), 3), the alarmed equipment is checked by means of the local Craft Terminal and of rack LED
indications and station buzzers.

The NE is provided with LEDs, which indicate:
Units Alarms:
Each port card or access card of the equipment is provided with a bicolor LED (green/red) on the front cover
plate.
This LED indicates:
• When red, internal failure (indicates that the unit concerned must be replaced)
• When green, in service unit
Centralized Equipment Alarms:
All the alarms detected on the units are collected by the COMPACT ADM unit which will deliver centralized
optical indications (by means of LEDs on its front cover plate). Specifically, from the top to the bottom:
• Red LED: detection of an urgent (MAJOR and CRITICAL) alarm
• Red LED: detection of a not urgent (MINOR) alarm
• Yellow LED: alarm condition ATTENDED
• Yellow LED: detection of an ABNORMAL operative condition. Type: active loopbacks, forcing the
unit into service, laser forced ON or OFF, try to restore after ALS
• Yellow LED: detection of an indication (WARNING) alarm
The analysis of these LEDs permits to detect the alarm type (Urgent - Not Urgent - Indication) and relevant
condition (Abnormal condition, Attended).
In case of urgent or not urgent alarm, after having located the alarmed equipment, the alarm condition can
be "attended" by pressing the relevant alarm storing push button on the COMPACT ADM unit.
This condition causes:
• On the rack
The YELLOW LED to light up
The RED LED to go off
On the front cover plate:
Yellow LED (ATTENDED) to light up
Red LEDs NOT URGENT (MINOR) and URGENT (MAJOR and CRITICAL) to turn off (free to
accept other alarms)
3AL 98325 ADAA 10/59
If both LEDs are on, the Attend command should be given twice: one for attending the NOT URGENT
(MINOR) alarm and one for attending the URGENT (MAJOR) alarm.
5.3 On site Troubleshooting
The trouble-shooting operation proceeds according to the information indicated in the flow-charts:
• Figure 1.: General flow-chart
• Figure 2.: Power supply alarm
As indicated in the flow-charts the troubleshooting operation is done by means of the Craft Terminal, and of
the optical indicators (LEDs) present on the NE.
The Craft Terminal is cord-connected to the relative connector on the COMPACT ADM unit front cover plate
(F interface).
The Craft Terminal applications provide detailed information on the alarm state thus facilitating fault location
and subsequent removal.
To correctly execute the troubleshooting operations the technician must know the exact equipment
configuration (see Equipment Configuration applications on the Craft Terminal).
The aim of the flow-charts which follow and of the maintenance tables is to locate the faulty unit and to
replace it with a spare as well as to locate a failure along the link.
The flow-charts/tables should be also consulted when the unit LEDs flash, because the flashing condition
might be due to external alarm causes usually related to line problems.
3AL 98325 ADAA 11/59
ED
02
Figure 1.
SC.4 : NE MAINTENANCE
3AL 98325 ADAA
General Flow-chart for on site troubleshooting
12/59
WARNING!
Before removing CONGI unit from subrack, switch-off the relevant Station Battery Fuse Breaker present at
the top of the Rack or in the Station Distribution Frame; subsequently remove the station battery cable if
necessary and then extract the CONGI unit.
Figure 2. Power supply alarm

N.B. IF THE REMOTE ALARMS ARE NOT UTILIZED CHECK FOR PRESENCE OF STATION POWER
SUPPLY. SHOULD IT HAVE FAILED THEN ALL THE UNIT’S LEDS WILL BE OFF (FOLLOW OUTPUT
“YES” OF THE FLOW-CHART). IF POWER SUPPLY IS PRESENT PROCEDE WITH OUTPUT “NO”.
5.4 Troubleshooting by means of the Craft Terminal.
The troubleshoot proceeds checking the detailed information on the NE alarm by means of the craft terminal.
The information on the NE alarm will be mainly obtained by means of the craft terminal through the Alarm
Surveillance data and the alarms/status indications presented in the various views, depending on the level
of the structure under observation.
Navigation across the various level views is done from higher to lower levels, by double clicking on the
objects (see instructions on "NE management" section).
The NE hierarchy is organized in the following order: NE > rack > subrack > board > port > TP.
3AL 98325 ADAA 13/59
The troubleshoot procedure with the Craft Terminal consists of the following steps:
a) The alarms/status view organization for the equipment is shown in Figure 2.. Observe the active
alarms on the Severity Alarm Synthesis, Domain Alarm Synthesis and Management States
Control Panel always present on the window (it resumes all the NE alarms).
Table 3. Describes the meaning of these alarms/statuses and the relevant maintenance actions.
b) In case of alarm presence, access the Alarm Surveillance to troubleshoot. This application
gives the details of the detected alarms and helps for their localization.
Para 1.1.4 describes this view.
c) It is possible to analyze the detailed alarm presence on the TPs of each ports of the NE,
following the indication of Para 1.1.5.
d) It is also possible to check alarm and status at Board view; Subrack view and Equipment view
are also supplied following the indication of Para 1.1.6 and Para 1.1.8.
e) Eventual housekeeping alarms can be localized following the indications given in Para. 1.1.9.
f) These above said paragraphs describe general aspect of alarms meaning and relevant
maintenance actions that can be done with the information given in the applications.
g) The history of past events can be obtained by means of the Event log option of the Diagnosis
pull down menu (see "NE management" section).
Troubleshooting with Automatic Laser Shutdown
The Automatic Laser Shutdown (ALS) is used to protect the operator who is working with the optical fiber.
When the ALS is active, it may be difficult to detect the link failed.
To locate it, it is necessary to "force on" the ALS, thus enabling the optical power transmission on the
opposite direction of the failed link.
WARNING: During this phase the operator has to pay attention when working with fibers and connectors.
The ABNORMAL indication informs the operator of the ALS forced condition.
After having completed the maintenance, enable the ALS.
The ALS states are indicated in the port view.
5.4.1 Preliminary Concepts and Definitions

The following concepts and definitions are considered useful to facilitate maintenance operations with the aid
of the previously indicated tables.
The various units specified in the synchronous multiplexing hierarchy imply structuring the Transmission
network into three levels (sublevels of the physical OSI level):
• Transmission bearer level. It is the support for the path level and can be further split into physical
level (Transmission media) and Transmission section level. The sections can be either regenerator
or multiplexer and utilized for specific functions associated to the EOW channels of the SDH frame.
The interface alarms (or section alarms, indicated in the tables) belong to this level (example: Line
LOS, LOS, B2etc.).
• Path level It concerns the data transfer between the access points and the path. It does not depend
on the service or on the type of Transmission media. It constitutes the circuit level support. The path
can be either lower order (LO) or higher order (HO) depending on the capacity of data transferring.
Like the regenerator and multiplexer sections, the paths too have specific functions associated to the
EOW channels of the SDH frame. The alarms listed in the cited tables, where path level
troubleshooting is required, belong to this level (example: TU AIS, TU LOP).
3AL 98325 ADAA 14/59
• Circuit level. This level concerns the transfer of information between the access points and the
circuit proper. It is a direct support for the telecommunication services. It superimposes the SDH
function and is considered as the transport agent hence no SDH order-wire channel associated
functions are required. An example of this level alarm is Tributary LOS.
The above level structuring in the Transmission network is depicted in Figure 3.
Figure 3. Transmission network level structure
5.4.2 Alarms/states view Organization (subrack view)
3AL 98325 ADAA 15/59
Figure 4. Alarms/status view Organization (subrack view)
The critical (CRI) or major (MAJ) alarms indicate severe alarms that could have impact on the current
traffic (interruption or degrade). Thus requiring a rapid intervention to restore the regular working condition
of the equipment.
A message under the mouse facility provides the alarm or status complete denomination. A message
appears in the message area in the bottom left corner of the view.
5.4.3 Alarm synthesis indication

Alarms and Statuses synthesis are given in all the screens.
The alarms CRI, MAJ, MIN, WNG, IND are part of the Severity Alarms Synthesis area, presented in Table
3.
The alarms EXTP, EQP, TRNS are part of the Domain Alarms Synthesis area, presented in Table 4.
The alarms SUP, LAC, COM, OS, MGR, NTP and AC are part of the Management States Control Panel,
presented in Table 5.
All these indications (except for SUP, LAC, COM, OS, MGR, and NTP) are the summaries of particular types
of alarms detected by the equipment, hence the specific cause of alarm is to be found as indicated in the
following paragraphs: 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.9.
Table 1. Reports the association between the colors of the Alarms and their Severity.
3AL 98325 ADAA 16/59
For the Domain Alarms Synthesis the color corresponds to the highest severity among the set of the active
alarms for the relevant domain, according to the same rules of previous Tableau 1.
Tableau 2. Reports the colors of the Management States Control Panel when not in "normal" condition.
Table 1. Alarms colors and Severity association
Alarm Color Severity

RED CRITICAL
ORANGE MAJOR
YELLOW MINOR
CYAN WARNING
WHITE INDETERMINATE
GREEN NO ALARM
Table 2. Alarm Synthesis indication
Mnemonic Alarm/Status Maintenance

Description
CRI Critical alarm Synthesis of alarms that needs immediate trouble-
Shooting (typical: NE isolation). NB1.
See detailed indication in the following Para.
MAJ Major (Urgent) alarm Synthesis of alarms that needs immediate trouble-
shooting. NB1. See detailed indication in the following
Para.
MIN Minor (Not urgent) alarm Synthesis of alarms for which a delayed
troubleshooting can be defined. NB1. See detailed
indication in the following Para.
WNG Warning alarm Synthesis of alarms due to failure of other NE in the
network. NB1. See detailed indication in the following
Para.
IND Indeterminate alarm Synthesis of alarms not associated to the previous

Severities. Not operative. See detailed indication in
the following Para.
3AL 98325 ADAA 17/59
Table 3. Domain Alarm Synthesis indication
Mnemonic Alarm/Status Maintenance

Description
EXTP External Point Check the relevant station alarm associated to the
(Housekeeping alarm) Input housekeeping indication. See detailed indication
in the following Para.
SYNC Synchronization alarm Synthesis of alarms of the Synchronization domain.
See unit detailed indication in the following Para.

EQP Equipment alarm Synthesis of alarms of the Equipment domain.

TRNS Transmission alarm Synthesis of alarms of the Transmission domain.
Table 4. Management States Control Panel.
Mnemonic Description Maintenance

SUP Supervision state GREEN: NE is under supervision.
BROWN: NE is not under supervision.
Used in the OS.
Local Access State GREEN: Indicates that the Craft Terminal has the OS
permission to manage the NE (granted).
CYAN: Indicates that the Craft Terminal has not the
OS permission to manage the NE (denied).
COM NE GREEN: Identifies the “Enable” operational state of
unreachable/unreachable the connection between NE and Craft Terminal (SDH
service link up)
RED: Identifies the “Disable” operational state of the
connection between NE and Craft Terminal (SDH
service link down)
OS Operational System GREEN: Indicates that the N.E. is not managed by

Isolation the 1353SH
CYAN: Indicates that the N.E. is managed by the
1353SH.
MGR Manager level GREEN: Indicates that the N.E. is not managed by
the 1354RM
CYAN: Indicates that the N.E. is not managed by the
1354RM
3AL 98325 ADAA 18/59
NTP Network Time Protocol GREEN: NTP protocol enabled and both NTP servers
(main and spare) are unreachable.
BROWN: NTP protocol disabled.
CYAN: NTP protocol enabled and at least one NTP
servers (main or spare) are reachable.
AC Abnormal Condition GREEN: normal operating condition.
CYAN: detection of an ABNORMAL operative
condition. Type: active loopbacks, forcing the unit into
service, laser forced ON or OFF, try to restore after
ALS
NB1: Alarm Severity Assignment Profile can modify the assignment of each alarm root to the various
syntheses.
5.4.4 Alarm Surveillance (AS)

• In case of alarm presence, access the Alarm Surveillance (AS) to troubleshoot. For this purpose
select the Diagnosis pull down menu. With the Alarm pull down menu (see Figure 3.). It is possible
to show all the NE Alarms or filter the alarms report, for example displaying only the alarms of a
specific domain (i.e. only alarms of the Equipment domain).
Figure 5. Alarm pull down menu

After the selection a list with a synthesis of the Alarm Surveillance is presented and immediately after also
the detailed list of the Alarm Surveillance (see Figure 6.).
In the synthesis list it is possible to filter the data to show with the detailed view, double clicking on the
selected row of the sublist of Figure 6.
3AL 98325 ADAA 19/59
Figure 6. Alarm Surveillance

Detailed information of each alarm is supplied.
The alarms scenario is indicated by the colors of the alarms and by the information displayed in the table.
For instance, if an alarm is still active, the whole row has the same color of its relevant "Perceived Severity";
else if it has been cleared, the color of the row is green (except the "Perceived Severity"). The same
information is reported in the "Clearing Status" column.
In the following are shortly described the main information obtained in the AS view, starting from the left
column:
3AL 98325 ADAA 20/59
Table 5. Alarm Surveillance information general description
TITLE DESCRIPTION
- Perceived Severity The severity assigned to the alarm is indicated, with the relevant
color, i.e.: MAJOR, MINOR, WARNING
- Event date and time Indicates year, month, day and hour of the alarm.
- Friendly Name Identify the rack, board, port, and TP in which the alarm is
detected, i.e.: / r01sr1sl09/#port01-CE1S
- Event Type Indicates the family type of the alarm as subdivided in the ASAP
list, i.e.: EQUIPMENT, COMMUNICATION,

- Probable Cause The fault/problem is indicated, i.e.: loss of signal, transmitter

degraded, replaceable unit missing, resource isolation, ...
- Reservation Status Indicates if the alarm is reserved (RSV) or not (NRSV) according
security management.
- Clearing status Indicates if the alarm condition is terminated (CLR) or is still
active (NCLR). If cleared it has a green background,
- Acknowledge status Indicates if the alarm has been acknowledge (ACK) with the
button on the COMPACT ADM unit or not (NACK).
- Correlated notification Not used
flag
- Repetition counter Not used
The information supplied helps the operator during the troubleshooting operation.
Table 6. Supply general indications of alarms meaning and relevant maintenance actions that can be done
with the information given in the applications.
The maintenance action must take into account the board where the alarm is detected.
External Points alarms are referred to the input external point relevant to the Housekeeping signals. They
are available for the customer by connecting them to a dedicated subrack connector.
Detailed description of this application is given in the AS Operator's Handbook.
Table 6. General aspect of alarms meaning and relevant maintenance actions
PROBABLE CAUSE MAINTENANCE

NAME AND/OR ACRONYM
OF DISPLAYED ALARM
Loss of signal (LOS) Check line
Transmitter Signal (TF) Replace unit
Transmitter degraded (TD) Replace unit when possible (laser degrade)
Loss of frame (LOF) Check line (alignment problems due to line error)
AIS Check connected equipment
3AL 98325 ADAA 21/59
PROBABLE CAUSE MAINTENANCE
NAME AND/OR ACRONYM
OF DISPLAYED ALARM
Excessive BER (EBER) Check line (excessive line BER)
Degraded Signal (DS) Check line (line signal degrade)
Loss of Pointer (LOP) Check line
Payload Mismatch (PLM) Configuration error
Far End Received Failure (FERF) Check far-end equipment
Server Signal Failure (SSF) Check the entire TU path. Alarm indicates AIS signal received on the
TU
Frequency offset (DRIFT) Check reference and connection between it and the equipment
Loss of timing source (LOSS) Check reference and connection between it and the equipment
Resource Isolation Check connection between NE and Craft Terminal
Communication Subsystem Check Communication configuration (LAPD)
Isolation (CSF)
Unequipped (U) Configuration error
Referred to Signal Label
Unconfigured Equipment Unit inserted but not declared
Present (UEP)
Internal Communication Problem Reset NE. If persists substitute Compact ADM unit
URU - Underlying Resource Insert the board
Unavailable
PM_AS- Performance Check path / line section interested to the indication.

Monitoring Alarm Synthesis
CPE-Communication protocol Check MSP protocol (architecture type, switch fail)
error
LOMF - Loss Of MultiFrame Check payload structure

PTM- Path Trace Mismatch Not operative in current release
AUXP Check far-end equipment
Remote Node Transmission Check far-end equipment
error (RNTE)
Loss Of Alignment (LOA) Check payload
Member Not De-skew-able (MND) Check payload
3AL 98325 ADAA 22/59
Table 7. Board Alarm
NAME AND ACRONYM BOARD

MAINTENANCE
OF DISPLAYED ALARM ACRONYM
Unit missing A2S1 Insert missing unit

(RUM) A21E1
A3E3
A3T3
A4ES1
Unit Problem Replace unit
ETH–ATX
(RUP) ETH–MB
GETH–AG
HPROT
L–41
L–41N
L–42
L–42N
P3E3/T3
P4ES1N
P4S1
P4S1N
P21E1
P21E1N
P21E1N–M4 Insert right unit (unit inserted into a slot set
Unit type mismatch
P63E1 with another type of
(RUTM)
P63E1N unit)
P63E1N–M4
P8DCN
S–41
S–41N
ES1–8FE
ES4–8FE
COADM1
COADM2
COWLA2
COMDX8
ASI-MB
ASI-ANNC
Unit missing PR16
Insert missing unit
(RUM)
Unit Problem
Replace unit
(RUP)
Unit type mismatch Insert right unit (unit inserted into a slot set
(RUTM) with another type of unit)
Power Problem
Replace unit
(POP)
Pump failure
Replace unit
(PF)
3AL 98325 ADAA 23/59
Enclosure Door Open
Check that the protection cover in front of
(EDO) the unit has been correctly placed.
Unit missing (RUM) Insert missing unit
Unit Problem (RUP) Replace unit
Insert right unit (unit inserted into a slot set
Unit type mismatch (RUTM)
with another type of unit)
BST10
Pump failure (PF) BST15 Replace unit
BST17
Check that the protection cover in front of
Enclosure Door Open (EDO)
the unit has been correctly placed.

Unit Problem (RUP) GETH–MB Replace unit

ES1–8FE Insert right unit (unit inserted into a slot set
Unit type mismatch (RUTM) ES1–8FX
ES4–8FE
ES16 Internal dialogue problem in the unit. It
Internal communication problem indicates a temporary condition which will
be restored. If the condition persists it is
(ICP)
due to a unit hardware failure: in this case
it will activate the RUP alarm
Unit Problem (RUP) SYNTH16 Replace unit
SYNTH16N Insert right unit (unit inserted into a slot set
Unit type mismatch (RUTM) SYNTH4V2 with another type of unit)
PREA1GBE
PREA4ETH Update software version by means of SW
Version Mismatch
ATM8X8 download
ATM4X4 Internal dialogue problem in the unit. It
indicates a temporary condition which will
Internal Communication problem
be restored. If the condition persists it is
(ICP)
due to a unit hardware failure: in this case
it will activate the RUP alarm
Unit missing S–161
Insert missing unit
(RUM) S–161N
Unit Problem S–161ND
Replace unit
(RUP) L–161
Unit type mismatch L–161N Insert right unit (unit inserted into a slot set
(RUTM) L–161ND with another type of unit)
L 162
High Laser Temperature L–162N
L–162ND Replace unit
(HLT)
I–161ND
Cooling Fans Failure
Check the fan units and substitute the
(CFF)
faulty one
FAN
Unit missing
(RUM) Insert missing unit
Unit missing CONGI Insert missing unit

(RUM)
3AL 98325 ADAA 24/59
Unit Problem
Replace unit
(RUP)
Unit type mismatch Insert right unit (unit inserted into a slot set
(RUTM) with another type of unit)
This alarm type is present only on

LAN problem 1650SMC or 1660sm.
(LAN) Check LAN interconnection or substitute
CONGI unit
Battery Failure According to the CONGI slot check the

(BF) station battery.(Battery A or Battery B)
Fuse Failure
Substitute the fuse on the CONGI unit.
(FF)
Unit missing Insert missing unit

(RUM)
Unit Problem Replace unit
(RUP)
SERGI Insert right unit (unit inserted into a slot set
Unit type mismatch
(RUTM)
Battery Failure Check the Station Battery connected to the
(BF) unit
Fuse Failure Substitute the fuse on the CONGI unit.
(FF)
3AL 98325 ADAA 25/59
Table 8. Module Alarm
NAME AND ACRONYM MODULE MAINTENANCE

OF DISPLAYED ALARM ACRONYM
ICMI
SS-11
SL-11
SL-12
SL-12C
SES1
MM1
SS-42C
SL-42C
SS-41
Unconfigured SL-41
Equipment Present SL-42 Insert missing unit
(UEP) 1000B
1000BC
100B
OH–I
OL–IN
OH–MM
OL–MM
SS-161
SL-161
SL-162
SS-162C
SL-162C
SL-162D
ETHEMR
5.4.5 Port View alarms

It is also possible to analyze the detailed alarm presence on the TPs of each ports of the NE, following the
indication of the Port View chapter on the previous Section of this Handbook.
Figure 7. To Figure 9 is an example of a Port view.
For each TP of the Port a detail of the relevant alarms is presented.
On the port view the messages displayed at the bottom provide information about:
- MSP protection (if enable)
- Automatic Laser Shutdown state
- State of the connection for Ethernet port (available only if an Ethernet port has been selected)
A message under the mouse indicator provides the name of the alarm or object on which it is located, in this
way facilitating the identification of the alarm or status or object.
The non-alarmed condition of an alarm icon is represented by a green color and a "-" sign in the box.
The alarmed condition is represented by the color of its severity (as assigned by the ASAP) and an "X" signs
in the box.
3AL 98325 ADAA 26/59
The alarms, which can be found in the Port view, are listed in Table 7. Where the relevant maintenance
actions are reported too.
The information regarding ALS states and Laser state useful for operators safety purpose are
reported in the following:
ALS states:
Inactive = No ALS has been activated (Off) or the laser has been Forced ON/OFF.
In test = the laser restart has been automatically activated.
Active = The ALS has been activated (On).
Undefined = The ALS is not present (not created).
Laser state:
On = all OK or ALS not present (not created).

Off = Laser off (when ALS is created).
Forced on = ALS forced on by operator command.
Forced off = ALS forced off by operator command.
Figure 7. Example of SDH Port View alarms (with MSP schema)
3AL 98325 ADAA 27/59
ED
02
Figure 9.
Figure 8.
3AL 98325 ADAA
Example of ATM Port View alarms
Example of Ethernet Port View alarms
28/59
5.4.6 Board view alarms and states
The alarm and status indications at Board level can be obtained, following the indication of the Board View
chapter on the previous Section of this Handbook.
The alarm and status indications depend on the unit type; for example SDH units is organized on two levels
of presentation (in the first is selected one of the available ports) and each view contains dedicated
indications.
An alarm box is displayed on each port, to indicate whether the port is alarmed.
An indication in the "message/status area" provides information about the board Administrative State: "in-
service" or "out-of-service".
The alarms of the board are reported at the bottom of the "message/status area", by means of various boxes
containing relevant acronyms.
The non-alarmed condition of an alarm icon is represented by a green color.

The alarmed condition is represented by the color of its severity (as assigned by the ASAP).
In the view is present the Administrative State information: "in service" or "out of service".
The alarms, which can be found in the Board view, are listed in Table 7., where the relevant maintenance
actions are reported too.
In the view can also be present EPS indications.
Figure 10. Example of SDH Board View alarms and status
3AL 98325 ADAA 29/59
Figure 11. Example of PDH Board View alarms and status
5.4.7 Subrack and Rack view alarms

The alarms and status indications at subrack and rack level can be obtained, following the indications given
on the previous Section of this Handbook ("NE management").
An alarm box is displayed on each board, to indicate whether the board is alarmed. This board alarm
summarization is activated when one of the board alarms (those reported at the bottom of the Board view) is
active.
A "lock" symbol on a board indicates that it is "in-service". Else, the lack of this symbol indicates its "out-of-
service" state. (Administrative State information).
3AL 98325 ADAA 30/59
ED
02
Figure 12.
3AL 98325 ADAA
Example of Subrack view alarms and status
31/59
Figure 13. Example of Rack view alarm and status
5.4.8 Fans Subrack alarms view

To obtain Fan Subrack alarms indications click twice with the mouse on the relevant subrack drawing in the
rack level view.
• Battery Failure (BF): check that the station battery cables are right connected
• Cabling Problem (CAP): check that the alarms cable between the Fans Subrack and the CONGI unit
is right connected; check also the configuration in the Equipment menu. (Connected FAN to
CONGI#1 or connected FAN to CONGI#20)
• Temperature Out Of Range (TOOR): verify the Fan unit alarm and in presence of faulty substitute
the relevant unit; clean also the Dust filter if necessary.
3AL 98325 ADAA 32/59
Figure 14. Fans subrack alarms view
5.4.9 Equipment View alarms

The alarm indications at Equipment level can be obtained, following the indication of the Equipment View
chapter on the previous Section of this Handbook.
• Fuse Failure (FF): Substitute the fuse in the CONGI unit and search for a cause
• AND Battery Failure (ABF): Failure of the Service Power Supply connected to the CONGI Rack
connector.
• Backplane Failure (BKF): Substitute the Termination BUS
• Specific Hardware Diagnostic (SDH): Indicate the presence of link failure between the MATRIX and
one of the units; for details choose the Internal Link Monitor option of the Diagnosis menu.
These alarms can be observed at OS level.
3AL 98325 ADAA 33/59
Figure 15. Example of Equipment View alarms and status
5.4.10 External Points alarms (Housekeeping)

The alarms and status indications relevant to External Points (housekeeping) can be obtained, following the
indication of the External Points chapter on the previous Section of this Handbook.
The external state represents the alarm state. "On" when the alarm is raised, else "Off".
If the external point is active (On), a red flag is represented near the state of the concerned point.
In case of input point the alarm state is reported also in the user label column, by the box near its name:
Green color and sign "-" ---> means non-alarmed condition.
The change of color, as assigned by the severity (ASAP) ---> means alarmed condition.
3AL 98325 ADAA 34/59
ED
02
Figure 16.
3AL 98325 ADAA
Example of External Points alarms and status
35/59
5.5 SYNTH16 Field Debug Form
5.5.1 Fault Description

Please kindly check the equipment and provide detailed fault description. You can check the following most
frequently occurred problems, and provide more information at last. You can check more than one.
　 1. RUP or ICP
　 2. Internal Link or Inside Failure
　 3. Boot Failure
　 4. EPS Failure
　 5. DCC Failure
　 6. BIT Error
　 7. Mechanical Broken
　 8. Other: ___________________________________________________________
5.5.2 Field Debug Guide

Please kindly collect following equipment information before you decide to send back the fault board to
factory for repair. It’s very important to help the repair staff to identify the root cause and speed up repair.
1. Equipment software version: ____________________________________________
2. SYNTH16 hardware version: ____________________________________________
3. Equipment position in network (ring or line): _______________________________
4. SYNTH16 position in equipment (slot 6 or 15): _____________________________
5. Environment (temperature, fan, dust filter, etc): ______________________________
6. Fault description (as described above)
7. The impact of fault: ____________________________________________________
8. How long does the problem exist? ________________________________________
9. Does the problem trigger by any operation action or other problems? _____________
10. Which actions have been done: ___________________________________________
11. What’s the result if you try “Manual EPS”?
12. What’s the result if you reboot the equipment?
13. What’s the result if you replace the card?
5.5.3 Inside Failure or Internal Link

If you meet Inside Failure or Internal Link problem, please kindly help to provide more information described
below.
3AL 98325 ADAA 36/59
1. How do you notice this problem (from Internal link view, or there is traffic hit, or both):
____________________________________________________________
2. The status of clock (locked or not?)
3. Please attach the detail of Internal link view: (example below)

Figure 17. Detail of Internal Link
5.5.4 RUP Alarm

If you meet RUP alarm problem, please kindly help to provide more information described below.
1. If there is any abnormal on front LED?
2. Is there any other alarms on the fault SYNTH16?
3. Is there also ICP alarm? If yes please check
a) The configuration of OSPF
b) The configuration of ANTP sever
4. What’s the RUP specific number? (see below table)

Table 9. RUP specific number
Defect Specific Problem description

Number
POWER_FAIL 0
SPI_FAIL 1
ASIC_FAIL 2
NGI_FAIL 3
SPI_FAILURE 41 RUP caused by SPI driver error (error in reading R.I.,
error in access to port A, B, C, D or FPGA)
SPI_CHECK_FAIL 42 Error in configuration check of the FPGA
ISPB_FAIL 43 ISPB driver error
3AL 98325 ADAA 37/59
ASIC_CHECK_FAIL 44 Error in configuration check of the ASIC
NGI_CARD_FAIL 45 NGI in-band Card Fail
EXC_IPUMP 46 Excessive Pump Current
EXC_ITEC 47 Excessive Thermo Electric Cooler/Heater Current
FPGA_DWN_FAIL 48 Error in FPGA download driver
ICP 49 Internal Communication Problem detected by EC
SPI_A0 to SPI_D11 50 to 97 alarm detected by polling on SPIDER port A, B, C,
D…
3AL 98325 ADAA 38/59
6 UNIT REPLACEMENT WITH A SPARE
No particular indication is given as to spare handling, which is left to the Maintenance Administration.
The replacement procedures are executed as follows:
- Hardware set the spare unit exactly as the unit to replace. Settings are specified in the MS
documents. Here a layout figure indicates the exact location of all the setting arrangements and a
table relates the operations to achieve with the settings. The cited documents are enclosed in the
Technical Handbook.
- Simply replace those units not provided with any software settings
- With regard to the COMPACT ADM (also called SYNTH16 or SYNTH16N) unit refer to paragraph 6..
- With regard to the ATM MATRIX 4X4 unit refer to paragraph 6.2.
- With regard to the IP MATRIX unit refer to paragraph 6.3.

- When upgrading equipment with “New Hardware” (for example SYNTH16N unit) that substitutes the
old units (for example SYNTH16 unit), follow the indication given in paragraph 7.
WARNING: In order to avoid short Circuit, before substituting the CONGI unit,
Switch--off the relevant Station battery fuse breaker. Subsequently remove the Station
Battery cable and extract the CONGI unit.
WARNING: before inserting the new spare unit carefully checks the integrity of the
relative connectors.
Don’t insert the units that have been damaged during the transport/storing or in a phase
before their replacing.
6.1 COMPACT ADM migration procedure
Since release 2.7B, 1662SMC supports migrating from SYNTN4V2 to SYNTH16 smoothly on some
conditions.
This paragraph is the description of the migration procedure.
In this release, there are some restrictions for the migration:
- All traffics have to configured with SNCP protection
- The network with MSP or MS-SPRING protection can not support this migration.
- SYNTH4V2 equipped with 2 SFP modules or equipped with the second SFP can not support this
migration.
There is a reference network to specify the procedure.
3AL 98325 ADAA 39/59
STM-4 or
STM-1
w B e w C e
B tributary C tributary
STM-4 or STM-4 or
STM-1 STM-1
w A e
A tributary
The network has three NEs: A, B and C. In every NE w and e directions equipped with SYNTH4V2, and
every SYNTH4V2 card only has one SFP module in the first hole. The SFP module can be STM-1 or STM-4
module. All traffics are protected by SNCP protection, and in all NEs there is no MSP protection.
Before starting migration, please check the following points at first:
- Synchronization status should be in “Locked” status. Reference is propagated in clockwise, and the
spare is propagated in counter-clockwise, SSM is enabled, which will avoid the clock loop and
un_synchronization during the migration.
- No link failure in Internal Link Monitor
- The SNCP working in normal condition.
Check the SNCP condition in Cross Connetction Management, and test protection switching working
normally and the impact on traffic should be less than 50ms. At last make sure the Prot. Status is
“Normal I”
- The Compact ADM EPS protection working in normal condition.
Check the SYNTH4V2 in slot6 is active, and SYNTH4V2 in slot15 is stand-by. Test switching EPS, it
should work normally and the traffic is no error. Then switching EPS back, make SYNTH4V2 in slot6
is active, and SYNTH4V2 in slot15 is stand-by and the condition of two COMPACT ADMs should be
normal.
- Please backup the MIB of NEs in advance.
If the above conditions are OK, we can start the migration procedure:
Step 1, in NE A:
· Select NE A, switch EPS on spare COMPACT ADM in EPS management menu.
· Plug out the fibers of SYNTH4V2 in slot6 to make SNCP switch to protecting.
· Remove first the SYNTH4V2 in slot6 from the subrack, and insert the SYNTH16 into the subrack slot
previously occupied by the SYNTH4V2; a RUTM (unit type mismatch) alarm will be present.
3AL 98325 ADAA 40/59
· After EC restart, in the Equipment view select the slot6 where the SYNTH4V2 is inserted, select the
Modify option from the Equipment menu and select the SYNTH16 acronym from the list then click on
ok; refer to the below figures.
Figure 18. Select modify from Equipment menu
Figure 19. Modify to SYNTH16

· Double click slot6 to access the port, select the SFP module. Then select the Modify option from the
Equipment menu and select the corresponding STM-16 SFP module acronym from the list then click
on ok; showing as the following figures.
3AL 98325 ADAA 41/59
Figure 20. Modify SFP module
Figure 21. Select corresponding STM-16 SFP module

· Verify that the RUTM alarm disappear. Recover the fiber.
Step 2, in NE B:
· Select NE B, plug out the fibers of SYNTH4V2 in slot15 to make SNCP work on another side.
· Remove first the SYNTH4V2 in slot15 from the subrack, and insert the SYNTH16 into the subrack
slot previously occupied by the SYNTH4V2; a RUTM (unit type mismatch) alarm will be present.
· In the Equipment view select the slot15 where the SYNTH4V2 is inserted, select the Modify option
from the Equipment menu and select the SYNTH16 acronym from the list then click on ok;
· Double click slot15 to access the port, select the SFP module. Then select the Modify option from
the Equipment menu and select the corresponding STM-16 SFP module acronym from the list then
click on ok; Recover the fiber.
· Verify that the RUTM alarm disappear.
· After having verified that the SYNTH16 is now working, 10-20minutes later, switch EPS on spare
COMPACT ADM (SYNTH16 in slot15) in EPS management menu.
· Plug out the fibers of SYNTH4V2 of slot6 to make SNCP switch to protecting.
3AL 98325 ADAA 42/59
· Remove the SYNTH4V2 in slot6 from the subrack, and insert the SYNTH16 into the subrack slot
previously occupied by the SYNTH4V2; the RUTM alarm will be present in card and module.
· Modify SYNTH4V2 in slot6 to SYNTH16, and modify the SFP module of it from STM-1 or STM-4 to
STM-16; Recover the filber
· Verify that the RUTM alarm disappear, and SYNTH16 in slot6 is working normally.
Step 3, in NE C:
· Select NE C, plug out the fibers of SYNTH4V2 in slot15 to make SNCP work on input.
from the Equipment menu and select the SYNTH16 acronym from the list then click on ok;
· Verify that the RUTM alarm disappear.
· After having verified that the SYNTH16 is now working, 10-20minutes later, switch EPS on spare
COMPACT ADM (SYNTH16 in slot15) in EPS management menu.
· Plug out the fibers of SYNTH4V2 of slot6 to make SNCP switch to protecting.
· Remove the SYNTH4V2 in slot6 from the subrack, and insert the SYNTH16 into the subrack slot
previously occupied by the SYNTH4V2; the RUTM alarm will be present in card and module.
· Modify SYNTH4V2 in slot6 to SYNTH16, and modify the SFP module of it from STM-1 or STM-4 to
STM-16; Recover the fiber.
· Verify that the RUTM alarm disappear, and SYNTH16 in slot6 is working normally.
Step 4, in NE A:
· Select NE A, switch EPS on main COMPACT ADM (SYNTH16 in slot6) in EPS management menu.
· Plug out the fibers of SYNTH4V2 of slot15 to make SNCP switch to input.
from the Equipment menu and select the SYNTH16 acronym from the list then click on ok; a RUTM
(unit type mismatch) alarm will be present.
· Verify that the RUTM alarm disappear and the new inserted SYNTH16 is now working normally..
· Check all NEs in Cross Connection Management, the traffics should in NORMAL (I or P) condition.
3AL 98325 ADAA 43/59
N.B. This migration procedure also can be applied in migration from STM-1 to STM-4. The only difference is
that just modify the SFP module from STM-1 to STM-4, not need to Modify the card type.
N.B. It is highly recommended that this migration procedure should be proceed by Alcatel- Lucent
professional engineers.
6.2 COMPACT ADM unit replacement
N.B. In this paragraph for COMPACT ADM is generically intended one of the following unit:
- SYNTH16
- SYNTH16N
Various procedures are utilized to replace a COMPACT ADM faulty unit. They depend on the
following maintenance conditions:
- EPS protection of the COMPACT ADM unit
o EPS present or not (typically present)
o Failure on the Main board
o Failure on the Spare board
- Type of spares available:
o Spare without software installed. This is the normal condition.
o Spares with installed software, belonging to the same type of equipment and with SW
release identical to the unit to replace.
o Spares with installed software, belonging to the same type of equipment but with SW
release differing from the one of the unit to replace, or belonging to other types of equipment
or unknown.
- CONGI unit version (read NOTES in Figure 17. and Figure 18.)
- MIB store in the Craft Terminal or O.S.
The flow charts of Figure 17. And Figure 18. Illustrates the procedures to follow
For the COMPACT ADM substitution.
The procedure aim is to replace the faulty unit without causing configuration changes and/or
unwanted faults; when not possible this is indicated in the flow chart.
Replacement problems:
1) When replacing the COMPACT ADM unit the traffic of the two SDH ports is lost when not SNCP
protected. Then it is suggested to replace in low traffic condition.
3AL 98325 ADAA 44/59
ED
02
Figure 22.
3AL 98325 ADAA
COMPACT ADM unit replacement (EPS protected)
45/59
ED
02
Figure 23.
3AL 98325 ADAA
COMPACT ADM unit replacement (EPS not protected)
46/59
2) When plug-in a COMPACT ADM unit and supervision it with NM, if the following warning box appear.
Then it is suggested to set the NE Time in CT.

Because when NTP is enable, and the board initial time isn’t changed firstly, sometimes the DCC
channel doesn’t work, the NE will be lost from NM.

The procedure as following:
Select the NE Time... option from the Configuration pull down menu.
Figure 24. Consulting and/or setting the local NE time

The following dialogue box is opened from which you can set the local NE time.
3AL 98325 ADAA 47/59
ED
02
Figure 25.
NE time dialogue box
3AL 98325 ADAA

48/59
6.3 ATM MATRIX 4X4 unit replacement
Two different procedures are available for ATM MATRIX 4X4 substitution according to the EPS schema.
The flow-charts of Figure 19. Illustrates the procedures to follow for the ATM MATRIX 4X4 when it is not EPS
protected.
The flow-charts of Figure 20. Illustrates the procedures to follow for the ATM MATRIX 4X4 when it is EPS
protected.
The procedure aim is to replace the faulty unit without causing configuration changes and/or unwanted faults.
Figure 26. ATM MATRIX 4X4 unit replacement without EPS protection
3AL 98325 ADAA 49/59
Figure 27. ATM MATRIX 4X4 unit replacement with EPS protection
6.4 IP MATRIX unit replacement
For IP MATRIX unit replacement refer to the specific Operator’s Handbook.
3AL 98325 ADAA 50/59
7 UPGRADING WITH NEW HARDWARE
In the next paragraphs is indicated the procedure to follow when upgrading an equipment with “New
Hardware”.
The new Hardware is identifying by the “N” letter at the end of the acronym unit (for example SYNTH16N is
the new version, SYNTH16 without “N” is the old version).
This procedure permits, if the equipment is EPS protected and inserted in a protected network (linear or ring
protection), to maintain the system “in service”.
7.1 SYNTH16 substitution with SYNTH16N

According to the EPS and SNCP SYNTH16 protection scheme different procedure are available:
[1] Upgrading with a new SYNTHN16 EPS not protected
Substituting the old SYNTH16 all the traffic is lost!

• Remove the old SYNTH16 in slot 6 from the subrack
• Before inserting the new SYNTH16N in subrack slot 6, follow the instruction described in Figure 28..
At the end of the procedure a RUTM (unit type mismatch) alarm will be present.
• On Craft Terminal in the Subrack level view select the SYNTH16N unit in slot 6
• Select the Modify option from the Equipment menu and select the SYNTH16N acronym from the
list then click on ok.
3AL 98325 ADAA 51/59
Figure 28. Upgrading with a new SYNTH16N EPS not protected

[2] Upgrading with a new SYNTH16N EPS protected
Supposing that the STM-16 ports are not network protected, their traffic will be lost during
the substitution; the traffic of all the other board will not be lost.
3AL 98325 ADAA 52/59
• Remove first the old SYNTH16 in slot 15 from the subrack
• Insert the new SYNTH16N into the subrack slot 15; a RUTM (unit type mismatch) alarm will be
present.
• Select the Modify option from the Equipment menu and select the SYNTH16 acronym from the list
then click on ok.
• Force the EPS Switching on SYNTH16N in slot 15 by selecting the Switch option from the EPS
menu. For details see the paragraph “Switching EPS” in the “NE MANAGEMENT” section of this
Handbook.
• Remove the old SYNTH16 in slot 6 from the subrack

• Before inserting the new SYNTH16N in subrack slot 6, follow the instruction described in Figure 29..
At the end of the procedure a RUTM (unit type mismatch) alarm will be present.
• Select the Modify option from the Equipment menu and select the SYNTH16N acronym from the
list then click on ok.
3AL 98325 ADAA 53/59
Figure 29. Upgrading with a new SYNTH16N EPS protected
[3] Upgrading with a new SYNTH16N EPS protected with STM-N ports SNCP protected
The procedure is the same of that described on point [2]. But without traffic interruption on the STM-16 ports
present on the SYNTH16 because SNCP protected.
3AL 98325 ADAA 54/59
7.2 P4S1, S-41, L-41, L-42 substitution with P4S1N, S-41N, L-41N, L-42N
During the substitution the traffic carried by the units will be lost if not SNCP protected.
In the following an example will be given substituting a P4S1 with a P4S1N; the same procedure can be
applied to substitute the S-41, L-41, L-42 units respectively with S-41N, L-41N, L-42N units.
• Remove the old unit (example P4S1) from the subrack
• Insert the new unit (example P4S1N) into the subrack slot previously occupied by the old unit; on
Craft Terminal a RUTM (unit type mismatch) alarm will be present.
• On Craft Terminal in the Subrack level view select the slot where the new unit has been inserted
• Select the Modify option from the Equipment menu and select the acronym of the new unit (in our
example P4S1N) from the list, then click on ok.

3AL 98325 ADAA 55/59
8 Flash Card Substitution
8.1 Flash card substitution procedure
N.B.In this paragraph for COMPACT ADM is generically intended one of the following unit:
–SYNTH16
–SYNTH4V2
The 256 Mbytes FLASH card (housed on COMPACT ADM unit in slot 6) requires to be replaced with new
one.
N.B. Before to start with the FLASH card substitution (flow-chart of Figure 30 or flow-chart of Figure 31)
execute the following instruction:
a) Save the MIB as explained in Section 3 (NE MANAGEMENT), Paragraph “Mib management" of
this Manual.
b) Create and install the enhanced software package (SDH+ATM/IP) as explained in “1320 CT Basic
Operator's Handbook".
The flow-charts of Figure 30 illustrate the procedures to follow for the FLASH card substitution with
COMPACT ADM board EPS protected.
Warning: Substituting the FLASH CARD on COMPACT ADM unit (placed in slot 6) the traffic
of the two SDH ports will be lost if not SNCP protected.Then it is suggested to replace in
low traffic condition.
The flow-charts of Figure 31 illustrate the procedures to follow for the FLASH card substitution with
COMPACT ADM board not EPS protected.
Warning: Substituting the FLASH CARD on COMPACT ADM (placed in slot 6) unit not EPS
protected will cause traffic loss!Then it is suggested to replace in low traffic condition.
3AL 98325 ADAA 56/59
ED
02
Figure 30.
3AL 98325 ADAA
FLASH CARD substitution (COMPACT ADM EPS protected)
57/59
ED
02
Figure 31.
3AL 98325 ADAA
FLASH CARD substitution (COMPACT ADM EPS not protected)
58/59
ED
02
END OF DOCUMENT
3AL 98325 ADAA

59/59
Download and SIBDL Configuration

√
ED 02 SC.5: SIBDL
3AL 98325 ADAA 1/18
1 INTRODUCTION .......................................................................................................................................4
1.1 Scope................................................................................................................................................4
1.1.1 Document scope...........................................................................................................................4
1.1.2 Target audience............................................................................................................................4
1.2 Terminology.....................................................................................................................................4
1.2.1 Acronyms and abbreviations ........................................................................................................4
1.2.2 Glossary of terms..........................................................................................................................4

2 DOWNLOAD WITH SIBDL .......................................................................................................................5

2.1 Purpose of the procedure ..............................................................................................................5
2.1.1 SIBDL download procedure..........................................................................................................5
3 CONFIGURATION FOR SIBDL ..............................................................................................................13

3.1 Purpose of the procedure ............................................................................................................13
3.1.1 Remote Access Service configuration (only needed for Windows NT environment) .................13
3.1.2 Serial Cable Modem configuration for Windows NT environment..............................................13
3.1.3 Serial Cable Modem configuration for Windows 2000 environment...........................................14
ED 02 SC.5: SIBDL
3AL 98325 ADAA 2/18
Figure 1. SIBDL download procedure - step 1.............................................................................................6
Figure 5. SIBDL download procedure - step 5...........................................................................................10


Figure 9. Serial Cable Modem configuration - step 1 ................................................................................14
ED 02 SC.5: SIBDL
3AL 98325 ADAA 3/18
1 INTRODUCTION
1.1 Scope
The SIBDL Manual describes the SIBDL application, used to download the NE software via Q or F interface.
The SIBDL (Standard Image Binary Download) procedure contains the following operative descriptions:
• Download with SIBDL. The complete procedure is indicated.

• Configuration for SIBDL. Configurations to be performed for SIBDL operation are described.

The SIBDL Manual is intended for all users.
• 1320CT Rel. 1.1 Basic Operator's Handbook
1.2 Terminology

ED 02 SC.5: SIBDL
3AL 98325 ADAA 4/18
2 DOWNLOAD WITH SIBDL
This procedure describes how to download NE software with the SIBDL (Standard Image Binary Download)
program.
2.1.1 SIBDL download procedure

Download with SIBDL program is performed in the following phases:
• Turn on phase, when activating the NE.

•
Maintenance phase, when substituting the COMPACT ADM unit with a spare, and the spare one
don’t contain software.
ATTENTION:
Download with SIBDL program put the COMPACT ADM unit out of service regarding to the supervision and
control function, while the traffic is not lost.
It must not be executed to download a spare unit that contains software; in this case use the Download
option of the EML-USM, presented in the previous section.
SIBDL tool permits to download the software towards the NE using the Q interface (Ethernet connection) or
the F interface RS232 (serial line) of the NE.
When using the Q interface the time necessary to the operation is reduced to some minute.
WARNING:
In Windows NT environment, it should have configured, before to use SIBDL:
• TCP/IP protocol, Protocol Service, TEL NET Accessory, defined by the NT Administrator.
• RAS (Remote Access Service) and Serial Cable Modem.
In Windows 2000 environment, it should have configured, before to use SIBDL:
• TCP/IP protocol, Protocol Service, TEL NET Accessory, defined by the NT Administrator.
• Serial Cable Modem refer in Para Serial Cable Modem configuration for Windows 2000
environment
N.B. RAS (Remote Access Service) is not necessary in Windows 2000 environment
To download with SIBDL execute the following steps:

1) Connect the Craft Terminal with the NE:
• When download by means of Q interface, always connect both the F and Q interface.
• When download by means of F interface, connect only the F interface.
2) Start SIBDL, selecting Start > Program> Alcatel> SIBDL"version"> SIBDL

3) In the screen, which appears (see Figure 1.) with the command menu, select "automatic mode"
commands typing 8 and then ENTER.
ED 02 SC.5: SIBDL
3AL 98325 ADAA 5/18
Figure 1. SIBDL download procedure - step 1
4) In the field "source file" at the bottom write the path name of the NE descriptor file (see Figure 2.).
The path name has typically the following format (see the example in the figure):
<Directory>/<NE name and release number>/<file descriptor>
Note: In current release it is possible to download two types of file descriptor according to the following rules:
1. Create the NE software package as explained in the paragraph "NE Software package installation
procedure" NE MANAGEMENT of this Manual.
2. If the software to download manage only the SDH functionality, select the file descriptor in the
directory 1662SMC (example:
/ALCATEL/Q3CT_Pv1.3.05/FTservices/data/1662SMC/2.3.08/1662.dsc)
3. If the software to download manage the SDH+ATM/IP functionality, select the file descriptor in the
directory
1662SMC(example:/ALCATEL/Q3CT_Pv1.3.05/FTservices/data/1662SMCE/2.3.08/1662.dsc)
ED 02 SC.5: SIBDL
3AL 98325 ADAA 6/18
5) Press ENTER
6) This step (see Figure 3.) asks for the "IP Address" insertion.
In the field "NE_IP_address [PPP TEL NET]" at the bottom:
- With F interface: write PPP and press ENTER
- With Q interface:
• First possibility: write TELNET and press ENTER
In next step, which appears, write the IP Address of the Craft Terminal
• Second possibility: write the IP Address of the NE and press ENTER
ED 02 SC.5: SIBDL
3AL 98325 ADAA 7/18
7) This step (see Figure 4.) asks if the flash card must be formatted. Type "y" to format the flash card; as
result of this action the program ask for a confirmation (see Figure 5.)
ED 02 SC.5: SIBDL
3AL 98325 ADAA 8/18
ED
02
SC.5: SIBDL
Figure 4.
3AL 98325 ADAA

SIBDL download procedure - step 4
9/18

8)Type”y”.(if the synth16’s version is before 2005/01/19,please choose “n” to improve the download speed.)
(see Figure 6.).
9) Type "y”. The screen shows the automatic download evolution with a final message indicating the
completed download (see Figure 7.).
ED 02 SC.5: SIBDL
3AL 98325 ADAA 10/18
On the contrary repeat the procedure.
10) Press ENTER.

11) In the presented screen type 4 (see Figure 8.) and ENTER.
12) Extract and re-insert the EQUICO unit to complete the operation.
ED 02 SC.5: SIBDL
3AL 98325 ADAA 11/18
13) Extract and re-insert again the EQUICO unit to complete the operation
14) Run the 1320CT application, execute Start supervision and NE login
15) From Craft Terminal (EML-USM view) execute the normal download procedure:
N.B. Check that no RUTM alarm is present in the slot reserved to the main MATRIXN.
If RUTM alarm is present means the board type inserted in the subrack (typically MATRIXN in this release)
and the board type software configured (typically MATRIX) is not the same; under this condition the user
must change the board type with the Equipment->Set menu.
- Select Init download from Download menu

- Select the SW package to Download and click on OK button
In this condition the download is executed immediately
- Select Unit info from Download menu
- Select the Software Package loaded as explained above and activate it
- Press OK to complete the operation
In this condition the download is executed immediately.
ED 02 SC.5: SIBDL
3AL 98325 ADAA 12/18
3 CONFIGURATION FOR SIBDL
This chapter describes the configurations to be performed for SIBDL operation.
3.1.1 Remote Access Service configuration (only needed for Windows NT environment)
To install a new modem, the user should have administrator privileges and need the installation CD-ROM of
Windows NT, then execute:
• Double click on "My computer" icon on the PC desktop and double click on "Control panel" icon;
• Double click on "Network" icon;

• Select the folder "Services" in the "Network" window and push the button "Add": start the "Select
Network Service" window;
• Select Remote Access Service (RAS) in the dialog box;
• Follow the instructions.
3.1.2 Serial Cable Modem configuration for Windows NT environment

To install a new modem, the user should have administrator privileges, then execute:
• Double click on "My computer" icon on the PC desktop and double click on "Control panel" icon;
• Double click on "Network" icon;
Select the folder "Services" in the "Network" window;
• Select "Remote Access Service" and push button "Properties...”

• Push the button "add" in "Remote Access Setup" window;
• Push the button "Install Modem" in "Add RAS Device" window: start the "Install New Modem"
window;
• Put a tick against "Don't detect my modem; I will select him from a list" and push the "Next > " button;
• Push the button "Have disk...” start the window Install from disk;
• Push the button "Browse...
Search the folder where SIBDL is installed (Alcatel / SIBDL "version" / SIBDL /) and select the file
"mdmalca.inf", after push the button "Open";
• Push the button "OK" in window "Install from disk";
Select the modem named "Serial cable" in the dialog box of window "Install New Modem" and push
the button "Next >";
Put a tick against "Selected ports" and select only one port (the port must be available, i.e. not used
by another RAS modem) and push the button "Next >";
• Follow the instructions;

• Push the button "OK" in "Add RAS Device" window;
• Push the button "Continue" in "Remote Access Setup" window;
• Push the button "OK" in "Network" window;
ED 02 SC.5: SIBDL
3AL 98325 ADAA 13/18
3.1.3 Serial Cable Modem configuration for Windows 2000 environment
To install a new modem, you should have administrator privileges;
• Double click on "My computer" icon on your PC desktop and double click on "Control panel" icon;
• Double click on "Phone and Modem Options" icon and select the "Modems" folder;
• Push the button "Add": "Add/Remove Hardware Wizard: Install New Modem" window will appear;
• Put a tick against "Don't detect my modem; I will select it from a list" and push the button "Next >";
Figure 9. Serial Cable Modem configuration - step 1
• Push the button "Have disk...” the window "Install from disk" will appear;
• Push the button "Browse..."
• Search the folder where SIBDL is installed and select the file "mdmalca.inf", after push the button
"Open";
• Push the button "OK" on the "Install from disk" window;
• Select the modem named "Serial cable" into dialog box from "Install New Modem" window and push
the button "Next >";
ED 02 SC.5: SIBDL
3AL 98325 ADAA 14/18
• Put a tick against "Selected ports" and select only one port (the serial port must be available, i.e. not
used by another RAS modem) and push the button "Next >";
ED 02 SC.5: SIBDL
3AL 98325 ADAA 15/18
• The window "Digital Signature Not found" will appear: push the button "Yes", and after the button
"Finish" to end modem installation;
ED 02 SC.5: SIBDL
3AL 98325 ADAA 16/18
• At the end, the "Phone and Modem Options" window will display the installed modem
ED 02 SC.5: SIBDL
3AL 98325 ADAA 17/18
ED
02
Figure 13.
SC.5: SIBDL
END OF DOCUMENT
3AL 98325 ADAA

Serial Cable Modem configuration - step 5
18/18

1662smc 2.7 Oper - HDBK

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

1662smc 2.7 Oper - HDBK

Încărcat de

Drepturi de autor:

Formate disponibile

Operator Handbook

3AL 98325ADAA Ed.02

Alcatel 1662SMC Rel2.7

02 09/01/2009 Creation Chen Yu

01 03/01/2009 Creation Chen Yu

ED DATE CHANGE NOTE APPROVED BY PREPARED BY

Distribution: Internal External

2 PRODUCT-RELEASE HANDBOOKS ······································································································5

3 SAFETY NORMS AND LABELS ··············································································································8

4 HANDBOOK DESCRIPTION ····················································································································9

5 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION ································································12

1.1 General information

1.2 Handbook applicability

This handbook applies to the following product-releases:

PRODUCT ANV P/N FACTORY P/N

1.3 Purpose of the handbook

1.4 Handbook configuration check

1.4.1 Notes on Ed.01

version is stated in para.1.2 consists of the following handbooks:

Table 1. Handbooks related to the specific product hardware

REF HANDBOOK ANV Part No. FACTORY THIS HDBK

1662SMC Rel.2.7 Turnup & 3AL 98325 ACAA

[3] Provide information regarding Equipment Turn-On, Test and Operation

REF HANDBOOK ANV Part No. FACTORY THIS HDBK

REF HANDBOOK ANV Part No. FACTORY THIS HDBK

[6] ATM Rel.1.2 Operator’s Handbook 3AL 80814 AAAA 957.140.652 W

Provides ATM SMART Terminal screens and operational procedures

Table 4. Handbooks related to IP specific product SW

REF HANDBOOK ANV Part No. FACTORY THIS HDBK

Table 5. Handbooks common to Alcatel Network Elements using 1320CT platform

REF HANDBOOK ANV Part No. FACTORY THIS HDBK

Provides detailed information and operational procedures regarding the alarm

REF CD-ROM TITLE ANV Part No. FACTORY Part No.

1662SMC Rel.2.7 CD-ROM-DOC 3AL 98326AAAA

ATM Rel.1.1 CD-ROM DOC EN 3AL80739 AAAA 417.100.060

[15] IP 1.0 CD-ROM-DOC EN 3AL 81063 AAAA 417.100.084

Table 7. Optional handbooks common to 16xxSM

REF HANDBOOK ANV Part No. FACTORY THIS HDBK

3.1 First aid for electric shock

• Do not apply ointments or other oily substances.

3.2 Norms and labels

This handbook is composed of the following Manuals:

- Chapter 3: Safety norms and labels

5.1 Products, product-releases, versions and Customer Documentation

“product-release” has been designed, engineered and marketed for.

5.2 Handbook supply to Customers

5.3 Aims of standard Customer Documentation

Standard Customer Documentation, referred to hereafter, must be always meant as plant-independent.

5.4 Handbook Updating

The handbooks associated to the “product-release” are listed in para.2.

5.4.1 Changes introduced in the same product-release (same handbook P/N)

5.4.2 Supplying updated handbooks to Customers

5.4.3 Changes due to a new product-release

In the following “CD-ROM” means Customer Documentation on “CD-ROM”

5.5.1 Contents, creation and production of a CD-ROM

CD-ROMs for Network Management products do not contain:

The Installation Guides

5.5.2 Use of the CD-ROM

WorldView: Copyright 1981-1996

5.5.3 CD-ROM identification

Each CD-ROM is identified:

5.5.4 CD-ROM updating

Alcatel 1662SMC Rel2.7