1650 Operators Handbook

C.T.
OPERATORS HANDBOOK
Alcatel 1650SMC
STM1/4 Multiservice Metro Node
Rel.1.1
Version B6
VOL. 1/1
957.130.112 T Ed.05
3AL 78987 AAAA Ed.05
957.130.112 T Ed.05
1650SMC REL.1.1 C.T. OPERATORS HANDBOOK
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Purpose of the handbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4 Handbook configuration check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1 Notes on Ed.01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.2 Notes on Ed.02proposal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.3 Notes on Ed.02A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.4 Notes on Ed.03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.5 Notes on Ed.04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.6 Notes on Ed.05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 PRODUCT-RELEASE HANDBOOKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 SAFETY NORMS AND LABELS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 First aid for electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Norms and labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 HANDBOOK DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Products, product-releases, versions and Customer Documentation . . . . . . . . . . . . . . 5.2 Handbook supply to Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Aims of standard Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Handbook Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Changes introduced in the same product-release (same handbook P/N) . . . . . . . . . . . . 5.4.2 Supplying updated handbooks to Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3 Changes due to a new product-release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5 Customer documentation supply on CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.1 Contents, creation and production of a CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.2 Use of the CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.3 CDROM identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.4 CDROM updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S.MAGGIOJ.MIR ITAVE C.FAVERO R. LEONARDUZZI ITAVE C.FAVERO R.LEONARDUZZI ITAVE E.CORRADINI APPRAISAL AUTHORITY 2 3 3 3 4 5 5 5 5 6 6 6 7 11 11 13 15 17 17 17 17 18 18 18 18 19 19 20 20 20
05 04 01
1AA 00014 0004 (9007) A4 ALICE 04.10
030521 001124 991216 DATE
SC03052101 SC00110301
P.GHELFI ITAVE P.GHELFI ITAVE C.FAVERO ITAVE P.GHELFI ORIGINATOR
ED
CHANGE NOTE
1650SMC REL.1.1 Version B6 C.T. OPERATORS HANDBOOK
ED
05
SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 1 / 20
957.130.112 X
LIST OF FIGURES AND TABLES

Table 1. Handbooks related to the specific product hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2. Handbooks related to the specific product software management and local product control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3. Handbooks common to Alcatel Network Elements using 1320CT Rel. 1.x platform . . . . . Table 4. Documentation on CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5. Optional handbooks common to 1650SM and 1650SMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7 8 8 9
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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 1650SMC PRODUCT 1650SMC RELEASE Rel.1.1 VERSION (N.B.) B6 ANV P/N 3AL 36641 AAAA ANV P/N 3AL 37414 AAAA FACTORY P/N 521.204.800 FACTORY P/N 521.530.000
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 Operators Handbooks) are not modified unless the new software version distributed to Customers implies manmachine interface changes or in case of slight modifications not affecting the understanding of the explained procedures. Moreover, should the screen prints included in the handbook contain the product-releases version marking, they are not replaced in the handbooks related to a subsequent version, if the screen contents are unchanged.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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 (see para. 1.2 on page 3). This handbook must be used together with the associated Technical Handbook ( see Table 1. on page 7) and the 1320CT associated documentation ( see Table 3. on page 8) 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. 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
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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. 02 02A
HANDBOOK EDITION REGISTER AND SECTION TITLE 1 2 3 4 5 HANDBOOK GUIDE INTRODUCTION MANUAL NE MANAGEMENT MANUAL MAINTENANCE MANUAL SIBDL MANUAL
01
03
04
05
SECTION EDITION 01 01 01 01 01 02A 02A 02A 02A 02A 03 03 04 03 03 04 03 05 03 04 05 03
EDITIONS ASSOCIATED TO EQUIPMENT VERSION A 1.4.1 Notes on Ed.01 Ed.01 issued on December 16, 1999 is the first released and validated version of the handbook. EDITIONS ASSOCIATED TO EQUIPMENT VERSION B 1.4.2 Notes on Ed.02proposal Ed.02proposal issued on July 26, 2000 is the second neither released nor validated version of the handbook, associated to product release 1.1 Version B. This issue is not archived. It has been done for: different menu organization of the software product; some options of the previous release has moved under other menu. different Chapter sequence in the Handbook in order to improve the description of the different functions. AU4 concatenation has been added OH Phone parameter has been added Loopback management has been added Abnormal condition list has been added 63 x 2 Mbit/s EPS Unit replacement has been updated SIBDL procedure has been updated
The revision bar point out changes from Ed. 01 to Ed. 02proposal. 1.4.3 Notes on Ed.02A
1AA 00014 0004 (9007) A4 ALICE 04.10
Ed.02A created on September 6, 2000 is the second validated and officially released issue of this handbook, associated to product release 1.1 Version B. The revision bars in the handbook include changes from Ed.01 to Ed.02proposal and from Ed.02proposal to Ed.02A.
ED
05
957.130.112 X
1.4.4 Notes on Ed.03 Ed.03 created on October 23, 2000 is the third validated and officially released issue of this handbook, associated to product release 1.1 Version B. Changes with respect to Ed.02A are relevant to the addition of HW upgrading procedure from Version A to Version B in section Maintenance. In order to give a complete view of functionality changes of equipments SW from Version A to Version B, the revision bars in the handbook include all modifications: from Ed.01 to Ed.02proposal and from Ed.02proposal to Ed.02A and from Ed.02A to Ed.03.
EDITIONS ASSOCIATED TO EQUIPMENT VERSION B1 1.4.5 Notes on Ed.04 Ed.04 created on November 24, 2000 is the fourth validated and officially released issue of this handbook, associated to product release 1.1 Version B1. Changes involved are: 3 X 34/45 Mbit/s and 4 x STM1 Electrical port EPS has been added different Synchronization option menu different substitution procedure in case of faulty SYNTH1 or SYNTH1N unit EDITIONS ASSOCIATED TO EQUIPMENT VERSION B6 1.4.6 Notes on Ed.05 Ed.05 created on May 2003 is the fifth validated and officially released issue of this handbook, associated to product release 1.1 Version B6. Changes has been made for Software upgrade (no hardware updating). The revision bars in the handbook include changes from Ed.04 to Ed.05 only.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
2 PRODUCT-RELEASE HANDBOOKS
The list of handbooks given here below is valid on the issue date of this Handbook and can be changed without any obligation for ALCATEL to update it in this Handbook. Some of the handbooks listed here below may not be available on the issue date of this Handbook. The standard Customer Documentation in the English language for the equipment whose product-release-version is stated in para.1.2 on page 3 consists of the following handbooks: Table 1. Handbooks related to the specific product hardware FACTORY Part No. THIS HDBK
REF
HANDBOOK
ANV Part No.
1650SMC Rel.1.1 Technical Handbook [1]
3AL 78986 AAAA
955.100.722 K
Provide information regarding Equipment description, Installation, TurnOn, Test an operation, Maintenance , Hardware setting documentation 1650SMC Rel.1.1 Installation Handbook [2] Provide information regarding Equipment Installation, according to AInstallation Enginneering Dept. rules. 1650SMC Rel.1.1 Turnup & Commissionig Handbook [3] Provide information regarding Equipment TurnOn, Test and Operation, according to AInstallation Enginneering Dept. rules. Table 2. Handbooks related to the specific product software management and local product control FACTORY Part No. 957.130.112 X THIS HDBK
3AL 79584 AAAA
955.110.062 A
3AL 79585 AAAA
955.110.072 C
REF
HANDBOOK 1650SMC Rel.1.1 CT Operators Handbook
ANV Part No.
3AL 78987 AAAA
[4] Provides 1650SMC screens and operational procedures
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
Table 3. Handbooks common to Alcatel Network Elements using 1320CT platform N.B. 1320CT and Q3CTP are equivalent terms FACTORY Part No. THIS HDBK OR NOTE
REF
HANDBOOK
ANV Part No.
1320CT Basic Operators Handbook [5]
3AL 79186 AAAA
957.130.542 E ED. 02
Provides general information and operational procedures common to all 1320CT (Craft terminal) of Alcatel InfoModel Network Elements. 1330AS Rel.5.1 Operators Handbook [6] Provides detailed information and operational procedures regarding the alarm Surveillance software embedded in the 1320CT software package. ELM Rel.5.0 Operators Handbook [7] Provide detailed information and operational procedures regarding the Event Log Management software embedded in the 1320CT software package. Table 4. Documentation on CDROM See para. 5.5 on page 19 REF CDROM TITLE 1650SMC Rel.1.1 CDROMDOC EN [8] ANV Part No. 3AL 78999 AAAA FACTORY Part No. 417.100.013
3AL 71109 AAAA
957.130.722 A
3AL 71081 AAAA
957.130.462 E
Contains, in electronic format, the following handbooks: REF.[1] and [4] N.B. Handbooks REF. [2] and [3] are available only on paper support. 3AL 79549 AAAA 417.100.031
1320CT CDROMDOC EN [9]
Contains, in electronic format, the following handbooks: REF. [5] to [7]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
Table 5. Optional handbooks common to 1650SM and 1650SMC REF

HANDBOOK S91650SMC1660SM System Installation Handbook
ANV Part No.
FACTORY Part No. 955.100.692 N
THIS HDBK
3AL 78901 AAAA
[10] Provides detailed procedures for installing 1650SMC & 1660SM in S9 Rack according to AInstallation Engineering Dept. rules. OPTINEX RACK 1650SM 1660SM System Installation Handbook [11] Provides detailed procedures for installing 1650SMC & 1660SM in OPTINEX TM Rack according to AInstallation Engineering Dept. rules. N.B. Handbooks REF. [10] and [11] are available only on paper support
3AL 38207 AAAA
955.110.202 L
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
SC.1:HANDBOOK GUIDE
3AL 78987 AA AA
20
10 / 20
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
Mouth to mouth resuscitation method

Lay the patient supine with his arms parallel with the body, if the patient is laying on an inclined plane, make sure that his stomach is slightly lower than his chest. Open the patients mouth and check that there are no extraneous bodies in his mouth (dentures, chewinggum etc.), Kneel beside the patient level with his head. Put a hand under the patients head and one under his neck (see fig.) Lift the patients head and let it recline backwards as far as possible Shift the hand from the patients neck to is chin: place your thumb between his chin and his mouth, the index along his jawbone, and keep the other fingers closed together (see fig.). While performing these operations take a good supply of oxygen by taking deep breaths with your mouth open.
With your thumb between the patients chin and mouth keep his lips together and blow into his nasal cavities (see fig.)
While performing these operations observe if the patients chest rises (see fig.) If not it is possible that his nose is blocked: in that case open the patients mouth as much as possible by pressing on his chin with your hand, place your lips around his mouth and blow into his oral cavity. Observe if the patients chest heaves. This second method can be used instead of the first even when the patients nose is kept closed by pressing the nostrils together using the hand you were holding his head with. The patients head must be kept sloping backwards as much as possible. Start with ten rapid expirations, hence continue at a rate of twelve/fifteen expirations per minute. Go on like this until the patient has regained consciousness, or until a doctor has ascertained his death.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
3.2 Norms and labels

Refer to the Technical Handbook associated to ALCATELs 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 Heatradiating Mechanical Parts
ELECTROMAGNETIC COMPATIBILITY ELECTROSTATIC DISCHARGERS (ESD) EQUIPMENT LABELS
Identical or similar information on Personal Computer, WorkStation etc., other than ALCATELs, loaded with software applicative described in this Handbook, is supplied in the Constructors technical documentation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
SC.1:HANDBOOK GUIDE
3AL 78987 AA AA
20
14 / 20
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 productrelease 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 (EMLUSM) 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 1: Introduction. This chapter gives the structure of this manual. 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 operators command), access to the Event Log file. Chapter 8: Communication and Routing management. In this chapter are presented the communication and routing 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 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) and to access the port view.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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 1: Introduction. This chapter gives the structure of this manual. 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. Shutdown 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: Chapter 1: Introduction Chapter 2: Download with SIBDL configuration Chapter 3: Configuration for SIBDL
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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. Not operative in current release. 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: Software management. This chapter permits to update the NE by means download procedure and to manage NE software.
5 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION 5.1 Products, product-releases, versions and Customer Documentation
A product is defined by the network hierarchical level where it can be inserted and by the whole of performance and services for which it is meant. A product evolves through successive product-releases which are the real products marketed for their delivery at a certain product-release availability date. So, a productrelease defines a set of hardware components and a software package which, as a whole, identify the possible network applications and the equipment performance which the specific product-release has been designed, engineered and marketed for. In some cases a product-release has further development steps, named versions, that are born to improve or add some performance (mainly software) with respect to the previous version, or for bug fixing purposes. A product-release has its own standard Customer Documentation, composed by one or more handbooks. A new version of a product-release may or may not produce a change in the status of the Customer Documentation set, as described in para.5.4 on page 18.
5.2 Handbook supply to Customers

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

Standard Customer Documentation, referred to hereafter, must be always meant as plant-independent. Plant-dependent documentation, if envisaged by the contract, is subjected to commercial criteria as far as contents, formats and supply conditions are concerned (plant-dependent documentation is not described here). Standard hardware and software documentation is meant to give the Customer personnel the possibility and the information necessary for installing, commissioning, operating and maintaining the equipment according to AlcatelTelecom Laboratory design choices. In particular the contents of the handbooks associated to the software applications focus on the explanation of the man-machine interface and of the operating procedures allowed by it. Consequently, no supply to the Customers of design documentation (like software source programs, programming tools, etc.) is envisaged.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
5.4 Handbook Updating

The handbooks associated to the productrelease are listed in para.2 on page 7. Each handbook is identified by: the name of the product-release (and version when the handbook is applicable to the versions starting from it, but not to the previous ones), the handbook name, the handbook P/N, the handbook edition (usually first edition=01), the handbook issue date. The date on the handbook does not refer to the date of print but to the date on which the handbook source file has been completed and released for the production. 5.4.1 Changes introduced in the same product-release (same handbook P/N) The edition and date of issue might change on future handbook versions for the following reasons: only the date changes (pointed out in the Table of Contents) when modifications are made to the editorial system not changing the technical contents of the handbook. the edition, hence the date, is changed because modifications made concern technical contents. In this case: the table in para.1.4 on page 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 Operators Handbooks) are not modified unless the new software version distributed to Customers implies manmachine interface changes or in case of slight modifications not affecting the understanding of the explained procedures. Moreover, should the screen prints included in the handbook contain the product-releases version marking, they are not replaced in the handbooks related to a subsequent version, if the screen contents are unchanged. 5.4.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 erratacorrige sheets is not envisaged). 5.4.3 Changes due to a new product-release A new product-release changes the handbook P/N and the edition starts from 01. In this case the modified parts of the handbook are not listed.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
5.5 Customer documentation supply on CDROM

In the following CDROM means Customer Documentation on CDROM
5.5.1 Contents, creation and production of a CDROM In most cases, a CDROM contains in readonly eletronic format the documentation of one productrelease(version) and for a certain language. In some other cases, the same CDROM can contain the documentation of different productrelease(version)s for a certain language. As a general rule: CDROMs for Network Management products do not contain: the Installation Guides the documentation of system optional features that Customers could not buy from Alcatel together with the main applicative SW.
CDROMs for Network Elements products do not contain: the documentation of system optional features (e.g. System Installation Handbooks related to racks that Customers could not buy from Alcatel together with the main equipment).
A CDROM is obtained collecting various handbooks and documents in .pdf format. Bookmarks and hyperlinks make the navigation easier. No additional information is added to each handbook, so that the documentation present in the CDROMs is exactly the same the Customer would receive on paper. The files processed in this way are added to files/images for managing purpose and a master CDROM is recorded. Suitable checks are made in order to have a virusfree product. After a complete functional check, the CDROM image is electronically transferred to the archive of the Production Department, so that the CDROM can be produced and delivered to Customers.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
5.5.2 Use of the CDROM The CDROM can be used both in PC and Unix WS environments. The CDROM starts automatically with autorun and hyperlinks from the opened Index document permit to visualize the .pdf handbooks Other hyperlinks permit to get, from the Technical handbooks, the specific .pdf setting documents. In order to open the .pdf documents Adobe Acrobat Reader Version 4.0 (minimum) must have been installed on the platform. The CDROM doesnt contain the Adobe Acrobat Reader program. The Customer is in charge of getting and installing it. ReadMe info is present on the CDROM to this purpose. Then the Customer is allowed to read the handbooks on the PC/WS screen, using the navigation and zooming tools included in the tool, and to print selected parts of the documentation through a local printer. 5.5.3 CDROM identification Each CDROM is identified: 1) by the following external identifiers, that are printed both on the booklet and the CDROM upper surface: the name of the productrelease(s) (and version when the CDROM is applicable to the versions starting from it, but not to the previous ones), a writing indicating the language(s), the CDROM P/N (Factory P/N 417.xxx.xxx x and ANV P/N), the CDROM edition (usually first edition=01) and, internally, by the list of the source handbooks and documents (P/Ns and editions) by whose collection and processing the CDROM itself has been created.
2)
5.5.4 CDROM updating The list of source handbook/document P/Nseditions indicated in previous para.5.5.3 point 2 ) , in association with the CDROMs own P/Nedition, is also loaded in the AlcatelInformationSystem as a structured list. Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive system, the AlcatelInformationSystem automatically rises a warning toward the Customer Documentation department, indicating the list of CDROMs that must be updated to include the new editions of these handbooks/documents. This causes the planning and creation of a new edition of the CDROM. Updating of CDROMs always follows, with a certain delay, the updating of the single handbooks composing the collection.
END OF DOCUMENT
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Reading rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 GENERAL DESCRIPTION OF THE CRAFT TERMINAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Alcatel software product and licence delivered to the customer . . . . . . . . . . . . . . . . . . . 2.2.1 Software product and licences description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 Software products and licences list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 Craft Terminal main functionalities in the NE management . . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 Network Element management supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.2 Network Element general configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.3 Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.4 External input and output point management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.5 Diagnosis management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.6 Communication and routing management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.7 Equipment and board management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.8 Port management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.9 Protection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.10 Transmission management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.11 Cross Connection management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.12 Performance monitoring management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.13 Synchronization management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.14 Software management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 ACRONYMS AND ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 GLOSSARY OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 3 3 3 3 3 5 5 6 6 7 8 8 8 8 8 8 9 9 9 9 10 10 10 10 10 11 13
03
001124 validated
02A 000906 01
1AA 00014 0004 (9007) A4 ALICE 04.10
991216 DATE CHANGE NOTE
R.LEONARDUZZI ITAVE C. FAVERO R.LEONARDUZZI ITAVE E.CORRADINI R.LEONARDUZZI ITAVE E.CORRADINI APPRAISAL AUTHORITY
ED
ED
03
SC.2:INTRODUCTION 3AL 78987 AA AA 16 1 / 16
957.130.112 X

Table 1. Software products part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2. Software licence part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
1 INTRODUCTION 1.1 Scope

1.1.1 Document scope The Introduction Manual present the Craft Terminal main functions and provides a general overview of the different functionalities provided by the ELMUSM 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 Operators 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 are surely given in another manual.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
SC.2:INTRODUCTION
3AL 78987 AA AA
16
4 / 16
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 element is possible obtaining a remote Craft Terminal application. The general information of the Craft Terminal are presented in the Basic Craft Terminal Operators Handbook, that the operator have to read before this Handbook. In the Basic Craft Terminal Operators 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 EMLUSM views. This Operators Handbook deals with the EMLUSM views of the Craft Terminal, which directly permit to manage the Network Element. The management main functions of the EMLUSM are inserted at para. 2.3 on page 8. A detailed description of the EMLUSM screens is given in Section Ne Management of this handbook. The list and part numbers of the software products distributed by Alcatel is inserted in para.2.2 on page 6. The Craft Terminal characteristic (computer configuration) are listed in the Basic Craft Terminal Operators Handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
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 CDROM. In this CDROM 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 EMLUSM ). 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 licences 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
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 SWP 1650SMC R 1.1 CDROM
ANV Part Number 3AL 79117 AA
Factory Part Number 415.100.552 C
N.B.
Every Software licence is identified by a denomination and a part number, listed on the following table. Table 2. Software licence part numbers
Name SWLA 1650SMC Rel. 1.1 LICENCE FEE SWLB 1650SMC Rel. 1.1 LICENCE FEE SWLC 1650SMC Rel. 1.1 LICENCE FEE SWLLCT 1650SMC Rel. 1.1 LICENCE FEE SWLRCT 1650SMC Rel 1.1 LICENCE FEE N.B. 1
ANV Part Number 3AL 78890 AA 3AL 78891 AA 3AL 78892 AA 3AL 78951 AA 3AL 78952 AA
Factory Part Number 700.200.150 T 700.200.151 Q 700.200.152 R 700.200.159 Y 700.200.160 V
N.B. 1 1 1 2 2
Licence alternative for Network Element software features: SWLA: full functionality set SWLB: improved functionality set SWLC: basic functionality set Licence alternative for Craft Terminal software features: SWLLCT: local Craft Terminal functionality SWLRCT: remote Craft Terminal functionality
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
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 EMLUSM. 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. 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 resynchronization. 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
1AA 00014 0004 (9007) A4 ALICE 04.10
Abnormal Condition list ( as result of operators commands) Event log Manager Permits to have access to the Event Log file. Remote Inventory (upload and view remote inventory)
ED
03
957.130.112 X
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
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). 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
Port view is also the entry point of other management functions : Performance Monitoring management Cross Connection management
For each port are presented: the various ITUT 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:
1AA 00014 0004 (9007) A4 ALICE 04.10
Equipment protection switching Multiple Section Protection (Not operative in current release)
ED
03
957.130.112 X
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). It supply an overview of the complete signal flow. For all the ports are presented: the various ITUT 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 ITUT 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 configuration Protection commands
2.3.14 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. Backup and restore on the MIB of the NE.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
3 ACRONYMS AND ABBREVIATIONS

AIS: Alarm Indication Signal
APS: Automatic Protection Switching ASAP: Alarm Severity Assignment Profile CDROM: Compact Disc Read Only Memory CCITT: Telegraph and Telephone International Consultative Committee CT: Craft Terminal DCN: Data Communications Network 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
1AA 00014 0004 (9007) A4 ALICE 04.10
NML: Network Management Layer NTP: Network Time Protocol
ED
03
957.130.112 X
OS: Operation System PI: Physical Interface SD: Signal Degrade SF: Signal Failure TMN: Telecommunications Management Network TN: Telecommunications Network TP: Termination Point USM: User Service Manager XC: CrossConnection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
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. Crossconnection CrossConnections 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 them.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
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 109 bits every second. Gateway Network Element: It is a Network Element devoted to the control, from the OS, of those NEs providing a QECC* interface. 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 ITUT (International Telecommunication Union). Kilobits per second: Unit that correspond to the transmission of 103 bits every second. Line Terminal: A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can undertake signal conversion functions (adapting a signal to two different transmission media) or multiplexing/demultiplexing functions. Logs: Logs are files used to store history data concerning the incoming notifications, operator commands and system alarms. The size of the log can be configured. 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 106 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: In general, represents the section containing the multiplexed signals.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
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 enduser 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 an equipment. Is related to a port. Thresholding: This is the assignment of a specified value to monitored parameters ( for example BIt Error Rates) that, when exceeded, generate trouble indications. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
03
957.130.112 X
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.2 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 GENERAL INTRODUCTION ON VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 EMLUSM view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Introduction on the EMLUSM menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 Views menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 Configuration menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.3 Diagnosis menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.4 Supervision menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.5 Download menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.6 Equipment menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.7 Board menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.8 Port menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.9 EPS menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.10 Transmission menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.11 Synchronization menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.12 External Points menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 Advices on Navigation principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 NE MANAGEMENT SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 NE management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 NE supervision and login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 NE MANAGEMENT GENERAL CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Access state (allow or inhibit NE Craft access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1 Switching from the OS to the Craft Terminal access state . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.2 Switching from the Craft Terminal access state back to the OS access state . . . . . . . . 4.2 NE Time management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 04 03 01 030521 001124 991216 DATE CHANGE NOTE S.MAGGIOJ.MIR ITAVE C. FAVERO R.LEONARDUZZI ITAVE C. FAVERO R.LEONARDUZZI ITAVE E.CORRADINI APPRAISAL AUTHORITY 6 11 11 11 11 11 11 11 13 13 15 17 18 19 20 20 21 21 22 23 24 26 26 30 33 33 34 35 35 35 36 37
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
ED
04
SC.3:NE MANAGEMENT 3AL 78987 AA AA 268 1 / 268
957.130.112 X
5 SECURITY MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Set Manager list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Set ACD level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 EXTERNAL INPUT AND OUTPUT POINTS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 Displaying external points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1.1 Expanding or reducing external points list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 External points configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 DIAGNOSIS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 Alarms surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3 Event Log Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.1 Upload remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.2 View Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 COMMUNICATION AND ROUTING MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1 Overview on Communication and Routing Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1 Partitioning into Routing Subdomains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2 Partitioning into separate Routing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2 Communication and routing views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4 OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5 NTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6 LAPD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8 Reachable Address Prefixes Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9 Manual ES Adjacencies table Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 EQUIPMENT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 Introduction and navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2 Set and change or remove board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3 Board administrative state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.1 Setting a board in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.2 Setting a board out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.3 Consulting a Boards Administrative state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4 Software description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.5 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.6 Show supporting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 BOARD VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 Board View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2.1 Port Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2.2 Show Supporting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 PORT VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47 47 48 49 50 52 53 55 55 57 59 60 60 61 63 63 63 64 66 67 69 70 71 72 74 75 77 77 81 84 84 84 84 85 86 88 89 89 91 92 93 95
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
4.3 Alarm Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1 Procedure to modify an ASAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2 Alarm Severity Assignment Profile Management (ASAP) . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.3 Allow/Inhibit Alarms Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.4 Alarms resynchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4 Restart NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39 39 39 44 45 46
11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Port View: elements on the TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 Port View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4 AU4 Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5 Physical Media option menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5.1 Automatic Laser Shutdown Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5.2 Show Optical Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5.3 Single Fiber Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5.4 Ms Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5.5 PDH Line Length Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6 Show Supporting Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.7 Navigate to Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 EQUIPMENT PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Management: consulting and modifying EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3 Configuration: revertive and WTR for EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4 Switching EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 MULTIPLEX SECTION PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 TRANSMISSION VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2 View elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3 View Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.1 View Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.2 Number of TPs Displayed in Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.3 Naming TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.4 Dynamic View Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.4 Transmission view access and menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5 Add TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5.1 TP Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6 TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.1 High Order TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.2 Low Order TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.7 PDH TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.8 TP Threshold Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.9 Alarm Persistency Time Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.10 Terminate/Disterminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.10.1 Terminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.10.2 Disterminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.11 POM/SUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.11.1 Creation/Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.11.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.12 Structure TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.13 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.13.1 Loopback Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.13.2 Loopback Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.14 Physical Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.14.1 Set Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.15 Navigation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.15.1 Expand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.15.2 Hide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.15.3 Show Supported Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
95 97 98 99 101 102 105 106 108 109 110 111 113 113 114 119 121 123 125 125 126 127 127 128 128 128 129 131 131 138 138 140 142 143 144 145 145 145 146 147 149 151 152 152 155 157 158 159 159 160 161
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.15.4 Navigate to Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 CROSS-CONNECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.2 Multiplex Structures for SDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.3 Definition of Termination Points (TP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.4 Cross-Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.5 Cross-Connection Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2 Operative Sequence to execute Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3 Cross-Connections management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.1 Search Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.2 Cross-Connection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.3 Actions available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4 Create/Modify Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.1 Cross-Connection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.2 Create a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.3 Modify a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.5 Activate/Deactivate/Delete Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.5.1 Activate a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.5.2 Deactivate a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.5.3 Delete a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.6 Split and Join Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.6.1 Split a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.6.2 Join Two Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.7 Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.8 Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.9 Port Switch Over . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.10 Show Cross-Connected TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 OVERHEAD MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2 OH Connection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.3 Overhead views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.4 OH Cross Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.5 OH TP creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.6 OH TP deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.7 OH Phone Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.2 Supported Performance Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.3 Far End Performance Counting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.4 Granularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.5 Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.6 Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.3 Display Current Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.4 Display History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.5 PM Threshold Table Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.6 PM Threshold Table Creation / Modification / Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.6.1 Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.6.2 Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
162 163 163 163 164 167 171 173 175 177 179 181 183 184 185 190 196 199 199 199 199 200 200 202 203 205 206 207 209 209 210 211 212 217 218 219 221 221 221 222 223 224 224 225 226 229 231 233 236 236 238
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
17.6.3 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 SYNCHRONIZATION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2 Synchronization Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.1 Displaying the Synchronization View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.2 Synchronization View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.3 Timing Source Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.4 Synchronization Protection Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.5 Synchronization Configuration for T0/T4 and T4 squelch criteria . . . . . . . . . . . . . . . . . . 18.2.6 SSU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.7 Remove Timing Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.8 Set and Remove T0 Equal T4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.9 Transmission of SSM Quality Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.10 Show Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 SOFTWARE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.1 Generalities and descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.1.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.2 Software download operative sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.2.1 Software Download upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.2.2 NE Software package installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.3 Software Download Manager menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.4 Init download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.5 SW package Activation and Units information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.6 Mib management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
238 241 241 243 243 244 247 250 251 253 254 255 256 257 259 259 260 261 261 262 263 264 266 268
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X

FIGURES Figure 1. EMLUSM main view organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2. Menu options flow chart 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3. Menu options flow chart 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4. Menu options flow chart 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5. NE EMLUSM Main view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6. NE management: setting the access state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7. Consulting and/or setting the local NE time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 8. NE Time dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 9. Configuring Alarm Severity Assignment Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 10. ASAPs Management dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 11. ASAP Edition dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 12. Set ASAP dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 13. Inhibit alarm notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 14. Allow alarm notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 15. Alarm resynchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 16. Restart NE confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 17. Set Manager list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 18. Set ACD level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 19. Opening the external points view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 20. External points view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 21. Expanding or reducing the external points list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 22. Configuring external points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 23. External input point configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 24. External output point configuration dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 25. Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 26. Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 27. Abnormal condition menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 28. Example of abnormal condition list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 29. Example of loopback dialog window management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 30. Event log option in Network Element context view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 31. Remote Inventory confirmation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 32. Remote Inventory completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 33. View Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 34. Routing subdomain organization example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 35. Comm/Routing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 36. Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 37. OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 38. NTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 39. LAPD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 40. Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 41. Ethernet Configuration L2 only parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 42. RAP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 43. MESA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 44. Equipment Overview Subracks level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 45. Equipment Overview Rack level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 46. Equipment Overview NE level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 47. Equipment menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 48. The list of different boards relative to an NE slot (examples) . . . . . . . . . . . . . . . . . . . . . . . Figure 49. Consulting a boards administrative state. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 50. Software Description dialogue box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10
14 27 28 29 34 35 37 37 40 40 42 43 44 44 45 46 47 48 50 51 52 53 53 54 55 56 57 57 58 59 60 60 61 65 66 68 69 70 71 72 73 74 75 78 78 79 79 81 84 85
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 51. Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 52. Select Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 53. Select Output Format for file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 54. Equipment Overview Subrack level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 55. Equipment view: select the SDH port on a board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 56. Example of a Board View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 57. Example of a SDH Port identification and alarm synthesis . . . . . . . . . . . . . . . . . . . . . . . . . Figure 58. Board menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 59. After Port Access selection (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 60. Subrack level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 61. Example of a Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 62. Termination TP box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 63. G.783 Adaptation TP box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 64. Port menu options (SDH and PDH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 65. AU4 concatenate/deconcatenate commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 66. Example of a concatenated AU4 transmission view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 67. Example of a concatenated AU4c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 68. Physical media menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 69. Automatic Laser Shutdown management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 70. Automatic Laser Shutdown Management (after ALS Function delete) . . . . . . . . . . . . . . . Figure 71. ALS and Laser current state (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 72. Visualizing a port optical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 73. Bidirectional Transmission on a single fiber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 74. Single Fiber Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 75. Ms Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 76. PDH Line Length Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 77. Board View Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 78. After Navigate to Transmission view selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 79. Consulting EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 80. EPS Management dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 81. EPS: board selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 82. EPS: choose protected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 83. EPS functional state from protected active board view . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 84. EPS functional state from protecting active board view . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 85. Configure EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 86. EPS Management dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 87. Switching EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 88. EPS Switch dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 89. Symbols Used in Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 90. Transmission View Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 91. Transmission menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 92. TP Search Dialog, Initial State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 93. Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 94. TP Search Dialog with Various TP Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 95. TP Search Dialog with Status Information Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 96. Symbols in TP Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 97. Board History Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 98. TP Search Dialog with Different Filtering Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 99. Information... Dialog for Search Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 100. Print to Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 101. Print to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 102. Example Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 103. High Order TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 104. Low Order TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86 87 87 88 89 90 90 91 92 93 96 97 97 98 99 100 100 101 102 103 104 105 106 107 108 109 110 111 114 114 117 117 118 118 119 119 121 121 126 127 130 131 131 132 133 133 134 135 135 136 136 137 138 140
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 105. PDH Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 106. Degraded Signal Threshold selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 107. POM/SUT Creation/Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 108. Display of POM/SUT in Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 109. POM/SUT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 110. Loopback configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 111. Port Loopbacks View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 112. Loopback Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 113. Set Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 114. Board View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 115. Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 116. SDH Multiplex Structure according to ITU-T G.709 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 117. Frame Construction within the Synchronous Digital Hierarchy . . . . . . . . . . . . . . . . . . . . Figure 118. SDH Transport Level Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 119. PDH Transport Level Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 120. Unidirectional Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 121. Bidirectional Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 122. Example of Broadcast Connection with Three Legs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 123. Protected Unidirectional Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 124. Bidirectional Connection Input Protected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 125. Protected Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 126. Drop and Continue Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 127. Cross-Connection Management Dialog (Initial State) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 128. Cross-Connection Management Dialog (After Search) . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 129. Protection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 130. Cross-Connection Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 131. Creation of a Unidirectional, Non-Protected Cross-Connection . . . . . . . . . . . . . . . . . . . . Figure 132. Create a Bidirectional Protected Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 133. Search for Cross-Connection Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 134. Create an Unprotected Broadcast Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 135. Create a Protected Broadcast Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 136. Unprotect a Unidirectional Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 137. Protect one Leg of a Broadcast Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 138. Split/Join Unprotected Bidirectional Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 139. Split/Join to Protected Bidirectional Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 140. Protection Actions Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 142. Select Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 143. Select Output Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 144. Show Cross Connected VC4 of an AU4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 145. Overhead options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 146. Cross Connection Management for OverHead dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 147. Main Cross-Connection for OverHead dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 148. OH TP creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 149. OH Search TP for creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 150. OH TP deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 151. Phone Parameters dialog window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 152. Far End Performance Monitoring Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 153. PM Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 154. Current PM Data Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 155. PM History Data Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 156. PM Threshold Table Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 157. Create PM Threshold Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 158. Modify PM Threshold Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 159. Internal organization of the SETS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
142 143 147 148 149 152 154 155 158 161 162 165 166 169 170 171 171 172 173 173 174 174 180 182 186 189 189 191 193 194 195 197 198 200 201 203 205 205 208 211 212 212 217 217 218 219 223 227 230 232 234 237 239 241
ED
04
957.130.112 X
Figure 160. Obtaining the synchronization view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 161. Synchronization View Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 162. Synchronization Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 163. Timing source configuration for crossconnect equipments . . . . . . . . . . . . . . . . . . . . . . Figure 164. Synch. source configuration for ADM equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 165. Lockout, Force and Manual commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 166. Configuring the T4 SSM algorithm and the squelch criteria . . . . . . . . . . . . . . . . . . . . . . . Figure 167. SSU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 168. Synchronization source removing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 169. Synchronization source removing confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 170. T4 equal T0 setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 171. Transmission SSM Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 172. Timing Source Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 173. Software Download general principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 174. Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 175. Download menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 176. SW Downloading dialogue box example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 177. Software download in progress (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 178. Software Package Information dialogue box (example) . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 179. Detail software package (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 180. NE MIB management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLES Table 1. Optional and Mandatory Configurable Parameters for Cross-Connection Creation . . . . . . Table 2. Modifiable Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3. Threshold table entities association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4. Maximum Performance Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
243 244 247 248 249 250 252 253 254 254 255 256 257 259 263 263 264 265 266 267 268
187 196 235 238
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
10 / 268

1.1.1 Document 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. 1.1.2 Target audience This document is intended for the operators whose role is to manage the Network Elements. The documents that should be read before starting this document are: 1320CT Basic Operators 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 Refer to the Section Introduction manual.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
12 / 268
2 GENERAL INTRODUCTION ON VIEWS AND MENUS

In this chapter the organization of the EMLUSM screen, presented after the NE login, is described.
First is introduced the view organization, than the accessible menu options are listed. At the end some further advice are given for Navigation principles.
2.1 EMLUSM view organization

The EMLUSM view (see Figure 1. ) is the first window presented to the operator after the login. It contains the following fields, that provide you with information needed to manage the NE: Severity alarm synthesis, Domain alarm synthesis, Management status control panel View title, View area Message/state area
The Menu bar and the View area contained in the same NE view permits to performs 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 are: Synchronization, External Point, Equipment, Transmission.
Information about the alarms and status is given in the Maintenance section of this handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Severity alarms synthesis Menu bar
Domain alarm synthesis

View title
View area
Message/state area
Management states control panel
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 1. EMLUSM main view organization.
ED
04
957.130.112 X
2.2 Introduction on the EMLUSM menu options

The menu bar allows to perform configuration and supervision functions on the Network Element.
This paragraph list all the menu options and then more details on the relevant contained entries. For each of them the relevant operative function are briefly introduced and it is referred the paragraphs where it is detailed or the introduction to the options of each menu inserted in next paragraphs of this chapter. The flow charts of Figure 2. on page 27, Figure 3. on page 28 and Figure 4. on page 29 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). See para.2.2.1 on page 17.
To navigate among the views and set TMN and OverHead parameters. Configuration (second column). See para.2.2.2 on page 18.
To set general configuration of the NE, set TMN and OverHead parameters and to show or modify some parameters (performance monitoring, crossconnection). Diagnosis (third column). See para.2.2.3 on page 19.
To get information about the NE (alarms, performance monitoring, remote inventory). Supervision (fourth column). See para.2.2.4 on page 20.
To set the supervision states (i.e. Craft Terminal enabling). Download (fifth column). See chapter 19 on page 259.
To manage the NE software (download, MIB management). Help To activate the help. (last column).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 (seventh column). See chapter 9 on page 77
To manage the NE as a whole, setting the boards which compose it. From the Equipment view the Board view can be accessed. Board (seventh column). See chapter 10 on page 89.
To show the physical port available in a specific board. It is the entry point for the Port view. Transmission (sixth column). See chapter 14 on page 125.
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. Port (sixth column). See chapter 11 on page 95.
To set and show (detailed alarm view) the transmission resources referred to the Port. EPS (sixth column). See chapter 12 on page 113.
To manage the EPS protection, setting the relevant configuration. Synchronization (sixth column). See chapter 18 on page 241.
To show and modify synchronization parameters. External Points (sixth column). See chapter 6 on page 49.
To show and modify housekeeping (environmental) alarms.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
2.2.1 Views menu introduction This menu permits to navigate among the views and set some parameters, by means of the following entries: Previous: Equipment: Go back to the previous view. Open the Equipment view. See chapter 9 on page 77. The Equipment menu and theEPS menu are then available on the menu bar. Open the External Point view. See chapter 6 on page 49. The External Point menu is then available on the menu bar. Open the Transmission view. See chapter 14 on page 125. The Transmission menu is then available on the menu bar. Open the Synchronization view. See chapter 18 on page 241. The Synchronization menu is then available on the menu bar.
External Points:
Transmission:
Synchronization:
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. Navigate and show the contents of the selected object. The current view doesnt change but a new window with a new view is opened. Close the EMLUSM view, without stopping the supervision of the NE
Open in Window:
Close:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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. See para. 4.3.2.1 on page 39. Send the Alarm Severity Assignment Profile to the selected object See para. 4.3.2.2 on page 43. Send the Alarm Severity Assignment Profile referred to the equipment level. See para. 4.3.2.2 on page 43.
Set Alarm severities:
Set SdhNe Alarm severities:
NE Time: Performance:
Display and set the NE local time. See para. 4.2 on page 37. Manage the the Performance Monitoring domain. Used to define the PM parameters, opening the following menu options: Threshold table: See para.17.5 on page. 233. See para.5.2 on page 48. Not operative Manage the connection of the paths. See para.15.3 on page 177
Set ACD level:
Cross Connection Management:
Loopback Management: Enter the loopback management. See para. 14.13 on page 152. Used to configure the loopback command for commissioning or maintenance purposes. Comm/Routing: Enter the Communication and Routing management. See para. 8 on page 63. Used to define the parameters for NE and OS in the TMN, opening the following menu options: Local configuration OS Configuration NTP Server Configuration LAPD Configuration Ethernet Configuration RAP Configuration MESA Configuration Handle the operation on the Overhead bytes. See para.16 on page 209. Used to define the parameters in the following menu options: OH Cross Connection OH Phone Parameter OH TP creation OH TP deleting
Overhead:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
2.2.3 Diagnosis menu introduction This menu permits to get information about the NE, by means of the following entries:
Alarms:
Performance data: Event log:
Display the Alarms Surveillance information of the NE. See para. 7.1 on page 55. It opens the following menu options: NE alarms Object alarms Subtree alarms Equipment alarms Transmission alarms External Points alarms Not operative It opens the following menu options: 15 Minutes 24 Hours Manage the events stored in the NE. See para. 7.3 on page 59 It opens the following menu options: logld1 logld2
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. See para 7.4.2 on page 61. 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. See para 7.2 on page 57.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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. See para.4.1 on page 35. It opens the following menu options: OS Requested Manage the alarms supervision of the NE. It opens the following menu options: Resynchronize. See para. 4.3.4 on page 45. Allow / Inhibits Notifs. See para. 4.3.3 on page 44.
Alarms:
Upload Remote Inventory:Store the Remote Inventory data in the Craft Terminal. See para. 7.4.1 on page 60. Set Manager list: Restart NE: See para.5.1 on page 47. Not operative Reset the NE software. See para.4.4 on page 46.
2.2.5 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. See para.19.4 on page 264. Show the status of the software package installed in the NE memory banks. See para.19.5 on page 266.
Units info:
Mib management: Permits backup of NE software configuration and restore of backupped file. See para. 19.6 on page 268.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
2.2.6 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: Set: Add or change the board type (a list is proposed). See para. 9.2 on page 81. 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) See para. 9.2 on page 81. Remove the board. See para. 9.2 on page 81. Insert a lock symbol in the board. See para. 9.3.1 on page 84. Delete the lock symbol in the board, enabling changes. See para. 9.3.2 on page 84. Not operative. Show information on the software of the board. See para. 9.4 on page 85. Show the Remote Inventory data inserted in the equipment. See para. 9.5 on page 86. It opens the following menu options: Subrack level Board level
Modify:
Remove:
Set in service: Set out of service
Reset: Software description: Remote Inventory:
Show supporting equipment: Navigate to the upper equipment level. See para. 9.6 on page 88.
2.2.7 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. See para.11.7 on page 111.
Show supporting equipment: Navigate to the upper subrack level. See para.11.6 on page 110.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
2.2.8 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). 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. It permits navigation to the Transmission view. TP configuration: Set parameters for the Overhead (Signal Label and Path Trace) on Synchronous TPs. See para 14.6 on page 138. Set B2 excessive BER and Signal Degraded parameter. See para 14.8 on page 143.
TP Threshold Configuration:
PDH TP configuration:
Set parameters for the Plesiochronous TPs to use it as a timing reference. Only for PDH ports views. See para 14.7 on page 142. Only for SDH ports views. See para. 11.4 on page 99. Manage the connection of the paths. See para.15 on page 163. It opens the following menu options: Cross Connection Management Create Cross Connection Modify Cross Connection
AU4 Concatenation: Cross Connection:
POM / SUT configuration: Set parameters for POM/SUT TPs. See para. 14.11 on page 146. Not available for PDH port. It opens the following menu options: Creation / Deletion Configuration Show TP performance data: not operative. Not available for HOA port. It opens the following menu options: 15 minutes 24 hours Performance: Set and show Performance Monitoring parameters and data. See chapter 17 on page 221. It opens the following menu options: Configure Monitoring Display Current Data Display History Data
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Loopback:
MSP Physical Media:
Enter the loopback management. See para. 14.13 on page 152. Used to configure the loopback command for commissioning or maintenance purposes: Port Loopback Configuration Loopback management Manage the Multiplex Section Protection of the NE. (Not operative) Manage the physical setting of the TP of the ports. Not applicable to HOA port. See para.11.5 on page 101. It opens a menu which 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 NT G703/704 Configuration NT X21 Configuration
Show supporting board: Navigate to the upper board level. See para.11.6 on page 110. Navigate to Transmission view: permit to show a complete overview about the signal flow, opening all TPs See para.11.7 on page 111
2.2.9 EPS menu introduction This menu permits to manage the EPS protection, setting the relevant configuration, by means of the following entries : Management: Configure: Switch: Set EPS protections. See para.12.2 on page 114. Set revertive / not revertive and WTR parameters. See para. 12.3 on page 119. Manage the EPS operator commands (Force, Manual, Lockout) See para.12.4 on page 121.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
2.2.10 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. See para.14.5 on page 131. Display the TPs related to a selected TP. See para.14.15.1 on page 159. It opens the following menu options: Next level of lower TP All lower TP Next level of upper TP All upper TP Remove the TP from the screen of the Transmission view. See para.14.15.2 on page 160. It opens the following menu options: Lower TP Upper TP Selected TP Set parameters for the Signal Label and Path trace. See para.14.6 on page 138. Set parameters for the Plesiochronous TPs to use it as timing reference. Only for PDH ports views. See para.14.7 on page 142.
Expand:
Hide:
TP configuration:
PDH TP configuration:
TP Threshold configuration: Set B2 Ex BER and Signal Degrade threshold. See para. 14.8 on page 143. Alarm Persistency Time To suppress oscillating alarms. See para.14.9 on page 144. Terminate TP: Disterminate TP: Cross Connection: Terminate the AU4CTP paths. See para.14.10 on page 145. Disterminate the AU4CTP paths. See para.14.10 on page 145 Manage the connection of the paths. See para.15 on page 163. It opens the following menu options: Cross Connection Management Create Cross Connection Modify Cross Connection Port Switch Over Show Cross Connected TPs
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
POM / SUT configuration: Add or change the board type (a list is proposed). See para.14.11 on page 146 It opens the following menu options: Creation / deletion Configuration Performance: Set and show Performance Monitoring parameters and data. See chapter 17 on page 221. It opens the following menu options: Configure Monitoring Display Current Data Display History Data Define the structure of a selected TP (TU2, TU3, TU12, VC3/VC4, VC12) See para.14.12 on page 151. : Enter the loopback management. See para. 14.13 on page 152. Used to configure the loopback command for commissioning or maintenance purposes: It opens the following menu options: Port Loopback Configuration Loopback management Manage the TP physical setting. See para.14.14 on page 157. It opens the following menu options: ALS Management Show Optical Configuration TX Quality Configuration Single Fiber Configuration Extra traffic Regeneration Section management Line Length Configuration Set Domain HDSL Configuration NT Configuration X21 Configuration Manage the Multiplex Section Protection of the NE. (Not operative in current release) It opens the following menu options: MSP Management MSP Commands NE MSP synthesis Navigate to the board supporting the selected TP See para.14.15.3 on page 161. Navigate to the port supporting the selected TP See para.14.15.4 on page 162.
Structure TPs:
Loopback
Physical Media: MSP
Show supported board:
Navigate to Port view:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
2.2.11 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. See para.18.2.3 on page 247. Protection Command: Manage commands (force, manual, lockout) for the selected timing reference. See para.18.2.4 on page 250. Enable/disable SSM and WTR on the T0 synchronization source. See para.18.2.5 on page 251. Enable/disable SSM, WTR and Squelch Criteria on the T4 synchronization source. See para.18.2.5 on page 251. Not used. Set NE single or with SSU. See para.18.2.6 on page 253. See para.18.2.7 on page 254. See para.18.2.8 on page 255. See para.18.2.8 on page 255.
T0 Configuration:
T4 Configuration:
T0 TEST Configuration: SSU Configuration: Remove Timing Reference Set T0 Equal T4 Remove T0 Equal T4
Transmitted SSM Quality Configuration: Set SSM quality transmitted on the selected T1 SDH timing reference. See para.18.2.9 on page 256.
Show Timing Source: Show the port view related to the selected timing reference. See para.18.2.10 on page 257.
2.2.12 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. See para. 6.2 on page 53. Show the list of the input/output environmental alarm. See para. 6.1 on page 50. It opens the following menu options: Show external Input Points Show external Output Points Show all external Points
Display:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED

Configuration Supervision Diagnosis
Views
Download
04
Alarm Severities Alarms Access State A E Set Alarm Severities OS NE alarms Requested B Object alarms NE Time Alarms Subtree alarms Set SdhNe Alarm Severities
Previous
Init download
957.130.112 X
Equipment
Units info
External Points
Transmission Performance Equipment alarms
SC.3:NE MANAGEMENT
C D Threshold table Transmission alarms Resynchronize Allow Notifs
Mib Management
Synchronization
Open Object Set ACD level External Points alarms
Open in Window Cross Connection Management Loopback Management Performance data
Inhibit Notifs
Close
Upload Remote Inventory Set Manager list
15 Minutes
Figure 2. Menu options flow chart 1

Comm/Routing
Local Configuration

24 Hours
OS Configuration
Overhead
Restart NE Event log
3AL 78987 AA AA
OH Cross Connection Oh Phone Parameters logld 1 OH TP Creation logld 2 OH TP Deleting
268
NTP Server Configuration
LAPD Configuration
Note: A.....F See next figures
Ethernet Configuration
RAP Configuration
View Remote Inventory
27 / 268
MESA Configuration
Abnormal Condition List
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
G F C

Board
All Lower TPs nb1: only for PDH port nb2: only for SDH port Add TP Expand Hide TP configuration PDH TP config. TP Threshold Configuration Alarm Persistency Time Terminate TP Disterninate TP Cross Connection ALS Management Next Level of Upper TPs

Port
Note: A.....F See previous figure
Equipment
Port Access Show supporting equipment TP Thresholds configuration F TP configuration
Transmission
Next Level of Lower TPs
04
PDH TP nb1 configuration Lower TPs Show Optical Configuration Upper TPs AU4 nb2 Concatenation Cross Connection TX Quality Configuration Selected TPs Cross Connection Management Single Fiber Configuration Extra traffic Create Cross Connections Create Cross Connection Regeneration Section manage Modify Cross Connections Configure Monitoring Modify Cross Connection Line Lenght Configuration Display Current Data POM / SUT nb2 Set Domain POM / SUT config. Display History Data Creation / deletion Configuration HDSL Configuration Creation / Deletion Configure Monitoring Configuration
Set
Modify
All Upper TPs
957.130.112 X
Remove
Set in service
Set out of service
Reset
SC.3:NE MANAGEMENT
Software description
Cross Connection Management
Remote Inventory
Subrack level
Board level
Port Switch Over
Show supporting equipment
Show Cross Connected TPs
with SDH port

Port Loopback Configuration Show TP performance data NT Configuration Performance Structure TPs Loopback MSP Management MSP commands MSP Commands Loopback management 15 minutes X21 Configuration 24 hours Performance
Display Current Data
ALS Management
Display History Data
Show Optical Configuration
TU2
3AL 78987 AA AA
Loopback with PDH port Line Lenght Configuration MSP HDSL Configuration Physical Media: NT G703/G704 Configuration Show supporting board NT X21 Configuration C Navigate to Transmission view
268
Tx Quality Configuration
TU3 TU12 Physical Media: NE MSP synthesis MSP Show Supported Boards F Navigate to Port View VC3/VC4 VC12
Single Fiber Configuration
LAPD config.
Ms Configuration
Port Loopback Configuration

Loopback management
28 / 268
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
E D B
04

Eps Synchronization External Points
Management Timing Source Configuration Display Protection Command T0 Configuration T4 Configuration T0 TEST Configuration SSU Config. Remove Timing Reference Set T0 Equal T4 Remove T0 Equal T4 Transmitted SSM Quality Configuration Show Timing Source Show All External Points Show External Output Points Configure Configuration
957.130.112 X
SC.3:NE MANAGEMENT
Switch Show External Input Points
Note: A.....F See previous figures
3AL 78987 AA AA
268
29 / 268
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: 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 toboard view or to transmission view) thus facilitating the operators activity.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Views Navigation The first level of the Equipment view representation will be displayed directly into the current window, immediately after the NE login. (See Figure 1. on page 14). 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. The navigation through different levels of the NE hierarchy is performed by double clicking on the objects: (see also para 9.1, pg. 77) the first level shows the subrack level of the Equipment view (see Figure 1. on page 14); by double clicking on a board body, the board level of the Equipment view can be reached. further, by double clicking on a port body contained in the board, the port level of the Equipment view can be reached. The port view displays the inner TPs. it is possible to go back to the upper level of representation by pressing the <ESC> key on the keyboard; or to go back to the previous view, by selecting the Previous option from the Views menu. Selecting in the first level of the Equipment view ( subrack level, Figure 1. on page 14 ) 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.
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
32 / 268
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 are presented. Management states are present at Network Element Synthesis view level and at USMEML view level. All the information referred to the management states are inserted in the Basic Craft Terminal Operators 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
3.2 NE supervision and login

The Network Element Synthesis views enable you to get access to the current NE EMLUSM 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 Operators Handbook. The EMLUSM Main view is presented as for the following figure.
Figure 5. NE EMLUSM Main view.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 NE can be managed by the OS or by the Craft Terminal. 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 6. 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 doesnt 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 cascading menu in Figure 6. From the confirmation dialogue box that opens you can confirm or cancel the OS access operation. The NE is now managed by the OS. N.B. The key symbol icon on the management states of the NE view, indicates whether the NE is managed by a craft terminal or by the OS. 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).
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
4.2 NE Time management

The NE local time of a selected NE can be visualized and/or realigned 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 7. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 8. NE Time dialogue box.
ED
04
957.130.112 X
The following fields are available: NTP Status section (read only) with the following parameters: NTP protocol It can be enabled (in the NTP Server Configuration option at para 8.5 on page 70) or disabled or empty (greyed). NTP Main and NTP Spare It displays the status of the Main and Spare NTP: reachable or unreachable.
Time section with the following data: NE Time 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 In this case, the NTP Main and NTP Spare are empty (greyed); the Set NE Time With OS Time message is operative and the user can set manually the NE Time (i.e. change the NE time with the Time of the Craft Terminal).
If you do not want to set the NE local time, click on the Close push button to close the dialogue box. To realign 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 which corresponds to the legal GMT time. N.B. When the NTP is not present, the OS system realigns 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 resynchronization.
4.3.1 Procedure to modify an ASAP a) b) c) d) e) f) g) h) i) j) k) Select the TP (or the board/port/etc...) whose ASAP is to be changed from the menu click on Configuration > Alarms Severities... (see Figure 10. on page 40 ) select one of the user profiles (#10001 or #10002) and click on Modify (see Figure 11. on page 42) click on the Probable Cause Families associated to the alarm select the relevant alarm in the list of Probable Cause Name in the Service affecting/non affecting fields select the needed severity (critical/major/minor...) click on OK (see Figure 10. on page 40) click on Close select the relevant TP and then Configuration > Set Alarms Severities... in the box that appears select the just modified ASAP (eventually check it by means of Detail ) click on OK For further details see paragraphs 4.3.2, 4.3.2.1, 4.3.2.2.
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. Select the Alarm Severities... option from the Configuration pull down menu.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 9. Configuring Alarm Severity Assignment Profile. The ASAP Management dialogue box is displayed.
Figure 10. ASAPs Management dialogue box.

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
The default presented profiles are:

Profile 1 No alarm : all the alarms are disabled (not alarmed). Profile 2 is fixed and shows the alarm criterion configuration defined for primary alarms. With this profile the following alarms are disabled: AIS Battery Degraded FERF SSF SFWR Download failure
Profile 3 is fixed and shows the alarm criterion configuration defined for path alarms. With this profile the following alarms are disabled: AIS FERF SFWR Download failure
Profile 4 is fixed and shows the alarm criterion configuration defined for all alarms. With this profile the following alarms are disabled: SFWR Download failure
Profile 10001 can be set by the user. 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 and SFWR Download Failure are not alarmed). NOTE: if this profile is not already present in the list, it is necessary to create it, by using the dialog of Figure 10. , selecting one existing profile and then clicking on the Clone button. Profile 0 is not used.
You can select an ASAP. For ASAP 10001 it is then possible to choose Detail, Modify, Clone or Delete buttons. For ASAP 1 to 4 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 11. ASAP Edition dialogue box. The alarm severity assignment profile dialogue box displays a list of probable causes and a list of alarm severity. The Probable cause family check buttons allows to filter 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 (dont used, it is not operative). For each the severity can be chosen from Critical, Major, Minor, Warning, Nonalarmed or Not used. A Nonalarm probable cause corresponds to no alarm emitted for this probable cause. When selecting Details the assigned severity are only shown and it isnt 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 (dont consider Profile0) 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. To take into account a profile modification, it is mandatory to perform a resynchronization of the alarms (see para. 4.3.4 on page. 45). During this resynchronization, the severity of each alarm is updated. Otherwise, the severities are updated only when the modified or new alarms are emitted by the NE.
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
4.3.2.2 Set Alarm Severities This option permits to send the ASAP to the previously selected object (rack, subrack, board, port, TP).
It permits also to check the currently operative ASAP used by the object. Only the alarms relative to the selected object will be set. Select the Set Alarm Severities... option from the Configuration pull down menu as for Figure 9. on page 40. Note: the Set Alarm Severities ... option is accessible only if an object has been selected. The Set ASAP dialogue box is displayed (Figure 12. ). The ASAP currently operative on the object is highlighted. To choose an ASAP select a new one of the presented list. It is then possible to choose only Detail button. Click on Detail button, a dialogue box is displayed. The presented alarm severity assignment profile dialogue box displays the list of probable causes and the list of alarm severity. Click on OK to send the selected ASAP to the TP of the selected Board. Note: the change of ASAP configuration must be done one by one, for each single object (for example for each single TP of one board). Selecting the Set SdhNE Alarms Severities option from the Configuration pull down menu only the alarms at Equipment level (FF and ABF) are managed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 12. Set ASAP dialogue box.
ED
04
957.130.112 X
4.3.3 Allow/Inhibit Alarms Notifications The system provides the possibility to allow/inhibit the spontaneous incoming alarm notifications. l) 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 13. Inhibit alarm notification From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok or Cancel push buttons respectively. To inform the operator that alarms have been inhibited, the labels of the alarm panel are greyed out.
N.B.
Inhibiting the alarms notification means that they are not forwarded to the CT but alarms are still generated by the NE.
m ) 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 14. Allow alarm notifications From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok or Cancel push buttons respectively.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
4.3.4 Alarms resynchronization 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 resynchronize 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 15. Alarm resynchronization From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok or Cancel push buttons respectively. N.B. This functionality has to be used only if there is any perturbation. Never use this operation during a correct behavior.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 16. Restart NE confirmation Click on the OK push button to perform the restart NE. Click on the Cancel push button to abort the restart NE.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
5 SECURITY MANAGEMENT
In this chapter are inserted setting options referred to the SECurity management:
5.1 Set Manager list

This function is not Operative. 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 dialogbox 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 manager 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 EMLUSM 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 to select 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 17. Set Manager list
ED
04
957.130.112 X
5.2 Set ACD level

This function is Not Operative. 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. Select the Set ACD level option from the Configuration pull down menu. The dialogbox contains the following fields: 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 EMLUSM 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 EMLUSM.
OK button is used to validate the selection. Close button close the dialog without changes of the data.
Figure 18. Set ACD level
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 are dedicated to check modification of the environment as for example a fire, a flood ... An external output point is used to manage a NE contact (i.e relay) connected to detector. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
6.1 Displaying external points

Select the External Points option from the Views pull down menu as shown in the following figure.
Figure 19. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 20. 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 userfriendly 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 configurated, display the alarm event and the board affected associated to the Output point (see further the paragraph External points configuration). In current release is fixed to Manual.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 21. Expanding or reducing the external points list.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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) change of associated Probable Cause. Only for External Input points (fixed value)
To configure an external point, click on the concerned row of Figure 20. on page 51 and then select the Configuration option from the External Points pull down menu as shown in the following figure.
Figure 22. Configuring external points. The following dialogue box is then opened, displaying information about the selected external point (Input or Output).
Figure 23. External input point configuration dialogue box.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 24. External output point configuration dialogue box. 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 or 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: this field is set to housekeeping and cant 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, in current release, is fixed to Manual. 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 to drain water from the room where the equipment is placed ; in this case is also necessary to set the option On in the field External State .
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
04
957.130.112 X
7 DIAGNOSIS MANAGEMENT
Alarms are always present on the operators 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 operators 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 of this handbook.
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 (see the following figure): 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 25. Alarm Surveillance
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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).
Figure 26. 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 help the operator, typically during troubleshooting operation, presented in next section of this handbook. (Maintenance section, where more details about alarms are given). Detailed description is given in the AS Operators Handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
7.2 Abnormal Condition List

The abnormal condition provides the synthesis of NE not normal conditions listinig the events that contribute to abnormal condition. Select Diagnosis>Abnormal Condition List ( see Figure 27. on page 57). Figure 28. on page 57 is opened.
Figure 27. Abnormal condition menu option
r01sr1sl02/port#01P
Figure 28. Example of abnormal condition list The abnormal condition are the following:
1AA 00014 0004 (9007) A4 ALICE 04.10
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 subboard) is placed in a not configured slot
ED
04
957.130.112 X
Select an abnormal condition and click on OK to open the relative dialog window. Figure 29. on page 58 is opened.
r01sr1sl02/port#01P r01sr1sl02/port#01P
Figure 29. Example of loopback dialog window management The other abnormal condition types will open the corrisponding management window or will open the window to navigate towards the management window.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
7.3 Event Log Manager

From the Network Element context views, perform the following operations to have access to the Event Log file: In the Diagnosis pulldown menu, select the Event log option. The following options are proposed:
Figure 30. Event log option in Network Element context view The proposed option Logld1 and Logld2 Select the Event Log option to access the Event Log file. The Configuration and Log Browsing ELM Windows open, permitting to analyze all events and alarms stored in the NE. Refer to the ELM Operators Handbook
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
7.4 Remote Inventory

This paragraph describes the access to the remote inventory of this NE. In the Remote Inventory are stored information of identification, construction data ect. The options used are: Upload Remote Inventory: store the Remote Inventory data in the 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 menu is instead presented in para. 9.5 on page 86. 7.4.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. The following confirmation dialog box is opened.
Figure 31. Remote Inventory confirmation request Clicking on OK after a while an information dialog box is presented.
Figure 32. Remote Inventory completed
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
7.4.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 as for the following figure.
Figure 33. View Remote Inventory Data is displayed in specific fields: Company It indicates the Companys (Alcatels branch) which designs the unit. Refer to Alcatel for the abbreviations meaning (four characters). Unit Type It indicates the units acronym Unit Part Number It indicates Alcatel or Factory products Part No.. The number indicated is that printed on the labels or on the units front coverplate. Software Part Number It indicates the id. of the units resident software CLEI Code It indicates the CLEI code according to Bellecore specs. TRISD325 Manufacturing plant It indicates the Companys manufacturing plant id. within the company, producing the unit. Refer to Alcatel for the abbreviations meaning (four characters). Serial Number It indicates the products serial number as specified by the NR 130 Norm. 04 SC.3:NE MANAGEMENT 3AL 78987 AA AA 268 61 / 268

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
957.130.112 X
Date identifier It indicates the meaning of the date that follow. It is a twodigit code supplying the following information: 00 01 02 03 04 date of construction at the time of final testing production order data construction date of the unit lot date product has been forwarded to customer 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
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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. 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 ISIS; these nodes will be called adaptive routers; ISIS protocol floods the network with link state information in order to build a complete consistent picture of the network topology. Use of ISIS routing protocol in a TMN facilitates installation and operation due to the self learning capabilities of these protocols and automatic network reconfiguration in case of failure; moreover the use of these standardized routing protocols guarantees interoperability in a multivendor environment. nodes not supporting these protocols; these nodes will be called static routers;
Networks partitions consisting of the former type of node will be called adaptive routing domains; networks partitions consisting of the later type of node will be called static routing domains. Moreover, a node which 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 34. on page 65. It is not a network planning example, it is only used to describe L1 ,L2, RAP and MESA. 8.1.1 Partitioning into Routing Subdomains In order to reduce the overhead associated with distributed adaptive routing, it may be useful to divide a adaptive routing domain into smaller routing subdomains, called areas or level 1 subdomain. A level 1 subdomain should fulfill the following requirements: a level 1 subdomain should form a connected subnetwork; this subnetwork should have only a few links to the outside world, compared with the number of internal links; each node must belong to exactly one level 1 subdomain; each node which is connected to a foreign level 1 subdomain must become a level 2 intermediate system; level 1 intermediate systems know how to communicate only with IS in the same area; obviously, there must be at least one level 2 intermediate system per level 1 subdomain; Level 2 intermediate systems must form a connected network, because level 1 paths cannot be utilized for level 2 communication. This network will be called level 2 backbone.
1AA 00014 0004 (9007) A4 ALICE 04.10
In the most simple case, all nodes within a level 1 subdomain share the same area address. In general it is allowed to have multiple synonymous area addresses within a level 1 subdomain even if the usage of this 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 subdomain: 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.
ED
04
957.130.112 X
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 system, whereby this link crosses routing domain boundaries. A Reachable Address Prefixes is handled in the same way as information about a foreign level 1 subdomain within the own domain. The Reachable Address Prefixes indicates that any packet whose destination network address NSAP 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 subdomain with area address a routing domain B resides in a level 1 subdomain with area address b In order to enable the communication, the Reachable Address Prefixes in routing domain A must contain the area address b and the Reachable Address Prefixes in routing domain B must contain the area address a. On the other hand, within a given level 1 subdomain, there can be some NEs not supporting ISIS nor ESIS protocol (static routing). In such condition, the communication can be achieved through the use of Manual End System Adjacencies (MESA). A prerequisite for the use of manual end system adjacencies is that the area addresses of the connected nodes must be the same; as a consequence the nodes must belong to the same level 1 subdomain. Within a pure Alcatel network there is no need to use any kind of static routing. Therefore normally RAP and MESA shall never be used.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
AREA (subdomain) 1
L1 All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.
L1 L1 L1 L1
L1 L1 L1 L2
L1 L1 L1 L2 L1 L1
L1

L2
L1 with MESA
AREA (subdomain) 2
L2 L2 L1
L2 L1
= NE
with RAP L1
= NE not supporting ISIS

L1
L1 with MESA
AREA (subdomain) 3
Figure 34. Routing subdomain organization example
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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: OS Configuration: definition of the local NE addresses 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 LAPD Configuration: definition of the LAPD port parameters for each LAPD channel on the local NE definition of configuration parameters needed to manage a local NE which provides a LAN ethernet interface configuration of parameters necessary to the addressing of NE connected by Reachable Address Prefixes in a domain different from the one of the local NE. These information are stored in RAP table. configuration of parameters necessary to the addressing of non ISIS NE in the same domain as the one of local NE. These information are stored in MESA table.
Ethernet Configuration:
RAP Configuration:
MESA Configuration:
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 35. Comm/Routing options

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 dialogbox opens (Figure 36. ) and allows to configure the local address of the NE. The following fields are present: a Local Address section contains the following graphical object: a Presentation Selector (P.Sel) identifies a presentation entity at the location identified by the NSAP Address. The presented value must not be modified. a Section Selector (S. Selector) identifies a section entity at the location identified by the NSAP Address. The presented value must not be modified. a Transport Selector (T. Sel) identifies a transport entity at the location identified by the NSAP Address. The presented value must not be modified. a Network Service Access Point (NSAP) Address identifies a location in the network. The first field of the NSAP address, AFI, determines the NSAP format. The AFI filed is 2 characters long (2 exadecimal digits) and, depending on the its value, the length of NSAP address is variable from 16 characters to 40 characters: the value of AFI 49 identifies the local format of variable length (from 16 characters to 40 characters). the value of AFI 39 identifies the ISODCC format of 40 characters long. the value of AFI 47 identifies the GOSIPV2 format of 40 characters long. In all cases the last two fields of the NSAP address are: System Id: uniquely identifies a NE in an area and is 12 characters long It might be the equipment MAC Ethernet address, level 2, inserted in the NE (check the value in the para. 8.7 on page 72 ) or it might be selected by the operator. Network Selector: provides the distinction among users of the network service and is 2 characters long (value is 1d). In the view, the NSAP is managed as simple strings of characters without any preformatting because of the variable format: a first string of two characters that identifies the AFI field a second string of variable length that identifies the remaining NSAP address Synonymous Area Addresses section allows to have multiple synonymous area addresses within a level 1 subdomain. The compilation of the two network addresses is optional and if they are inserted, the last two fields, System Id and Network Selector, of the mandatory address and of the synonymous addresses must be the same. System Type section determines whether the local NE acts as a intermediate system level 1 or as a intermediate system level 2 or as a End System. Note that a level 2 intermediate system performs functions of a level 1 too. End System is not operative.
Ok button is used to perform a configuration change of the data contained in the dialogbox and closes it; the dialog is visible until the end of the operations and a wait cursor is displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Cancel button close the dialog without changes of the data. Help button provides some useful information about the dialog.
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Figure 36. Local Configuration
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
68 / 268
8.4 OS Configuration
Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading menu the OS Configuration option. The dialogbox opens (Figure 37. ) and allows to configure the addresses of the Main and Spare OSs connected to the local NE. The following fields are present: Main OS Address section contains the same graphical object of the Local Address Section in the Local Configuration dialogbox. Spare OS Address section contains the same graphical object of the Local Address Section in the Local Configuration dialogbox.
Ok button is used to perform a configuration change of the data contained in the dialogbox and closes it; the dialog is visible until the end of the operations and a wait cursor is displayed. Cancel button close the dialog without changes of the data. Help button provides some useful information about the dialog.
Figure 37. OS Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
8.5 NTP Server Configuration

Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading menu the NTP Server Configuration option. The dialogbox opens (Figure 38. ) and allows to configure the addresses of the Main and Spare NTP (Network Protocol synchronization Time) Servers connected to the local NE, used for time distribution in the network. The following fields are present: Enabling NTP Protocol section allows to enable or disable the NTP Protocol. Main NTP Server Address section contains the same graphical object of the Local Address Section in the Local Configuration dialogbox. Spare NTP Server Address section contains the same graphical object of the Local Address Section in the Local Configuration dialogbox.
If the NTP server is coincident with the OS (same hardware), the same NSAP address of the OS must be assigned. Ok button is used to perform a configuration change of the data contained in the dialogbox and closes it; the dialog is visible until the end of the operations and a wait cursor is displayed. Cancel button close the dialog without changes of the data. Help button provides some useful information about the dialog.
Figure 38. NTP Server Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
8.6 LAPD Configuration

Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading menu the LAPD Configuration option. The dialogbox opens (Figure 39. ) and allows to configure a LAPD port of each LAPD channel on the NE. The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing device (upper part of the figure); each page represents a particular LAPD port of Multiplex or Regeneration Section and the respective pointing device displays the complete user label of the MS/RS TTPs associated to the port. The display of the view can be required directly by the port view containing MS/RS functional blocks; in this way only the LAPD configuration parameters of the selected MS/RS TTP are displayed In detail, each page contains the following data: LAPD Interface field allows to define or remove a LAPD Port on the selected MS/RS TTP. LAPD Role field indicates the role of a defined LAPD Port (User/Network) according the LAPD protocol. This connection is a must to establish connection between two NEs: if one is configured with User role, the other one connected must be configured with Network role.
Apply button performs a configuration change of the data contained in the selected page. Close button close the dialog without changes of the data.
Figure 39. LAPD Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
8.7 Ethernet Configuration

Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading menu the Ethernet Configuration option. The dialogbox opens (Figure 40. ) and allows to define the parameters needed to manage a NE which provide a LAN ethernet interface . The following fields and data are present: Ethernet Interface field allows to define or remove a Local Area Network Port for the access to the Data Communication Network. L2 only Parameter field indicates if the port shall be used for level 2 traffic only, thus avoiding transmitting L1 packets. Note that the flag shall be set to No if some other nodes (NEs or OSs) of the same area of the relevant NE are connected to the Ethernet. One example is indicated in Figure 41. on page 73. MAC Address section allows to display the address of the Network Element in the Ethernet LAN; it is a readonly field.
Apply button performs a configuration change of the data. Close button close the dialog without changes of the data.
Figure 40. Ethernet Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
LAN L2 NE No AREA 2 NE No L2 OS AREA 1 NE Yes L2
04
957.130.112 X Figure 41. Ethernet Configuration L2 only parameter AREA 3
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
73 / 268
8.8 Reachable Address Prefixes Configuration

Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading menu the RAP option. The dialogbox opens (Figure 42. ) and allows to configure the Reachable Address Prefix table. Each element of the RAP table allows to link a LAPD port or a LAN port of the local NE to a separate domain; the separate domain is selected by the address Prefixes. If the addressed element is the OS, the LAN port will be used. The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing device (upper part of the figure); each page represents a particular 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 if the element is empty, displays the none value and allows to select a LAPD ports or a LAN port which will be used to reach the addressed area. if the element isnt empty, displays the selected port and allows to change it. Area Address Prefix section allows the user to address the separate domain. The Area Address Prefix represents a NSAP address without the fields System Id and Network Selector. MAC Address section allows to address the element of a domain to be reached the Ethernet LAN; the field is managed as a simple strings of 12 digit. Apply button is used to perform a configuration change of the data contained in the complete RAP table and close the view; the view is visible until the end of the operations and a wait cursor is displayed. New button is used to insert a new page. Delete button is used to delete the selected page. Close button close the dialog without changes of the data.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 42. RAP Configuration
ED
04
957.130.112 X
8.9 Manual ES Adjacencies table Configuration

Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading menu the MESA option. The dialogbox opens (Figure 43. ) and allows to configure the Manual ES Adjacencies table. Each element of the MESA table allows to link a LAPD port or a LAN port of the local NE to a End System element; the ES element must be in the same area as the one of the local NE. If the addressed element is the OS, the LAN port will be used. The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing device (upper part of the figure); each page represents a particular 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 if the element is empty, displays the none value and allows to select a LAPD ports or a LAN port which will be used to reach the End System element. if the element isnt empty, displays the selected port and allows to change it. System Id section represents the System Id of the ES element. MAC Address section allows to address the element in the Ethernet LAN; the field is managed as a simple strings of 12 digit. 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. New button is used to insert a new page. Delete button is used to delete the selected page. Close button close the dialog without changes of the data.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 43. MESA Configuration
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
76 / 268
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 (see the following figure). 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 The navigation through different levels of the NE hierarchy is performed by double clicking on the objects: the first level shows the subrack level of the Equipment view (see Figure 44. ); further, by double clicking on a board body, the board level of the Equipment view can be reached (as described in chapter 10 on page 89). further, by double clicking on a port body contained in the board, the port level of the Equipment view can be reached (as described in chapter 11 on page 95). The port view displays the inner TPs. it is possible to go back to the upper level of representation by pressing the <ESC> key on the keyboard; or to go back to the previous view, by selecting the Previous option from the Views menu. Selecting in the first level of the Equipment view ( subrack level, Figure 44. ) the Show supporting equipment option from the Equipment menu, the Rack level view of Figure 45. is presented; further, selecting in the Rack level view the Show supporting equipment option from the Equipment menu, the Equipment level view of Figure 46. is presented.
N.B.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Figure 44. Equipment Overview Subracks level
04
957.130.112 X
SC.3:NE MANAGEMENT
Figure 45. Equipment Overview Rack level
3AL 78987 AA AA
268
78 / 268
Figure 46. Equipment Overview NE level In the Subrack view it is possible use the options offered by the Equipment menu (see following figure) clicking on it in the menu bar. Alarms indications are present at every NE level. Details about these alarms indications 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 decide on the in/out of service of the board is also described.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 47. Equipment menu.
ED
04
957.130.112 X
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
9.2 Set and change or remove board

The boards can be set, changed or removed using the menu options of the Equipment view.
a)
Setting or changing a board A new board may be created in either an empty slot or it may replace an existing Out of Service board (without the lock symbol). In fact, the Set option is available only after selecting an empty slot or an Outofservice board. Click on the empty slot in which a board has to be added, or on an existing Out of Service board in order to change it (see next para. 9.3 on page 84 for in /out of service info). The contour becomes highlighted to show that operations can be done on it. Select the the Set option of the Equipment pull down menu of Figure 47. on page 79. The following example of dialogue box containing a list of the different types of boards is displayed.
ACCESS CARD LIST
PORT LIST Figure 48. The list of different boards relative to an NE slot (examples) N.B. The list of boards 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 identified by acronyms and NE physical composition please refers to the Technical Handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Choose the board type required, by clicking on the corresponding item in the list. The name of the board is highlighted. Click on the OK push button to validate the choice.
The board representation appears on the NE view in the slot when the board change is effective. A lock representation appears over the boards (inservice, see next para. 9.3 on page 84) 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 NOTE: the Remove action is not possible in the case that, on the considered board, is still existing operation/connection/termination on the underlying supported signals, such as: Performance Monitoring on underlying TPs POM monitoring operations Lower order Connections Higher order Connections Lower/Higher order Path Terminations Loop backs LAN/LAPD (and any comm/routing service) Auxiliary channels Timing Sources References Daughter boards, Submodules, etc.
Thus the deletion of every operation/connection/termination is necessary, in the same order as above listed, before removing a board. Click on the board to remove (Out of Service board, as for next para. 9.3 on page 84). 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 the Equipment pull down menu of Figure 47. on page 79. From the confirmation dialogue box that opens you can confirm or cancel the Remove Board operation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
c)
Modify a board NOTE: 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 of Figure 47. on page 79 . A dialog box containing a list of different types of optical module is displayed. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
9.3 Board administrative state

The operator decides to set a board in service or out of service, if it is allowed by the NE. N.B. In the equipment view, a lock representation appears over the boards which are in in service state.
9.3.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 of Figure 47. on page 79. A lock representation appears over the boards.
9.3.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 of Figure 47. on page 79. Select the Ok push button in the confirmation window which appears. A lock representation disappears, substituted by the symbol 9.3.3 Consulting a Boards Administrative state The boards administrative (in service or out of service) state is indicated on the board view as shown in the following figure. over the boards..
Administrative State Information
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 49. Consulting a boards administrative state.
ED
04
957.130.112 X
9.4 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, defined SYNTH in the views). 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 of Figure 47. on page 79.
The following window opens.
Figure 50. Software Description dialogue box. The dialogue box contains as many folder sheets as there are softwares in the selected board. Click on the Close push button to close the dialogue box.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
9.5 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 (see the following figure): 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
For the Board level a dialog similar to Figure 51. appear.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 51. Remote Inventory
ED
04
957.130.112 X
The remote inventory data of the Subrack level can be printed on the default printer ( Figure 52. ) or to a file in postscript or ASCII format ( Figure 53. ).
Figure 52. Select Printer N.B. If no printer is installed, there is no error message displayed to indicate this.
Figure 53. Select Output Format for file
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
9.6 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 54. (example) opens.
Figure 54. Equipment Overview Subrack level
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 (see example of Figure 55. ) An example of board view with the presented port is in Figure 56. 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.
Administrative state
Board Alarms/Status
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 55. Equipment view: select the SDH port on a board.
ED
04
957.130.112 X
Figure 56. Example of a Board View A port type is described with a board rectangular view and a port identification. The port identification is usually internal to the rectangular board (see Figure 57. one example of optical port).
Figure 57. Example of a SDH 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. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
By double clicking on a board view, it is also possible open the corresponding port view (see chapter 11 on page 95).
ED
04
957.130.112 X
10.2 Board View Menu

Selecting the Board option in the menu bar of Figure 56. on page 90 the complete pull down Board menu is presented (Figure 58. ): Port Access: Access the Port view. See para.10.2.1 on page 92 . Note: this option is accessible after the selection of a port contained in the view.
Show supporting equipment: Navigate to the upper subrack level. See para.10.2.2 on page 93.
Figure 58. Board menu options These options are described in next paragraphs.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
10.2.1 Port Access Click on Port Access menu option of the Board menu to access the Port View ( see chapter 11 on page 95). Navigation to the Port view permits to show a detailed alarm presentation of the port and to set the relevant configurations as for the example of the following figure.
Figure 59. After Port Access selection (example)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
10.2.2 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 60. (example) opens.
Figure 60. Subrack level.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
94 / 268
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). The Port View can be accessed from the Equipment or Transmission Views. The Port view is reached selecting the Equipment option in the View pull down menu to present the subrack view, as described in chapter 9 on page 77. Double clicking on the selected board the relevant Board view is available presenting the ports (see chapter 10 on page 89). By double clicking on a board view, the corresponding port view is opened (see Figure 61. ). 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 (see the description at para. 14.5 on page 131). 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. 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)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 61. Example of a 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
11.2 Port View: elements on the TP

The symbols of the TPs (see Figure 62. ) 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. Selected state An orange frame around the box identifies the TP selection, so port menu refers to the selected TP.
Alarm icon area
G.783 TP Role (Termination) TP identifier
Crossconnected state
Selection indication
Figure 62. Termination TP box. Figure 63. is another example of TP with different G.783 function role. Alarm icon area
G.783 TP Role (Adaptation) G.783 Functional block acronym
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 63. G.783 Adaptation TP box.
ED
04
957.130.112 X
11.3 Port View Menu

Selecting the Port option in the menu bar of Figure 59. on page 92 the complete pull down Port menu is presented (Figure 64. ) The menu differs according the port type (SDH, PDH, HOA), and is introduced in the following: TP configuration: Set parameters for the Signal Label and Path Trace overhead on Synchronous TPs. See para 14.6 on page 138. Set B2 excessive BER and Signal Degraded parameter See para. 14.8 on page 143.
TP Threshold Configuration: PDH TP configuration:
Set parameters for the Plesiochronous TPs to use it as a timing reference. Only for PDH ports views. See para 14.7 on page 142. Only for SDH ports views. See para 11.4 on page 99 Manage the connection of the paths. See para.15 on page 163
AU4 Concatenation: Cross Connection:
POM / SUT configuration:Set parameters for POM/SUT TPs. Not available for PDH port. See para.14.11 on page 146 Show TP performance data: Performance: Loopback: MSP Not operative Not available for HOA port.
See and Show Performance Monitoring parameters and data. See Chapter 17 on page 221. Manage the loopback commands, for commissioning or maintenance purposes. See para. 14.13 on page 152.
Manage the Multiplex Section Protection of the NE. Not operative 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, see para.11.6 on page 110 Navigate to Transmission view: permit to show a complete overview about the signal flow, opening all TPs. It is described in this chapter, see para.11.7 on page 111
1AA 00014 0004 (9007) A4 ALICE 04.10
SDH Port
PDH Port
Figure 64. Port menu options (SDH and PDH)
ED
04
957.130.112 X
11.4 AU4 Concatenation

Select a STM4 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 65. Select the supported concatenation Number =4 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 65. AU4 concatenate/deconcatenate commands The Concatenate button will be enabled and the Deconcatenate button will be disabled when is selected a non concatenated AU4, viceversa when is selected a concatenated AU4.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 66. Example of a concatenated AU4 transmission view The port view represented in Figure 66. 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, CrossConnection 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 (see Figure 67. ). Click on the Deconcatenate push button to apply the command or on Cancel to exit.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 67. Example of a concatenated AU4c
ED
04
957.130.112 X
11.5 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 which differs according the port type: SDH port: ALS Management Show Optical Configuration Tx Quality Configuration: see para. 18.2.9 on page 256 Single Fiber Configuration LAPD Configuration: see para.8.6 on page 71. Ms Configuration PDH port: PDH Line Length Configuration. See para. 11.5.5 on page 109. HDSL Configuration. Not operative NT G703/704 Configuration. Not operative NT X21 Configuration. Not operative
These options are described in next paragraphs except the previously referenced.
Figure 68. Physical media menu
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
11.5.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 69. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 69. Automatic Laser Shutdown management
ED
04
957.130.112 X
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. 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. 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
2)
c)
Delete : this option deactivates the ALS function, returning to the state shown in Figure 70. on page 103. From this window it is only possible to create the ALS function (all the ALS commands are greyed).
Figure 70. 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 perform a laser restart for a single time period.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 (not operative in current release) When the ALS Manual Restart is Enable 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 Figure 71. ), 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. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 71. ALS and Laser current state (example)
ED
04
957.130.112 X
11.5.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. Figure 72. 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 72. 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 = 109 m).
The use of the port: describes whether the laser port is used for intraoffice transmissions on long distances (Long Haul ] 40 km) or for infraoffice transmissions on short distances (Short Haul ] 15 km). To close the dialogue box click on the Cancel push button.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
11.5.3 Single Fiber Configuration The single fiber configuration can be realized with passive optical couplers (see Figure 73. ) 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 73. shows that is accepted the label 1 from Tx1 to Rx2 while is accepted label 2 from Tx2 to Rx1.
Tx1 Label : 1 Tx1
Tx2 Label : 2 Tx2
Single bidir OPTICAL PASSIVE COUPLER Rx1 Rx1: accepted label=2 OPTICAL PASSIVE COUPLER Rx2 Rx2: accepted label=1
Figure 73. Bidirectional Transmission on a single fiber
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Select the Physical media option and then from the cascading menu the SDH Single Fiber Configuration option .
Figure 74. 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 (014). 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 (014).
Figure 74. Single Fiber Configuration View
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
11.5.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. Figure 75. opens. This dialog allows to select 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 75. Ms Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
11.5.5 PDH Line Length Configuration To manage the Line Length configuration click on PDH Line Length Configuration menu option of the Physical Media menu. Figure 76. opens. This dialog allows to configure the line length for a PDH PPI TP of a 45 Mbit/s port. The OK button validate the configuration and close the dialog box. The Cancel button removes the dialog
Figure 76. PDH Line Length Configuration View
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
11.6 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 77. (example) opens.
Figure 77. Board View Example.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
11.7 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 78. After Navigate to Transmission view selection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
112 / 268
12 EQUIPMENT PROTECTION MANAGEMENT 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 EMLUSM. The protection is performed by switching the board supporting the protected service when this board fails to a protecting board capable of supporting the same service. This protection is realized according to a protection scheme. An equipment protection scheme is composed of the following parameters which can be configured: Group type: 1+1 or 1+n the group type specifies if one or more unreliable resources for protection can be assigned to one or more reliables resources. 1+1 group type means that a working element is protected by one protecting unit. 1+n group type means that n working elements are protected by only one protecting unit. Protection priority: A priority can be assigned to protected units in 1+n protection schemes. This priority can be be 1, 2, ... or n, 1 being the highest priority. Configuration type: revertive or non revertive In revertive mode, a protected service will be switched back to its protected element when it has recovered from its failure. In non revertive mode, the switch to the protecting element is maintained even after a recovery from failure. Protection wait 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), Force Switch EPS,
In Board view, the board whose contents is represented is considered as implicitly selected. EPS protection states are displayed by the functional state message area of the boards involved in an equipment protection scheme.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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, as described at chapter 9.1 on page 77. Select the Equipment option in the View pull down menu. Select the EPS pull down menu. Then select the Management... option as show in the following figure.
Figure 79. Consulting EPS The following dialogue box is opened.
Figure 80. EPS Management dialogue box
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 to modify the EPS configuration. The current release of this NE fix the following protection: N+1 (with N=1) P63E1 protection board of slot 6, 63 x 2 Mbit/s (P63E1) main (protected) board of slot 7, 63 x 2 Mbit/s (P63E1) spare (protecting)
N+1 (with N 2) P3E3/T3 protection board of slot MAIN (protected): P3E3/T3, from slot 7 to 8 board of slot SPARE (protecting): P3E3/T3, from slot 6 to 7
N+1 (with N 2) P4ES1N protection board of slot MAIN (protected): P4ES1N, from slot 7 to 8 board of slot SPARE (protecting): P4ES1N, from slot 6 to 7 For P3E3/T3 and P4ES1N only 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 are the following: the access card corresponding to the protecting board must be an HPROT card the HPROT card has to be plugged at the left side of the access card group the main/spare boards have to be adjacent. the protecting board has to be plugged at the left side of the protected group of boards the protecting/protected group of ports have to be of the same type
N.B.
1+1 SYNTH protection N.B. board of slot 9, COMPACT ADM1 (SYNTH) main (protected) board of slot 10, COMPACT ADM1 (SYNTH) spare (protecting) for each type of failure on the COMPACT ADM1 main board (matrix, CRU, Shelf Controller) a switch is performed to the spare boards. The optical/electrical port and the Equipment Controller function on the COMPACT ADM1 board are not EPS protected. The SYNTH protection is automatically presented in the left side of the dialog box when the SPARE SYNTH is created in the Set option of the Equipment menu. It is not created with the EPS menu described in this chapter.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
04
957.130.112 X
a)
Scheme displaying
b)
Scheme creation
To create a new protection scheme,dont click on item in the left list. In this way the right part is displayed empty and the Choose Protecting button is sensitive. Press this button to displays a window to choose a board in the Board Selection list (see Figure 81. on page 117). The board are listed opening the NE>rack>subrack levels. After that operation, Choose Protecting button becomes insensitive and Choose Protected becomes sensitive (see Figure 82. on page 117) The user can add, always using the same Board Selection list dialogue box presented, as many protected boards as wanted (max.2 in this NE). 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 reopening the EPS Management dialogue box). The Cancel push button cancels the creation and closes the dialog box. c) Scheme deletion
To delete an existing protection scheme, the user selects a scheme in the left list. Using the Delete button, user could delete the scheme. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Figure 81. EPS: board selection
04
957.130.112 X
SC.3:NE MANAGEMENT
Figure 82. EPS: choose protected
3AL 78987 AA AA
268
117 / 268
The EPS functional state of a board selected in the board view is displayed at the bottom of the view as shown in the following figures.
Protection role
Protection status
Switch Type
Figure 83. EPS functional state from protected active board view
Figure 84. EPS functional state from protecting active board view
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
12.3 Configuration: revertive and WTR for EPS

This functionality configure 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 option as show in the following figure.
Figure 85. Configure EPS The following dialogue box is opened.
r01sr1/board#07 P63E1 r01sr1/board#06
Revertive 60
Figure 86. EPS Management dialogue box

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
The dialog box provides configuration for elements such as : the name of the protecting element as a label the board type of the protecting element as a label a list displaying the protected elements owned by the scheme 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 COMPACT ADM (SYNTH1 or SYNTH1N) is Not Revertive only N+1 63 x 2 Mbit/s ( P63E1) protection is Revertive N+1 3 x 34/45 Mbit/s (P3E3/T3) protection is Revertive N+1 4 x STM1 Electrical (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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 option as show in the following figure.
Figure 87. Switching EPS
The following dialogue box is opened.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 88. EPS Switch dialogue box
ED
04
957.130.112 X
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Not operative in the current release
04
13 MULTIPLEX SECTION PROTECTION MANAGEMENT
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
123 / 268
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
124 / 268
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 state is indicated by the alarm synthesis icon the cross-connection state is indicated by a cross whether a TP can be structured is indicated by a circle
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. This functionality is accessed by calling the configuration dialogs of the common Transmission/Port Views category. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.2 View elements

The Transmission View uses the symbols illustrated in Figure 89. AU4 Label indicates the type of TP Adaption function
Termination function
Compound Termination and Adaption function Structurable point Crossconnectable point with crossconnected TP or Alarm synthesis icon
Figure 89. Symbols Used in Transmission View
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 pulldown menu which provides the Transmission View operations. 14.3.1 View Description Figure 90. illustrates the Transmission View area. TPs that are received from the network element are displayed in the Transmission View with the respective TP and connection symbols described in Figure 89. 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.
Figure 90. Transmission View Area
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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.
14.3.4 Dynamic View Behavior The following section describes the view states and provides a short description of events that affect the view. 14.3.4.1 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. 14.3.4.2 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. 14.3.4.3 Navigation to Transmission View from other views If the Transmission View is popped up from the Port View, only the selected TP is displayed. 14.3.4.4 Alarm notification Alarms concerning the TPs displayed are indicated graphically by the alarm synthesis icons of the TP objects. The TP objects are updated accordingly. 14.3.4.5 Object deletion All kinds of object deletion events related to TPs displayed are indicated by the TP objects. The graphical objects are removed accordingly from the Transmission View. Example: modification of the payload structure from 63 TU-12 to 3 TU-3.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 (see for example Figure 90. on page 127. Selecting the Transmission option in the menu bar of Figure 90. on page 127. the complete pull down Transmission menu is presented (Figure 91. ) The following menu items are available: Add TP Select the TP to show on the Transmission view. It is described in the following paragraph. Display TPs that are related to the selected TP. It is described in this chapter, see para 14.15.1 on page 159. Hide TPs that are related to the selected TP or the selected TP. It is described in this chapter, see para 14.15.2 on page 160 Set parameters for the Overhead on Synchronous TPs. It is described in this chapter, see para 14.6 on page 138 Set parameters for the Plesiochronous TPs to use it as a timing reference. It is described in this chapter, see para 14.7 on page 142
Expand
Hide
TP Configuration
PDH TP Configuration
TP Threshold Configuration Set B2 ExBER and Degraded Signal parameters. It is described in this paragraph, see para.14.8 on page 143. Alarm Persistency Time Helps to suppress oscillating alarms. It is described in this chapter, see para 14.9 on page 144 Terminate a path on a AU-4 CTP It is described in this chapter, see para 14.10 on page 145 Disterminate a path on a AU-4 CTP It is described in this chapter, see para 14.10 on page 145 Manage the connection of the paths. See para. 15 on page 163 Create, configure and delete POM/SUT TPs. It is described in this chapter, see para 14.11 on page 146 Set and show Performance Monitoring parameters and data. See chapter 17 on page 221. Provides the possibility of structuring and destructuring selected TP It is described in this chapter, see para 14.12 on page 151 Manage the loopback commands, for commissioning or maintenance purposes. See paragraph 14.13 on page 152. Manage the physical TP setting. See para 14.14 on page 157.
Terminate TP
Disterminate TP
Cross-Connection POM/SUT
Performance
Structure TPs
1AA 00014 0004 (9007) A4 ALICE 04.10
Loopback
Physical Media
ED
04
957.130.112 X
MSP
Manage the Multiplex Section Protection of the NE. (Not operative in the current release)
Show Supported Board
Navigate to the upper board level. It is described in this chapter, see para 14.15.3 on page 161 Permit to show the detailed alarm of the TP. It is described in this chapter, see 14.15.4 on page 162
Navigate to Port View
These options are described in next paragraphs except the previously referenced.
Figure 91. Transmission menu options
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.5 ADD TP
Select the Transmission > Add TP option.
This menu item opens the TP Search dialog (see Figure 92. ). 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). 14.5.1 TP Search 14.5.1.1 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 items displayed small, they are displayed in a hierarchical order. Double-click again to recall the next level (see Figure 94. ).
Figure 92. TP Search Dialog, Initial State After double-clicking on an object, an Information window appears (see Figure 93. ). The message text corresponds to the object selected.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 93. Information Window The search can be stopped with Cancel.
ED
04
957.130.112 X
Figure 94. TP Search Dialog with Various TP Selections After clicking on Show CC State, a more detailed TP list is displayed (see Figure 95. ) containing TP cross connection status information.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
It is possible to select several individual TPs from the TP list by clicking on them while holding down the Ctrl key on the keyboard. To select a block of TPs, click on the first TP and then click on the last TP in the block while holding down the Shift key on the keyboard. But only the first TP selected in the list will be shown in the Transmission View.
Figure 95. TP Search Dialog with Status Information Displayed The symbols in the TP list have the following significance: Not connected Unidirectonal connected from and to Bidirectional connected Not allowed Figure 96. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 97. Board History Check List 14.5.1.2 Search Mode Use Search Mode together with the filtering options provided below the TP list (see Figure 98. ). The following options are available: Class: Ignore, TU-12, VC-12, VC-12+TU-12, TU-3, VC-3, VC-3+TU-3, AU-4, VC-4, VC-4+AU-4. 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:
1AA 00014 0004 (9007) A4 ALICE 04.10
Permits to insert the location of r<rack#>sr<subrack#>sl<slot#><port#>

Name: not supported
the
TP
in
the
following
format:
ED
04
957.130.112 X
Figure 98. TP Search Dialog with Different Filtering Options After activating the search process with the Search TP button, the following dialog box appears. The search can be interrupted by clicking on Cancel.
Figure 99. Information... Dialog for Search Process N.B.

1AA 00014 0004 (9007) A4 ALICE 04.10
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).
ED
04
957.130.112 X
14.5.1.3 Common Buttons The following buttons are available in all modes: 14.5.1.3.1 Ok Closes the dialog and opens the Transmission View containing the selected TP, as for the example of Figure 90. on page 127. 14.5.1.3.2 Close Closes the dialog without updating the Transmission View. 14.5.1.3.3 Print This command is used to generate and print a list of TPs according to the current filter selection (refer to Figure 102. for an example of a printout). The command opens the following dialog:
Figure 100. 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 101. Print to File

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 102. Example Printout 14.5.1.3.4 Help This command opens the online help for the TP-Search dialog.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 following objects: 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. Not operative in current release. Enabling Monitoring. Not operative in current release. Enabling Generator. Not operative in current release.
The dialogs of the following figure appears:
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 103. High Order TP Configuration
ED
04
957.130.112 X
14.6.1.1 J1 Path Trace Not operative in current release. If the Path Trace is 16 bytes long, the first byte is a CRC7 checksum calculated by 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. Received fields is read only. With the relevant button it is possible to enable or disable TTI Monitoring. Empty TTI button permits to send an all zeroes path trace. 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 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 C2 Signal Label value is automatically selected by the NE according the VC structure. Equipped not specific (it corresponds to number 1)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.6.2 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. J2 Path Trace. Not operative in current release.
The following dialogs appears:
Figure 104. Low Order TP Configuration 14.6.2.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. Received fields is read only. With the relevant button it is possible to enable or disable TTI Monitoring. Empty TTI send an all zeroes path trace.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.6.2.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: 1: 2: 3: 4: Unequipped Equipped non-specific Asynchronous Bit Synchronous Byte Synchronous
In the Transmitted field it is possible to select the values: Automatic: the C2 Signal Label value is automatically selected by the NE according the VC structure. Equipped not specific (it corresponds to number 1)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.7 PDH TP Configuration

Select the Transmission > PDH TP configuration option. PDH TP Configuration can also be accessed from the Port view menu. This menu item enables the configuration of the most important transmission parameters for a PDH TP. Only the parameters supported by the object are displayed. Supported options include Enable Framed Mode and Enable CRC4 Mode. This command is available for: E1-CTP
The following dialog appears:
Figure 105. PDH Port Configuration Enable CRC4 Mode is only available when Enable Framed Mode is selected and the TP supports the CRC4 Mode. Press Ok to apply the parameters or Cancel to close the dialog.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.8 TP Threshold Configuration

Select the MST block.
Select the Transmission > TP Threshold Configuration option. The following box appears, permitting to select the TP Thresholds. Only the Poisson parameter is available, setting the B2 ExBER (103 to 105) and B2 Signal Degrade (105 to 109) For B2 ExBER it is also possible to enable the relevant consequent actions. \
Figure 106. Degraded Signal Threshold selection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Not operative in current release.
04
14.9 Alarm Persistency Time Configuration
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
144 / 268
14.10 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.10.1 Terminate TP Use this action to terminate a path. It can be performed on a AU-4 CTP. A cross-connection between the selected AU-4 CTP (= aTP) and a modifiable VC-4 TTP (= bTP) is created. Three TUG-3 and TU-3 are created 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.10.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 operations Lower order Connections Higher order Connections Lower/Higher order Path Terminations Loopbacks 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 .
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.11 POM/SUT
Select the Transmission > POM/SUT option as for the following figure. Creation/Deletion and Configuration options are present.
POM/SUT Configuration can also be accessed from the Port view menu. The commands of this menu item are for the management of the POM/SUT (Path Overhead Monitoring/Supervised Unequipped Termination). This command is available for: AU-4 CTP TU-3 CTP TU-12 CTP
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.11.1 Creation/Deletion The following dialog opens:

Figure 107. POM/SUT Creation/Deletion The Path Overhead Monitoring has the following parameters: Before Matrix (not supported in current release) After Matrix
The Supervisory Unequipped Termination, not operative in current release, has the following parameters: Sink (before matrix) Sink (after matrix) Source Bidirectional
Press Ok to apply the parameters or Close to close the dialog and discard the not with Ok applied changes.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
When select and apply the Path Overhead Monitoring, the changes will be displayed in the Port View in the following manner:
TP with POM after Matrix
Figure 108. Display of POM/SUT in Port View
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.11.2 Configuration Depending on the parameters selected in the POM/SUT Creation/Deletion dialog, not all sections of the dialog are available. N.B. It is possible to open the POM/SUT Configuration dialog for a CTP even if neither Path Overhead Monitor nor Supervised Unequipped Termination was created before. No changes can be made in this case and the values displayed can be ignored.
Figure 109. POM/SUT Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.11.2.1 TTI Definition This function is not operative. 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 Continuous
14.11.2.2 Error Distribution Poisson and Bursty error distribution are supported (Poisson only supported). 14.11.2.3 Alarm Severities It allows to change the ASAP assigned to the specified POM/SUT. 14.11.2.4 Thresholds Set the thresholds of the following parameters: Signal Degrade Poisson mode only: from 105 to 109. Excessive Error Poisson mode only: from 103 also if presented a selection from 103 to 105 Bursty Degrade Select a value between 1 and 8000 errors/sec for the Bursty Degrade threshold. Not operative Bursty Consecutive Select a value between 2 and 10 sec for the Bursty Degrade Consecutive. Not operative 14.11.2.5 Alarm Timing Not available. 14.11.2.6 Unequipped Trail Not available.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.12 Structure TPs

Select the Transmission > Structure TPs option as for the following figure.
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:

1AA 00014 0004 (9007) A4 ALICE 04.10
modifiable VC-4 TTP: TU-3, TU-12 TUG-3: TU-3, TU-12 TUG-2: TU-12. 04 SC.3:NE MANAGEMENT 3AL 78987 AA AA 268 151 / 268
ED
957.130.112 X
14.13 Loopback
The commands of this menu item are for the management of the loopback commands, for commissioning or maintenance purposes. 14.13.1 Loopback Configuration The loopbacks 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. The loopback architecture provides four configurations ( see Figure 110. ). Line Loopback And Continue Line Loopback And AIS Internal Loopback And Continue Internal Loopback and AIS
Initial
Destination
Line
Internal
Line
Destination
AIS
Initial
Line Loop And Continue
Line Loop And AIS
Destination
Initial
AIS
Line
Internal
Line
Initial
Destination
Internal loop And Continue
Internal loop And AIS
Figure 110. Loopback configurations

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Select a TP that supports the Loopback Configuration Loopbacks act on the following TPs:
PDH board: Line loopback performed on: P for 2/34/45 Mbit/s PPI Internal loopback performed on: p12 for 2 Mbit/s CTP p31 for 34/45 Mbit/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, SYNTHN, etc.) Line loopback performed on: EIS for electrical STM1 SPI OpS for optical STM1, STM4 SPI Internal loopback performed on: MsT TTP for STM1, STM4 ports
Select the Transmission > Loopback > Port Loopback Configuration option as for the following figure. Port Loopback Configuration can also be accessed from the Port view menu.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 111. opens.
Figure 111. Port Loopbacks View Choose the TP clicking on the Choose TP button. Select the TP where to apply the loopback command. For the TP selection procedure, follow the TP research description reported in para. 14.5.1 on page 131. For this NE the Timed Loopbacks field is not managed and thus Start/Stop loopbacks time is not editable.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.13.2 Loopback Management To manage the loopback configuration select the Transmission > Loopback > Loopback Management option as for the following figure.
Loopback Management can also be accessed from the Port view menu and from the Configuration menu. Figure 112. opens.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 112. Loopback Management
ED
04
957.130.112 X
The configured loopback are listed into the current loopbacks table. This table can be managed by the Search criteria, Delete and Create commands.
Search Criteria (not 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 ( Figure 111. ) opens. Follow the previously paragraph indications to create a new loopback configuration.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.14 Physical Media

Select the Transmission > Physical Media option as for the following figure.
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 TPs type (for the option common with the Port view reference is made to the relevant paragraph):
1AA 00014 0004 (9007) A4 ALICE 04.10
ALS Management. Show Optical Configuration TX Quality Configuration Single Fiber Configuration. Extra traffic Regeneration Section management Line Length Configuration Set Domain HDSL Configuration NT Configuration X21 Configuration SC.3:NE MANAGEMENT
See para. 11.5.1 on page 102. See para.11.5.2 on page 105. See para.18.2.9 on page 256. See para.11.5.3 on page 106. Not operative Not operative See para.11.5.5 on page 109. See para. 14.14.1 on page 158. Not operative Not operative Not operative
ED
04
957.130.112 X
3AL 78987 AA AA 268
157 / 268
14.14.1 Set Domain This function is Not Operative. 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: The dialogbox contains the following fields: NML Assignment: each connected manager to the TP is highlighted in the list. The user can set a manager clicking on the denomination. Several manager 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 EMLUSM 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 to select the domain among that displayed in the list, assigning it to the TP. 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 113. Set Domain
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.15 Navigation Commands

14.15.1 Expand Select the Transmission > Expand option as for the following figure.
This menu item provides the possibility of displaying TPs that are related to the selected TP. These may be TPs that are contained by the TP or TPs which belong to the physical port that is actually connected to the TP. Show next level of lower TPs, Show all lower TPs, Show next level of upper TPs, Show all upper TPs.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.15.2 Hide Select the Transmission > Hide option as for the following figure.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.15.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 114. Board View
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
14.15.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:
Figure 115. Port View
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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: Para. 15.1.2 on page 164 Multiplex Structures for SDH gives an overview on the SDH technology Para. 15.1.3 on page 167 Definition of Termination Points gives an overview about the termination points implemented on the NE Para. 15.1.4 on page 171 Cross-Connection Types provides information concerning cross-connection types supported by the NE Para. 15.1.5 on page 173 Cross-Connection Protection provides information concerning cross-connection protection supported by the NE Para. 15.2 on page 175 Operative sequence to execute Cross-Connections details the complete procedure to realize cross-connection Para. 15.3 on page 177 Cross-Connections Management details the contents of the main cross-connections view Para. 15.4 on page 184 Create/Modify Cross-Connections describes the creation and modification of cross-connections Para. 15.5 on page 199 Activate/Deactivate/Delete Cross-Connections describes the activation, deactivation and deletion of cross-connections. Activation and deactivation not supported in current release. Para. 15.6 on page 200 Split and Join Cross-Connections describes how to split or join bidirectional cross-connections. Not supported in current release. Para. 15.7 on page 203 Protection Switching deals with switching actions (force, manual, lockout protection) on cross-connections Para. 15.8 on page 205 Print deals with printing out list entries on printers or into files Para. 15.9 on page 206 Port Switch Over not operative in the current release Para. 15.10 on page 207 Show Cross-Connected TPs describes the possibility of showing connections between two or more TPs of different different hierarchies, e.g. connection between au4 and vc4.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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. Signals of the Synchronous and Plesiochronous Digital Hierarchy (PDH) are packed by synchronous multiplexers into Virtual Containers (VC). The STM-1 signal structure is achieved by using the multiplex structure complying with ITU-T and ETSI, (see Figure 116. ). 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 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 make up the STM-1 frame.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
x1 C4 x1 TUG3 x3 x3 VC4 AU4 STM1 xN STMN VC3 TU3 C3 x7 x1 C2 x3 C12 x4 C11 VC11 TU11 VC12 TU12 VC2 TU2 TUG2 x7 Legend: VC3 AU3 C VC TU TUG AU : Container : Virtual Container : Tributary Unit : Tributary Unit Group : Administrative Unit Pointer -Processing not implemented
04
957.130.112 X
SC.3:NE MANAGEMENT
140 Mbit/s
(45 Mbit/s) 34 Mbit/s
6 Mbit/s
2 Mbit/s
(1,5 Mbit/s)
Figure 116. SDH Multiplex Structure according to ITU-T G.709
3AL 78987 AA AA
268
165 / 268
The STM-1 frame consists of: a Section Overhead (SOH) an AU Pointer area a payload area 270 Columns (Bytes) 1 1 Section Overhead SOH 3 4 9 rows 5 AU Pointer Payload 9 270
Section Overhead SOH 9
Figure 117. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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.
15.1.3 Definition of Termination Points (TP) When ports are depicted on the user interface, the following abbreviations are used. This section concerns the multiplex structure (see Figure 116. ) 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 (see Figure 118. ) a distinction is made between the following CTPs: au4 (au4 Connection Termination Point) The au4CTP represents both the creation and termination of an STM-1 connection. The High-order Connection Supervision (HCS) function is included. tux (tux Connection Termination Point), e.g. tu12CTP, tu3CTP. The tuxCTP represents both the creation and termination of a vcx connection. The Low-order Connection Supervision (LCS) function is included.
CTPs on PDH level On PDH level (see Figure 119. ), a distinction is made between the following CTPs: e4CTP (e4 Connection Termination Point) The e4CTP represents both the creation and termination of a 140 Mbit/s connection. e3CTP (e3 Connection Termination Point) The e3CTP represents both the creation and termination of a 34 Mbit/s connection. DS3CTP (e3 Connection Termination Point) The DS3CTP represents both the creation and termination of a 45 Mbit/s connection. e1CTP (e1 Connection Termination Point) The e1CTP represents both the creation and termination of a 2 Mbit/s connection.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
TTPs on SDH level On SDH level (see Figure 118. ) a distinction is made between the following TTPs: esTTP (Electrical Section TTP) An esTTP displays the physical characteristics of a port with electrical access (level and code monitoring and conversion). osTTP (Optical Section TTP) An osTTP displays the physical characteristics of a port with optical access (level and code monitoring and conversion). rsTTP (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. msTTP (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. protTTP (Multiplexer Section Protection TTP) An protTTP displays the protection of the multiplex section.
TTPs on PDH level On PDH level (see Figure 119. ) a distinction is made between the following TTPs: vc4 (vc4 Trail Termination Point) A vc4TTP represents both the creation and termination of a VC4 path. P (pPI Trail Termination Point) On the PDH side, an pPITTP corresponds to the esTTP of the synchronous side. Depending on the type, it can either display the characteristics of a 140 Mbit/s, a 45MBit/s, a 34 Mbit/s or a 2 Mbit/s port. vc3 (vc3 Trail Termination Point) A vc3TTP represents both the creation and termination of a VC3 path. vc12 (vc12 Trail Termination Point) A vc12TTP represents both the creation and termination of a VC12 path.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
esTTP/osTTP
rsTTP
msTTP
protTTP
au4CTP
vc4TTP
TUG3
TUG3
TUG3
tu3CTP
TUG2 TUG2
TUG2 TUG2
TUG2 TUG2
TUG2
tu2CTP
tu12CTP
tu12CTP
tu12CTP
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 118. SDH Transport Level Diagram
ED
04
957.130.112 X
pPITTP
140 Mbit/s
45 MBit/s DS3CTP
(e#aCTP)
34 Mbit/s e3CTP
(e#aCTP)
2 Mbit/s e1CTP
(e#aCTP)
e4CTP
(e#aCTP)
4 vc4TTP vc3TTP vc3TTP vc12TTP
Number of branches
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 119. PDH Transport Level Diagram
ED
04
957.130.112 X
15.1.4 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, Alcatels standardized signal format for internal interfaces, is similar to the STM-1 format. The incoming signals are mapped or converted to GTI format on the plesiochronous and synchronous I/O boards. This frame is based on the STM-1 frame specified by ITU-T Recommendation G.707. It enables the transport of all signals in the US hierarchy and ETSI hierarchy levels 1 to 4 (1.5 Mbit/s to 140 Mbit/s) mapped to Virtual Containers (VCs) (see Figure 116. ). 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. 15.1.4.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.

input TP

output TP
Figure 120. Unidirectional Connection 15.1.4.2 Bidirectional Connection Information is transmitted between input port and output port in both directions (point-to-point).

input TP

output TP
Figure 121. Bidirectional Connection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
15.1.4.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.

input TP
leg 1 leg 2 leg 3

output A output B output C
Figure 122. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
15.1.5 Cross-Connection Protection 15.1.5.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 (see Figure 123. ).

input A prot. input B
in case of failure

output TP
Figure 123. Protected Unidirectional Connection 15.1.5.2 Protected Bidirectional Connection A bidirectional connection is routed from Input A to the Output C (primary route). Input A (input protected see Figure 124. ) can be protected:

A B
in case of failure
Figure 124. Bidirectional Connection Input Protected N.B. By means of this connection are created links with SNCP protection.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
15.1.5.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, as illustrated in Figure 125. 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.

input A prot. input B
leg 1 leg 2
in case of failure
leg 3

output A output B output C
Figure 125. Protected Broadcast Figure 125. 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.5.4 Drop and Continue Connection A Drop and Continue connection is a composed by: (see Figure 126. ) 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.

A Input

C Output

B Prot. input
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 126. Drop and Continue Normal
ED
04
957.130.112 X
15.2 Operative Sequence to execute Cross-Connections

This paragraphs list the complete procedure to realize cross-connection moving among the various menus. Three main cases have been considered: an high order signal cross connection (AU4) an high order concatenated signal cross connection (AU4c) a low order signal cross connection (example : TU12)
Procedure for high order signal (AU4) Select Transmission option from the View menu Select Transmission Cross Connection Cross Connection Management Click on Create in the Cross Connection Management windows; a new window called Main Cross Connection is opened. Select the correct value in the fields Type and Protection
Click on Choose relative to the Input field; a new window called TP search is opened. On the Equipment field select the Board, in the Termination Points field select the AU4
Click on OK; the TP search window is closed. In the Main Cross Connection window repeat the same on the Output field and on the Prot. Input field for protected connections Click on OK in the Main Cross Connection window to terminate the creation and subsequently click on Cancel to go to the Cross Connection Management window. Click on Search in the Cross Connection Management window to see the new crossconnection created.
Procedure for AU4 concatenated (AU4c) N.B. Before to create an AU4 concatenated crossconnection is necessary to define that the AU4s on a STM4 board are concatenated as explained in para 11.4 on page 99. 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. 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 concatenated AU4c (syntax example: r01sr1sl08/port#01#01AU4P4c )
1AA 00014 0004 (9007) A4 ALICE 04.10
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 04 SC.3:NE MANAGEMENT 3AL 78987 AA AA 268 175 / 268
ED
957.130.112 X
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 crossconnection 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 choosed and indicated as port # n, where n is the VC4 number. This connection will appear on the Cross Connection Management view in a independent line.
If TU12 (example) are selected, in the transmission window clicking twice on the TUG3 and TUG2 blocks the TU12 are displayed Select the TU12 to be 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. 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 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 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 crossconnection created.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
15.3 Cross-Connections management

A list of cross-connections can be displayed in the Cross-Connection Management dialog (see Figure 128. on page 182). 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
The Cross-Connection Management dialog is initially empty (see Figure 127. on page 180). 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
15.3.1 Search Criteria

Name (not supported in current release) Number of the crossconnection (automatically assigned)
ACD (not supported in current release) 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 (for more detailed information, refer to Chapter 9.5): Forced to Input 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 (see Figure 128. on page 182)

The # within brackets identifies a number.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X Figure 127. Cross-Connection Management Dialog (Initial State)

SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
180 / 268
15.3.2 Cross-Connection List After a successful search, a read only list of cross-connections matching the search criteria appears (see Figure 128. ). 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 errored signal: P (Protecting input) or I (Input) <signal state> indicates the signal state: SD (Signal Degrade) or SF (Signal Failure) <switch status> status of the switch: c (completed) or p (pending)
Example: Auto I (P:SD-c) 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(ctivated) or D(eactivated) Dir. Direction-related connection type: uni(directional), bi(directional) or mp (multipoint) Input signal source; contains the TP type and physical location of the port according to the format <rack#><subr.#><board#><port#>,<port#>#TP (see Figure 128. on page 182) The # within brackets identifies a number. Protecting Input protecting source (for protected cross-connections only); contains the TP type and physical location of the port according to the format
1AA 00014 0004 (9007) A4 ALICE 04.10
r<rack#>s<subr.#>b<board#>/port#<port#>-TP (see Figure 128. on page 182)

The # within brackets identifies a number.
ED
04
957.130.112 X
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 128. Cross-Connection Management Dialog (After Search)
ED
04
957.130.112 X
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.
15.3.3 Actions available The following actions are available:

Create a crossconnection (see chapter 15.4 on page 184) The Main Cross-Connection dialog (see Figure 132. on page 191) is opened.
Modify a Cross-Connection (see chapter 15.4 on page 184) Available if just one cross-connection is selected from the list. The Main Cross-Connection dialog (see Figure 132. on page 191) is opened. Activate a Cross-Connection (see chapter 15.5 on page 199) Available if at least one cross-connection is selected from the list. Not operative in current release. Deactivate a Cross-Connection (see chapter 15.5 on page 199) Available if at least one cross-connection is selected from the list. Not operative in current release. Delete a Cross-Connection (see chapter 15.5 on page 199) Available if at least one cross-connection is selected from the list. Split a Cross-Connection (see paragraph 15.6.1 on page 202) Available if at least one bidirectional cross connection is selected from the list. Not operative in current release. Join Cross-Connections (see paragraph 15.6.2 on page 202) Available if two cross connections are selected. Not operative in current release. Protection Switching (see chapter 15.7 on page 203) Available if exactly one protected cross-connection is selected from the list. The Protection Actions dialog is opened. Print (see chapter 15.8 on page 205) Prints the filtered list of cross-connections.
The dialog has to be closed explicitly.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 (chapter 15.3.3 on page 183) in the Cross-Connection Management dialog (see Figure 127. on page 180). The dialog box of Figure 132. on page 191 is presented ( Main Cross Connection view).
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
15.4.1 Cross-Connection Parameters The Main Cross Connection view of Figure 132. on page 191 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). 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, Figure 129. for the Protection Criteria dialog is opened, where the user can display and configure the criteria for automatic protection switching. The following criteria are always present and cannot be changed by the user: AU-TU-AIS (Alarm Indication Signal). LOP (Loss Of Pointer)
The following switching criterion can be configured selecting the respective button: ExBer (Excessive Bit error rate)
This parameter are important to define the SNCP protection: SNCP/I: only AUTUAIS and LOP fixed criteria used
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 129. Protection Criteria 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. Input To enter the input TP, click the relevant Choose button and select the TP in the TP Search dialog (see Figure 94. on page 132). 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
04
957.130.112 X
Table 1. Optional and Mandatory Configurable Parameters for Cross-Connection Creation
Input Parameters
Unidirectional/Bidirectional Cross Connection Not Protected Protected
Broadcast Cross Connection Not Protected not protected one TP one or more TPs Protected
Type D&C Topology Protection Protection Criteria Protected Revertive Input Protecting Input Output
unidirectional/bidirectional normal/inverse not protected one TP one TP protected x x one TP one TP one TP
unidirectional protected x one TP one TP one or more TPs
not available configuration optional
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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
Broadcast with one protected leg
1AA 00014 0004 (9007) A4 ALICE 04.10
Drop & Continue normal
ED
04
957.130.112 X
Drop & Continue inverse
Loopback connection: unidirectional, same input and output TP Figure 130. Cross-Connection Icons
Example:
current state: TPs are not connected
state after creation: unidirectional, non-protected cross-connection
Figure 131. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 view of Figure 132. on page 191. For a detailed description of the single parameters, refer to the previous para. 15.4.1 on page 185. For information on cross-connection types, refer to para. 15.1.4 on page 171. 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 (uni- or bidirectional) 1) 2) 3) Select the cross-connection type. Select the protection state. 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 (see Figure 133. ), 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, then select the filter criteria ConnectionState not connected and Class AU-4 and click on button Search. The matching TPs are listed in the right listbox. Select the input TPs in the list and confirm with Ok. For a more detailed description on the Search for Cross Connection dialog see para. 14.5.1 on page 131. 4) Select or type in the output TP as described in Step 3 ).
The following steps only apply to protected cross-connections: 5) 6) Select or type in the protection TP as described in Step 3 ). Configure the criteria for automatic protection switching.
Press the button Ok to confirm the creation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
Figure 132. Create a Bidirectional Protected Cross-Connection
3AL 78987 AA AA
268
191 / 268
Create a Broadcast Connection 1) 2) 3) Select the cross-connection type unidirectional Select the protection state. 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 (see Figure 133. ) or select the input field and enter the name of the TP directly. 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 listbox (see Figure 133. ). Select the input TPs in the list and confirm with Ok. For a more detailed description on the Search for Cross Connection dialog see para. 14.5.1 on page 131. 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 (Figure 134. on page 194). 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. Examples are in Figure 134. and Figure 135. 6) Configure the criteria for automatic protection switching.
Press the button Ok to confirm creation.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Figure 133. Search for Cross-Connection Output
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
193 / 268
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X Figure 134. Create an Unprotected Broadcast Cross-Connection

SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
194 / 268
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
Figure 135. Create a Protected Broadcast Cross-Connection
3AL 78987 AA AA
268
195 / 268
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. 15.4.1 on page 185. To modify a cross connection select one from the connection list of Figure 128. on page 182. 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 2. Modifiable Parameters
Input Parameters not protected to protected Type D&C Topology Protection Protection Criteria Unprotected Protected Revertive Input Protecting Input Output
x
Modification protected to not protected normal/ inverse not protected x x x
normal/ inverse protected x x x x x x

not accessible accessible
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
The following few facts should be taken into consideration when modifying connections.
Unprotect a protected cross-connection (see Figure 136. ): 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 136. In addition, a question box appears, asking the user to confirm the unprotect action.
Figure 136. Unprotect a Unidirectional Cross-Connection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 137. Protection principle are given in para. 15.1.5 on page 173.
Figure 137. Protect one Leg of a Broadcast Connection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 (see Chapter 15.3 on page 177). The connection state (Act = A or D) is indicated in this connection list. To activate a cross-connection, select one from the connection list (see Figure 128. ) 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 Not supported in current release. After creation, a cross-connection is automatically in an active state. To deactivate a cross-connection, select one from the connection list (see Figure 128. ) 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. To delete a cross-connection, select the corresponding connection from the list and click on the Delete button. To prevent operation errors, the user must confirm the deletion request. The deleted cross-connection automatically disappears from the connection list when the operation is successful.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
15.6 Split and Join Cross-Connections

Not supported in current release. 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 138. ). The new cross connection has the same name and activation status as the old bidirectional one.
Split

B B
Join (case 1)
Figure 138. Split/Join Unprotected Bidirectional Cross-Connection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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.

A B

A B
Split
Join (case 2)

C C

A B
protected unidirectional crossconnection
broadcast connection
Figure 139. Split/Join to Protected Bidirectional Cross-Connection
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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) 2) both unprotected, unidirectional and the input is the output of the other one, or 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 (case 1, see Figure 138. ) or a protected bidirectional (case 2, see Figure 139. ) cross-connection. If the original cross-connections have different names, the new name is a concatenation of the names of both of them.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
15.7 Protection Switching

The Protection Actions dialog is displayed after clicking on the Protection button in the Cross Connection Management dialog (see Figure 128. ). 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 140. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
Release Force Forced switching is disabled and automatic protection switching re-enabled.
ED
04
957.130.112 X
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.
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 (grayed) accordingly.
After completion of protection switching, the list entry in the Cross Connection Management dialog is updated automatically. After clicking on an action button and completing the action initiated, the dialog disappears automatically.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 (see Figure 142. and Figure 141. )
Figure 142. Select Printer N.B. If no printer is installed, there is no error message displayed to indicate this.
Figure 143. Select Output Format
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED 15.9 Port Switch Over

Not operative in the current release.
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
206 / 268
15.10 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.
The result is that all other TPs connected to the currently selected TP are displayed (see the example of Figure 144. on page 208). 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Figure 144. Show Cross Connected VC4 of an AU4
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
208 / 268
16 OVERHEAD MANAGEMENT 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 crossconnection Crossconnection between 2 or more OH bytes Termination of an OH byte onto an auxiliary port or vocal channel Total Passthrough of the MSOH bytes for some cards Definition of the Phone Parameters
There is a TP associated to every OH byte and to every auxiliary port, so TP could be used instead of OH bytes or auxiliary port, depending on the context.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
16.2 OH Connection overview

Here are described the possible OH connections For OH Phone Parameters directly refer to the para 16.7 on page 219. OH Crossconnection
The operator has to be able to crossconnect 2 or more OH bytes on 2 different boards. The possible crossconnection types are: unprotected bidirectional point to point The steps an operator has to do in order to perform the crossconnection are the following: create the OH TPs involved in the operation create the OH crossconnection: select type of crossconnection select the input OH TP involved in the operation select the output OH TP involved in the operation
After having deleted an OH crossconnection, 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 Passthrough
For STM ports it make sense to allow the operator to perform a total passthrough of the MSOH bytes. A total msoh passthrough connection (connection between msPassThroughCTP points) is setup only if no single msoh passthrough connection are set and if no single msoh crossconnection are set. If a total msoh passthrough connection is set, a single msoh passthrough connection or a single msoh crossconnection cannot be set. The steps an operator has to do in order to perform the total MSOH passthrough are the following: create the msPassThroughCTP points involved in the operation create the total MSOH passthrough: select the input msPassThroughCTP point involved in the operation select the output msPassThroughCTP point involved in the operation After having deleted a total MSOH passthrough, the involved msPassThroughCTP points have to be deleted.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
16.3 Overhead views

The Overhead Views allows to perform the previously presented operations.
To access select Overhead option from the Configuration pull down menu; the following options are presented in the cascading menu, as shown in the following figure: OH Cross Connection See next para. OH Phone Parameters See para.16.7 on page 219. OH TP creation OH TP deleting See para.16.5 on page 217. See para.16.6 on page 218.
Figure 145. Overhead options The options are described in next paragraphs.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 (see Figure 146. on page 212 ) and allows to start the configuration.
Figure 146. Cross Connection Management for OverHead dialog It is similar to the dialog used for the crossconnection of the TP for paths, then the same description and functions are valid. Next configuration steps use the Main Cross-Connection for OverHead (see Figure 147. on page 212) dialog and the TP Search dialog (see Figure 94. on page 132), also in this case already described for path management.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 147. Main Cross-Connection for OverHead dialog
ED
04
957.130.112 X
For all details, navigation and sequences on these views refer to chapter 15 on page 163. 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 crossconnection/termination operation involving them has been performed. deleted AFTER a crossconnection/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. 16.4.1 Cross-Connection Management for OverHead dialog See Figure 146. on page 212 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 readonly list as a result of the search operation. For each crossconnection/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
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 crossconnection dialog. the create button is always enabled. It brings up the Main crossconnection Dialog.
When some operation may affect the existing traffic, the operator is warned about that, and a confirmation dialog must be answered to carry on/cancel the operation. The choices for this dialog are: yes/no for single items, yes to all/cancel for multiple items Not Supported operation
When used for OH purposes, the Cross-Connection Management dialog doesnt support the following functionalities:
1AA 00014 0004 (9007) A4 ALICE 04.10
Protect cross connections/terminations: all the OH cross connections/terminations are unprotected Activate/Deactivate cross connections/terminations: all connections/terminations are automatically active since their creation 04 SC.3:NE MANAGEMENT 3AL 78987 AA AA 268 213 / 268 the OH cross
ED
957.130.112 X
16.4.1.1 Main Cross-Connection for OverHead dialog See Figure 147. on page 212. According to the philosophy of offering only meaningful operations to the user, and being the OH crossconnection operations a subset of those applying to the general cross connections (e.g:protections are not allowed), some fields of this dialog are disabled. By clicking on the proper portions of the dialog and on the proper buttons, the operator can perform the operations hereafter listed: selection of the crossconnection type selection of the input TP involved in the crossconnection selection of the output TP involved in the crossconnection
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 and one output TP. It is possible to directly type in the TP name or to click on the Choose button to select a TP from the TP Search dialog box
When modifying an existing cross connection, the same operations are available. Some changes, may be trafficaffecting, as they may imply a temporary cross connections destruction. In these cases a proper dialog box forces the user to confirm the operation. In the proper part of the dialog, an icon shows the icon of the selected existing cross connection. For OH handling, these icons cannot be used to change the topology.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
16.4.1.2 TP Search dialog The TP Search dialog (see Figure 94. on page 132) 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 SERGI board of slot 05 The auxiliary channels are: 1 x G.703 2 Mbit/s; in the screen is indicated as: r01sr1sl05/port#01P Expanding this TP 31 referred TP are presented
2 x G.703 64Kbit/s; in the screen are indicated as: r01sr1sl05/port#02P r01sr1sl05/port#03P
2 x V11; in the screen are indicated as: r01sr1sl05/port#01#01v11TTP r01sr1sl05/port#02#01v11TTP
4 x V24; in the screen are indicated as: r01sr1sl05/port#01#01v24TTP r01sr1sl05/port#02#01v24TTP
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1 x phonic interface (voice channel): in the screen are indicated as: r01sr1sl05/port#01#01q23TTP Expanding this TP four referred TP are presented: r01sr1sl05/port#01#001q23TTP r01sr1sl05/port#01#002q23TTP r01sr1sl05/port#01#003q23TTP r01sr1sl05/port#01#004q23TTP These TPs permit to connect the voice channel toward four directions.
The other boards used to terminate or crossconnect the OH bytes are the STMn boards. The OH TP are present in MS, RS and VC4 TP Class. In these TPs the indication ......#0011 to 0099 (MS or RS) are referred to the coordinates of the Section OverHead bytes on the SDH frame (1,1 to 9,9). The voice channel are identified by the ow indication, the FU is for Future Use, the NU is for National Use, UC is for User Channel and Pass is for Passthrough channel.
The examples of the figure in this OH connection chapter can be helpful to the operator.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
16.5 OH TP creation
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu the OH TP creation option. The OH TP creation dialog opens (see Figure 148. ) and allows to create the OH TP to cross connect. In detail, the dialogbox contains the following graphical object: a Choose button is used to display a list of OH Tps to be created. The Choose button starts the TP Search (see Figure 149. ) with predefined filtering; the TP Search dialog allows the operator to visualize only not created OH Tps. To visualize the OH TP in the TP Search view double click on the MS, RS or VC4 Tp. OH Tp field displays the label of the selected OH Tp to be created.
Apply button is used to perform a create request of the tp displayed in the OH Tp field. After having performed the create request, the OH Tp field is set to empty. Close button close the dialog without changes of the data. Help button provides some useful information about the dialog.
Figure 148. OH TP creation
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 149. OH Search TP for creation
ED
04
957.130.112 X
16.6 OH TP deleting
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu the OH TP deleting option. The OH TP deleting dialog opens (see Figure 150. ) and allows to delete the OH TP no more involved in an OH crossconnection. In detail, the dialogbox 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 crossconnected 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. Close button close the dialog without changes of the data. Help button provides some useful information about the dialog.
Figure 150. OH TP deleting
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
16.7 OH Phone Parameters

The OH phone parameters option permits to configure the telephone number and to manage the parameter phonic extension. Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu the OH Phone Parameters option. Figure 151. opens.
Figure 151. Phone Parameters dialog window In the window are presented: the interface field (at the top) where can be selected the phonic interfaces to be configured. It identifies a TP indicated as q23TTP, referred to the physical voice connection on the SERGI unit in slot 5. the phone number field, to set the telephone number for operator call on the phonic interface. The phonic extension field, where enable or disable the extension of the selected phonic interface. If enabled the phonic signal is extended towards the external on the access panel of the NE.
Apply button performs the configuration change of the modified phone parameters of the selected phonic interface without close the dialog Close button close the dialog without changes of the data.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
220 / 268
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 Errored Seconds (ES) and Severely Errored 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.
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 ro display the same
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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. The following performance counters are supported: Background Block Error (BBE): A BBE counter measures the number of errored blocks which do not occur as part of an SES. Errored Second (ES): A one second period with one or more errored blocks or with a defect. Severely Errored Second (SES): A one second period which contains > 30% of errored blocks, or at least one Severely Disturbed Period (SDP). An SES is also counted as an ES. NearEndUnAvailable Second (NEUAS/UAS): An Unavailable Second is a second which is part of the Unavailable Time. Far End Background Block Error (FEBBE): A far end errored block which does not occur as part of an FESES. Far End Errored Second (FEES): Identifies, at a terminal, a one second period with one or more errored blocks or with a defect which were received by the Far End Terminal. Far End Severely Errored Second (FESES): Identifies, at a terminal, a one second period which contains > 30% of errored blocks, or at least one Severely Disturbed Period (SDP) which was received/detected by the Far End Terminal. An FESES is counted as an FEES. Far End UnAvailable Second (FEUAS): An Unavailable Second is a second which is part of the Unavailable Time at the far end. In case of bidirectional TP only one UAS performance data is obtained, counting both the Near End and Far End terminal values.
Further definitions: Errored Block (EB): A block in which one or more bits associated with the block are erroneous. Far End Block Error (FEBE): Identifies, at a terminal, the count of errored blocks that were received by the far end terminal. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
17.1.3 Far End Performance Counting Far end performance monitoring parameters are derived from Far End Block Errors and Far End Receive Failures which are transmitted in the overhead bytes. Both near end and far end counters are supported in receive direction of the signal for all path layers of SDH, and for the multiplex section layer. For the regenerator section, no far end information is transmitted and, therefore, only near end counting is supported. Node A Node B Far End Counter at Node B, RX side
Source FERF bits
Sink FERF bits FERF insertion
FESES
Far End Counter at Node A, TX side FESES
Sink FERF insertion
Source
FERF bits
FERF bits
Figure 152. 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. N.B. In case of near end failures, far end errors cannot be counted.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
17.1.4 Granularity A monitoring period of defined granularity is associated with each performance counter. This NE supports unidirectional PM of 15 minute and 24 hour granularity and bidirectional PM for 24 hour granularity. After the monitoring period has elapsed, the performance data is stored in the associated history data log. Time stamping of history records is performed using UTC (as for all alarms). The measurement intervals start at 00 : 00 (UTC) for 24-hour periods and at xx : 00, xx : 15, xx : 30 and xx : 45 for 15-minute periods. 17.1.5 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
17.1.6 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 a dialog. The system behavior concerning the clearance of 15 min. and 24 h TCAs differs: 15 min. (explicit clearance): A TCA is only indicated once in the alarm manager, even if the same threshold is crossed several times a day. TCAs are automatically cleared by the system after one error-free 15 min. interval. 24 h (implicit clearance): A TCA is indicated for each interval in which the related threshold has been crossed. The system implicitly clear TCAs, at the end of the 24 hours.
The following limitations apply for explicit clearance: The value of the low threshold is fixed to 0 (only a single threshold is provided by a threshold table). An SES threshold crossing is cleared at the end of the interval if no unavailability was detected and SES had not reached the low threshold (low threshold equal to 0). Even in case of a suspect interval the TCA is cleared if no unavailability was detected and the low threshold had not been reached. Additionally an explicit clearance of TCAs for all granularity periods is executed if one of the following events occurs during the current interval: deletion of the current data instance, resetting of counters, increased thresholds (higher than current value of counters).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
17.2 Configuration
Use menu item Add TP to display a special TP in the Transmission menu (see para.14.5 on page 131). Select the TP and open the PM Configuration dialog (see Figure 153. ) by clicking on the menu item 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 (see para.11 on page 95). N.B. To configure PM for au4CTPs and tuxCTPs, Path Overhead Monitoring (POM) or Supervised Unequipped Termination (SUT, not supported) must be created first (see description in para. 14.11 on page 146 ).
The PM Configuration dialog is designed as a notebook consisting of a text field, to identify the selected TP, and page labels.
1AA 00014 0004 (9007) A4 ALICE 04.10
The selected TP is indicated in the first box at the top of the screen: TP Identifier. In case of au4CTP and tuxCTPs, the PM Configuration dialog also contains an option button showing the configured POM and SUT option (see Figure 153. ).
ED
04
957.130.112 X
N.B.
As long as the PM Configuration dialog is open, a modified POM/SUT 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: NE15, near end 15 minutes page NE24, near end 24 hours page FE15, far end 15 minutes page FE24, far end 24 hours page
Each dataset has to be configured independently.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 153. PM Configuration Dialog
ED
04
957.130.112 X
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 and three for 24 hours 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 exceed 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 Figure 156. ) and configure the threshold table (see Chapter 17.5 on page 233). Select button Remove to disassociate the threshold table from the entity.
1AA 00014 0004 (9007) A4 ALICE 04.10
N.B.
A threshold table can only be attached if Data Collection is enabled.
Confirm the configuration with the button Apply before closing the dialog. Otherwise the configuration is lost.
ED
04
957.130.112 X
17.3 Display Current Data

Use menu item Add TP to display a special TP in the Transmission view (see para.14.5 on page 131).
Select the TP and open the Current PM Data dialog (see Figure 154. ) by clicking on the menu item Display Current Data.
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 (see para.11 on page 95). The Current PM Data 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, the Current PM Data dialog also contains an option button showing the configured POM and SUT option (see Figure 154. ). This option is the highest PM criteria, i.e. select the POM or SUT option first and then the subordinate granularity period. 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)
1AA 00014 0004 (9007) A4 ALICE 04.10
All datasets available which are related to the selected TP and recorded in the current monitoring interval are displayed in this dialog.
ED
04
957.130.112 X
N.B.
The entry Unavailable ThresholdCrossed indicates, that both alarms are active. Since the text field is too small to display the full text at a time, use the cursor to scroll the text field in this case.
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.
Reset button is used to restart the counting period. Two buttons are present for nearend and farend periods. At the bottom the PM results are listed. N.B. If no printer is installed, there is no error message displayed to indicate this. Press the Refresh button to update the window contents and display the latest data.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 154. Current PM Data Dialog
ED
04
957.130.112 X
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 (ThresholdCrossed) alarms.
17.4 Display History Data

Use menu item Add TP to display a special TP in the Transmission view (see para.14.5 on page 131).
Select the TP and open the PM History Data dialog (see Figure 155. ) by clicking on the menu item Display History Data.
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 (see para.11 on page 95). The PM History Data 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, the PM History Data dialog also contains an option button showing the configured POM and SUT option (see Figure 155. ). This option is the highest PM criteria, i.e. select the POM or SUT option first and then the subordinate granularity period. 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)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 (see para.17.1.5 on page 224) susp indicating suspect data where collection errors occurred during the collection period.
In case of 15 min. entities, a maximum of 16 datasets recorded in the previous 16 monitoring interval can be displayed simultaneously for each counter, the 24h entities display a maximum of 1 dataset. These figures cannot be changed by the user. If the limit of 16 datasets for 15 min. granularity and 1 dataset for 24 h granularity is reached, the oldest set in the list is cleared when the next data set arrives. N.B. If no printer is installed, there is no error message displayed to indicate this.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 155. PM History Data Dialog
ED
04
957.130.112 X
17.5 PM THRESHOLD TABLE SELECTION

The PM Threshold Table Select dialog (see Figure 156. ) pops up if the Attach button is clicked in the PM Configuration dialog (see Figure 153. ). 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. The tables are individually indicated with a number. Each table is dedicated to a specific entities, as reported in Table 3. 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 (see Figure 153. )
The user has to close the dialog explicitly by clicking on the button Close.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Figure 156. PM Threshold Table Select
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
234 / 268
Table 3. Threshold table entities association
N 1 2 3 4 5 6 7 8 9 10 11 12 13 14 STM4 STM4 STM1 STM1 STM4 STM4 STM1 STM1 VC4 VC4 VC3 VC3 VC12 VC12
layer RS RS RS RS
TPs ASSOCIATED
granularity 15 minutes 24 hours 15 minutes 24 hours 15 minutes 24 hours 15 minutes 24 hours 15 minutes 24 hours 15 minutes 24 hours 15 minutes 24 hours
MS NE / FE MS NE / FE MS NE / FE MS NE / FE Path Termination NE / FE Path Termination NE / FE Path Termination NE / FE Path Termination NE / FE Path Termination NE / FE Path Termination NE / FE
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
17.6 PM Threshold Table Creation / Modification / Display

17.6.1 Creation The PM Threshold Table Create dialog (see Figure 157. on page 237) pops up when the Create button is clicked in the PM Threshold Table Selection dialog (see Figure 156. on page 234). Carry out the following steps to create a threshold table: 1) Enter the table name in input field Name. Leading and successing blanks are ignored. Leaving the input field blank or entering only blanks is not allowed and rejected. Select a Granularity of 15 min. or 24 h for the entity. Enter the upper threshold value (Value Up). Table 4. on page 238 shows the allowed maximum performance parameter values. The lower value (Value Down) is not available in the current release. Select the alarm Severity for each PM attribute in case a threshold is crossed. Disable Send notification if no notification message should be sent in the case of a crossed threshold. Confirm the entries with Apply to create the threshold table. A number of threshold tables can be created from the same window.
2) 3)
4) 5)
6)
Explicitly close the window with button Close.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
Figure 157. Create PM Threshold Table
3AL 78987 AA AA
268
237 / 268
17.6.2 Modification The PM Threshold Table Modify dialog (see Figure 158. ) pops up if a threshold table is selected in the PM Threshold Table Selection dialog (see Figure 156. ) 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 4. shows the allowed maximum performance parameter values. The lower value (Value Down) is fixed to 0 in the current release . 2) 3) Modify the alarm Severity for each PM attribute in case a threshold is crossed. 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) 5) Confirm the modifications with Apply. To modify more than one threshold table, do not close the dialog, but select the next threshold table in the PM Threshold Table Selection dialog and press the Modify button (see Figure 156. ).
Explicitly close the dialog with button Close. 17.6.3 Display The PM Threshold Table Display dialog (similar to Figure 158. ) pops up if a threshold table is selected in the PM Threshold Table Selection dialog (see Figure 156. ) and the Display button is clicked. Refer to the previous chapter for a description of the attribute values and types. Table 4. Maximum Performance Parameter Values
Performance Parameter
BBE, FEBBE on STM-4 BBE, FEBBE on STM-1 BBE, FEBBE on all the other board OFS, ES, UAS, FEES, SES, FESES
Max. Value for 15-min. period

8,639,100 2,159,100 539,100 900 810
Max. Value for 24-h period

829,353,600 207,273,600 51,753,600 86,400 78,760
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Figure 158. Modify PM Threshold Table
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
239 / 268
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
240 / 268
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 Freerunning mode that will be explained later. The simplified figure that follows represents the internal organization of the SETS.
Selector A
Squelch A Squelch B
Selector C
T4
T1 T2 T3
Selector B OSC
SETG
T0
SETS S15 Y
Figure 159. Internal organization of the SETS. The internal sources (inputs) are:
1AA 00014 0004 (9007) A4 ALICE 04.10
T1: Reference obtained from incoming STMN signals, T2: Reference obtained from incoming 2 Mbits signals, T3: 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.
ED
04
957.130.112 X
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.
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 priority level is determined by the Operator for each candidate timing source. It is static information. On the other hand, the quality of the source is dynamic information, dependant of the quality of the reference clock generating the timing. In an SDH signal frame, the quality of the timing source is located in the 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). HoldOver mode: The external timing reference is malfunctioning. The SETG during normal functioning stores regularly the value of the external timing reference. In this case the SETG output is controlled by this memorized value. Free running mode: This is not a normal operating mode. The external timing reference and the memorized timing reference are malfunctioning. In this case the SETG output is controlled by the internal clock source.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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, SSU Configuration, Remove Timing Reference, Set T0 Equal T4, Remove T0 Equal T4, Transmitted SSM Quality 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 (see Figure 160. ). Using menu options, select the Synchronization option from the Views pull down menu as shown in the following figure.
Figure 160. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
18.2.2 Synchronization View The Synchronization view shows the external timing reference sources and the T0, T4, 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 in Figure 161.
Figure 161. Synchronization View Example
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Synchronization View Description The synchronization view provides two list of allowable timing references:
one for T0 timing output; T0 list is always present; one for T4 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 configurable by the operator.
T4 list contains : 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 ( Figure 172. ) to visualize the alarm detail.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 boxes contained a label field are used to represent the squelch statuses T0/T4 and T4. The box dis plays 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; 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 signal (or T0_Test signal) box is drawn when T0 signal is used to generate T4.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
18.2.3 Timing Source Configuration This functionality allows to configure the input synchronization sources and configure or modify the timing source priority and quality.
Figure 162. Synchronization Menu The menu options are greyed 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 ( Figure 162. ). Then select the Timing Source Configuration option from the cascading menu, as shown in the above figure. The following dialogue box is opened.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 163. Timing source configuration for crossconnect equipments The Timing source configuration dialogue box displays the extracted quality of the selected timing source. It permits to configure the following timing source information: Quality level, Priority level
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 164. shows the opened windows. Following the TP Search procedure described in para.14.5.1 on page 131 ( 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 all the available empty synch. sources both for T0 clock and for T4 clock.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 164. 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. Dont 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 can not 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 (racksubrackboardport) is written on the window bottom left.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
18.2.4 Synchronization Protection Commands Select the timing reference from the synchronization view. As in Figure 162. , select the Synchronization pull down menu. You can then select the Protection Commands to open the Figure 165. Menu options are greyed according to the current state of the selected timing source.
Figure 165. 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. Invoke/Release Force and Manual Selection of Timing Source
b)
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. The forced switch mode is terminated by releasing 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 (Figure 159. ) 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 of Figure 166. Click on the SSM Algorithm to select/deselect it. Wait To Restore Time button and Revertive option button are disabled Selecting Synchronization > T4 Configuration it is possible to set the T4 squelch criteria in the bottom dialog box of Figure 166. This functionality allows to configure 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 Figure 159. ): 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 Figure 159. ) :T1 may be squelched if T1 Quality Level is lower than the programmable threshold or if it becomes unavailable.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Figure 166. Configuring the T4 SSM algorithm and the squelch criteria 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
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 is presented Figure 167.
Figure 167. SSU Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
18.2.7 Remove Timing Reference Select the synch. source to remove and click on the Remove Timing Reference option (Figure 168. ). To remove the selected source click on OK button of the confirmation message (Figure 169. ).
Figure 168. Synchronization source removing To remove the selected source click on OK button of the confirmation message (Figure 169. ).
Figure 169. Synchronization source removing confirmation
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
18.2.8 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 170.
Figure 170. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
18.2.9 Transmission of SSM Quality Configuration Select the T1 SDH Reference Source in the Synchronization View (Figure 161. ) hence the Transmission SSM Quality Configuration is enabled. This selection allows, with the Inserted option, to transmit the system internal T0 clock quality towards the external SDH interface. It is also possible to transmit different quality level selecting a different value. Click on Transmitted SSM Quality Configuration of the Figure 171. opens. Synchronization menu option.
Figure 171. 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
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
18.2.10 Show Timing Source Selecting any T1 or T2 Reference Source in the Synchronization View (Figure 161. ) hence the Show Timing Source is enabled. This selection allows to analyze 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 172. opens.
Figure 172. Timing Source Example
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
SC.3:NE MANAGEMENT
3AL 78987 AA AA
268
258 / 268
19 SOFTWARE MANAGEMENT 19.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.
Software Management OPERATOR MANAGER Download Control
Event Report Transfer Request
AGENT NE CLIENT
Software Downloading OPERATOR
SERVER
Binary & Data Files
Figure 173. Software Download general principle
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
19.1.1 Naming Conventions The naming conventions used for Download Management are the following: Software Package: Software Package stands for a piece of software which can be executed by an NE of a particular type. It consists in one or more Software Units and a Descriptor File. A software package is identified by its name, release, version and edition. On the NE (i.e. once downloaded) a software package can be: the active version: the software package currently running on the NE 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
19.2 Software download operative sequence

Two main different operative condition are defined for this Equipment:
First installation of a 1650SMC 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 1650SMC with an already installed software. Follow the operative indications of para. 19.2.1 on page 261 .
19.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, as for the procedure of para 19.2.2 on page 262. open a session on Craft Terminal application (startup of the application, start supervision and NE login) Check the present status of the software on a selected NE. Download should not be performed in presence of unstable alarms d) e) Open the Download menu as for para. 19.3 on page 263. Select the new software package in the server and triggers the download process, as presented at para.19.4 on page 264. A message will indicate the completed download. Activate the package as presented at para.19.5 on page 266. Check that the activated package is in the Commit status. If problems are found with the new activated package, activate the previous software package (revertback operation) to come back to the previous condition and then try to repeat the procedure.
b)
c)
f) g) h)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
19.2.2 NE Software package installation procedure Before to begin the software download choose one of this two procedure: 1) Install from CD ROM the NE Software Package on the Personal Computer, as explained in the 1320CT Basic Operator Handbook. Run the Sotware Administration menu from Network Equipment Synthesis, as explained in the 1320CT Basic Operators Handbook. In the window that opens select the directory where the NE software package file has been installed ( tipically is Alcatel/usm/ect/swdw/<equipment name>/<version>/<descriptor file> ) and execute. 2) Simply insert the CD ROM in the drive of the Personal Computer. Run the Software Administration menu from NES as explained in the 1320CT Basic Operators Handbook. Select the NE software package file directly from the CD ROM and execute (tipically ect/swdw/ <equipment name>/<version>/ <descriptor file> At this point the NE Software Package is installed in another directory and available to be downloaded as explained from para. 19.3 on page 263.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
19.3 Software Download Manager menu

All the software download operations are carried out from the software download manager.
Figure 174. 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 175. Download menu

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
19.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 176. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
04
957.130.112 X
Click on the OK push button to start the download. From the confirmation dialogue box that opens, you can confirm or cancel the download. If you confirm the operation, the SW Downloading dialogue box then disappears and the Software download in Progress dialogue box is displayed (see Figure 177. ) from which you can if necessary abort the software download. 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 177. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
19.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. The following dialogue box is opened.
Figure 178. 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, 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 standby 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 action = activate serves to activate the selected SW package action = force
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
Select the Activate option of the CurrentState\Action field, to activate the Software package The Sw units Det. button allows to give more information about a selected software package.
Clicking on it, the following window is displayed:
Figure 179. Detail software package (example) Clicking on [] symbol behind each software package all details disappear. When you click on Close the previous view is displayed (Figure 178. ). In Figure 178. when you click on the: OK push button you close dialogue box, Cancel push button you close the SW Information dialogue box, Help push button you access to help on context.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
04
957.130.112 X
19.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:
Figure 180. 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 to choose 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 to delete a backup of the NE database. The NE is not involved in this action. The only effect is to delete the selected backup version stored in a specific directory of the FT server.
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
To save or load the Mib to/from an external disk follow the indication of the Basic 1320CT Operators Handbook using the menu options of the Network Element Synthesis.
END OF DOCUMENT ED
04 SC.3:NE MANAGEMENT 3AL 78987 AA AA 268 268 / 268
957.130.112 X
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.2 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 MAINTENANCE INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 MAINTENANCE OF THE PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 PROBLEMS WITH CRAFT TERMINAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Purpose of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 CORRECTIVE MAINTENANCE (TROUBLESHOOTING) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Purpose of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Troubleshooting organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 On site Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Troubleshooting by means of the Craft Terminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Preliminary Concepts and Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 Alarms/states view Organization (subrack view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3 Alarm synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.4 Alarm Surveillance (AS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.5 Port View alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.6 Board view alarms and states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.7 Subrack view alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.8 Equipment View alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9 External Points alarms (HouseKeepings) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 UNIT REPLACEMENT WITH A SPARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 COMPACT ADM unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 CONGI unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 05 04 01 030521 001124 991216 DATE CHANGE NOTE S.MAGGIOJ.MIR ITAVE C. FAVERO R.LEONARDUZZI ITAVE C. FAVERO R.LEONARDUZZI ITAVE E.CORRADINI APPRAISAL AUTHORITY 3 5 5 5 5 5 5 5 7 9 11 11 11 13 13 13 15 18 19 20 21 23 28 30 32 33 34 35 36 40
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
ED
05
SC.4:NE MAINTENANCE 3AL 78987 AA AA 46 1 / 46
957.130.112 X
7 UPGRADING WITH NEW HARDWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 SYNTH substitution with SYNTHN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 P4S1, S41, L41, L42 substitution with P4S1N, S41N, L41N, L42N . . . . . . . . . . . .
41 41 45
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X

FIGURES Figure 1. General Flowchart for on site troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2. Power supply alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3. Transmission network level structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4. Alarms/status view Organization (subrack view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5. Alarm pull down menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6. Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7. Example of Port View alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 8. Example of board view alarms and status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 9. Example of daughter View alarms and status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 10. Example of Subrack view alarms and status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 11. Example of Equipment View alarms and status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 12. Example of External Points alarms and status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 13. COMPACT ADM unit replacement (EPS protected) part A . . . . . . . . . . . . . . . . . . . . . . . Figure 14. COMPACT ADM unit replacement (EPS protected) part B . . . . . . . . . . . . . . . . . . . . . . . Figure 15. COMPACT ADM unit replacement (EPS not protected) . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 16. Upgrading with a new SYNTHN EPS not protected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 17. Upgrading with a new SYNTHN EPS protected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TABLES Table 1. Alarms colors and Severity association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2. Alarm Synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3. Domain Alarm Synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4. Management States Control Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5. Alarm Surveillance information general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6. General aspect of alarms meaning and relevant maintenance actions . . . . . . . . . . . . . . . . Table 7. Boards alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16 17 19 20 23 23 29 31 31 32 33 34 37 38 39 42 44
21 21 22 22 24 25 26
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
SC.4:NE MAINTENANCE
3AL 78987 AA AA
46
4 / 46

1.1.1 Document scope The Maintenance Manual mainly describes the NE troubleshooting with Craft Terminal. 1.1.2 Target audience The Maintenance Manual is intended for all users. The documents that should be read before starting this document are: 1320CT Basic Operators Handbook
The documents of this Handbook that should be read before starting this document are: Introduction manual NE Management manual
1.2 Terminology
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
SC.4:NE MAINTENANCE
3AL 78987 AA AA
46
6 / 46
2 MAINTENANCE INTRODUCTION
The maintenance procedures consist of the following steps:
Maintenance of the PC. See Chapter 3 on page 9 Problems with Craft terminal (shutdown and restart of the PC). See Chapter 4 on page 11. Corrective Maintenance (Troubleshooting). See Chapter 5 on page 13. Unit replacement with a spare. See Chapter 6 on page 35.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
SC.4:NE MAINTENANCE
3AL 78987 AA AA
46
8 / 46
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
With regard to maintenance PC, refer to the constructors documentation.
05
3 MAINTENANCE OF THE PC
957.130.112 X
SC.4:NE MAINTENANCE
3AL 78987 AA AA
46
9 / 46
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
SC.4:NE MAINTENANCE
3AL 78987 AA AA
46
10 / 46
4 PROBLEMS WITH CRAFT TERMINAL 4.1 Purpose of the procedure

This procedure describes the Shutdown and restart the PC should the Craft Terminal SoftWare Product not be working properly or not responding to the operators commands.
4.2 Procedure
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
SC.4:NE MAINTENANCE
3AL 78987 AA AA
46
12 / 46
5 CORRECTIVE MAINTENANCE (TROUBLESHOOTING) 5.1 Purpose of the procedure

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 flowcharts 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 (backpanel, 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. 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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) 2) 3) 4) the equipment is not managed by a TMN or by a Remote Craft terminal (RCT) the equipment is not reachable by the remote manager (TMN or RCT) and is therefore isolated link problems are present 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 coverplate. 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 coverplate). 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
1AA 00014 0004 (9007) A4 ALICE 04.10
the YELLOW LED to light up the RED LED to go off
On the front coverplate: yellow LED (ATTENDED) to light up red LEDs NOT URGENT (MINOR) and URGENT (MAJOR and CRITICAL) to turn off (free to accept other alarms) 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. 05 SC.4:NE MAINTENANCE 3AL 78987 AA AA 46 14 / 46
ED
957.130.112 X
5.3 On site Troubleshooting

The troubleshooting operation proceeds according to the information indicated in the flowcharts:
Figure 1. on page 16: General flowchart Figure 2. on page 17: Power supply alarm
and according to para.5.4 on page 18. As indicated in the flowcharts 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 cordconnected to the relative connector on the COMPACT ADM unit front coverplate (F interface). The Craft Terminal applications provide detailed information on the alarm state thus facilitating fault location and subsequent removal as indicated in para. 5.4 on page 18. 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 flowcharts 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 flowcharts/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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
START
AN ALARM IS PRESENT
IN CASE OF URGENT OR NOT URGENT ALARM ATTEND IT WITH THE BUTTON ON THE EQUICO UNIT
IS THE EQUICO BICOLOR LED RED?
NO
IS THE EQUICO UNIT RED LED URGENT (MAJOR) ON ? YES YES IS NO ONE OF THE BICOLOR LEDS INDICATING UNIT FAILURE RED? YES NO TRANSITORY FAILURE REPLACE THE UNIT IN ALARM. BY CONNECTING THE PC AND ACCORDING THE TYPE OF FAILURE AND THE TRAFFIC DAMAGE THE FAULTY UNIT CAN BE REPLACED (OR NOT) IN CASE OF LOW TRAFFIC . NO
THROUGH PUSHBUTTON RESET THE UNIT
DOES THE ALARM CONDITION PERSIST ? YES
THE UNIT IS FAULTY. REPLACE IT ACCORDING TO THE DESCRIBED PROCEDURE (see chapter 6 on page 35)
CONNECT THE PC TO THE EQUIPMENT AND, ACCORDING TO THE TYPE OF DETECTED ALARM, PROCEED AS STATED IN PARA 5.4 ON PA GE 18
YES END
YES END
IS THE NO EQUICO UNIT NOT URGENT (MINOR) YELLOW LED ON ? YES
IN EQUICO UNIT THE INDICATION (WARNING) YELLOW ALARM IS ON. MAINTENANCE OPERATION MUST BE PERFORMED ON THE EQUIPMENT CONNECTED TO THE LOCAL ONE. CONNECT THE PC AND ACCORDING TO THE TYPE OF ALARM PROCEED AS INDICATED IN PARA 5.4 ON PA GE 18
CONNECT THE PC TO THE EQUIPMENT, AFTER HAVING DETECTED THE TYPE OF FAILURE, ESTABLISH IF INTERVENTION MUST BE IMMEDIATE OR NOT AS STATED IN THE RELATIVE PARA 5.4 ON PA GE 18
END
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 1. General Flowchart for on site troubleshooting
ED
05
957.130.112 X
WARNING!
Before removing CONGI unit from subrack, switchoff 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.
ALL LEDS OFF
START
IS REMOTE ALARM TAND PRESENT ? (N.B.) YES STATION POWER SUPPLY FAILURE
NO
OVERLOAD LIKELY TO HAVE BEEN CAUSED BY ONE OF THE ASSEMBLY UNITS. SUBSTITUTE THE FUSE ON THE CONGI UNIT
YES ARE LEDS ACTIVE?
TRANSITORY OVERLOAD
YES END NO REMOVE ALL THE UNITS FROM THE SUBRACK AND SUBSTITUTE THE FUSE IF NECESSARY. INSERT THEM BACK ONE AT A TIME TILL THE ONE CAUSING THE FAILURE IS DETECTED. HENCE REPLACE IT. SUBSTITUTE THE FUSE IF NECESSARY.
END
N.B.
IF THE REMOTE ALARMS ARE NOT UTILIZED CHECK FOR PRESENCE OF STATION POWER SUPPLY. SHOULD IT HAVE FAILED THEN ALL THE UNITS LEDS WILL BE OFF (FOLLOW OUTPUT YES OF THE FLOWCHART). IF POWER SUPPLY IS PRESENT PROCEDE WITH OUTPUT NO.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 2. Power supply alarm
ED
05
957.130.112 X
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. The troubleshoot procedure with the the Craft Terminal consists of the following steps: a) The alarms/status view organization for the equipment is shown in Figure 4. pg. 20. 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 2. on page 21 describes the meaning of these alarms/statuses and the relevant maintenance actions. 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 5.4.4 on page 23 describes this view. It is possible to analyze the detailed alarm presence on the TPs of each ports of the NE, following the indication of para 5.4.5 on page 28. 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 5.4.6 on page 30 and para 5.4.8 on page 33. Eventual housekeeping alarms can be localized following the indications given in para. 5.4.9 on page 34. 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. 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).
b)
c)
d)
e)
f)
g)
In case of unit replacement, follow the indications reported in Chapter. 6 on page 35. 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 inform the operator of the ALS forced condition. After having completed the maintenance, enable the ALS. The ALS states are indicated in the port view, as described in para. 5.4.5 on pg. 28.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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 nor 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:TUAIS, TU LOP). 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 orderwire 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.
G.703 STMN G.703 STMN TRIBUTARIES SDH MUX REGENERATOR SDH MUX STMN SDH MUX TRIBUTARIES
RSOH REGENERATOR SECTION
RSOH REGENERATOR SECTION
MSOH MULTIPLEXER SECTION
POH PATH
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 3. Transmission network level structure
ED
05
957.130.112 X
5.4.2 Alarms/states view Organization (subrack view) Severity alarms synthesis Menu bar Domain alarms synthesis
View title
Boards Alarms
View area
Administrative state indications
Message/status area
Management status control panel
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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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 2. on page 21. The alarms EXTP, EQP, TRNS are part of the Domain Alarms Synthesis area, presented inTable 3. on page 22. The alarms SUP, LAC, Q3, MGR, AC are part of the Management States Control Panel, presented in Table 4. on page 22. All these indications (except for SUP, LAC, Q3, MGR,) 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: 5.4.4, 5.4.5, 5.4.6, 5.4.7, 5.4.9. Table 1. reports the association between the colors of the Alarms and their Severity. 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 Table 1. Table 1. Alarms colors and Severity association
Alarm Color RED ORANGE YELLOW CYAN WHITE GREEN
Severity CRITICAL MAJOR MINOR WARNING INDETERMINATE NO ALARM
Table 2. Alarm Synthesis indication Mnemonic CRI Alarm/Status Description Critical alarm Maintenance Synthesis of alarms that needs immediate troubleshooting (typical: NE isolation). NB1. See detailed indication in the following para. Synthesis of alarms that needs immediate troubleshooting. NB1. See detailed indication in the following para. Synthesis of alarms for which a delayed troubleshooting can be defined. NB1. See detailed indication in the following para.
MAJ
Major (Urgent) alarm
MIN
Minor (Not urgent) alarm
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
Mnemonic WNG
Alarm/Status Description Warning alarm
Maintenance Synthesis of alarms due to failure of other NE in the network. NB1. See detailed indication in the following para. Synthesis of alarms not associated to the previous severities. Not operative. See detailed indication in the following para.
IND
Indeterminate alarm
Table 3. Domain Alarm Synthesis indication Mnemonic EXTP SYNC EQP TRNS Alarm/Status Description External Point (Housekeeping alarm) Synchronization alarm Equipment alarm Transmission alarm Maintenance Check the relevant station alarm associated to the input housekeeping indication. See detailed indication in the following para. Synthesis of alarms of the Synchronization domain. See unit detailed indication in the following para. Synthesis of alarms of the Equipment domain. See unit detailed indication in the following para. Synthesis of alarms of the Transmission domain. See unit detailed indication in the following para.
Table 4. Management States Control Panel. Mnemonic SUP Description Supervision state Maintenance GREEN: NE is under supervision. BROWN: NE is not under supervision. Used in the OS. 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). GREEN: Identifies the Enable operational state of 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)
Local Access State
Q3
Operational System Isolation
GREEN: Indicates that the N.E. is not managed by the 1354RM MGR Manager level CYAN: Indicates that the N.E. is not managed by the 1354RM GREEN: normal operating condition. CYAN: detection of an ABNORMAL operative condiAC Abnormal Condition tion. 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 synthesis.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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 5. ). 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.
Figure 6. Alarm Surveillance Detailed information of each alarm are 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
In the following are shortly described the main information obtained in the AS view, starting from the left column:
Table 5. Alarm Surveillance information general description
TITLE Perceived Severity Event date and time Friendly Name
DESCRIPTION The severity assigned to the alarm is indicated, with the relevant color, i.e.: MAJOR, MINOR, WARNING.... Indicates year, month, day and hour of the alarm. Identify the rack, subrack, board, port, and TP in which the alarm is detected, i.e.: / r01sr1sl09/#port01E1S Indicates the family type of the alarm as subdivided in the ASAP list, i.e.: EQUIPMENT, COMMUNICATION, The fault/problem is indicated, i.e.: loss of signal, transmitter degraded, replaceable unit missing,resource isolation, ... Indicates if the alarm is reserved (RSV) or not (NRSV) according security management. Indicates if the alarm condition is terminated (CLR) or is still active (NCLR). If cleared it has a green background, Indicates if the alarm has been acknowledge (ACK) with the button on the COMPACT ADM unit or not ( NACK).
Event Type
Probable Cause
Reservation Status
Clearing status
Acknowledge status
Correlated notification Not used flag Repetition counter Not used
The information supplied help the operator during the troubleshooting operation. Table 6. on page 25 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 Operators Handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
Table 6. General aspect of alarms meaning and relevant maintenance actions
PROBABLE CAUSE NAME AND/OR ACRONYM OF DISPLAYED ALARM Loss of signal (LOS) Transmitter Signal (TF) Transmitter degraded (TD) Loss of frame (LOF) AIS Excessive BER (EBER) Degraded Signal (DS) Loss of Pointer (LOP) Payload Mismatch (PLM) Far End Received Failure (FERF) Server Signal Failure (SSF) Frequency offset (DRIFT) Loss of timing source (LOSS) Resource Isolation Communication Subsystem Isolation (CSF) Unequipped (U) Referred to Signal Label Unconfigured Equipment Present (UEP) Check line Replace unit
MAINTENANCE
Replace unit when possible (laser degrade) Check line (alignment problems due to line error) Check connected equipment Check line (excessive line BER) Check line (line signal degrade) Check line Configuration error Check farend equipment Check all the TU path. Alarm indicates AIS signal received on the TU Check reference and connection between it and the equipment Check reference and connection between it and the equipment Check connection between NE and Craft Terminal Check Communication configuration (LAPD)
Configuration error
Unit inserted but not declared
Internal Communication ProbReset NE. If persists substitute Compact ADM unit lem TCA Alarm threshold cross Check path / line section interested to the indication.
URU Underlying Resource Insert the board Unavailable
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
Table 7. Boards alarms NAME AND ACRONYM OF DISPLAYED ALARM
MAINTENANCE
Unit missing (RUM)
Unit Problem (RUP)
Unit type mismatch (RUTM)
A2S1 A21E1 A3E3 A3T3 A4ES1 HPROT L41 L41N L42 L42N P3E3/T3 P4ES1N P4S1 P4S1N P63E1 S41 S41N
Insert missing unit
Replace unit
Insert right unit (unit inserted into a slot set with another type of unit)
Unit missing (RUM) Unit Problem (RUP) Unit type mismatch (RUTM) Version Mismatch Internal communication problem (ICP) Unit missing (RUM) Unit Problem (RUP) CONGI Unit type mismatch (RUTM) LAN problem (LAN) SYNTH1 SYNTH1N
Insert missing unit
Replace unit Insert right unit (unit inserted into a slot set with another type of unit) Update software version by means of SW download Internal dialogue problem in the unit. It indicates a temporary condition which will be restored. If the condition persists it is due to a unit hardware failure: in this case it will activate the RUP alarm
Insert missing unit
Replace unit Insert right unit (unit inserted into a slot set with another type of unit) This alarm type is present only on 1650SMC or 1660sm. Check LAN interconnection or substitute CONGI unit
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
BOARD ACRONYM
NAME AND ACRONYM OF DISPLAYED ALARM Unit missing (RUM) Unit Problem (RUP)
BOARD ACRONYM
MAINTENANCE
Insert missing unit
Replace unit SERGI Insert right unit (unit inserted into a slot set with another type of unit) Replace unit.
Unit type mismatch (RUTM) Power Problem (POP)
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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. 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 and Automatic Laser Shutdown state (if they are supported). 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 nonalarmed 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 sign in the box. The alarms which can be found in the Port view are listed in Table 6. pg.25, 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Mouse message Alarms Figure 7. Example of Port View alarms TPs
05
957.130.112 X Protection message
SC.4:NE MAINTENANCE
3AL 78987 AA AA
46
29 / 46
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. Figure 8. and Figure 9. are examples of Boards view. 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: inservice or outofservice. The alarms of the board are reported at the bottom of the message/status area, by means of various boxes containing relevant acronyms. The nonalarmed 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). 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. 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 6. page 25, where the relevant maintenance actions are reported too. In the view can also be present EPS indications. Subboard alarms In case of board with multi access points (i.e. containing subboards) another view permits to select the contained port, named daughter or subboard (see example of Figure 9. on page 31 ). An example of daughter (subboard) view with the presented ports is in Figure 9. on page 31. It is displayed after clicking on it. The alarms which can be found in the subboard view are listed in Table 6. page 25, where the relevant maintenance actions are reported too.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
port alarm synthesis
daughters
Administrative state
Board Alarms/Status
Figure 8. Example of board view alarms and status
port alarm synthesis
Board alarms
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 9. Example of daughter View alarms and status
ED
05
957.130.112 X
5.4.7 Subrack view alarms The alarms and status indications at subrack level can be obtained, following the indications given on the previous Section of this Handbook (NE management). Figure 10. shows an example of subrack view. 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 inservice. Else, the lack of this symbol indicates its outofservice state . (Administrative State information). 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. Severity alarms synthesis Menu bar Domain alarms synthesis
View title
Boards Alarms
View area
Administrative state indications
Message/status area
1AA 00014 0004 (9007) A4 ALICE 04.10
Management status control panel
Figure 10. Example of Subrack view alarms and status
ED
05
957.130.112 X
5.4.8 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. Figure 11. shows the Equipment view, with the alarm indications presented: Fuse Failure AND Battery Failure Substitute the fuse in the CONGI or SERGI unit and search for a cause. Failure of the Service Power Supply connected to the CONGI Rack connector.
These alarms can be observed at OS level.
Equipment alarms
Figure 11. Example of Equipment View alarms and status
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
5.4.9 External Points alarms (HouseKeepings) The alarms and status indications relevant to External Points (housekeepings) 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 nonalarmed condition. the change of color, as assigned by the severity (ASAP) > means alarmed condition.
Figure 12. Example of External Points alarms and status
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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 relate 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 unit refer to the following paragraph. When upgrading an equipment with New Hardware (for example SYNTHN unit) that substitute the old units (for example SYNTH unit), follow the indication given in paragraph 7 on page 41. With regard to the CONGI unit refer to paragraph 6.2 on page 40. WARNING: In order to avoid shortcircuit, before substituting the CONGI unit, switchoff 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 check the integrity of the relative connectors. Dont insert the units that have been damaged during the transport/storing or in a phase before their replacing.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
6.1 COMPACT ADM unit replacement

N.B. In this paragraph for COMPACT ADM is generically intended one of the following unit: SYNTH1 SYNTH1N
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 EPS present or not (typically present) failure on the Main board failure on the Spare board
type of spares available: Spare without software installed. This is the normal condition. Spares with installed software, belonging to the same type of equipment and with SW release identical to the unit to replace. 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. Spares with installed software, belonging to the another type of equipment or unknown SW.
CONGI unit version (read NOTES in Figure 14. on page 38 and Figure 15. on page 39) MIB store in the Craft Terminal or O.S.
The flowcharts of Figure 13. on page Figure 13. and Figure 15. on page 39 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: 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
PROTECTED COMPACT ADM unit
FAILURE ON SPARE
FAILURE ON MAIN YES Force EPS on spare COMPACT ADM
Substitute COMPACT ADM
NO
Craft Terminal manages the NE?
END Substitute main COMPACT ADM
HWPRESET THE NEW UNIT WITH: (Reset Data Base) I11 OFF I12 ON INSERT THE NEW UNIT
WAIT UNTIL THE ACCESS WILL BE RETURNED TO THE C.T.

NEW UNIT HW CONDITION: software of the same release and NE NEW UNIT HW CONDITION: unit with different software NEW UNIT HW CONDITION: unit without software NEW UNIT HW CONDITION: unit with wrong or unknown software Download the NE relevant software release with normal dowload procedure. (see NE management section) Download the NE relevant software release with SIBDL procedure (see SIBDL section)
REMOVE AND HW PRESET THE NEW UNIT WITH: I11 ON I12 ON INSERT THE NEW UNIT AGAIN
CONTINUE REFER TO
Figure 14. on page 38
Figure 13. COMPACT ADM unit replacement (EPS protected) part A

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
CONTINUE FROM
Figure 13. on page 37
I11 ON
REMOVE AND HWPRESET THE NEW UNIT WITH: I12 OFF (Reset Data Base and upload Comm/Routing Tables) INSERT THE NEW UNIT AGAIN
NO
Is the MIB stored in the Craft Terminal?
YES
From O.S. send the saved MIB containing the correct configuration (NB1)
From C.T. send the saved MIB containing the correct configuration (NB1) (see NE management section) From C.T. Activate the sent MIB
From O.S. Activate the sent MIB
REMOVE AND HWPRESET THE NEW UNIT WITH: (Normal operating condition) I11 OFF I12 OFF
INSERT THE NEW COMPACT ADM
IN CASE OF EPS THE DECISION TO FORCE OR NOT TO THE main COMPACT ADM IS LEFT TO THE OPERATOR END
NOTE: NB1: The Comm/Routing tables are automatically retrieved only with CONGI starting from version 3AL 78830AAAC Otherwise the Comm/Routing tables must be configurated manually using the Craft Terminal
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 14. COMPACT ADM unit replacement (EPS protected) part B
ED
05
957.130.112 X
NOT PROTECTED COMPACT ADM unit
Substitute main COMPACT ADM (NB1) HWPRESET THE NEW UNIT WITH: I11 OFF I12 ON (Reset Data Base) INSERT THE NEW UNIT

NEW UNIT HW CONDITION: software of the same release and NE NEW UNIT HW CONDITION: unit with different software NEW UNIT HW CONDITION: unit without software Download the NE relevant software release with normal dowload procedure. (see NE management section)

NEW UNIT HW CONDITION: unit with wrong or unknown software
REMOVE AND HW PRESET THE NEW UNIT WITH: I11 ON I12 ON INSERT THE NEW UNIT AGAIN Download the NE relevant software release with SIBDL procedure (see SIBDL section)
REMOVE AND HWPRESET THE NEW UNIT WITH: I11 ON I12 OFF (Reset Data Base and upload Comm/Routing Tables) INSERT THE NEW UNIT AGAIN
NO
YES
From C.T. send the saved MIB containing the correct configuration (NB2) (see NE management section) From O.S. send the saved MIB containing the correct configuration (NB2) From C.T. Activate the sent MIB
REMOVE AND HWPRESET THE NEW UNIT WITH: NOTES: NB1: with not protected Compact ADM all traffic is lost NB2: The Comm/Routing tables are automatically retrieved only with CONGI starting from version 3AL 78830AAAC Otherwise the Comm/Routing tables must be configurated manually using the Craft Terminal INSERT THE NEW COMPACT ADM END I11 OFF I12 OFF (Normal operating condition)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 15. COMPACT ADM unit replacement (EPS not protected)
ED
05
957.130.112 X
6.2 CONGI unit replacement

When substituting an old CONGI unit (from code 3AL 78830 AAAA to code 3AL 78830 AAAE) with a new CONGI unit (starting from code 3AL 78830 AAAF) must be taken into account the rules reported in the following; this is necessary for the right management of the Fuse Broken alarm on the CONGI units. [1] The alarm Fuse Broken is meaningful (hence it is active) only if two batteries connections (this means that one CONGI and one SERGI in 1650SMC has been equipped) are present. If old CONGI units are present in main slot ( 4 for 1650SMC) it is mandatory to connect the service battery to the front connector (refer to Installation Handbook for details) to correctly activate the alarms. In presence of configurations having 2 CONGI units composed of an old and new type it is mandatory to open TC5 setting (refer to Technical Handbook for details on Hardware settings) on the soldering side of the old type CONGI if the latter is placed in the spare position (slot 5 in 1650SMC). If the old CONGI is maintained in a main slot (slot 4 in 1650SMC), TC5 can be nevertheless closed or open.
[2]
[3]
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
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 identify by the N letter at the end of the acronym unit (for example SYNTHN is the new version, SYNTH 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 SYNTH substitution with SYNTHN

According to the EPS and SNCP SYNTH protection scheme different procedure are available: [1] Upgrading with a new SYNTHN EPS not protected Substituting the old SYNTH all the traffic is lost! Remove the old SYNTH in slot 9 from the subrack Before inserting the new SYNTHN in subrack slot 9, follow the instruction described in Figure 16. on page 42. 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 SYNTHN unit in slot 9 Select the Modify option from the Equipment menu and select the SYNTHN acronym from the list then click on ok. Verify that the RUTM alarm disappear
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
HWPRESET THE NEW UNIT WITH: I11 OFF I12 ON (Reset Data Base) INSERT THE NEW UNIT

NEW UNIT HW CONDITION: software of the same release and NE NEW UNIT HW CONDITION: unit with different software NEW UNIT HW CONDITION: unit without software NEW UNIT HW CONDITION: unit with wrong or unknown software REMOVE AND HW PRESET THE NEW UNIT WITH: I11 ON I12 ON INSERT THE NEW UNIT AGAIN Download the NE relevant software release with normal dowload procedure. (see NE management section) Download the NE relevant software release with SIBDL procedure (see SIBDL section)
REMOVE AND HWPRESET THE NEW UNIT WITH: I11 ON I12 OFF (Reset Data Base and upload Comm/Routing Tables) INSERT THE NEW UNIT AGAIN
NO
YES
From C.T. send the saved MIB containing the correct configuration (NB1) (see NE management section) From O.S. send the saved MIB containing the correct configuration (NB1) From C.T. Activate the sent MIB
REMOVE AND HWPRESET THE NEW UNIT WITH: I11 OFF NOTES: NB1: The Comm/Routing tables are automatically retrieved only with CONGI starting from version 3AL 78830AAAC Otherwise the Comm/Routing tables must be configurated manually using the Craft Terminal I12 OFF (Normal operating condition)
INSERT THE NEW COMPACT ADM END
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 16. Upgrading with a new SYNTHN EPS not protected
ED
05
957.130.112 X
[2]
Upgrading with a new SYNTHN EPS protected Supposing that the two STM1 ports are not network protected, their traffic will be lost during the substitution; the traffic of all the other board will not be lost. Remove first the old SYNTH in slot 10 from the subrack Insert the new SYNTHN into the subrack slot 10; a RUTM (unit type mismatch) alarm will be present. On Craft Terminal in the Subrack level view select the SYNTHN unit in slot 10 Select the Modify option from the Equipment menu and select the SYNTH acronym from the list then click on ok. Verify that the RUTM alarm disappear Force the EPS Switching on SYNTHN in slot 10 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 SYNTH in slot 9 from the subrack Before inserting the new SYNTHN in subrack slot 9, follow the instruction described in Figure 17. on page 44. 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 SYNTHN unit in slot 9 Select the Modify option from the Equipment menu and select the SYNTHN acronym from the list then click on ok. Verify that the RUTM alarm disappear
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
HWPRESET THE NEW UNIT WITH: (Reset Data Base) I11 OFF I12 ON INSERT THE NEW UNIT All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

NEW UNIT HW CONDITION: software of the same release and NE NEW UNIT HW CONDITION: unit with different software NEW UNIT HW CONDITION: unit without software NEW UNIT HW CONDITION: unit with wrong or unknown software REMOVE AND HW PRESET THE NEW UNIT WITH: I11 ON I12 ON INSERT THE NEW UNIT AGAIN Download the NE relevant software release with normal dowload procedure. (see NE management section) Download the NE relevant software release with SIBDL procedure (see SIBDL section)
I11 ON
REMOVE AND HWPRESET THE NEW UNIT WITH: I12 OFF (Reset Data Base and upload Comm/Routing Tables) INSERT THE NEW UNIT AGAIN
NO
YES
From O.S. send the saved MIB containing the correct configuration (NB1)
From C.T. send the saved MIB containing the correct configuration (NB1) (see NE management section) From C.T. Activate the sent MIB
REMOVE AND HWPRESET THE NEW UNIT WITH: (Normal operating condition) I11 OFF I12 OFF
INSERT THE NEW COMPACT ADM
IN CASE OF EPS THE DECISION TO FORCE OR NOT TO THE main COMPACT ADM IS LEFT TO THE OPERATOR NOTES: NB1: The Comm/Routing tables are automatically retrieved only with CONGI starting from version 3AL 78830AAAC Otherwise the Comm/Routing tables must be configurated manually using the Craft Terminal END
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 17. Upgrading with a new SYNTHN EPS protected
ED
05
957.130.112 X
[3]
Upgrading with a new SYNTHN EPS protected with STMN ports SNCP protected The procedure is the same of that described on point [2] on page 43 but without traffic interruption on the STM1 ports present on the SYNTH because SNCP protected.
7.2 P4S1, S41, L41, L42 substitution with P4S1N, S41N, L41N, L42N
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 S41, L41, L42 units respectively with S41N, L41N, L42N 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. Verify that the RUTM alarm disappear
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
SC.4:NE MAINTENANCE
END OF DOCUMENT
3AL 78987 AA AA
46
46 / 46
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.2 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 DOWNLOAD WITH SIBDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Purpose of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.1 SIBDL download procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 CONFIGURATION FOR SIBDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Purpose of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 Remote Access Service configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2 Serial Cable Modem configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 3 3 3 3 3 3 5 5 5 11 11 11 11
03
001124 validated
02A 000906 01
1AA 00014 0004 (9007) A4 ALICE 04.10
991216 DATE CHANGE NOTE
R.LEONARDUZZI ITAVE C. FAVERO R.LEONARDUZZI ITAVE E.CORRADINI R.LEONARDUZZI ITAVE E.CORRADINI APPRAISAL AUTHORITY
ED
ED
03
SC.5: SIBDL 3AL 78987 AA AA 12 1 / 12
957.130.112 X

Figure 1. SIBDL download procedure step 1 Figure 2. SIBDL download procedure step 2 Figure 3. SIBDL download procedure step 3 Figure 4. SIBDL download procedure step 4 Figure 5. SIBDL download procedure step 5 Figure 6. SIBDL download procedure step 6 Figure 7. SIBDL download procedure step 7 ............................................ ............................................ ............................................ ............................................ ............................................ ............................................ ............................................ 6 6 7 7 8 8 9
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
SC.5: SIBDL 3AL 78987 AA AA 12 2 / 12
957.130.112 X

1.1.1 Document 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. See Chapter 2 on page 5 Configuration for SIBDL. Configurations to be performed for SIBDL operation are described. See Chapter 3 on page 11.
1.1.2 Target audience The SIBDL Manual is intended for all users. The documents that should be read before starting this document are: 1320CT Basic Operators Handbook
1.2 Terminology
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
SC.5: SIBDL 3AL 78987 AA AA 12 3 / 12
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
SC.5: SIBDL
3AL 78987 AA AA
12
4 / 12
2 DOWNLOAD WITH SIBDL 2.1 Purpose of the procedure

This procedure describes how to download a 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 doesnt 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 EMLUSM, 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 presented at Chapter 3 on page 11.
To download with SIBDL execute the following steps: 1) Connect the Craft Terminal with the NE: 2) 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.
Start SIBDL, selecting Start > Program>Alcatel>SIBDLversion>SIBDL
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
SC.5: SIBDL 3AL 78987 AA AA 12 5 / 12
957.130.112 X
3)
In the screen which appears (see Figure 1. ) with the command menu, select automatic mode command typing 8 and then ENTER.
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>
Figure 2. SIBDL download procedure step 2 5) Press ENTER
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
SC.5: SIBDL 3AL 78987 AA AA 12 6 / 12
957.130.112 X
6)
This step (see Figure 3. ) ask 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
Figure 3. SIBDL download procedure step 3 7) This step ( see Figure 4. ) ask 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. )
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 4. SIBDL download procedure step 4
ED
03
SC.5: SIBDL 3AL 78987 AA AA 12 7 / 12
957.130.112 X
Figure 5. SIBDL download procedure step 5 8) Type y . The screen shows the automatic download evolution with a final message indicating the completed download (see Figure 6. ). On the contrary repeat the procedure.
Figure 6. SIBDL download procedure step 6
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
SC.5: SIBDL 3AL 78987 AA AA 12 8 / 12
957.130.112 X
9)
Press ENTER.
10 ) In the presented screen type 4 (see Figure 7. ) and ENTER.

Figure 7. SIBDL download procedure step 7 11 ) Extract and reinsert the COMPACT ADM unit to complete the operation. 12 ) From Craft Terminal (EMLUSM) execute the normal download procedure: Select Init download from Download menu Select the SW package to Download and click on OK button 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
SC.5: SIBDL 3AL 78987 AA AA 12 9 / 12
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
SC.5: SIBDL
3AL 78987 AA AA
12
10 / 12
3 CONFIGURATION FOR SIBDL 3.1 Purpose of the procedure

This chapter describes the configurations to be performed for SIBDL operation. 3.1.1 Remote Access Service configuration To install a new modem, the user should have administrator privileges and need the installation CDROM 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 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 Dont 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;

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
SC.5: SIBDL 3AL 78987 AA AA 12 11 / 12
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
03
957.130.112 X
SC.5: SIBDL
END OF DOCUMENT
3AL 78987 AA AA
12
12 / 12
LABELS AND ASSEMBLY INSTRUCTIONS TARGHETTE E INFORMAZIONI PER IL CENTRO STAMPA

QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
COD.MANUALE HDBK P/N: 957.130.112
X Ed.05 3AL 78987 AAAA Ed.05
1650SMC Rel.1.1 Version B6 C.T. OPERATORS HANDBOOK

ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
No PAGINE TOTALI PER ARCHIVIAZIONE: 364+4=368 DIMENSIONE BINDER SORGENTE (du ks): 293.056 kbytes
INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS

STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE: HANDBOOK COMPOSITION AND ASSEMBLY: SERVONO 5 SEPARATORI NUMERATI DA 1 A 5 5 REGISTERS FROM 1 TO 5 ARE NECESSARY No pagine (facciate) No pages TARGHETTE - LABELS FRONTESPIZIO - FRONT INSERIRE SEPARATORE 1 - INSERT REGISTER 1 SC.1: HANDBOOK GUIDE INSERIRE SEPARATORE 2 - INSERT REGISTER 2 SC.2: INTRODUCTION INSERIRE SEPARATORE 3 - INSERT REGISTER 3 SC.3: NE MANAGEMENT INSERIRE SEPARATORE 4 - INSERT REGISTER 4 SC.4: NE MAINTENANCE INSERIRE SEPARATORE 5 - INSERT REGISTER 5 SC.5: SIBDL 12 1/12 12/12 46 1/46 46/46 268 1/268 268/268 16 1/16 16/16 20 1/20 20/20 2 1/2 2/2 numerate numbered da from a to
fase step
1 2 3 4 5 6 7 8 9 10 11 12
1AA 00014 0004 (9007) A4 ALICE 04.10
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: TOTALE FOGLI A4 TOTAL A4 SHEETS:
364 182
ED
05
RELEASED 3AL 78987 AAAA TQZZA 4 Y 1/ 4
957.130.112 X
QUESTA PAGINA NON VA INSERITA NEL MANUALE

THIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
Site VIMERCATE
FCG
Originators P. GHELFI
1650SMC REL.1.1 VERSION B6 C.T. OPERATORS HANDBOOK
Domain Division Rubric Type Distribution Codes
: : : :
OND SDH 1650 SMC 1650SMC REL.1.1 TECHNICAL HANDBOOK Internal : External :
Approvals Name App. S.MAGGIO C. FAVERO J.MIR
Name App.
WARNING FOR A-UNITS OTHER THAN A-ITALY Labels are done according to A-Italy binder format. Source files: ALICE 6.10
957.130.112 X 3AL 78987 AAAA Ed.05 1650SMC Rel.1.1 Version B6 STM 1/4 Multiservice Metro Node C.T. OPERATORS HANDBOOK
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
1650SMC Rel.1.1
Version B6
STM 1/4 Multiservice Metro Node
C.T. OPERATORS HANDBOOK

957.130.112 X Ed.05 3AL 78987 AAAA Ed.05
VOL.1/1
1650SMC Rel.1.1
Version B6 STM 1/4 Multiservice Metro Node C.T. OPERATORS HANDBOOK
957.130.112 X Ed.05 3AL 78987 AAAA Ed.05
VOL.1/1
1650SMC Rel.1.1
Version B6 STM 1/4 Multiservice Metro Node 957.130.112 X Ed.05 3AL 78987 AAAA Ed.05 C.T. OPERATORS HANDBOOK VOL.1/1
1650SMC Rel.1.1
957.130.112 X Ed.05 Version B6 STM 1/4 Multiservice Metro Node 3AL 78987 AAAA Ed.05 C.T. OPERATORS HANDBOOK VOL.1/1
1650SMC Rel.1.1
Version B6 STM 1/4 Multiservice Metro Node
957.130.112 X Ed.05
1AA 00014 0004 (9007) A4 ALICE 04.10
C.T. OPERATORS HANDBOOK
VOL.1/1
ED
05
957.130.112 X
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
05
957.130.112 X
RELEASED
FINE DEL DOCUMENTO INTERNO END OF INTERNAL DOCUMENT
3AL 78987 AAAA TQZZA
4/ 4

1650 Operators Handbook

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

1650 Operators Handbook

Enviado por

Direitos autorais:

Formatos disponíveis

C.T.

3AL 78987 AAAA Ed.05

3AL 78987 AAAA Ed.05

1650SMC REL.1.1 C.T. OPERATORS HANDBOOK

030521 001124 991216 DATE

P.GHELFI ITAVE P.GHELFI ITAVE C.FAVERO ITAVE P.GHELFI ORIGINATOR

1650SMC REL.1.1 Version B6 C.T. OPERATORS HANDBOOK

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 1 / 20

LIST OF FIGURES AND TABLES

1AA 00014 0004 (9007) A4 ALICE 04.10

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 2 / 20

1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK 1.1 General information

1.2 Handbook applicability

1AA 00014 0004 (9007) A4 ALICE 04.10

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 3 / 20

1.3 Purpose of the handbook

1AA 00014 0004 (9007) A4 ALICE 04.10

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 4 / 20

1.4 Handbook configuration check

SECTION EDITION 01 01 01 01 01 02A 02A 02A 02A 02A 03 03 04 03 03 04 03 05 03 04 05 03

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 5 / 20

1AA 00014 0004 (9007) A4 ALICE 04.10

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 6 / 20

ANV Part No.

1650SMC Rel.1.1 Technical Handbook [1]

3AL 78986 AAAA

3AL 79584 AAAA

3AL 79585 AAAA

HANDBOOK 1650SMC Rel.1.1 CT Operators Handbook

ANV Part No.

3AL 78987 AAAA

[4] Provides 1650SMC screens and operational procedures

1AA 00014 0004 (9007) A4 ALICE 04.10

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 7 / 20

ANV Part No.

1320CT Basic Operators Handbook [5]

3AL 79186 AAAA

3AL 71109 AAAA

3AL 71081 AAAA

1320CT CDROMDOC EN [9]

Contains, in electronic format, the following handbooks: REF. [5] to [7]

1AA 00014 0004 (9007) A4 ALICE 04.10

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 8 / 20

Table 5. Optional handbooks common to 1650SM and 1650SMC REF

HANDBOOK S91650SMC1660SM System Installation Handbook

ANV Part No.

FACTORY Part No. 955.100.692 N

3AL 78901 AAAA

3AL 38207 AAAA

1AA 00014 0004 (9007) A4 ALICE 04.10

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 9 / 20

1AA 00014 0004 (9007) A4 ALICE 04.10

1AA 00014 0004 (9007) A4 ALICE 04.10

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 11 / 20

Mouth to mouth resuscitation method

1AA 00014 0004 (9007) A4 ALICE 04.10

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 12 / 20

3.2 Norms and labels

ELECTROMAGNETIC COMPATIBILITY ELECTROSTATIC DISCHARGERS (ESD) EQUIPMENT LABELS

1AA 00014 0004 (9007) A4 ALICE 04.10

SC.1:HANDBOOK GUIDE 3AL 78987 AA AA 20 13 / 20

1AA 00014 0004 (9007) A4 ALICE 04.10

1AA 00014 0004 (9007) A4 ALICE 04.10