Professional Documents
Culture Documents
1662SMC Rel.2.4 - Operator Handbook - Ed 03
1662SMC Rel.2.4 - Operator Handbook - Ed 03
Alcatel 1662SMC
STM4/16 Compact Multiservice Node
1662SMC Rel.2.4
03
09/01/2006
Creation
ED
DATE
CHANGE NOTE
Distribution: Internal
Chen Yu
APPROVED BY
PREPARED BY
1/15
External
ED
03
SC 1: HANDBOOK GUIDE
General information 3
1.2
Handbook applicability3
1.3
1.4
PRODUCT-RELEASE HANDBOOKS 5
3.2
HANDBOOK DESCRIPTION 9
5.2
5.3
5.4
Handbook Updating 12
5.4.1
5.4.2
5.4.3
5.5
ED
5.5.1
5.5.2
5.5.3
CD-ROM identification 15
5.5.4
CD-ROM updating 15
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
2/15
1
1.1
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.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization.
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
PRODUCT
ANV P/N
FACTORY P/N
1662SMC
--
PRODUCT
RELEASE
VERSION(N.B.)
ANV P/N
FACTORY P/N
1662SMC
2.4
--
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 man-machine interface changes or
in case of slight modifications not affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the product-releases version
marking, they are not replaced in the handbooks related to a subsequent version, if the screen
contents are unchanged.
1.3
This handbook describes the operations concerning commissioning, operation and maintenance that the
operators must carry out as indicated by the specific software application(s) referred to in this handbook
This handbook must be used together with the associated Technical Handbook (see Table 1.) and the
1320CT associated documentation (see Table 5.) does not replicate information contained into it.
In particular, all cautions relevant to safety, rules for EMC and ESD, as well as warnings regarding
operations that may cause damages to the equipment, are not duplicated here, but must be retrieved from
the Technical Handbook.
ED
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
3/15
1.4
The structure (hardware composition) and all the possible operating modes of the equipment
(product-release) this handbook refers to.
This handbook is a collection of documents (each contained in a specific section) that can have
editions different from one another.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization.
HANDBOOK EDITION
01
ED
03
02
03
04
05
SECTION EDITION
HANDBOOK GUIDE
INTRODUCTION MANUAL
NE MANAGEMENT MANUAL
MAINTENANCE MANUAL
SIBDL MANUAL
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
4/15
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-releaseversion is stated in para.1.2 consists of the following handbooks:
Table 1. Handbooks related to the specific product hardware
REF
HANDBOOK
FACTORY
THIS HDBK
Part No.
[1]
[2]
Table 2. Handbooks related to the specific product SW management and local product control
REF
HANDBOOK
1662SMC Rel.2.4
FACTORY
THIS HDBK
Part No.
Or note
--
CT Operators Handbook
[4]
ED
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
5/15
REF
HANDBOOK
FACTORY
THIS HDBK
Part No.
Or note
[5]
957.140.552 J
[6]
957.140.652 W
[7]
HANDBOOK
IP Rel.1.0
FACTORY
THIS HDBK
Part No.
Or note
957.140.722 L
Operators Handbook
Provides ATM SMART Terminal screens and operational procedures
HANDBOOK
FACTORY
THIS HDBK
Part No.
1320CT
[8]
957.130.542 E
[9]
ED
957.130.442 A
[10]
957.130.462 E
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
6/15
[11]
CD-ROM TITLE
3AL 98254AAAA
Contains, in electronic format, the following handbooks: REF. [1] to [4] Envisaged after the
release of all handbooks
417.100.031
3AL80739 AAAA
417.100.060
[13]
Contains, in electronic format, the following handbooks: REF. [5] Envisaged after the release of
all handbooks
[14]
417.100.068
IP 1.0 CD-ROM-DOC EN
417.100.084
HANDBOOK
FACTORY
THIS HDBK
Part No.
S9-16xxSM
[16]
955.100.692 N
[17]
955.110.202 L
N.B.
ED
Handbooks REF. [16] and [17] are available only on paper support
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
7/15
3.1
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:
3.2
Refer to the Technical Handbook associated to ALCATELs designed and manufactured equipment to
obtain the following information:
-
SAFETY RULES
General rules
Risk of explosion
ELECTROMAGNETIC COMPATIBILITY
EQUIPMENT LABELS
Identical or similar information on Personal Computer, Work-Station etc., other than ALCATELs, loaded
with software applicative described in this Handbook, is supplied in the Constructors technical
documentation.
ED
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
8/15
HANDBOOK DESCRIPTION
Chapter 1:Handbook structure and configuration check. This chapter gives information on the whole
handbook application, composition and evolution.
Chapter 2: Product-release handbooks. This chapter lists the handbooks the Operator should have
in order to carry out the tasks allowed by the specific product-release this handbook refers to.
Chapter 2: General description of the Craft Terminal. The Craft Terminal is introduced and the
software product listed. The Craft Terminal main functionality in the NE management (EML-USM)
are listed and briefly described.
Chapter 3: Acronyms and abbreviations. The acronyms used in all the operator manuals are listed.
ED
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 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 and Alarm Log file and Internal Link Monitor.
Chapter 8: Communication and Routing management. In this chapter are presented the
communication and routing parameters, concerning the OSI and IP communication protocols for the
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
9/15
local NE, the OS and each other related NE in order to provide a global communication capabilities
inside the network
-
Chapter 9: Equipment management. This chapter deals mainly with the setting and changing of the
boards present on the Equipment and undertaking board protection operations.
Chapter 10: Board view. This chapter permits to show the physical port available in a specific board
(alarm synthesis and port symbol), to access the port and to change the physical interface.
Chapter 11: Port view. This chapter permits to set and show the transmission resources referred to
the Port.
Chapter 12: Equipment protection management. This chapter permits to manage the EPS protection,
setting the relevant configuration.
Chapter 13: Multiplex Section protection management. This chapter permits to manage the MSP
protection.
Chapter 14: Transmission view. This chapter permits to show and set the Termination Point of the
equipment, thus having an overview of the complete signal flow of the various port.
Chapter 15: Cross connection management. This chapter permits to manage the connection of the
paths.
Chapter 16: Overhead management. This chapter permits to manage the Overhead, setting the
relevant configuration.
Chapter 17: Performance Monitoring management. This chapter permits to set and show
Performance Monitoring parameters and data.
Chapter 18: Synchronization management. This chapter permits to set and show Synchronization
parameters and status.
Chapter 19: MSSPRing Management. This chapter permits to set the MSSPRing protection of the
NE
Chapter 20: ISA/IP/ETH Configuration. This chapter describes the operations necessary for the ATM
boards creation and the ATM/IP/ETH TTPs creation.
Chapter 21: Software management. This chapter permits to update the NE by means download
procedure and to manage NE software.
Chapter 3: Maintenance of the Personal Computer. The Personal Computer manual is referred.
Chapter 4: Problems with Craft terminal. Shut Cdown and restart of the PC is indicated.
Chapter 5: Troubleshooting (Corrective Maintenance). Detection location and correction of failure are
presented.
Chapter 7: Upgrading with New Hardware. The Hardware upgrading procedure is detailed.
ED
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
10/15
Chapter 1: Introduction
ED
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
11/15
5.1
A product is defined by the network hierarchical level where it can be inserted and by the whole of
performance and services for which it is meant.
A product evolves through successive product-releases which are the real products marketed for their
delivery at a certain product-release availability date.
So, a product-release defines a set of hardware components and a software package which, as a whole,
identify the possible network applications and the equipment performance which the specific
product-release has been designed, engineered and marketed for.
In some cases a product-release has further development steps, named versions, that are born to
improve or add some performance (mainly software) with respect to the previous version, or for bug fixing
purposes.
A product-release has its own standard Customer Documentation, composed by one or more handbooks.
A new version of a product-release may or may not produce a change in the status of the Customer
Documentation set, as described in para.5.4.
5.2
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
5.4
Handbook Updating
ED
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),
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
12/15
5.4.1
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.
Changes introduced in the same product-release (same handbook P/N)
The edition and date of issue might change on future handbook versions for the following reasons:
-
Only the date changes (pointed out in the Table of Contents) when modifications are made to the
editorial system not changing the technical contents of the handbook.
The edition, hence the date, is changed because modifications made concern technical contents. In
this case:
In each section, the main changes with respect to the previous edition are listed;
In affected chapters of each section, revision bars on the left of the page indicate
modifications in text and drawings (this is done after the first officially released and validated
version).
Changes concerning the technical contents of the handbook cause the edition number increase (e.g. from
Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition of a
version character (e.g. from Ed.02 to Ed.02A).
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operators Handbooks) are not modified
unless the new software version distributed to Customers implies man-machine interface hanges
or in case of slight modifications not affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the product-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 who have already received previous issues is submitted to
commercial criteria.
By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue
(supplying errata-corrige sheets is not envisaged).
5.4.3
A new product-release change the handbook P/N and the edition start from 01. In this case the modified
parts of the handbook are not listed.
ED
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
13/15
5.5
In most cases, a CD-ROM contains the documentation of one product-release(-version) and for a certain
language.
In some other cases, the same CD-ROM can contain the documentation of different Product-release (version) s for a certain language.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization.
As a general rule:
CD-ROMs for Network Management products do not contain:
The Installation Guides
The documentation of system optional features that Customers could not buy from Alcatel together with the
main applicative SW.
CD-ROMs for Network Elements products do not contain the documentation of system optional features (e.g.
System Installation Handbooks related to racks that Customers could not buy from Alcatel together with the
main equipment).
A CD-ROM is obtained collecting various handbooks and processing them by
Interleaf-World-View-Press after the manual addition of some hyperlinks that make the navigation through
the various handbooks easier. No additional information is added to each handbook; so that the
documentation present in the CD-ROMs is exactly the same the Customer would receive on paper.
The files processed in this way are then transferred on a PC where the viewer (Interleaf-World-View) is
added and a master CD-ROM is recorded.
Suitable checks are made in order to have a virus-free product.
After a complete functional check, the CD-ROM image is electronically transferred to the archive of the
Production Department, so that the CD-ROM can be produced and delivered to Customers.
5.5.2
Processor: Pentium
RAM: 32 Mbyte
The set-up procedure is present in the booklet included in the CD-ROM box.
After the set-up procedure, which installs the viewer in the PC or Unix WS environment, the Customer is
allowed to read the handbooks on the PC/WS screen, using the navigation and zooming tools included in the
viewer, and to print selected parts of the documentation through a local printer.
N.B. Copyright notification
WorldView:
Copyright 1981-1996
INTERLEAF Inc.
ED
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
14/15
5.5.3
CD-ROM identification
The name of the product-release(s) (and version when the CD-ROM is applicable to the
versions starting from it, but not to the previous ones),
2) And, internally, by the list of the source handbooks and documents (P/Ns and editions) by whose
collection and processing the CD-ROM itself has been created.
5.5.4
CD-ROM updating
The list of source handbook/document P/Ns-editions indicated in previous para.5.5.3 point 2), in association
with the CD-ROMs own P/N-edition, is also loaded in the Alcatel-Information-System as a structured list.
Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive system, the
Alcatel-Information-System automatically rises a warning toward the Customer Documentation department,
indicating the list of CD-ROMs that must be updated to include the new editions of these
handbooks/documents.
This causes the planning and creation of a new edition of the CD-ROM.
Updating of CD-ROMs always follows, with a certain delay, the updating of the single handbooks composing
the collection.
END OF DOCUMENT
ED
03
SC 1: HANDBOOK GUIDE
3AL 98253 ADAA
15/15
03
09/01/2006
Creation
ED
DATE
CHANGE NOTE
Distribution: Internal
Chen Yu
APPROVED BY
PREPARED BY
External
ED
03
SC.2:Introduction
3AL 98253 ADAA
1/15
INTRODUCTION .......................................................................................................................................4
1.1
Scope4
1.1.1
Document scope...........................................................................................................................4
1.1.2
Target audience............................................................................................................................4
1.2
Reading rules 4
1.2.1
2
Introduction 5
2.2
2.2.1
2.2.2
2.3
2.3.1
2.3.2
2.3.3
Security Management...................................................................................................................7
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
Protection management................................................................................................................8
2.3.10
2.3.11
2.3.12
2.3.13
Synchronization management..................................................................................................9
2.3.14
ATM/IP/ETH Configuration.......................................................................................................9
2.3.15
ED
03
SC.2:Introduction
3AL 98253 ADAA
2/15
TABLES
Table 1. Software products part numbers ..........................................................................................................6
ED
03
SC.2:Introduction
3AL 98253 ADAA
3/15
INTRODUCTION
1.1
Scope
1.1.1
Document scope
The Introduction Manual presents the Craft Terminal main functions and provides a general overview of the
different functionalities provided by the ELMUSM of the Craft Terminal for Info Model NE.
1.1.2
Target audience
1.2
Reading rules
1.2.1
Menu options
All the manuals describe menus, but not necessarily all the options of these menus. When a menu option is
not detailed in a manual, the information is surely given in another manual.
ED
03
SC.2:Introduction
3AL 98253 ADAA
4/15
2.1
Introduction
The Craft Terminal is a project in charge of the local management of single network elements, providing
ITU compliant Information Model Interface to the Network Element.
Multiple NE management up to 32 Network elements is possible obtaining a remote Craft Terminal
application.
The general information of the Craft Terminal are presented in the Basic Craft Terminal Operators
Handbook, which the operator has 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.
A detailed description of the EMLUSM screens is given in Section Ne Management of this handbook.
From the Craft Terminal is possible to run another Specific Software application. This application is in charge
of the ATM and IP management inside the NE such as ATM/IP crossconnection, Backup and Restore
configuration files etc.
Details information about Specific Application are described in the relevant Operators Handbook (see
Section 1 HANDBOOK GUIDE for the code).
The list and part numbers of the SDH software products distributed by Alcatel is inserted in para.2.2.
The Craft Terminal characteristic (computer configuration) are listed in the Basic Craft Terminal Operators
Handbook.
2.2
2.2.1
ED
03
SC.2:Introduction
3AL 98253 ADAA
5/15
2.2.2
Every Software Product is identified by a denomination and a part number, listed on the following table.
Table 1. Software products part numbers
Name
415.100.666 N
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
N.B.
700.200.301 X
700.200.302 Y
700.200.303 Z
3AL98185 AAAA
700.200.304 S
700.200.305 T
LICENCE FEE
SWLB 1662SMC Rel. 2.4
LICENCE FEE
SWLC 1662SMC Rel. 2.4
LICENCE FEE
SWLLCT 1662SMC Rel. 2.4
LICENCE FEE
SWLRCT 1662SMC Rel. 2.4
LICENCE FEE
N.B. 1
License alternative for Network Element software features:
SWLA: Full functionality set
SWLB: Improved functionality set
SWLC: Basic functionality set
N.B. 2
License alternative for Craft Terminal software features:
SWLLCT: Local Craft Terminal functionality
SWLRCT: Remote Craft Terminal functionality
2.3
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
03
SC.2:Introduction
3AL 98253 ADAA
6/15
2.3.2
Security Management
Deals with housekeeping signals input from the external (station alarms) or forwarded (output) towards the
external.
Display External points
Configure External points
2.3.5
Diagnosis management
For real time alarm reporting and subsequent fault localization and correction.
Alarm Surveillance
The alarms concerning a particular managed entity will be represented in a synthetic way in all the views
concerning the entity.
Alarms information are detailed in the Alarms Surveillance Manual
Abnormal Condition list (as result of operators commands)
Event log Manager
Permits to have access to the Event Log file.
Remote Inventory (upload and view remote inventory)
Internal Link Monitor
2.3.6
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
ED
03
SC.2:Introduction
3AL 98253 ADAA
7/15
IP Configuration
Tunneling Configuration
2.3.7
Deals with the presentation of the equipment and the hierarchical tree structure, permitting to define the
types of boards present. The Board view permits to access the Port view.
Set / modify / remove boards
Software information of the selected board.
Remote Inventory
2.3.8
Port management
This permits to set and show the transmission resources (TP) referred only to the port (SDH, PDH, HOA
ATM and IP).
It is used to check the detailed alarm of each TP and to configure them (many options are the same of the
Transmission view).
For each port a specific menu is available where various configuration of the specific port can be set, for
example:
Automatic Laser Shutdown
MSP protection
Loopback management and configuration
Single fiber configuration
TP Frame Mode Configuration
Retiming
Ethernet Port Configuration
Port view is also the entry point of other management functions:
Performance Monitoring management
Cross Connection management
For each port are presented:
The various 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:
Equipment protection switching
Multiple Section Protection
2.3.10 Transmission management
This permits to cover the management of the transmission resources, opening the views of all the specific
ports of the NE (SDH and PDH).
ED
03
SC.2:Introduction
3AL 98253 ADAA
8/15
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, T5 and T6 configuration
Protection commands
2.3.14 ATM/IP/ETH Configuration
Describes the operations necessary for the ATM/IP/ETH boards and the ATM/IP/ETH TPs creation.
2.3.15 Software management
Deals with the manipulation of the software package within NE.
Software download refers to the NE software, permitting to charge the software in the relevant NE to
upgrade the NE software, thus following product evolution, or as a consequence of substitution with a spare.
Backup and restore on the MIB of the NE.
ED
03
SC.2:Introduction
3AL 98253 ADAA
9/15
ED
03
SC.2:Introduction
3AL 98253 ADAA
10/15
XC: CrossConnection
ED
03
SC.2:Introduction
3AL 98253 ADAA
11/15
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
ED
03
SC.2:Introduction
3AL 98253 ADAA
12/15
them.
Flushing:
This deals with logs. When a log is flushed, all its records are deleted.
Functional Access Domain:
It defines the range of functions which are available to a specified user.
Gigabits per second:
Unit that corresponds to the transmission of 10 9 bits every second.
ED
03
SC.2:Introduction
3AL 98253 ADAA
13/15
ED
03
SC.2:Introduction
3AL 98253 ADAA
14/15
User Profile:
Identifies the functionalities of the Craft Terminal to which a user has access. A finite number of predefined
user profiles is determined by a fixed set of FADs. To give user access to Craft Terminal functionality, the
administrator must assign a profile to a UNIX user account by choosing one among the predefined profiles
installed with Craft Terminal.
User Service Manager:
These are presentation processes used by the Craft Terminal to manage the Human Machine Interface and
facilitate the interaction with the product.
Wrapping:
Wrapping is the technique that enables the most recent entries in a file to replace the oldest when a file is full.
END OF DOCUMENT
ED
03
SC.2:Introduction
3AL 98253 ADAA
15/15
03
09/01/2006
Creation
ED
DATE
CHANGE NOTE
Distribution: Internal
Chen Yu
APPROVED BY
PREPARED BY
External
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
1/396
INTRODUCTION .....................................................................................................................................21
1.1
1.1.1
Document scope.........................................................................................................................21
1.1.2
Target audience..........................................................................................................................21
1.2
Scope21
Terminology21
1.2.1
1.2.2
Glossary of terms........................................................................................................................21
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.2.8
2.2.9
2.2.10
2.2.11
2.2.12
2.2.13
2.3
3
NE management states40
3.2
4.1.1
4.1.2
Switching from the Craft Terminal access state back to the OS access state ...........................43
4.2
NE Time management43
4.3
Alarm Configuration 45
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
2/396
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
Alarms resynchronization........................................................................................................52
4.3.6
4.4
Restart NE54
5.2
6.1.1
6.2
7
Alarms surveillance 62
7.2
7.3
7.4
Log Browsing 66
7.5
Remote Inventory67
7.5.1
7.5.2
8.1.1
8.1.2
8.1.3
8.1.4
8.2
8.3
Local Configuration 75
8.4
OS Configuration 76
8.5
8.6
LAPD Configuration79
8.7
Ethernet Configuration 82
8.8
8.9
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
3/396
8.10
IP Configuration 86
8.10.1
8.11
8.12
8.13
8.14
8.15
OSI over IP 91
8.16
IP over OSI 91
9.2
9.3
9.4
9.4.1
9.4.2
9.4.3
9.5
Software description104
9.6
Remote Inventory105
9.7
10
BOARD VIEW........................................................................................................................................109
10.1
Introduction 109
10.2
11
10.2.1
10.2.2
10.2.3
PORT VIEW...........................................................................................................................................114
11.1
Introduction 114
11.2
11.3
11.4
11.5
11.6
ED
11.6.1
11.6.2
11.6.3
11.6.4
Ms Configuration ..................................................................................................................128
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
4/396
11.6.5
11.6.6
11.6.7
11.6.8
11.6.9
LCAS Configuration..............................................................................................................134
11.7
11.8
11.9
11.10
11.11
12
Introduction 148
12.2
12.3
12.4
12.5
13
Architecture types161
13.2
13.3
13.4
13.4.1
MSP modification..................................................................................................................166
13.5
MSP Delete167
13.6
13.7
MSP Commands170
13.8
14
Overview 177
14.2
14.3
14.3.1
View Description...................................................................................................................178
14.3.2
14.3.3
Naming TPs..........................................................................................................................179
14.3.4
14.4
14.5
Add TP181
14.5.1
ED
03
TP Search.............................................................................................................................182
SC.3: NE MANAGEMENT
3AL 98253 ADAA
5/396
14.6
TP Configuration 188
14.6.1
14.6.2
14.6.3
14.7
14.8
TP Threshold Configuration195
14.9
Terminate/Disterminate TP196
14.9.1
Terminate TP........................................................................................................................196
14.9.2
Disterminate TP....................................................................................................................196
14.10
Monitoring Operations197
14.10.1
Creation/Deletion..................................................................................................................197
14.10.2
Configuration ........................................................................................................................199
14.11
Structure TPs201
14.12
Loopback 202
14.12.1
14.12.2
Loopback Management........................................................................................................204
14.13
14.13.1
14.14
15
Set Domain...........................................................................................................................208
14.14.1
Expand .................................................................................................................................209
14.14.2
Hide ......................................................................................................................................209
14.14.3
14.14.4
14.14.5
Cross-Connection Management.........................................................................................................214
15.1
Introduction 214
15.1.1
Overview...............................................................................................................................214
15.1.2
15.1.3
15.1.4
15.1.5
Cross-Connection Types......................................................................................................222
15.1.6
15.2
15.3
Cross-Connections management228
ED
15.3.1
Search Criteria......................................................................................................................230
15.3.2
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
6/396
15.3.3
15.4
15.4.1
15.4.2
Create a Cross-Connection..................................................................................................240
15.4.3
15.5
Actions available...................................................................................................................234
15.5.1
Activate a Cross-Connection................................................................................................248
15.5.2
Deactivate a Cross-Connection............................................................................................248
15.5.3
15.6
15.6.1
Split a Cross-Connection......................................................................................................249
15.6.2
15.7
15.8
Print 253
15.9
16
Introduction 256
16.2
OH Connection overview256
16.3
Overhead views257
16.4
OH Cross Connection258
16.5
OH TP creation 262
16.6
OH TP deleting 264
16.7
17
ED
Introduction 266
17.1.1
Overview...............................................................................................................................266
17.1.2
17.1.3
17.1.4
17.1.5
17.1.6
17.1.7
17.1.8
17.1.9
17.1.10
17.1.11
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
7/396
17.1.12
Thresholds............................................................................................................................271
17.2
17.3
17.3.1
Overview...............................................................................................................................276
17.3.2
17.3.3
17.3.4
17.4
17.5
17.6
17.7
17.7.1
Creation ................................................................................................................................286
17.7.2
Modification ..........................................................................................................................288
17.7.3
Display..................................................................................................................................288
17.8
17.9
17.10
17.11
PM Overview293
18
Synchronization management............................................................................................................297
18.1
Introduction 297
18.2
19
18.2.1
18.2.2
18.2.3
18.2.4
18.2.5
18.2.6
SSU Configuration................................................................................................................307
18.2.7
18.2.8
18.2.9
18.2.10
18.2.11
18.2.12
MS-SPRING introduction315
19.2
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
8/396
19.2.1
19.3
19.3.1
19.4
MS-SPRING Management316
19.4.1
19.4.2
19.4.3
19.5
20
MS-SPRING Protection Status and Commands for 2 fiber terrestrial application 328
19.5.1
19.5.2
19.5.3
19.5.4
ISA/IP/ETH CONFIGURATION.............................................................................................................362
20.1
Introduction 362
20.2
21
20.2.1
20.2.2
PR_EA boards......................................................................................................................365
20.2.3
20.2.4
20.2.5
20.2.6
20.2.7
ISA-ES16 board....................................................................................................................379
Software Management.........................................................................................................................382
21.1
21.1.1
21.2
21.2.1
21.2.2
21.2.3
Procedure .............................................................................................................................384
21.3
21.4
21.5
21.6
Mib management395
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
9/396
FIGURES
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Figure 5.
Figure 6.
Figure 7.
Figure 8.
Figure 9.
Figure 10.
Figure 11.
Figure 12.
Figure 13.
Figure 14.
Figure 15.
Figure 16.
Figure 17.
Alarm re--synchronization...........................................................................................................52
Figure 18.
Figure 19.
Figure 20.
Restart NE confirmation..............................................................................................................54
Figure 21.
Figure 22.
Figure 23.
Figure 24.
Figure 25.
Figure 26.
Figure 27.
Figure 28.
Figure 29.
Figure 30.
Figure 31.
Alarm Surveillance......................................................................................................................63
Figure 32.
Figure 33.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
10/396
Figure 34.
Figure 35.
Figure 36.
Figure 37.
Figure 38.
Figure 39.
Figure 40.
Figure 41.
Figure 42.
Figure 43.
Local Configuration.....................................................................................................................76
Figure 44.
OS Configuration ........................................................................................................................77
Figure 45.
Figure 46.
Figure 47.
TP search dialog.........................................................................................................................80
Figure 48.
Figure 49.
Figure 50.
Ethernet Configuration................................................................................................................83
Figure 51.
Figure 52.
Figure 53.
Figure 54.
Figure 55.
Figure 56.
Figure 57.
Figure 58.
Figure 59.
IP over OS ..................................................................................................................................92
Figure 60.
Figure 61.
Figure 62.
Figure 63.
Figure 64.
Equipment menu.........................................................................................................................98
Figure 65.
Figure 66.
Figure 67.
Figure 68.
Figure 69.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
11/396
Figure 70.
Figure 71.
Figure 72.
Figure 73.
Figure 74.
Figure 75.
Figure 76.
Figure 77.
Figure 78.
Figure 79.
Figure 80.
Figure 81.
Figure 82.
Figure 83.
Figure 84.
Figure 85.
Figure 86.
Figure 87.
Figure 88.
Examples of port menu options (SDH, PDH and ATM port) ....................................................117
Figure 89.
Figure 90.
Figure 91.
Figure 92.
Figure 93.
Figure 94.
Figure 95.
Figure 96.
Figure 97.
Figure 98.
Figure 99.
Figure 100.
Figure 101.
Ms Configuration ..................................................................................................................128
Figure 102.
Figure 103.
Figure 104.
Figure 105.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
12/396
Figure 106.
Figure 107.
Figure 108.
Figure 109.
Figure 110.
LCAS Configuration..............................................................................................................136
Figure 111.
Figure 112.
Figure 113.
Figure 114.
Figure 115.
Figure 116.
Figure 117.
Figure 118.
Figure 119.
Figure 120.
Figure 121.
Figure 122.
Figure 123.
Figure 124.
Figure 125.
Figure 126.
Configure EPS......................................................................................................................153
Figure 127.
Figure 128.
Figure 129.
Figure 130.
Figure 131.
Figure 132.
Figure 133.
Figure 134.
Figure 135.
Figure 136.
Figure 137.
TP Search.............................................................................................................................164
Figure 138.
Figure 139.
Figure 140.
Figure 141.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
13/396
Figure 142.
Figure 143.
Figure 144.
Figure 145.
Figure 146.
MSP overview.......................................................................................................................172
Figure 147.
Figure 148.
Figure 149.
Figure 150.
Figure 151.
Figure 152.
Figure 153.
Information Window..............................................................................................................182
Figure 154.
Figure 155.
Figure 156.
Symbols in TP Search..........................................................................................................184
Figure 157.
Figure 158.
Figure 159.
Figure 160.
Print to Printer.......................................................................................................................187
Figure 161.
Figure 162.
Figure 163.
Figure 164.
Figure 165.
J0 Configuration ...................................................................................................................191
Figure 166.
Figure 167.
Figure 168.
Figure 169.
Figure 170.
Figure 171.
Figure 172.
Figure 173.
Figure 174.
Figure 175.
Figure 176.
Figure 177.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
14/396
Figure 178.
Figure 179.
Figure 180.
Loopback Management........................................................................................................205
Figure 181.
Figure 182.
Figure 183.
Figure 184.
Set Domain...........................................................................................................................208
Figure 185.
Expand option.......................................................................................................................209
Figure 186.
Figure 187.
Figure 188.
Figure 189.
Figure 190.
Figure 191.
Figure 192.
Figure 193.
Figure 194.
Figure 195.
Bidirectional Connection.......................................................................................................223
Figure 196.
Figure 197.
Figure 198.
Figure 199.
Protected Broadcast.............................................................................................................225
Figure 200.
Figure 201.
Figure 202.
Figure 203.
Figure 204.
Figure 205.
Protection Criteria.................................................................................................................237
Figure 206.
Figure 207.
Figure 208.
Figure 209.
Figure 210.
Figure 211.
Figure 212.
Figure 213.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
15/396
Figure 214.
Figure 215.
Figure 216.
Figure 217.
Figure 218.
Figure 219.
Figure 220.
Figure 221.
Figure 222.
Figure 223.
Figure 224.
OH TP creation.....................................................................................................................262
Figure 225.
Figure 226.
OH TP deleting .....................................................................................................................264
Figure 227.
Figure 228.
Figure 229.
Figure 230.
Figure 231.
Figure 232.
Figure 233.
Figure 234.
Figure 235.
Figure 236.
Figure 237.
Figure 238.
Figure 239.
Figure 240.
Figure 241.
PM Port View........................................................................................................................286
Figure 242.
Figure 243.
Figure 244.
Figure 245.
Figure 246.
Figure 247.
Figure 248.
Figure 249.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
16/396
Figure 250.
Figure 251.
Figure 252.
PM Overview ........................................................................................................................294
Figure 253.
Figure 254.
Figure 255.
Figure 256.
Figure 257.
Figure 258.
Synchronization Menu..........................................................................................................302
Figure 259.
Figure 260.
Figure 261.
Figure 262.
Figure 263.
SSU Configuration................................................................................................................308
Figure 264.
Figure 265.
Figure 266.
Figure 267.
Figure 268.
Figure 269.
Figure 270.
Figure 271.
Figure 272.
T4 equal T0 setting...............................................................................................................313
Figure 273.
Figure 274.
Figure 275.
Figure 276.
Figure 277.
Figure 278.
Figure 279.
Figure 280.
Figure 281.
Figure 282.
Figure 283.
Figure 284.
Figure 285.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
17/396
Figure 286.
Figure 287.
Figure 288.
Figure 289.
Figure 290.
Figure 291.
Figure 292.
Figure 293.
Figure 294.
Figure 295.
Figure 296.
Figure 297.
Figure 298.
Protection and working channels where the lockout command can be activated (2F) ........330
Figure 299.
Figure 300.
Tail-end / head-end protection with a lockout working and a one direction failure (2F).......331
Figure 301.
Figure 302.
Figure 303.
Figure 304.
Figure 305.
Figure 306.
Figure 307.
Figure 308.
Figure 309.
Figure 310.
Figure 311.
Figure 312.
Figure 313.
Figure 314.
Figure 315.
Figure 316.
Figure 317.
Figure 318.
Figure 319.
Figure 320.
Protection status with double ring failure (reference point-OS-AN) recovering to "idle" ......349
Figure 321.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
18/396
Figure 322.
Figure 323.
Figure 324.
Figure 325.
Figure 326.
Figure 327.
Figure 328.
Figure 329.
Figure 330.
Figure 331.
Figure 332.
Figure 333.
Figure 334.
Figure 335.
Figure 336.
Figure 337.
Figure 338.
Figure 339.
Figure 340.
Figure 341.
Figure 342.
Figure 343.
Figure 344.
Figure 345.
Figure 346.
Figure 347.
Figure 348.
Figure 349.
Figure 350.
Figure 351.
Figure 352.
Figure 353.
Figure 354.
Figure 355.
Figure 356.
Figure 357.
Download menu....................................................................................................................391
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
19/396
Figure 358.
Figure 359.
Figure 360.
Figure 361.
Figure 362.
TABLE
Table 1.
Table 2.
Table 3.
Table 4.
Table 5.
Table 6.
Table 7.
Table 8.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
20/396
1
1.1
1.1.1
INTRODUCTION
Scope
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
1.2.1
Terminology
Acronyms and abbreviations
Glossary of terms
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
21/396
In this chapter the organization of the EML--USM screen, presented after the NE login, is described.
First is introduced the view organization, then the accessible menu options are listed.
At the end some further advice are given for Navigation principles.
2.1
The EML--USM view (see Figure 1) is the first window presented to the operator after the login.
It contains the following fields, which provide you with information needed to manage the NE:
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 perform all the configuration and
supervision and display the specific selected item.
The view organization is detailed in the Basic Craft Terminal Operator Handbook to which refer for the
description, except for the following information, that differs according the NE type:
-- Domain alarm synthesis
The different alarm domain type in which can be subdivided the NE is: Synchronization, External Point,
Equipment, and Transmission.
Information about the alarms and status is given in the Maintenance section of this handbook.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
22/396
Figure 1.
2.2
The menu bar allows performing configuration and supervision functions on the Network Element.
This paragraph lists all the menu options and then more details on the relevant contained entries.
For each of them the relevant operative functions are briefly introduced.
The flow charts of Figure 2., Figure 3., Figure 4., Figure 5., summarize the menu options.
From chapter 3 on details and operative information on the all the views are given. They are not presented
according the menu option sequence but according a functional subdivision.
In the menu bar there are permanent menu items always displayed. Staring from the left, the menus are:
ED
Permanent Menus
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
23/396
Further, in the menu bar there are other menus, presented as an alternative, only when a particular object or
option is selected.
Other Menus
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
24/396
This menu permits to navigate among the views and set some parameters, by means of the following entries:
Backward:
Forward:
Equipment:
Open the Equipment view. The "Equipment" menu and the "EPS" menu are
then available on the menu bar.
External Points:
on the menu bar.
Open the External Point view. The "External Point" menu is then available
Transmission:
the menu bar.
Synchronization:
Open the Synchronization view. The "Synchronization" menu is then
available on the menu bar
Refresh:
The aim of the refresh feature is to avoid a misalignment between the CT
and the managed NE. This misalignment is due to a loss of notifications coming from the NE.
Open Object:
Navigate and show the contents of the selected object: the current view
change. It is equivalent to a double click on the selected object in the view area.
Open in Window:
Navigate and show the contents of the selected object. The current view
doesn't change but a new window with a new view is opened.
Close:
2.2.2
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:
Set SdhNe Alarm severities: Send the Alarm Severity Assignment Profile referred to the equipment
level.
NE Time:
Performance:
Manage the Performance Monitoring domain. Used to define the PM
parameters, opening the following menu options:
- Threshold table
ED
EPS overview:
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
25/396
Loopback Management: Enter the loopback management. Used to configure the loopback command
for commissioning or maintenance purposes.
Comm/Routing: Enter the Communication and Routing management. Used to define the parameters
for NE and OS in the TMN, opening the following menu options:
Local configuration
OS Configuration
Interfaces Configuration
LAPD Configuration
Ethernet Configuration
RAP Configuration
MESA Configuration
IP Configuration
-
Tunneling Configuration
-
OSI Over IP
IP over OSI
Overhead: Handle the operation on the Overhead bytes. Used to define the parameters in the following
menu options:
-
OH Cross Connection
OH Phone Parameter
OH TP creation
OH TP deleting
MSP overview:
PM overview:
2.2.3
This menu permits to get information about the NE, by means of the following entries:
ED
Alarms: Display the Alarms Surveillance information of the NE. It opens the following menu options:
03
NE alarms
Object alarms
SC.3: NE MANAGEMENT
3AL 98253 ADAA
26/396
Subtree alarms
Equipment alarms
Transmission alarms
Log Browsing: Manage the events stored in the NE. It opens the following menu options:
-
Alarm Log
Event Log
View Remote Inventory: Display the remote inventory data, previously stored in the Craft Terminal by
means the "upload remote inventory" performed in the "Supervisory" menu.
Abnormal Condition list Display the list of the object class (Loopback, ALS Handler, protection board)
and the name of the boards that are in abnormal condition.
Internal Link Monitor: Indicates the preference of failure on Rx or Tx side for the signal
incoming/outgoing from/to the active/standby MATRIX board.
Dataflow Analyzer.
2.2.4
This menu permits to set the supervision states of the NE, by means of the following entries:
Access State: Manage the supervision access to the NE, with CT or OS. It opens the following menu
options:
-
OS
Requested
Alarms: Manage the alarms supervision of the NE. It opens the following menu options:
-
Resynchronize.
Upload Remote Inventory: Store the Remote Inventory data in the Craft Terminal.
2.2.5
This menu permits to age the 2-fiber and 4-fiber MS-SPRing protection (the last is not operative in current
release), setting the relevant configuration, by means of the following entries:
Main dialog for MS-SPRing management: Contains all the command to set and manage the MS-SPRing
2.2.6
This menu permits to manage the NE software, by means of the following entries:
ED
Units info: Show the status of the software package installed in the NE memory banks.
Mib management: Permits backup of NE software configuration and restore of backup file.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
27/396
2.2.7
This menu permits to manage the NE as a whole, setting the boards, which compose it, by means of the
following entries:
Modify: Change the board type without previously remove it. It is only possible between compatible
board or modules (ex. it is possible to change from an Long and Short 1.1 optical module)
Set out of service Delete the lock symbol in the board, enabling changes.
Remote Inventory: Show the Remote Inventory data inserted in the equipment. It opens the following
menu options:
Subrack level
Board level
Connect FAN to CONGI #1: Enable the management of the Fan subrack alarms on CONGI inserted
in slot 1.
N.B. This option is available only after having selected a CONGI board at Subrack level view.
Connect FAN to CONGI # 20: Enable the management of the Fan subrack alarms on CONGI
inserted in slot 20.
N.B. This option is available only after having selected a CONGI board at Subrack level view.
2.2.8
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:
Change Physical Interface: Change the SPI or PPI object into PPI or SPI (and vice versa) on the bimode port (140Mbit/s / STM-1 switch able).
ISA Port Configuration: It allows creating the TPs for the ATM/IP/ETH connections.
This menu permits to set and show the transmission resources (TP) referred to the Port, by means of the
entries indicated in the following list.
The menu differs according the port type (SDH, PDH, HOA, ATM, IP and ETHERNET).
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
28/396
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.
TP configuration: Set parameters for the Overhead (Signal Label and Path Trace) on Synchronous
TP's.
TP Frame Mode Configuration: Set parameters for 2Mbit/s G.703/704 or ISDN-PRA management.
Set Retiming: Set the retiming feature applies to the outgoing 2Mbit/s. It opens the following options:
-
Enable
Disable
Cross Connection: Manage the connection of the paths. It opens the following options:
Monitoring Operation: Set parameters for POM, SUT . Not available for PDH port. It opens the
following menu options:
-
Creation / Deletion
Configuration
Performance: Set and show Performance Monitoring parameters and data. It opens the following
menu options:
-
Configure Monitoring
Loopback: Enter the loopback management. Used to configure the loopback command for
commissioning or maintenance purposes:
-
Loopback management
MSP: Manage the Multiplex Section Protection of the NE. Only for SDH ports view. It opens the
following menu options:
-
MSP Create
MSP Management
MSP Commands
MSP Delete
Physical Media: Manage the physical setting of the TP of the ports. Not applicable to HOA port. It
opens a menu which differs according the port type:
ED
SDH port:
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
29/396
ALS Management
TX Quality Configuration
LAPD Configuration
Ms Configuration
PDH port:
-
HDSL Configuration
NT G703/704 Configuration
NT X21 Configuration
ETHERNET port:
-
ALS Management
Navigate to Transmission view: permit to show a complete overview about the signal flow, opening
all TP's
Navigate to monitoring view: permit to show for a selected TP the related POM/SUT/TCM and TCT
object if present.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
30/396
Add TP: Search and add TP to the transmission view, than presented in the screen.
Expand: Display the TP's related to a selected TP. It opens the following menu options:
All lower TP
All upper TP
Hide: Remove the TP from the screen of the Transmission view. It opens the following menu options:
-
Lower TP
Upper TP
Selected TP
TP configuration: Set parameters for the Signal Label and Path trace.
TP Frame Mode Configuration: Set parameters for 2Mbit/s G.703/704 or ISDN-PRA management.
Only for PDH ports views.
Cross Connection: Manage the connection of the paths. It opens the following menu options:
Monitoring Operation: Set parameters for POM, SUT. It opens the following menu options:
-
Creation / deletion
Configuration
Performance: Set and show Performance Monitoring parameters and data. It opens the following
menu options:
-
Configure Monitoring
Structure TP's: Define the structure of a selected TP (TU2, TU3, TU12, VC3/VC4, VC12)
Loopback : Enter the loopback management. Used to configure the loopback command for
commissioning or maintenance purposes: It opens the following menu options:
ED
Loopback management
Physical Media: Manage the TP physical setting. It opens the following menu options:
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
31/396
ALS Management
TX Quality Configuration
Extra traffic
Set Domain
HDSL Configuration
NT Configuration
X21 Configuration
MSP: Manage the Multiplex Section Protection of the NE. It opens the following menu options:
-
MSP Create
MSP Management
MSP Commands
MSP Delete
NE MSP synthesis
ED
Timing Source Configuration: Set timing source priority and quality for the selected input reference.
Protection Command: Manage commands (force, manual, lockout) for the selected timing reference.
T4 Configuration: Enable/disable SSM, WTR and Squelch Criteria on the T4 synchronization source.
Change T4<->T5: Change the synchronization physical interface from 2MHz (T4) to 2Mbit/s (T5)
without traffic and vice versa.
Change 2MHx->2Mbit: Change the source of a protection unit from 2Mhz to 2Mbit and vice versa.
Set T0 Equal T4
Remove T0 Equal T4
Transmitted SSM Quality Configuration: Set SSM quality transmitted on the selected T1 SDH timing
reference.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
32/396
Frame Mode Configuration: Set parameters for 2Mbit/s G.703/704 or ISDN-PRA management. Only
for PDH ports views.
Show Timing Source: Show the "port view" related to the selected timing reference.
Display: Show the list of the input/output environmental alarm. It opens the following menu options:
ED
03
Show
all
external
Points
SC.3: NE MANAGEMENT
3AL 98253 ADAA
33/396
Figure 2.
ED
03
SC.3: NE MANAGEMENT
34/396
Figure 3.
ED
03
Menu options flow chart 2
SC.3: NE MANAGEMENT
35/396
Figure 4.
ED
03
SC.3: NE MANAGEMENT
36/396
Figure 5.
2.3
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):
ED
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:
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
37/396
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:
The menu structure also permits to pass from a view menu to another (i.e. from "port view" to board view" or
to "transmission view") thus facilitating the operators activity.
Views Navigation
The first level of the "Equipment view" representation will be displayed directly into the current window,
immediately after the NE login.
The Equipment view enables a fast navigation through all levels of the equipment hierarchy.
Navigation is done from higher to lower levels. The NE hierarchy is generally organized in the following way:
Subrack > board > port > TP.
Double clicking on the objects performs the navigation through different levels of the NE hierarchy:
The first level shows the subrack level of the Equipment view
By double clicking on a board body, the board level of the Equipment view can be reached.
Further, by double clicking on a port body contained in the board, the port level of the Equipment
view can be reached. The port view displays the inner TPs.
It is possible to go back to the upper level of representation by pressing the <ESC> key on the
keyboard;
It is also possible to:
ED
Go back to the previous view, by selecting the Backward option from the views menu
Go to the next view, by selecting the Forward option from the view menu.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
38/396
N.B. Selecting in the first level of the Equipment view the Show supporting equipment option from the
Equipment menu, the Rack level view (Example) is presented.
In the Rack Level view two subrack are presented:
-
The Fans Subrack presence is managed with the Set option as for the boards of the 1662SMC
Subrack. (Example)
Further, selecting in the Rack level view the Show supporting equipment option from the Equipment
menu, the Equipment level view is presented.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
39/396
NE MANAGEMENT SUPERVISION
3.1
NE management states
The elementary building blocks of any telecommunication network are the Network Elements (NEs).
Operating with the Craft Terminal the NE can present different management states according to the
condition of the connection (supervision, local access, connection state, etc). Also general Alarm status is
presented.
Management states are present at Network Element Synthesis view level and at USM--EML view level.
All the information referred to the management states are inserted in the Basic Craft Terminal 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.
3.2
The Network Element Synthesis views enable you to get access to the current NE EML-USM view described
in this handbook.
The Network Element Synthesis views enable you to work on local or remote NE, selecting it and activating
"Supervision" and "Login", as described in the Basic Craft Terminal Operator's Handbook.
The EML-USM Main view is presented as for the following figure.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
40/396
Figure 6.
ED
03
NE EML-USM Main view
SC.3: NE MANAGEMENT
41/396
In this chapter general configuration referred to the equipment management are described (Craft Terminal
access, NE Time, Alarms configuration, etc).
4.1
The Craft Terminal can manage by the OS or the NE. To control the competition of the OS and the CT, a
Local Access Control (LAC) is available.
If the LAC is "granted" that means the CT is allowed to manage the NE. In the view the icon with a key
symbol has a rectangular shape.
If the LAC is "access denied" that means the OS manages the NE and the CT is not allowed to modify NE
configuration (it can only "read"). In the view the icon with a key symbol has a circular shape.
If the LAC is "requested" that means the CT has requested permission from the OS and is waiting for a
replay.
However the OS does continue to provide a certain number of services. These services includes:
Select the Supervision pull down menu. Then select the Requested option from the Access State
cascading menu as shown in the following figure.
Figure 7.
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
42/396
If the OS doesn't answer in a predefined time it is assumed that the NE is in the Craft access state and can
be managed from a Craft Terminal.
4.1.2
Switching from the Craft Terminal access state back to the OS access state
Select the Supervision pull down menu. Then select the OS... option from the Access State.
From the confirmation dialogue box that opens you can confirm or cancel the "OS access" operation.
The OS now manages the NE.
N.B. The key symbol icon on the management states of the NE view indicates whether the OS manages by
a craft terminal or the NE.
N.B. Local Craft Terminal access is denied on recovery phase after a loss of communication of the NE.
When communication is lost with the NE, the OS automatically recovers the communication and put the state
that was set before the loss of communication (therefore the Craft Terminal access can be denied or
granted).
4.2
NE Time management
The NE local time of a selected NE can be visualized and/or re-aligned on the OS time basis.
In this view the OS indication identifies the Craft Terminal.
The status of the Network Time Protocol can be checked
Select the NE Time... option from the Configuration pull down menu.
Figure 8.
The following dialogue box is opened from which you can get and/or set the local NE time and check the
NTP Status.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
43/396
Figure 9.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
44/396
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.
If you do not want to set the NE local time, click on the Close push button to close the dialogue box.
To re-align the NE time on the OS time basis click in the Set NE Time With OS Time radio button and either
click on the Apply push button to validate or on the Close push button to cancel and close the dialogue box.
The OS time comes from the PC date configuration that corresponds to the legal GMT time.
N.B. When the NTP is not present, the OS system re-aligns the time of all supervised NEs periodically and
automatically with a configured periodicity. This periodicity is common for all the NEs.
If you set the NE time, you will force the change, with an immediate effect on the NE. However it will not
have any effect on the periodic and automatic mechanism.
4.3
Alarm Configuration
The operations described in this chapter, mainly related to alarm setting, are:
Alarm re-synchronization
4.3.1
a)
b)
c)
Select one of the user profile (#10001 or #10002) and click on Modify
d)
e)
f)
g)
Click on OK
h)
Click on Close
i)
Select the relevant TP and then Configuration -> Set Alarms Severities
j)
In the box that appears select the just modified ASAP (eventually check it by means of Detail)
k)
Click on OK
4.3.2
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:
ED
SC.3: NE MANAGEMENT
3AL 98253 ADAA
45/396
Select the Alarm Severities... option from the Configuration pull down menu.
Figure 10.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
46/396
Figure 11.
Profile No alarms. Whit this profiles all the alarms are enabled (only Software Download Failure
is not alarmed). This ASAP enables the emission of all alarms.
Profile No Remote Alarms shows the alarm criterion configuration defined for "path alarms" (only
AIS and RDI and Software Download Failure are not alarmed). This ASAP enables the emission of
all:
ED
Communication Alarms (i.e. the AIS & RDI alarms are not alarmed)
Equipment alarms
Environmental
Profile Primary alarms with this profile the AIS, Battery Degraded, Software Download Failure,
SSF and RDI alarms are not alarmed. This ASAP enables the emission of all:
-
Communication Alarms (i.e. the AIS, SSF & RDI alarms are not alarmed)
Equipment alarms
Environmental
Profile All Alarms (i.e. all alarms disabled). This ASAP inhibits the emission of any potential
alarm.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
47/396
The user can set profile 10001. Each single alarm can be classified with a criterion selected by the
operator. A default standard configuration is set. (Battery Degraded, Battery Failure, Communication
Subsystem Failure, Path Trace Mismatch are not alarmed).
NOTE: if this profile is not already present in the list, it is necessary to create it, selecting
one existing profile and then clicking on the Clone button.
For ASAP No Alarms, Primary alarms. No Remote Alarms and All Alarms it is only possible to choose
Detail, or Clone buttons.
Clone selection can be used to create new ASAP.
Click on Detail, Modify, or Clone button, the ASAP edition dialogue box is displayed.
Figure 12.
The alarm severity assignment profile dialogue box displays a list of probable causes and a list of alarm
severity.
The Probable cause family checks buttons allows filtering the probable causes that will appear in the
Probable cause name list. NOTE: it is necessary to choose one or more of these filters to have the list.
To find a particular probable cause, enter its name in the Search entry box at the bottom.
ASAPs are already defined in the system with default values for the assigned severities.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
48/396
You can modify the severity associated with each probable cause. To do this, select the probable cause
whose severity level you wish to modify.
Then click on the option button: Service Affecting (not protected probable cause), and then Non Service
Affecting (protected probable cause) and then Service Independent (don't used, it is not operative). For each
the severity can be chosen from "Critical", "Major", "Minor", "Warning", "Non-alarmed" or "Not used". A "Nonalarm" probable cause corresponds to no alarm emitted for this probable cause.
When selecting Details the assigned severity are only shown and it isn't possible to modify.
When you have finished configuring ASAP, press the OK button to confirm the settings and close the
dialogue box or the Cancel push button to cancel the new settings and close the dialogue box.
When Clone an ASAP the created one is identified with next number (10002,).
The max number of ASAP is six.
N.B. The number of severities and the number of probable causes is fixed. The ASAP function only enables
the modification of the severities assigned to the probable causes, it does not allow the addition, removal or
modification of these severities and causes.
N.B. To take into account a profile modification, it is mandatory to perform a re-synchronization of the alarms.
During this re-synchronization, the severity of each alarm is updated. Otherwise, the severities are updated
only when the NE emits the modified or new alarms.
4.3.2.2 Set Alarm Severities
To assign an alarm severity to a TP or equipment, select the TP or equipment in the related view and then
select the Set Alarm Severities... option from the Configuration pull down menu.
The Set ASAP dialog opens.
Figure 13.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
49/396
Within the "Apply to" section on the right side, the user specifies the objects (TP or equipment) the ASAP
selected in the List of ASAPs (new ASAP) should be applied to:
Choose Scope
Network element
The new ASAP is applied to all objects of the NE matching criteria specified in "Choose
Classes" and "Choose current ASAP".
Since this application process takes some time, its progress is shown in the section "Execution
Monitoring".
This is the default if no object is selected in the view.
Selecting the Set SdhNE Alarms Severities option from the Configuration pull down menu only the alarms
at Equipment level (FF, BKF, SHD and ABF) are managed.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
50/396
Figure 14.
If an object was selected in a view before opening this dialog, its ASAP is highlighted in the list. Using the
Detail button or double-clicking on a list item opens the ASAP Edition dialog which displays detailed
information on this ASAP.
Press Ok to confirm the ASAP assignment and close the dialog. Press Close the dialog and discard any
changes.
4.3.4
The system provides the possibility to allow/inhibit the spontaneous incoming alarm notifications.
a) To inhibit alarm notification, select the Supervision pull down menu. You can then select the Inhibit
Notifs option from the Alarms pull down menu as shown in the following figure.
Figure 15.
From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok or
Cancel push buttons respectively.
To inform the operator that alarms have been inhibited, the labels of the alarm panel are grey out.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
51/396
N.B. Inhibiting the alarms notification means that they are not forwarded to the CT but alarms are still
generated by the NE.
Figure 16.
From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok or
Cancel push buttons respectively.
4.3.5
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 re--synchronize the alarms, select the Supervision pull down menu. You can then select the
Resynchronize option from the Alarms pull down menu as shown in the following figure.
Figure 17.
Alarm re--synchronization
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
52/396
4.3.6
Figure 18.
Figure 19.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
53/396
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.
Figure 20.
Restart NE confirmation
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
54/396
SECURITY MANAGEMENT
In this chapter are inserted setting options referred to the Security management:
5.1
This option is referred to the Security management and allows the user to set the Manager list and the
Access Control Domain of the NE.
Select the Set Manager list option from the Supervision pull down menu.
The dialog-box contains the following fields:
Manager list: each connected manager to the NE is highlighted in the list. The user can set a
manager clicking on the denomination.
Several managers can be enabled contemporaneously, having in charge the NE.
The Manager List contains the list of managers (i.e. RM, SY, NPOS, EML) that work on the NE. The
EML-USM administrator (SH or Craft Terminal) should set the Manager List only to remove a
manager in case of emergency (i.e. the Manager misses the NE connection).
NE Domain field allow selecting the domain among that displayed in the list, assigning it to the NE.
The different domains could be assigned to different operators.
Figure 21.
5.2
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
55/396
Select the Set ACD level option from the Configuration pull down menu.
The dialog-box contains the following fields:
Permit to set one of two level checks. By the way, this is an operation that should be performed only
during the EML-USM installation phase:
Figure 22.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
56/396
This chapter describes how to display and set the input/output environmental alarm (housekeeping alarm),
An external input point is an environmental alarm (also called housekeeping alarm). It corresponds to an
external event, which is monitored by the NE. Number of relays on the NE is dedicated to check modification
of the environment as for example a fire, a flood...
An external output point is used to manage a NE contact (i.e. relay) connected to detector. An external
output point is independent from external input point.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization.
6.1
Select the External Points option from the Views pull down menu.
Figure 23.
After selecting this menu option the external points view is displayed into the current window instead of the
current view.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
57/396
Figure 24.
The external points view displays a list of all input and output points.
The following information is given for each external point:
The user label: a user-friendly label associated to the configurable external point (see further the
paragraph External points configuration).
The external state: represents the alarm state. "On" when the alarm is raised, else "Off". If the
external point is active (On), a little flag is represented near the status of the concerned point.
Only for the Output external point there is the following information:
ED
The Output criteria: if configured, display the alarm event and the board effected associated to the
Output point (see further the paragraph External points configuration)
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
58/396
6.1.1
The external points view displays a complete list of the external points but it can also be restricted to the
input or to the output points.
To see either the input points, the output points or all the external points, select the appropriate option from
the External Points pull down menu as shown in the following figure.
Figure 25.
6.2
To configure an external point, click on the concerned row. And then select the Configuration option from the
External Points pull down menu as shown in the following figure.
Figure 26.
The following dialogue box is then opened, displaying information about the selected external point (Input or
Output).
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
59/396
Figure 27.
Figure 28.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
60/396
Figure 29.
Opening the dialog the current state of the selected External Point is shown.
1) External Input Point Configuration
User Label: this field can be filled by the user with a Label that indicate the associated event that
must be taken under check (for example presences of water of fire in the room where the Equipment
is placed)
External State: this field is set to off and can't be changed by the operator
Probable Cause: the field is set to housekeeping and can't be changed by the operator
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.
Manual (forced). The output contact is set in a fixed way, not depending on a particular event.
For example the output contact could be used to "Manually" activate a pump drain water from the
room where the equipment is placed; in this case is also necessary to set the option "On" in the field
"External State".
Flexible. It is possible to define from CT the couple event/CPO#, where the event is chosen between
a set of Output Criteria (LOS, RDI and LOF) and specifies the STM-N interface which the Output
Criteria refers to by clicking on Choose button; subsequently the TP search dialog box will be
opened.
When the configuration of the external point is completed, click on the OK push button to validate the choice
and close the dialogue box. The Cancel push button cancels the configuration and closes the dialogue box.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
61/396
DIAGNOSIS MANAGEMENT
Alarms are always present on the operator's workspace. The different types of alarms, their number and their
severity level, are represented in all Equipment views (NE views, Board views and Port views). An icon
representation is used, which change color when the relevant alarm is active. Thus, at all times, you know
the number of alarms and their severity relating to the equipment.
Access to the Alarm Surveillance to show the alarm condition is detailed in the following paragraph.
Than is presented the abnormal condition list (as result of operator's command such us loop, laser forced on
etc.).
At the end the Event log access is introduced.
Information about the significance of equipment alarms and status is given in the Maintenance
section.
7.1
Alarms surveillance
In this chapter is described the access to the Alarm Surveillance information of the NE.
It is possible to show all the Alarms or filter the alarms report.
Select the Diagnosis pull down menu. You can then select the following option from the Alarms pull down
menu:
NE Alarms: all the NE alarms are listed in the Alarm Surveillance report which is activated
Object Alarms: only the alarms of the selected object are listed in the Alarm Surveillance Report
Subtrees Alarm: only the alarms of the selected object and of the relevant subtrees are listed in the
Alarm Surveillance report
Equipment Alarms: only the alarms of the equipment management are listed in the Alarm
Surveillance report
Transmission Alarms: only the alarms of the transmission management are listed in the Alarm
Surveillance report
External Points Alarms: only the alarms of the input external point management are listed in the
Alarm Surveillance report
Figure 30.
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).
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
62/396
Figure 31.
Alarm Surveillance
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
63/396
7.2
The abnormal condition provides the synthesis of NE "not normal conditions" listing the events that
contribute to abnormal condition. Select Diagnosis->Abnormal Condition List.
Figure 32.
Figure 33.
Loopback
Protection units (in case of EPS, SNCP and MSP if supported) are in lockout or in forced status
Select an abnormal condition and click on OK to open the relative dialog window. Figure below is opened.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
64/396
Figure 34.
The other abnormal condition types will open the corresponding management window or will open the
window to navigate towards the management window.
7.3
This function improves, at the user interface level, the diagnostic associated to the hardware failure.
The presence of a failure on RX or TX side for the signal incoming/outgoing from/to the active MATRIX is
detected; Internal Link Monitor displays a detailed localization of the link failure: a graphical representation of
all NGI link status, for the active and stand-by MATRIX is shown.
Select the Internal Link Monitor option of the Diagnosis menu.
As shown in Figure below. The first page displays the link status for the main MATRIX, the second one
concern the spare MATRIX.
In detail, each page contains the following functional blocks and graphical objects:
ED
The tab of the page displays the user label of the MATRIX board;
The left side of the page displays the block representing the MATRIX board;
The right side of the page displays the list of blocks representing the equipped boards; each block
displays a string contained the user label of the associated board;
Two arrows are displayed between the MATRIX block and each board block; the two arrows
represent the link status in RX and TX side:
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
65/396
The Refresh button allows performing an explicit refresh of all the displayed information.
In order to indicate all the possible roots of the "link failure", all boards that detect the link failure are
represented by a red block in the page of the MATRIX main:
a port" board in represented by a red block if a link problem is detected in the NGI Rx from the
active MATRIX.
A red block represents the MATRIX if a link problem is detected in one of the NGI Tx from one of the
possible "port" board.
Figure 35.
7.4
Log Browsing
From the Network Element context views, perform the following operations to have access to the Event Log
file:
-
Figure 36.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
66/396
Select the Alarm Log option (Log Id # 1) to access the Event Log file.
The Configuration and Log Browsing ELM Windows open, permitting to analyze all alarms stored in
the NE.
Select the Event Log option (Log Id # 2) to access the Event Log file.
The Configuration and Log Browsing ELM Windows open, permitting to analyze all events stored in
the NE.
7.5
Remote Inventory
This paragraph describes the access to the remote inventory of this NE.
In the Remote Inventory are stored information of identification, construction data etc.
The options used are:
Upload Remote Inventory: store the Remote Inventory data in the Craft Terminal.
View Remote Inventory: display the remote inventory data, previously stored in the Craft Terminal
by means the "upload remote inventory" performed in the "Supervision" menu.
This command stores the Remote Inventory data in the Craft Terminal.
Select the Upload Remote Inventory option of the Supervision pull down menu.
A confirmation dialog box is opened.
Figure 37.
Figure 38.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
67/396
7.5.2
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.
Figure 39.
Company
Unit Type
It indicates Alcatel or Factory product's Part No. The number indicated is that printed on the labels or on the
units' front cover plate.
CLEI Code
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
68/396
Manufacturing plant
It indicates the Company's manufacturing plant id. Within the company, producing the unit.
Refer to Alcatel for the abbreviation's meaning (four characters).
Serial Number
Date identifier
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- - - - "
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
69/396
8.1
The purpose of the communication and routing domain is to define configuration parameters concerning the
communication protocols for the local NE, the OS and each other related NE in order to provide a global
communication capabilities inside the network.
8.1.1
A brief description of basic concepts and terms involved in the communication and routing domain follows.
During the TMN design process, a network is partitioned into domains; each domain can consist of a
collection of two types of nodes:
Nodes supporting a link state routing protocol IS-IS; these nodes will be called adaptive routers;
IS-IS protocol floods the network with link state information in order to build a complete consistent
picture of the network topology. Use of IS-IS routing protocol in a TMN facilitates installation and
operation due to the "self learning" capabilities of these protocols and automatic network
reconfiguration in case of failure; moreover the use of these standardized routing protocols
guarantees interoperability in a MultiFinder environment.
Nodes not supporting these protocols; these nodes will be called static routers;
Networks partitions consisting of the former type of node will be called adaptive routing domains; networks
partitions consisting of the later type of node will be called static routing domains.
Moreover, a node which have to take routing decisions must became Intermediate Systems, all others can
be made End Systems
For the description of the following paragraphs use is made of Figure below. It is not a network-planning
example; it is only used to describe L1, L2, RAP and MESA.
8.1.1.1
In order to reduce the overhead associated with distributed adaptive routing, it may be useful to divide a
adaptive routing domain into smaller routing sub domains, called areas or level 1 sub domain. A level 1 sub
domain should fulfill the following requirements:
A level 1 sub domain should form a connected sub network; this sub network should have only a few
links to the outside world, compared with the number of internal links;
Each node which is connected to a foreign level 1 sub domain must become a level 2 intermediate
system; level 1 intermediate systems know how to communicate only with IS in the same area;
obviously, there must be at least one level 2 intermediate system per level 1 sub domain;
Level 2 intermediate systems must form a connected network, because level 1 path cannot be
utilized for level 2 communications. This network will be called level 2 backbones.
In the simplest case, all nodes within a level 1 sub domain share the same area address.
In general it is allowed to have multiple synonymous area addresses within a level 1 sub domain even if the
usage of this features should be checked with Alcatel engineers.
The synonymous list is used to ease partitioning in the future. There is a basic rule, which must be followed
by two neighboring level 1 intermediate systems within a sub domain: there must be at least one area
address in common between their two synonymous list, otherwise they are not able to communicate with
each other.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
70/396
8.1.2
In certain situations it may be necessary to partition a given network into separate routing domains, where no
routing information is exchanged between these domains. The major benefits of this partitioning are
reduction of memory, processing and traffic overhead, because there is no exchange of routing information
between the domains. Communication between separate routing domains must be achieved through the use
of Reachable Address Prefixes (RAP).
A Reachable Address Prefixes represents static routing information. It can only be associated with a link of
a level 2 intermediate systems, whereby this link crosses routing domain boundaries. A Reachable Address
Prefixes is handled in the same way as information about a foreign level 1 sub domain within the own
domain. The Reachable Address Prefixes indicates that any packet whose destination network address
NSAP matches the prefix may be forwarded via the link with witch the prefix is associated.
For example, consider network, which is split into two separate routing domains:
Routing domain A resides in a level 1 sub domain with area address "a"
Routing domain B resides in a level 1 sub domain with area address "b"
In order to enable the communication, the Reachable Address Prefixes in routing domain A must contain the
area address "b" and the Reachable Address Prefixes in routing domain B must contain the area address "a".
On the other hand, within a given level 1 sub domain, there can be some NEs not supporting IS-IS nor ES-IS
protocol (static routing). In such condition, the communication can be achieved through the use of Manual
End System Adjacencies (MESA).
A prerequisite for the use of manual end system adjacencies is that the area addresses of the connected
nodes must be the same; as a consequence the nodes must belong to the same level 1 sub domain. Within
a pure Alcatel network there is no need to use any kind of static routing. Therefore normally RAP and MESA
shall never be used.
Figure 40.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
71/396
8.1.3
This feature allows the Element Manager to reach the GNEs (and all the relevant NEs behind them) by using
IP networking.
This would permit to use an external DCN based on IP only. Hence, no OSI networking would be required on
the external DCN.
OSI over IP technique is used to meet the target. OSI packets leaving the SH are encapsulated into IP
packets within the SH system itself. Hence, packets leaving the SH are IP packets, containing the original
OSI packet.
Once the packet gets the NE through a pure IP network, the GNE has to strip off the IP encapsulation,
extracting the OSI packet, and to route the OSI packet as it does today using a pure OSI networking.
Hence, the internal networking of the SDH network (DCCs) is still based on OSI. No IP packets shall flow
inside DCCs, because the GNE receives the IP packet containing the OSI packet, deletes the IP header, and
forwards only the OSI packet on DCCs.
The default OSI lower layers networking can be replaced by IP routing capability at the bottom of the
QB3/QECC communication protocol suite; the choice is software switchable at NE level. The implementation
adopts the RFC1006 standard to put the OSI upper layers on top of IP networking.
The application goal is to offer the TCP/IP transport (i.e. Internet compatibility) in alternative to the full
ISO/OSI communication protocols, in the complete DCN network or at least in a consistent portion of it.
Figure below depicts the protocol architecture.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
72/396
Figure 41.
8.2
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:
ED
OS Configuration: addressing of the main and spare OSs connected to the local NE
NTP Server Configuration: addressing of the main and spare NTP servers connected to the local NE
LAPD Configuration: definition of the LAPD port parameters for each LAPD channel on the local NE
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
73/396
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 42.
ED
03
Comm/Routing options
SC.3: NE MANAGEMENT
3AL 98253 ADAA
74/396
8.3
Local Configuration
Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading
menu the Local Configuration option.
The dialog-box opens and allows configuring the local address of the NE.
The following fields are present:
a Presentation Selector (P.Sel) identifies a presentation entity at the location identified by the
NSAP Address. The presented value must not be modified.
a Section Selector (S. Selector) identifies a section entity at the location identified by the NSAP
Address. The presented value must not be modified.
a Transport Selector (T. Sel) identifies a transport entity at the location identified by the NSAP
Address. The presented value must not be modified.
a Network Service Access Point (NSAP) Address identifies a location in the network. The first
field of the NSAP address, AFI, determines the NSAP format. The AFI filed is 2 characters long
(2 hexadecimal digits) and, depending on the its value, the length of NSAP address is variable
from 16 characters to 40 characters:
o
The value of AFI 49 identifies the local format of variable length (from 16 characters
to 40 characters).
In all cases the last two fields of the NSAP address are:
o
Network Selector: provides the distinction among users of the network service and is
2 characters long (value is "1d").
In the view, the NSAP is managed as simple strings of characters without any pre-formatting
because of the variable format:
o
a second string of variable length that identifies the remaining NSAP address
Synonymous Area Addresses section allows having multiple synonymous area addresses within a
level 1 sub domain. The compilation of the two network addresses is optional and if they are inserted,
the last two fields, System Id and Network Selector, of the mandatory address and of the
synonymous addresses must be the same.
System Type section determines whether the local NE acts as a "intermediate system level 1" or as
a "intermediate system level 2" or as a "End System". Note that a level 2 intermediate systems
performs functions of a level 1 too. End System is not operative.
Ok button is used to perform a configuration change of the data contained in the dialog-box and closes it; the
dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
75/396
Figure 43.
8.4
Local Configuration
OS Configuration
Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading
menu the OS Configuration option.
The dialog-box opens and allows configuring the addresses of the Main and Spare OSs connected to the
local NE.
The following fields are present:
Main OS Address section contains the same graphical object of the Local Address Section in the
Local Configuration dialog-box.
Spare OS Address section contains the same graphical object of the Local Address Section in the
Local Configuration dialog-box.
Ok button is used to perform a configuration change of the data contained in the dialog-box and closes it; the
dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
76/396
Figure 44.
8.5
OS Configuration
Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading
menu the NTP Server Configuration option.
The dialog-box opens and allows configuring the addresses of the Main and Spare NTP (Network Protocol
synchronization Time) Servers connected to the local NE, used for time distribution in the network.
The following fields are present:
Enabling NTP Protocol section allows enabling or disabling the NTP Protocol.
Main NTP Server Address section contains the same graphical object of the Local Address Section
in the Local Configuration dialog-box.
Spare NTP Server Address section contains the same graphical object of the Local Address Section
in the Local Configuration dialog-box.
If the NTP server is coincident with the OS (same hardware), the same NSAP address of the OS must be
assigned.
Ok button is used to perform a configuration change of the data contained in the dialog-box and closes it; the
dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
77/396
Figure 45.
ED
03
NTP Server Configuration
SC.3: NE MANAGEMENT
78/396
8.6
LAPD Configuration
Select the Configuration pull down menu. Select the Comm/Routing-> Interface Configuration option
and then from the cascading menu the LAPD Configuration option.
The "LAPD Configuration" dialog opens.
It contains the following functional block and graphical objects:
To change the role of the LAPD Interface selected in the LAPD Interface List;
The LAPD Interface List that lists all the configured LAPD Interfaces; for each LAPD Interfaces, the
table displays:
The user label of the TTP containing the configured LAPD Interface (MS/RS/E1A TTP);
User
Network
Delete button that allows to delete the LAPD Interface selected in the LAPD table;
Change Role button that allows too change the role (User or Network) of the LAPD Interface
selected in the table;
Create button that allows to create a new LAPD Interface; this button starts a new dialog. Named
Create LAPD Interface; it is disabled when the maximum number of LAPD Interface has been
configured.
This Create LAPD Interface dialog contains the following functional blocks and graphical objects:
A Choose button that allows the operator to select the superior TTP of the LAPD Interface to
be created; this button starts the TP Search dialog; the TP Search dialog will be configured in order
to display in the right tree only the allowed TTP of the LAPD Interface;
A section LAPD Role that allows configuring the role (User or Network) of the LAPD Interface to be
created.
This connection is a must to establish connection between two NE's: if one is configured with User
role, the other one connected must be configured with Network role.
- a section named Search Criteria that allows the user to display only the LAPD's of the selected type in
the LAPD Table; the section contains the following graphical objects:
ED
The field Interface Type that allows to select the type of the LAPD's to be displayed in the LAPD
Table; the field will manage both ADM and WDM DCC type; the value "Ignore" will allow to display
all the LAPD types;
The Search button starts the search of the selected LAPD type; this buttons can be used to refresh
the LAPD table too.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
79/396
The LAPD Interface List will be updated on reception of the Delete/Create/Change DCC CTP notification. If
no LAPD Interface is configured in the equipment, the message "No LAPD Interface" will be displayed near
LAPD Interface counter (that it is at zero)
Figure 46.
\
Figure 47.
ED
03
TP search dialog
SC.3: NE MANAGEMENT
3AL 98253 ADAA
80/396
Figure 48.
Figure 49.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
81/396
8.7
Ethernet Configuration
Select the Configuration pull down menu. Select the Comm/Routing-> Interfaces Configuration option
and then from the cascading menu the Ethernet Configuration option.
The dialog-box opens (figure below) and allows defining the parameters needed to manage a NE, which
provide a LAN Ethernet interface.
Ethernet Interface field allows defining or removing a Local Area Network Port for the access to the
Data Communication Network.
MAC Address section allows displaying the address of the Network Element in the Ethernet LAN; it
is a read-only field.
OSI Section:
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.
L1 Default Metric is a not modifiable field, Priority field can be set (default value for
Ethernet is 64)
L2 Default Metric is a not modifiable field, Priority field can be set (default value for
Ethernet is 64)
IP Section allows to define the node IP Address, IP Mask and the Routing IP Protocol used; If
OSPF or Both options of Routing IP Protocol field are selected, also the Associated OSPF Area
must be set.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
82/396
Figure 50.
ED
03
Ethernet Configuration
SC.3: NE MANAGEMENT
83/396
Figure 51.
8.8
Select the Configuration pull down menu. Select the Comm/Routing -> OSI Routing Configuration option
and then from the cascading menu the RAP Configuration option.
The dialog-box opens and allows configuring the Reachable Address Prefix table.
Each element of the RAP table allows to link a LAPD port or a LAN port of the local NE to a separate domain;
the separate domain is selected by the address Prefixes. If the addressed element is the OS, the LAN port
will be used.
The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing
device; each page represents a particular element of the RAP table and the respective pointing device
displays the element counter.
In detail, each page contains the following data:
If the element is empty, displays the "none" value and allows to select a LAPD ports
or a LAN port which will be used to reach the addressed area.
If the element isn't empty, displays the selected port and allows to change it.
Area Address Prefix section allows the user to address the separate domain. The Area Address
Prefix represents a NSAP address without the fields System Id and Network Selector.
MAC Address section allows addressing the element of a domain to be reached the Ethernet LAN;
the field is managed as a simple string of 12 digits.
Apply button is used to perform a configuration change of the data contained in the complete RAP table and
close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
84/396
Figure 52.
8.9
RAP Configuration
Select the Configuration pull down menu. Select the Comm/Routing -> OSI Routing Configuration option
and then from the cascading menu the MESA Configuration option.
The dialog-box opens and allows configuring the Manual ES Adjacencies table.
Each element of the MESA table allows linking a LAPD port or a LAN port of the local NE to a End System
element; the ES element must be in the same area as the one of the local NE. If the addressed element is
the OS, the LAN port will be used.
The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing
device; each page represents a particular element of the MESA table and the respective pointing device
displays the element counter.
In detail, each page contains the following data:
If the element is empty, displays the "none" value and allows selecting a LAPD ports
or a LAN port, which will be used to reach the End System element.
If the element isn't empty, displays the selected port and allows changing it.
MAC Address section allows addressing the element in the Ethernet LAN; the field is managed as a
simple string of 12 digits.
Apply button is used to perform a configuration change of the data contained in the complete MESA table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
85/396
Figure 53.
MESA Configuration
8.10 IP Configuration
The options listed in the menu Configuration > Comm/Routing > IP Configuration and also in
Configuration > Comm/Routing > Tunneling Configuration is relevant to the configuration of
messages communications for the management of ATM or IP boards (ISA) inside the equipment and in the
network.
8.10.1 IP routing configuration for ATM/IP boards management
In order to manage the ATM/IP boards inserted into the equipment, the following operations are to be done:
ISA Board IP Address it defines the IP address for the ATM or IP boards (ISA); it is to be defined
for every ISA board hosted by the equipment.
NOTE: if the ISA boards are in EPS 1+1 configuration, they must have the same address)
ED
IP over OSI Tunneling it defines the OSI address (NSAP) of the destination node to be reached
(for instance the GNE connected to the TMN), when the ATM/IP management message passes
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
86/396
through an SDH/OSI network; i.e. it is to be done for every SDHNE of the network, if equipped with
ATM/IP boards.
NOTE: this addressing must be carried out at both end nodes of the tunnel, so that they can see each
other.
OSI over IP Tunneling it defines the IP address of the destination node to be reached (for
instance the IP router where the TMN is connected), when an OSI management message passes
through an IP network. It is to be defined on a a Gateway Network Element (GNE) equipped with the
QB3 interface, where the QB3 is connected to a LAN/IP network.
NOTE: this addressing must be carried out at both end nodes of the tunnel, so that they can see each
other.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
87/396
Figure 54.
Both fields gives a synthetically information that includes all the addresses (specific a NE and to a Network)
in an Area.
Apply button is used to perform a configuration change of the data contained in the complete RAP table and
close the view is visible until the end of the operations and a wait cursor is displayed.
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
88/396
Figure 55.
Figure 56.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
89/396
Figure 57.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
90/396
The dialog-box opens (Figure below) and allows configuring the Remote Destination IP Address of the
Equipment Controller.
Figure 58.
Apply button is used to perform a configuration change of the data contained in the complete table and
close the view; the view is visible until the end of the operations and a wait cursor is displayed.
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
91/396
System Id: uniquely identifies a NE in an area and is 12 characters long. It might be the equipment
MAC Ethernet address; level 2, inserted in the NE or the operator might select it.
Network Selector: provides the distinction among users of the network service and is 2 characters
long (value is "1d")
In the view, the NSAP is managed as simple strings of characters without any pre-formatting
because of the variable format:
A second string of variable length that identifies the remaining NSAP address
Both
None
If "OSPF" or "Both" options are selected, also the "Associated OSPF Area" must be set.
Apply button is used to perform a configuration change of the data contained in the complete table
and close the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page
Delete button is used to delete the selected page
Close button close the dialog without changes of the data.
Figure 59.
ED
03
IP over OS
SC.3: NE MANAGEMENT
3AL 98253 ADAA
92/396
Equipment Management
9.1
This section deals mainly with the setting and changing of the boards present on the Equipment and
undertaking board protection operations.
Using the menu options, select the Equipment option from the View pull down menu.
The first level of the "Equipment Overview" representation will be displayed directly into the current window
The Equipment Overview enables a fast navigation through all levels of the equipment hierarchy. Navigation
is done from higher to lower levels.
The NE hierarchy is organized in the following way: subrack > board > port > TP.
Double clicking on the objects performs the navigation through different levels of the NE hierarchy:
The first level shows the subrack level of the Equipment view;
Further, by double clicking on a board body, the board level of the Equipment view can be reached.
Further, by double clicking on a port body contained in the board, the port level of the Equipment
view can be reached. The port view displays the inner TPs.
It is possible to go back to the upper level of representation by pressing the <ESC> key on the
keyboard;
It is also possible to:
Go back to the previous view, by selecting the Backward option from the views menu
Go to the next view, by selecting the Forward option from the view menu
N.B. Selecting in the first level of the Equipment view (subrack level)
The Show supporting equipment option from the Equipment menu, the Rack level view is presented;
further, selecting in the Rack level view the Show supporting equipment option from the Equipment menu,
the Equipment level view is presented.
In the Rack level view, two subrack are presented:
The Fans Subrack presence is managed with the Set option as for the boards of the 1662SMC Subrack
Further, selecting in the Rack level view the Show supporting equipment option from the Equipment
menu, the Equipment level view is presented.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
93/396
Figure 60.
ED
03
Equipment Overview -- Subracks level
SC.3: NE MANAGEMENT
94/396
Figure 61.
ED
03
Equipment Overview -- Rack level (without Fans subrack)
SC.3: NE MANAGEMENT
95/396
Figure 62.
ED
03
Equipment Overview- Rack level (with Fans subrack)
SC.3: NE MANAGEMENT
96/396
Figure 63.
In the Subrack view it is possible use the options offered by the Equipment menu clicking on it in the menu
bar.
Alarms indications are present at every NE level.
Details about these alarms indication are given in the Maintenance section.
All the options offered by equipment menu are described in the next paragraphs.
Set and change the boards present on the Equipment is the main function.
Board administrative state that decides on the "in/out of service" of the board is also described.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
97/396
Figure 64.
Equipment menu
Remove a board
9.2
The boards can be set, changed or removed using the menu options of the Equipment view.
a ) Setting or changing a board/subrack
A new board/subrack may be created in either an empty slot or it may replace an existing Out of Service
board/subrack (without the lock symbol). In fact, the Set option is available only after selecting an empty slot
or an Out-of-service board.
ED
Click on the empty slot in which a board/subrack has to be added, or on an existing Out of Service
board in order to change it. The contour becomes highlighted to show that operations can be done
on it.
The following example of dialogue box containing a list of the different types of boards/subrack is
displayed.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
98/396
Figure 65.
N.B. The list of boards/subrack displayed during a "Set Board" operation is restricted to those, which the
equipment may accept in the selected slot. Therefore the list will vary depending on which slot has been
selected.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
99/396
For details on the board/subrack identified by acronyms and NE physical composition please refers to the
Technical Handbook.
Choose the board/subrack/access card type required, by clicking on the corresponding item in the
list. The name of the board is highlighted. Click on the OK push button to validate the choice.
Note: In case of 4xANY Modules it is also necessary to choose the type of user supported as shown
in Figure 64.
The board/subrack representation appears on the NE view in the slot when the board change is
effective.
A lock representation appears over the boards ("in-service")
In the Create/Modify dialogue box, the Cancel push button cancels the operation and closes the
dialogue box. The Help push button opens a Help view giving information about the context.
b) Removing a board/subrack
If the slot you are working on is already empty no name appears under the slot.
From the confirmation dialogue box that opens you can confirm or cancel the "Remove" operation.
N.B. It is possible remove a board only if it is not involved in any type of cross connection (OH bytes
included) or Performance monitoring.
c) Modify a board
N.B. This procedure can be done to replace an existing optical module with another of different type
without previously remove it.
ED
Click on the optical module to replace. The outline of the slot becomes highlighted to show that
operation can be done on it.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
100/396
Figure 66.
Figure 67.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
101/396
9.3
Chose the optical module type required by clicking on the corresponding item in the list; the name of
the module is highlighted.
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.
This command enable the Fan Subrack alarms management from CONGI in slot 10 or slot 12 according to
the option selected in the Equipment menu.
Figure below. Shows an example
Select the CONGI board
To enable this function select the Connect Fan to CONGI#1 option (or as alternative Connect Fan to
CONGI#20) of the Equipment menu if the supervision Fan Subrack cable is connected to CONGI unit
inserted in slot 1.
Figure 68.
It is possible to disable this function by selecting the relevant CONGI board and then choosing the Remove
Fan connection from CONGI#1 option of the Equipment menu.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
102/396
Figure 69.
9.4
The operator decides to set a board in service or out of service, if the NE allows it.
N.B. In the equipment view, a lock representation appears over the boards which are in "in service" state.
9.4.1
Select the Set in service option of the Equipment pull down menu.
A lock representation appears over the boards.
9.4.2
Select the Set out of service option of the Equipment pull down menu. Select the Ok push button
in the confirmation window that appears.
A lock representation disappears, substituted by the symbol
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
103/396
9.4.3
The board's administrative ("in service" or "out of service") state is indicated on the board view as shown in
the following figure.
Figure 70.
9.5
Software description
This function allows the operator to visualize information about the software(s) which is (are) present in the
selected board.
Click on a board in which the software is wanted to know (COMPACT ADM unit). The outline of the
slot becomes highlighted. This indicates that the board is selected and that operations can be done
on the slot.
Select the Software description option of the Equipment pull down menu.
Opened dialogue box contains as many folder sheets as there is software in the selected board.
Click on the Close push button to close the dialogue box.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
104/396
Figure 71.
9.6
Remote Inventory
This command displays the remote inventory data present in the Subrack and Boards.
Select the Remote Inventory option of the Equipment pull down menu.
Two options are available:
Subrack level: prints or write on a file the remote inventory data of the subrack.
Board level: show the remote inventory data of the selected board
Figure 72.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
105/396
Figure 73.
The remote inventory data of the Subrack level can be printed on the default printer or to a file in postscript
or ASCII format.
Figure 74.
Select Printer
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
106/396
Figure 75.
ED
03
Select Output Format for file
SC.3: NE MANAGEMENT
107/396
9.7
Click on Show Supporting Equipment menu option of the Equipment menu to navigate to the equipment
that supports the selected board.
Figure 76.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
108/396
10 BOARD VIEW
10.1 Introduction
The Board View permits to show the physical port available in a specific board and to access the Port view.
The "Board view" is reached selecting the Equipment option in the View pull down menu, then double
clicking on the selected board to show the relevant Board view, presenting the ports.
In case of board with multi access SDH another view permits to select the SDH port.
An example of "board view" with the presented port is in Figure 78.
Alarms and Status indications referred to the board level are present at the bottom of the view, as indicated
in the example (Administrative State and Board Alarms/Status).
This information are "In/Out of service" of the board (Administrative State) and board alarms and status like
"missing" (RUM) or "mismatch" (RUTM), EPS condition if supported and other indications typical of each unit.
In the Maintenance section details on this indication are given.
Figure 77.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
109/396
Figure 78.
A port type is described with a board rectangular view and port identification.
The port identification is usually internal to the rectangular board (see Figure below. one example of optical
port)
(SDH)
Figure 79.
(ATM or IP)
(PDH)
(GBit ETHERNET)
The operator is provided with a representation of the port alarm synthesis on each port.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
110/396
Note: this option is accessible after the selection of a port contained in the view.
Change Physical Interface: Change the SPI or PPI object into PPI or SPI (and vice versa) on the bimode port (140Mbit/s / STM-1 switchable).
ISA Port Configuration: It allows configuring the TPs for the ATM connections.
Figure 80.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
111/396
Figure 81.
Figure 82.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
112/396
Figure 83.
Figure 84.
ED
03
Subrack level
SC.3: NE MANAGEMENT
3AL 98253 ADAA
113/396
11 PORT VIEW
11.1 Introduction
This section describes the operations necessary for the consultation, modification and configuration of each
port.
The Port View permits to set and show the transmission resources (i.e. the Termination Point, TP) referred to
the specific Port; it permits to check the detailed alarms presented by each TP of the Port, and the
available menu permits to configure the port, (many setting options listed in the port menu are common
with the "Transmission" view).
In these views are presented only the TP specific of the port.
The menu differs according the port type (SDH, PDH, HOA, ATM/IP/ETH).
The Port View can be accessed from the Equipment or Transmission Views.
The "Port view" is reached selecting the Equipment option in the View pull down menu then double clicking
on the presented rack/subrack to present the subrack view, as described in chapter "Show supporting
equipment"
Double clicking on the selected board the relevant Board view is available presenting the ports.
By double clicking on a board view, the corresponding port view is opened.
The "Port view" is also reached selecting the Transmission option in the View pull down menu.
Then the Add TP option of the Transmission menu permits to select and confirm a TP.
On the transmission view, which appears, select the TP and on the Transmission menu select the Navigate
to a port view option.
The HOA port view can only be reached from the Transmission view, selecting a VC or TU TP.
The ATM/IP/ETH TPs are not automatically created when the board is inserted in the subrack but must be
created as explained in chapter ATM/IP/ETH Configuration
From the Port view It is possible to Navigate to Transmission view.
The port types contain the following TP:
ED
SDH port: Electrical or Optical SPI TTP, RS TTP, prot TTP (MSP TTP), AU4 CTP, Trail Monitor (only
with enabled POM)
HOA port: VC4 TTP, TUG3, TUG2, TU3, TU12, Trail Monitoring (only with enabled POM)
ATM port: VC4C TTP, VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP and E1 TTP
Fast ETHERNET port: MAU, PTC, VC3XV, VC12XV, VC4 TTP, VC3 TTP and VC12 TTP
Gigabit ETHERNET port: MAU, PTC, VC4XV, VC4 TTP, VC3 TTP and VC12 TTP
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
114/396
Figure 85.
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.
TP Role
The icon boxes represent the function: Adaptation, Termination or Compound Adaptation and
Termination.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
115/396
Cross-connected state
If the condition of the resource is cross-connected, an icon with a x appears beneath the box.
Performance State
If the condition of the resource is under performance monitoring, an icon with a P appears beneath
the box.
Loop state
If the condition of the resource is under loop, an icon with a L appears beneath the box
Selected state
An orange frame around the box identifies the TP selection, so port menu refers to the selected TP.
Figure 86.
Figure 87.
ED
03
Termination TP box.
SC.3: NE MANAGEMENT
3AL 98253 ADAA
116/396
The menu differs according the port type (SDH, PDH, HOA and ATM), and is introduced in the following:
TP configuration: Set parameters for the Signal Label and Path Trace overhead on Synchronous
TP's.
Set Retiming: Enable/disable the retiming feature on the outgoing 2 Mbit/s signal.
Monitoring Operations: Set parameters for POM/SUT and TC (Tandem Connection) TPs. Not
available for PDH port.
Physical Media: Manage the physical setting of the TP of the port. Not applicable to HOA port. It is
described in the following paragraph.
Show supporting board: Navigate to the upper board level. It is described in this chapter.
Navigate to Transmission view: permit to show a complete overview about the signal flow, opening
all TP's
Navigate to Monitor view: permit to show an overview about the monitoring operation (POM, SUT,
TC) all TP's.
Figure 88.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
117/396
When the Retiming feature is disabling, the color of the state information at the bottom of the window is
brown and the label "Retiming State Disable" is written.
Figure 89.
As result of this operation the state information color become green and the label "Retiming State Enable" is
written.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
118/396
Figure 90.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
119/396
Figure 91.
The Concatenate button will be enabled and the Deconcatenate button will be disabled when is selected a
non concatenated AU4, vice versa when is selected a concatenated AU4.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
120/396
Figure 92.
The port view represented in Figure up. Shows an STM4 interface with four AU4 concatenated in one AU4c.
The AU4c appears as a single icon that has the same size of the actual AU4 blocks. The AU4c streams
support the Alarm synthesis, Cross-Connection states and Performance Monitoring information as standard
AU4 streams.
To deconcatenate an AU4c select again the "AU4 Concatenation" option in the Port View menu and then
select the AU4c to deconcatenate. Click on the Deconcatenate push button to apply the command or on
Cancel to exit.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
121/396
Figure 93.
SDH port:
- ALS Management
- Show Optical Configuration
- Tx Quality Configuration
- Single Fiber Configuration
- LAPD Configuration
- Ms Configuration
PDH port:
- Line Length Configuration.
- HDSL Configuration. Not operative
- NT G703/704 Configuration. . Not operative
- NT X21 Configuration. . Not operative
ETHERNET port:
- Remote Laser Management. Not operative
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
122/396
These options are described in next paragraphs except the previously referenced.
Figure 94.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
123/396
Figure 95.
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.
2) Force laser OFF.
To carry out a laser forced OFF, select the Laser Forced OFF option of the ALS Function
then click on Apply and then or close push button to close the dialogue
c) Delete: this option deactivates the ALS function, returning to the state.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
124/396
From this window it is only possible to create the ALS function (all ALS commands are grey)
Figure 96.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
125/396
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.
Figure 97.
Figure 98.
ED
SC.3: NE MANAGEMENT
3AL 98253 ADAA
126/396
The wavelength of the laser source: the units are nanometers (nm = 10-9 m).
The use of the port: describes whether the laser port is used for interoffice transmissions on long
distances (Long Haul) 40 km) or for interoffice transmissions on short distances (Short Haul ] 15
km).
The Colored Interface Parameters section is not applicable in the current release
To close the dialogue box click on the Cancel push button.
11.6.3 Single Fibber Configuration
The single fiber configuration can be realized with passive optical couplers.
The optical coupler must not loop the Tx signal onto the local Rx.
For this purpose and in general to avoid a low Tx/Rx decoupling also when the optical line is interrupted, an
identification label has been assigned to the local Tx side; the Rx part in the remote receive side checks the
congruency between the received and the expected labels. If a signal label mismatch is recognized on the
received section, an alarm (AIS and RDI) will be generated. Example of Figure below. Shows that are
accepted the label "1" from Tx1 to Rx2 while is accepted label "2" from Tx2 to Rx1.
Figure 99.
Select the Physical media option and then from the cascading menu the SDH Single Fiber Configuration
option.
In the figure that opens, the following fields have to be considered:
Allow Single Fiber - select the transmit mode on the single fiber (enable or disable).
Transmitted Section:
Transmitted Media Byte - assigned label to Tx (0-14)
Transmitted Media Type - overhead byte used for the communication:
- Media Dependent byte of Regeneration Section or
- S1 byte of Multiplex Section (the part not used for the SSM)
ED
Received Section:
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
127/396
Received label
Figure 100.
11.6.4 Ms Configuration
The Ms Configuration menu allows the SS bit provisioning for Multiplex Section Object (MSTTP) in
SONET/SDH network interworking.
Select the MSP TP.
Click on Ms Configuration menu option of the Port menu.
This dialog allows selecting between SDH or SONET networks. After the selection click on Apply and then
on Close to close the dialog.
Ms Forced AIS is not supported in the current release.
Figure 101.
ED
03
Ms Configuration
SC.3: NE MANAGEMENT
3AL 98253 ADAA
128/396
Figure 102.
Figure 103.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
129/396
Figure 104.
For the Fast Ethernet (10/100 Mbit/s) port it is possible to choose between two Configuration Type:
1. Auto navigation : enable allows to configure the "Rate" to be negotiated (10 or 100 Mb/s). The
"Directionality" (Full Duplex) and the "Flow Control" (Activated) are always enabled and can't be
changed.
2. "Manual: allows forcing the "Rate" at 10 or 100 Mb/s.
The "Directionality" is always Full Duplex.
Moreover It is possible to Restart the Auto Negotiation by depressing the relevant button; if parameters
has been changed before pressing the Restart button, a question dialog is displayed to advice that the user
has changed data but not applied them.
Figure 105.
Information dialog
In read only mode there are indication if the Auto negotiation on remote side is activated (Remote Auto
Negotiation) and what parameters are allowed on remote (Remote Allowed Parameters).
In both cases is possible to check the Auto negotiation Current State with the possible massage:
Completed OK
Completed KO
Configuring
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
130/396
Deactivated
Parallel Defect Fail
Other
At the bottom of the port view are displayed the following indications:
S100BaseTX
S100BaseFX
Unknown
S10BaseT
10 Mb/s
100 Mb/s
Figure 106.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
131/396
Click on Port Ethernet Mapping Protocol option of the Port> Physical Media menu. Figure below opens.
Figure 107.
This dialog aims to show the actual Ethernet mapping protocol used and allowing the user to change it. The
options available are the following:
FAST ETHERNET boards:
GFP null extension Header with FCS
GFP null extension Header without FCS
GFP for packed concatenation extended
GIGABIT ETHERNET boards:
GFP null extension Header with FCS
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
132/396
Figure 108.
On the contrary to change in Idle the Active state of a TP decrease the Virtual TPs to be active field and
then and click on the Apply button.
Click on the Refresh button to update the changes.
Click on Close button to close the Control Path Activation window.
Example figure below is the Active state.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
133/396
Figure 109.
MaxDifferentialDelayPackage for reporting the max supported (by the board) differential delay and
for configuring the maximum tolerated differential delay; the default value has been chosen at
48(ms).
RsAckTimeoutPkg for configuring the timeout of re-sequence acknowledge; the default value has
been chosen at 512 (ms) .
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
134/396
functionality is not working if LCAS protocol is not activated, but its possible to de-activate from last active
member. Simmetrically the capability of activating (ADD) specific members ( vc-nVirtualTTP) is supported.
The activation of LCAS protocol on a virtual concatenation group already working is possible, but its a trafficaffecting operation since it requires to de-activate all members before LCAS enabling.
The symmetrical operation (even if not meaningful) of de-activing the LCAS protocol on a virtual
concatantion group already working is possible, such operation impacts the traffic bandwidth transmission
since it requires of remaining with only the vc-VirtualTTP with ID=1 as active member.
11.6.9.1.3 LCAS protocol information
For monitoring the LCAS protocol the LcasMonitor action is provided; some parameters returned by the
action are defined as Optional, the following ones are expected to be anyway returned:the number of
working members in tx, the number of working members in Rx, the member identifier reference for MST
(TBC), the received rs-ack bit (TBC), the transmitted rs -ack bit (TBC), the differential delay of each member.
11.6.9.1.4 Alarm indications
If the LCAS protocol is activated the following alarm indications can be raised:
At virtual path level (vc n Virtual TTP, n=12, 3, 4)
Member Not De-skew-able (probable Cause excessive Differential Delay): when the virtual path has
a differential delay which cant be compensated; if LCAS is not activated this alarm corresponds to
Loss Of Alignment alarm raised at virtual group level (virtual PTC). at virtual concatenation group
level (vc-nX Virtual TTP, n=12, 3, 4):
Loss Of Partial (probable Cause bandwidth Reduced): when one of active members vc-n Virtual TTP)
is affected by SSF, TIM, UNEQ, L OM or Excessive Differential Delay.
Loss Of Total (probable Cause server Signal Failure): when all the active members are affected by
SSF,TIM, UNEQ, LOM or Excessive Differential Delay.
LCAS protocol failure (probable Cause communications Protocol Error) raised when inconsistent
sequence numbering of the members is received or the CRC error control fails on LCAS multiframed
packet.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
135/396
In the following picture we can note that are managed all the attributes described before and the two actions
are managed by means of the two buttons (Enable/Disable and Monitoring...).
Figure 110.
LCAS Configuration
The "Monitoring..." button start the "LCAS protocol monitoring" view like the figure below.
Figure 111.
ED
03
LCAS Monitoring
SC.3: NE MANAGEMENT
3AL 98253 ADAA
136/396
The LCAS Monitoring window is divided in two section, the first reports information concerning the Virtual
Concatenation Group Monitoring Parameters, the second reports the Channels Monitoring Parameters.
Virtual Concatenation Group Monitoring Parameters fields description:
Active Channel Number: display the number of Vcs active on Source and Sink read on Node A.
Acknowledge Bit (ReSequence Acknowledge) Source and Sink: when a renumbering of the
sequence numbers of the members sending in CTRL field NORM, DNU, EOS, or when a change of
the number of these members is detected at the Sk, a notification to the So per VCG has to be
performed by toggling (i.e. change from 0 to 1 or from 1 to 0 ) the RSAck bit.
MST Channel Ref.: indicates wich channel of the VCG is the reference one for MST information;
MST information report the member status from Sk to So with two states: OK or FAIL (1 status bit
per member).OK = 0, FAIL = 1.
VCG Master: indicates wich channel is the reference channel for the Differential Delay calculation.
Channels Monitoring Parameters fields description:
The first column contains the channel identifier inside the VCG (called Sequence Number) .
Tx CTRL Packet: Message sent (ADD, DNU, IDLE, NORM, EOS, FIXED), relative to a traffic flow
from Node A to Node B; it provides the status of the individual member of the group as reported in
the following:
Fixed: this is an indication that this end uses Fixed bandwidth (nonLCAS mode)
Dnu: Do Not Use (the payload) the Sk side reported FAIL status
Unknow
Rx Channel State: MST indication (OK/FAIL) relative to a traffic flow Node B to Node A;
Rx CTRL Packet: Message received (ADD, DNU, IDLE, NORM, EOS, FIXED), relative to a traffic
flow from Node B to Node A; it provides the status of the individual member of the group as reported
in the following:
ED
Fixed: this is an indication that this end uses Fixed bandwidth (nonLCAS mode)
Dnu: Do Not Use (the payload) the Sk side reported FAIL status
Unknow
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
137/396
Tx Channel State: MST indication (OK/FAIL) relative to a traffic flow Node A to Node B;
Differential Delay: it is calculated respect to the Virtual Concatenation group Master channel,
relative to a traffic from Node B to Node A .
TxVC: contains the sequence number assigned to a specific member from Node A to Node B. Each
member of the same VCG is assigned a unique sequence number, starting at 0.
RxVC:contains the sequence number assigned to a specific member from Node B to Node A. Each
member of the same VCG is assigned a unique sequence number, starting at 0.
G.703/G.704 management
This functionality allows to activate the adaptation function to process a framed (G.704 interface) or not
framed (G.703 interface) 2Mbit/s signal.
This TP Frame Mode Configuration option is available for: P12CTP
Select the desired P12CTP and then the Port >TP Frame Mode Configuration option.
TP Frame Mode Configuration can also be accessed from the Transmission and Synchronization view
menu.
The following dialog appears:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
138/396
Figure 112.
Framed Signal Mode that allows to configure the attribute framed Signal Mode; the user can choose
one of the following value:
Framed without PRA (G.704): the behavior according to ETS 300233 is applied in the handling of
bits of Time Slot 0 in terms of state, defect detection and consequent action;
Framed with leased line PRA: a proprietary leased line behavior is applied.
CRC4 Status that defines the monitoring capabilities applied to the signal with a CRC multiframe:
Operation: allows configuring the CRC4 processing modalities; the possible value is:
ED
SC.3: NE MANAGEMENT
3AL 98253 ADAA
139/396
Automatic that triggers the CRC4 algorithms in order to allow interworking of pieces of equipment
with and without a CRC4 capability.
Remote Indication: readonly field that indicates if status of CRC4 error counting functionality of
farend NE is enabled or disabled.
Loss of Synch Consequent Action allows to perform the consequent action on the transmitted
2M/s signal with retiming when the CRU is in Holdover or Free running mode; the consequent action is
performed only if PRA or leased line application ha been configured on the associated P12CTP.
Frame Status is a readonly field that reports an indication of the received signal:
No indication
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
140/396
Figure 113.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
141/396
Navigation to the Transmission view permits to show a complete overview about the signal flow as for the
example of the following figure.
Figure 114.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
142/396
Figure 115.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
143/396
Figure 116.
ED
03
View of Monitoring Operations (example)
SC.3: NE MANAGEMENT
144/396
Click on Port mode option of the Configuration> Port mode menu. Figure below.
Figure 117.
Figure 118.
You can select the port type you want to see, and click the search button to list them. As below, then you can
click the port you want to set at the found port list table. And set the port mode.
Port Mode Overview Dialog allows a centralized mechanism for:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
145/396
To prevent alarms from being raised and failures being reported during trail provisioning actions, trail
termination functions have the ability to enable and disable fault cause declaration.
This is controlled via their termination point mode or port mode parameter.
The termination point mode can be either monitored (MON) or not monitored (NMON). The state can be
MON if the termination function is part of a trail and provides service and NMON if the termination function is
not part of a trail or is part of a trail which is in the process of set-up, breakdown or re-arrangement.
In physical section layers, the termination point mode is called the port mode. It has three modes: MON,
AUTO, and NMON (the last is not supported).
The AUTO mode is like the NMON mode with one exception: if the LOS defect clears, the port mode is
automatically changed to MON. This allows for alarm-free installation without the burden of using a
management system to change the monitor mode.
Change of Port Mode setting can be done on the selected ports in the matrix gadget. Multiple selection is
allowed. The user can choose the new Port Mode ( in the Define Port Mode Values field) and can start the
change on the selected ports (Set Mode).
Change of Port Mode System Default can be done in the related frame Current system default is visualized
in the combo box current value. Port Mode Overview dialog is available both at Configuration menu and Port
View menu and Transmission View as well. Using it at Configuration menu the multi port working mode is
enabled with full support for search and filtering. Using it in Port View or Transmission View enable the
single port functionality and the search capability is greyed out.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
146/396
Figure 119.
ED
03
set the selected port mode
SC.3: NE MANAGEMENT
147/396
Protection priority:
A priority can be assigned to protected units in 1+n protection schemes. This priority can be 1, 2, ...
or n, 1 being the highest priority.
Board duplication remains the easiest way to ensure equipment protection in a system.
The actions that can be undertaken are of the following type:
In Board view, the board whose content is represented is considered as implicitly selected.
The functional state message area of the boards involved in an equipment protection scheme displays EPS
protection states.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
148/396
Select the EPS pull down menu. Then select the Management...
Figure 120.
Consulting EPS
Figure 121.
The EPS Management dialogue box shows the current NE protection schemes in the left side. The list
gives for each protecting board the protected board(s).
The available protection schemes are coherent with the NE type and release.
The right side of the dialogue box allows modifying the EPS configuration.
The current release of this NE fixes the following protection:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
149/396
N.B. For P3E3/T3 and P4ES1N more than one protection group N+1 revertive can be created, depending
on the equipment configuration. The spare board position can be assigned in a flexible way. The only
constraint is the following:
The access card corresponding to the protecting board must be an HPROT card
The HPROT card has to be plugged at the left side of the access card group
The protecting board has to be plugged at the left side of the protected group of boards
N.B. For each type of failure on the MATRIX main board (CRU, Shelf Controller) a switch is performed to
the spare boards
The COMPACT ADM protection is automatically presented in the left side of the dialog box when
the SPARE COMPACT ADM is created in the Set option of the Equipment menu. It is not created with
the EPS menu described in this chapter.
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
150/396
The lower part provides a list to display the Protected boards currently in the displayed scheme.
A choose button is provided to display the list of boards which could be added as protected.
A delete button enables user to remove a protected board from a scheme.
a) Scheme displaying
To display a specific scheme, user selects an item on the left list.
This operation fills the protecting element text field and the protected list with the board user name. If user
clicks where there is no item displayed, the right part is displayed empty.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
151/396
Figure 122.
ED
03
EPS: board selection
SC.3: NE MANAGEMENT
152/396
Figure 124.
Figure 125.
Select the EPS pull down menu. Then select the Configure.
Figure 126.
Configure EPS
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
153/396
Figure 127.
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.
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
154/396
Select the EPS pull down menu. Then select the Switch.
Figure 128.
Switching EPS
Figure 129.
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
155/396
Selecting the EPS Overview option from the Configuration pull down menu Figure below. Opens:
Figure 130.
EPS overview
To Search the EPS groups two different ways of filtering are supported; a filtering for all protection units
located on a dedicated Board Type as well as a filtering for protection units carrying a specific Status.
The search criteria can be chosen with the help of a combo box:
- Board Type: allows filtering for the EPS protected boards; the following filters values should be offered
(examples)
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
156/396
- Status: allows filtering for all possible EPS protection states; the following values should be offered
(examples):
Ignore
Normal
DNR
Auto-Fail
Auto-WTR
Manual
Lockout
After the filter selection click on Search button to start; the field below the Search button will be updated
(see Figure below.)
Figure 131.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
157/396
Board Role:
Ped
(Protected)
Ping
(Protecting)
(Active)
(Standby)
(Faulty)
Protection Status: defines the current state of the protection unit follow
Normal
DNR
Auto-Fail
Auto-WTR
Manual
(Manual switch)
Force
Lockout
The colors used for each row have the following meaning:
-
- Red (Critical): for protected protection units in fail condition, protection unit in lockout or active on auto
switch or commands
- Orange (Major): for protected units in standby after a command and protecting protection unit in standby
for auto switch or commands
- Cyan (Indicative) for protecting protection unit active and no fail condition present in the schema (Do Not
Revert State)
At the button of the EPS Overview windows are available five buttons that allows navigating through the
EPS management views and subrack view, board view. In this way the operator has a quick link towards the
views showing the correlation between the alarms and the protection states.
N.B.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
158/396
Symbol
Open Board View: opens the board view showing the alarm and the board administrative states
Open Commands: opens the EPS Switch dialog box, and the relevant description.
EPS Management: opens the EPS Management dialog box, and the relevant description.
EPS Parameters: opens the EPS Configuration dialog box, and the relevant description.
Figure 132.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
159/396
Figure 133.
ED
03
Board view after Open Board View command
SC.3: NE MANAGEMENT
160/396
The Multiplex Section Protection in the connection between two NEs protected by cable and port duplication.
At the source the signal is duplicated and sent to the sink via two independent cables. When occurs a
multiplex section failure, the system switches to the other cable and port.
The MS Linear Trail Protection can be applied to any NE where it is possible to configure a linear APS
(single ended/dual ended) line protection. For this NE is applicable the APS 1+1 Proprietary, m the APS 1+1
Standard and the APS 1:1 Standard dual ended.
The APS 1+1 (not revertive) feature permits a 1+1 protection in a linear link, where a path signal is protected
by another dedicated path carrying the same signal. The protection can be set both in single (unidirectional)
and in dual (bidirectional) ended mode.
In single ended mode (unidirectional) the protection is accomplished by switching only the signal affected
by the failure.
In dual ended mode (bidirectional) the protection is accomplished by switching both the affected and the
unaffected signals.
Architecture 1+1 or N+1 Standard
Described in ITU-T Rec. G783/G841. The reference switching criteria are SF and SD. It provides a
k1/k2 communication protocol thus this protection can be single or dual ended.
Architecture 1+1 Proprietary (not used)
The reference switching criteria are SF and SD. No k1/k2 communication protocol is provided thus
this protection can be only single ended.
Architecture 1+1 Optimized (not used)
Architecture 1 : 1 Standard (not used)
Described in ITU-T Rec. G.783/G841 as architecture 1 : n (with n=1). The reference switching
criteria are SF and SD. It provides revertive mode managed by k1/k2 protocol and thus this
protection can be single or dual ended. The spare interface can be used to transport "low priority
traffic".
The WTR time is used with revertive mode.
Signal Degrade (SD) software setting enables the MSP protection mechanisms when a SD is recognized on
the working port. The SD threshold reference values depend on the NE selected threshold on the MS
termination point.
Double click on the SDH optical board to configure to open the port icon
- Select the MSP block in the port view and then choose the MSP options by clicking on Port -> MSP
menu; the possible choice are:
ED
MSP Create
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
161/396
MSP Management
MSP Commands
MSP Delete
MSP Create, MSP Management, MSP Commands and MSP Delete can also be accessed from the
Transmission-> MSP menu
Select the MSP Create option from the Port -> MSP menu (see Figure below.) to open the MSP Schema
Creation.
Figure 134.
Figure 135.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
162/396
MSP N: 1 standard
Select one and then click on Add Port button in the Ports field to create a MSP schema.
Figure below. Is opened
Choose Port
Figure 136.
Select the Choose Port button to define the "Protected Port" and "Protecting Port" units.
Figure below is opened.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
163/396
Figure 137.
TP Search
Click on Rack-Subrack and select the Board (Protected/Protecting) on the "Equipment" window (left side).
The "termination Points" list (right side) is available.
On this right side select the OpS TP of the chosen board and then click on the OK button. It is possible to
select the board through the "Board History" button selecting the board list menu.
The "Filter Section" is divided into different fields. It permits to visualize a reduced TP Class. If used, OpS
class must be selected. The complete TP research description is reported in the "Transmission View".
Click on the OK button and repeat the operation for both Protected Port" and "Protecting Port". If it has been
selected a Protected/Protecting port configured in a previously MSP schema protection an error message of
access denied will be appear on the screen.
In the dialogue of Figure below. Also configure the MSP protection schema with the chosen Protection
Schema and enter the related Schema Parameters according the following rules:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
164/396
At the end click on the OK button to confirm the MSP protection schema configuration. An error message will
be appear if the NE does not support the selected schema
Figure 138.
Figure 139.
The MSP Schema Configuration dialog shows the current state of the MSP schema, setting and state
(protected or protecting) of the current SDH-n port.
This dialog allows setting the configuration parameters for the designated multiplex section:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
165/396
Schema Parameters:
The WTR Time (Wait to Restore) is the delay time for switching protection and protecting port after
recovery from failure / defect.
Configure the MSP protection Schema with the chosen protection schema and enter the related schema
parameters. At the end click on the OK button to configure the MSP protection schema. An error message
will be appear if the selected schema in not supported by the NE.
Figure 140.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
166/396
Select the MSP Delete option from the Port->MSP menu (see Figure below.) to open the "MSP Schema
Deletion".
Figure 141.
Figure 142.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
167/396
Port Status - Active (red color) or Standby (orange color). The active protection status is referred to
a protected/protecting port (where the traffic is transported): when a failure is detected, the protecting
port is ready to save the traffic (and becomes active). The standby protection status is referred to a
protecting/protected port that is ready to save the traffic.
MSP Group Status, MSP Own Unit and MSP Related Unit - (green color) Displayed if an automatic switch
is requested. "Own Unit" stands for the currently displayed unit in the port view; "Related Unit" stands for the
related unit of the same protection group. The status indications are:
NR: (abbreviation of No Request); normal, idle condition, the traffic is on the main port
DNR: (abbreviation of Do Not Revert); the SF or SD has been recovered but the traffic is switched on
the spare port
PF: a protection failure has been detected on the port
RF: a release command has been failed
FOP: a failure of protocol has been detected
Complete: = the bridge/switch actions are completed
Pending: = the bridge/switch actions are pending
The "complete" and "pending" indications precede the following statuses:
AS: automatic protection switching enabled
MS: a manual local protection command has been activated
FS: a forced local protection command has been activated
LO: a lockout local protection command has been activated
SF/SD: Signal Failure or Signal Degraded has been detected
WTR: wait time to restore status
MSP Request Source - (green color) indicates where the operator commands (force/manual/lockout) have
been performed. Only present when a command is operative.
- Local: switch due to near end SD/SF or local user switch command
- Remote: switch due to received K1/K2 bytes.
A remote switch cannot be released locally, but can be overwritten by a switch with higher priority.
MSP Protocol Status
This parameter indicates the current APS Protocol status.
The following values are possible:
- OK
- Failure (in case of FOP)
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
168/396
Figure 143.
Figure up. Represent a MSP configuration with a normal condition, with an automatic protection switching
and with a forced command. In any situation are represent the statuses displayed on both
protected/protecting Port views. The Active status indication, with a forced command on the protecting group,
shows where the forced command is applied.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
169/396
Select the MSP Commands option from the Port -> MSP menu (see Figure below) to open the "MSP
Command window".
Figure 144.
Protecting Port: the location of the board hosting the protecting port is displayed.
Protected Port: the location of the board hosting the protected port is displayed.
The lockout of protection command denies working channel access to the protection section by issuing a
"Lockout" of protection request (on the "Protection Status" of MSP Management). It is possible to "Lockout
the Protecting Port" or "Lockout the Protected Port"; to remove the lockout commands select Release Ping
(for the protecting) and Release Ped (for the protected).
The Force to command switches the working channel (Protected port) to the protection section (Protecting
port), unless an equal or higher priority switch command is in effect or SF condition exits on the protection
section, by issuing a "Forced" switch request for that port (on the "Protection Status" of MSP Management).
It is also possible to switch back to the working channel using again the "Forced to" Protected port command.
For 1+1 non-revertive system, forced switch no working channel transfer the working channel back from
protection to working section, unless an equal or higher priority request is in effect. Since forced switch has
higher priority than SF or SD on working section, this command will be carried out regardless of the working
section condition.
The Manual to command switches the working channel (Protection port) to the protection section (Protection
port), unless a failure condition exits on the protection section or an equal or higher priority switch command
is in effect, by issuing a "Manual" switch request for that port (on the "Protection Status)" of MSP
Management). Is also possible to switch back to the working channel using again the "Manual to" Protected
port command.
For 1+1 non-revertive system, manual switch no working channel transfers the working channel back from
protection to working section, unless an equal or higher priority request is in effect. Since manual switch has
lower priority than SF or SD on working section, this command will be carried out only if the working section
is not in SF or SD condition
The Clear WTR command cancels the delay time for switching protection and protecting port after recovery
from failure/defect.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
170/396
The Exercise command issues an exercise request for protection channel and checks response on MSP
bytes, unless the protection channel is in use. This check controls the k1/k2 communication protocol
functionality to be sure that the protocol is right also on the protection section.
Not operative in current release.
Figure 145.
MSP Commands
The priority levels for the MSP commands are (from the higher to the lower one)_ Lockout. Force to, Autoswitch (SF&SD), Manual to.
Table 1. Gives the priority rules when are occurred two different commands. The first column on the left and
the first row at the top report the switch protection and the external MSP commands. The row/column
crossing gives the command or protection result (i.e.: if an "Auto-switch" and a "Manual to" command are
present, "Auto-switch" is operative.
Table 1. MSP commands and Auto-switch protection priority
Lockout of
Protection
Forced to
Auto--switch
Manual to
Lockout
Lockout
Lockout
Forced
Forced
Lockout of
Protection
Forced to
______________
Auto--switch
Lockout
Forced
Manual to
Lockout
Forced
ED
Lockout
03
______________
______________
Auto--switch
Auto--switch
______________
SC.3: NE MANAGEMENT
3AL 98253 ADAA
171/396
Selecting the MSP Overview option from the Configuration pull down menu Figure below opens.
Figure 146.
MSP overview
To Search the MSP groups two different ways of filtering are supported; a filtering foe all protection units
located on a dedicated Board Type as well as a filtering for protection units carrying a specific Status.
The search criteria can be chosen with the help of a combo box:
- Board Type: allows filtering for the MSP protected boards; the following filters values should be offered
(example):
ED
Ignore
P4ES1N
P4S1N
P4E4N
P4S4N
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
172/396
P16S1N
S-41N
L-41N
L-42N
S-161
S-161N
S-161ND
L-161
L-161N
L-161ND
L-162
L-162N
L-162ND
SYNTH16
SYNTH16N
- Status: allows to filter for all possible EPS protection states; the following filters values should be offered
(example):
Ignore
NR (Normal)
DNR
Auto-SF
Auto-SD
Auto-WTR
Manual
Force
Lockout
After the filter selection click on Search button to start; the field below the Search button will be update (see
Figure below.)
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
173/396
Figure 147.
Role:
Ped
Protected
Ping
Protecting
(Active)
(Standby)
(Faulty)
ET
Protection Status: defines the current state of the protection unit as follow
ED
NR
(Normal)
DNR
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
174/396
Auto-SF
Auto-SD
Auto-WTR
Manual
(Manual Switch)
Force
Lockout
APS Invalid
Bad channel
The colors used for each row have the following meaning:
-
- Red (Critical): for protected protection units in fail condition, protection unit in lockout or active on
autoswitch on commands
- Orange (Major) for protected units in standby after a command and protecting protection unit in standby
for autoswitch or commands
- Cyan (Indicative: for protecting protection unit active and no fail condition present in the schema (Do Not
Revert State)
At the bottom of the MSP Overview windows are available five buttons that allows to navigate through the
MSP management views and to open the Port View.
By clicking on Open Port View the operator has a quick link towards the view showing the correlation
between the alarms and the protection states.
N.B.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
175/396
Figure 148.
ED
03
Port view after Open Port View commands
SC.3: NE MANAGEMENT
176/396
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:
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.
ED
Provide the functionality to create/show Multiplex Section Protection (Not operative in the current
release)
Provide the possibility of configuring a selected TP. Calling the configuration dialogs of the common
Transmission/Port Views category accesses this functionality.
Provide the possibility of showing a detailed view of a TP with alarms, navigating to the Port view.
Provide the possibility of showing and setting Performance Monitoring parameters and data.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
177/396
Figure 149.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
178/396
Figure 150.
ED
All child nodes contain a short label indicating the position inside the tree.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
179/396
ED
Add TP
Expand
Hide
Hide TPs that are related to the selected TP or the selected TP.
TP Configuration
TP Threshold Configuration
Terminate TP
Disterminate TP
AU4 Concatenation
Cross-Connection
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
180/396
Monitoring Operations
Performance
Structure TPs
TP
Loopback
maintenance purposes
Manage
Physical Media
MSP
Manage the Multiplex Section Protection of the NE. Not available
for PDH port. See MSP Management. In this paragraph is not described the MSP>NE MSP
synthesis option of the Transmission menu, not used in this NE.
the
loopback
commands,
for
commissioning
or
These options are described in next paragraphs except the previously referenced.
Figure 151.
14.5 Add TP
Select the Transmission -> Add TP option.
This menu item opens the TP Search dialog. The TP Search dialog enables the user to search for and add a
TP to the Transmission View (e.g. search for all TPs on a board with PM enabled).
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
181/396
14.5.1 TP Search
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 .
Figure 152.
After double-clicking on an object, an Information window appears (see). The message text corresponds to
the object selected.
Figure 153.
ED
03
Information Window
SC.3: NE MANAGEMENT
3AL 98253 ADAA
182/396
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 154.
After clicking on Show CC State, a more detailed TP list is displayed containing TP cross connection status
information.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
183/396
Figure 155.
Figure 156.
Symbols in TP Search
The background color of the symbols represents the status of the TP:
Grey = inactive
Green = active
An easy way to recall to previously displayed boards is to use Board History. Select the relevant board from
the list.
Figure 157.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
184/396
Search Mode
Use Search Mode together with the filtering options provided below the TP list. The following options are
available:
Class:
Ignore, E1S, OpS, PPI, AU-4, VC-4, AU-4+VC-4, TU-3, TU-3+VC-3, TU2, TU-12, VC-12,
TU-12+VC12, AUX, MS, RS, OGP, GMAU.
Assign State:
Ignore, NML, EML
Location:
Permits to insert the location of the TP in the following format:
r<rack#>sr<subrack#>sl<slot#><port#>
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
185/396
Figure 158.
After activating the search process with the Search TP button, the following dialog box appears. Clicking on
Cancel can interrupt the search.
Figure 159.
N.B. When searching for PM-enabled TPs on NE, Rack or Subrack, the time for the request can be very high.
It is recommended to search for PM-enabled TPs at the board level (a board is selected for the search).
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
186/396
Common Buttons
The following buttons are available in all modes:
Ok
Closes the dialog and opens the Transmission View containing the selected TP.
Close
Closes the dialog without updating the Transmission View.
Print
This command is used to generate and print a list of TPs according to the current filter selection.
The command opens the following dialog:
Figure 160.
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 161.
ED
03
Print to File
SC.3: NE MANAGEMENT
3AL 98253 ADAA
187/396
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 162.
Example Printout
Help
This command opens the online help for the TP-Search dialog.
14.6 TP Configuration
Select the Transmission -> TP Configuration option.
TP Configuration can also be accessed from the "Port" view menu.
14.6.1 High Order TP Configuration
Depending on the TP selected, a dialog appears for the configuration of the main parameters of the objects.
Example:
J1 Path Trace.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
188/396
Figure 163.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
189/396
TP
VC-4 TTP
VC3-TTP
VC-12 TTP
(SDH)
(PDH)
Significant Byte
C2
C2
C2
V5
Default value
18
Click on Hex button will be opened displaying in hexadecimal code the same value reported in Transmitted
and received field.
Figure 164.
0: Unequipped
1: Equipped non-specific
2: TUG structure
3: Locked TU-n
4: Asynchronous 34/45Mbyte
19: ATM
21: FDDI.
ED
Automatic: the NE according the VC structure automatically selects the C2 Signal Label value.
SC.3: NE MANAGEMENT
3AL 98253 ADAA
190/396
Figure 165.
J0 Configuration
VC-12 TTP.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
191/396
Figure 166.
Click on Hex button will be opened displaying in hexadecimal code the same value reported in Transmitted
and received field.
Figure 167.
ED
03
J2 hexadecimal editor
SC.3: NE MANAGEMENT
3AL 98253 ADAA
192/396
One repeated byte allows setting one byte that will be repeated
Received fields are read only.
With the relevant button it is possible to enable or Disable TTI Monitoring.
Empty TTI send an all zeroes path trace.
14.6.3.2 V5 Signal Label
Received, Expected and Transmitted fields are read only.
They can display the following number, according the G.707 recommendations for the V5 Signal Label:
0: Unequipped
1: Equipped non-specific
2: Asynchronous
3: Bit Synchronous
4: Byte Synchronous
Automatic: the NE according the VC structure automatically selects the C2 Signal Label value.
To replace modified with the default, enter the default manually according to the value reported in Table 2.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
193/396
P12
This menu item enables the configuration of the most important transmission parameters concerning the
Primary Rate Access and G.703/G.704 frame management.
The following dialog appears:
Figure 168.
"Framed without PRA" (G.704): the behavior according to ETS 300-233 is applied in the handling of
bits of Time Slot 0 in terms of state, defect detection and consequent action;
"Framed with leased line PRA" a proprietary leased line behavior is a applied.
"CRC4 Mode" that defines the monitoring capabilities applied to the signal with a CRC multiframe:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
194/396
"Remote Indication": red-only field that indicates if status of CRC-4 error counting functionality of farend NE is enabled or disabled
"No indication"
This menu allows the operator to set the alarm thresholds for MST and VCi layer.
Select the MST or the VCi block
Select the Transmission -> TP Threshold Configuration option.
Figure below. Will be opened.
The user can select one of the two different Defect distributions:
- Poisson distribution enable configuration of the Excessive Bit Error Ratio (ExBER on MST, VCi)
threshold and of the Signal Degrade (SD on MST, VC) threshold of the TP's related counted primitives.
- Burst distribution enable configuration of the maximum number of error frames and the total a amount
of bad block per frame.
-
Figure 169.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
195/396
14.9 Terminate/Disterminate TP
Select the Transmission -> Terminate TP or Disterminate TP option.
Only one command in the menu is available, depending on whether a TP is terminated or not.
14.9.1 Terminate TP
Use this action to terminate a path. It can be performed on a AU-4 CTP.
A cross-connection between the selected AU-4 CTP (= aTP) and a modifiable VC-4 TTP (= bTP) is created.
Three TUG-3 and TU-3 are created if the modifiable VC-4 TTP was not already structured.
A cross appears in the icon of the terminated TP:
case
that
is
still
existing
any
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
196/396
Figure 170.
Monitoring Operations
Monitoring Operations can also be accessed from the "Port" view menu.
The commands of this menu item are for the management of the POM/SUT /TC (Path Overhead
Monitoring, Supervised Unequipped Termination and Tandem Connection).
This command is available for:
AU-4 CTP
TU-3 CTP
TU-12 CTP
14.10.1 Creation/Deletion
The dialog allows multiple object creation/deletion.
The dialog shown in the following Figure below opens
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
197/396
Figure 171.
After Matrix
The Supervisory Unequipped Termination, not operative in current release, has the following parameters:
Source
Bidirectional
Press Ok to apply the parameters or Close to close the dialog and discard the not with Ok applied changes.
When select and apply the Path Overhead Monitoring, the changes will be displayed in the Port View in the
following manner:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
198/396
Figure 172.
When select and apply the Tandem Connection Monitoring / Tandem Connection Termination, the changes
will be displayed in the Port View in the following manner:
Figure 173.
14.10.2 Configuration
Depending on the parameters selected in the Monitoring Operations Creation/Deletion dialog, not all
sections of the dialog are available.
N.B. It is possible to open the POM and TCT/TCM Configuration dialog for a CTP even if neither Path
Overhead Monitor nor Tandem Connection was created before (SUT isn't available in this release). No
changes can be made in this case and the values displayed can be ignored.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
199/396
Figure 174.
Monitor Configuration
TTI Definition
The TTI (Trail Trace Identifier) has a maximum length of 16 characters.
The following TTI Definitions are available:
TTI Expected
TTI Sent
TTI Enabled
TTI Disabled
Error Distribution
Poisson and Burst error distribution are supported
TCM/TCT Cons Actions
It is needed to support explicit consequent action activation (AIS insertion) for TCT sink and bidirectional.
Thresholds
Set the thresholds of the following parameters:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
200/396
Signal Degrade
Poisson mode only: from 10-5 to 10-9.
Excessive Error
Poisson mode only: from 10-3 also if presented a selection from 10-3 to 10-5
Burst Degrade
Select a value between 1 and 1000 errors/sec for the Burst Degrade threshold.
Burst Consecutive
Select a value between 2 and 10 sec for the Burst Degrade Consecutive.
Alarm Timing
Rising and Clearing Timing are not supported by OMSN.
Unequipped Trail
Not available
Figure 175.
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:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
201/396
TU-3.
TU-12.
TUG-2: TU-12.
14.12 Loopback
The commands of this menu item are for the management of the loopback commands, for commissioning or
maintenance purposes.
14.12.1 Loopback Configuration
The loopback can be applied at line (external to equipment) level or at internal equipment level. The
loopback commands are used to separate the communication network into independent part checking the
line/equipment functionality during the network installation or maintenance operation.
The loopback architecture provides four configurations.
Line Loopback And Continue
Line Loopback And AIS
Internal Loopback And Continue
Internal Loopback and AIS
Figure 176.
ED
03
Loopback configurations
SC.3: NE MANAGEMENT
3AL 98253 ADAA
202/396
SDH board:
The loopback configuration can be done only on SDH ports with the acronym ending with a
"N" letter (i.e. P4S1N, S-4.1N, L-4.1N, L-4.2N, etc.)
- Line loopback performed on:
EIS for electrical STM-1 SPI
OpS for optical STM-1, STM-4, STM-16 SPI
- Internal loopback performed on:
MsT TTP for STM-1, STM-4, STM-16 ports
Select the Transmission -> Loopback -> Port Loopback Configuration option.
Port Loopback Configuration can also be accessed from the "Port" view menu.
Figure 177.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
203/396
Figure 178.
Choose the TP clicking on the "Choose TP" button. Select the TP where to apply the loopback command.
For this NE the "Timed Loopbacks" field is not managed and thus Start/Stop loopbacks time is not editable.
14.12.2 Loopback Management
To manage the loopback configuration select the Transmission -> Loopback -> Loopback Management
option.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
204/396
Figure 179.
Loopback Management can also be accessed from the "Port" view menu and from the "Configuration
menu
Figure below. Opens.
Figure 180.
ED
03
Loopback Management
SC.3: NE MANAGEMENT
3AL 98253 ADAA
205/396
The configured loopback are listed into the current loopback table. This table can be managed by the
"Search" criteria, "Delete" and "Create" commands.
Search Criteria (operative): to configure the filter select the "Loop and Continue" type (Yes= Loop
And Continue, No= Loop And AIS) then select the "Directionality" Internal or Line and edit the Initial
TP Id (write: rack, subrack, board, port# and the TP type: EIS (SPI/PPI Electrical), OpS (SPI/PPI
Optical), MST and so on. For "Initial TP" has to be intended the outgoing signal while for "Destination
TP" the incoming signal. Enable the filter through the "Toggle Filter" Enable/Disable button. Click on
the "Search" button to start the configured loopback research into the current loopback table.
The "Delete" command permits to delete a loopback listed in the Current loopbacks Table: select a
loopback in the list and click on the "Delete" button.
The "Create" command permits to create a new loopback configuration: clicking on "Create" the
previous figure opens. Follow the previously paragraph indications to create a new loopback
configuration.
The activated loopbacks are signaled in the Port view and in the Transmission view as for the following
figures:
Figure 181.
Figure 182.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
206/396
Figure 183.
The Physical Media options permit to set physical configuration of each TP.
It opens a menu in which the various options will be available according the TP's type (for the option
common with the "Port view" reference is made to the relevant paragraph):
- ALS Management.
- Show Optical Configuration.
- TX Quality Configuration.
- Single Fiber Configuration.
- Extra traffic Not operative
- Regeneration Section management Not operative
- Line Length Configuration.
- Set Domain.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
207/396
Select the Set Domain option from the Physical Media cascade menu to present the following view:
The dialog-box 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 managers can be enabled contemporaneously, having in charge the TP.
The Manager List contains the list of managers ( i.e. RM, SY, NPOS , EML) that work on the NE.
The EML-USM administrator (SH or Craft Terminal) should set the Manager List only to remove a
manager in case of emergency (i.e. the Manager misses the NE connection).
Resource domain field allow selecting the domain among that displayed in the list, assigning it to
the TP.
The different domains could be assigned to different operators.
Figure 184.
ED
03
Set Domain
SC.3: NE MANAGEMENT
3AL 98253 ADAA
208/396
Figure 185.
Expand option
This menu item provides the possibility of displaying TPs that are related to the selected TP. These may be
TPs that are contained by the TP or TPs, which belong to the physical port that is actually connected to the
TP.
14.14.2 Hide
Select the Transmission -> Hide option.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
209/396
Figure 186.
Hide option
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
210/396
Figure 187.
Board View
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
211/396
Figure 188.
ED
03
Port View
SC.3: NE MANAGEMENT
212/396
The HOA port displays the internal structure of the payload, as for the following figure:
Figure 189.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
213/396
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:
"Definition of Termination Points" gives an overview about the termination points implemented on the
NE
"Split and Join Cross-Connections" describes how to split or join bidirectional cross-connections. Not
supported in current release.
"Protection Switching" deals with switching actions (force, manual, lockout protection) on crossconnections
"Print" deals with printing out list entries on printers or into files
"Show Cross-Connected TPs" describes the possibility of showing connections between two or more
TPs of different hierarchies, e.g. connection between AU4 and VC4.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
214/396
TUs form a Tributary Unit Group (TUG) and TUGs again can be combined into a VC. The AU of the signal,
together with the Section Overhead (SOH), finally makes up the STM-1 frame.
Figure 190.
ED
An AU Pointer area
A payload area
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
215/396
Figure 191.
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:
ED
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 21 x VC-2
Or 14 x VC-2 + 21 x VC-12
Or 7 x VC-2 + 42 x VC-12
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
216/396
Or 63 x VC-12.
STM-N signals are constructed by integer multiples of the basic signal STM-1 of 155.520 Mbit/s. For
example an STM-16 signal of 2.488.320 Mbit/s is generated by combining sixteen STM-1 signals byte
interleaved.
15.1.3 Definition of Termination Points (TP)
When ports are depicted on the user interface, the following abbreviations are used.
This section concerns the multiplex structure as well as on the information model of object-oriented
programming which was used when forming the user interface. As a rule, a Termination Point (TP) is the
starting and terminating point of a transmission segment. A distinction is made between the following types
of TPs:
Both TP types exist on the SDH level and the PDH level.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
217/396
The S1-CTP represents the non-intrusive monitoring of outgoing 2 Mbit/s PPI. The Mon.
(Monitoring) label indicates that is possible to enable the CRC4 control signal.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
218/396
On the PDH side, a pPITTP corresponds to the esTTP of the synchronous side.
Depending on the type, it can either display the characteristics of a 140 Mbit/s, a
45MBit/s, a 34 Mbit/s or a 2 Mbit/s port.
MSP definition
Transmit side, the MSNP (AU4-CTP) input enters two different MSNP/MSN (unprotected CTP) sources and
then the MSN-TTP working and protection sources (to insert the K1-K2 bytes) are sent to the own SPI
interfaces. Receive side; the working and protection MSN/MSNP outputs (AU4-CTP) enter in the switching
selector. The MSNP-TTP terminates the selected signal and checks the SSF and the MSP protocol failure.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
219/396
Figure 192.
ED
03
SC.3: NE MANAGEMENT
220/396
Figure 193.
TP names on 1662SMC
P
E4 CTP
eCTP
S4 CTP
p4
E31 CTP
eCTP
S31 CTP
p31
E32 CTP
eCTP
S32 CTP
p32
E1 CTP
eCTP
S1 CTP
p12Mon
E4 TTP
not supported
not supported
E3 TTP
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
221/396
ITU-T
E2 TTP
TP names on 1662SMC
not supported
VC-4 TTP
Vc4
VC-3 TTP
Vc3
VC-12 TTP
Vc12
ITU-T
TP names on 1662SMC
ESTTP
ElS
OSTTP
OpS
RSTTP
RST
MSTTP
MST
MSP
MSP
AU-4 CTP
Au4/Au4P
AU-4-4c CTP
Au4P-4c
VC-4 TTP
Vc4
TUG-3
Tug3
TUG-2
Tug2
TU-3 CTP
Tu3
TU-2 CTP
Tu2
TU-12 CTP
Tu12
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
222/396
Figure 194.
Unidirectional Connection
Figure 195.
Bidirectional Connection
Figure 196.
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
223/396
A unidirectional connection is routed from Input A to the Output (primary route). In the case of a failure, the
system automatically switches to the protection path from protection Input B to the Output. This second
connection is permanently kept in hot standby operation.
Figure 197.
N.B. By means of this connection are created links with SNCP protection.
15.1.6.2 Protected Bidirectional Connection
A bidirectional connection is routed from Input A to the Output C (primary route). Input A (input protected)
can be protected:
Figure 198.
N.B. By means of this connection are created links with SNCP protection.
15.1.6.3 Protected Broadcast Connection
The protected broadcast is realized as a set of independent, protected, unidirectional connections using the
same pair of input termination points. Each protection can be forced, locked out or switched independently.
Therefore, if a failure occurs at a certain input, it is possible that only some of the protections of the protected
broadcast actually switch to the protection input.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
224/396
Figure 199.
Protected Broadcast
Figure up. Shows a broadcast connection from input A to outputs A, B and C. Leg 2 and 3 are protected via
input B, whereas leg 1 is not protected.
In current release only one out of N legs can be protected.
15.1.6.4 Drop and Continue Connection
A Drop and Continue connection is a composed by:
A unidirectional connection routed from Input A to the Output C and also to Input protecting B.
Output C is protected; when receive from Input main the connection is defined normal,
when receive from Input Protecting main the connection is defined inverse.
All the connections are created in a single step of configuration.
Figure 200.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
225/396
High order concatenated signal cross connection (AU4xc between SDH ports)
Low order signal cross connection (TU12 cross connected with VC12; ports involved: SDH and
PDH )
Click on "Create" in the Cross Connection Management windows; a new window called "Main Cross
Connection" is opened.
Select the correct value in the fields "Type" and "Protection"
Click on "Choose" relative to the "Input" field; a new window called "TP search" is opened.
On the "Equipment" field select the Board, in the "Termination Points" field select the AU4
Click on "OK"; the "TP search" window is closed.
In the "Main Cross Connection" window repeat the same on the "Output" field and on the "Prot.
Input" field for protected connections
Click on "OK" in the "Main Cross Connection" window to terminate the creation and subsequently
click on "Cancel" to go to the "Cross Connection Management" window.
Click on "Search" in the "Cross Connection Management" window to see the new cross-connection
created.
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-#01AU4P-4c)
ED
In the "Main Cross Connection" window repeat the same on the "Output" field and on the "Prot.
Input" field for protected connections
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
226/396
Click on "OK" in the "Main Cross Connection" window to terminate the creation and subsequently
click on "Cancel" to go to the "Cross Connection Management" window.
Click on "Search" in the "Cross Connection Management" window to see the new cross-connection
created.
Select "Transmission" ""Add TP"; a new window called "Tp search" is opened.
On the "Equipment" field select the Board, In the "Termination Points" field select the AU4 and
click on "OK";
In the transmission window the AU4 block is displayed;
Select "Transmission" " "Terminate TP" ; a cross is displayed on the AU4 block
Click twice on the AU4 block and on the VC4 block that appears, then selecting the showed TUG3
Select "Transmission" " "Structure TPs" " then selecting the structure
N.B. The AU4 is then terminated on a VC4 of the matrix circuit of the COMPACT ADM unit.
The VC4 is automatically choose and indicated as "port # n", where "n" is the VC4 number.
This connection will appear on the Cross Connection Management view in a independent line.
If TU12 (example) are selected, in the transmission window clicking twice on the TUG3 and TUG2
blocks the TU12 are displayed
Select "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)
Repeat the same on the "Output" field and on the "Prot. Input" field for protected connections
Click on "OK" in the "Main Cross Connection" window to terminate the creation and subsequently
click on "Cancel" to go to the "Cross Connection Management" window.
Click on "Search" in the "Cross Connection Management" window to see the new cross-connection
created.
ED
configure the 4xANY board with the Equipment > Set menu
configure the 4xANY MODULES with the Equipment > Set menu and choose the traffic type that
must be supported by the module (e.g. FICON, FDDI etc.); after having selected the traffic type,
automatically a number of TPs (VC4) are generated for this port and can be viewed in the port view.
All the TPs must be used when the cross connection will be created.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
227/396
option of the menu bar; a new window called Main Cross Connection is opened.
Click on Choose relevant to the Output field; a new window called Search for Cross Connection
Output is opened.
On the Equipment field select the Board to be used for the connection with the 4XANY board (for
example S4.1N), in the Termination Points field select the AU4
Click on OK; the Search for Cross Connection Output window is closed.
Click on OK in the Main Cross Connection window to terminate the creation.
repeat the same procedure for all the VC4 generated for the specific traffic type associated to the 4xANY
module.
To check the presence of the new crossconnection select the Port >Cross Connection > Cross
Connection Management option of the menu bar; a new window called Coss connection Management will
be opened
Click on the Search button; all the cross connected TP will be displayed in the Cross Connection
in list field.
configure the ISA board with the Equipment > Set menu
define the TP that must be created on the ISA board by selecting the Configuration > ISA Port
Configuration menu (refer to Chapter 20 for details)
The ISA board TP cross connection is similar to that described for the 4xANY board .
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
228/396
Figure 201.
ED
03
SC.3: NE MANAGEMENT
229/396
Do not enter any search criteria and press the Search button to display a list of all existing crossconnections,
Enter Search Criteria (one or more) and then press the Search button to display a selection of
cross-connections. Set Ignore for attributes not to be used as filtering criteria.
Use button Cancel Search to cancel an active search request or close the dialog.
15.3.1 Search Criteria
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:
ED
Forced to Input
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
230/396
Forced to Protecting
Lockout
Normal I
Normal P
TP ID Prefix
Enter the TP type and physical location of the port, or only the physical location at least down to
board level, according to the following format:
R<rack#>s<subr.#>b<board#>/port#<port#>-TP.
The # within brackets identifies a number.
Figure 202.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
231/396
Prot. State
Detailed switching information in the format:
<Protection state> <traffic Ind> (<location>: <signal state>-<switch status>,
[<Location>: <signal state>-<switch status>])
<Protection state>
Normal, Auto, Lockout, Forced or Manual.
<Traffic ind>
Indicates the location of current traffic:
P (Protecting input) or I (Input).
<Location>
Indicates the location of the error signal:
P (Protecting input) or I (Input)
<Signal state>
Indicates the signal state: SD (Signal Degrade) or SF (Signal Failure)
<Switch status>
Status of the switch:
C (completed) or p (pending)
Example:
Auto I (P: SD-c)
There has been an Automatic switch from the protecting input to the Input where the traffic is
currently located. The reason for the automatic switch was Signal Degrade in the Protecting input.
The switch was completed.
State
Connection state indicating whether cross-connection is A (activated) or D (deactivated)
Dir.
Direction-related connection type:
uni (directional), bi(directional) or mp (multipoint), DC_N (Drop & Continue Normal) or DC_I (Drop &
Continue Inverse)
Input
Signal source; contains the TP type and physical location of the port according to the format
<Rack#>-<subr. #>-<Board#>-<port#>, <port#>#TP
The # within brackets identifies a number.
ED
Protecting Input
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
232/396
Protecting source (for protected cross-connections only); contains the TP type and physical location
of the port according to the format
r<rack#>s<subr.#>b<board#>/port#<port#>-TP.
The # within brackets identifies a number.
Output
Signal
destination
for point-to-point cross-connections, the TP ID of the destination is specified according to the format
Figure 203.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
233/396
Create a cross-connection.
The Main Cross-Connection dialog is opened.
Modify a Cross-Connection.
Available if just one cross-connection is selected from the list. The Main Cross-Connection dialog
is opened.
Activate a Cross-Connection.
Available if at least one cross-connection is selected from the list. Not operative.
Deactivate a Cross-Connection.
Available if at least one cross-connection is selected from the list. Not operative.
Delete a Cross-Connection.
Available if at least one cross-connection is selected from the list.
Split a Cross-Connection.
Available if at least one bidirectional cross connection is selected from the list.
Join Cross-Connections.
Available if two cross connections are selected. Not operative.
Protection Switching.
Available if exactly one protected cross-connection is selected from the list. The Protection Actions
dialog is opened.
Print.
Prints the filtered list of cross-connections.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
234/396
Figure 204.
Create Cross-Connections
To prevent operation faults, the system is designed according to the following guidelines:
ED
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 crossconnection is assigned to NML or it is not assigned to the user profile.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
235/396
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.
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 crossconnection 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
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
236/396
Figure 205.
Protection Criteria
HOT (available only for protected connections) Not operative in current release
To enter the Hold Off Time expressed in msec. HOT is the time between declaration of Signal
Degrade or Signal Fail, and the initialization of the protection switching algorithm.
Input
To enter the input TP, click the relevant Choose button and select the TP in the TP Search dialog.
Otherwise, select the input field and enter the name of the TP directly.
Prot. Input
To enter the protecting TP, click the relevant Choose button and select the TP in the TP Search
dialog. Otherwise, select the input field and enter the name of the TP directly.
Output
It is possible to enter one or more output TPs.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
237/396
To enter one output TP, click the relevant Choose button and select the TP in the TP Search dialog.
Otherwise, select the input field and enter the name of the TP directly.
To enter more than one output TP and create a broadcast connection, proceed as described
previously and press button Add afterwards. The previously chosen TP is then moved to the list box
located below. Click the Choose button and select the next TP in the TP Search dialog. Otherwise,
select the input field and enter the name of the TP directly. Repeat this procedure for each destination
TP. A list of all the selected output TPs is displayed in the list box located below it.
To delete a leg from the list, select the TP in the list box and click on the Delete Leg button.
N.B.
Non-intrusive
Monitoring
Adding a protection leg to a unidirectional cross-connection offers the ability to perform non-intrusive
monitoring on this cross-connection. No errors are introduced to the original cross-connection with
applying or removing the protection leg.
Table 5. Optional and Mandatory Configurable Parameters for Cross-Connection Creation
Input Parameters
Unidirectional/Bidirectional Cross
Connection
Not Protected
Type
Protected
Unidirectional/Bidirectional
D&C Topology
Protected
Unidirectional
Normal/inverse
Protection
Not Protected
Protected
Not Protected
Protected
Protection
SNCP-1
SNCP-1
Criteria
SNCP-N
HOT
operative)
(NOT
SNCP-N
Protected
Revertive
One TP
One TP
One TP
One TP
One TP
One TP
One TP
One TP
Input
Protecting Input
Output
_ not available
x configuration optional
Non-configurable Parameters
CC Topology
The topology of the cross-connection is indicated via two icons. The left-hand icon displays the
current topology and the right one displays a view of the topology following confirmation of the
current modifications.
In addition, the color of an icon indicates the connection state of the cross-connection:
Green -> active
Brown -> inactive
The icon is set according to the entries made in Type and Protection:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
238/396
Unidirectional, protected
Bidirectional, protected
Cross-Connection Icons
Example:
Figure 207.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
239/396
-- Input TTI
The received Trail Trace Identifier of the far end signal is displayed. Not operative in the current Release.
-- Output TTI
The Trail Trace Identifier of the transmitted (near end) signal is displayed. Not operative in the current
Release.
15.4.2 Create a Cross-Connection
This chapter lists the steps the user has to take to create a cross-connection using The "Main Cross
Connection"
For a detailed description of the single parameters.
For information on cross-connection types.
N.B. After creation of a cross-connection, the cross-connection list in the Cross Connection Management
dialog is not automatically updated. Use button Search in this dialog to update the list.
Create a Point-to-Point Cross-Connection (unit- or bidirectional)
1) Select the cross-connection type.
2) Select the protection state.
3) Select or type in the input TP.
To enter the TP, click the Choose button and select the TP in the Search for Cross Connection
Input dialog, or select the input field and enter the name of the TP directly.
The Search for Cross Connection Input dialog offers the possibility to list TPs according to different filter
criteria. E.g. to obtain a list of all not connected AU-4 TPs of a rack, first select the rack in the left list box,
then select the filter criteria Connection State "not connected" and Class "AU-4" and click on button Search.
The matching TPs are listed in the right list box. Select the input TPs in the list and confirm with Ok.
For a more detailed description on the Search for Cross Connection.
4) Select or type in the output TP as described in Step 3).
The following steps only apply to protected cross-connections:
5) Select or type in the protection TP as described in Step 3).
6) Configure the Revertive mode
7) Configure the Protection Criteria (Prot.Criteria)
8) The Hot (Hold Off Time) is not operative in current release
Press the button Ok to confirm the creation.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
240/396
Figure 208.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
241/396
and Class "TU12" and click on button Search TPs. The matching TPs are listed in the right list box. Select
the input TPs in the list and confirm with Ok.
For a more detailed description on the Search for Cross Connection.
4) Select or type in the output TPs as described in Step 3 )
Press the button Add Leg in the Main Cross Connection dialog and all output TPs are displayed in
the list box under the output field.
To delete a leg from the list, select the TP in the list box and click on the Delete Leg button.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
242/396
Figure 209.
ED
03
Search for Cross-Connection Output
SC.3: NE MANAGEMENT
243/396
Figure 210.
ED
03
Create an Unprotected Broadcast Cross-Connection
SC.3: NE MANAGEMENT
244/396
Figure 211.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
245/396
Modification
Not Protected to Protected
Normal/inverse
Normal/inverse
Protected
Not Protected
Protection Criteria
Unprotected
Protected
Revertive
Input
Protecting Input
Output
Type
D&C Topology
Protection
_ Not available
X configuration optional
The following few facts should be taken into consideration when modifying connections.
Unprotect a protected cross-connection:
When a protected cross-connection is being unprotected (protection changed to "not protected"), the
dialog displays the additional option button Unprotected.
It offers the choice of whether to keep the protected input TP (Input) or the protecting input TP (Prot.
Input) as the only signal source of the new unprotected cross-connection. Ensure that the active TP is
selected (i.e. check the protection state in the Cross-Connection Management dialog).
An example is in the following Figure.
In addition, a question box appears, asking the user to confirm the unprotect action.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
246/396
Figure 212.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
247/396
Figure 213.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
248/396
Loopbacks
Auxiliary channels
Thus the deletion of every active operation/connection/termination is necessary, in the same order as above
listed, before the deletion of a crossconnection.
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.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
249/396
The new cross connection has the same name and activation status as the old bidirectional one.
Figure 214.
b) Protected Cross-Connection
Splitting a protected connection results in one protected unidirectional cross-connection and one
broadcast with two legs. The input of the original cross-connection is one of the legs in the broadcast.
The other leg in the broadcast is the protecting input. The input of the broadcast is the output of the
original protected cross-connection.
Figure 215.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
250/396
1) Both unprotected, unidirectional and the input is the output of the other one, or
2) One of them is protected and unidirectional, and the other one a broadcast with two legs.
Restriction: the input of the broadcast connection has to be the output of the protected connection
and the legs of the broadcast match the input and the protection input of the unidirectional
connection, also refer to Chapter Split a Cross-Connection, effect b).
Both cross-connections have the operational state "enabled", i.e. they are listed in black color in the
Cross Connection Management dialog.
Join
Select exactly two cross connections in the Cross Connection Management dialog and press the Join
button. The cross-connections are joined without further confirmation from the user.
The original cross connection(s) disappear from the list in the Cross Connection Management dialog after a
successful action. Press Search to see the new cross-connections in the list.
The result is either a bidirectional or a protected bidirectional cross-connection.
If the original cross-connections have different names, the new name is a concatenation of the names of
both of them.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
251/396
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 216.
The dialog window enables the user to perform protection- related operations on protected crossconnections. These are:
Release Force
Forced switching is disabled and automatic protection switching re-enabled.
ED
SC.3: NE MANAGEMENT
3AL 98253 ADAA
252/396
Release Lock
The protection lock is disabled.
N.B. All the operations listed are context-dependent and are enabled or disabled ("grey") accordingly.
After completion of protection switching, the list entry in the Cross Connection Management dialog is
updated automatically.
After clicking on an action button and completing the action initiated, the dialog disappears automatically.
15.8 Print
This option is used to print the currently filtered cross-connection list and the related filter settings on the
default printer or to a file in postscript or ASCII format.
Figure 217.
Select Printer
Figure 218.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
253/396
An overview of signal flow can be requested by means of a user action. The user can select a TP and initiate
the action Show Cross Connected TPs from the Transmission view.
Figure 219.
The result is that all other TPs connected to the currently selected TP are displayed. A line indicates the
connection.
This functionality should only be applied selectively (either for a single TP or selected group of TPs).
Expanding and hiding TPs that are associated with the currently selected TP (e.g. show all TPs that are
above the TU12CTP) enables all the related TPs to be added to the view so that the complete signal flow
can be illustrated.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
254/396
Figure 220.
ED
03
Show Cross Connected VC4 of an AU4
SC.3: NE MANAGEMENT
255/396
16 OVERHEAD MANEGEMENT
16.1 Introduction
The purpose of this set of dialogs is to handle the operations on the Overhead (OH) bytes of the NE.
The possible operations are:
Overhead cross-connection
OH Cross-connection
The steps an operator has to do in order to perform the cross-connection are the following:
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:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
256/396
For STM ports it make sense to allow the operator to perform a total pass-through of the MSOH bytes. A
total msoh pass-through connection (connection between msPassThroughCTP points) is set-up only if no
single msoh pass-through connection are set and if no single msoh cross-connection are set. If a total msoh
pass-through connection is set, a single msoh pass-through connection or a single msoh cross-connection
cannot be set.
The steps an operator has to do in order to perform the total MSOH pass-through are the following:
OH Cross Connection.
OH Phone Parameters.
OH TP creation.
OH TP deleting.
Figure 221.
Overhead options
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
257/396
The Cross-Connection Management for Overhead dialog opens and allows to start the configuration.
Figure 222.
It is similar to the dialog used for the cross-connection of the TP for paths, then the same description
and functions are valid.
Next configuration steps use the Main Cross-Connection for Overhead dialog and the TP Search dialog,
also in this case already described for path management.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
258/396
Figure 223.
There is one big difference between the OH TPs and the other kinds of TPs: the OH TPs have to be:
The current implementation of the TP Search Dialog (TPSD) works only with created TPs.
In the following a description of the main functions and commands is given, also to list the Supported and
Not Supported operation.
Cross-Connection Management for Overhead dialog
Supported operations
Search cross connections/terminations according to one or more of the following filtering
attributes: type, TPs . The operator can set the filtering criteria, can start the search and select
one or more cross connections/terminations among those presented in a read-only list as a
result of the search operation. For each cross connection/termination matching the filtering
criteria, the following information is shown: direction (bidirectional) and the input, output TPs
involved ;
After choosing one or more cross connections/terminations, this dialog allows to:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
259/396
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 Delete and Print buttons are enabled only if at least one item is selected from the list.
A special dialog will ask the user for a confirmation.
The modify button is enabled if one (and only one) item is selected. It brings up the Main cross
connection dialog.
The create button is always enabled. It brings up the Main cross connection Dialog.
When some operation may affect the existing traffic, the operator is warned about that, and a confirmation
dialog must be answered to carry on/cancel the operation. The choices for this dialog are: yes/no for single
items, yes to all/cancel for multiple items
When used for OH purposes, the Cross-Connection Management dialog doesn't support the following
functionalities:
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
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
260/396
Navigation rack/subrack/board/port
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)
In this Network Element to connect the auxiliary / vocal channels and the Overhead bytes the following
operative indication must be observed:
-
The auxiliary and vocal channels TPs are in the SERVICE board of slot 20
The auxiliary channels are:
1 x G.703 2Mbit/s (not operative in current release); in the screen are indicated as:
- R01sr1sl20/port#03--#01-eOCTP
Expanding this TP, 31 referred TPs are presented
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
261/396
- R01sr1sl20/port#01-#02-q23TTP
- R01sr1sl20/port#01-#03-q23TTP
- R01sr1sl20/port#01-#04-q23TTP
-
The other boards used to terminate or cross-connect the OH bytes are the STM-n boards.
The OH TP is present in MS, RS and VC4 TP Class.
In these TPs the indication "...#0011 to 0099 (MS or RS) are referred to the coordinates of the Section
Overhead bytes on the SDH frame (1,1 to 9,9)
The voice channel are identified by the "ow" indication, the "FU" is for Future Use, the "NU" is for National
Use, "UC" is for User Channel and "Pass" is for Pass through channel.
The examples of the figure in this OH connection chapter can be helpful to the operator
16.5 OH TP creation
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 and allows to create the OH TP to cross connect.
In detail, the dialog-box contains the following graphical object:
- a Choose button is used to display a list of OH Tps to be created. The Choose button starts the
TP Search with predefined filtering; the TP Search dialog allows the operator to visualize only not
created OH Tps.
To visualize the OH TP in the TP Search view double clicks on the MS, RS or VC4 Tp.
- OH TP field displays the label of the selected OH Tp to be created.
Apply button is used to perform a create request of the TP displayed in the OH TP field. After having
performed the create request, the OH TP field is set to empty.
Close button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
Figure 224.
ED
03
OH TP creation
SC.3: NE MANAGEMENT
3AL 98253 ADAA
262/396
Figure 225.
ED
03
OH Search TP for creation
SC.3: NE MANAGEMENT
263/396
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 and allows deleting the OH TP no more involved in an OH crossconnection.
Figure 226.
ED
03
OH TP deleting
SC.3: NE MANAGEMENT
3AL 98253 ADAA
264/396
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu
the OH Phone Parameters option. Figure below. Opens.
Figure 227.
The interface field (at the top) where can be selected the phonic interfaces to be configured.
The phone number field, to set the telephone number for operator calls on the phonic interface.
The phonic extension field, where enable or disable the extension of the selected phonic interface.
If enabled the phonic signal is extended towards the external on the access panel of the NE.
Not operative in current release
Apply button performs the configuration change of the modified phone parameters of the selected phonic
interface without close the dialog
Close button close the dialog without changes of the data.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
265/396
17 Performance Monitoring
17.1 Introduction
The Performance Monitoring domain on the NE covers the monitoring of counter values for trail termination
points and connection termination points.
Examples of these counters are Error Seconds (ES) and Severely Error Seconds (SES).
The Performance Monitoring domain counts these errors during specified granularity periods (15 min, 24h)
and stores the values in history data logs.
For the purpose of quality supervision, the values of the error counters can be compared to user-defined
threshold levels. If a counter value has crossed a threshold level, a notification (threshold crossing alarm) is
issued.
The principle performance management functions are:
Configuration of the quality thresholds that generate alarms and log records when predefined values
are exceeded.
On the ETHERNET boards a set of performance counters are foreseen, for future releases ,for QoS and
maintenance purpose. By selecting the GMAU TP and subsequently the Transmission >Performance menu,
the following options are available:
Configure Performance Monitoring. Not operative in current release.
Display Current Data. Not operative in current release.
Display Maintenance Counter. Not operative in current release.
17.1.1 Overview
These functionalities are described in the following chapters in addition to general information concerning
performance monitoring on the NE.
Chapter Display Current Data deals with displaying current performance data
Chapter Display History Data deals with displaying history performance data
Chapter PM Threshold Table Selection deals with the selection of threshold tables
Chapter PM Threshold Table Modification/Display deals with the modification of threshold tables
and permits or display the same
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
266/396
Background Block Error (BBE): A BBE counter measures the number of error blocks, which do not
occur as part of an SES.
Error Second (ES): A one second period with one or more error blocks or with a defect.
Severely Error Second (SES): A one second period which contains > 30% of error blocks, or at
least one Severely Disturbed Period (SDP). An SES is also counted as an ES.
Near End Unavailable Second (NEUAS): An Unavailable Second is a second, which is part of the
Unavailable Time.
Far End Background Block Error (FEBBE): A far end error block, which does not occur as part of
an FESES.
Far End Error Second (FEES): Identifies, at a terminal, a one second period with one or more error
blocks or with a defect, which were received by the Far End Terminal.
Far End Severely Error Second (FESES): Identifies, at a terminal, a one second period which
contains > 30% of error blocks, or at least one Severely Disturbed Period (SDP) which was
received/detected by the Far End Terminal. An FESES is counted as an FEE.
Far End Unavailable Second (FEUAS): An Unavailable Second is a second, which is part of the
Unavailable Time at the far end.
The Termination Point (TP) type determines which performance monitoring events can be counted:
-
SDH TPs
Both near end and far end counters are supported in receive direction of the signal for all SDH path
layers and for the multiplex section layer. For the regenerator section, no far end information is
transmitted and, therefore, only near end counting is supported.
PDH TPs
Only near end counters are supported in receive direction for all PDH path layers.
Further definitions:
Error Block (EB): A block in which one or more bits associated with the block are erroneous.
Remote Error Indicator (REI) [formerly Far End Block Error (FEBE)]: Identifies, at a terminal, the
count of error blocks that were received by the far end terminal.
Remote Defect Indicator (RDI) [formerly Far End Receive Failure (FERF)]: indicates to a terminal
that the far end terminal has detected an incoming failure.
Unavailable Time (UAT): A period of unavailable time begins at the onset of 10 consecutive SES
events. These 10 seconds are considered to be part of unavailable time. A new period of available
time begins at the onset of 10 consecutive non-SES events.
Pointer Justification Event (PJE): A PJE is an inversion of I- or D- bits of the pointer, together with
an increment or decrement of the pointer value to signify a frequency justification.
Out of Frame Second (OFS): An AFS is defined as a second in which one or more out of frame
events have occurred. This event is identified by the A1/A2 byte of the SDH Frame.
The counting of OFS is sonly supported for the regenerator section termination. Please note that this
counter is deprecated by ETSI and will be removed from international standards.
17.1.3 Far End (FE) and Near End (NE) Performance Counting
Far end performance monitoring parameters are derived from Remote Defect Indicators (RDI) and Remote
Error Indicators (REI).
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
267/396
Figure 228.
At Node A, the near end information represents the performance of the unidirectional section/path
from B to A, while the far end information represents the performance of the unidirectional
section/path from A to B.
At Node B, the near end information represents the performance of the unidirectional section/path
from A to B, while the far end information represents the performance of the unidirectional
section/path from B to A.
Near end performance data at Node A and far end performance data at Node B correspond as long as
neither direction is disturbed, and vice versa.
In compliance with ETSI and ITU-T standards, far end errors cannot be counted in the case of near end
failures.
17.1.4 Bidirectional Counting (24 h Bi) for QoS
As specified in G.826, G.784 and ETSI 300417, the bidirectional PM collection for Quality of Service has
been supported by combining the information on each direction of transport to assess a single unavailability
state: the bidirectional path is in the unavailable state if either one or both directions are in the unavailable
state.
PM data are collected by a single UAS plus two sets of three event counters (BEE, ES, SES) for NE-PM and
FE-PM respectively. When the path transports unidirectional payload just the four counters for the NE-PM
are activated (BEE, ES, SES and UAS). Data collection is performed only on 24 hours registers and the NE
maintains a buffer of two registers: the 24hours current registers and the historical one.
17.1.5 End to End (e-e 24h) Performance Counting
VCn trails can be monitored in intermediate node through the activation of performance monitoring
process on Monitoring function.
As the trails are often responsible of the end-to-end customer service, the end-to-end monitoring can be
requested provide monitoring for Quality of Service purposes and, in addition, for network Maintenance
applications.
If SNCP is configured the Quality of Service collection have to be enable in the monitoring functions after the
matrix.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
268/396
End to end monitoring is achieved by activation of Performance monitoring on the two direction of path and
using far-end primitives. This process can be unidirectional (for Monitoring) or bidirectional process (for QoS).
In case of unidirectional process one direction can be monitored end to end and both 15minute and 24h
collection can be activate 15min./24H FE_BBE_, FE-ES, FE-SES, FE-UAS on incoming or egress signal
depending of the POM is enable. The TCA are also evaluated in both 15-minute and 24H counters.
The bidirectional process need the presence on the two Monitoring functions in the two directions in one NE
and among the two monitoring function a 24 hour collection can be activated with the collection of
incFE_BBE, incFE-ES, incFE-SES, UAS, eFE-BBE, eFE-es, eFE-SES.
17.1.6 Performance Monitoring on AU-PJE
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization.
AU PJE (Administrative unit point justification event) is an optional parameters request in G.784.
For AU PJE counters, the positive and negative PJE shall be counted separately on one selectable AU
within an STM-N signal, after the AU has been resynchronized to the local clock. Refer to G.783
The number of positive and negative outgoing PJE per second are collected in 15 minutes and 24 H
counters. A history of 16 x 15minutes counters and 2 x 24H are stored in the NE for each AU selected.
No Threshold crossing mechanism is supported on AU-PJE counters.
17.1.7 Tandem Connection Termination (TCT) and Monitoring (TCM)
TCM allows monitoring within the operator domain. The quality within the operator's on domain can be
proven regardless of the received quality of the signal at the entry point of the network. At the input point the
reference value is set to zero by using the TCM feature.
Tandem Connection Monitoring is applicable to VC-4-nc (n=1,4,16...), VC-4, VC-3 and VC-12 layers.
TCM provides:
-
TC_API as access point identifier complying with generic 16-byte string format;
TC_RDI indicating to the far end that defects have been detected within the TC at the near end TC sink;
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
269/396
Event Counting
The performance events (e.g. SES) are counted in a counter per event. These counters are called the
current register. At the end of the monitoring period, the contents of the current registers are transferred to
the first of the recent registers, together with a time stamp to identify the period (including the day). Time
stamping is performed using UTC (as for all alarms). After that, the current register is reset. It is also possible
to reset an individual current register manually.
Suspect Flag
A suspect interval flag is set as an indication that the data of the corresponding register may be either
incomplete or invalid.
Zero Suppression
Zero suppression is a basic mechanism to remove irrelevant PM information and to reduce the amount of
PM reports in the system. A PM report is suppressed and hence no history record is created by the entity,
which is responsible for PM reporting when all of the following conditions are true for the monitoring period:
-
- PM was enable enabled during the entire monitoring interval (the elapsed time equals its nominal value,
i.e. 900 for 15 min. and 86400 for 24 h<9.
-
By default, zero suppression is active for all PM enabled TPs. The number of suppressed intervals is
indicated.
17.1.10 Data Collection
N.B. PM data is not counted on boards that were plugged out at the moment of enabling data collection (see
PM Configuration dialog). Nevertheless, PM data is counted on boards that were plugged in at the moment
of enabling data collection, but were plugged out and back in some time during data collection.
Performance Monitoring can be started at any time.
As soon as Performance Monitoring is started on the Craft Terminal, current PM data is collected on the I/O
boards, incrementing the performance counters each time an error is detected.
The performance data counted is evaluated every quarter of an hour or every 24 hours and stored there in a
history record.
When the user disables the monitoring of a TP within the first 10 minutes of a 15-minute period, it is possible
that have still not been received the PM data of the previous monitoring interval.
Since PM data is not stored after monitoring is disabled, the PM data of the previous interval is lost in this
case.
If equipment or line protection switching occurs during a counting interval, the NE does not provide complete
performance measurement for the protected TPs.
Only the period between the last switch and the end of the counting window is counted.
The interval is marked for suspect data and the elapsed time indicates the length of the measured period.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
270/396
In compliance with ETSI and ITU-T standards, the history registers operate as follows:
The history data is contained in a stack of registers. There are sixteen 15-minute period registers and one
24-hour period registers per monitored event. These registers are called the recent registers. At the end of
each monitoring period, the contents of the current registers are moved the first of the recent registers. When
all recent registers are full, the oldest information is discarded.
17.1.12 Thresholds
For quality supervision purposes, the recorded errors through the performance counters can be compared to
threshold levels. If a counter value has crossed a threshold level, a Threshold Crossing Alarm (TCA) is
transmitted to the alarm manager.
The threshold values are defined in threshold tables together with a severity and a flag indicating whether
crossing this value should be notified by an alarm and logged or only stored in the current problem list. The
user can modify and delete such tables.
Different thresholds can be assigned for near end and far end and for granularity of 15 minutes and 24 hours.
The TCA only reports the value of the counter, which has crossed the threshold; it does not provide a
complete set of all counters. Therefore, the user has to explicitly retrieve all current performance data after
receiving the alarm. The user can retrieve this information from the Current Performance Management Data
Dialog..
Two thresholds mechanism are supported:
- For 24-hour (implicit clearance) monitoring periods, one threshold value is defined: if the event count
reaches or exceeds the threshold value during the monitoring period, a TCA is generated. To clear a TCA,
the alarm must be manually acknowledged by the user.
- For 15-minute (explicit clearance) monitoring periods, two threshold values (set, reset) are defined: a TCA
is generated during the monitoring period when the event count reaches or exceeds the set threshold value
the first time. This TCA is automatically cleared by the system at the end of the following monitoring period in
which the event count is less than or equal to the reset threshold value and there was neither an unavailable
nor a suspect period during this monitoring period.
The following limitations apply for explicit clearance:
The value of the low threshold is fixed to "0" (only a single threshold is provided by a threshold table).
An SES threshold crossing is cleared at the end of the interval if no unavailability was detected and
SES had not reached the low threshold (low threshold equal to 0).
Even in case of a suspect interval the TCA is cleared if no unavailability was detected and the low
threshold had not been reached.
Additionally an explicit clearance of TCAs for all granularity periods is executed if one of the following events
occurs during the current interval:
ED
Resetting of counters,
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
271/396
Select the TP and open the PM Configuration dialog by clicking on the menu item Configure Monitoring.
Figure 229.
Configure Monitoring.
This "PM Configuration" dialog serves as the main interface to all PM services. Every configuration
of all monitoring intervals is defined using this dialog.
It is possible to access the same "PM Configuration" dialog selecting a TP in the "Port view" and opening the
same Performance > Configure Monitoring option in the Port pull down menu.
N.B. To configure PM for au4CTPs and tuxCTPs, Path Overhead Monitoring (POM) or Supervised
Unequipped Termination (SUT, not supported) or Tandem Connection (TCT, TCM) must be created first.
The PM Configuration dialog is designed as a notebook consisting of a text field, to identify the selected TP,
and page labels.
The selected TP is indicated in the first box at the top of the screen: TP Identifier.
In case of au4CTP and tuxCTPs and VcxCTP, the PM Configuration dialog also contains an option button
showing the configured POM and SUT options as follow.
-
When more than one of the above options is chosen, a Question dialog box is displayed; click on Cancel to
continue or OK to interrupt any action.
N.B. As long as the PM Configuration dialog is open, a modified POM/SUT/TC configuration is not
automatically recognized and displayed. This may lead to rejections or confirmations of forbidden PM
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
272/396
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:
24hBi, near and far end 24 hours page bidirectional (UAS is the sum of far end near end)
Each dataset has to be configured independently. For AU-4 CTP and TU-x CTP the highest criteria are POM
and SUT. I.e. select the POM or SUT option first and then configure the different associated data sets.
Confirm the configuration with Apply before you continue with a different POM or SUT option.
Figure 230.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
273/396
Figure 231.
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
274/396
Note that on disabling this mode item, no history data is available. Nevertheless, datasets collected
prior to deactivation are not cleared and are displayed after re-enabling the item, as long as the
number of displayed datasets does not exceed 16 for 15 min. granularity.
Lock Data Collection. Not supported
If Lock is selected, PM remains enabled but data collection is stopped. All history performance data
remain available. All current values are set to zero.
Notifications
Threshold Table
Attach a threshold table to the selected TP. Only assign threshold tables that match the granularity
period of the datasets (i.e. a 15 min. threshold table must not be assigned to a 24 h dataset).
Otherwise the Transmission view is blocked and only released by closing and reopening the PM
Configuration window and the Transmission view.
Click on button Attach... to open the PM Threshold Table Select dialog (see) and configure the
threshold table (see Chapter on page).
Select button Remove to disassociate the threshold table from the entity.
N.B. A threshold table can only be attached if Data Collection is enabled.
Confirm the configuration with the button Apply before closing the dialog. Otherwise the configuration is lost.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
275/396
[2] Outgoing (network centric view): it refers to the direction starting from SDH domain toward Ethernet
domain (see Figure 232.). The traffic arrives to the board from an SDH link and goes out from an
Ethernet link.
Figure 232.
17.3.1 Overview
Ethernet counters can be distinguished from different points of view as depicted in Figure 230.
They can be:
Physical interface counters
aggregate counters
flow counters
At physical interface level, the working status of transceiver is controlled.
At aggregate level, all Ethernet traffics passing through the same port can be viewed as an aggregate.
At flow level, each single flow is managed.
Besides this classification, some counters can be of Quality of Service, others only of maintenance.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
276/396
Figure 233.
Counter subdivision
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
277/396
TTO (Total Transmitted Octets): total number of octets of Ethernet frames transmitted out by the Virtual
Ethernet Interface , including Ethernet header characters.
TTF (Total Transmitted Frames): total number of Ethernet frames transmitted out by the Virtual Ethernet
Interface
TDF (Total Discarded Frames): total number of Ethernet frames which were chosen to be discarded due to
buffer congestion. TRSEF (Total Received Service Errored frames): it is the sum of three contributions.
Figure 234.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
278/396
TDF_G (Total Discarded Green Frames): total number of green Ethernet frames which were chosen to be
discarded due to buffer congestion.
TDF_Y (Total Discarded Yellow Frames): total number of yellow Ethernet frames which were chosen to be
discarded due to buffer congestion.
TTO_G (Total Transmitted Green Octets): total number of octets of green Ethernet frames transmitted out,
including Ethernet header characters.
TTF_G (Total Transmitted Green Frames): total number of green Ethernet frames transmitted out.
TTO_Y (Total Transmitted Yellow Octets): total number of octets of yellow Ethernet frames transmitted out,
including Ethernet header characters.
TTF_Y (Total Transmitted Yellow Frames): total number of yellow Ethernet frames transmitted out.
Figure 235.
This "Current PM Data" dialog serves to show the results and status of the Performance Monitoring
counters.
It is possible to access the same "Current PM Data" dialog selecting a TP in the "Port view" and opening the
same Performance > Display Current Data option in the Port pull down menu.
The Current PM Data dialog is designed as a notebook consisting of a text field, to identify the selected TP,
and page labels.
The selected TP is indicated in the first box at the top of the screen: TP Identifier.
In case of au4CTP and tux CTPs, the Current PM Data dialog also contains an option button showing the
configured POM and SUT options to display as follow:
-
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
279/396
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:
24hBi, far end 24 hours page bidirectional (UAS is the sum of far end and near end)
All datasets available, which are related to the selected TP and recorded in the current monitoring interval,
are displayed in this dialog.
The following items are indicated for each entity:
Administrative State
Indicates whether the PM collection is locked for the local user or not.
Operational State
Indicates whether PM is enabled or disabled.
Suspect Data
Indicates if collection errors occurred during the collection period.
Threshold Table
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
280/396
Figure 236.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
281/396
Figure 237.
This "PM History Data" dialog serves to show stored Performance Monitoring counting.
It is possible to access the same "PM History Data" dialog selecting a TP in the "Port view" and opening the
same Performance > Display History Data option in the Port pull down menu.
The PM History Data dialog is designed as a notebook consisting of a text field, to identify the selected TP,
and page labels.
The selected TP is indicated in the first box at the top of the screen: TP Identifier.
In case of au4CTP and tuxCTPs VCxCTPs, the PM History Data dialog also contains a cascading menu
that allows choosing the POM and SUT options to display follow:
-
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:
24hBi, far end 24 hours page bidirectional (UAS is the sum of far end and near end)
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
282/396
The number of recorded events concerning an entity is divided into near end and far end data
Elapsed Time
Indicating whether the data collection was complete.
Susp
Indicating suspect data where collection errors occurred during the collection period.
In case of 15 min. entities, a maximum of 16 datasets can be displayed simultaneously for each counter; the
24h entities display a maximum of one dataset. The user cannot change these figures.
If the limit of 16 datasets for 15 min. granularity and 3 datasets for 24 h granularity is reached, the oldest set
in the list is cleared when the next data set arrives.
Using the Print button, PM data can be saved to a file or printed on paper.
N.B. If no printer is installed, there is no error message displayed to indicate this.
Figure 238.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
283/396
The PM Threshold Table Select dialog pops up if the Attach button is clicked in the PM Configuration
dialog.
Figure 239.
PM Configuration dialog
Attach the selected threshold table to a TP entity. It is only available entering from the PM
Configuration dialog.
The user has to close the dialog explicitly by clicking on the button Close.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
284/396
Figure 240.
ED
03
PM Threshold Table Select
SC.3: NE MANAGEMENT
285/396
Layer
TPs ASSOCIATED
Granularity
STM4
RS
15 minutes
2
3
4
STM4
STM1
STM1
RS
RS
RS
24 hours
15 minutes
24 hours
5
6
7
8
STM4
STM4
STM1
STM1
MS NE / FE
MS NE / FE
MS NE / FE
MS NE / FE
15 minutes
24 hours
15 minutes
24 hours
9
10
11
12
13
14
VC4
VC4
VC3
VC3
VC12
VC12
Path Termination NE / FE
Path Termination NE / FE
Path Termination NE / FE
Path Termination NE / FE
Path Termination NE / FE
Path Termination NE / FE
15 minutes
24 hours
15 minutes
24 hours
15 minutes
24 hours
After the activation of a PM on a TP, it will be signaled in the Port view and in the Transmission view as for
the following figures:
Figure 241.
Figure 242.
PM Port View
PM Transmission View
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
286/396
Leading and succession blanks are ignored. Leaving the input field blank or entering only blanks is not
allowed and rejected.
2) Select a Granularity of 15 min. or 24 h for the entity.
3) Enter the set (Value Up) and the reset (Value Down) threshold values. Node that the reset value if
supported, will be available with 15 min. monitoring periods.
Table 1 shows the maximum performance monitoring event values.
The respective value is automatically reset to the maximum if a larger figure is entered.
4) Select the alarm Severity for each PM attribute in case a threshold is crossed.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization.
5) Disable Send notification if no notification message should be sent in the case of a crossed threshold.
6) Confirm the entries with Apply to create the threshold table. A number of threshold tables can be created
from the same window.
Explicitly close the window with button Close.
Figure 243.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
287/396
17.7.2 Modification
The PM Threshold Table Modify dialog (see) pops up if a threshold table is selected in the PM Threshold
Table Selection dialog (see) and the Modify button is clicked.
Carry out the following steps to modify a threshold table:
1) Modify the upper threshold value (Value Up) and the lower value (Value down)
Table 1. Shows the allowed maximum performance parameter values.
2) Modify the alarm Severity for each PM attribute in case a threshold is crossed.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization.
3) Disable Send notification if no notification message should be sent in the case of a crossed threshold.
Note that the Name (really "number") cannot be changed.
4) Confirm the modifications with Apply.
5) To modify more than one threshold table, do not close the dialog, but select the next threshold table in the
PM Threshold Table Selection dialog and press the Modify button (see).
Explicitly close the dialog with button Close.
17.7.3 Display
The PM Threshold Table Display dialog pops up if a threshold table is selected in the PM Threshold Table
Selection dialog and the Display button is clicked.
Refer to the previous chapter for a description of the attribute values and types.
Table 8. Maximum Performance Parameter Values
Performance Parameter
Max. Value for 15-min period Max. Value for 24-h period
8,639,100
829,353,600
2,159,100
207,273,600
539,100
51,753,600
900
86,400
SES, FESES
810
78,760
1,800,000
172,800,000
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
288/396
Figure 244.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
289/396
Figure 245.
PM Configuration dialog
Figure 246.
In that dialog the operator will be allowed to create/delete the current Data by checking/unchecking the
corresponding checkbox for the incoming and outgoing direction.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
290/396
Figure 247.
This Current PM Data allows the operator to send a request in order to retrieve the maintenance counters.
The layout of the dialog maintenance counters is depicted in Figure 248.
At startup the dialog displays an empty table; the dialog allows to choose the polling time and how many
times the action will be done; the default values for those entries are 0 for polling time and 1 for number of
retries, with that default configuration if the Start polling button allows to perform the configured request. If
the number of retries is bigger than 1, several actions are performed on the NE.
During the polling interval the label of the button Start polling will be changed to Stop polling, and for
every response arrived a row is added to the table. Every time the operators push the Start polling button
new lines will be added to the lines already present in the table.
Figure 248.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
291/396
Select the TP (Gmau) and open the PM History Data dialog (see Figure 249.) by clicking on the menu item
Display History Data.
Figure 249.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
292/396
Figure 250.
17.11 PM Overview
MSP Overview allows displaying performance overview.
Selecting the PM Overview option from the Configuration pull down menu figures below open.
Figure 251.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
293/396
Figure 252.
ED
03
PM Overview
SC.3: NE MANAGEMENT
294/396
Figure 253.
You can click Add TP button to see the PM data about the selected TP. Like the figure below.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
295/396
Figure 254.
ED
03
SC.3: NE MANAGEMENT
296/396
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:
The SETG is responsible for the generation of the external timing source for the Frame structure and the
clock, whilst the internal oscillator is useful only in the abnormal functioning "Free-running" mode that will be
explained later.
The simplified figure that follows represents the internal organization of the SETS.
Figure 255.
The number of timing reference inputs depends on the configuration of the NE.
The external sources (outputs) are:
ED
T0: is the reference output signal for the clock and signal frames,
SC.3: NE MANAGEMENT
3AL 98253 ADAA
297/396
T5: is the 2 Mbit/s reference output for the external equipment synchronization
Y: is used for communication of Synchronization Status Message (SSM) between SETS and MST
functional blocks.
S15: is used to provide notifications and loss of incoming timing reference reporting to the
Synchronous Equipment Management Function (SEMF).
Selector A provides the capability to select timing reference from available T1 inputs, either automatically
based on the priority and quality level of the candidate sources (SSM algorithm), or manual as a result of
commands issued from the managing system.
Selector B is capable of selecting timing reference from T1, T2, or T3 inputs, according to the SSM
algorithm. The capability for manual selection of the timing source is also provided.
Selector C is only operated in manual mode, to switch between SETG output signal (T0) and a T1 timing
reference.
The squelch functions A and B mute the relevant timing references in the presence of failure condition, or
SSM threshold violation.
The choice of the timing reference is done in two ways:
Automatically:
Following a particular algorithm based on the quality and the priority of the incoming timing signals.
The automatic selection is based either on the priority of the incoming timing source (Priority
algorithm) or on the priority and the quality level of the incoming sources (SSM algorithm).
Manually:
Following an order from the Operator.
N.B. The Operator for each candidate-timing source determines the priority level. It is static information.
On the other hand, the quality of the source is dynamic information, dependant of the quality of the
reference clock generating the timing.
In an SDH signal frame, the quality of the timing source is located in the Section Overhead.
The SETG has 3 modes of operation:
Locked mode:
The SETG output is fully controlled by the external timing references (T1, T2 and T3).
Hold-Over mode:
The external timing reference is malfunctioning. The SETG during normal functioning stores
regularly the value of the external timing reference. In this case the SETG output is controlled by this
memorized value.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
298/396
The operations that can be done on the synchronization sources are the following:
Protection Commands,
T0 Configuration,
T4 Configuration,
SSU Configuration,
Change T4<-> T5
Set T0 Equal T4
Change 2 MHz -> 2 Mbit (available only if T3 has been configured as timing source)
Figure 256.
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
299/396
After selecting the Synchronization option from the Views menu the Synchronization View is visualized.
Figure 257.
One for T4 timing output; the presence of the T4 list is configurable using resource files.
T0 list contains:
- A timing reference associated to the Internal Oscillator timing source; it is always present and it cannot be
removed or redefined.
- 6 max timing reference for candidate inputs belonging to the allowable timing reference T1, T2 or T3/T6
configurable by the operator.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
300/396
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 to visualize the alarm detail.
In the timing reference graphical object associated to the Internal Oscillator the following information are
displayed:
- The name of the timing source: Internal Oscillator
- A small box representing the LOS alarm; the small box will be lighted up when all the selected timing
source are lost, indicating the Holdover or Free Running operation mode;
- A label field representing the abnormal clock operation modes, one of the following strings can be
displayed in the label field:
- Holdover, displayed when the clock operates in Holdover mode;
- Free running, displayed when the clock operates in Free Running mode;
- Empty string is displayed when the clock operates in Lock;
- A label "0" representing the priority of the Internal Oscillator
Selectors
ED
Squelch Status
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
301/396
Boxes contained a label field are used to represent the squelch statuses T0/T4 and T4. The box displays the
configured quality level threshold and it is lighted up when the output-timing signal is inhibited.
Output Signal
Line Type
The following different line type are used to link the output signals and the respective allowable timing
reference:
- A solid line between an output signal and an allowable timing reference means that timing reference is
currently used to generate that signal;
- A dashed line between an output signal and an allowable timing reference means that timing reference is
not currently in use as timing source but will act in the protecting role.
In the same way, a solid line between T0 signal and T4/T5 signal (or T0_Test signal) box is drawn when T0
signal is used to generate T4/T5
18.2.3 Timing Source Configuration
This functionality allows configuring the input synchronization sources and configuring or modifying the
timing source priority and quality.
Figure 258.
Synchronization Menu
The menu options are grey according to the current state of the dialogue box that the user can open.
Firstly select a synchronization source reference and after the Synchronization menu to open the
Synchronization Option List. Then select the Timing Source Configuration option from the cascading menu,
as shown in the above figure.
The following dialogue box is opened.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
302/396
Figure 259.
The Timing source configuration dialogue box which opens, displays the extracted quality of the selected
timing source. It permits to configure the following timing source information:
Quality level,
Priority level
Extracted Quality is the actual Rx quality retrieved from the signal received from the line.
Select an empty synch. Source reference and click on Timing Source Configuration and then on the Input
Source Choice. Figure below shows an example of the opened windows.
Following the TP Search procedure (rack, subrack, board, port) enter the physical board termination point
(TP) value; these TP are: EIS for electrical SDH port, OpS for optical SDH port.
This operation can be repeated for the entire available empty synch. Sources both for T0 clock and for T4
clock.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
303/396
Figure 260.
Click on the Input Quality Configuration: the option button opens the option menu to select the desired
quality level.
Timing source may have, in increasing order, five quality levels: G.811, G.812T, G.812L, G.813, Q. Don't use
(where the highest quality level is G.811).
If Input Quality Configuration is set to a value other than "Extracted", Rx quality is forced to this value.
Click on the Priority: the option button opens the option menu to select the desired priority level.
The internal oscillator-timing source will have the lowest priority (priority=0) and its priority cannot be
changed. The other timing sources will have a priority of 1 to n.
Priority of 1 is the highest priority. Levels 6,...2 are intermediate levels between level 0 and 1, in increasing
order of priority (i.e. 0 6 5 4 3 2 1).
When the configuration of the timing source is completed, click on the OK push button to validate the choice
and close the dialogue box. The Cancel push button cancels the configuration and closes the dialogue box.
Positioning the mouse on the synch. Source box "Port#" test, the corresponding physical interface
denomination (rack-subrack-board-port) is written on the window bottom left.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
304/396
Select the timing reference from the synchronization view. Select the Synchronization pull down menu. You
can then select the Protection Commands to open the view. Menu options are grey. According to the
current state of the selected timing source.
Figure 261.
a) Invoke/Release Lockout: Locking or unlocking a timing source enables or disables the timing
source from being considered as a possible timing source for T0 or T4.
b) Invoke/Release Force and Manual Selection of Timing Source
General selection
A timing source can be selected manually or automatically. Furthermore, the selection of a particular
incoming timing source (except the internal oscillator) may be forced.
This selection is independent of the priority or quality of the timing source. If the timing source is lockout or
unavailable, this operation is impossible. A timing source is considered to be available if it is not lockout and
has not a failure condition or Priority level of 0.
Releasing terminates the forced switch mode or inhibiting the force selected timing source.
The manual selection option is only possible if the quality and priority of the selected timing source are
sufficient. Otherwise the automatic selection algorithm overrules the manual selection.
If the previously manual selected timing source becomes unavailable the automatic selection is activated.
The "Status" indication describes the current synch. status (No Request, Automatic Switch, Failure, ...)
N.B. The internal oscillator cannot be forced or manually selected.
From the dialogue box that opens, you can confirm or cancel the operation.
To perform or release a T0 or T4 lockout, forced or manual selection, the following operations have to be
done:
ED
Select the Protection Commands option then invoke/Release the Lockout, Forced or manual
Selection option.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
305/396
When T0 is selected to generate T4 (squelch B ): T0 may be squelched if all the allowable timing
references of Selector B have Quality Level lower than the programmable threshold.
When T1 is selected to generate T4 (squelch A ) :T1 may be squelched if T1 Quality Level is lower
than the programmable threshold or if it becomes unavailable.
The T0/T4 and T1/T4 squelch fields enables you to configure the quality level of the T0 or T4 timing source,
opening the relevant option menu.
When the configuration of T0/T4 Configuration is completed, click on the OK button to validate the choice
and close the dialogue box.
The T5 output field allows selecting the bit used (from #4 to #8) for SSM.
The Cancel push button cancels the configuration and closes the dialogue box.
The T4 squelch configuration dialogue box enables you to configure the quality level of the T4 timing
source.
Click on the T0: option button to open the option menu and select the desired quality level.
Click on the T4: option button to open the option menu and select the desired quality level.
The T4 Force Squelch enables you to activate the T4 forced squelch.
When the configuration of T0/T4 Configuration is completed, click on the OK push button to validate the
choice and close the dialogue box.
The Cancel push button cancels the configuration and closes the dialogue box.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
306/396
Figure 262.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
307/396
Figure 263.
SSU Configuration
Figure 264.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
308/396
To remove the selected source click on "OK" button of the confirmation message.
Figure 265.
Figure 266.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
309/396
Figure 267.
Figure 268.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
310/396
Figure 269.
Figure 270.
Click on ok to confirm
The label of the protection unit will be changed depending on the kind of source selected:
ED
If the selected protection unit is a 2 MHz, then the label will be changed into 2Mbit/s.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
311/396
If the selected protection unit is a 2 Mbit/s, then the label will be changed into 2MHz
Figure 271.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
312/396
To connect T0 internal synch. Select a synch. Source and click on Set T0 Equal T4 menu option. The
connection between T0/T4 will pass from a shaped to a continue line as in the example of Figure below.
Figure 272.
T4 equal T0 setting
To separate T4 from T0 click on the "Remove T0 Equal T4" menu option. The T0/T4 connection will become
shaped while the connection between T1/T4 will pass from a shaped to a continue line.
18.2.11 Transmission of SSM Quality Configuration
Select the T1 SDH Reference Source in the Synchronization View hence the Transmission SSM Quality
Configuration is enabled. This selection allows, with the Inserted option, to transmit the system internal T0
clock quality towards the external SDH interface. It is also possible to transmit different quality level selecting
a different value.
Click on Transmitted SSM Quality Configuration of the Synchronization menu option.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
313/396
Figure 273.
This Transmission SSM Quality window can be also opened from any SDH boards. Select the Equipment
option of the View menu, then access the Board view> Port view> Physical Media> SDH Tx Quality
Configuration; it is also possible to open the window selecting the Transmission option of the View menu,
then access the Physical Media> SDH Tx Quality Configuration option.
In both cases select the MST block
18.2.12 Show Timing Source
Selecting any T1 or T2 Reference Source in the Synchronization View hence the Show Timing Source is
enabled. This selection allows analyzing
the input source considering its payload structure and the related alarms (Port view is presented) .
Click on Show Timing Source of the Synchronization menu option.
Figure 274.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
314/396
19 MS-SPRING MANAGEMENT
19.1 MS-SPRING introduction
Different MS-SPRING protections architectures are provided: 2-Fiber (Terrestrial), and 4-Fiber NPE
(Transoceanic).
See ITU-T Rec. G.841.
SNCP, 4 Fiber MS-SPRING and Aggregate MSP protection connections cannot be installed in a 2
Fiber MS-SPRING network. This leads to an unprotected connections installation.
AU4s from #9 to #16 don't have to be used for connections nor considered in any parameter of
"Squelching table" provisioning. Only AU4s from #1 to 8# must be used and configured for path
installation.
AU4 permutation (change of AU4 allocation) is not allowed. The AU4 allocated to pass-through in
HVC connections must be the same through the node.
AU4 cross connection Aggregate side, i.e. paths received from the Aggregate line and looped-back
to the (same) Aggregate line are not allowed.
Follow the "Squelching Table Configuration" in order to define the "Squelching Table HO" for East
and for West aggregates describing, for each connection installed, as Source Node, the Node
Identifier of the node generating the considered AU4 and as Destination Node, the Node Identifier
of the node terminating the AU4.
Activation procedure
a. Create an MS-SPRING schema with WTR, Node Identifier, Ring map and the related Squelching
Table for each node of the ring, in the desired order. WTR Ring must be same in all the nodes.
b. In the Main dialog for MS-SPRing management select "ACTIVATE" in each node of the ring, in the
desired order. Consider that, in this step, "Default K byte West or East" detection by View Protection
Status Parameter (under MS-SPRing label -> " Protocol exception"), will occur on those Aggregate
of the activated nodes connected to the nodes just deactivated.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
315/396
c. Verify in the View Protection Status Parameter screen, at the end of the provisioning update, that all
the nodes of the ring are in "MS-SPRing activate" and "No request" state.
-
Deactivation procedure
a. In the Main dialog for MS-SPRing management select "DEACTIVATE" in each node of the ring.
Consider that, in this step, "Default K byte West or East" detection by View Protection Status
Parameter (under MS-SPRing label -> "Protocol exception"), will occur on those Aggregate of the
activated nodes connected to the nodes just deactivated.
b. In the Main dialog for MS-SPRIng management select "DELETE" in each node of the ring.
Removing a node
a. In the Manage ring Map view select the node and click on the "Remove Node" button
b. Modify the table in the Configure Squelch Table view according the new Ring Map.
c.
Opening the View Protection Status Parameter screen, send "Force Ring" command to both NE's
adjacent to the node to be removed.
Adding a node
a. In the Manage ring Map view insert the node in the selected position. Next nodes are automatically
shifted.
b. Modify the table in the Configure Squelch Table view according the new Ring Map.
c.
Opening the View Protection Status screen, send "Force Ring" command to both NE's adjacent to
the node to be added.
d. Physical add the node and configure with 2-Fiber MS-SPRING activated with the right configuration
(Ring Map, Squelching table, WTR, node Identifier).
e. Connect the fibers and send the "Release" command of the relevant "Force Ring" to both NE's
adjacent to the added node.
Figure 275.
The first Main Dialog for MS-SPRing management option contains all the commands to configure and
manage the MS-SPRing.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
316/396
In any dialog box is present the Cancel or Close buttons. When the user clicks on these buttons the dialog
box will close without starting any operation.
19.4.1
Select the MS-SPRing pull down menu. Then select the Main Dialog for MS-SPRing management option
from the pull down menu.
The following dialogue box is displayed when no protection have been previously configured
Figure 276.
The only command available is Create. The name of Schema Selection in not editable but is fixed to "No
Schema".
Click on Create to start the MS-SPRing configuration. Figure below opens
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
317/396
Figure 277.
The user can select the MS_SPRing Application and the Architecture types supported by the Network
Element.
Terrestrial MS-SPRing Application is a 2Fiber architecture.
Transoceanic MS-SPRing is a 4 Fiber architecture.(not supported in current relese)
The "Port Selection" depends on the Architecture type: if the architecture is a 2F MS-SPRing, the working
and protection port on each side is the same and the "Protecting West and East" fields are disabled (greyed).
If the architecture is a 4F MS-SPRing, the working and protection ports on each side are different.
The label r(xx)sr(y)sl(zz)port#(hh) where r=rack, sr=subrack, sl=slot give the position of the physical port. In
the same board it is generally possible to have different port numbers.
The OK button will start the selected operation. The cursor is displayed busy up to receiving a reply. Then
the dialog window will be closed. Figure below opens and all commands are now available.
The Holdoff Time command is not operative in current release.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
318/396
Figure 278.
Click on Ring Map to configure the network node connection. Figure below opens
Figure 279.
The Ring Map sets the connection sequence of the nodes within the ring. The matrix represents up to 64
nodes for transoceanic application and up to 16 nodes for terrestrial application.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
319/396
Select Current Nodeld (it means the NE where the operator is acting) in the box and enable
Nodeld button (Id means Node Identifier)
Change
Select Available Nodeld in the pull down list ( 0 to 63 for transoceanic application, 0 to 15 for terrestrial
application) releasing the left mouse button or pushing the stepper arrows and enter keys to select the
Nodeld value.
This will be displayed in the Available Nodeld box then click on Add Node button.
Clicking on the Add Node button the selected "Ring position" will shift one step on the righ starting from "1"
position and in the "Nodeld" field the Available Nodeld values is inserted. In the same time the Available
Nodeld will be updated to a new value.
The default association for a four node node ring related to the fourth node (Nodeld=3; Ring Position=4) is
depicted in Figure below.
Figure 280.
Repeat the procedure for all nodes of the ring selecting the different NEs and edit the different Current
Nodeld value.
To remove a node, select the node and click on Remove Node button. The following Ring Position of the
nodes on the right decreases by one and the erased Nodeld is inserted into Available Nodeld, so it can be
assigned to other nodes.
The OK button will start the selected operation, displaying the busy cursor up to receiving the replay to the
actions. Then the dialog window will be closed.
Click on the WTR Time button. Figure below opens
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
320/396
Figure 281.
Click on the push mouse button on the p/down Seconds arrows to select the required delay for the relevant
WTR. The step value is 60 sec. The range value accepted is from 60 sec. to 900 sec. Click on OK to apply
the WTR Configuration.
WTR Time Span is used only for 4-fiber architecture; it is disable (grey) for 2 fiber architecture.
The same WTR Time Ring must be set on each Node of the ring.
19.4.2 Squelching table with 2 fiber Terrestrial applications
With a 2 fiber Terrestrial application can be selected the Squelching Table while with a 4 fiber
Transoceanic application can be selected the Ring Traffic
If the operator tries to select a different table a error message is visualized. Figure below shows the error
message visualized when is selected the Ring Traffic with a Terrestrial application.
Figure 282.
Click on Squelching Table to configure the AU4 (Au4#1 to AU4#8 for 2F Architecture) connection between
the different nodes. Figure below opens. The same opens clicking on Configure Squelch Table of the MSSPRing pull down menu.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
321/396
Figure 283.
Squelching table
When the window is opened for the first time the squelching table is N/A (not available) because the NE has
never been configured. Point the mouse on the matrix position and click on the right mouse button to open
the node list menu. Select the node identification number ( 0 to 15 ) from the available list using the slider or
the stepper arrows on the right scroll region.
19.4.2.1 Squelching table example
Figure 284.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
322/396
Figure 285.
Figure 286.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
323/396
ED
03
Figure 287.
Squelching table of Node A, East side
Figure 288.
SC.3: NE MANAGEMENT
324/396
ED
03
Figure 289.
Squelching table of Node B, East side
Figure 290.
SC.3: NE MANAGEMENT
325/396
ED
03
Figure 291.
Squelching table of Node C, East side
Figure 292.
SC.3: NE MANAGEMENT
326/396
Figure 293.
19.4.3
The Main Activates commands manage the MS-SPRing configuration. The MS-SPRing status can be Enable,
Active, Disable and Inactive.
After having configured the protection schema by means of the Create button, the status becomes Enable.
The Activate button selection set "in service" the MS-SPRing protection mechanism on the selected schema
configuration.
To change from Active to Enable click on the Deactivate button. This command starts the request to
deactivate the MS-SPRing protection mechanism
When the selected protection schema is Enable the Delete button starts the request to remove it. The delete
action is started after confirming the window message.
Figure 294.
Confirmation message
During the activation procedure on different ADMs some of these can be Activate status, others in Inactivate
status. The statuses, the protocol request and the protocol protection errors are described in next chapters
describing the "MS-SPRing Protection Status and Commands".
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
327/396
19.5 MS-SPRING Protection Status and Commands for 2 fiber terrestrial application
19.5.1 2F MS-SPRing protection commands
If a protection schema is Active it is possible to select one of the above commands.
Clicking on the Prot. Commands button in the MS-SPRing -> Main Dialog for MS-SPRing management
Figure below is opened.
Figure 295.
The working/protection span state boxes are not available (grey) for the 2Fibwer MS-SPRing architecture.
In the MSPRing 2 Fiber configuration, the 1-8 working channels are inserted into the 9-16 protection
channels in the opposite side of the failure event as shown in figure below.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
328/396
Figure 296.
Figure 297.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
329/396
Figure 298.
Protection and working channels where the lockout command can be activated (2F)
The protection events can be equipment/signal failure, signal degrade or external command or a
combination of them.
The "Events" will be served if some actions (B/S=bridges and switches) are executed and the network has
been updated.
The "Events" will be signaled if the K1/K2 protocol communicates to the network nodes what has happened,
without execute actions.
A single ring failure is completely restored but not two ring failures. When are present multiple ring failures
the automatic B/S protection will try to maintain on all the possible connections.
The K1/K2 communication protocol MS-SPRing is generated from the two nodes adjacent to "Event" via the
protection communication channels. A node is defined tail-end when it firstly receives the "Event", the
second node is defined head-end when it receives back the protocol answer. Figure below shows the
association of tail end / tail end or head-end / tail end.
Some network protection mechanisms are accepted or rejected depending on the type (tail/head) (lockout
command.)
Figure 299.
If the node is tail end, the lockout working ring/span commands disable the protection MS-SPRing
mechanisms, while if the node is head-end, it serves the request node protection. (Protection not disable).
With the lockout protection span command and a ring failure, the ring protection is served if this ring failure
occurred the same section; the ring protection is disable if this ring failure has occurred in another ring
section. On the contrary, with the lockout working ring command failure and a ring failure along a different
section, the ring protection is served (protection non disable)
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
330/396
Figure 300.
ED
03
Tail-end / head-end protection with a lockout working and a one direction failure (2F)
SC.3: NE MANAGEMENT
331/396
Figure 301.
Figure below shows a ring with three nodes and the actions performed by the lockout commands. This
command disables the acknowledgment of the signal failure/degrade on the aggregate ports.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
332/396
Figure 302.
The Force command executes a forced protection. The Force Ring command substitutes the working
channels (AU4 1 to 8) with the opposite direction protection channels (AU4 9 to 16) between two adjacent
nodes.
The Force Span command is not operative in " fiber MS-SPring.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
333/396
Figure 303.
Figure 304.
The Manual command is similar to Force command but it is at a lower priority level with respect to automatic
MS-SPRing. The general priority scale that can be applied to solve antithetical situations starting from the
lowest priority level is: manual ring - automatic working ring force ring - lockout working ring - lockout
protection span.
When a force ring command is applied a next working failure is not able to modify the forced configuration
applied. That is because force ring command has a higher priority respect to the "Automatic" working
protection. In this condition the ring can be split according the location of command and event. Vice versa
the "Manual" protection is exceeded by the "Automatic" protection. Figure below visualizes the ring
protection with a Force/Manual command and a signal failure. FS-R is for "Force Switching Request", SF-R
is for "Signal Failure Request".
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
334/396
Figure 305.
ED
03
SC.3: NE MANAGEMENT
335/396
Figure 306.
Each command starts when the proper button is selected. A dialog box has to be confirmed before the
command is performed.
From each command exists its own Release button to cancel the previously selected command and come
back to normal MS-SPRing protection.
Figure 307.
Clicking on the WTR command next figure opens. If the WTR box, in the Local Condition field of Figure
(Protection states and commands "Idle" status (2F)), becomes red a waiting time has been activated after
repairing the ring failure. The waiting time, set in the configuration menu, can be cleared selecting the Clear
WTR Ring command. A confirmation dialog box opens and, if the operator clicks OK, the WTR box turns off
and the protection status window is updated.
Figure 308.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
336/396
Dual "Events" can appear on the same side W/W (West/West) or E/E (East/East)(SS= same side) or on the
opposite side W/E or E/W (OS= opposite site) of the ring network. In the SS or OS the "Events" can appear
on the same node (SN) or on the different nodes (DN), the different node can be an adjacent node (AN) or a
remote node (RN). Figure below depicts a clockwise ring network. The network propagation K1-K2 protocol
signals are according to the following legend:
C
Cs
Rs
Bs
When a command (Manual switch, Force switch) is neither served nor signaled that is erased
(it is not pending at the node)
Figure 309.
Figure up visualizes the ring reference scheme: the adjacent node (AN) is the node connected to the
reference point.
The automatic protection for dual ring failure is below. Consider the network reference scheme with a tail end
/ head-end alarm propagation. In this figure are depicted the node switches for any reported double events.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
337/396
Figure 310.
ED
03
SC.3: NE MANAGEMENT
338/396
Figure 311.
Schemas are applied to describe dual generic "Events" where both ring failures and external commands are
considered.
The first row at the top of the protection table shows the "Events" at the reference pint. For each of them the
associated "Events" is listed on the first column at the left of the table.
Two manual ring commands can be only signaled: Bs (Manual SS-SN and OS-AN commands give the same
ring protection switching and then both can be served).
Two Lockout commands are both always served: B
Force command has priority with respect to the Manual one.
Automatic protection has priority with respect to the Manual command.
Force Ring and Automatic Protection (or two Force ring commands) are always served if they are not applied
on the SS-SN. In this last case has to be considered the priority level. The behavior is that seen for two
automatic protection switching.
Lockout working SS.SN has priority with respect to Manual or Automatic protection and Force commands. In
the other cases. both commands are served (B).
Lockout protection SS.SN/OS-AN and Manual or Automatic or Force command are both served because the
switching SS.SN/OS.AN channels are not managed by the lockout protection: B.
Lockout protection SS-AN/OS-SN overrides the Manual or Automatic or Force command because the
lockout protection controls the switching channels of the same Node.
Lockout protection SS-RN/OS-RN and manual or automatic or force command. The lockout protection
prevents the working 1-8 channels from being inserted into protecting 9-16 ones. The lockout protection is
served, because it has a higher priority, the ring protection will be only signaled (pending).
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
339/396
Figure 312.
1 - Lockout Switching
2 - Forced Switching
4 - Manual Switching
These protection states are represented with the following color state boxes:
-
Red: Inactive State and any external or protection executed command (that has been served).
Yellow: ordered but not executed command (that has only been signaled = pending status)
Automatic switching and external commands are revertive: then when the "Events" have been cleared, the
MS-SPRing configuration comes back to its status.
The state boxes visualize the "Node Condition Request" as a consequence of the equipment/signal failure or
the external commands detected on the corresponding side ("Event"). The state boxes don't describe the
protection actions provided on the NEs.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
340/396
The served "Events" (B/S=bridges and switches are executed and the network has been updated) are
completed B/S actions visualized as red box indications.
The signaled "Events" (the k1/k2 protocol communicates to the network nodes what has happened) are
pending B/S visualized as yellow box indications.
Figure below shows the protection status with a served East manual ring command. Any protection status
window is divided in different status fields: Schema description and status, Local Conditions, Node
Conditions and Protocol Exceptions. The first one describes the network configuration and application type
and its status, the second gives the local external commands indications, the third the "Events" result on the
nodes and the fourth one checks the k1/k2 ring protocol. The window is divided into three parts: West,
Middle and East. On the West there are all the box indications corresponding to the West protections and
commands. In the middle "WTR-Ring" refers to West and East sides, "No Request" corresponding to "Idle
Status", and "Intermediate Node" denotes that the protections and commands don't concern the node
involved. The Manual Ring command visualizes "Manual Ring" on the local node and "Request Node Ring"
in the both "Local Conditions adjacent East ADM1-West ADM2 nodes, while the 3 and 4 nodes are
"Intermediate Node". The red color means that the command has been served. A regular protocol
"Exceptions" is represented with white boxes; a protocol alarm is signaled with red boxes. The "Prot.
Unavailable" indications are activated when a lockout protection command is applied in a network node.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
341/396
Figure 313.
ED
03
SC.3: NE MANAGEMENT
342/396
Figure below reports the "Protection Status" for external "Force and Manual" commands in a 3 -node ring (A,
B, C). Figure below shows the lockout statuses and Figure below the automatic protection statuses.
Figure 314.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
343/396
Figure 315.
ED
03
Visualization of the Lockout command Statuses (2F)
SC.3: NE MANAGEMENT
344/396
Figure 316.
The WTR status is visualized on the side where the link has been repaired. The considered network failures
are related to a tail-end/head-end node connection. The "WTR Clear" command can be executed by the user
without waiting the WTR setting time.
19.5.4.1 Double ring failure
The double ring failure visualization Figures (Example of Double ring failure) are here following reported.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
345/396
Figure 317.
Figure up reports the protection status with double ring failure (reference point-SS-AN). The node 2 isolated,
the nodes 2-3 in switching and the node 4 intermediate. The box color is white unless otherwise specified:
"Active: green
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
346/396
Figure 318.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
347/396
Figure up reports the protection status with double ring failure (reference point-SS-RN). The nodes 1,2,3,4
are being switched for signal failure alarm and both the two signal failures are served. The box color is white
unless otherwise specified:
"Active: green
"Request Node Ring" East ADM3-Eas ADM1: red (switching for SF)
"Request Node Ring" East ADM4-East ADM2: red (switching of the opposite nodes)
Figure 319.
ED
03
348/396
Figure up reports the protection status with double ring failure (reference point-OS-AN). The nodes 1,2 are
being switched for signal failure alarm and both signal failures are served: B. The box color is white unless
otherwise specified:
"Active: green
"Request Node Ring" West ADM2-East ADM1: red (switching for SF)
Figure 320.
ED
03
Protection status with double ring failure (reference point-OS-AN) recovering to "idle"
SC.3: NE MANAGEMENT
3AL 98253 ADAA
349/396
Figure up reports the previous protection status with double ring failure (reference point-OS-AN) while the
ring protection comes back to its "idle" status. The "WTR (Wait To Restore) Ring" on ADM1 node becomes
red to signal that the SF disappears at the "reference point". The box color is white unless otherwise
specified:
"Active: green
"WTR Ring: red (to signal the SF recovering)
"Request Node Ring" West ADM2-East ADM1: red
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
350/396
Figure 321.
Figure up report the protection status with double manual command (reference point-SS-AN). Both the
commands can be only pending. The "Request ring" to 1,2,3 nodes becomes pending while the 4 node is
"Intermediate node". The box color is white unless otherwise specified.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
351/396
"Active": green
"Request Node Ring" East ADM1-West ADM2: yellow (pending) for Manual Ring East ADM1
"Request Node Ring" East ADM2-West ADM3: yellow (pending) for Manual Ring East ADM2
"Request Node Ring" West ADM1-East ADM3: yellow (pending) for switching of the opposite nodes
Figure 322.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
352/396
Figure up reports the protection status with double manual command (reference point-OS-AN). Both the
commands can be served. The "Request Manual ring" to ADM1 (East) and to ADM2 opposite side (West)
collapses in the same manual command. Both the manual commands are served. The box color is white
unless otherwise specified:
"Active: green
"Request Node Ring" East ADM1-West ADM2: red (served)
Figure 323.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
353/396
Figure up reports the protection status with a manual command and a lockout protection (reference pointSS-SN). Both the manual and the lockout commands are visualized to the same ADM1 node (East). Both the
commands are served because the bridge/switch points are different. The box color is white unless
otherwise specified:
"Active: green
"Request Node Ring" East ADM1 - West ADM2: red (served)
"Intermediate Node" ADM3, ADM4: red
"Manual Ring and Lockout Prot." commands East ADM1: red
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
354/396
Figure 324.
Figure up reports the protection status with a manual command and a lockout protection (reference pointSS-RN). The manual command is pending while the lockout command is served. The box color is white
unless otherwise specified:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
355/396
"Active: green
"Manual Ring" commands East ADM1: yellow
Request Node Ring" East ADM1 - West ADM2: yellow (pending)
"Request Node Ring" West ADM1 - East ADM2: yellow (pending) for switching of the opposite nodes
"Lockout Prot." command: East ADM3: red
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
356/396
Figure 325.
Figure up reports the protection status with a ring failure and a manual ring command (reference point-OSAN). The automatic protection has a higher priority with respect to the manual command and then it has
been served. The box color is white unless otherwise specified:
"Active: green
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
357/396
Figure 326.
Figure up reports the protection status with a ring failure and a force ring command (reference point-SS-AN)
The ADM2 is isolated and the force command is pending. The box color is white unless otherwise specified:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
358/396
"Active: green
"Request Node Ring" East ADM1: red (served) the West ADM1 switching is applied for SF
"Request Node Ring" West ADM3: red (served) the East ADM3 switching is applied for the force command
"Request Node Ring" West ADM2, East ADM2: yellow (pending) the ADM2 is isolated
Figure 327.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
359/396
Figure up reports the protection status with a ring failure and a lockout working command (reference pointSS-SN). The lockout command has a higher with respect to the automatic protection switching and then only
the lockout command has been served. The box color is white unless otherwise specified:
"Active: green
"Lockout Ring" commands East ADM1: red
"Request Node Ring" East ADM1 - West ADM2: red (served)
Figure 328.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
360/396
The lockout protection has a higher priority with respect to the automatic ring protection. The box color is
white unless otherwise specified:
"Active": green
"Lockout Prot." commands West ADM3: red
"Prot. Unavailable" West ADM3 - East ADM2: red (lockout protections served)
"Request Node Ring" East ADM1 - West ADM2: yellow (automatic protection is pending)
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
361/396
20 ISA/IP/ETH CONFIGURATION
20.1 Introduction
This Chapter describes the operations necessary for the ATM/PR_EA/Ethernet boards creation in the
Equipment view and the ATM/PR_EA/Ethernet TTPs creation; as a matter of fact ATM/PR_EA/Ethernet
boards does not crate TTPs when they are configured.
The ATM/Ethernet/PR_EA board creation is performed when CT users sets an ATM/PR_EA/Ethernet board
and then configure the IP Address.
For the TTPs creation refer to paragraph 20.2 where all the operation are explained.
For the ATM/PR_EA/Ethernet traffic configuration (for example creation of Hard/Soft cross connection, PNNI
configuration etc.) refers to the relevant OPERATORS HANDBOOK (ATM or PR_EA) where Specific
Terminal application is explained in details.
The operational sequence to follow to manage ATM/PR_EA/Ethernet crossconnection is:
a) ATM/PR_EA/Ethernet board declaration (Equipment Set)
b) ATM/PR_EA/Ethernet IP Address Configuration (Called ISA board IP Address)
c) ATM/PR_EA/Ethernet board TTPs creation (VC4XV, VC12XV, VC3XV, VC44c TTP, VC4 TTP, VC3 TTP,
VC12 TTP, s31 TTP, E1 TTP)
d) TTPs crossconnection.
e) ATM/PR_EA/Ethernet traffic configuration with Specific Terminal application
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
362/396
Figure 329.
ED
03
ATM 4X4 MATRIX (initial empty fields)
SC.3: NE MANAGEMENT
363/396
Figure 330.
The ATM/IP/Ethernet ports Configuration window is filled with notebook pages (initially blank), each page is
an ATM, Ethernet or PR_EA board with relevant ports;
The user can create a new port, delete an existing one and change port associations (that means
modify the STM1 number and STM1 Time Slot on ATM/IP/Ethernet ports already created) via the three
buttons contained in the notebook page.
When the users want to create a new ATM port he can select an empty row, then in the Selected Item
sections, he can fill the field Signal choosing among the available options and push the Create button.
The STM1 Number and the STM1 Time Slot are automatically assigned.
If the users want to change the port attribute association he can select a filled row, then in the Selected
Item section he can change the fields STM1 number and STM1 Time Slot and than push the Time Slot
Sw. button.
To delete a port the user can select a row and push Delete button.
To close the dialog box click on the Close push button.
It is possible to see the ATM Ports created as above explained by selecting the relevant row in the
ATM/IP/Ethernet configuration window and then click on the Navigate button.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
364/396
Figure 331.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
365/396
Figure 332.
ED
03
PR_EA MATRIX (initial empty fields)
SC.3: NE MANAGEMENT
366/396
Figure 333.
The ATM/IP/Ethernet ports Configuration window is filled with notebook pages (initially blank), each page is
an ATM, Ethernet or PR_EA board with relevant ports;
The user can create a new port, delete an existing one and change port associations (that means
modify the STM1 number and STM1 Time Slot on ATM/IP/Ethernet ports already created) via the three
buttons contained in the notebook page.
When the users want to create a new PR_EA port he can select an empty row, then in the Selected Item
sections, he can fill the field Signal choosing among the available options and push the Create button.
The STM1 Number and the STM1 Time Slot are automatically assigned.
If the users want to change the port attribute association he can select a filled row, then in the Selected
Item section he can change the fields STM1 number and STM1 Time Slot and than push the Time Slot
Sw. button.
To delete a port the user can select a row and push Delete button.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
367/396
Figure 334.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
368/396
Figure 335.
ED
03
ETHMB (initial empty fieds)
SC.3: NE MANAGEMENT
369/396
Figure 336.
The ATM/IP/Ethernet ports Configuration window is filled with notebook pages (initially blank), each page is
an ATM, Ethernet or PR_EA board with relevant ports;
The user can create a new port, delete an existing one and change port associations (that means
modify the STM1 number and STM1 Time Slot on ATM/IP/Ethernet ports already created) via the three
buttons contained in the notebook page.
When the user want to create a new TPs he can select an empty row, then in the Selected Item sections,
he can fill the field Signal choosing among the available options and push the Create button.
Note: in case of concatenated VC TP creation (example VC12XV or VC3XV), before to push on Create
button it is also necessary to choose the Concatenation Level value; after creation command new fields and
a new button appear.
The STM1 Number and the STM1 Time Slot are automatically assigned.
If the user want to change the port attribute association he can select a filled row, then in the Selected Item
section he can change the fields STM1 number and STM1 Time Slot and than push the Time Slot Sw.
button.
The Ctrl Path Act. button allows to change the state of the concatenated virtual VCs (example VC12XV or
VC3XV) that could be Idle or active.; Click on Ctrl Path Act. button a new window will be opened.
To delete a port the user can select a row and push Delete button.
To close the dialog box click on the Close push button.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
370/396
Figure 337.
It is possible to see the VCs created on the ETHERNET board as above explained by selecting the relevant
row in the ATM/IP/Ethernet configuration window and then click on the Navigate button.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
371/396
Figure 338.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
372/396
For more details read the Gigabit Ethernet description reported in the Technical Handbook.
[3] GIGABIT board (GETHMB) + GBIT Access (GETHAG).
With this architecture can be configured up to 4 TPs (VC4XV Type) on the GETHAG access card and up to
4 TPs (VC4XV TTP Type) on the GETHMB main board taking into account that the maximum throughput
for the couple must not exceed 1.2 Gbit/s.; the concatenation level per port can be from 1 to 7.
The Gigabit Ethernet TPs creation follows the same rules described for the 10/100Mbit/s Ethernet Board.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
373/396
Figure 339.
ED
03
ES1-8FE MATRIX (initial empty fields)
SC.3: NE MANAGEMENT
374/396
Figure 340.
ED
03
ES1-8FE MATRIX (with defined TPs)
SC.3: NE MANAGEMENT
375/396
Figure 341.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
376/396
Figure 342.
ED
03
ES4-8FE MATRIX (initial empty fields)
SC.3: NE MANAGEMENT
377/396
Figure 343.
ED
03
ES4-8FE MATRIX (with defined TPs)
SC.3: NE MANAGEMENT
378/396
Figure 344.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
379/396
ED
03
Figure 345.
ISA-ES16 MATRIX (initial empty fields)
Figure 346.
SC.3: NE MANAGEMENT
380/396
Figure 347.
ED
03
Navigate to ETH port view (example)
SC.3: NE MANAGEMENT
381/396
21 Software Management
21.1 Generalities and descriptions
The Craft Terminal provides a set of functions, which allow software packages manipulation within NEs. The
downloading operation consists in the establishment of session between the NE and a software server for
the purpose of file transfer.
Actions can then be performed on the NE software version as update and activation operation, or roll back
to the previous software version operation. In this way the NE can follow the product evolution with "in
service" equipment.
The same function is used during maintenance phase, to update spare boards for substitution after
troubleshooting.
The operations that can be undertaken in this section are:
Manage Software Packages within NEs, activating the downloaded Software Package or coming
back to the previous condition.
A backup/restore can be also done on the MIB of the NE. Indeed the MIB can be saved to or restored from
the mass storage of the Craft Terminal.
The software download general principle is represented in the following figure.
Figure 348.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
382/396
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:
- 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...).
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.
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
383/396
b) Open a session on Craft Terminal application (start-up of the application, start supervision and NE login)
c) Check the present status of the software on a selected NE.
Download should not be performed in presence of unstable alarms
d) Open the Download menu.
e) Select the new software package in the server and triggers the download process, A message will indicate
the completed download.
f) Activate the package as presented at para.20.5 on page 333.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
384/396
Figure 349.
Figure 350.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
385/396
Figure 351.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
386/396
Figure 352.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
387/396
Figure 353.
ED
03
OMSN enhanced software package creation (part A)
SC.3: NE MANAGEMENT
388/396
Figure 354.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
389/396
Figure 355.
It is now possible to download the enhanced software package (SDH + ATM) from the EML-USM
(Refer to paragraph 20.4 for details).
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
390/396
All the software download operations are carried out from the software download manager.
Figure 356.
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 357.
ED
03
Download menu
SC.3: NE MANAGEMENT
3AL 98253 ADAA
391/396
Figure 358.
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:
Click on Forced push button to set the forced download attribute: then all software units of the Descriptor file
have to be downloaded. Otherwise only the units with different software version will be loaded.
If you want stop the download, click on the Cancel push button of the Software download initiate dialogue
box to close it.
Click on the OK push button to start the download. From the confirmation dialogue box that opens, you can
confirm or cancel the download. If you confirm the operation, the SW Downloading dialogue box then
disappears and the Software download in Progress dialogue box is displayed from which you can if
necessary abort the software download.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
392/396
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 359.
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.
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
393/396
Figure 360.
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:
Service Specific Components: name, release, version, edition of the Service Specific Components
(example ATM, IP etc.)
Current state\Action: commit or stand-by and with the option button; none/Force/Activate/Delete
Current state = standby means the package is not active on the NE
Current state = commit means the package is active on the NE
Action = (none) means no action to do
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
394/396
Figure 361.
Clicking on [-] symbol behind each software package all details disappear.
When you click on Close the previous view is displayed
In when you click on the:
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
395/396
Figure 362.
NE MIB management
Available backups on local server: gives the list of the backups available on the Craft Terminal,
Three push buttons allow choosing the action with click on:
Backup: performs the backup on the CT of the Mib present on the NE,
Restore: this function allows the managing system to restore the NE configuration database of the
managed system. Only one restore operation can be performed at the same time on a given NE.
Delete: this action allows deleting a backup of the NE database. The NE is not involved in this action.
The only effect is to delete the selected backup version stored in a specific directory of the FT server.
To activate an already restored MIB you click on Activate push button. Only at this point it becomes
operative on the NE.
To exit of the NE MIB management window, you click on Close push button.
To save or load the Mib to/from an external disk follow the indication of the "Basic 1320CT Operator's
Handbook" using the menu options of the Network Element Synthesis.
END OF DOCUMENT
ED
03
SC.3: NE MANAGEMENT
3AL 98253 ADAA
396/396
03
09/01/2006
Creation
ED
DATE
CHANGE NOTE
Distribution: Internal
Chen Yu
APPROVED BY
PREPARED BY
External
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
1/51
INTRODUCTION .......................................................................................................................................6
1.1
1.1.1
Document scope...........................................................................................................................6
1.1.2
Target audience............................................................................................................................6
1.2
Scope6
Terminology6
1.2.1
1.2.2
Glossary of terms..........................................................................................................................6
MAINTENANCE INTRODUCTION............................................................................................................7
2.1
Introduction 7
Introduction 8
5.2
Troubleshooting organization 10
5.3
On site Troubleshooting12
5.4
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
5.4.6
5.4.7
5.4.8
5.4.9
5.4.10
6
6.2
6.3
7
ED
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
2/51
7.2
P4S1, S-41, L-41, L-42 substitution with P4S1N, S-41N, L-41N, L-42N 51
7.1
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
3/51
FIGURES
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Figure 5.
Figure 6.
Alarm Surveillance......................................................................................................................21
Figure 7.
Figure 8.
Figure 9.
Figure 10.
Figure 11.
Figure 12.
Figure 13.
Figure 14.
Figure 15.
Figure 16.
Figure 17.
Figure 18.
Figure 19.
Figure 20.
Figure 21.
Figure 22.
Figure 23.
Figure 24.
TABLES
Table 1.
Table 2.
Table 3.
Table 4.
Table 5.
Table 6.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
4/51
Table 8.
ED
03
Table 7.
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
5/51
INTRODUCTION
1.1
1.1.1
Scope
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
1.2.1
Terminology
Acronyms and abbreviations
Glossary of terms
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
6/51
MAINTENANCE INTRODUCTION
2.1
Introduction
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
7/51
3
3.1
MAINTENANCE OF THE PC
Introduction
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
8/51
4
4.1
This procedure describes the Shutdown and restarts the PC should the Craft Terminal Software Product not
be working properly or not responding to the operator's commands.
In order to shut down the PC execute the command: start>shut down
A window (Windows NT Security user dialog) is displayed. It permits to shut down the computer or restart it.
The same window is displayed pressing he keys <Ctrl> + <Alt> + <Del> simultaneously.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
9/51
5.1
Troubleshooting involves the detection, location and correction of failures in the equipment and the
replacement of the defective parts.
5.2
Troubleshooting organization
The troubleshooting procedure is carried out with the help of some flow-charts and tables, reported
hereinafter. Anyway this method does not deal with the following aspects (which are to be deduced in other
ways):
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:
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.
When a second CONGI unit is used the following remote alarms are added:
ED
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.
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
10/51
TUP: remote alarm due to microprocessor fault in the COMPACT ADM unit
LOSQ2: remote alarm due to loss of communication with Mediation Device. Not operative.
Depending on the supervisory center organization, it is possible to locate the equipment in troubles and to
detect the failure type and source.
On site: the operator is on site in case:
1) The equipment is not managed by a TMN or by a Remote Craft terminal (RCT)
2) The equipment is not reachable by the remote manager (TMN or RCT) and is therefore isolated
When red, internal failure (indicates that the unit concerned must be replaced)
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
The analysis of these LEDs permits to detect the alarm type (Urgent - Not Urgent - Indication) and relevant
condition (Abnormal condition, Attended).
In case of urgent or not urgent alarm, after having located the alarmed equipment, the alarm condition can
be "attended" by pressing the relevant alarm storing push button on the COMPACT ADM unit.
This condition causes:
On the rack
The YELLOW LED to light up
The RED LED to go off
On the front cover plate:
Yellow LED (ATTENDED) to light up
Red LEDs NOT URGENT (MINOR) and URGENT (MAJOR and CRITICAL) to turn off (free
to accept other alarms)
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
11/51
If both LEDs are on, the Attend command should be given twice: one for attending the NOT URGENT
(MINOR) alarm and one for attending the URGENT (MAJOR) alarm.
5.3
On site Troubleshooting
The trouble-shooting operation proceeds according to the information indicated in the flow-charts:
As indicated in the flow-charts the troubleshooting operation is done by means of the Craft Terminal, and of
the optical indicators (LEDs) present on the NE.
The Craft Terminal is cord-connected to the relative connector on the COMPACT ADM unit front cover plate
(F interface).
The Craft Terminal applications provide detailed information on the alarm state thus facilitating fault location
and subsequent removal.
To correctly execute the troubleshooting operations the technician must know the exact equipment
configuration (see Equipment Configuration applications on the Craft Terminal).
The aim of the flow-charts which follow and of the maintenance tables is to locate the faulty unit and to
replace it with a spare as well as to locate a failure along the link.
The flow-charts/tables should be also consulted when the unit LEDs flash, because the flashing condition
might be due to external alarm causes usually related to line problems.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
12/51
Figure 1.
ED
03
SC.4 : NE MAINTENANCE
13/51
WARNING!
Before removing CONGI unit from subrack, switch-off the relevant Station Battery Fuse Breaker present at
the top of the Rack or in the Station Distribution Frame; subsequently remove the station battery cable if
necessary and then extract the CONGI unit.
Figure 2.
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 FLOW-CHART). IF POWER SUPPLY IS PRESENT PROCEDE WITH OUTPUT NO.
5.4
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.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
14/51
The troubleshoot procedure with the Craft Terminal consists of the following steps:
a) The alarms/status view organization for the equipment is shown in Figure 2.. Observe the active
alarms on the Severity Alarm Synthesis, Domain Alarm Synthesis and Management States
Control Panel always present on the window (it resumes all the NE alarms).
Table 3. Describes the meaning of these alarms/statuses and the relevant maintenance actions.
b) In case of alarm presence, access the Alarm Surveillance to troubleshoot. This application
gives the details of the detected alarms and helps for their localization.
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):
ED
Transmission bearer level. It is the support for the path level and can be further split into physical
level (Transmission media) and Transmission section level. The sections can be either regenerator
or multiplexer and utilized for specific functions associated to the EOW channels of the SDH frame.
The interface alarms (or section alarms, indicated in the tables) belong to this level (example: Line
LOS, LOS, B2etc.).
Path level It concerns the data transfer between the access points and the path. It does not depend
on the service or on the type of Transmission media. It constitutes the circuit level support. The path
can be either lower order (LO) or higher order (HO) depending on the capacity of data transferring.
Like the regenerator and multiplexer sections, the paths too have specific functions associated to the
EOW channels of the SDH frame. The alarms listed in the cited tables, where path level
troubleshooting is required, belong to this level (example: TU AIS, TU LOP).
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
15/51
Circuit level. This level concerns the transfer of information between the access points and the
circuit proper. It is a direct support for the telecommunication services. It superimposes the SDH
function and is considered as the transport agent hence no SDH order-wire channel associated
functions are required. An example of this level alarm is Tributary LOS.
Figure 3.
5.4.2
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
16/51
Figure 4.
The critical (CRI) or major (MAJ) alarms indicate severe alarms that could have impact on the current
traffic (interruption or degrade). Thus requiring a rapid intervention to restore the regular working condition
of the equipment.
A message under the mouse facility provides the alarm or status complete denomination. A message
appears in the message area in the bottom left corner of the view.
5.4.3
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
17/51
The alarms SUP, LAC, COM, OS, MGR, NTP and AC are part of the Management States Control Panel,
presented in Table 5.
All these indications (except for SUP, LAC, COM, OS, MGR, and NTP) are the summaries of particular types
of alarms detected by the equipment, hence the specific cause of alarm is to be found as indicated in the
following paragraphs: 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.9.
Table 1. Reports the association between the colors of the Alarms and their Severity.
For the Domain Alarms Synthesis the color corresponds to the highest severity among the set of the active
alarms for the relevant domain, according to the same rules of previous Tableau 1.
Tableau 2. Reports the colors of the Management States Control Panel when not in "normal" condition.
Table 1. Alarms colors and Severity association
Alarm Color
Severity
RED
CRITICAL
ORANGE
MAJOR
YELLOW
MINOR
CYAN
WARNING
WHITE
INDETERMINATE
GREEN
NO ALARM
Mnemonic
Alarm/Status
Description
CRI
Critical alarm
Maintenance
Synthesis of alarms that needs immediate troubleShooting (typical: NE isolation). NB1.
See detailed indication in the following Para.
MAJ
Major (Urgent) alarm Synthesis of alarms that needs immediate troubleshooting. NB1. See detailed indication in the following
Para.
MIN
WNG
Warning alarm
IND
Indeterminate alarm
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
18/51
Alarm/Status
Description
EXTP
External Point
(Housekeeping alarm)
SYNC
Maintenance
Check the relevant station alarm associated to the
Input housekeeping indication. See detailed indication
in the following Para.
EQP
Equipment alarm
TRNS
Transmission alarm
Description
SUP
Supervision state
Maintenance
GREEN: NE is under supervision.
BROWN: NE is not under supervision.
Used in the OS.
COM
NE
GREEN: Identifies the Enable operational state of
unreachable/unreachable the connection between NE and Craft Terminal (SDH
service link up)
RED: Identifies the Disable operational state of the
connection between NE and Craft Terminal (SDH
service link down)
OS
Operational System
Isolation
MGR
Manager level
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
19/51
NTP
AC
Abnormal Condition
NB1: Alarm Severity Assignment Profile can modify the assignment of each alarm root to the various
syntheses.
5.4.4
Figure 5.
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.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
20/51
Figure 6.
Alarm Surveillance
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
21/51
DESCRIPTION
The severity assigned to the alarm is indicated, with the relevant
color, i.e.: MAJOR, MINOR, WARNING
- Event date and time Indicates year, month, day and hour of the alarm.
- Friendly Name
- Event Type
- Probable Cause
- Reservation Status
- Clearing status
Identify the rack, board, port, and TP in which the alarm is detected,
i.e.: / r01sr1sl09/#port01-CE1S
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,
- Acknowledge status Indicates if the alarm has been acknowledge (ACK) with the button
on the COMPACT ADM unit or not (NACK).
- Correlated notification Not used
flag
- Repetition counter
Not used
The information supplied helps the operator during the troubleshooting operation.
Table 6. Supply general indications of alarms meaning and relevant maintenance actions that can be done
with the information given in the applications.
The maintenance action must take into account the board where the alarm is detected.
External Points alarms are referred to the input external point relevant to the Housekeeping signals. They
are available for the customer by connecting them to a dedicated subrack connector.
Detailed description of this application is given in the AS Operator's Handbook.
Table 6. General aspect of alarms meaning and relevant maintenance actions
PROBABLE CAUSE
MAINTENANCE
Check line
Replace unit
AIS
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
22/51
Check line
Configuration error
Check the entire TU path. Alarm indicates AIS signal received on the
TU
Resource Isolation
Communication Subsystem
Isolation (CSF)
Unequipped (U)
Configuration error
Present (UEP)
Internal Communication Problem
Unavailable
PM_AS- Performance
error
LOMF - Loss Of MultiFrame
AUXP
error (RNTE)
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
23/51
BOARD
OF DISPLAYED ALARM
ACRONYM
Unit missing
(RUM)
A2S1
A21E1
A3E3
A3T3
A4ES1
ETHATX
ETHMB
GETHAG
HPROT
L41
L41N
L42
L42N
P3E3/T3
P4ES1N
P4S1
P4S1N
P21E1
P21E1N
P21E1NM4
P63E1
P63E1N
P63E1NM4
P8DCN
S41
S41N
ES18FE
ES48FE
COADM1
COADM2
COWLA2
COMDX8
MAINTENANCE
Unit Problem
(RUP)
Replace unit
PR16
Unit missing
(RUM)
Unit Problem
Replace unit
(RUP)
Unit type mismatch
(RUTM)
Power Problem
(POP)
Pump failure
Replace unit
(PF)
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
24/51
Replace unit
GETHMB
ES18FE
ES18FX
ES48FE
ES16
SYNTH16
SYNTH16N
PREA1GBE
PREA4ETH
ATM8X8
ATM4X4
S161
S161N
S161ND
L161
L161N
L161ND
L 162
L162N
L162ND
I161ND
ED
Replace unit
03
Replace unit
Insert right unit (unit inserted into a slot set
with another type of unit)
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)
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)
Replace unit
Check the fan units and substitute the
faulty one
Insert missing unit
CONGI
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
25/51
Unit Problem
(RUP)
Replace unit
LAN problem
(LAN)
Battery Failure
(BF)
Fuse Failure
(FF)
Unit missing
(RUM)
Unit Problem
(RUP)
SERGI
Battery Failure
(BF)
Fuse Failure
(FF)
ED
MODULE
OF DISPLAYED ALARM
ACRONYM
03
MAINTENANCE
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
26/51
Unconfigured
Equipment Present
(UEP)
5.4.5
ICMI
IS1.1
IL1.1
IL1.2
MM1
IS4.1
IL4.1
IL4.2
1000B
1000B
100B
OHI
OLIN
OHMM
OLMM
SS162E
SL162E
SS162C
SL162C
SL162
SL161
SI161
SS161
It is also possible to analyze the detailed alarm presence on the TPs of each ports of the NE, following the
indication of the Port View chapter on the previous Section of this Handbook.
Figure 7. To Figure 9 is an example of a Port view.
For each TP of the Port a detail of the relevant alarms is presented.
On the port view the messages displayed at the bottom provide information about:
-
State of the connection for Ethernet port (available only if an Ethernet port has been selected)
A message under the mouse indicator provides the name of the alarm or object on which it is located, in this
way facilitating the identification of the alarm or status or object.
The non-alarmed condition of an alarm icon is represented by a green color and a "-" sign in the box.
The alarmed condition is represented by the color of its severity (as assigned by the ASAP) and an "X" signs
in the box.
The alarms, which can be found in the Port view, are listed in Table 7. Where the relevant maintenance
actions are reported too.
The information regarding ALS states and Laser state useful for operators safety purpose are
reported in the following:
ALS states:
Inactive = No ALS has been activated (Off) or the laser has been Forced ON/OFF.
In test = the laser restart has been automatically activated.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
27/51
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
28/51
Figure 7.
ED
03
Example of SDH Port View alarms (with MSP schema)
SC.4 : NE MAINTENANCE
29/51
Figure 8.
ED
03
Example of ATM Port View alarms
SC.4 : NE MAINTENANCE
30/51
Figure 9.
5.4.6
The alarm and status indications at Board level can be obtained, following the indication of the Board View
chapter on the previous Section of this Handbook.
The alarm and status indications depend on the unit type; for example SDH units is organized on two levels
of presentation (in the first is selected one of the available ports) and each view contains dedicated
indications.
An alarm box is displayed on each port, to indicate whether the port is alarmed.
An indication in the "message/status area" provides information about the board Administrative State: "inservice" or "out-of-service".
The alarms of the board are reported at the bottom of the "message/status area", by means of various boxes
containing relevant acronyms.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
31/51
Figure 10.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
32/51
Figure 11.
5.4.7
The alarms and status indications at subrack and rack level can be obtained, following the indications given
on the previous Section of this Handbook ("NE management").
An alarm box is displayed on each board, to indicate whether the board is alarmed. This board alarm
summarization is activated when one of the board alarms (those reported at the bottom of the Board view) is
active.
A "lock" symbol on a board indicates that it is "in-service". Else, the lack of this symbol indicates its "out-ofservice" 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.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
33/51
Figure 12.
ED
03
Example of Subrack view alarms and status
SC.4 : NE MAINTENANCE
34/51
Figure 13.
5.4.8
To obtain Fan Subrack alarms indications click twice with the mouse on the relevant subrack drawing in the
rack level view.
ED
Battery Failure (BF): check that the station battery cables are right connected
Cabling Problem (CAP): check that the alarms cable between the Fans Subrack and the CONGI unit
is right connected; check also the configuration in the Equipment menu. (Connected FAN to
CONGI#1 or connected FAN to CONGI#20)
Temperature Out Of Range (TOOR): verify the Fan unit alarm and in presence of faulty substitute
the relevant unit; clean also the Dust filter if necessary.
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
35/51
Figure 14.
5.4.9
The alarm indications at Equipment level can be obtained, following the indication of the Equipment View
chapter on the previous Section of this Handbook.
Fuse Failure (FF): Substitute the fuse in the CONGI unit and search for a cause
AND Battery Failure (ABF): Failure of the Service Power Supply connected to the CONGI Rack
connector.
Specific Hardware Diagnostic (SDH): Indicate the presence of link failure between the MATRIX and
one of the units; for details choose the Internal Link Monitor option of the Diagnosis menu.
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
36/51
Figure 15.
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
37/51
Figure 16.
ED
03
Example of External Points alarms and status
SC.4 : NE MAINTENANCE
38/51
No particular indication is given as to spare handling, which is left to the Maintenance Administration.
Hardware set the spare unit exactly as the unit to replace. Settings are specified in the MS
documents. Here a layout figure indicates the exact location of all the setting arrangements and a
table relates the operations to achieve with the settings. The cited documents are enclosed in the
Technical Handbook.
Simply replace those units not provided with any software settings
With regard to the COMPACT ADM (also called SYNTH or SYNTHN) unit refer to paragraph 6..
With regard to the ATM MATRIX 4X4 unit refer to paragraph 6.2.
When upgrading equipment with New Hardware (for example SYNTHN unit) that substitutes the
old units (for example SYNTH unit), follow the indication given in paragraph 7.
WARNING: In order to avoid short Circuit, before substituting the CONGI unit,
Switch--off the relevant Station battery fuse breaker. Subsequently remove the Station
Battery cable and extract the CONGI unit.
WARNING: before inserting the new spare unit carefully checks the integrity of the
relative connectors.
Dont insert the units that have been damaged during the transport/storing or in a phase
before their replacing.
6.1
N.B. In this paragraph for COMPACT ADM is generically intended one of the following unit:
-
SYNTH16
SYNTH16N
Various procedures are utilized to replace a COMPACT ADM faulty unit. They depend on the
following maintenance conditions:
-
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
39/51
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.
CONGI unit version (read NOTES in Figure 17. and Figure 18.)
The flow charts of Figure 17. And Figure 18. Illustrates the procedures to follow
For the COMPACT ADM substitution.
The procedure aim is to replace the faulty unit without causing configuration changes and/or
unwanted faults; when not possible this is indicated in the flow chart.
Replacement problems:
1 When replacing the COMPACT ADM unit the traffic of the two SDH ports is lost when not SNCP protected.
Then it is suggested to replace in low traffic condition.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
40/51
Figure 17.
ED
03
SC.4 : NE MAINTENANCE
41/51
Figure 18.
ED
03
SC.4 : NE MAINTENANCE
42/51
2 When plug-in a COMPACT ADM unit and supervision it with NM, if the following warning box
appear.
Figure 19.
The following dialogue box is opened from which you can set the local NE time.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
43/51
Figure 20.
6.2
Two different procedures are available for ATM MATRIX 4X4 substitution according to the EPS schema.
The flow-charts of Figure 19. Illustrates the procedures to follow for the ATM MATRIX 4X4 when it is not EPS
protected.
The flow-charts of Figure 20. Illustrates the procedures to follow for the ATM MATRIX 4X4 when it is EPS
protected.
The procedure aim is to replace the faulty unit without causing configuration changes and/or unwanted faults.
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
44/51
Figure 21.
ED
03
ATM MATRIX 4X4 unit replacement without EPS protection
SC.4 : NE MAINTENANCE
45/51
Figure 22.
6.3
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
46/51
In the next paragraphs is indicated the procedure to follow when upgrading an equipment with New
Hardware.
The new Hardware is identifying by the N letter at the end of the acronym unit (for example 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
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!
ED
Before inserting the new SYNTHN in subrack slot 6, follow the instruction described in Figure 21.. 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 6
Select the Modify option from the Equipment menu and select the SYNTHN acronym from the list
then click on ok.
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
47/51
Figure 23.
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
48/51
ED
Insert the new SYNTHN into the subrack slot 15; a RUTM (unit type mismatch) alarm will be present.
On Craft Terminal in the Subrack level view select the SYNTHN unit in slot 15
Select the Modify option from the Equipment menu and select the SYNTH acronym from the list
then click on ok.
Force the EPS Switching on SYNTHN in slot 15 by selecting the Switch option from the EPS menu.
For details see the paragraph Switching EPS in the NE MANAGEMENT section of this Handbook.
Before inserting the new SYNTHN in subrack slot 6, follow the instruction described in Figure 22.. 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 6
Select the Modify option from the Equipment menu and select the SYNTHN acronym from the list
then click on ok.
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
49/51
Figure 24.
ED
03
SC.4 : NE MAINTENANCE
50/51
[3] Upgrading with a new SYNTHN EPS protected with STM-N ports SNCP protected
The procedure is the same of that described on point [2]. But without traffic interruption on the STM-16 ports
present on the SYNTH because SNCP protected.
7.2
P4S1, S-41, L-41, L-42 substitution with P4S1N, S-41N, L-41N, L-42N
During the substitution the traffic carried by the units will be lost if not SNCP protected.
In the following an example will be given substituting a P4S1 with a P4S1N; the same procedure can be
applied to substitute the S-41, L-41, L-42 units respectively with S-41N, L-41N, L-42N units.
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.
END OF DOCUMENT
ED
03
SC.4 : NE MAINTENANCE
3AL 98253 ADAA
51/51
03
09/01/2006
Creation
ED
DATE
CHANGE NOTE
Distribution: Internal
Chen Yu
APPROVED BY
PREPARED BY
External
ED
03
SC.5: SIBDL
3AL 98253 ADAA
1/19
INTRODUCTION .......................................................................................................................................4
1.1
1.1.1
Document scope...........................................................................................................................4
1.1.2
Target audience............................................................................................................................4
1.2
Scope................................................................................................................................................4
Terminology.....................................................................................................................................4
1.2.1
1.2.2
Glossary of terms..........................................................................................................................4
2.1.1
3
ED
3.1.1
Remote Access Service configuration (only needed for Windows NT environment) .................14
3.1.2
3.1.3
03
SC.5: SIBDL
3AL 98253 ADAA
2/19
ED
03
SC.5: SIBDL
3AL 98253 ADAA
3/19
INTRODUCTION
1.1
Scope
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:
1.1.2
Download with SIBDL. The complete procedure is indicated. See Chapter on page
Configuration for SIBDL. Configurations to be performed for SIBDL operation are described.
Target audience
1.2
1.2.1
Terminology
Acronyms and abbreviations
Glossary of terms
ED
03
SC.5: SIBDL
3AL 98253 ADAA
4/19
2.1
This procedure describes how to download NE software with the SIBDL (Standard Image Binary Download)
program.
2.1.1
ATTENTION:
Download with SIBDL program put the COMPACT ADM unit out of service regarding to the supervision and
control function, while the traffic is not lost.
It must not be executed to download a spare unit that contains software; in this case use the Download
option of the EML-USM, presented in the previous section.
SIBDL tool permits to download the software towards the NE using the Q interface (Ethernet connection) or
the F interface RS232 (serial line) of the NE.
When using the Q interface the time necessary to the operation is reduced to some minute.
WARNING:
In Windows NT environment, it should have configured, before to use SIBDL:
TCP/IP protocol, Protocol Service, TEL NET Accessory, defined by the NT Administrator.
RAS (Remote Access Service) and Serial Cable Modem.
TCP/IP protocol, Protocol Service, TEL NET Accessory, defined by the NT Administrator.
Serial Cable Modem refer in Para Serial Cable Modem configuration for Windows 2000
environment
N.B.
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.
ED
03
SC.5: SIBDL
3AL 98253 ADAA
5/19
Figure 1.
4) In the field "source file" at the bottom write the path name of the NE descriptor file (see Figure 2.).
The path name has typically the following format (see the example in the figure):
<Directory>/<NE name and release number>/<file descriptor>
Note: In current release it is possible to download two types of file descriptor according to the following rules:
1. Create the NE software package as explained in the paragraph "NE Software package installation
procedure" NE MANAGEMENT of this Manual.
2. If the software to download manage only the SDH functionality, select the file descriptor in the
directory 1662SMC (example:
/ALCATEL/Q3CT_Pv1.3.05/FTservices/data/1662SMC/2.3.08/1662.dsc)
3. If the software to download manage the SDH+ATM/IP functionality, select the file descriptor in the
directory
1662SMC(example:/ALCATEL/Q3CT_Pv1.3.05/FTservices/data/1662SMCE/2.3.08/1662.dsc)
ED
03
SC.5: SIBDL
3AL 98253 ADAA
6/19
Figure 2.
5) Press ENTER
6) This step (see Figure 3.) asks for the "IP Address" insertion.
In the field "NE_IP_address [PPP TEL NET]" at the bottom:
- With F interface: write PPP and press ENTER
- With Q interface:
ED
03
SC.5: SIBDL
3AL 98253 ADAA
7/19
Figure 3.
7) This step (see Figure 4.) asks if the flash card must be formatted. Type "y" to format the flash card; as
result of this action the program ask for a confirmation (see Figure 5.)
ED
03
SC.5: SIBDL
3AL 98253 ADAA
8/19
Figure 4.
ED
03
SC.5: SIBDL
9/19
ED
03
Figure 5.
SIBDL download procedure - step 5
Figure 6.
SC.5: SIBDL
10/19
8)Typey.(if the synth16s version is before 2005/01/19,please choose n to improve the download speed.)
(see Figure 6.).
9) Type "y. The screen shows the automatic download evolution with a final message indicating the
completed download (see Figure 7.).
Figure 7.
ED
03
SC.5: SIBDL
3AL 98253 ADAA
11/19
Figure 8.
12) Extract and re-insert the EQUICO unit to complete the operation.
13) Extract and re-insert again the EQUICO unit to complete the operation
14) Run the 1320CT application, execute Start supervision and NE login
15) From Craft Terminal (EML-USM view) execute the normal download procedure:
N.B. Check that no RUTM alarm is present in the slot reserved to the main MATRIXN.
If RUTM alarm is present means the board type inserted in the subrack (typically MATRIXN in this release)
and the board type software configured (typically MATRIX) is not the same; under this condition the user
must change the board type with the Equipment->Set menu.
- Select Init download from Download menu
- Select the SW package to Download and click on OK button
In this condition the download is executed immediately
- Select Unit info from Download menu
- Select the Software Package loaded as explained above and activate it
ED
03
SC.5: SIBDL
3AL 98253 ADAA
12/19
ED
03
SC.5: SIBDL
13/19
3.1
To install a new modem, the user should have administrator privileges and need the installation CD-ROM of
Windows NT, then execute:
Double click on "My computer" icon on the PC desktop and double click on "Control panel" icon;
Select the folder "Services" in the "Network" window and push the button "Add": start the "Select
Network Service" window;
3.1.2
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;
ED
03
SC.5: SIBDL
3AL 98253 ADAA
14/19
Double click on "My computer" icon on your PC desktop and double click on "Control panel" icon;
Double click on "Phone and Modem Options" icon and select the "Modems" folder;
Push the button "Add": "Add/Remove Hardware Wizard: Install New Modem" window will appear;
Put a tick against "Don't detect my modem; I will select it from a list" and push the button "Next >";
Figure 9.
ED
Push the button "Have disk... the window "Install from disk" will appear;
Push the button "Browse..."
Search the folder where SIBDL is installed and select the file "mdmalca.inf", after push the button
"Open";
Push the button "OK" on the "Install from disk" window;
Select the modem named "Serial cable" into dialog box from "Install New Modem" window and push
the button "Next >";
03
SC.5: SIBDL
3AL 98253 ADAA
15/19
Figure 10.
ED
Put a tick against "Selected ports" and select only one port (the serial port must be available, i.e. not
used by another RAS modem) and push the button "Next >";
03
SC.5: SIBDL
3AL 98253 ADAA
16/19
Figure 11.
ED
The window "Digital Signature Not found" will appear: push the button "Yes", and after the button
"Finish" to end modem installation;
03
SC.5: SIBDL
3AL 98253 ADAA
17/19
Figure 12.
ED
At the end, the "Phone and Modem Options" window will display the installed modem
03
SC.5: SIBDL
3AL 98253 ADAA
18/19
Figure 13.
ED
03
END OF DOCUMENT
SC.5: SIBDL
19/19