Professional Documents
Culture Documents
Operator's Handbook (3AL91670AAAATQZZA - ED02)
Operator's Handbook (3AL91670AAAATQZZA - ED02)
Alcatel
METRO OMSN Rel. 4.4B/5.2B
VOL. 1/1
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
4
5
5
5
2 PRODUCT-RELEASE HANDBOOKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
15
4 HANDBOOK DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
21
21
21
21
22
22
22
22
23
23
24
24
24
02
050414
01
041119
ED
DATE
ECR 23082
CHANGE NOTE
C.FAVERO ITAVE
J. MIR S. MAGGIO
C.FAVERO ITAVE
J. MIR S. MAGGIO
P.GHELFI ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
P.GHELFI ITAVE
METRO OMSN
Rel. 4.4/5.2A
OPERATORS HANDBOOK
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
1 / 24
TABLES
Table 1. Handbooks related to the specific product hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. Handbooks related to the specific product SW management and local product control . .
Table 3. Handbooks related to ATM specific product SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Handbooks related to PR_EA specific product SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5. Handbook related to ISAPR specific product SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6. Handbook related to ISAES specific product SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7. Handbooks common to Alcatel Network Elements using 1320CT platform . . . . . . . . . . . . .
Table 8. Optional handbooks common to 16xxSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9. Documentation on CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
02
7
8
9
9
9
10
10
11
11
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
2 / 24
ANV P/N
PRODUCT
RELEASE
VERSION
(N.B.)
ANV P/N
1640FOX
Rel.4.4
1650SMC
Rel.4.4
1660SM
Rel.4.4
1660SM
Rel.5.2
3AL 81407ACAA
For further information on the Alcatel software product and its physical distribution support refer to the
Introduction section.
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
3 / 24
ED
the structure (hardware composition) and all the possible operating modes of the equipment
(product-release) this handbook refers to.
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
4 / 24
N.B.
This handbook is a collection of documents (each contained in a specific section) that can have
editions different from one another.
The Edition of the whole handbook is that of Section 1 (HANDBOOK GUIDE).
The edition of the enclosed documents indicated in the following table is that of the
corresponding original internal document.
HANDBOOK EDITION
01
02
03
04
05
SECTION EDITION
HANDBOOK GUIDE
01
02
INTRODUCTION MANUAL
01
02
NE MANAGEMENT MANUAL
01
02
MAINTENANCE MANUAL
01
02
SIBDL MANUAL
01
02
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
5 / 24
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
6 / 24
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2 PRODUCT-RELEASE HANDBOOKS
The list of handbooks given here below is valid on the issue date of this Handbook and
can be changed without any obligation for ALCATEL to update it in this Handbook.
Some of the handbooks listed here below may not be available on the issue date of this
Handbook.
The standard Customer Documentation in the English language for the equipment whose
product-release-version is stated in para.1.2 on page 3 consists of the following handbooks:
Table 1. Handbooks related to the specific product hardware
HANDBOOK
REF
1640FOX Rel.4.4
Technical Handbook
Part Number
THIS
HDBK
1
Provide information regarding Equipment description, Maintenance,
Hardware setting documentation.
1640FOX Rel.4.4
Installation Handbook
2
Provide information regarding Equipment Installation, according to
AInstallation Engineering Dept. rules.
1640FOX Rel.4.4
Turnup & Commissionig Handbook
3AL 91666CAAA
3
Provide information regarding Equipment TurnOn, Test and Operation,
according to AInstallation Engineering Dept. rules.
1650SMC Rel.4.4
Technical Handbook
4
Provide information regarding Equipment description, Maintenance,
Hardware setting documentation.
1650SMC Rel.4.4
Installation Handbook
5
Provide information regarding Equipment Installation, according to
AInstallation Engineering Dept. rules.
1650SMC Rel.4.4
Turnup & Commissionig Handbook
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
7 / 24
HANDBOOK
1660SM Rel.4.4
Technical Handbook
Part Number
THIS
HDBK
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
REF
3AL91668 AAAA
7
Provide information regarding Equipment description, Maintenance,
Hardware setting documentation.
1660SM Rel.4.4
Installation Handbook
8
Provide information regarding Equipment Installation, according to
AInstallation Engineering Dept. rules.
1660SM Rel.4.4
Turnup & Commissionig Handbook
3AL 91668CAAA
9
Provide information regarding Equipment TurnOn, Test and Operation,
according to AInstallation Engineering Dept. rules.
1660SM Rel.5.2 Version B
Technical Handbook
3AL91669 AAAA
10
Provide information regarding Equipment description, Maintenance,
Hardware setting documentation.
1660SM Rel.5.2
Installation Handbook
11
Provide information regarding Equipment Installation, according to
AInstallation Engineering Dept. rules.
1660SM Rel.5.2
Turnup & Commissionig Handbook
12
Provide information regarding Equipment TurnOn, Test and Operation,
according to AInstallation Engineering Dept. rules.
Table 2. Handbooks related to the specific product SW management and local product control
REF
HANDBOOK
METRO OMSN REL. 4.4 & 5.2 Version B
CT Operators Handbook
Part Number
THIS
HDBK
13
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
8 / 24
REF
Part Number
THIS
HDBK
or note
14
ATM Rel.1.2
Operators Handbook
15
ATM Rel.2.0
Operators Handbook
16
ATM Rel.2.1
Operators Handbook
17
ATM Rel.2.2
Operators Handbook
REF
HANDBOOK
Part Number
18
THIS
HDBK
or note
REF
HANDBOOK
FACTORY
Part No.
19
20
21
THIS
HDBK
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
9 / 24
REF
HANDBOOK
22
23
24
25
26
THIS
HDBK
HANDBOOK
REF
1320CT 3.x
Basic Operators Handbook
Part Number
THIS
HDBK
OR
NOTE
27
Provides general information and operational procedures common to all 1320CT
(Craft terminal) of Alcatel InfoModel Network Elements.
1330AS Rel. 6.5
Operators Handbook
28
Provides detailed information and operational procedures regarding the alarm
Surveillance software embedded in the 1320CT software package.
ELB 2.X
Operators Handbook
29
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
10 / 24
REF
FACTORY
Part No.
955.100.692 N
HANDBOOK
S916xxSM
System Installation Handbook
THIS
HDBK
30
Provides general installation rules necessary to install the Optinex family
equipment in the S9 Rack .
Optinex RACK16xxSM
System Installation Handbook
955.110.202 L
31
Provides general installation rules necessary to install the Optinex family
equipment in the Optinex Rack .
N.B.
CDROM TITLE
Part Number
32
Contains, in electronic format, the following handbooks: REF. 1 to 13
1320CT 3.x BASIC CDROMDOC EN
3AL79552 AAAA
33
Contains, in electronic format, the following handbooks: REF. 27 to 29
ATM 1.2 CDROMDOC EN
34
Contains, in electronic format, the following handbook: REF. 14 on page 9
ATM 2.0 CDROMDOC EN
35
Contains, in electronic format, the following handbook: REF. 15 on page 9
ATM 2.1 CDROMDOC EN
36
Contains, in electronic format, the following handbook: REF. 16 on page 9
ATM 2.2 CDROMDOC EN
37
38
Contains, in electronic format, the following handbook: REF. 18 on page 9
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
11 / 24
CDROM TITLE
Part Number
PR 1.0 CDROM EN
39
Contains, in electronic format, the following handbook: REF. 19 on page 9
PR 1.1 CDROM EN
40
Contains, in electronic format, the following handbook: REF. 20 on page 9
PR 1.2 CDROM EN
41
Contains, in electronic format, the following handbook: REF. 21 on page 9
ES1 1.0 CDROM EN
3AL89875 AAAA
42
Contains, in electronic format, the following handbook: REF. 22 on page 10
ES1/ES4 1.1 CDROM EN
3AL89871 AAAA
43
Contains, in electronic format, the following handbook: REF. 23 on page 10
ES1/ES4 1.2 CDROM EN
3AL91805 AAAA
44
Contains, in electronic format, the following handbook: REF. 24 on page 10
ES16 2.0 CDROMDOC EN
45
Contains, in electronic format, the following handbooks: REF. 25 on page 10
ES16 2.1 CDROMDOC EN
46
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
12 / 24
REF
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
13 / 24
Lay the patient supine with his arms parallel with the body, if the patient is laying
on an inclined plane, make sure that his stomach is slightly lower than his chest.
Open the patients mouth and check that there are no extraneous bodies in his
mouth (dentures, chewinggum etc.),
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
14 / 24
SAFETY RULES
General rules
Risk of explosion
ELECTROMAGNETIC COMPATIBILITY
EQUIPMENT LABELS
Identical or similar information on Personal Computer, WorkStation etc., other than ALCATELs, loaded
with software applicative described in this Handbook, is supplied in the Constructors technical
documentation.
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
15 / 24
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
16 / 24
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
4 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 productrelease 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 (EMLUSM)
are listed and briefly described.
Chapter 3: Acronyms and abbreviations. The acronyms used in all the operator manuals are listed.
The aim of this document is to describe the Craft Terminal view, inserting operative information.
The Network Element Manual includes the following chapters:
Chapter 2: General introduction on views and menus. The view organization is presented and the
menus available listed and briefly described.
Chapter 3: NE management supervision. This chapter is dedicated to the NE states and NE access.
Chapter 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).
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
17 / 24
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 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 view 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 (EPS). This chapter permits to manage the EPS
protection, setting the relevant configuration.
N.B.
EPS is not applicable in 1640FOX
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
N.B.
MSSPRing Management menu is available only for 1660SM
Chapter 20: ISA port Configuration. This chapter describes the operations necessary for the
ATM/PR_EA/Ethernet boards creation and the ATM/PR_EA/Ethernet TTPs creation.
Chapter 21: Software management. This chapter permits to update the NE by means download
procedure and to manage NE software.
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
18 / 24
Chapter 7: Upgrading with New Hardware. The Hardware upgrading procedure is detailed.
Chapter 8: FLASH card substitution. The FLASH card substitution procedure is detailed.
Chapter 1: Introduction
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
19 / 24
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
20 / 24
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Consequently, no supply to the Customers of design documentation (like software source programs,
programming tools, etc.) is envisaged.
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
21 / 24
the name of the product-release (and version when the handbook is applicable to the versions
starting from it, but not to the previous ones),
the handbook issue date. The date on the handbook does not refer to the date of print but to the date
on which the handbook source file has been completed and released for the production.
5.4.1 Changes introduced in the same product-release (same handbook P/N)
The edition and date of issue might change on future handbook versions for the following reasons:
only the date changes (pointed out in the Table of Contents) when modifications are made to the
editorial system not changing the technical contents of the handbook.
the edition, hence the date, is changed because modifications made concern technical contents. In
this case:
in each section, the main changes with respect to the previous edition are listed;
in affected chapters of each section, revision bars on the left of the page indicate modifications
in text and drawings (this is done after the first officially released and validated version).
Changes concerning the technical contents of the handbook cause the edition number increase (e.g. from
Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition of
a version character (e.g. from Ed.02 to Ed.02A).
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operators Handbooks) are not
modified unless the new software version distributed to Customers implies manmachine
interface changes or in case of slight modifications not affecting the understanding of the
explained procedures.
Moreover, should the screen prints included in the handbook contain the product-releases
version marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
5.4.2 Supplying updated handbooks to Customers
Supplying updated handbooks to Customers who have already received previous issues is submitted to
commercial criteria.
By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue
(supplying erratacorrige sheets is not envisaged).
5.4.3 Changes due to a new product-release
A new product-release changes the handbook P/N and the edition starts from 01. In this case the modified
parts of the handbook are not listed.
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
22 / 24
the documentation of system optional features that Customers could not buy from Alcatel
together with the main applicative SW.
the documentation of system optional features (e.g. System Installation Handbooks related to
racks that Customers could not buy from Alcatel together with the main equipment).
A CDROM is obtained collecting various handbooks and documents in .pdf format. Bookmarks and
hyperlinks make the navigation easier. No additional information is added to each handbook, so that the
documentation present in the CDROMs is exactly the same the Customer would receive on paper.
The files processed in this way are added to files/images for managing purpose and a master CDROM
is recorded.
Suitable checks are made in order to have a virusfree product.
After a complete functional check, the CDROM image is electronically transferred to the archive of the
Production Department, so that the CDROM can be produced and delivered to Customers.
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
23 / 24
The CDROM starts automatically with autorun and hyperlinks from the opened Index document permit
to visualize the .pdf handbooks
Other hyperlinks permit to get, from the Technical handbooks, the specific .pdf setting documents.
In order to open the .pdf documents Adobe Acrobat Reader Version 4.0 (minimum) must have been
installed on the platform.
The CDROM doesnt contain the Adobe Acrobat Reader program. The Customer is in charge of getting
and installing it.
ReadMe info is present on the CDROM to this purpose.
Then the Customer is allowed to read the handbooks on the PC/WS screen, using the navigation and
zooming tools included in the tool, and to print selected parts of the documentation through a local printer.
5.5.3 CDROM identification
Each CDROM is identified:
Each CDROM is identified:
1)
by the following external identifiers, that are printed on the CDROM upper surface:
2)
and, internally, by the list of the source handbooks and documents (P/Ns and editions) by whose
collection and processing the CDROM itself has been created.
END OF DOCUMENT
ED
02
SC.1:HANDBOOK GUIDE
3AL 91670 AA AA
24
24 / 24
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Reading rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
3
3
3
5
5
6
6
7
8
9
10
10
10
10
10
11
11
11
12
12
13
13
13
13
13
14
15
4 GLOSSARY OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
02
050414
01
041119
ED
DATE
ECR 23082
CHANGE NOTE
C. FAVERO ITAVE
J.MIR S.MAGGIO
C. FAVERO ITAVE
J.MIR S.MAGGIO
P.GHELFI ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
P.GHELFI ITAVE
METRO OMSN
Rel. 4.4/5.2A
OPERATORS HANDBOOK
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
1 / 22
TABLES
Table 1. Software products part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. Software licence part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. Software products part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Software licence part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5. Software products part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6. Software licence part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
02
7
7
8
8
9
9
SC.2:INTRODUCTION
3AL 91670 AA AA
22
2 / 22
1 INTRODUCTION
1.1 Scope
1.1.1 Document scope
The Introduction Manual present the Craft Terminal main functions and provides a general overview of the
different functionalities provided by the ELMUSM of the Craft Terminal for Info Model NE.
1.1.2 Target audience
The Introduction Manual is intended for all users.
The documents that should be read before starting this document are:
All the manuals describe menus, but not necessarily all the options of these menus. When a menu option
is not detailed in a manual, the information are surely given in another manual.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
3 / 22
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
4 / 22
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The Craft Terminal characteristic (computer configuration) are listed in the Basic Craft Terminal Operators
Handbook.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
5 / 22
Software package of the NE, to be installed in the NE or update the NE (by means of download
function)
The software package used for management permits the dialogue between craft terminal and NE, to
realize all the functions of the NES and EMLUSM ).
The software package used for updating the NE must be installed on the PC and then downloaded on
the NE, thus following product evolution.
Alcatel typically offers several software licences on the software product.
They are referred both to the Network Element software features and to the Craft Terminal software
features.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
6 / 22
2.2.2 1640FOX Software products and licences list and part numbers
Every Software Product is identified by a denomination and a part number, listed on the following table.
Table 1. Software products part numbers
Name
SWP 1640FOX SDH R.4.4 CDROM
N.B.
3AL 89846 AA
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.
3AL89684 AJ
3AL 89684 AK
3AL 89684 AL
3AL 89684 AM
3AL 89684 AN
3AL 89684 AP
3AL 89684 AQ
3AL 89684 AR
N.B.
N.B.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
7 / 22
2.2.3 1650SMC Software products and licences list and part numbers
Name
SWP 1650SMC SDH R.4.4 CDROM
N.B.
3AL 89849 AA
Every Software licence is identified by a denomination and a part number, listed on the following table.
Table 4. Software licence part numbers
Name
N.B.
3AL 89685 AF
3AL 89685 AG
3AL 89685 AH
3AL 89685 AJ
3AL 89685 AK
N.B.
N.B.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
8 / 22
Every Software Product is identified by a denomination and a part number, listed on the following table.
2.2.4 1660SM Software products and licences list and part numbers
Every Software Product is identified by a denomination and a part number, listed on the following table.
Table 5. Software products part numbers
Name
SWP 1660SM SDH R.4.4 CDROM
3AL 89852AA
3AL 89854 AA
3AL 89855 AA
N.B.
Every Software licence is identified by a denomination and a part number, listed on the following table.
Table 6. Software licence part numbers
Name
N.B.
3AL 89686 AF
3AL 89686 AG
3AL 89686 AH
3AL 89686 AJ
3AL 89686 AK
3AL 89686 AR
3AL 89686 AS
3AL 89686 AT
3AL 89686 AU
3AL 89686 AV
N.B.
N.B.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
9 / 22
In this chapter, are described the main functionalities of the Craft Terminal, referred to the Network Element
management views, obtained by means EMLUSM. The functionalities constitute the heading of each of
the paragraphs below.
2.3.1 Network Element management supervision
Deals with the NE state and access.
2.3.2 Network Element general configuration
Deals with the general configuration of the equipment.
NE Time management
Alarms Configuration
Alarm resynchronization.
Restart NE
Deals with housekeeping signals input from the external (station alarms) or forwarded (output) towards
the external.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
10 / 22
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
NTP configurations
IP Configuration
Tunneling Configuration
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.
Remote Inventory
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
11 / 22
This permits to set and show the transmission resources (TP) referred only to the port (SDH PDH, HOA,
ISA).
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:
MSP protection
Retiming
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
12 / 22
For each port a specific menu is available similar to the Port view where various configuration of the
specific port can be set.
Also Transmission view is than the entry point of other management functions .
2.3.11 Cross Connection management
This deals with the connection of all the Termination Point (TP), which are the starting and terminating
points of a transmission segment. In this way the multiplex structures are created, managing the traffic
flow. Similar operation are made on the OverHead cross connections.
Protection commands
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
13 / 22
ED
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.
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
14 / 22
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
15 / 22
XC: CrossConnection
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
16 / 22
4 GLOSSARY OF TERMS
Acknowledgment:
When an alarm is taken into account by the application, the operator has to acknowledge it to point out
that he has seen it and that he will react in the right way. During alarm configuration it is possible to set
a maximum delay for alarm acknowledgement. The operator can decide whether or not the alarm clear
has to be acknowledged.
Administrator:
A user who has access rights to all the Management Domains of the Craft Terminal product. He has access
to the whole network and to all the management functionalities.
Alarm:
An alerting indication to a condition that may have an immediate or potentially negative impact on the state
of an equipment or the CT. An alarm is characterized by an alarm begin and an alarm end.
Alarm Severity Assignment Profile:
Function allowing the assignment of severities to the alarms depending on their probable causes.
Alarm Status:
Identifies the type and severity of an occurring alarm.
Board:
A board is part of an NE. They are electronic cards that fit into slots in the NE.
Bridge:
The action of transmitting identical traffic on both the working and protection trails.
Bridge Request:
A message sent from a tailend node to the headend node requesting that the headend perform a
bridge of the working channels onto the protection channels.
Bridge Request status:
A message sent from a tailend node to all other nodes within the protection system indicating that the
tailend has requested a bridge.
Bridge&switch node:
The node that performs the bridge and switch function for a protection event. Where the bridge and switch
is performed on a per AU4 basis, the node executing a bridge and switch of at least one AU4 is referred
to as a bridge and switch node. Note that with a Transoceanic application, a node in the switching status
may not be a bridge&switch node, whereas a node in the passthrough state may be a bridge&switch
node. With the Classic application, only a request node (see below) may be a bridge&switch node.
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.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
17 / 22
Intermediate node:
The node that is not a request node. It is always in the passthrough state. If such a node executes bridge
and switch of at least one AU4 it is also a bridge&switch node.
International Telegraph and Telephone Consultative Committee:
Standard organization for telecommunications. Now called the ITUT (International Telecommunication
Union).
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
18 / 22
Isolated Node:
A single node that is isolated from a traffic perspective by ring switches on each of its two spans by its
adjacent nodes.
Kilobits per second:
Unit that correspond to the transmission of 103 bits every second.
Line Terminal:
A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can
undertake signal conversion functions (adapting a signal to two different transmission media) or
multiplexing/demultiplexing functions.
Logs:
Logs are files used to store history data concerning the incoming notifications, operator commands and
system alarms. The size of the log can be configured.
Management Domain:
The Craft Terminal product is partitioned into management domains for functional proposes. Each
management domain is associated with functionalities that enable the operators to manage the NEs.
Media Access Control Address:
Represents the Level 2 address for Local Area Networks.
Megabits per second:
Unit that corresponds to the transmission of 106 bits every second.
Misconnection:
A condition in which traffic destined for a given node is incorrectly routed to another node and no corrective
action has been taken.
MSSPRing channels:
The range of channels that are part of the MSSPRing operation (i.e. the whole of the working and
protection channels).
Multiplexer:
Equipment used to combine several signals to produce a single signal at a higher transmission rate and
to decompose it back to the smaller rate signals.
Multiplex Section:
In general, represents the section containing the multiplexed signals.
Network Access Domain:
Defined as a set of Network Elements. NADs are used to define the set of Network Elements that a user
can manage.
Network Element:
Either a telecommunication equipment or groups parts of a Telecommunication Network. Have
characteristics compliant with CCITT recommendations.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
19 / 22
Operator:
The enduser of the Craft Terminal. He supervises a part of the network that is dependant on his user profile.
Path:
According to ITUT Recommendation G.803, a path is a transport entity (i.e., architectural component)
used to transfer information. Nevertheless, this name will be used throughout this document to indicate
the information carried either unidirectionally or bidirectionally between two access points of a ring on
either a path link connection (if the two points are both PDH) or trail segment.
Physical Interface:
Electrical or Electrical/Optical transformers that decouples the line signals and adapt the form of signal
for further transmission. This functional block also manages clock extraction, signal loss monitoring and
loopback functions.
Port:
A physical point at which the Network Element can be attached to a transmission medium. A port is either
a termination point or an origination point.
Protocol request:
A message sent by a node to another node via K1/K2 bytes with the purpose of settling a certain behavior.
All the K1 request codes represent protocol requests, but not all of them are bridge requests. For example,
a SFR is a bridge request (see ITUT G841), but LPS is not: both of them are protocol requests. Even
NR is a protocol request.
Protocol reply:
A message sent by a node to another node via K1/K2 bytes with the purpose of acknowledging a received
protocol request.
Protection trail:
The trail allocated to transport the working traffic during a switch event. When there is a switch event, traffic
on the affected working trail is bridged onto the protection trail.
Protection section:
The full set of both protection and (lower) unprotected channels in a multiplex section.
Protection semisection:
The part of multiplex section (i.e. the N/2+1..N channels in a 2fiber STMN NE) consisting of protection
channels.
Repeater:
Equipment used to regenerate a signal when it has travelled a long distance.
Request node:
A node that generates either a protocol request or protocol reply (other than NR!). The pair of nodes
sending each other protocol request/reply are peer request nodes.
Severity:
Linked to alarms, severities indicate the magnitude related to the failure.
Shared protection:
A protection architecture using m protection entities shared among n working entities (m:n). The protection
entities may also be used to carry extra traffic when not used for protection.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
20 / 22
Operation System:
A system dedicated to the supervision of NEs in a standard way, using protocols and interfaces. it offers to
the operator a set of functions necessary to supervise the NEs. The 1353SH is an Operation System.
Span:
The set of multiplex sections between two adjacent nodes on a ring.
Span Switching:
Protection mechanism similar to the MSP that applies only to fourfibre rings where working and protection
channels are contained in separate fibres and the failure only affects the working channels. During a span
switch, the working traffic is carried over the protection channel on the same span as failure.
Squelched traffic:
An all 1s signal resulting from the squelching process (insertion of AUAIS in order to guarantee the
connections)
Switch:
The action of selecting traffic from the protection trail rather than the working trail.
Switching Node:
The node that performs the bridge or switch function for a protection event. In the case of a multiplex
section switched ring network architecture, this node also performs any necessary squelching of
misconnected traffic.
Tail End:
Node which detects the failure.
Telecommunication Management Network:
Defines the concept of interoperable management of TNs. They provide an organized network structure
to achieve the interconnection of the different components of the TN and the services to process the
information.
Telecommunication Network:
Describes the network to be managed. Provides the transmission, the transport and the switching
supports to the interconnected Network Elements.
Terminal Point:
Describes either the origin or the termination of a signal in an equipment. Is related to a port.
Thresholding:
This is the assignment of a specified value to monitored parameters ( for example BIt Error Rates) that,
when exceeded, generate trouble indications.
Unprotected channels:
See unprotected channel in ITUT G841. Each pair of unprotected channels is made up on one in the
working (semi)section plus one in the protection (semi)section.
Unprotected traffic:
See unprotected traffic in ITUT G841.
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.
ED
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
21 / 22
Working traffic:
Traffic that is normally carried in a working trail, except in the event of a protection switch.
Working trail:
The trail over which working traffic is transported when there is no switch events.
Working section:
The full set of both working and (upper) unprotected channels in a multiplex section.
Working semisection:
The part of multiplex section (i.e. the 1..N/2 channels in a 2fiber STMN NE) consisting of working
channels.
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
02
SC.2:INTRODUCTION
3AL 91670 AA AA
22
22 / 22
Working channels:
The channels over which working traffic is transported when there are no switch events. An APS system
performs restoration for the working channels only.
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
15
15
15
15
15
17
17
21
23
24
25
26
26
27
27
28
29
31
31
33
34
42
3 NE MANAGEMENT SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 NE management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 NE supervision and login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
45
46
49
49
50
50
02
050414
01
041119
ED
DATE
ECR 23082
CHANGE NOTE
C. FAVERO ITAVE
J. MIR S. MAGGIO
C. FAVERO ITAVE
J. MIR S. MAGGIO
P.GHELFI ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
P.GHELFI ITAVE
METRO OMSN
Rel. 4.4/5.2A
OPERATORS HANDBOOK
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
1 / 448
51
53
53
53
63
64
65
66
67
5 SECURITY MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Set Manager list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Set ACD level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
69
69
70
71
72
74
75
7 DIAGNOSIS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Alarms surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 Internal Link Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4 Log Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5.1 Upload remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5.2 View Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79
79
81
83
85
86
86
87
89
89
89
90
91
91
93
95
97
98
99
102
104
105
106
106
107
108
109
110
111
112
9 EQUIPMENT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 Introduction and navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 Set and change or remove board/subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 Connect Fan to CONGI board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
115
115
122
126
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
2 / 448
128
128
128
128
129
130
132
10 BOARD VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Board View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1 Port Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.2 Change Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.3 Show Supporting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
133
133
135
136
137
138
11 PORT VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Port View: elements on the TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 Port View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.4 Port Mode Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 Set Retiming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6 AU4 Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 Physical Media option menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.1 Automatic Laser Shutdown Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.2 Show Optical Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.3 Single Fiber Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.4 Ms Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.5 Line Length Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.6 Ethernet Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.7 Ethernet Mapping Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.8 Control Path Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7.9 LCAS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.8 TP Frame Mode Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.9 Show Supporting Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.10 Navigate to Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.11 Navigate to Monitoring View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.11.1 Navigate to HOA Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
139
139
141
142
144
146
148
151
152
156
157
159
160
161
164
165
167
170
173
174
175
176
177
177
178
185
187
188
193
193
194
195
199
200
201
202
204
206
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
3 / 448
211
211
212
213
213
214
214
214
215
217
217
227
227
230
231
234
235
235
235
236
237
239
241
242
242
245
247
248
249
249
250
251
252
15 CROSS-CONNECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.2 Multiplex Structures for SDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.3 Definition of Termination Points (TP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.4 Mapping Tables: TP Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.5 Cross-Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.6 Cross-Connection Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2 Operative Sequence to execute Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3 Cross-Connections management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3.1 Search Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3.2 Cross-Connection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3.3 Actions available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.4 Create/Modify Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.4.1 Cross-Connection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.4.2 Create a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.4.3 Modify a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.5 Activate/Deactivate/Delete Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.5.1 Activate a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.5.2 Deactivate a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
253
253
253
254
257
261
262
264
266
270
272
274
276
277
278
283
289
292
292
292
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
4 / 448
14 TRANSMISSION VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2 View elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3 View Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.1 View Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.2 Number of TPs Displayed in Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.3 Naming TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.4 Dynamic View Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.4 Transmission view access and menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5 Add TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5.1 TP Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6 TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6.1 High Order TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6.2 J0 Section Trace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6.3 Low Order TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.7 TP Threshold Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.8 Terminate/Disterminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.8.1 Terminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.8.2 Disterminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.9 Monitoring Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.9.1 Creation/Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.9.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.10 Structure TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.11 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.11.1 Loopback Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.11.2 Loopback Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.12 Physical Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.12.1 Set Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.13 Navigation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.13.1 Expand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.13.2 Hide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.13.3 Show Supported Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.13.4 Navigate to Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
292
293
293
295
296
298
299
16 OVERHEAD MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2 OH Connection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.3 Overhead views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.4 OH Cross Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.5 OH TP creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.6 OH TP deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.7 OH Phone Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
301
301
302
303
304
309
310
311
17 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2 Performance Monitoring on SDH port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.2 Supported Performance Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.3 Far End (FE) and Near End (NE) Performance Counting . . . . . . . . . . . . . . . . . . . . . . . .
17.2.4 Bidirectional counting (24 h Bi) for QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.5 End to End (ee 24h) Performance Counting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.6 Performance Monitoring on AUPJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.7 Tandem Connection Termination (TCT) and Monitoring (TCM) . . . . . . . . . . . . . . . . . . .
17.2.8 Performance Monitoring on 2 Mbit/s ISDNPRA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.9 Performance Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.10 Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.11 Performance Monitoring History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2.12 Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.3 Performance Monitoring on ETHRNET port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.3.2 Ethernet physical interface counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.3.3 Aggregate counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.3.4 Flow counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.4 Configuration (SDH port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.5 Display Current Data (SDH port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.6 Display History Data (SDH port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.7 PM Threshold Table Selection (SDH port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.8 PM Threshold Table Create / Modification / Display (SDH port) . . . . . . . . . . . . . . . . . . .
17.8.1 Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.8.2 Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.8.3 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.9 Configuration (Ethernet port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.10 Display current Data (Ethernet port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.11 Display history Data (Ethernet port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.12 PM overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
313
313
314
314
314
316
316
317
317
318
318
318
319
319
320
321
322
322
323
324
325
330
333
335
339
339
341
341
343
344
348
350
18 SYNCHRONIZATION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2 Synchronization Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.1 Displaying the Synchronization View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
355
355
357
357
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
5 / 448
358
361
364
365
368
369
370
372
374
375
376
19 MSSPRING MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.1 MSSPRING introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.2 MSSPRING connection configuration advices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.2.1 2Fiber MSSPRING connection configuration advices . . . . . . . . . . . . . . . . . . . . . . . . .
19.3 Operative sequence to configure MSSPRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.3.1 Operative sequence to configure 2Fiber MSSPRING . . . . . . . . . . . . . . . . . . . . . . . . .
19.4 MSSPRING Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4.1 MSSPRing Main Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4.2 Squelching Table with 2 fiber Terrestrial applications . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4.3 Activate, Deactivate and Delete commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5 MSSPRING Protection Status and Commands for 2 fiber terrestrial application . .
19.5.1 2F MSSPRing protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.2 External commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.3 2F MSSPRing dual protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.4 2F Protection Status Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
377
377
378
378
379
379
380
381
387
393
394
394
396
404
409
427
427
428
428
430
432
434
435
21 SOFTWARE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.1 Generalities and descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.1.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2 Software download operative sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2.1 Software Download upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.3 Software Download Manager menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.4 Init download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.5 SW package Activation and Units information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.6 Mib management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
439
439
440
441
441
442
443
445
447
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
6 / 448
ED
02
18
19
20
35
36
37
38
39
40
41
46
47
47
50
51
51
54
54
56
57
59
60
61
62
63
64
64
65
66
67
69
70
72
73
74
75
75
76
76
79
80
81
81
82
84
85
86
86
87
90
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
7 / 448
ED
02
92
94
96
97
98
100
101
101
103
103
104
105
107
108
109
110
111
113
117
118
119
119
120
120
121
123
126
127
128
129
130
131
131
132
133
134
134
135
136
137
138
140
141
141
143
144
145
146
147
149
150
150
151
152
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
8 / 448
Figure 105. Automatic Laser Shutdown Management (after ALS Function delete) . . . . . . . . . . . . . .
Figure 106. ALS and Laser current state (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 107. Visualizing a port optical parameters (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 108. Bidirectional Transmission on a single fiber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 109. Single Fiber Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 110. Ms Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 111. PDH Line Length Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 112. Ethernet Port Configuration options (fast ethernet example) . . . . . . . . . . . . . . . . . . . . .
Figure 113. Ethernet Port Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 114. Information dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 115. Gigabit Ethernet port view (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 116. Ethernet Mapping Protocol (EXAMPLE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 117. Control Path Activation:Individual Path mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 118. Control Path Activation:Range Path mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 119. LCAS configuation pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 120. LCAS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 121. LCAS Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 122. TP Frame Mode Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 123. Board View Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 124. After Navigate to Transmission view selection (example) . . . . . . . . . . . . . . . . . . . . . . .
Figure 125. View of Monitoring Operations (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 126. Navigate to HOA Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 127. Consulting EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 128. EPS Management dialogue box (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 129. EPS: board selection (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 130. EPS: choose protected (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 131. EPS functional state from protected active board view . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 132. EPS functional state from protecting active board view . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 133. Configure EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 134. EPS Management dialogue box (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 135. Switching EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 136. EPS Switch dialogue box (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 137. EPS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 138. EPS overview after Search (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 139. Subrack view after Open Subrack View command (example) . . . . . . . . . . . . . . . . . . .
Figure 140. Board view after Open Board View command (example) . . . . . . . . . . . . . . . . . . . . . . .
Figure 141. MSP Create Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 142. MSP Schema Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 143. MSP schema creation Port dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 144. TP Search (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 145. MSP 1+1 standard protection schema (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 146. MSP N:1 standard protection schema (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 147. MSP Management Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 148. MSP Management View (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 149. MSP Delete option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 150. MSP Schema Deletion (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 151. MSP Protection Status Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 152. MSP Commands option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 153. MSP Commands (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 154. MSP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 155. MSP overview after Search (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 156. Port view after Open Port View command (example) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 157. Symbols Used in Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 158. Transmission View Area (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
02
153
154
156
157
158
159
160
161
161
162
163
164
165
166
167
167
168
170
173
174
175
176
178
178
183
183
184
184
185
185
187
187
188
189
192
192
195
195
196
197
198
198
199
200
201
201
203
204
205
206
207
209
212
213
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
9 / 448
ED
02
216
217
218
218
219
219
220
220
221
222
224
224
225
225
226
227
228
230
230
231
232
234
237
238
238
239
242
244
245
248
251
252
255
256
259
260
262
262
263
264
264
265
265
270
273
275
279
282
282
284
286
287
288
290
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
10 / 448
ED
02
291
293
294
296
298
298
300
303
304
304
309
309
310
311
316
321
322
324
324
327
327
332
334
336
340
342
343
344
345
346
347
349
350
351
353
355
357
358
361
362
363
364
366
367
368
369
369
370
370
371
372
372
373
374
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
11 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
12 / 448
421
422
423
424
425
428
429
430
431
432
433
433
435
436
437
438
439
442
442
443
444
445
446
447
TABLES
Table 1. SDH NE alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. STMN port and AU4 concatenation supported by each equipment . . . . . . . . . . . . . . . . . .
Table 3. MSP commands and Autoswitch protection priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Default value for C2/V5 Signal Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5. Supported loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6. PDH TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7. SDH TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8. Optional and Mandatory Configurable Parameters for Cross-Connection Creation . . . . . .
Table 9. Modifiable Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 10. 1660SM Threshold table entities association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 11. 1640FOX and 1650SMC Threshold table entities association . . . . . . . . . . . . . . . . . . . . . . .
Table 12. Maximum Performance Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
148
205
228
243
261
261
280
289
337
337
341
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
13 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
14 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
1 INTRODUCTION
1.1 Scope
1.1.1 Document scope
The aim of this document is to help the operator understand, configure and manipulate Network Elements
(NEs) easily, using the Craft Terminal (CT). The different functionalities related to the equipment views,
the menu items and the different actions that can be undertaken from these views are described in detail.
Unless otherwise specified, the menu and the relevant description in the following
chapters are intended as applicable to all the three Network Elements (1640FOX,
1650SMC, 1660SM).
In many screen of this handbook the release number is not indicated, while it is instead
present in the real screen displayed to the operator.
This is due to the fact that the same screen is associated to the different releases.
Sometimes the release number reported is only for example.
The most part of the screen of this handbook are referred to 1660SM menu because it is
the equipment with the complete set of features, so it has been choosed like reference
example.
Anyway similar screen are presented for 1650SMC and 1640FOX so can be apply to
them, the same description of 1660SM .
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:
The documents of this Handbook that should be read before starting this document are:
Introduction manual
1.2 Terminology
1.2.1 Acronyms and abbreviations
Refer to the Section Introduction manual.
1.2.2 Glossary of terms
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
15 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
16 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
In this chapter the organization of the EMLUSM screen, presented after the NE login, is described.
First is introduced the view organization, than the accessible menu options are listed.
At the end some further advice are given for Navigation principles.
The Menu bar and the View area contained in the same NE view permits to performs all the configuration
and supervision and display the specific selected item.
The view organization is detailed in the Basic Craft Terminal Operator Handbook to which refer for the
description, except for the following information, that differs according the NE type:
Information about the alarms and status is given in the Maintenance section of this handbook.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
17 / 448
Severity alarms
synthesis
Menu bar
View title
LCA
View area
Message/state
area
Management
states control panel
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
18 / 448
Severity alarms
synthesis
Menu bar
View title
LCA
View area
Message/state
area
Management
states control panel
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
19 / 448
Severity alarms
synthesis
Menu bar
View title
LCA
View area
Message/state
area
Management
states control panel
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
20 / 448
The menu bar allows to perform configuration and supervision functions on the Network Element.
This paragraph list all the menu options and then more details on the relevant contained entries.
For each of them the relevant operative function are briefly introduced and it is referred the paragraphs
where it is detailed or the introduction to the options of each menu inserted in next paragraphs of this
chapter.
The flow charts from Figure 4. summarize the menu options.
From chapter 3 on details and operative information on the all the views are given. They are not presented
according the menu option sequence but according a functional subdivision.
In the menu bar there are permanent menu items always displayed. Staring from the left , the menus are:
Permanent Menus
Views
(first column).
Configuration
(second column).
To set general configuration of the NE, set TMN and OverHead parameters and to show or
modify some parameters (performance monitoring, ISA Port Configuration, MSP, EPS and
crossconnection).
Diagnosis
(third column).
To get information about the NE (alarms, performance monitoring, remote inventory, internal
link monitor).
Supervision
(fourth column).
MS_SPRing
(fifth column).
Download
(sixth column).
Help
(last column).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
21 / 448
Other Menus
Equipment
(eighth column).
To manage the NE as a whole, setting subracks and boards which compose it. From the
Equipment view the Board view can be accessed.
From the Equipment menu is also possible to start the Specific Terminal application for ISA port
traffic configuration.
Board
(eighth column).
To show the physical port available in a specific board. It is the entry point for the Port view.
Transmission
(seventh column).
It permits to show and set the Termination Point of the equipment, thus having an overview of
the complete signal flow of the various port.
The menu permits to define all the Cross Connections and manages the transmission
resources, setting the relevant configuration.
Further access the Performance Monitoring and permits navigation to the Board view.
It also permits to manage the MSP protection setting the relevant configuration.
Port
(seventh column).
To set and show (detailed alarm view) the transmission resources referred to the Port.
It also permits to manage the MSP protection setting the relevant configuration.
EPS
(seventh column).
Synchronization
(seventh column).
External Points
(seventh column).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
22 / 448
Further, in the menu bar there are other menus, presented as an alternative, only when a particular object
or option is selected.
Backward:
Forward:
Equipment:
External Points:
Transmission:
Synchronization:
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:
Close:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
23 / 448
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:
NE Time:
Display and set the NE local time. See para. 4.2 on page 51.
Performance:
EPS overview :
Loopback Management: Enter the loopback management. See para. 14.11 on page 242.
Used to configure the loopback command for commissioning or
maintenance purposes.
Comm/Routing:
ED
02
Local configuration
OS Configuration
Interfaces Configuration
LAPD Configuration
RAP Configuration
MESA Configuration
IP Configuration
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
24 / 448
Tunnelling Configuration
IP Over OSI
Overhead:
MSP overview :
PM overview
Port Mode
ISA port Configuration : It allows to create the TPs for the ISA connections.
See paragraph 20.2 on page 428.
Alarm Persistency Configuration: This feature has the aim to avoid transient alarm conditions.
See paragraph 4.3.6 on page 66
This menu permits to get information about the NE, by means of the following entries:
Alarms:
NE alarms
Object alarms
Subtree alarms
Equipment alarms
Transmission alarms
Log Browsing:
Manage the events stored in the NE. See para. 7.4 on page 85
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. See para 7.5.2 on page 87.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
25 / 448
Abnormal Condition list: Display the list of the object class (Loopback, ALS Handler, protection
board) and the name of the boards that are in abnormal condition.
See para 7.2 on page 81.
or
Not operative
Access State:
OS
Requested
Alarms:
Upload Remote Inventory:Store the Remote Inventory data in the Craft Terminal.
See para. 7.5.1 on page 86.
Restart NE:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
26 / 448
This menu permits to manage the NE software, by means of the following entries:
Init download:
Units info:
Show the status of the software package installed in the NE memory banks.
See para.21.5 on page 445.
Mib management: Permits backup of NE software configuration and restore of backupped file.
See para. 21.6 on page 447.
Set:
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)
See para. 9.2 on page 122.
Remove:
Set in service:
Insert a lock symbol in the board. See para. 9.4.1 on page 128.
Reset:
Not operative.
Software description:
Show information on the software of the board. See para. 9.5 on page 129.
Remote Inventory:
Subrack level
Board level
Used to define the ISA board IP address. See paragraph 8.14 on page 110.
N.B.
This option is available only at Subrack view level.
Show supporting equipment: Navigate to the upper equipment level. See para. 9.7 on page 132.
ISA navigate:
ED
02
Start the Specific Craft Terminal application for the ISA traffic
management configuration.
For details refer to the specific ISA board Operators Handbook.
N.B.
This option is available only after having selected an ISA board
at subrack level view.
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
27 / 448
This menu permits to show the physical port available in a specific board (alarm synthesis and port symbol)
and to access the port view, by means of the following entries:
Port Access:
Change the SPI or PPI object into PPI or SPI (and viceversa) on the
bimode port( 140Mbi/s/ STM1 switchable). See para. 10.2.2 on
page 137.
This option is not supported by 1640FOX.
Show supporting equipment: Navigate to the upper subrack level. See para. 10.2.3 on page 138.
ISA port Configuration: It allows to create the TPs for the ATM/PR_EA/ETH connections.
See paragraph 20.2 on page 428.
N.B.
This menu is available only if an ATM/PREA/ETH board
has been equipped in the subrack.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
28 / 448
TP configuration:
Set parameters for the Overhead (Signal Label and Path Trace) on
Synchronous TPs. See para 14.6 on page 227.
TP Threshold Configuration:
Set Retiming:
Enable
Disable
AU4 Concatenation:
Only for SDH ports views. See para. 11.6 on page 148.
Cross Connection:
Monitoring Operation:
Creation / Deletion
Configuration
Performance:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
29 / 448
Loopback:
MSP
Physical Media:
MSP Create
MSP Management
MSP Commands
MSP Delete
Manage the physical setting of the TP of the ports. Not applicable to HOA
port. See para.11.7 on page 151.
It opens a menu which differs according the port type:
SDH port:
ALS Management
TX Quality Configuration
LAPD Configuration
Ms Configuration
PDH port:
ETHERNET port:
LCAS Configuration
Navigate to Transmission view: permit to show a complete overview about the signal flow, opening
all TPs
See para.11.10 on page 174
Navigate to Monitoring view: permit to show for a selected TP the related POM/SUT/TCM and TCT
object if present.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
30 / 448
Management:
Configure:
Switch:
Add TP:
Search and add TP to the transmission view, than presented in the screen.
See para.14.5 on page 217.
Expand:
Display the TPs related to a selected TP. See para.14.13.1 on page 249.
It opens the following menu options:
All lower TP
All upper TP
Hide:
Lower TP
Upper TP
Selected TP
TP configuration:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
31 / 448
TP Threshold Configuration:
Terminate TP:
Disterminate TP:
AU4 Concatenation
Only for SDH ports views. See para. 11.6 on page 148.
Cross Connection:
Monitoring Operation:
Creation / deletion
Configuration
Performance:
Structure TPs:
Loopback
ED
02
Loopback management
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
32 / 448
Physical Media:
ALS Management
TX Quality Configuration
Extra traffic
Set Domain
MSP
MSP Create
MSP Management
MSP Commands
MSP Delete
NE MSP synthesis
This menu permits to set and show the Synchronization parameters and status, setting the relevant
configuration, by means of the following entries :
Timing Source Configuration: Set timing source priority and quality for the selected input reference.
See para.18.2.3 on page 361.
Protection Command:
T0 Configuration:
T4 Configuration:
SSU Configuration:
Transmitted SSM Quality Configuration: Set SSM quality transmitted on the selected T1 SDH
timing reference. See para.18.2.11 on page 375.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
33 / 448
Change T4<>T5:
Change 2MHz>2Mbit
This option is not supported by 1640FOX.
Change the source of a protection unit from 2Mhz (T3) to 2Mbit(T6)
and viceversa (see para. 18.2.9 on page 372).
Set T0 Equal T4
Remove T0 Equal T4
Configuration:
Display:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
34 / 448
Views
Backward
Forward
Equipment
A
F
Refer to Figure 7.
Refer to Figure 10.
External Points
Transmission
Refer to Figure 9.
Synchronization
Refresh
Open Object
Open in Window
Close
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
35 / 448
Configuration
Alarm Severities
Threshold table
Local Configuration
OS Configuration
NTP Server
Configuration
Interfaces
Configuration
EPS overview
Set ACD level
Cross Connection
Management
Loopback
Management
OSI Routing
Configuration
IP Configuration
Comm/Routing
LAPD Configuration
Ethernet
Configuration
RAP Configuration
MESA Configuration
IP Static Routing
Configuration
OSPF Area
Configuration
IP Address Config.
of PointtoPoint
interfaces
ISA board IP
address
Overhead
MSP overview
PM Overview
Tunneling
Configuration
OH Cross
Connection
OSI over IP
IP over OSI
Oh Phone
Parameters
Port Mode
OH TP Creation
ISA port
Configuration
Alarm Persistency
Configuration
OH TP Deleting
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
36 / 448
Supervision
Diagnosis
NE alarms
Object alarms
OS
Access State
Requested
Subtree alarms
Alarms
Equipment alarms
Resynchronize
Transmission alarms
External Points
alarms
Alarm Log
Log Browsing
Alarms
Allow Notifs
Inhibit Notifs
Upload Remote
Inventory
Set Manager list
Event Log
Restart NE
View
Abnormal
Condition List
Remote Inventory
Internal Link
Monitor
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
37 / 448
Refer to Figure 4.
A
MS_SPRing
Download
Equipment
Init download
Set
Units info
Modify
Mib
Management
Remove
Refer to Figure 8.
Set in service
Reset
Software
description
Subrack level
Remote Inventory
Board level
ISA Board IP
Address
Show supporting
equipment
ISA Navigate NB.3
Connect FAN to
CONGI#04 NB.1
Connect FAN to
CONGI#10 NB.2
Connect FAN to
CONGI#12 NB.2
Notes:
NB.1 avaialble only if CONGI board has been selected
in the 1650SMC Subrack level view
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
38 / 448
Refer to Figure 7.
Port
Board
Port Access
Change Physical
Interface
Show supporting
equipment
ISA port
Configuration
TP configuration
Port Mode
Configuration
Enable
Disable
TP Thresholds
configuration
Cross Connection
Management
TP Frame mode
configuration nb1
Create Cross
Connection
Modify Cross
Connection
AU4
Concatenation nb2
Set Retiming
Creation / deletion
nb1
Configuration
Cross
Connection
Monitoring
Operations
Configure
Performance
Monitoring
nb2
Display Current
Data
Display History
Data
Performance
Port Loopback
Configuration
Loopback
Loopback
management
MSP Create
MSP
MSP Management
MSP Commands
MSP Delete
Physical Media:
ALS
Management
Ethernet port
Configuration
Ethernet mapping
Protocol
ISA port
Configuration
Control Path
Activation
LCAS
Configuration
ALS
Management
Show Optical
Configuration
Tx Quality
Configuration
Single Fiber
Configuration
LAPD config.
Ms Configuration
Show supporting
board
Navigate to
Transmission view
Refer to Figure 9.
HDSL
Configuration
Navigate to
Monitoring view
Notes:
nb1: only for PDH port
nb2: only for SDH port
Line Lenght
Configuration
NT G703/G704
Configuration
Navigate to
HOA port
NT X21
Configuration
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
39 / 448
Next Level of
Lower TPs
Transmission
Next Level of
Upper TPs
Add TP
Refer to Figure 4.
Expand
Lower TPs
Upper TPs
Selected TPs
Hide
Port Mode
Configuration
Cross Connection
Management
TP configuration
Create Cross
Connections
TP Frame mode
configuration
Modify Cross
Connections
TP Threshold
Configuration
Terminate TP
Show Cross
Connected TPs
Disterninate TP
Creation / Deletion
Configuration
AU4 Concatenation
Cross Connection
Configure
Performance
Monitoring
Monitoring
Operations
Display Current
Data
Display History
Data
Performance
TU2
TU3
TU12
AU3
AU4
Structure TPs
VC3/VC4
VC12
Port Loopback
Configuration
Loopback
Loopback
management
Physical Media:
MSP Create
MSP Management
MSP Commands
MSP Delete
NE MSP synthesis
MSP
Show Supported
Boards
Navigate to
Port View
Refer to Figure 8.
ALS Management
Show Optical
Configuration
TX Quality
Configuration
Single Fiber
Configuration
Extra traffic
Regeneration
Section management
Line Lenght
Configuration
Set Domain
HDSL
Configuration
NT
Configuration
X21
Configuration
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
40 / 448
Refer to Figure 4.
E
Eps
Refer to Figure 4.
Refer to Figure 4.
Synchronization
External Points
Configuration
Management
Configure
Switch
Timing Source
Configuration
Display
Show External
Input Points
Protection
Command
Show External
Output Points
T0 Configuration
T4 Configuration
Show All
External Points
SSU Configuration
Transmitted
SSM Quality
Configuration
Frame Mode
Configuration
Remove Timing
Reference
Change
T4 <> T5
Change
2MHz > 2Mbit
Set T0 Equal T4
Remove
T0 Equal T4
Show Timing
Source
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
41 / 448
This general rules are described in the Basic Craft Terminal Operator Handbook.
In this paragraphs are instead inserted menu options typical for every NEs 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):
select the object and use the Open object or Open in Window option of the View pull down
menu
use the Menu option tree structure. The View pull down menu permits to show the following
menus:
Equipment
Transmission
Synchronization
External Points
The menu structure permits to open the same window following several menu paths.
EXAMPLE: to obtain the Create Cross Connection window:
The menu structure also permits to pass from a view menu to another (i.e. from port view toboard view
or to transmission view) thus facilitating the operators activity.
Depending on which object the mouse arrow is located, a related popup menu can be activated by means
of the right button of the mouse; this menu is correspondent to the possible actions that can be done on
the specific object of the view.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
42 / 448
Navigation rules are the same for all the NE using the same Craft Terminal Info Model.
Views Navigation
The first level of the Equipment view representation will be displayed directly into the current window,
immediately after the NE login. (See Figure 1. on page 18, Figure 2. on page 19 and Figure 3. on page
20).
The Equipment view enables a fast navigation through all levels of the equipment hierarchy.
Navigation is done from higher to lower levels.
The NEs hierarchy is different organized according to the equipment type, as follow:
the first level shows the subrack level of the Equipment view (see Figure 2. on page 19 and
Figure 3. on page 20);
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, see Figure 2. on page
19 and Figure 3. on page 20 ) the Show supporting equipment option from the
Equipment menu, the Rack level view is presented.
In the Rack Level view two subracks are presented:
at the top the Equipment Subrack (example SR60M for 1660SM or SR50C for
1650SMC)
at the bottom the Fans Subrack, named SRFAN.
The Fans Subrack presence is managed with the Set option as for the boards of the
Equipment Subrack (refer to paragraph 9.2 on page 122 for details)
Further, selecting in the Rack level view the Show supporting equipment option from the
Equipment menu, the Equipment level view is presented.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
43 / 448
1640FOX:
The navigation through different levels of the NE hierarchy is performed by double clicking on the
objects (see also para 9.1, on page 115):
the first level shows the Rack level of the Equipment view (see Figure 1. on page 18); two
subracks are presented:
by double clicking on a Subrack body, the relevant subrack level of the Equipment view can be
reached.
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 previous level of representation by pressing the <ESC> key on
the keyboard; or:
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 Views menu.
N.B.
ED
Selecting, in the first level of the Rack view (rack level, see Figure 1. on page 18 ), the Show
supporting equipment option from the Equipment menu, the Equipment level overview is
presented.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
44 / 448
3 NE MANAGEMENT SUPERVISION
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
45 / 448
The Network Element Synthesis views enable you to get access to the current NE EMLUSM view
described in this handbook.
The Network Element Synthesis views enable you to work on local or remote NE, selecting it and
activating Supervision and Show Equipment, as described in the Basic Craft Terminal Operators
Handbook.
The EMLUSM Main view is presented as for the following figures.
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
46 / 448
LCA
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
47 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
48 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
If the LAC is Denied that means the OS manages the NE and the CT is not allowed to modify NE
configuration (it can only read), the icon LCA has a cyan circular shape.
If the LAC is Requested! that means the CT has requested permission to the OS and is waiting for a
replay, the icon LCA has a blue circular shape.
However the OS does continue to provide a certain number of services. These services includes:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
49 / 448
Select the Supervision pull down menu. Then select the Requested option from the Access State
cascading menu as shown in the following figure.
Select the Supervision pull down menu. Then select the OS... option from the Access State
cascading menu in Figure 14.
From the confirmation dialogue box that opens you can confirm or cancel the OS access operation.
The NE is now managed by the OS.
N.B.
The key symbol icon on the management states of the NE view, indicates whether the NE is
managed by a Craft Terminal or by the OS.
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).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
50 / 448
The following dialogue box is opened from which you can get and/or set the local NE time and check the
NTP Status.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
51 / 448
NTP protocol
It can be enabled (in the NTP Server Configuration option at para 8.5 on page 98) or disabled
or empty (greyed).
If you do not want to set the NE local time, click on the Close push button to close the dialogue box.
To realign the NE time on the OS time basis click in the Set NE Time With OS Time radio button and either
click on the Apply push button to validate or on the Close push button to cancel and close the dialogue
box. The OS time comes from the PC date configuration which corresponds to the legal GMT time.
N.B.
ED
When the NTP is not present, the OS system realigns the time of all supervised NEs
periodically and automatically with a configured periodicity. This periodicity is common for all
the NEs.
If you set the NE time, you will force the change, with an immediate effect on the NE. However
it will not have any effect on the periodic and automatic mechanism.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
52 / 448
The operations described in this chapter, mainly related to alarm setting, are:
Select the Alarm Severities... option from the Configuration pull down menu.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
53 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
54 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Profile All Alarms. With this profile all the alarms are enabled (only Sfwr Download Failure
is not alarmed).
This ASAP enables the emission of all alarms.
Profile No Remote Alarmsshows the alarm criterion configuration defined for path alarms
(only AIS and RDI and Sfwr Download Failure are not alarmed)
This ASAP enables the emission of all:
Communication Alarms (i.e. the AIS & RDI alarms are not alarmed)
Equipment alarms
Environmental
Error Processing (i.e. Sfwr Download Failure is not alarmed)
Profile Primary alarms. With this profile the AIS, Battery Degraded, Sfwr 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
Error Processing (i.e. Sfwr Download Failure is not alarmed)
Another Profile #10002 can be created by the user, as explained for the #10001; the profile
identifier is incremented automatically.
For ASAP 10001 and 10002 is then possible to choose Detail, Modify, Clone or Delete buttons.
For ASAP No Alarms , Primary alarms, No Remote Alarms and All Alarms it is only possible to
choose Detail, or Clone buttons.
Clone selection can be used to create new ASAP.
By selecting an ASAP and clicking on Detail, Modify, or Clone button, the following ASAP edition dialogue
box is displayed.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
55 / 448
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
56 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
57 / 448
Choose Scope
Network element
The new ASAP is applied to all objects of the NE matching the criteria specified in Choose Classes
and Choose current ASAP.
Since this application process takes some time, its progress is shown in the Section Execution
Monitoring.
This is the default if no object is selected in the view.
Due to system architecture, AU4 CTPs are no subordinates of MSTTPs. Therefore, if the
AU4 CTP should be included as subordinate, select the related OSTTP (OpS) or ESTTP
(ElS) as main object.
Choose Class(es)
Enabled if one of the scopes Network element or Selected object and subordinates is selected.
All classes
Specific class(es)
Select one or more object classes the new ASAP shall be applied to.
Press Ok to confirm the ASAP assignment and close the dialog. Press Cancel to close the dialog and
discard any changes.
The TP list.... button let the operator to search for resources assigned to a specific ASAP and to change
ASAP on multiple object istances; for detail concerning the clipboard refer to paragraph 4.3.2.3 on page
59.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
58 / 448
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:
Note:
Clipboard dialog is not called directly from a view menu entry . It is started as subdialog from
another dialog using the TP List button.
In principle, every dialog supporting clipboard can be the starting point to obtain a list of
resources assigned to an ASAP .
Use the Clipboard dialog to perform the same action, e.g. PM configuration, on a number of objects (TPs
or equipment) in one step.
Clipboard layout is depicted in Figure 21. on page 59.
The buttons on the right side of the dialog are used to create a list of objects:
Add Tp Opens the TP Search dialog in which the user selects the TPs to be configured. The selected
TPs are added to the clipboard list.
Add EQP Opens the Equipment Filter dialog in which the user selects the equipment to be
configured. The selected equipment is added to the clipboard list.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
59 / 448
Load/Save Opens the User Preference dialog where a preference set can be loaded or saved. If a
preference set has been loaded, the name of this set is displayed on the lower left side of the dialog.
Print The Print dialog opens and the user selects the print destination and print format.
Start Starts the action process on the listed objects. The semantics of the action is defined in the
calling dialog. After starting, an information window opens to cancel the action during its progress.
Click on Ok to cancel the process.
Continue Continues an action performed on the clipboard which was previously cancelled.
Clipboard dialog starts an improved version of TP search dialog (Figure 22. on page 60 ) (with support
for ASAP management and Performance Monitoring/Monitoring operations as well) using the AddTP...
button.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
60 / 448
Add Eqp... button in clipboard starts the EqpSearch dialog with support for ASAP filtering Figure 23.
The use case to search for ASAP assigned resources (both TPs and Eqp resources) could be summarized
in the following steps:
In TP search use the ASAP filter to search for TPs using the selected ASAP.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
61 / 448
From the clipboard dialog ask for Equipment objects using the Add Eqp... button
In Eqp Search dialog use the ASAP filter to search for equipment objects using the selected ASAP.
The content of clipboard is the list of resources assigned to a specific ASAP. It is possible to change
the ASAP for this list of objects (since the first operation was the invoke of ASAP Enhanced dialog),
to select the object instance to move toward a view (according to the object instance type), to
load/save this object instance list and to Print it.
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
62 / 448
1640FOX
1650SMC
1660SM
FF (not used)
FF
FF
ABF
ABF
CFF
BKF
SHD
SHD
SHD
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
63 / 448
l)
N.B.
Inhibiting the alarms notification means that they are not forwarded to the CT but alarms
are still generated by the NE.
From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok
or Cancel push buttons respectively.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
64 / 448
The system provides the possibility to allow/inhibit the spontaneous incoming alarm notifications.
N.B.
ED
This functionality has to be used only if there is any perturbation. Never use this operation during
a correct behavior.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
65 / 448
This feature has the aim to avoid transient alarm conditions on 2Mbit/s signals. To get this goal the network
element perform a persistency check on the fault causes, before declaring a failure. Once the failure is
declared, it shall be cleared if the fault cause is absent continiously for a persistency time.
Select the Alarm Persistency Configuration option from the Configuration pull down menu.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
66 / 448
4.4 Restart NE
The restart operation is a software reset and can be executed in normal traffic conditions.
The restart operation in any case activates the Commit (active) version.
Select the Restart NE option from the Supervision cascading menu.
The following dialogue box is opened.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
67 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
68 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
5 SECURITY MANAGEMENT
In this chapter are inserted setting options referred to the SECurity management:
Manager list: each connected manager to the NE is highlighted in the list. The user can set a
manager clicking on the denomination.
Several manager can be enabled contemporaneously, having in charge the NE.
The Manager List contains the list of managers ( i.e. RM, SY, NPOS , EML) that work on the NE.
The EMLUSM administrator (SH or Craft Terminal) should set the Manager List only to remove a
manager in case of emergency (i.e. the Manager misses the NE connection).
NE Domain field allow to select the domain among that displayed in the list, assigning it to the NE.
The different domains could be assigned to different operators.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
69 / 448
The ACD manage the concurrence of access among several different managers (i,e. RM and EML).
This only acts on the functions that can be used by different manager.
Select the Set ACD level option from the Configuration pull down menu.
The dialogbox contains the following fields:
Port Level
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
70 / 448
This option allows the user to select the level of the Access Control Domain.
This chapter describes how to display and set the input/output environmental alarm (housekeeping alarm),
An external input point is an environmental alarm (also called housekeeping alarm). It corresponds to an
external event which is monitored by the NE. Number of relays on the NE are dedicated to check
modification of the environment as for example a fire, a flood ...
An external output point is used to manage a NE contact (i.e relay) connected to detector. An external
output point is independent from external input point.
The operations that can be undertaken in this section are:
Note: the max. number of External Points depends by the equipment type (1640FOX, 1650SMC,
1660SM) and board type were applicable ( example CONGI 3 Wire or CONGI 2 Wire boards equipped
in 1650SMC and 1660SM); for details refer to the relevant Technical Handbook.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
71 / 448
Select the External Points option from the Views pull down menu as shown in the following figure.
After selecting this menu option the external points view is displayed into the current window instead of
the current view.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
72 / 448
LCA
Only for the Output external point there is the following information:
ED
the Output criteria: if configurated, display the alarm event and the board affected associated to the
Output point (see further the paragraph External points configuration).
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
73 / 448
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
74 / 448
To configure an external point, click on the concerned row of Figure 34. on page 73 and then select the
Configuration option from the External Points pull down menu as shown in the following figure.
The following dialogue boxes are then opened, displaying information about the selected external point
(Input or Output).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
75 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
76 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Opening the dialog the current state of the selected External Point is shown.
[1]
[2]
Type: In the field the name of the involved Input point is displayed (e.g. ExtP#8 in Figure 37. )
User Label: this field can be filled by the user with a Label that indicate the associated event
that must be taken under check (for example presences of water or fire in the room where the
Equipment is placed)
External State: this field is set to off and cant be changed by the operator
Probable Cause: this field is set to housekeeping and cant be changed by the operator
Type: In the field the name of the involved Output point is displayed (e.g. ExtP#8 in Figure 38. )
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 to drain water
from the room where the equipment is placed ; in this case is also necessary to set the
option On in the field External State.
Flexible. It is possible to define from CT the couple event/CPO#, where the event is
chosen between a set of Output Criteria (LOS, RDI and LOF) and specifies the STMN
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
77 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
78 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
7 DIAGNOSIS MANAGEMENT
Alarms are always present on the operators workspace. The different types of alarms, their number and their
severity level, are represented in all Equipment views (NE views, Board views and Port views). An icon
representation is used, which change color when the relevant alarm is active. Thus, at all times, you know the
number of alarms and their severity relating to the equipment.
Access to the Alarm Surveillance to show the alarm condition is detailed in the following paragraph.
Than is presented the abnormal condition list (as result of operators command such us loop, laser forced
on etc.).
At the end the Event log access is introduced.
Information about the significance of equipment alarms and status is given in the Maintenance
section of this handbook.
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
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
79 / 448
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).
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
80 / 448
Selecting any of the previously seen options, the Alarm surveillance report is displayed as for the example
of the following figure.
ED
Loopback
Protection units (in case of EPS, SNCP and MSP ) are in lockout or in forced status
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
81 / 448
Select an abnormal condition and click on OK to open the relative dialog window. Figure 44. on page
82 is opened.
The other abnormal condition types will open the corrisponding management window or will open the
window to navigate towards the management window.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
82 / 448
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 the
status of the link among the active and standby MATRIX is shown.
Select the Internal Link Monitor option of the Diagnosis menu.
As shown in Figure 45. on page 84 the first page displays the link status for the main MATRIX, the second
one concern the spare MATRIX.
In detail, each page contains the following functional blocks and graphical objects:
the tab of the page displays the user label of the MATRIX board;
the left side of the page displays the block representing the MATRIX board;
the right side of the page displays the list of blocks representing the equipped boards; each
block displays a string contained the user label of the associated board;
two arrows are displayed between the MATRIX block and each board block; the two arrows
represent the link status in Rx and Tx side:
the Refresh button allows to perform 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 is represented by a red block if a link problem is detected in the NGI Rx from the
active MATRIX;
the MATRIX is represented by a red block if a link problem is detected in one of the NGI Tx from
one of the possible port board.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
83 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
84 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
In the Diagnosis pulldown menu, select the Log Browsing option. The following options are
proposed:
Select the Alarm Log option (Log Id # 1 ) to access the Event Log file.
The Configuration and Log Browsing ELB Windows open, permitting to analyze all alarms
stored in the NE.
Refer to the ELB Operators Handbook
Select the Event Log option (Log Id # 2 ) to access the Event Log file.
The Configuration and Log Browsing ELB Windows open, permitting to analyze all events
stored in the NE.
Refer to the ELB Operators Handbook
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
85 / 448
This paragraph describes the access to the remote inventory of this NE.
In the Remote Inventory are stored information of identification, construction data ect.
The options used are:
Upload Remote Inventory: store the Remote Inventory data in the Craft Terminal.
View Remote Inventory: display the remote inventory data, previously stored in the Craft Terminal
by means the upload remote inventory performed in the Supervision menu.
Remote Inventory option of the Equipment menu is instead presented in para. 9.6 on page 130.
7.5.1 Upload remote Inventory
This command stores the Remote Inventory data in the Craft Terminal.
Select the Upload Remote Inventory option of the Supervision pull down menu.
The following confirmation dialog box is opened.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
86 / 448
ED
Company
It indicates the Companys (Alcatels branch) which designs the unit.
Refer to Alcatel for the abbreviations meaning (four characters).
Unit Type
It indicates the units acronym
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
87 / 448
CLEI Code
It indicates the CLEI code according to Bellecore specs. TRISD325
Manufacturing plant
It indicates the Companys manufacturing plant id. within the company, producing the unit.
Refer to Alcatel for the abbreviations meaning (four characters).
Serial Number
It indicates the products serial number as specified by the NR 130 Norm.
Date identifier
It indicates the meaning of the date that follow.
It is a twodigit code supplying the following information:
00
01
02
03
04
ED
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
88 / 448
nodes supporting a link state routing protocol ISIS; these nodes will be called adaptive
routers; ISIS protocol floods the network with link state information in order to build a complete
consistent picture of the network topology. Use of ISIS routing protocol in a TMN facilitates
installation and operation due to the self learning capabilities of these protocols and automatic
network reconfiguration in case of failure; moreover the use of these standardized routing
protocols guarantees interoperability in a multivendor environment.
nodes not supporting these protocols; these nodes will be called static routers;
Networks partitions consisting of the former type of node will be called adaptive routing domains;
networks partitions consisting of the later type of node will be called static routing domains.
Moreover, a node which have to take routing decisions must became Intermediate Systems, all others
can be made End Systems
For the description of the following paragraphs use is made of Figure 50. on page 90. It is not a network
planning example, it is only used to describe L1 ,L2, RAP and MESA.
8.1.1.1 OSI Partitioning into Routing Subdomains
In order to reduce the overhead associated with distributed adaptive routing, it may be useful to divide
a adaptive routing domain into smaller routing subdomains, called areas or level 1 subdomain. A level
1 subdomain should fulfill the following requirements:
a level 1 subdomain should form a connected subnetwork; this subnetwork should have only
a few links to the outside world, compared with the number of internal links;
each node must belong to exactly one level 1 subdomain;
each node which is connected to a foreign level 1 subdomain must become a level 2
intermediate system; level 1 intermediate systems know how to communicate only with IS
in the same area; obviously, there must be at least one level 2 intermediate system per level
1 subdomain;
Level 2 intermediate systems must form a connected network, because level 1 paths cannot
be utilized for level 2 communication. This network will be called level 2 backbone.
In the most simple case, all nodes within a level 1 subdomain share the same area address.
In general it is allowed to have multiple synonymous area addresses within a level 1 subdomain even if
the usage of this features should be checked with Alcatel engineers.
The synonymous list is used to ease partitioning in the future. There is a basic rule, which must be followed
by two neighboring level 1 intermediate systems within a subdomain: there must be at least one area
address in common between their two synonymous list, otherwise they are not able to communicate with
each other.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
89 / 448
In certain situations it may be necessary to partition a given network into separate routing domains, where
no routing information is exchanged between these domains. The major benefits of this partitioning are
reduction of memory, processing and traffic overhead, because there is no exchange of routing
information between the domains. Communication between separate routing domains must be achieved
through the use of Reachable Address Prefixes (RAP).
A Reachable Address Prefixes represents static routing information. It can only be associated with a link
of a level 2 intermediate system, whereby this link crosses routing domain boundaries. A Reachable
Address Prefixes is handled in the same way as information about a foreign level 1 subdomain within the
own domain. The Reachable Address Prefixes indicates that any packet whose destination network
address NSAP matches the prefix may be forwarded via the link with witch the prefix is associated.
For example, consider network which is split into two separate routing domains:
L1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L2
L2
L1 with MESA
L1
L2
AREA (subdomain) 2
L2
L2
L1
L1
with RAP
= NE
L2
L1
L1 with MESA
L1
AREA (subdomain) 3
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
90 / 448
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 get the NE through a pure IP network, the GNE has to strip off the IP encapsulation,
extracting the OSI packet, and to route the OSI packet as it does today using a pure OSI networking.
Hence, the internal networking of the SDH network (DCCs) is still based on OSI. No IP packets shall flow
inside DCCs, because the GNE receives the IP packet containing the OSI packet, deletes the IP header,
and forwards only the OSI packet on DCCs.
The default OSI lower layers networking can be replaced by IP routing capability at the bottom of the
QB3/QECC communication protocol suite; the choice is software switchable at NE level. The
implementation adopts the RFC1006 standard to put the OSI upper layers on top of IP networking.
The application goal is to offer the TCP/IP transport (i.e. Internet compatibility) in alternative to the full
ISO/OSI communication protocols, in the complete DCN network or at least in a consistent portion of it.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
91 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
92 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Local Configuration:
OS Configuration:
NTP Server Configuration:addressing of the main and spare NTP servers connected to the local NE
LAPD Configuration:
Ethernet Configuration:
RAP Configuration:
MESA Configuration:
IP over OSI:
All the previously cited operation can be entered choosing the relevant option of the menu, as shown in
the Figure 52.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
93 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
94 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
a Presentation Selector (P.Sel) identifies a presentation entity at the location identified by the
NSAP Address. The presented value must not be modified.
a Section Selector (S. Selector) identifies a section entity at the location identified by the NSAP
Address. The presented value must not be modified.
a Transport Selector (T. Sel) identifies a transport entity at the location identified by the NSAP
Address. The presented value must not be modified.
a Network Service Access Point (NSAP) Address identifies a location in the network. The first
field of the NSAP address, AFI, determines the NSAP format.
The AFI filed is 2 characters long (2 exadecimal digits) and, depending on the its value, the
length of NSAP address is variable from 16 characters to 40 characters:
the value of AFI 49 identifies the local format of variable length (from 16 characters to 40
characters).
Network Selector: provides the distinction among users of the network service and is 2
characters long (value is 1d).
In the view, the NSAP is managed as simple strings of characters without any preformatting
because of the variable format:
a second string of variable length that identifies the remaining NSAP address
Synonymous Area Addresses section allows to have multiple synonymous area addresses within a
level 1 subdomain. The compilation of the two network addresses is optional and if they are inserted,
the last two fields, System Id and Network Selector, of the mandatory address and of the synonymous
addresses must be the same.
System Type section determines whether the local NE acts as a intermediate system level 1 or as
a intermediate system level 2 or as a End System. Note that a level 2 intermediate system
performs functions of a level 1 too. End System is not operative.
Ok button is used to perform a configuration change of the data contained in the dialogbox and closes
it; the dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
95 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
96 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
8.4 OS Configuration
Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading
menu the OS Configuration option.
The dialogbox opens (Figure 54. ) and allows to configure the addresses of the Main and Spare OSs
connected to the local NE.
The following fields are present:
Main OS Address section contains the same graphical object of the Local Address Section in the
Local Configuration dialogbox.
Spare OS Address section contains the same graphical object of the Local Address Section in the
Local Configuration dialogbox.
Ok button is used to perform a configuration change of the data contained in the dialogbox and closes
it; the dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
97 / 448
Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading
menu the NTP Server Configuration option.
The dialogbox opens (Figure 55. ) and allows to configure the addresses of the Main and Spare NTP
(Network Protocol synchronization Time) Servers connected to the local NE, used for time distribution in
the network.
The following fields are present:
Enabling NTP Protocol section allows to enable or disable the NTP Protocol.
Main NTP Server Address section contains the same graphical object of the Local Address Section
in the Local Configuration dialogbox.
Spare NTP Server Address section contains the same graphical object of the Local Address Section
in the Local Configuration dialogbox.
If the NTP server is coincident with the OS (same hardware), the same NSAP address of the OS must be
assigned.
Ok button is used to perform a configuration change of the data contained in the dialogbox and closes
it; the dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
98 / 448
the user label of the TTP containing the configured LAPD Interface (MS/RS TTP);
User
(one end of the link)
Network
(the other end of the link)
Delete button that allows to delete the LAPD Interface selected in the LAPD table;
Change Role button that allows to change the role (User or Network) of the LAPD Interface
selected in the table (after selection the Figure 58. on page 101 is shown to confirm action
required);
Create button that allows to create a new LAPD Interface; this button starts a new dialog (see
Figure 57. on page 101) 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 section named Search Criteria that allows the user to display only the LAPDs of the selected type
in the LAPD Table; the section contains the following graphical objects:
the field Interface Type that allows to select the type of the LAPDs 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.
ED
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
i.e. RSTTP or MSTTP;
a section LAPD Role that allows to configure the role (User or Network) of the LAPD
Interface to be created.
This connection is a must to establish endtoend connection between two NEs: if one
end is configured with User role, the other end connected must be configured with Network
role.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
99 / 448
The LAPD Interface List will be updated on reception of the Delete/Create/Change DCC CTP
notification. If no LAPD Interface are configured in the equipment, the message No LAPD Interface
will be displayed near LAPD Interface counter (that it is at zero).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
100 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
101 / 448
Select the Configuration pull down menu. Select the Comm/Routing > Interfaces Configuration
option and then from the cascading menu the Ethernet Configuration option.
The dialogbox opens (Figure 59. ) and allows to define the parameters needed to manage a NE which
provides a LAN ethernet interface .
The following fields and data are present:
Ethernet Interface field allows to define or remove a Local Area Network Port for the access to the
Data Communication Network.
MAC Address section allows to display the address of the Network Element in the Ethernet LAN;
it is a readonly field.
OSI Section:
L2 only Parameter field indicates if the port shall be used for level 2 traffic only, thus avoiding
transmitting L1 packets. Note that the flag shall be set to No if some other nodes (NEs or OSs)
of the same area of the relevant NE are connected to the Ethernet.
One example is indicated in Figure 60. on page 103.
L1 Default Metric is a not modifiable field , Priority field can be set ( default value for ethernet
is 64)
L2 Default Metric is a not modifiable field , Priority field can be set ( default value for ethernet
is 64)
IP Section section allows to define the node IP Address, IP Mask and the Routing IP Protocol used;
If OSPF or Both options of Routing IP Protocol field are selected, also the Associated OSPF
Area must be set.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
102 / 448
AREA 1
AREA 2
OS
LAN
L2
NE
No
ED
02
L2
NE
No
L2
AREA 3
NE
Yes
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
103 / 448
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 dialogbox opens (Figure 61. ) and allows to configure the Reachable Address Prefix table.
Each element of the RAP table allows to link a LAPD port or a LAN port of the local NE to a separate
domain; the separate domain is selected by the address Prefixes. If the addressed element is the OS, the
LAN port will be used.
The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing
device (upper part of the figure); each page represents a particular element of the RAP table and the
respective pointing device displays the element counter.
In detail, each page contains the following data:
if the element is empty, displays the none value and allows to select a LAPD ports or a LAN
port which will be used to reach the addressed area.
if the element isnt empty, displays the selected port and allows to change it.
Area Address Prefix section allows the user to address the separate domain. The Area Address
Prefix represents a NSAP address without the fields System Id and Network Selector.
MAC Address section allows to address the element of a domain to be reached the Ethernet LAN;
the field is managed as a simple strings of 12 digit.
Apply button is used to perform a configuration change of the data contained in the complete RAP table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Close button close the dialog without changes of the data.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
104 / 448
if the element is empty, displays the none value and allows to select a LAPD ports or a LAN
port which will be used to reach the End System element.
if the element isnt empty, displays the selected port and allows to change it.
MAC Address section allows to address the element in the Ethernet LAN; the field is managed as
a simple strings of 12 digit.
Apply button is used to perform a configuration change of the data contained in the complete MESA table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Close button close the dialog without changes of the data.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
105 / 448
The options listed in the menu Configuration > Comm/Routing > IP Configuration and also in
Configuration > Comm/Routing > Tunneling Configuration are relevant to the configuration of
messages communications for the management of ATM or PR_EA boards (ISA) inside the equipment and
in the network.
8.10.1 IP routing configuration for ISA boards management
In order to manage the ISA boards (excepted ETHERNET and PR boards) inserted into the equipment,
the following operations are to be done:
ED
IP Address Configuration of PointtoPoint Interface (see para 8.13 page 109), defines
the IP address for the EquipmentController (EC). This should be the first addressing operation
IP Static Routing Configuration (see para 8.11 page 107), if using static routing
OSPF Area Configuration (see para 8.12 page 108), if using the automatic OSPF
routing
ISA Board IP Address (see para. 8.14 page 110), it defines the IP address for the ISA boards;
it is to be defined for every ISA board hosted by the equipment.
NOTE: if the ISA boards are in EPS 1+1 configuration (not applicable to 1640FOX), they must
have the same address)
IP over OSI Tunneling (see para. 8.16 page 112), it defines the OSI address (NSAP) of the
destination node to be reached (for instance the GNE connected to the TMN), when the ATM/IP
management message passes through an SDH/OSI network; i.e. it is to be done for every
SDHNE of the network, if equipped with ISA 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 (not applicable to 1640FOX), 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.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
106 / 448
8.10 IP Configuration
Destination Host IP Address: allows to define the IP address necessary to reach a specific Host
[2]
Destination Network:
[3]
Default Gateway IP Address: allows to define the address of the next hop gateway
[4]
CLNP (Connection Less Network Protocol): allows to use a predefine IP over OSI tunnel towards
a gateway. The information in the field is automatically
assigned after the execution of the option IP over OSI
Tunneling (see para. 8.16 page 112).
[5]
IP PointtoPoint Interface Id: allows to use point to point interfaces made available by EC
N.B.
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
107 / 448
Select the Configuration pull down menu. Select the Comm/Routing>IP Configuration and then from
the cascading menu, the OSPF Area Table Configuration option.
The dialogbox opens (Figure 64. ) and allows to configure the parameters for OSPF (Open Shortest Path
First) Area Table Configuration , i.e. it is used in an IP network in automatic, dynamic OSPF routing
configuration. More area addresses may be set; in this case new pages are created by the system.
The following fields and data are present:
OSPF Area IP Address: it is the address of the area containing the equipment
Both fields gives a synthetical information that includes all the addresses (specific to a NE and to a
Network) in an Area.
Apply button is used to perform a configuration change of the data contained in the complete RAP table
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
108 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
109 / 448
Select an ISA board of the equipment and then the Configuration pull down menu. Select the
Comm/Routing>IP Configuration and then from the cascading menu, the ISA Board IP Address
option.
The dialogbox opens (Figure 66. ) and allows to set the IP Address of the ISA Board that communicate
with the Equipment Controller (EC).
Ok button is used to perform a configuration change of the data contained in the dialogbox and closes
it; the dialog is visible until the end of the operations and a wait cursor is displayed.
Cancel button close the dialog without changes of the data.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
110 / 448
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
111 / 448
Select the Configuration pull down menu. Select the Comm/Routing>Tunneling Configuration and
then from the cascading menu, the IP over OSI option.
The dialogbox opens (Figure 68. ) and allows to configure the Destination NSAP Address and the IP
Routing Type; i.e. it permits the TMN to reach the ATM/IP boards inserted into the SDH/OSI network . More
tunneling channels may be created, in these cases new pages are created by the system.
The following fields are present:
the value of AFI 49 identifies the local format of variable length (from 16 characters to 40
characters).
Network Selector: provides the distinction among users of the network service and is 2
characters long (value is 1d).
In the view, the NSAP is managed as simple strings of characters without any preformatting
because of the variable format:
a second string of variable length that identifies the remaining NSAP address
OSPF (Open Shortest Path First) , if the OSPF Area Configuration option has been used
(see para 8.12 page 108)
Both
None, if the option IP Static Routing Configuration (see para 8.11 page 107) has been
used
If OSPF or Both options are selected, also the Associated OSPF Area must be set (it is to
be chosen among the presented options); in this case the information field is automatically filled
with the addresses set in the OSPF Area Configuration application.
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
112 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
113 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
114 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
9 EQUIPMENT MANAGEMENT
9.1 Introduction and navigation
This section deals mainly with the setting and changing of the boards present on the Equipment and
undertaking board protection operations.
Using the menu options, select the Equipment option from the View pull down menu
The first level of the Equipment Overview representation will be displayed directly into the current window
(see the following figures).The Equipment Overview enables a fast navigation through all levels of the
equipment hierarchy. Navigation is done from higher to lower levels.
The NEs hierarchy is different organized according to the equipment type, as follow:
the first level shows the subrack level of the Equipment view (see Figure 69. on page 117);
by double clicking on a board body , the board level of the Equipment view can be reached (as
described in chapter 10 on page 133).
further, by double clicking on a port body contained in the board, the port level of the Equipment
view can be reached (as described in chapter 11 on page 139). 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, see Figure 69. on page
117 ) the Show supporting equipment option from the Equipment menu, the Rack level
view of Figure 70. is presented.
In the Rack Level view two subracks are presented:
at the top the Equipment Subrack (example SR60M for 1660SM or SR50C for
1650SMC)
at the bottom the Fans Subrack, named SRFAN.
The Fans Subrack presence is managed with the Set option as for the boards of the
Equipment Subrack (refer to paragraph 9.2 on page 122 for details)
Further, selecting in the Rack level view the Show supporting equipment option from the
Equipment menu, the Equipment level view of Figure 71. is presented.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
115 / 448
1640FOX:
The navigation through different levels of the NE hierarchy is performed by double clicking on the
objects (see also para 9.1, on page 115):
the first level shows the Rack level of the Equipment view (see Figure 72. on page 119); two
subracks are presented:
by double clicking on a Subrack body, the relevant subrack level of the Equipment view can be
reached (see Figure 73. on page 120).
by double clicking on a board body, the board level of the Equipment view can be reached (as
described in chapter 10 on page 133).
further, by double clicking on a port body contained in the board, the port level of the Equipment
view can be reached (as described in chapter 11 on page 139). The port view displays the inner
TPs.
it is possible to go back to the previous level of representation by pressing the <ESC> key on
the keyboard; or:
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 Views menu.
N.B.
ED
Selecting, in the first level of the Rack view (rack level ), the Show supporting equipment
option from the Equipment menu, the Equipment level overview is presented (see Figure 74.
on page 120).
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
116 / 448
LCA
1650SMC
LCA
1660SM
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
117 / 448
LCA
LCA
SRFAN
SR60M
LCA
LCA
SRFAN
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
118 / 448
SR50C
LCA
LCA
1650SMC
1660SM
LCA
1640FOX
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
119 / 448
1640FOX
ED
02
3AL 91670 AA AA
448
LCA
LCA
1640FOX
SC.3:NE MANAGEMENT
120 / 448
The equipment management is achieved by using the options offered by the Equipment menu (see
Figure 75. page 121).
Alarms indications are present at every NE level.
Details about these alarms indications are given in the Maintenance section.
All the options offered by equipment menu are described in the next paragraphs.
The main functions are the setting and changing of the boards on the Equipment.
Boards administrative state settings, that decide about the in/out of service of the boards is also
described.
remove a board
Delete all the underlying traffic, connections, services, etc. concerning the board
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
121 / 448
a)
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 Outofservice 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 (see next para. 9.4 on page 128 for in /out of service info).
The contour becomes highlighted to show that operations can be done on it.
Select the the Set option of the Equipment pull down menu of Figure 75. on page 121.
The following example of dialogue box containing a list of the different types of boards/subrack/
access card and modules is displayed.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
122 / 448
The boards can be set, changed or removed using the menu options of the Equipment view.
BOARDS LIST
SUBRACK LIST
MODULES LIST
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
123 / 448
b)
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 76.
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 (inservice, see next para. 9.4 on page 128)
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.
Removing a board/subrack/modules
NOTE: the Remove action is not possible in the case that, on the considered board, is still existing any
operation/connection/termination on the underlying supported signals, such as:
Loopbacks
Auxiliary channels
Click on the board/subrack to remove (Out of Service board/subrack, as for next para. 9.4 on
page 128).
The outline of the slot becomes highlighted. This indicates that the board is selected and that
operations can be done on the slot.
ED
If the slot you are working on is already empty no name appears under the slot.
Select the Remove option the Equipment pull down menu of Figure 75. on page 121.
From the confirmation dialogue box that opens you can confirm or cancel the Remove operation.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
124 / 448
NOTE: The list of boards/subrack displayed during a Set operation is restricted to those which the
equipment may accept in the selected slot. Therefore the list will vary depending on which slot has
been selected.
For details on the board/subrack identified by acronyms and NE physical composition please refers
to the Technical Handbook.
c)
Modify a board
NOTE: this procedure can be done to replace an existing unit with a similar one of different version,
without previously remove it. In other words: it is possible when changing only the version of the
board, not the type.
Click on the optical module to replace. The outline of the slot becomes highlighted to show that
operation can be done on it.
Select the Modify option of the Equipment pull down menu of Figure 75. on page 121 .
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
125 / 448
This command enable the Fan Subrack alarms management by means of a connection to a CONGI board.
The option menu is different according to the equipment type (1650SMC or 1660SM) as explained in the
following table:
Equipment Type
Options available
1650SMC
1660SM
Figure 77. shows an example of connection for 1660SM equipment; the description that follows can be
apply also to 1650SMC taking into account that the option to be chosen is Connect Fan to CONGI#5.
Select the CONGI board
To enable this function select the option (Connect Fan to CONGI#10 ) of the Equipment menu
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
126 / 448
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
127 / 448
N.B.
In the equipment view, a lock representation appears over the boards which are in in service
state.
LCA
Administrative
State Information
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
128 / 448
The operator decides to set a board in service or out of service, if it is allowed by the NE.
Click on a board in which the software is wanted to know (EQUICO or MATRIX unit for 1660SM,
SYNTH unit for 1650SMC and 1640FOX). The outline of the slot becomes highlighted. This
indicates that the board is selected and that operations can be done on the slot.
Select the Software description option of the Equipment pull down menu of Figure 75. on page
121.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
129 / 448
This command displays the remote inventory data present in the Subrack and Boards.
Select the Remote Inventory option of the Equipment pull down menu.
Two options are available (see the following figure):
Subrack level: prints or write on a file the remote inventory data of the subrack.
Board level: show the remote inventory data of the selected board
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
130 / 448
The remote inventory data of the Subrack level can be printed on the default printer ( Figure 82. ) or to a
file in postscript or ASCII format ( Figure 83. ).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
131 / 448
Click on Show Supporting Equipment menu option of the Equipment menu to navigate to the
equipment that supports the selected board.
Figure 84. (example) opens.
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
132 / 448
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 containing subboards, another view permits to see the contained item, named
daughter or subboard (see example of Figure 85. )
An example of daughter with the presented port is in Figure 86. It is displayed after clicking on it.
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.
LCA
daughters
Administrative state
Board Alarms/Status
Figure 85. Equipment view: select the SDH port on a board (example)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
133 / 448
LCA
(SDH)
(ISA)
(PDH)
(GBit ETHERNET)
(ISAES)
The operator is provided with a representation of the port alarm synthesis on each port.
The messages displayed at the top view provide port denomination.
The messages displayed at the bottom provide information about Board alarms.
A message under the mouse facility provides the name and the port type or the alarms name. A message
appears in the message area in the bottom left corner of the view.
By double clicking on a board view, it is also possible open the corresponding port view (see chapter 11
on page 139).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
134 / 448
Port Access:
Change the SPI or PPI object into PPI or SPI (and viceversa) on the
bimode port( 140Mbit/s / STM1 switchable).
See para. 10.2.2 on page 137.
This feature is not applicable to 1640FOX
ISA Port Configuration: It allows to configure the TPs for the ISA port connections.
Note: this is available only if an ISA board has been
equipped in the Subrack.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
135 / 448
Navigation to the Port view permits to show a detailed alarm presentation of the port and to set the relevant
configurations as for the example of the following figure.
Note: on the ISA port the TPs are not automatically created (except for MAU TP) when the board is
equipped in the subrack but they must be created with the aid of the Configuration >ISA port
Configuration (refer to Chapter 20 on page 427).
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
136 / 448
Click on Port Access option of the Board menu to access the Port View ( see chapter 11 on page 139).
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
137 / 448
Click on Show Supporting Equipment menu option of the Board menu to navigate to the subrack that
supports the selected port view.
Figure 91. (example) opens.
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
138 / 448
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, ISA port).
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 9 on page 115.
Double clicking on the selected board the relevant Board view is available presenting the ports (see
chapter 10 on page 133).
By double clicking on a board view, the corresponding port view is opened (see Figure 92. ).
The Port view is also reached selecting the Transmission option in the View pull down menu.
Then the Add TP option of the Transmission menu permits to select and confirm a TP (see the description
at para. 14.5 on page 217).
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 be reached from the Port view, selecting a Tp and then Port > Navigate to HOA
port view.
The ISA port (ATM, ETH, PR_EA) are not automatically created when the board is inserted in the subrack
but must be created as explained in Chapter 20 on page 427.
From the Port view It is possible to Navigate to Transmission view.
The port types contain the following TP:
SDH port: Electrical or Optical SPI TTP, RS TTP, MST TTP, prot TTP (MSP TTP), AU4 CTP,
Trail Monitor (only with enabled POM)
SONE Tport: Eelctrical or Optical SPI TTP, RST TTP, prot TTP (MSP), AU3 P.
PDH port: PPI TTP, En CTP, VCn TTP
HOA port: VC4 TTP, TUG3, TUG2, TU3, TU12, Trail Monitoring (only with enabled POM)
ISAATM port: VC4C TTP, VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP and E1 TTP
ISAPR_EA port: VC4 TTP, VC3 TTP and VC12 TTP
ISAFast ETHERNET port: MAU, PTC, VC3XV, VC12XV, VC4 TTP, VC3 TTP and VC12 TTP
ISAGigabit ETHERNET port: MAU, PTC, VC4XV, VC4 TTP, VC3 TTP and VC12 TTP
ISAES port: MAU, PTC, VC4XV, VC3XV, VC12XV, VC4 TTP, VC3 TTP and VC12 TTP
NOTE: ISAPR board does not have any kind of port type.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
139 / 448
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
140 / 448
LCA
The symbols of the TPs (see Figure 93. ) have the following meaning:
TP Role
The icon boxes represent the function: Adaptation, Termination or Compound Adaptation and
Termination.
Cross-connected state
If the condition of the resource is cross-connected, an icon with a x appears beneath the box.
Performance state
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.
Alarm icon area
G.783 TP Role
(Termination)
TP identifier
Crossconnected state
Selection indication
TP under Performance monitoring
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
141 / 448
Selecting the Port option in the menu bar of Figure 89. on page 136 the complete pull down Port menu
is presented (Figure 95. )
The menu differs according the port type (SDH, PDH, HOA and ATM), and is introduced in the following:
TP configuration:
TP Threshold Configuration:
Set Retiming:
AU4 Concatenation:
Only for SDH ports views. See para 11.6 on page 148
Cross Connection:
Monitoring Operations:
Performance:
Loopback:
MSP
Set parameters for the Signal Label and Path Trace overhead on
Synchronous TPs.
See para 14.6 on page 227.
Navigate to Transmission view: permit to show a complete overview about the signal flow, opening
all TPs.
It is described in this chapter, see para.11.10 on page 174
Navigate to Monitor view: permit to show an overview about the monitoring operation (POM, SUT,
TCT/TCM) TPs. It is described on paragraph 11.11 on page 175.
Navigate to HOA port view: this option is available only on SDH ports;
The HOA pot view display the internal structureof the payload.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
142 / 448
SDH Port
PDH port
ISA port
Figure 95. Examples of port menu options (SDH, PDH and ATM/GBIT ETHERNET port)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
143 / 448
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 setup, breakdown or
rearrangement.
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 on OMSN).
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 alarmfree installation without the burden of using a
management system to change the monitor mode.
Selecting the Port Mode Configuration option in the menu bar of Figure 96. on page 144 the complete
Port Mode Configuration window is presented (Figure 97. )
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
144 / 448
System wide search capability is offered in order to show port mode value representation for all ports in
a NE or in a port subset.
The subset is defined according to the filtering capabilities on Port Type (all ports, SDH port Only, PDH
port Only, Ethernet port only, CWDM port only) and to the Port Mode set (Ignore, Mon, Auto).
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
145 / 448
The Retiming feature applies to the outgoing 2 Mbit/s and its purpose is to absorb the jitter /wander that
is transferred to the PDH signal when SDH pointer justification occur. The feature is set individually per
port.
Select a 2Mbit/s port and zoom in to open the port view.
When the Retiming feature is disable, the color of the state information at the bottom of the window is brown
and the label Retiming State Disable is written.
Select the Set Retiming>Enable option from the Port menu (see Figure 98. example)
LCA
As result of this operation the state information color become green and the label Retiming State Enable
is written (see Figure 99. example)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
146 / 448
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
147 / 448
1640FOX
STM4
AU44c
1650SMC
STM4
AU44c
STM4
AU44c
STM16
AU416c
1660SM
Zoom in to open the board and then the port view menu.
In the following a 1660SM has been choosed like example.
Select the AU4 Concatenation option from the Port menu to open Figure 100. on page 149 (in this
example a STM16 view is shown)
The STM16 stream appears divided into different groups: not all AU4s can be chosen as first AU4 but only
AU4#1, AU4#5, AU4#9, AU4#13 for AU4c. Therefore for concatenated action of four AU4s in one AU4c
these AU4 streams are deleted and substituted by the new AU4c component.
Select the supported concatenation Number =4 to visualize the available group/groups then select the
group to concatenate and click on the Concatenate push button.
Click on the Cancel key to exit and come back to the previous window.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
148 / 448
Select a STMN optical interface to configure as AU4 concatenation structure; refer to Table 2.
The Concatenate button will be enabled and the Deconcatenate button will be disabled when is selected
a non concatenated AU4, viceversa when is selected a concatenated AU4.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
149 / 448
To deconcatenate an AU4c select again the AU4 Concatenation option in the Port View menu and then
select the AU4c to deconcatenate (see Figure 102. ). Click on the Deconcatenate push button to apply
the command or on Cancel to exit.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
150 / 448
The Port > Physical Media options permit to set physical configuration of each TP of the port.
The Physical Media options are also accessible from the Transmission menu.
It opens a menu which differs according to the port type:
SDH port:
ALS Management
Show Optical Configuration
Tx Quality Configuration:see para. 18.2.11 on page 375
Single Fiber Configuration
LAPD Configuration:
see para.8.6 on page 99.
Ms Configuration
PDH port:
ETHERNET port:
These options are described in next paragraphs except the previously referenced.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
151 / 448
Automatic laser shutdown (ALS) is useful in case of a loss of communication between two NEs due to
optical fiber breakdown. For safety reasons it may be necessary to shutdown the laser to enable the fixing
of the communication link.
The automatic laser shutdown function can only be configured from the optical ports of the equipment.
Select the SPI block in the port view and then select the Port pull down menu.
Select the Physical media option and then from the cascading menu the ALS Management option .
The Automatic Laser Shutdown State dialogue box opens ( Figure 104. ).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
152 / 448
The aim of this paragraph is to describe the optical port hence the laser sources.
The dialogue box enables the ALS Management and the Restart parameters. The following actions are
available:
a)
b)
c)
1)
2)
Delete : this option deactivates the ALS function, returning to the state shown in Figure 105. on page
153.
From this window it is only possible to create the ALS function (all the ALS commands are greyed).
Figure 105. Automatic Laser Shutdown Management (after ALS Function delete)
d)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
153 / 448
f)
When all the different parameters have been configured, select the Apply button to confirm the setting
and close the dialogue box.
Selecting only the Close button allows you to cancel the choices made.
The TP list... button opens the clipboard dialog; refer to paragraph 4.3.2.3 on page 59 for details.
Note that the ALS procedure is activated ( if enable ) only when the fiber has been interrupted and the
ALS state has not to be confused with the laser state.
ALS states (see example of Figure 106. ), displayed by the functional state message area of the optical
port, are:
ALS states:
Inactive = No ALS has been activated (Off) or the laser has been Forced ON/OFF.
In test = The laser restart has been automatically activated .
Active = The ALS has been activated (On).
Undefined = The ALS is not present (not created).
Laser state:
On = all OK or ALS not present (not created).
Off = Laser off (when ALS is created).
Forced on = ALS forced on by operator command.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
154 / 448
e)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
155 / 448
This command permits to get detailed information on the optical characteristics of the port that is
visualized.
Firstly select an optical board and the SPI block, then click on Show Optical Configuration option from
the Physical media pull down menu to visualize the parameters of the selected optical port.
Figure 107. shows an example of the parameters of the selected interface.
N.B.
This dialogue box can only be read. You cannot write in the entry boxes.
The wavelength of the laser source: the units are nanometers (nm = 109 m).
The use of the port: describes whether the laser port is used for intraoffice transmissions on long
distances (Long Haul ] 40 km) or for infraoffice transmissions on short distances (Short Haul ]
15 km).
The Colored Interface Parameters display the Channel used and the Grid spacing.
To close the dialogue box click on the Cancel push button.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
156 / 448
Tx1 Label : 1
Tx2 Label : 2
Tx2
Tx1
Single bidir
OPTICAL
PASSIVE
COUPLER
Rx1
OPTICAL
PASSIVE
COUPLER
Rx2
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
157 / 448
option and then from the cascading menu the SDH Single Fiber
Allow Single Fiber: select the transmit mode on the single fiber (enable or disable).
Transmitted Section:
Received Section:
Received label
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
158 / 448
11.7.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> Physical Media menu. Figure 110. opens.
This dialog allows to select between SDH or SONET networks. After the selection click on Apply and then
on Close to close the dialog.
Ms Forced AIS is not supported in the current release.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
159 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
160 / 448
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
161 / 448
[1]
Auto Negotiation : allows to configure the Rate to be negotiated (10 or 100 Mb/s).
The Directionality (Full Duplex) and the Flow Control (Activated) are always enable and cant
be changed.
[2]
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 (see Figure 114.
on page 162) to advice that the user has changed data but not applied them.
completed OK
completed KO
configuring
deactivated
parallel Defect Fail
other
At the bottom of the port view are displayed the following indications (refer to Figure 112. on page 161
and Figure 115. on page 163):
ED
10 Mb/s
100 Mb/s
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
162 / 448
For the Fast Ethernet (10/100 Mbit/s) port it is possible to choose between two Configuration Type:
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
163 / 448
Click on PortEthernet Mapping Protocol option of the Port> Physical Media menu. Figure 116.
opens.
ED
HDLC
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
164 / 448
Select a VC TP.
11.7.8
This dialog allows to modify the state of the Ethernet port virtualTPs, created as explained in Chapter
20 on page 427.
Select a TP in the Ethernet port view window.
Click on Control Path Activation option of the Port> Physical Media menu.
A new window will be opened (Figure 117. and Figure 118. are examples); a similar window is display
when a new concatenated VCX is created in the ISA port configuration window (refer to paragraph 20.2.3
on page 432).
This dialog aims to show the activation state of the virtualTPs present in the Ethernet Port View and to
change the number of virtual TPs active.
Two modality are foreseen to activateTPs:
[1]
Individual path (refer to Figure 117. ): the Active state is reached by selecting the individual row with
the mouse and click on the Change Status button.
[2]
Path Range (refer to Figure 118. ):the Active state is reached by choosing the number of TPs to be
active and click on the Apply button.
On the contrary to change in Idle the Active state of a TP decrease the TPs to be active field and
then and click on the Apply button.
To switch bwtween the two modality click on the relevant button in the Activation Mode field. In this field
it is also displayed the Actual Selected Mode.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
165 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
166 / 448
Figure 120. can be reached also from ISA board Configuration window (refer to paragraph 20.2 on page
428).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
167 / 448
The Monitoring... button opens the LCAS monitoring window dysplayed in Figure 121.
Other parameters can be set:
RS acknowledge timeout; it is the timeout value (in milliseconds) LCAS protocol waits for the
resequence acknowledge message
The button Apply will se the attribute Max differential delay and RS acknowledge timeout if the LCAS
protocol is enable.
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
168 / 448
In the LCAS Configuration window it is possible to Enable / Disable the LCAS scheme protocol selecting
the relevant button.
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)
Add: this member is about to be Added to the group
Norm: Normal transmission
Eos: End of Sequence indication and Normal transmission
Idle: this member is not part of the group or about to be removed
Dnu: Do Not Use (the payload) the Sk side reported FAIL status
Unknow
Rx Channel State: MST indication (OK/FAIL) relative to a traffic flow Node B to Node A;
Rx CTRL Packet: Message received (ADD, DNU, IDLE, NORM, EOS, FIXED), relative to a traffic
flow from Node B to Node A; it provides the status of the individual member of the group as reported
in the following:
Fixed: this is an indication that this end uses Fixed bandwidth (nonLCAS mode)
Add: this member is about to be Added to the group
Norm: Normal transmission
Eos: End of Sequence indication and Normal transmission
Idle: this member is not part of the group or about to be removed
Dnu: Do Not Use (the payload) the Sk side reported FAIL status
Unknow
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
169 / 448
This menu item enables the configuration of the most important transmission parameters concerning the
Primary Rate Access (PRA) and G.703/G.704 frame management.
PRA management
The PRA functionality performs termination bidirectional function for Time Slot 0 on framed with CRC4
2 Mbit/s signal.
In detail, it extracts in sink direction and writes in source direction particular bits (E, Sa5, Sa6 and A) of
the Time Slot 0.
Moreover, it generates substitution frames in case of detection of LOS on the signal coming from a
Terminal Equipment.
The PRA functionality has been extended in order to manage proprietary handling of the bits of Time Slot
0 (Framed with leased line PRA option) in terms of state, defect detection and consequent actions.
G.703/G.704 management
This functionality allows to activate the adaptation function to process a framed (G.704 interface) or not
framed (G.703 interface) 2Mbit/s signal.
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
170 / 448
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.
a configurable parameter in order to define the operation modes of the CRC procedure;
the configuration of the consequent action on the transmitted 2M/s signal in case of configured
retiming functionality and loss of synchronization (when the CRU is in HoldOver or
FreeRunning mode).
the configuration of the consequent action concerning the AIS insertion for board
P63E1NM4 in leased Line mode.
CRC4 Status that defines the monitoring capabilities applied to the signal with a CRC multiframe:
Operation: allows to configure the CRC4 processing modalities; the possible value are:
Remote Indication: readonly field that indicates if status of CRC4 error counting
functionality of farend NE is enabled or disabled.
ED
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 Freerunning mode; the
consequent action is performed only if PRA or leased line application ha been configured on
the associated P12CTP.
The possible values of the Loss of Sync Consequent Action are:
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
171 / 448
FarEnd defect Consequent Action allows the AIS insertion towards 2Mb/s PDH as
consequent action upon the detection of the farend defect on the SDH side (by a special
pattern carried in Sa4bits); it works only in leased line application;
The values attribute are:
Frame Status is a readonly field that reports an indication of the received signal:
no indication
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
172 / 448
Select a TP.
Click on Show Supporting Board menu option of the Port menu to navigate to the board that supports
the selected port view.
Figure 123. (example) opens.
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
173 / 448
Click on Navigate to Transmission View menu option of the Port menu to navigate to the corresponding
Transmission View that is related to the selected TP.
Navigation to the Transmission view permits to show a complete overview about the signal flow as for the
example of the following figure..
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
174 / 448
Select a TP.
Select a TP where are configurated some Monitoring Operations (POM, SUT, TC).
Click on Navigate to Monitoring View menu option of the Port menu to navigate to the corresponding
Monitoring View that is related to the selected TP.
Navigation to the Monitoring view permits to show a complete overview about the Monitoring Operations
(POM, SUT, TC) as for the example of the following figure.
In Figure 125. on page 175 is shown an example of Monitoring View of a TP with POM and TCM both
before and after matrix.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
175 / 448
After having selected a Tp (for example AU4), click on Port > Navigate to HOA Port View option.
The HOA port displays the internal structure of the payload, as for the following figure:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
176 / 448
12.1 Introduction
It is unthinkable to launch a telecommunications system, handling millions of communications, without the
possibility of replacing equipment in a real time way, consequent to equipment failure. Everything must
be done so that the communications can continue smoothly and so that the equipment failure remains
transparent to the users. Protection management deals with this aspect of the EMLUSM.
The protection is performed by switching the board supporting the protected service when this board fails
to a protecting board capable of supporting the same service. This protection is realized according to a
protection scheme.
An equipment protection scheme is composed of the following parameters which can be configured:
Protection priority:
A priority can be assigned to protected units in 1+n protection schemes. This priority can be be
1, 2, ... or n, 1 being the highest priority.
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 contents is represented is considered as implicitly selected.
EPS protection states are displayed by the functional state message area of the boards involved in an
equipment protection scheme.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
177 / 448
The Port view is reached selecting the Equipment option in the View pull down menu to present the
subrack view, as described at chapter 9.1 on page 115.
r01sr1/board#40
r01sr1/board#23
r01sr1/board#32
r01sr1/board#27
The right side of the dialogue box allows to modify the EPS configuration.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
178 / 448
1660SM EQUIPMENT:
N.B.
For P3E3/T3 P4ES1N and P16S14E 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 are
the following:
ED
the access card corresponding to the protecting board must be an HPROT card
the HPROT card has to be plugged at the left side of the access card group
the main/spare boards have to be adjacent.
the protecting board has to be plugged at the left side of the protected group of boards
the protecting/protected group of ports have to be of the same type
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
179 / 448
N.B.
The MATRIX protection is automatically presented in the left side of the dialog box when
the SPARE MATRIX is created in the Set option of the Equipment menu. It is not created
with the EPS menu described in this chapter.
1650SMC EQUIPMENT:
N.B.
ED
the access card corresponding to the protecting board must be an HPROT card
the HPROT card has to be plugged at the left side of the access card group
the main/spare boards have to be adjacent.
the protecting board has to be plugged at the left side of the protected group of boards
the protecting/protected group of ports have to be of the same type
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
180 / 448
The spare card position can be assigned in a flexible way; no restriction for position of main and
spare ISA PR_EA are present.
The spare card position can be assigned in a flexible way; no restriction for position of main and
spare ATM MATRIX are present.
In the following will be explained some rules for EPS schema configuration using
SYNTH1N board; the same rules can be applied to SYNTH4 board.
Mixed configuration are also allowed (i.e. EPS schema composed by SYNTH1N and
SYNTH4).
board of slot 9, COMPACT ADM1 (SYNTH1N) main (protected)
board of slot 10, COMPACT ADM1 (SYNTH1N) spare (protecting)
N.B.
for each type of failure on the COMPACT ADM main board (matrix, CRU, Shelf
Controller) a switch is performed to the spare boards. The optical/electrical port and
the Equipment Controller function on the COMPACT ADM board are not EPS
protected.
The SYNTH1N/SYNTH4 protection is automatically presented in the left side of
the dialog box when the SPARE SYNTH1N/SYNTH4 is created in the Set option
of the Equipment menu. It is not created with the EPS menu described in this
chapter.
a)
Scheme displaying
ED
Scheme creation
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
181 / 448
After that operation, Choose Protecting button becomes insensitive and Choose Protected becomes
sensitive (see Figure 130. on page 183)
The user can add, always using the same Board Selection list dialogue box presented, as many
protected boards as wanted (max.15 in 1660SM, max. 2 in 1650SMC).
When the right part of window is correctly filled, the OK button close the dialog box and create the scheme
(the new list is update reopening the EPS Management dialogue box).
The Cancel push button cancels the creation and closes the dialog box.
c)
Scheme deletion
To delete an existing protection scheme, the user selects a scheme in the left list. Using the Delete button,
user could delete the scheme.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
182 / 448
d)
Scheme modification
To modify an existing protection scheme by adding or removing protection units, the user selects a scheme
in the left list. Using Choose button for protected elements, user could add protected boards.
By selecting a protected board and using the Delete Protected button, user could remove protected
elements from scheme. When the right part of window is correctly filled, the OK button close the dialog
box and modify the scheme.
The Cancel push button cancels the creation and closes the dialog box.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
183 / 448
Protection role
Protection status
The EPS functional state of a board selected in the board view is displayed at the bottom of the view as
shown in the following figures.
Switch Type
Figure 131. EPS functional state from protected active board view
Figure 132. EPS functional state from protecting active board view
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
184 / 448
This functionality configure Revertive and Wait Time to Restore in a protection scheme.
In order to configure, perform the following operations:
Select the EPS pull down menu. Then select the Configure option as show in the following figure.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
185 / 448
1660SM EQUIPMENT:
1650SMC EQUIPMENT:
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
186 / 448
This functionality enables to force a protecting board to work even if there is not failure.
The forced switch will fail if the other board is already forced switched or if the protecting board has a failure
condition.
In order to switch an EPS, perform the following operations:
Select the EPS pull down menu. Then select the Switch option as show in the following figure.
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
187 / 448
The search criteria can be chosen with the help of a combo box:
Board Type: allows to filter for the EPS protected boards (example Ignore, SYNTH1N, MATRIXN,
P3E3/T3, etc. )
Status: allows to filter for all possible EPS protection states;the following filters values should be
offered (examples):
Ignore
Normal
DNR
AutoFail
AutoWTR
Manual
Force
Lockout
After the filter selection click on Search button to start; the field below the Search button will be updated
(see Figure 138. )
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
188 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
189 / 448
Board Role:
Ped
Ping
(Protected)
(Protecting)
A
S
F
(Active)
(StandBy)
(Faulty)
Protection Status: defines the current state of the protection unit as follow
Normal
DNR
AutoFail
AutoWTR
Manual
Force
Lockout
The colors used for each row have the following meaning:
Green (OK):
Red (Critical):
for protected protection units in fail condition, protection unit in lockout or active
on autoswitch or commands
Orange (Major):
for protected units in standby after a command and protecting protection unit
in standby for autoswitch or commands
Cyan (Indicative):
for protecting protection unit active and no fail condition present in the schema
(Do Not Revert State)
At the bottom of the EPS Overview windows are available five button that allows to navigate through the
EPS management views and subrack view, board view.
In this way the operator has a quick link towards the views showing the correlation between the alarms
and the protection states.
N.B.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
190 / 448
opens the Subrack view showing the protection states with icons on the
boards (see example of Figure 139. )
The possible protection states and the relevant symbols are explained in
the following:
Symbol
opens the board view showing the alarm and the board administrative
states (see example of Figure 140. )
Open Commands:
opens the EPS Switch dialog box. See 12.4 on page 187 and the
relevant description.
EPS Management:
and
opens the EPS Management dialog box. See Figure 128. on page 178
the relevant description.
EPS Parameters:
opens the EPS Configuration dialog box. See 12.3 on page 185
and the relevant description.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
191 / 448
ED
02
3AL 91670 AA AA
448
LCA
Figure 139. Subrack view after Open Subrack View command (example)
LCA
Figure 140. Board view after Open Board View command (example)
SC.3:NE MANAGEMENT
192 / 448
Architecture 1+1 or N+1 Standard (the last is only available for 1660SM)
Described in ITUT Rec. G783/G841. The refence switching criteria are SF and SD. It provides a
k1/k2 communication protocol thus this protection can be single or dual ended.
Architecture 1+1 Proprietary (not used )
The refence switching criteria are SF and SD. No k1/k2 communication protocol is provided thus
this protection can be only single ended.
Architecture 1+1 Optimized (not used )
Architecture 1 : 1 Standard (not used )
Described in ITUT Rec. G783/G841 as architecture 1 : n ( with n=1 ). The refence switching criteria
are SF and SD. It provides revertive mode managed by k1/k2 protocol and thus this protection can
be single or dual ended. The spare interface can be used to transport low priority traffic .
The 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 value depend on the NE selected threshold on the MS
termination point. This threshold value is configured as explained in the para.14.7 on page 234.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
193 / 448
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:
MSP Create, MSP Management, MSP Commands and MSP Delete can also be accessed from the
Transmission > MSP menu.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
194 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
195 / 448
Select one and then click on Add Port button in the Ports field to create a MSP schema.
Figure 143. on page 196 is opened.
Following steps are necessary:
choose Port
Select the Choose Port button to define the Protected Port and Protecting Port units.
Figure 144. on page 197 is opened.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
196 / 448
At the end click on the OK button to confirm the MSP protection schema configuration. An error message
will be appear if the selected schema is not supported by the NE.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
197 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
198 / 448
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 is not supported by the NE.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
199 / 448
Before changing a single ended (unidirectional) schema into a dual ended (bidirectional), all active
switches must be cleared (manual switch, lockout,... ). If the operator wants to change the protection
schema architecture or the ports involved in the MSP schema, the current schema must be removed and
recreated.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
200 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
201 / 448
Local: switch due to near end SD/SF or local user switch command
OK
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
202 / 448
Figure 151. represents a MSP configuration with a normal condition, with an automatic protection
switching and with a forced command. In any situation are represented the statuses displayed on both
protected/protecting Port views. The Active status indication, with a forced command on the protecting
group, shows where the forced command is applied.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
203 / 448
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 Force to
Protected port command.
For 1+1 nonrevertive system, forced 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 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 (Protected port) to the protection section
(Protecting 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). It is also possible to switch back to the working channel using again the Manual
to Protected port command.
For 1+1 nonrevertive 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
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
204 / 448
The Clear WTR command cancel the delay time for switching protection and protecting port after
recovery from failure/defect.
The Exercise command issues an exercise request for protection channel and checks responses 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.
The Release command clears all previously switching commands.
ED
Lockout of
protection
Forced to
Autoswitch
Manual to
Lockout of
protection
Lockout
Lockout
Lockout
Forced to
Lockout
Forced
Forced
Autoswitch
Lockout
Forced
Autoswitch
Manual to
Lockout
Forced
Autoswitch
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
205 / 448
ED
Board Type: allows to filter for the MSP protected boards (example P4ES1N, P4E4N, L41N,
Ignore, etc.)
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
206 / 448
Status: allows to filter for all possible MSP protection states;the following filters values should be
offered (examples):
Ignore
NR (Normal)
DNR
AutoSF
AutoSD
AutoWTR
Manual
Force
Lockout
APS Invalid (Fail)
Bad channel (Fail)
After the filter selection click on Search button to start; the field below the Search button will be updated
(see Figure 138. )
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
207 / 448
Role:
Ped
Ping
Protected
Protecting
A
S
F
ET
(Active)
(StandBy)
(Faulty)
Extra Traffic (Not operative)
Protection Status: defines the current state of the protection unit as follow
NR
DNR
AutoSF
AutoSD
AutoWTR
Manual
Force
Lockout
APS Invalid
Bad channel
(Normal)
(Do Not Revert)
(AutoSwitch Signal Fail)
(AutoSwitch Signal Degrade)
(AutoSwitch Wait Time To Restore)
(Manual Switch)
The colors used for each row have the following meaning:
Green (OK):
Red (Critical):
for protected protection units in fail condition, protection unit in lockout or active
on autoswitch or commands
Orange (Major):
for protected units in standby after a command and protecting protection unit
in standby for autoswitch or commands
Cyan (Indicative:
for protecting protection unit active and no fail condition present in the schema
(Do Not Revert State)
At the bottom of the MSP Overview windows are available five button that allows to navigate through the
MSP management views and to open the Port View.
By clicking on Open Port View the operator has a quick link towards the view showing the correlation
between the alarms and the protection states.
N.B.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
208 / 448
opens the port view showing the correlation between the alarm and the MSP
protection states. See Figure 156. on page 209.
MSP Create:
opens the MSP Create dialog box. See Figure 142. on page 195 and the
relevant description.
MSP Delete:
opens the MSP Delete dialog box. See Figure 150. on page 201 and the
relevant description.
MSP Management: opens the MSP Management dialog box. See Figure 148. on page 200 and
the relevant description.
MSP Commands: opens the MSP Commands dialog box. See Figure 153. on page 205 and the
relevant description.
Figure 156. Port view after Open Port View command (example)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
209 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
210 / 448
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 all TPs belonging to a port can be called in by activating the function
to expand the selected TP. TP names are listed in an additional information area if the mouse
pointer is positioned over it. The following states are indicated (see Figure 157. on page 212):
An overview concerning signal flow can be requested by a user action. The user can select
a TP and apply the action Transmission > 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.
Search for and select a termination point in a TP search dialog and display it in the Transmission
View.
Pop-up the Transmission View from the board view. All TPs/compound TPs associated with the
physical port are displayed (i.e. TPs down to AU-4).
Provide the possibility of configuring a selected TP. This functionality is accessed by calling the
configuration dialogs of the common Transmission/Port Views category.
Provide the possibility of showing a detailed view of a TP with alarms, navigating to the Port view.
Provide the possibility of showing and setting Performance Monitoring parameters and data.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
211 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
212 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
213 / 448
It is possible both to expand a VC-4, thus displaying all underlying TPs, and to hide TPs which are of no
interest. The objects initially displayed depend on the situation/definition.
14.3.3 Naming TPs
The following rules are applied in order to identify the TPs displayed:
all child nodes contain a short label indicating the position inside the tree.
All kinds of object deletion events related to TPs displayed are indicated by the TP objects. The graphical
objects are removed accordingly from the Transmission View. Example: modification of the payload
structure from 63 TU-12 to 3 TU-3.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
214 / 448
Add TP
Expand
Hide
Hide TPs that are related to the selected TP or the selected TP.
It is described in this chapter, see para 14.13.2 on page 250
TP Configuration
Terminate TP
Disterminate TP
AU4 Concatenation:
Cross-Connection
Monitoring Operations
Performance
Structure TPs
Loopback
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
215 / 448
Physical Media
MSP
These options are described in next paragraphs except the previously referenced.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
216 / 448
14.5 ADD TP
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
217 / 448
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
218 / 448
After clicking on Show CC State, a more detailed TP list is displayed (see Figure 163. ) containing TP
cross connection status information.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
219 / 448
After clicking on Show Mon, a more detailed TP list is displayed (see Figure 165. ) containing TP under
monitoring with relevant type information (example TCT, POM, SUT, etc.)
After clicking on Show PM, a more detailed TP list is displayed (see Figure 166. ) containing the TPs under
Perfomance monitoring with relevant performance type information ( example near end 15 min, Farend
15 min., 1 day Nearend etc.)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
220 / 448
An easy way to recall to previously displayed boards is to use Board History ( refer to Figure 167. on page
221 ).
Select the relevant board from the list.
(No Alarms)
Primary Alarms)
All Alarms)
When a selection different by Ignore is done, all criteria, except Class option menu and the check boxes
related to Equipment/PM/Monitoring objects, are grayed.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
221 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
222 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Class:
Ignore, E1S, OpS, PPI, AU-4, VC-4, AU-4+VC-4, TU-3, VC3, AU3 & TU3 & VC3, TU-3+VC-3, TU2,
TU-12, VC-12, TU-12+VC12, AUX, MS, RS, OGPI, GMAU.
Assign State:
Ignore, NML, EML; not used
Monitoring Object:
Ignore, POM, SUT, TCT, TCM, Any; None.
Location:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
223 / 448
N.B.
ED
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).
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
224 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
225 / 448
The output file is generated after clicking on Ok. Use Cancel to stop the process.
This command opens the online help for the TP-Search dialog.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
226 / 448
14.6 TP Configuration
Select the desired TP and then the Transmission > TP Configuration option.
TP Configuration can also be accessed from the Port view menu.
14.6.1 High Order TP Configuration
Depending on the TP selected, a dialog appears for the configuration of the main parameters of the
following objects:
J1 Path Trace.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
227 / 448
If the Path Trace is 16 bytes long, the first byte is a CRC7 checksum calculated by NE.
If the Path Trace is shorter than 16 bytes, it is filled with zero bytes (0 hexadecimal).
Received fields is read only.
With the relevant button the operator can set the Expected field as:
TTI Enable
TTI Disable
TTI Repeated
The Transmitted field can be set with TTI Enable or TTI Repeated byte
Empty TTI button permits to send an all zeroes path trace.
To replace modified with the default, enter the default manually according to the following table.
Table 4. Default value for C2/V5 Signal Label
TP
VC4 TTP
(PDH)
VC3TTP
VC12 TTP
Significant Byte
C2
C2
C2
V5
Default value
18
Click on Hex button Figure 175. will be opened displaying in hexadecimal code the same value repored
in Trasmitted and Received field.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
228 / 448
0: Unequipped
1: Equipped non-specific
2: TUG structure
3: Locked TU-n
4: Asynchronous 34/45Mbyte
19: ATM
21: FDDI.
In the Transmitted field it is possible to select the values:
Automatic: the C2 Signal Label value is automatically selected by the NE according the VC
structure.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
229 / 448
Click on Hex button Figure 177. will be opened displaying in hexadecimal code the same value repored
in Trasmitted and Received field.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
230 / 448
Depending on the TP selected, a dialog to configure the main parameters of the following objects:
VC-12 TTP.
Select the desired VC12 and then the Transmission > TP Configuration option.
The main parameters are:
J2 Path Trace.
Click on Hex button Figure 179. will be opened displaying in hexadecimal code the same value repored
in Trasmitted and Received field.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
231 / 448
ED
02
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
232 / 448
If the Path Trace is 16 bytes long, the first byte is a CRC7 checksum calculated by the NE.
If the Path Trace is shorter than 16 bytes, it is filled with zero bytes (0 hexadecimal).
Expected and Transmitted fields are editable by the operator.
Mode1 enable the 16 bytes long sequence for Path trace
One repeated byte allows to set one byte that will be repeated.
Received fields is read only.
With the relevant button it is possible to enable or Disable TTI Monitoring.
Empty TTI send an all zeroes path trace.
0:
1:
2:
3:
4:
Unequipped
Equipped non-specific
Asynchronous
Bit Synchronous
Byte Synchronous
Automatic: the C2 Signal Label value is automatically selected by the NE according the VC
structure.
Equipped not specific (it corresponds to number 1)
To replace modified with the default, enter the default manually according to the value reported in
Table 4. on page 228.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
233 / 448
Poisson distribution enable configuration of the Excessive Bit Error Ratio (ExBER on MST, VCi)
threshold and Signal Degrade (SD on MST, VCi) threshold of the TPs related counted primitives.
Bursty distribution enable configuration of the maximum number of errored frames and the total
amount of bad block per frame.
Note (*): the ExBER and Signal Degrade may be: B2 for MST, B3 for VC4 and VC3, BIP12 for VC12.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
234 / 448
This menu allows the operator to set the alarm thresholds for MST and VCi layer.
14.8 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.8.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:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
235 / 448
Select the Transmission > Monitoring Operations option as for the following figure.
Creation/Deletion and Configuration options are presented.
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, TCT, TCM functions (Path
Overhead Monitoring, Supervised Unequipped Termination, Tandem Connection Termination/Monitoring;
SUT function is not operative).
AU4 CTP (High order POM before and after matrix; TCM before and after matrix)
AU44c CTP (High order POM before and after matrix; TCM before and after matrix)
AU416c CTP (High order POM before and after matrix; TCM before and after matrix) only for
1660SM
TU-3 CTP (Low order POM before and after matrix;TCM before and after matrix)
TU-12 CTP (Low order POM before and after matrix; TCM before and after matrix)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
236 / 448
14.9.1 Creation/Deletion
This dialog allows multiple object creation/deletion.
The dialog shown in the following Figure 181. opens:
Before Matrix
After Matrix
The Supervisory Unequipped Termination, not operative in current release, has the following parameters:
Press Ok to apply the parameters or Close to close the dialog and discard the not with Ok applied
changes.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
237 / 448
When select and apply the Path Overhead Monitoring, the changes will be displayed in the Port View in
the following manner:
Also refer to para. 11.11 on page 175, about navigation to Monitoring View.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
238 / 448
The TP list... button opens the Clipboard window; refer to paragraph 4.3.2.3 on page 59 about the use
of the Clipboard.
14.9.2 Configuration
Depending on the parameters selected in the Monitoring Operations Creation/Deletion dialog, not all
sections of the dialog are available.
NOTE: It is possible to open the POM and TCT/TCM Configuration dialog for a CTP even if neither
PathOverheadMonitor nor Tandem Connection was created before (SUT isnt available in this
release). No changes can be made in this case and the values displayed can be ignored.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
239 / 448
TTI Definition
TTI Expected
TTI Received without the display
TTI Sent
TTI Enabled
TTI Disabled
TTI Repeated Byte
Error Distribution
Poisson and Bursty error distribution are supported.
TCM/TCT ConsActions
It is needed to support explicit consequent action activation (AIS insertion) for TCT sink and
bidirectional.
Thresholds
Set the thresholds of the following parameters:
Signal Degrade
Poisson mode only: from 105 to 109.
Excessive Error
Poisson mode only: from 103 also if presented a selection from 103 to 105
Bursty Degrade
Select a value between 1 and 1000 errors/sec for the Bursty Degrade threshold.
Bursty Consecutive
Select a value between 2 and 10 sec for the Bursty Degrade Consecutive.
Alarm Timing
Raising and Clearing Timing are not supported by OMSN.
Unequipped Trail
Not available.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
240 / 448
Select the Transmission > Structure TPs option as for the following figure.
This menu item provides the possibility of structuring and destructuring a selected TP. The level that is
selected defines how the signal is to be structured, e.g. if a VC-4 TTP is selected and the menu item TU-12
is chosen, the signal is structured down to 63 TU-12 CTPs. The following menu items represent all those
possible:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
241 / 448
The commands of this menu item are for the management of the loopback commands, for commissioning
or maintenance purposes.
14.11.1 Loopback Configuration
The loopbacks can be applied at line (external to equipment) level or at internal equipment level. The
loopback commands are used to separate the communication network into independent part checking the
line/equipment functionality during the network installation or maintenance operation.
The loopback architecture provides four configurations ( see Figure 185. ).
Line Loopback And Continue
Line Loopback And AIS
Internal Loopback And Continue
Internal Loopback and AIS
Initial
Destination
Line
Internal
Destination
Line
Initial
AIS
Destination
AIS
Initial
Internal
Line
Initial
Line
Destination
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
242 / 448
14.11 Loopback
Internal Loop
& Continue
Internal Loop
& AIS
STM64
(only on 1660SM Rel. 5.x)
OK
Access Denied
OK
Access Denied
STM16
(only on 1660SM)
OK
Access Denied
OK
Access Denied
STM4
Access Denied
OK
Access Denied
OK
STM1
Access Denied
OK
Access Denied
OK
140Mbit/s
(not available on 1640FOX)
Access Denied
OK
Access Denied
OK
34/45 Mbit/s
OK
Access Denied
OK
Access Denied
2 Mbit/s
Access Denied
OK
Access Denied
OK
SDH board:
The loopback configuration can be done only on SDH ports with the acronym ending
with a N letter (i.e. P4S1N, S4.1N, L4.1N, L4.2N, etc.)
OpS for optical STM1, STM4, STM16 SPI (only available on 1660SM), STM64
SPI (only available on 1660SM Rel.5.x)
MsT TTP for STM1, STM4, STM16 (only available on 1660SM), STM64 (only
available on 1660SM Rel. 5.x)
Select the Transmission > Loopback > Port Loopback Configuration option as for the following
figure.
Port Loopback Configuration can also be accessed from the Port view menu.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
243 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
244 / 448
Loopback Management can also be accessed from the Port view menu and from the Configuration
menu.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
245 / 448
Search Criteria (not operative): to configure the filter select the Loop and Continue type (Yes= Loop
And Continue, No= Loop And AIS) then select the Directionality Internal or Line and edit the Initial
TP Id (write: rack, subrack, board, port# and the TP type: EIS (SPI/PPI Electrical), OpS (SPI/PPI
Optical), MST and so on. For Initial TP has to be intended the outgoing signal while for
Destination TP the incoming signal. Enable the filter through the Toggle Filter Enable/Disable
button. Click on the Search button to start the configured loopback research into the current
loopback table.
The Delete command permits to delete a loopback listed in the Current loopbacks Table: select a
loopback in the list and click on the Delete button.
The Create command permits to create a new loopback configuration: clicking on Create the
previous figure ( Figure 186. ) opens. Follow the previously paragraph indications to create a new
loopback configuration.
The activated loopbacks are signalled in the Port view and in the Transmission view as for the following
figures:
PORT VIEW
Active Loopback
TRANSMISSION VIEW
Active Loopback
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
246 / 448
The configured loopback are listed into the current loopbacks table. This table can be managed by the
Search criteria, Delete and Create commands.
Select the Transmission > Physical Media option as for the following figure.
The Physical Media options permit to set physical configuration of each TP.
It opens a menu in which the various options will be available according the TPs type (for the option
common with the Port view reference is made to the relevant paragraph):
ED
02
ALS Management.
TX Quality Configuration
Extra traffic
Not operative
Not operative
Set Domain
HDSL Configuration
Not operative
NT Configuration
Not operative
X21 Configuration
Not operative
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
247 / 448
This option is referred to the SECurity management and allows the user to set the Manager list and the
Access Control Domain of the selected TP.
Select the block: EIS for Electrical SDH port, OpS for Optical SDH port, P (PPI) for PDH port.
Select the Set Domain option from the Physical Media cascade menu to present the following view:
The dialogbox contains the following fields:
NML Assignment: each connected manager to the TP is highlighted in the list. The user can set a
manager clicking on the denomination.
Several manager can be enabled contemporaneously, having in charge the TP.
The Manager List contains the list of managers ( i.e. RM, SY, NPOS , EML) that work on the NE. The
EMLUSM administrator (SH or Craft Terminal) should set the Manager List only to remove a
manager in case of emergency (i.e. the Manager misses the NE connection).
Resource domain field allow to select the domain among that displayed in the list, assigning it to
the TP.
The different domains could be assigned to different operators.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
248 / 448
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
249 / 448
14.13.2 Hide
Select the Transmission > Hide option as for the following figure.
This menu item provides the possibility of hiding all upper/lower TPs of a selected TP and the deletion of
a selected TP.
Lower TPs,
Upper TPs,
Selected TPs.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
250 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
251 / 448
This menu provides the possibility of navigating to the corresponding Port View related to the selected
TP in order to access a detailed overview of alarms quickly.
The Port View appears:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
252 / 448
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:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
253 / 448
By introducing the Synchronous Digital Hierarchy (SDH), a standardized transmission has been created,
matching the European with the American standard. The SDH signal structure contains an extended
overhead as well as a fixed pointer controlled assignment of the user signal elements, thus improving the
possibilities of the network management.
Signals of the Synchronous and Plesiochronous Digital Hierarchy (PDH) are packed by synchronous
multiplexers into Virtual Containers (VC). The STM-1 signal structure is achieved by using the multiplex
structure complying with ITU-T and ETSI, (see Figure 191. ). Each of the user channels (2 Mbit/s, 34
Mbit/s, 45 Mbit/s and 140 Mbit/s) is packed into a container synchronous to the STM-1 frame according
to a predefined structure.
To adjust the plesiochronous signals to the synchronous network clock, certain filling algorithms are
available. Fix fill bits are inserted into synchronous signals. A byte column (9 Byte) as Path Overhead
(POH) is added to the Container (C) generated. Path Overhead and Container together form the Virtual
Container (VC). With the pointer pointing to the start of the VC, in respect of the STM-1 frame, an
Administrative Unit (AU) or if several Containers of a group are to be combined a Tributary Unit (TU)
is generated. Several TUs form a Tributary Unit Group (TUG) and TUGs again can be combined into a
VC. The AU of the signal, together with the Section Overhead (SOH), finally make up the STM-1 frame.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
254 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
255 / 448
C11
VC11
VC12
C12
2 Mbit/s
(1,5 Mbit/s)
VC2
C2
6 Mbit/s
VC3
C3
C4
(45 Mbit/s)
34 Mbit/s
140 Mbit/s
TU11
TU12
TU2
TU3
x3
x1
x1
x4
TUG2
x7
TUG3
x7
VC3
x3
VC4
C
VC
TU
TUG
AU
x1
x3
STM1
xN
not implemented
Pointer -Processing
: Container
: Virtual Container
: Tributary Unit
: Tributary Unit Group
: Administrative Unit
Legend:
AU3
AU4
STMN
270
1
Section Overhead
SOH
3
4
9 rows
AU Pointer
Payload
Section Overhead
SOH
9
Figure 192. Frame Construction within the Synchronous Digital Hierarchy
The STM-1 frame has a basic bit rate of 155.520 Mbit/s. A single user channel is packed into a Virtual
Container. These Virtual Containers are of different size and may be nested or packed differently.
Virtual Containers for the European bit rates:
either 1 x VC-4
or 3 x VC-3
or 2 x VC-3 + 7 x VC-2
or 2 x VC-3 + 21 x VC-12
or 1 x VC-3 + 14 x VC-2
or 1 x VC-3 + 7 x VC-2 + 21 x VC-12
or 21 x VC-2
or 14 x VC-2 + 21 x VC-12
or 7 x VC-2 + 42 x VC-12
or 63 x VC-12.
STM-N signals are constructed by integer multiples of the basic signal STM-1 of 155.520 Mbit/s. For
example an STM-16 signal of 2.488.320 Mbit/s is generated by combining sixteen STM-1 signals byte
interleaved.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
256 / 448
When ports are depicted on the user interface, the following abbreviations are used.
This section concerns the multiplex structure (see Figure 191. ) 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
TU-x (Connection Termination Point), i.e. TU-12 CTP, TU-2 CTP, TU-3 CTP.
The TU-x CTP represents both the creation and termination of a VC-x connection. The
Low-order Connection Supervision (LCS) function is included.
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
257 / 448
ED
MSP definition
Transmit side, the MSNP (AU4CTP) input enters two different MSNP/MSN (unProtected CTP)
sources and then the MSNTTP working and protection sources (to insert the K1K2 bytes) are sent
to the own SPI interfaces. Receive side, the working and protection MSN/MSNP outputs (AU4CTP)
enter in the switching selector. The MSNPTTP terminates the selected signal and checks the SSF
and the MSP protocol failure.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
258 / 448
On SDH level (see Figure 193. ) a distinction is made between the following TTPs:
!"#
$
+
%&
'(
'(
'(
(
')
')
')
')
')
')
')
)
*)
*)
*)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
259 / 448
.+ "
*,+"
!
!
!()&
)+"
(+"
!(*&
!(
%
!(
!*
%(
%(
!)
!)
!*
%*)
%*)
!*
%*)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
260 / 448
-
!
!
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
261 / 448
A cross-connection represents the logical connection between the input and output of the matrix, called
the matrix port.
The matrix only receives and transmits signals in GTI format. The Generic Transport Interface GTI,
Alcatels standardized signal format for internal interfaces, is similar to the STM-1 format. The incoming
signals are mapped or converted to GTI format on the plesiochronous and synchronous I/O boards. This
frame is based on the STM-1 frame specified by ITU-T Recommendation G.707. It enables the transport
of all signals in the US hierarchy and ETSI hierarchy levels 1 to 4 (1.5 Mbit/s to 140 Mbit/s) mapped to
Virtual Containers (VCs) (see Figure 191. ).
The VCs are sent from the I/O boards to both copies of the Matrix (A and B) via the GTI. The matrix
performs the cross-connection on the VC-4, VC-3, VC-2 or VC-12 level and transfers the VCs to the
relevant I/O boards via GTI. The configuration of both matrix copies is always identical. On the I/O boards,
one GTI signal is selected from Copy A or Copy B, based on quality.
The NE supports unidirectional, bidirectional and broadcast connections unprotected as well as protected.
15.1.5.1 Unidirectional Connection
Information is transmitted exclusively from the input port to the output port (point-to-point); there is no
routing in reverse direction.
input TP
output TP
input TP
output TP
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
262 / 448
In the example below, information is broadcast from one input to outputs A, B and C on three legs.
output A
input TP
leg 1
leg 2
leg 3
output B
output C
A warning box indicates when the resources available for broadcast connections are exhausted.
N.B.
ED
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.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
263 / 448
A unidirectional connection is routed from Input A to the Output (primary route). In the case of a failure,
the system automatically switches to the protection path from protection Input B to the Output. This second
connection is permanently kept in hot standby operation (see Figure 198. ).
input A
prot.
input B
output TP
in case of
failure
in case of
failure
N.B.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
264 / 448
/
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.
Input
Prot. input
Output
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
265 / 448
This paragraphs list the complete procedure to realize some examples of cross-connection moving among
the various menus.
The following main cases have been considered:
[1]
[2]
High order concatenated signal cross connection (AU4xc between SDH ports)
[3]
Low order signal cross connection (TU12 cross connected with VC12; ports involved: SDH and
PDH )
[4]
[5]
In the following example an AU4 will be cross connected with another AU4; the P4S1N board has been
taken like reference board.
In the subrack view click twice on the SDH port; the board view will be opened
Click twice on the daughter board icon; the daughter view will be opened.
Click twice on the SDH port icon present in the daughter view. the port view will be opened with all
the relevant TPs (SPI, RST, MST, MSP and AU4).
Select the AU4 TP and then choose the Port >Cross Connection > Create Cross Connection option
of the menu bar; a new window called Main Cross Connection is opened.
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 (in our example is P4S1N), in the Termination Points
field select the AU4
Click on OK; the Search for Cross Connection Output window is closed.
Repeat the same procedure as obove described for the Prot. Input field for protected connections
To check the presence of the new cross connection select the Port >Cross Connection > Cross
Connection Management option of the menu bar; a new window called Coss connection
Management will be opened
ED
Click on the Search button; all the cross connected Tps will be displayed in the Cros
Connection in list field.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
266 / 448
N.B.
Before to create an AU4 concatenated crossconnection is necessary to define that the AU4s
on a STM4 or STM16 (the last only for 1660SM) board are concatenated as explained in para
11.6 on page 148.
In the subrack view click twice on the STM_N SDH port; the board view will be opened
Click twice on the SDH port icon present in the board view. the port view will be opened with all the
relevant TPs (SPI, RST, MST, MSP and AU4xC).
Select the AU4xC (with 4 X 16) TP and then choose the Port >Cross Connection > Create
Cross Connection option of the menu bar; a new window called Main Cross Connection is opened.
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 STMN Board , in the Termination Points field select the
AU4xC (with 4 X 16) (syntax example: r01sr1sl24/port#01#01AU4P4c ).
Click on OK; the Search for Cross Connection Output window is closed.
Repeat the same procedure as obove described for the Prot. Input field for protected connections
To check the presence of the new cross connection select the Port >Cross Connection > Cross
Connection Management option of the menu bar; a new window called Coss connection
Management will be opened
Click on the Search button; all the cross connected Tp will be displayed in the Cros
Connection in list field.
In the subrack view select Configuration > Cross Connection Management the Cross Connection
Management window will be opened.
Click on the Create button; a new window called Main Cross Connection is opened.
ED
Click on Choose relevant to the Input field; a new window called Search for Cross
Connection Input is opened.
On the Equipment field select the Equipment Subrack (SR60M for 1660SM), in the TP Seach
Criteria field select the TU12&VC12, then click on search.
In the Termination Point Field select the TU12 to be connected and subsequently click on OK
button; the Search for Cross Connection Input window will be closed.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
267 / 448
Click on Choose relevant to the Output field and repeat the same sequence as above
described for the input point but instead of TU12 select now the VC12 to be connected in the
Termination Point Field; click on OK button AND the Search for Cross Connection Output
window will be closed.
Select the VC12 TP and then select the Port >Cross Connection > Create Cross Connection
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.
Repeat the same on the Prot. Input field for protected connections by selecting the TU12 involved
in the protection.
To check the presence of the new cross connection select the Port >Cross Connection > Cross
Connection Management option of the menu bar; a new window called Coss connection
Management will be opened
Click on the Search button; all the cross connected Tp will be displayed in the Cros
Connection in list field.
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.
For details on 4xANY board refer to the Technical Handbook.
In the subrack view click twice on the 4xANY board; the board view will be opened .
Click twice on the module to be used; the daughter view will be opened
Click twice on the daughter board icon; the port view will be opened with all the relevant TPs.
In the following will be explained how to connect one TpP of the 4XANY; repeat the same sequence for
all the TPs that has been generated when the traffic type has been defined.
ED
Select the VC4 TP and then choose the Port >Cross Connection > Create Cross Connection
option of the menu bar; a new window called Main Cross Connection is opened.
Click on Choose relevant to the Output field; a new window called Search for Cross
Connection Output is opened.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
268 / 448
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.
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 Cros
Connection in list field.
ED
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 so refer to point
[4] .
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
269 / 448
Port view is presented with the View Equipment pull down menu, then clicking on the presented
objects with the sequence board>port.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
270 / 448
The Cross-Connection Management dialog is initially empty (see Figure 203. on page 273).
A list of cross-connections is displayed in the Cross-Connection Management dialog after selecting the
Search command.
There are two possibilities of displaying a list of cross-connections:
do not enter any search criteria and press the Search button to display a list of all existing
cross-connections,
enter Search Criteria (one or more) and then press the Search button to display a selection of
cross-connections. Set Ignore for attributes not to be used as filtering criteria.
Use button Cancel Search to cancel an active search request or close the dialog.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
271 / 448
Type
Select the connection type:
Unidirectional
Bidirectional
Multipoint
Drop&Continue
Protection
Select protection functionality:
Protected
Not protected
TP Class
Select one of the TP types involved in the requested cross-connection.
State
Select the connection state:
Activated
Deactivated (not operative in current release, the connection state is always Activated)
Prot. State
Select the protection state (for more detailed information, refer to Chapter 9.5):
Forced to Input
Forced to Protecting
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:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
272 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
273 / 448
After a successful search, a read only list of cross-connections matching the search criteria appears
(see Figure 204. ). The number of matching cross-connections is displayed in the upper left corner of the
list. The list contains information concerning the following parameters for each cross-connection:
Prot. State
detailed switching information in the format:
<protection state> <traffic ind> (<location>:<signal state><switch status>,
[<location>:<signal state><switch status>])
<protection state>
Normal, Auto, Lockout, Forced or Manual.
<traffic ind>
indicates the location of current traffic:
P (Protecting input) or I (Input).
<location>
indicates the location of the errored signal:
P (Protecting input) or I (Input)
<signal state>
indicates the signal state: SD (Signal Degrade) or SF (Signal Failure)
<switch status>
status of the switch:
c (completed) or p (pending)
Example:
Auto I (P:SD-c)
There has been an Automatic switch from the protecting input to the Input where the traffic is
currently located. The reason for the automatic switch was Signal Degrade in the Protecting input.
The switch was completed.
SNCP
State
connection state indicating whether cross-connection is A(ctivated) or D(eactivated)
Dir.
Direction-related connection type:
uni(directional), bi(directional), mp (multipoint), DC_N (Drop & Continue Normal) or DC_I (Drop &
Continue Inverse)
Input
signal source; contains the TP type and physical location of the port according to the format
<rack#><subr.#><board#><port#>,<port#>#TP (see Figure 204. on page 275)
The # within brackets identifies a number.
Protecting Input
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
274 / 448
protecting source (for protected cross-connections only); contains the TP type and physical location
of the port according to the format
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Output
signal destination
for point-to-point cross-connections, the TP ID of the destination is specified according to the format
r<rack#>s<subr.#>b<board#>/port#<port#>-TP ; for multi-leg cross-connections, the string
multiple Legs appears instead.
At the bottom of the dialog is a range of buttons to start actions on the listed cross-connections. Before
starting any action apart from creation or printing, mark at least one cross-connection.
To mark several cross-connections (multi-select) that are listed in succession, select the first
cross-connection of a block with a mouse click and the last one with a mouse click while pressing the
<Shift> key.
Or, mark a number of individual cross-connections by clicking the mouse button while pressing the
<Control> key.
Deselect cross-connections by clicking on the respective row while simultaneously pressing the <Control>
key. To deselect a number of cross-connections at a time, press the <Shift> key and hold it down while
moving the mouse pointer to the last entry.
All actions that may affect traffic must be confirmed. A confirmation dialog pops up in this case and the
user has to confirm the requested action.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
275 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
276 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
277 / 448
All operations that may affect traffic must be confirmed. The subsystem provides a confirmation
dialog box before the operation can be executed.
If the window displays an existing cross-connection, the OK button is insensitive when this
cross-connection is assigned to NML or it is not assigned to the user profile.
If the window is used to create a new cross-connection, the system verifies that the relevant TPs can
be used (not assigned to NML and assigned to the user profile) after the OK button is pressed. If a
specified TP is not permitted, the corresponding message box appears.
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
278 / 448
To prevent operation faults, the system is designed according to the following guidelines:
Input
To enter the input TP, click the relevant Choose button and select the TP in the TP Search dialog
(see Figure 162. on page 218). Otherwise, select the input field and enter the name of the TP directly.
Prot. Input
To enter the protecting TP, click the relevant Choose button and select the TP in the TP Search
dialog. Otherwise, select the input field and enter the name of the TP directly.
Output
It is possible to enter one or more output TPs.
To enter one output TP, click the relevant Choose button and select the TP in the TP Search dialog.
Otherwise, select the input field and enter the name of the TP directly.
To enter more than one output TP and create a broadcast connection, proceed as described
previously and press button Add afterwards. The previously chosen TP is then moved to the list box
located below. Click the Choose button and select the next TP in the TP Search dialog. Otherwise,
select the input field and enter the name of the TP directly. Repeat this procedure for each destination
TP. A list of all the selected output TPs is displayed in the list box located below it.
To delete a leg from the list, select the TP in the list box and click on the Delete Leg button.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
279 / 448
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.
"3
&
&
&
&-
&
&-
4#
&
&
&
&
&
&
$33
&
&
&
&
&
&
-
-
#
&
5
"
12
ED
02
&
3
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
280 / 448
N.B.
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:
Unidirectional, protected
Bidirectional, protected
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
281 / 448
Loopback connection:
unidirectional, same input and output TP
Figure 206. Cross-Connection Icons
Example:
current state:
TPs are not connected
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
282 / 448
2)
3)
To enter the TP, click the Choose button and select the TP in the Search for Cross Connection
Input dialog (see Figure 209. ), or select the input field and enter the name of the TP directly.
The Search for Cross Connection Input dialog offers the possibility to list TPs according to
different filter criteria. E.g. to obtain a list of all not connected AU-4 TPs of a rack, first select the
rack in the left list box, then select the filter criteria ConnectionState not connected and Class
AU-4 and click on button Search. The matching TPs are listed in the right listbox. Select the
input TPs in the list and confirm with Ok.
For a more detailed description on the Search for Cross Connection dialog see para. 14.5.1
on page 217.
4)
6)
7)
8)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
283 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
284 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2)
3)
4)
Press the button Add Leg in the Main Cross Connection dialog and all output TPs are displayed
in the list box under the Output field (Figure 210. on page 287).
To delete a leg from the list, select the TP in the list box and click on the Delete Leg button.
The following steps only apply to protected broadcast connections:
5)
Select or type in the Protecting input TP. Note that each single protected leg of the broadcast
has to be assigned to the same protecting input.
Proceed as described in Step 3 ). Afterwards, select the protected output TP in the output list box
and click button Protect Leg. The leg is then marked as protected in the list box. Repeat this
procedure for each protected output TP (only one protected leg is supported in current release).
To unprotect a leg from the list, select the protected TP in the list box and click on the Unprotect Leg
button.
Examples are in Figure 210. and Figure 211.
6)
7)
8)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
285 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
286 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
287 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
288 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
&
&
12
"
3
"
3
&
&
&
4#
&
$33
&
-
-
&
#
&
5
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
289 / 448
The following few facts should be taken into consideration when modifying connections.
Unprotect a protected cross-connection (see Figure 212. ):
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 212.
In addition, a question box appears, asking the user to confirm the unprotect action.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
290 / 448
When an unprotected cross-connection is being protected, the Prot. Input button is available to
select the protection input connection to insert.
An example is in the following Figure 213.
Protection principle are given in para. 15.1.6 on page 264.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
291 / 448
NOTE: the Delete crossconnection action is not possible in the case that is still
existing any operation/connection/termination on the underlying supported signals, such as:
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
292 / 448
Unprotected Cross-Connection
An unprotected bidirectional cross-connection is split into two unidirectional cross-connections with
the input TP in one of them being the output in the other and vice versa (see Figure 214. ).
The new cross connection has the same name and activation status as the old bidirectional one.
6
7
*8
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
293 / 448
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.
6
7
)8
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
294 / 448
b)
Precondition
Two cross-connections can be joined if they match the following characteristics:
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 (case 1, see Figure 214. ) or a protected bidirectional (case 2, see
Figure 215. ) cross-connection.
If the original cross-connections have different names, the new name is a concatenation of the names of
both of them.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
295 / 448
The Protection Actions dialog is displayed after clicking on the Protection button in the Cross
Connection Management dialog (see Figure 204. ).
Users can only switch protection on cross-connections belonging to them and not assigned to the NML.
A second condition is that protection is enabled for the cross-connection concerned (protection parameter
is set to protected).
The three protection actions Force, Lock Out and Manual Switch belong to different levels, whereby
Lock has the highest priority and Manual Switch the lowest.
Note that a protection state can only be changed within the same or from a higher priority level, e.g. Force
To Protecting can be reverted with Release but not with Manual Switch To Input.
Force to Input
The cross-connection is switched to the protected input regardless of signal quality. Automatic
protection is disabled.
Release Force
Forced switching is disabled and automatic protection switching re-enabled.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
296 / 448
Release Lock
The protection lock is disabled.
N.B.
All the operations listed are context-dependent and are enabled or disabled (grayed)
accordingly.
After completion of protection switching, the list entry in the Cross Connection Management dialog is
updated automatically.
After clicking on an action button and completing the action initiated, the dialog disappears automatically.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
297 / 448
This option is used to print the currently filtered cross-connection list and the related filter settings on the
default printer or to a file in postscript or ASCII format (see Figure 217. and Figure 218. )
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
298 / 448
15.8 Print
The result is that all other TPs connected to the currently selected TP are displayed (see the example of
Figure 219. on page 300). 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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
299 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
300 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
16 OVERHEAD MANAGEMENT
16.1 Introduction
All the descriptions in the following paragraphs are applicable only to 1650SMC and 1660SM.
The purpose of this set of dialogs is to handle the operations on the Overhead (OH) bytes of the NE.
The possible operations are:
Overhead crossconnection
There is a TP associated to every OH byte and to every auxiliary port, so TP could be used instead of
OH bytes or auxiliary port, depending on the context.
These bytes are E1 (for V11 signal) and F1 (for RS232). The auxiliary signals are available, at the
backside connector, as soon as the CompactADM unit is inserted, without any software presetting.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
301 / 448
OH Crossconnection
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:
For STM ports it make sense to allow the operator to perform a total passthrough of the MSOH bytes.
A total msoh passthrough connection (connection between msPassThroughCTP points) is setup only
if no single msoh passthrough connection are set and if no single msoh crossconnection are set. If a
total msoh passthrough connection is set, a single msoh passthrough connection or a single msoh
crossconnection cannot be set.
The steps an operator has to do in order to perform the total MSOH passthrough are the following:
After having deleted a total MSOH passthrough, the involved msPassThroughCTP points have to be
deleted.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
302 / 448
OH TP creation
OH TP deleting
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
303 / 448
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu
the OH Cross Connection option.
The Cross-Connection Management for OverHead dialog opens (see Figure 221. on page 304 ) and
allows to start the configuration.
It is similar to the dialog used for the crossconnection of the TP for paths, then the same
description and functions are valid.
Next configuration steps use the Main Cross-Connection for OverHead (see Figure 222. on page 304)
dialog and the TP Search dialog (see Figure 162. on page 218), also in this case already described for
path management.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
304 / 448
For all details, navigation and sequences on these views refer to chapter 15 on page 253.
There is one big difference between the OH TPs and the other kinds of TPs: the OH TPs have to be:
Supported operations
After choosing one or more cross connections/terminations, this dialog allows to:
Note: this dialog disappears only when the user explicitly clicks on the close button.
Delete operations can be performed on several cross connections/termination at the same time.
Modify operations can be performed only on single cross connections/terminations.
The OH xconnections are automatically active at the moment of their creation.
The operation buttons availability follows some rules:
The Delete and Print buttons are enabled only if at least one item is selected from the list.
A special dialog will ask the user for a confirmation.
the create button is always enabled. It brings up the Main crossconnection Dialog.
When some operation may affect the existing traffic, the operator is warned about that, and a confirmation
dialog must be answered to carry on/cancel the operation. The choices for this dialog are: yes/no for
single items, yes to all/cancel for multiple items
When used for OH purposes, the Cross-Connection Management dialog doesnt support the following
functionalities:
ED
Activate/Deactivate
cross
connections/terminations:
all
connections/terminations are automatically active since their creation
02
the
OH
cross
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
305 / 448
According to the philosophy of offering only meaningful operations to the user, and being the OH
crossconnection operations a subset of those applying to the general cross connections (e.g:protections
are not allowed), some fields of this dialog are disabled.
By clicking on the proper portions of the dialog and on the proper buttons, the operator can perform the
operations hereafter listed:
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:
navigation rack/subrack/board/port
When used in the OH domain, this dialog is a subcase of the most generic TP Search.
ED
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)
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
306 / 448
In 1660SM and 1650SMC to connect the auxiliary / vocal channels and the Overhead bytes the following
operative indication must be observed:
1660SM:
the auxiliary and vocal channels TPs are in the SERVICE board of slot 11
The auxiliary channels are:
r01sr1sl11/port#05P
Expanding this TP, 31 referred TPs are presented
r01sr1sl11/port#06P
Expanding this TP, 31 referred TPs are presented
r01sr1sl11/port#01#01v24TTP
r01sr1sl11/port#02#01v24TTP
r01sr1sl11/port#03#01v24TTP
r01sr1sl11/port#04#01v24TTP
r01sr1sl11/port#01#01v11TTP
r01sr1sl11/port#02#01v11TTP
r01sr1sl11/port#03#01v11TTP
r01sr1sl11/port#04#01v11TTP
ED
r01sr1sl11/port#07P
r01sr1sl11/port#08P
r01sr1sl11/port#09P
r01sr1sl11/port#10P
02
r01sr1sl11/port#01#01q23TTP
Expanding this TP, four referred TPs are presented:
r01sr1sl11/port#01#001q23TTP
r01sr1sl11/port#01#002q23TTP
r01sr1sl11/port#01#003q23TTP
r01sr1sl11/port#01#004q23TTP
These TPs permit to connect the voice channel toward four directions.
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
307 / 448
1650SMC:
the auxiliary and vocal channels TPs are in the SERGI board of slot 05
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
1 x G.703 2 Mbit/s (not operative in current release); in the screen is indicated as:
r01sr1sl05/port#03P
Expanding this TP, 31 referred TP are presented from
r01sr1sl05/port#04P
r01sr1sl05/port#05P
r01sr1sl05/port#01#01v11TTP
r01sr1sl05/port#02#01v11TTP
r01sr1sl05/port#01#01v24TTP
r01sr1sl05/port#02#01v24TTP
r01sr1sl05/port#01#01q23TTP
Expanding this TP two referred TP are presented:
r01sr1sl05/port#01#001q23TTP
r01sr1sl05/port#01#002q23TTP
These TPs permit to connect the voice channel toward two directions.
The other boards used to terminate or crossconnect the OH bytes are the STMn boards.
The OH TP are present in MS, RS and VC4 TP Class.
In these TPs the indication ......#0011 to 0099 (MS or RS) are referred to the coordinates of the
Section OverHead bytes on the SDH frame (1,1 to 9,9).
The voice channel are identified by the ow indication, the FU is for Future Use, the NU is for
National Use, UC is for User Channel and Pass is for Passthrough channel.
The examples of the figure in this OH connection chapter can be helpful to the operator.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
308 / 448
16.5 OH TP creation
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu
the OH TP creation option.
The OH TP creation dialog opens (see Figure 223. ) and allows to create the OH TP to cross connect.
In detail, the dialogbox contains the following graphical object:
a Choose button is used to display a list of OH Tps to be created. The Choose button starts
the TP Search (see Figure 224. ) with predefined filtering; the TP Search dialog allows the
operator to visualize only not created OH Tps.
To visualize the OH TP in the TP Search view double click on the MS, RS or VC4 Tp.
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
309 / 448
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu
the OH TP deleting option.
The OH TP deleting dialog opens (see Figure 225. ) and allows to delete the OH TP no more involved
in an OH crossconnection.
In detail, the dialogbox contains the following graphical object:
a Choose button is used to display a list of OH Tps to be deleted. The Choose button starts
the TP Search with predefined filtering; the TP Search dialog allows the operator to visualize
only created and not crossconnected OH Tps.
Apply button is used to perform a delete request of the tp displayed in the OH Tp field. After having
performed the delete request, the OH Tp field is set to empty.
Close button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
310 / 448
16.6 OH TP deleting
r01sr1sl11/port#01#01q23TTP
the interface field (at the top) where can be selected the phonic interfaces to be configured.
It identifies a TP indicated as q23TTP, referred to the physical voice connection on the SERVICE
unit in slot11.
the phone number field, to set the telephone number for operator call on the phonic interface.
The phonic extension field, where enable or disable the extension of the selected phonic interface.
If enabled the phonic signal is extended towards the external on the access panel of the NE.
Apply button performs the configuration change of the modified phone parameters of the selected phonic
interface without close the dialog
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
311 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
312 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
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 on the SDH PORT are Errored Seconds (ES) and Severely Errored Seconds
(SES).
The Performance Monitoring domain counts these errors during specified granularity periods (15 min,
24h) and stores the values in history data logs.
For the purpose of quality supervision, the values of the error counters can be compared to user-defined
threshold levels. If a counter value has crossed a threshold level, a notification (threshold crossing alarm)
is issued.
The principle performance management functions are:
Configuration of the quality thresholds that generate alarms and log records when predefined values
are exceeded.
On the ETHERNET PORT a set of performance counters are foreseen, for QoS and maintenance
purpose. By selecting the GMAU TP and subsequently the Transmission>Performance menu, the
following options are available:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
313 / 448
17.2.1 Overview
Performance Monitoring functionalities, are described in the following paragraph in addition to general
information concerning performance monitoring on the NE.
Paragraph 17.4 on page 325 Configuration ( SDH port) deals with the configuration of performance
monitoring
Paragraph 17.5 on page 330 Display Current Data ( SDH port) deals with displaying current
performance data
Paragraph 17.6 on page 333 Display History Data ( SDH port) deals with displaying history
performance data
Paragraph 17.7 on page 335 PM Threshold Table Selection ( SDH port) deals with the selection
of threshold tables
Paragraph 17.8 on page 339 PM Threshold Table Modification/Display ( SDH port) deals with
the modification of threshold tables and permits to display the same
Background Block Error (BBE): A BBE counter measures the number of errored blocks which do
not occur as part of an SES.
Errored Second (ES): A one second period with one or more errored blocks or with a defect.
Severely Errored Second (SES): A one second period which contains > 30% of errored blocks, or
at least one Severely Disturbed Period (SDP). An SES is also counted as an ES.
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 errored block which does not occur as part
of an FESES.
Far End Errored Second (FEES): Identifies, at a terminal, a one second period with one or more
errored blocks or with a defect which were received by the Far End Terminal.
Far End Severely Errored Second (FESES): Identifies, at a terminal, a one second period which
contains > 30% of errored blocks, or at least one Severely Disturbed Period (SDP) which was
received/detected by the Far End Terminal. An FESES is counted as an FEES.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
314 / 448
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:
Errored Block (EB): A block in which one or more bits associated with the block are erroneous.
Remote Error Indicator (REI) [formerly Far End Block Error (FEBE)] : Identifies, at a terminal,
the count of errored blocks that were received by the far end terminal.
Remote Defect Indicator (RDI) [formerly Far End Receive Failure (FERF)]: indicates to a terminal
that the far end terminal has detected an incoming failure.
Unavailable Time (UAT): A period of unavailable time begins at the onset of 10 consecutive SES
events. These 10 seconds are considered to be part of unavailable time. A new period of available
time begins at the onset of 10 consecutive non-SES events.
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 OFS is defined as a second in which one or more out of frame
events have occurred. This event is identified by the A1/A2 byte of the SDH Frame.
The counting of OFS is only supported for the regenerator section termination. Please note that this
counter is deprecated by ETSI and will be removed from international standards.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
315 / 448
Far end performance monitoring parameters are derived from Remote Defect Indicators (RDI) and
Remote Error Indicators (REI) (refer to Figure 227. ).
Node B
Node A
Source
transmission
signal
Sink
significant bits
significant bits
far end
defect
RDI insertion
Sink
near end
defect
near end
counter
far end
counter
far end
defect
significant bits
near end
defect
far end
counter
near end
counter
RDI insertion
Source
significant bits
transmission
signal
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
316 / 448
17.2.3 Far End (FE) and Near End (NE) Performance Counting
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
317 / 448
TCM allows monitoring within the operator domain. The quality within the operators own 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 VC4nc (n=1, 4, 16, ...), VC4, VC3 and VC12 layers.
TCM provides:
A suspect interval flag is set as an indication that the data of the corresponding register may be either
incomplete or invalid.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
318 / 448
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:
By default, zero suppression is active for all PM enabled TPs. The number of suppressed intervals is
indicated.
17.2.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.
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 to the first of the recent registers.
When all recent registers are full, the oldest information is discarded.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
319 / 448
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 24hour (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 15minute (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 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:
increased thresholds (higher than current value of counters) (only for 24 h).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
320 / 448
17.2.12 Thresholds
Paragraph 17.9 on page 343 Configuration (Ethernet port) deals with the configuration of
performance monitoring
Paragraph 17.10 on page 344 Display Current Data (Ethernet port) deals with displaying current
performance data
Paragraph 17.11 on page 348 Display History Data (Ethernet port) deals with displaying history
performance data
An Ethernet link can be defined between two 10/100 Ethernet interfaces, or between two Gb Ethernet
interfaces, or also between a Fast Ethernet and a Gb Ethernet interface.
At the terminations of Ethernet link, it s possible to monitor the Ethernet frames and to collect information
about the Ethernet traffic by means of some counters.
Incoming (network centric view): it refers to the direction starting from Ethernet domain toward SDH
domain (see Figure 228. ). The traffic arrives to the board from an Ethernet link and goes out from
an SDH link.
[2]
Outgoing (network centric view): it refers to the direction starting from SDH domain toward Ethernet
domain (see Figure 228. ). The traffic arrives to the board from an SDH link and goes out from an
Ethernet link.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
321 / 448
17.3.1 Overview
They are:
Aggregate counters
Flow counters
Besides this classification, some counters can be of Quality of Service, others only of maintenance.
Port interface#1
TRSEFin
TRSEFout
Interface
Counters
TRCOin
TRCFin
TDFin
TTOin
TTFin
SDH
Ethernet
Symbol Error
Media Available Exits
Jabber State
False Carrier
TRCOout
TRCFout
TDFout
TTOout
TTFout
Flow
Counters
Aggregate
Counters
They are:
Symbol Error : for an interface operating at 100Mb/s, the number of times there was as invalid data
symbol when a valid carrier was present. For an interface operating in fullduplex mode at 1000 Mb/s,
the number of times the receiving media is nonidle carrier event for a period of time equal or greater
than minFrameSize, and during which there was at least one occurrence of an event that causes the
PHY to indicate Data reception error on the GMII. The count represented by an instance of this object
is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier
event. This count does not increment if a collision is present.
Media Available Exits : number of times that ifMauMediaAvailable for this MAU instance leaves
the state available. Discontinuities in the value of this counter can occur at reinitialization of the
management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
322 / 448
Ethernet counters can be distinguished from different points of view as depicted in Figure 229.
Jabber State : number of times that mauJabberState for this MAU instance enters the state
jabbering. This counter will always indicate zero for MAUs of type dot1MauTypeAUI and those of
speeds above 10Mbps. Discontinuities in the value of this counter can occur at reinitialization of the
management system, and at other times as indicated by the value ifCounterDiscontinuityTime.
False Carrier: number of false carrier events during IDLE in 100BASEX and 1000BASEX links.
For all other MAU types, this counter will always indicate zero. This counter does not increment at
the symbol rate. It can increment after a valid carrier completion at a maximum rate of once per 100
ms for 100BASEX and once per 10s for 1000BASEX until the next CarrierEvent. Discontinuities
in the value of this counter can occur at reinitialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
TRSEF (Total Received Service Errored frames): it is the sum of three contributions.
Alignment Errors:
A count of frames received on a particular interface that are not an integral number of octets
in length and do not pass the FCS check.
The count represented by an instance of this object is incremented when the alignment Error
status is returned by the MAC service to the LLC (or other MAC user).
Received frames for which multiple error conditions obtain are, according to the conventions
of IEEE 802.3 Layer Management, counted exclusively according to the error status presented
to the LLC.
FCSErrors :
A count of frames received on a particular interface that are an integral number of octets in
length but do not pass the FCS check. This count does not include frames received with
frametoolong or frametooshort error.
The count represented by an instance of this object is incremented when the frameCheckError
status is returned by the MAC service to the LLC (or other MAC user).
Received frames for which multiple error conditions obtain are, according to the conventions
of IEEE 802.3 Layer Management, counted exclusively according to the error status presented
to the LLC.
Note: Coding errors detected by the physical layer for speeds above 10 Mb/s will cause the
frame to fail the FCS check.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
323 / 448
TRSEF outgoing
SDH VCn
pipe
Node A
Node B
Transmitted
frames
Received
frames
ISA Eth/GbE port
OMSN
OMSN
Incoming direction
Outgoing direction
SDH >Eth
TRCO (Total Received Correct Octets): total number of octets of Ethernet frames received correctly,
including Ethernet header characters.
TRCF (Total Received Correct Frames): total number of Ethernet frames received correctly
TDF (Total Discarded Frames): total number of Ethernet frames which were chosen to be discarded
due to buffer congestion.
TTO (Total Transmitted Octets): total number of octets of Ethernet frames transmitted out, including
Ethernet header characters.
TTF (Total Transmitted Frames): total number of Ethernet frames transmitted out.
TTO incoming
TTF incoming
TRCO incoming
TRCF incoming
TTO outgoing
TTF outgoing
TRCO outgoing
TRCF outgoing
SDH VCn
pipe
Node A
Node B
Transmitted
frames
Received
frames
ISA Eth/GbE port
TDF incoming
OMSN
OMSN
Incoming direction
Outgoing direction
TDF outgoing
SDH >Eth
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
324 / 448
TRSEF incoming
Use menu item Add TP to display a special TP in the Transmission menu (see para.14.5 on page 217).
Select the TP and open the PM Configuration dialog (see Figure 232. ) by clicking on the menu item
Transmission >Performance >Configure Performance 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 Performance Monitoring option in the Port pull down menu (see
para.11 on page 139).
N.B.
To configure PM for au4CTPs and tuxCTPs, Path Overhead Monitoring (POM) ,Supervised
Unequipped Termination (SUT, not supported) or Tandem Connection (TCT, TCM) must be
created first (see description in para. 14.9 on page 236 ).
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
325 / 448
When more than one of the above options is chosen, a Question dialog box is displayed (see Figure 233. );
click on Cancel to continue or OK to interrupt any action.
N.B.
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 and near end)
Each dataset has to be configured independently. For AU4 CTP and TUx CTP the highest criteria is
POM and SUT. I.e. select the POM or SUT option first and then configure the different associated datasets.
Confirm the configuration with Apply before you continue with a different POM or SUT option.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
326 / 448
In case of au4CTP tuxCTPs and VcxCTP, the PM Configuration dialog also contains a cascading menu
that allows to configured the POM/SUT/TC options as follow:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
327 / 448
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.
Notifications
This parameter can only be selected during creation and cannot be subsequently
modified.
Threshold Table
Attach a threshold table to the selected TP. Only assign threshold tables that match the granularity
period of the datasets (i.e. a 15 min. threshold table must not be assigned to a 24 h dataset).
Otherwise the Transmission view is blocked and only released by closing and reopening the PM
Configuration window and the Transmission view.
Click on button Attach... to open the PM Threshold Table Select dialog (see Figure 236. ) and
configure the threshold table (see Chapter 17.7 on page 335).
Select button Remove to disassociate the threshold table from the entity.
N.B.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
328 / 448
ASAP Id
This field shows the label of the ASAP pointer assigned to the UAT alarm
Set ASAP
Allows to set a new ASAP pointer for the UAT alarm. The Set ASAP button opens the window
displayed in Figure 20. on page 57.
The Tp List... button opens the Clipboard windows; for details refer to paragraph 4.3.2.3 on page 59.
Confirm the configuration with the button Apply before closing the dialog. Otherwise the configuration is
lost.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
329 / 448
Select the TP and open the Current PM Data dialog (see Figure 234. ) by clicking on the menu item
Display Current Data.
This Current PM Data dialog serves to show the results and status of the Performance
Monitoring counters.
It is possible to access the same Current PM Data dialog selecting a TP in the Port view and opening
the same Performance > Display Current Data option in the Port pull down menu (see para.11 on page
139).
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 tuxCTPs, VCxCTP the Current PM Data dialog also contains a cascading menu that
allows to choose the POM/SUT/TC options to display as follow:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
330 / 448
Use menu item Add TP to display a special TP in the Transmission view (see para.14.5 on page 217).
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:
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
The entry Unavailable ThresholdCrossed indicates, that both alarms are active. Since
the text field is too small to display the full text at a time, use the cursor to scroll the text
field in this case.
Elapsed Time
Indicates the time which has elapsed since the monitoring interval was started. This information tells
the user whether the data collection covers the whole period.
N.B.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
331 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
332 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Use menu item Add TP to display a special TP in the Transmission view (see para.14.5 on page 217).
Select the TP and open the PM History Data dialog (see Figure 235. ) by clicking on the menu item
Display History Data.
This PM History Data dialog serves to show stored Performance Monitoring counting.
It is possible to access the same PM History Data dialog selecting a TP in the Port view and opening
the same Performance > Display History Data option in the Port pull down menu (see para.11 on page
139).
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 , tuxCTPs VCxCTPs, the PM History Data dialog also contains a cascading menu that
allows to choose the POM/SUT/TC options to display as follow:
Each page label presents a range of parameters for one near end and far end granularity period. To select
a special page label, click on the top part of the label.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
333 / 448
The number of recorded events concerning an entity is divided into near end and far end data
Elapsed Time
indicating whether the data collection was complete (see para. 17.2.10 on page 319)
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. These figures cannot be changed by the user.
If the limit of 16 datasets for 15 min. granularity and one 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.
Monitor
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
334 / 448
All available datasets (entities), which are related to the selected TP, are displayed in the table:
N.B.
Do not open several dialogs at the same time using both possibilities. Since those dialogs are
not synchronized, they could display different contents.
Attach the selected threshold table to a TP entity. It is only available entering from the PM
Configuration dialog (see Figure 232. )
The user has to close the dialog explicitly by clicking on the button Close.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
335 / 448
1660SM example
ED
02
1640FOX and 1650SMC
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
336 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
layer
TPs ASSOCIATED
granularity
STM16
RS
15 minutes
STM16
RS
24 hours
STM4
RS
15 minutes
STM4
RS
24 hours
STM1
RS
15 minutes
STM1
RS
24 hours
STM16
15 minutes
STM16
24 minutes
STM4
15 hours
10
STM4
24 hours
11
STM1
15 minutes
12
STM1
24 hours
13
VC4
15 minutes
14
VC4
24 hours
15
VC3
15 minutes
16
VC3
24 hours
17
VC12
15 minutes
18
VC12
24 hours
ED
layer
TPs ASSOCIATED
granularity
STM4
RS
15 minutes
STM4
RS
24 hours
STM1
RS
15 minutes
STM1
RS
24 hours
STM4
MS NE / FE
15 minutes
STM4
MS NE / FE
24 hours
STM1
MS NE / FE
15 minutes
STM1
MS NE / FE
24 hours
VC4
Path Termination NE / FE
15 minutes
10
VC4
Path Termination NE / FE
24 hours
11
VC3
Path Termination NE / FE
15 minutes
12
VC3
Path Termination NE / FE
24 hours
13
VC12
Path Termination NE / FE
15 minutes
14
VC12
Path Termination NE / FE
24 hours
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
337 / 448
After the activation of a PM on a TP, it will be signalled in the Port view and in the Transmission view as
for the following figures:
PORT VIEW
Active PM
TRANSMISSION VIEW
Active PM
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
338 / 448
2)
3)
Enter the set (Value Up) and the reset (Value Down) threshold values. Note that the reset value
if supported, will be available with 15 min. monitoring periods.
Table 12. on page 341 shows the maximum performance monitoring event values.
The respective value is automatically reset to the maximum if a larger figure is entered.
4)
Select the alarm Severity for each PM attribute in case a threshold is crossed.
5)
Disable Send notification if no notification message should be sent in the case of a crossed
threshold.
6)
Confirm the entries with Apply to create the threshold table. A number of threshold tables can
be created from the same window.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
339 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
340 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
17.8.2 Modification
The PM Threshold Table Modify dialog (see Figure 238. ) pops up if a threshold table is selected in the
PM Threshold Table Selection dialog (see Figure 236. ) 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 12. shows the allowed maximum performance parameter values.
2)
Modify the alarm Severity for each PM attribute in case a threshold is crossed.
3)
Disable Send notification if no notification message should be sent in the case of a crossed
threshold.
5)
To modify more than one threshold table, do not close the dialog, but select the next threshold
table in the PM Threshold Table Selection dialog and press the Modify button
(see Figure 236. ).
Performance Parameter
34,559,100
3,317,673,600
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
BBE, FEBBE
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
341 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
342 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Use menu item Add TP to display a special TP in the Transmission menu (see para.14.5 on page 217).
Select the TP (Gmau) and open the PM Configuration dialog (see Figure 232. ) by clicking on the menu
item Transmission >Performance >Configure Performance Monitoring.
The Create Ethernet Counter window is opened (refer to Figure 239. on page 343)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
343 / 448
Select the TP and open the Current PM Data dialog (see from Figure 241. to Figure 242. ) by clicking
on the menu item Display Current Data.
The button Display Graph. allow to visualize the counter values in a graphical view but is not operative
in current release.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
344 / 448
Use menu item Add TP to display a special TP in the Transmission view (see para.14.5 on page 217).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
345 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
346 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
347 / 448
Select the TP (Gmau) and open the PM History Data dialog (see Figure 235. ) by clicking on the menu
item Display History Data.
The menu item Display History Data will be opened (refer to Figure 244. ):
In case of one hour history data, the showed values are the hourly historic data collected by NE.
If the NE has collected only one history data, the dialog shows directly counter values.
If the NE has collected more than one history data, the displayed counter values are calculated as
a difference from the older available history data value.
The older one will be added in the first line with the label and for each cell a tooltip will show the
history value received.
In the bottom of the dialog, the description of the showed counters value is dispalyed.
The layout of the dialog Display History Data is depicted in Figure 244. ; this dialog shows the numeric
value for each counter calculated as described before.
The button Display Graph. allow to visualize the counter values in a graphical view but is not operative
in current release.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
348 / 448
Use menu item Add TP to display a special TP in the Transmission view (see para.14.5 on page 217).
OUTGOING
INCOMING
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
349 / 448
This menu provide a NE global view for PM and Monitoring operations helps the operator to list these
resources.
Select the PM overview option from the Configuration menu (refer to Figure 245. ); the PM Overview
dialog will be opened (refer to Figure 246. )
PM/Monitoring Overview (PMO) dialog is able to show both PM and Monitoring objects.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
350 / 448
17.12 PM overview
the operator chooses a list of interesting TP using TP search; at the end fo this search operation then
operator moves such a list of TPs into PMO dialog.These TPs define a list of search roots for
Monitoring and PM.
[2]
the operator configure the filtering criteria in PMO and starts PM/Monitoring search oeprations using
the Show button in PMO.
The button area contains the following button (refer to Figure 246. ):
[1]
ADD TP: it starts the search operations using the TP Search dialog. Only TP references are moved
by TP search into PMO dialog. This is a precondition to start PM/Monitoring search operations, using
TP selected by TP search as search roots.
[2]
Show: it starts the search for PM/Monitoring objects in the MIB. according to the filtering criteria.
[3]
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
351 / 448
Preferences : it start the user preferences dialog. It is greyed out in USM not supporting this feature.
[5]
[6]
[7]
[8]
[9]
[10] Delete: it starts a request to remove the selected objects (monitoring and/or).
[11] Delete All: it destroys the TP list and make empty the TreeGadget
[12] Port View: it starts the Port View . PMO dialog is not closed after Port View or Port details dialog
opening.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
352 / 448
[4]
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
353 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
354 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
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 (OSC) is useful only in the abnormal functioning Freerunning mode
that will be explained later.
The simplified figure that follows represents the internal organization of the SETS.
Squelch
A
Selector
A
Selector
C
T4/T5 (**)
Squelch
B
T1
T2
T3/T6 (*)
Selector
B
SETG
T0
OSC
SETS
S15
NOTES:
(*) T3/T6 are not available on 1640FOX
(**) T5 is not available on 1640FOX
The number of timing reference inputs depends on the configuration of the NE.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
355 / 448
T0: is the reference output signal for the clock and signal frames,
T4: is the 2 MHz reference output for the external equipment synchronization.
T5: is the 2 Mbit/s reference output for the external equipment synchronization.
T5 reference clock is not available on 1640FOX
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/T6 inputs, according to the SSM
algorithm. The capability for manual selection of the timing source is also provided.
Selector C is only operated in manual mode, to switch between SETG output signal (T0) and a T1 timing
reference.
The squelch functions A and B mute the relevant timing references in the presence of failure condition,
or SSM threshold violation.
The choice of the timing reference is done in two ways:
Automatically:
Following a particular algorithm based on the quality and the priority of the incoming timing signals.
The automatic selection is based either on the priority of the incoming timing source (Priority
algorithm) or on the priority and the quality level of the incoming sources (SSM algorithm).
Manually:
Following an order from the Operator.
N.B.
The priority level is determined by the Operator for each candidate timing source. It is static
information. On the other hand, the quality of the source is dynamic information, dependant
of the quality of the reference clock generating the timing.
In an SDH signal frame, the quality of the timing source is located in the Section Overhead.
Locked mode:
The SETG output is fully controlled by the external timing references (T1, T2 and T3/T6).
HoldOver mode:
The external timing reference is malfunctioning. The SETG during normal functioning stores
regularly the value of the external timing reference. In this case the SETG output is controlled by this
memorized value.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
356 / 448
The operations that can be done on the synchronization sources are the following:
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
357 / 448
The Synchronization view shows the external timing reference sources and the T0, T4 or T5, generation.
The selection is based on the SSM algorithm or on the priority of the incoming timing sources. Activating
the SSM algorithm implies that the selection of the source is before done on the quality criteria and then
on the priority criteria for sources at the same quality level.
After selecting the Synchronization option from the Views menu the Synchronization View is visualized
in Figure 250.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
358 / 448
a timing reference associated to the Internal Oscillator timing source; it is always present
and it cannot be removed or redefined.
6 max timing reference for candidate inputs belonging to the allowable timing reference
T1, T2 or T3/T6 configurable by the operator.
T4 list contains :
6 timing reference for candidate inputs belonging to the allowable timing reference T1
configurable by the operator.
The T0 and T4/T5 lists are used for the management of reference timing source protection; a 1:n protection
like mechanism is used for the selection of the timing source from T0 (T4/T5) list of the allowable timing
references, . The protection system chooses the timing reference to generate the output T0 (T4/T5) either
automatically, basing on the priority and quality level of the candidate sources according a selection
algorithm or manually under control of the managing system.
View elements description
Here 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):
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
359 / 448
ED
Free Running, displayed when the clock operates in Free Running mode
Selectors
small ellipse are used to represent respectively:
the selector A;
the selector B;
the selector C;
Squelch Status
boxes contained a label field are used to represent the squelch statuses T0/T4 and T4. The box
dis plays the configured quality level threshold and it is lighted up when the output timing signal
is inhibited.
Output Signal
an arrow and a label field are used to represent respectively:
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.
SSU
box indicating a possible external SSU (Synchronization Source Unit).
Timing Generator
box indicating the status of the timing generator .
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
360 / 448
In the timing reference graphical object associated to the Internal Oscillator the following
information are displayed :
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
361 / 448
Input source
Quality level
Priority level
Click on the Input Source Choice field and then on its related button Choose; Figure 253. shows the
opened window, to search a TP as a source.
Following the TP Search procedure described in para.14.5.1 on page 217 ( rack, subrack, board, port )
enter the termination point (TP) value.
The valid TPs for timing reference are : EIS for electrical SDH ports, OpS for optical SDH ports, PPI for
2Mb/s ports.
This operation can be repeated for all the available empty synch. sources both for T0 clock and for T4
clock.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
362 / 448
When the configuration of the timing source is completed, click on the OK push button to validate the
choice and close the dialogue box. The Cancel push button cancels the configuration and closes the
dialogue box.
Positioning the mouse on the synch. source box Port# test, the corresponding physical interface
denomination (racksubrackboardport) is written on the window bottom left.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
363 / 448
Select the timing reference from the synchronization view. As in Figure 251. , select the Synchronization
pull down menu. You can then select the Protection Commands to open the Figure 254. Menu options
are greyed according to the current state of the selected timing source.
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/T5.
b)
General selection
A timing source can be selected manually or automatically. Furthermore, the selection of a particular
incoming timing source (except the internal oscillator) may be forced.
This selection is independent of the priority or quality of the timing source. If the timing source is lockout
or unavailable, this operation is impossible. A timing source is considered to be available if it is not lockout
and has not a failure condition or Priority level of 0.
The forced switch mode is terminated by releasing or inhibiting the force selected timing source.
The manual selection option is only possible if the quality and priority of the selected timing source are
sufficient. Otherwise the automatic selection algorithm overrules the manual selection.
If the previously manual selected timing source becomes unavailable the automatic selection is activated.
The Status indication describes the current synch. status (No Request, Automatic Switch, Failure, ...)
N.B.
The internal oscillator cannot be forced or manually selected.
From the dialogue box that opens, you can confirm or cancel the operation.
To perform or release a T0 or T4/T5 lockout, forced or manual selection, the following operations have to
be done:
Select the Protection Commands option then invoke/Release the Lockout, Forced or manual
Selection option.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
364 / 448
when T0 is selected to generate T4 (squelch B Figure 248. ): T0 may be squelched if all the
allowable timing references of Selector B have Quality Level lower than the programmable
threshold.
when T1 is selected to generate T4 (squelch A Figure 248. ) :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 the operator 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 to select the bit used (from #4 to #8) for SSM (refer to Figure 256. )
The Cancel button cancels the configuration and closes the dialogue box.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
365 / 448
Figure 255. Configuring the T0 or T4 SSM algorithm and the squelch criteria
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
366 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The Cancel push button cancels the configuration and closes the dialogue box.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
367 / 448
The SSU configuration command allows either to configure the single NE or the NE with SSU. In the last
case the SSU quality has to be defined.
SSU: Synchronization Source Unit, it is an external equipment that serves the NE for timing reference.
Selecting SSU Configuration from the Synchronization menu is Figure 257. is presented
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
368 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
369 / 448
This menu allows the change of the synchronization physical interface from 2Mhz (T4 ) to 2 Mbit/s (T5)
and viceversa.
NOTE: this menu is enable only if the SERGI board ( on 1650SMC) or SERVICE board (on 1660SM) is
present in the subrack.
Select Change T4 <> T5 from the Synchronization menu as shown in Figure 257.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
370 / 448
Click on ok to confirm; the new window display T5 instead of T4 (see Figure 262. on page 371)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
371 / 448
This menu is enabled only if the operator selects a protection unit which have as source a 2 MHz (T3)
or a 2 Mbit/s (T6) without traffic.
Select Change 2MHz >2Mbit from the Synchronization menu as shown in Figure 263.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
372 / 448
The label of the protection unit will be changed depending on the kind of source selected (see Figure 265.
on page 373):
If the selected protection unit is a 2 MHz, then the label will be changed into 2Mbit/s (2 Mbps
T6#A in the example of Figure 265. )
If the selected protection unit is a 2 Mbit/s, then the label will be changed into 2MHz (2MHz T3#A
for example)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
373 / 448
To connect T0 internal synch. select a synch. source and click on Synchronization > 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 266.
To separate T4 from T0 click on the Synchronization > 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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
374 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
375 / 448
Selecting any T1 or T2 Reference Source in the Synchronization View (Figure 250. ) hence the Show
Timing Source is enabled. This selection allows to analyze the input source considering its payload
structure and the related alarms (Port view is presented) .
Click on Show Timing Source of the Synchronization menu option. Figure 268. opens.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
376 / 448
19 MSSPRING MANAGEMENT
MSSPRING is a feature applicable only to 1660SM Equipment; it cannot be applicable
to 1640FOX and 1650SMC.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
377 / 448
In the following paragraphs 2Fiber advices are reported, to follow before to implement the MSSPRing
protection: there are some limitations concerning the aggregate types or the AU4s crossconnections to
be considered.
19.2.1 2Fiber MSSPRING connection configuration advices
ED
SNCP, 4 Fiber MS SPRING and MSP protection connections cannot be installed in a 2 Fiber
MSSPRING network. This leads to an unprotected connections installation.
AU4s from #9 to #16 dont 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 passthrough
in HVC connections must be the same through the node.
AU4 crossconnection line side, i.e. paths received from the line and loopedback to the same
line are not allowed.
Follow the Squelching Table Configuration in order to define the Squelching Table HO for
East and for West Side 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.
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
378 / 448
Activation procedure
a)
Create an MSSPRING 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 the same in all the nodes.
b)
In the Main dialog for MSSPRing 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 MSSPRing label > Protocol exception), will occur on those Ports connected
to the nodes not provisioned yet with the MSSPRing protection created (active).
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 MSSPRing active and No request state.
Deactivation procedure
a)
In the Main dialog for MSSPRing 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 MSSPRing label > Protocol exception), will occur on those Ports of the
activated nodes connected to the nodes just deactivated.
b)
In the Main dialog for MSSPRing 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 theRemove 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 NEs
adjacent to the node to be removed.
d)
e)
Connect the fibers and send the Release command of the relevant Force Ring to both NEs
adjacent to the removed node.
Adding a node
a)
In the Manage ring Map view insert the node in the selected position. Next nodes are automatically
shifted.
Modify the table in the Configure Squelch Table view according the new Ring Map.
Opening the View Protection Status Parameter screen, send Force Ring command to both NEs
adjacent to the node to be added.
Physically add the node and configure with 2Fiber MSSPRING activated with the right
configuration (Ring Map, Squelching table, WTR, Node Identifier).
Connect the fibers and send the Release command of the relevant Force Ringto both NEs
adjacent to the added node.
b)
c)
d)
e)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
379 / 448
In the current release the NE supports the MSSPRING protection as Terrestrial architecture.
The Transoceanic application with 4Fiber is not supported in current release.
For the 2Fiber Terrestrial application a max. of 16 nodes are available.
The available tables permit to visualize for the same NE the architecture 2 x 2Fiber.
Figure 269. shows the MSSPRing pull down menu.
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
380 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
381 / 448
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 272. opens and all commands are now available.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
382 / 448
It is possible to give an identification name to the schema by means of the Set Name command (refer to
Figure 273. on page 383).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
383 / 448
Click on Ring Map to configure the network node connection. Figure 274. opens.
The default association for a four node ring related to the fourth node (NodeId=3; Ring Position=4) is
depicted in Figure 275.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
384 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
385 / 448
The same WTR Time Ring must be set on each Node of the ring.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
386 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
387 / 448
AU4#1
AU4#2
West
East
West
East
B
AU4#1
AU4#2
AU4#3
AU4#2
AU4#3
AU4#3
East
East
West
West
AU4#1
AU
Number
1
2
3
west
A
Node
east
VC
VC
VC
4
5
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
388 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
389 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
390 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
391 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
392 / 448
During the activation procedure on different ADMs some of these can be in Active status , others in Inactive
status. The statuses, the protocol request and the protocol protection errors are described in the chapters
describing theMSSPRing Protection Status and Commands .
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
393 / 448
ED
02
span state boxes are not available (greyed) for the 2Fiber MSSPRing
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
394 / 448
In the MSPRing 2 Fiber configuration, the 18 working channels are inserted into the 916 protection
channels in the opposite side of the failure event as shown in Figure 291.
w/p
A
w/p
w/p
B
w/p
Ring Protection:
the working channels (AU4 1 to 8) are substituted
by the ring protection channels p (AU4 9 to 16)
( B on East side )
( A on West side )
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
395 / 448
The external protection commands are : Lockout, Force, Exercise (not operative in current
release),Manual, WTR.
The lockout commands disable the MSSPRing management.
The lockout section presents six lockout commands, four operative ( Figure 292. ). Each lockout
command is applicable on different points where the lockout actions has to be performed ( Figure 293. )
and any Lockout command is associated to a Release command to come back to the previous status.
Term Span identifies the section interested by the command, it doesnt assume the Span meaning of the
four fiber protection.
West
w
p
p
w
East
w
p
p
w
w= working (AU4 1 to 8)
p=protection (AU4 9 to 16)
Figure 293. Protection and working channels where the lockout command can be activated (2F)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
396 / 448
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 signalled 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 MSSPRing 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 headend when it receives back the protocol answer. Figure 294. shows the
association of tailend / tailend or headend / tailend.
Some network protection mechanisms are accepted or rejected depending on the end type (tail/head)
(lockout command,...)
w/p
w/p
X
w/p
w/p
Tailend
Tailend/Headend
Tailend
With the lockout protecting span command and a ring failure, the ring protection is served if this ring failure
occurred along the same section; the ring protection is disabled if the 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 not disable). See Figure 296.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
397 / 448
Lockout working
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
w/p
w/p
head
E
W
failure
W
B
E
tail
ring protection
Lockout working
failure
w/p
w/p
tail
W
E
W
B
head
E
no ring protection
Figure 295. Tailend / headend protection with a lockout working and a one direction ring failure (2F)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
398 / 448
W
no ring protection
ring protection
Lockout working
A
W
Lockout working
failure
w/p
w/p
E
Lockout working
failure
w/p
B
E
w/p
w/p
w/p
E
failure
failure
w/p
w/p
E
W
B
E
ring protection
B
E
no ring protection
Lockout working
failure
w/p
w/p
W
A
E
C
W
ring protection
Figure 296. Ring protection with a lockout and a ring failure (2F)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
399 / 448
ED
Combinations
of nonserved
failures and
external commands
02
W
E
3
B
w/p
w/p
A Node
A Node
Ring E
Lockout Working
Ring W
Lockout Working
E
2
ring protection on
the opposite side
if the ring failure
occurs between
AB or BC nodes
A Node
Ring E
Lockout Protection
w/p
w/p
ring protection on
the opposite side
if the ring failure
occurs between
AC or CB nodes
A Node
Ring W
Lockout Protection
Figure 297. 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 receiving ports.
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
400 / 448
The Force command ( Figure 298. ) 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 (Figure 299. ).
The Force Span command is not operative in 2 fiber MSSPring.
A
W
A1
E
W/P
w18
p916
w18
B1
W/P
p916
w18
w18
p916
p916
w18
w18
p916
p916
W
W/P
w18
p916
w18
p916
The Manual command is similar to Force command but it is at a lower priority level with respect to
automatic MSSPRing. 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 Protecting 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 300. visualizes the ring
protection with a Force/Manual command and a signal failure. FSR is for Force Switching Request,
SFR is for Signal Failure Request.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
401 / 448
w/p
w/p
E
W
E
A node is isolated
w/p
w/p
W
A
E
C
E
W
failure
w/p
w/p
E
B
E
A
E
W
ring protection for SFR
Figure 300. Ring Protection with Force and Manual commands (2F)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
402 / 448
A node
12 w. channels are
sobstituted by 34 p.
channels
B/S actions
w/p
34 w. channels are
sobstituted by 12 p.
channels
w/p
A
w/p
C
3
w/p
Clicking on the WTR command (of Figure 272. on page 383) next figure opens. If the WTR box, in the
Local Condition field of Figure 290. on page 394, 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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
403 / 448
Cs
Rs
Bs
when a command (Manual switch, Force switch) is neither served nor signalled, it is erased ( it is
not pending at the node)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
404 / 448
Reference point
clockwise
OS SN
SS SN
1
SS RN
OS RN
OS AN
2
W
SS AN
w/p
w/p
3
w/p
SS RN
w/p
OS RN
The automatic protection for dual ring failures is represented in Figure 306. Consider the network
reference scheme of Figure 305. with a tailend / headend alarm propagation. In this figure are depicted
the node switches for any reported double events.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
405 / 448
failure
w/p
E
4
W
SSAN
failure
failure
w/p
1
W
w/p
E
4
W
SSRN
3
failure
failure
w/p
1
failure
w/p
E
W
E
4
W
OSSN
3
failure
w/p
w/p
E
W
E
failure
W
4
W
OSAN
failure
w/p
1
E
w/p
4
W
OSRN
failure
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
406 / 448
w/p
Reference
point
Automatic Protection Ring
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Other
points
SN
SS
AN
Node 2 : isolated = Bs
Node 13 in switching for SF alarm =B
Node 4=intermediate
RN
SN
Node 1: isolated=Bs
Nodes 2,4 in switching for SF alarm=B
Node 3= intermediate
AN
RN
Node 2: isolated=Bs
Node 1,3 in switching for SF alarm=B
Node 4 = intermediate
OS
Figure 306. 2F Automatic protection (tail/head) for double ring failure visualization
The same reference Figure 304. and Figure 305. schemas are applied to describe dual generic Events
where both ring failures and external commands are considered.
The first row at the top of the protection table (Figure 307. ) shows the Events at the reference point. For
each of them the associated Event is listed on the first column at the left of the table.
Two manual ring commands can be only signalled: Bs (Manual SSSN and OSAN 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 SSSN. In this last case has to be considered the priority level. The behavior is that seen
for two automatic protection switching ( Figure 305. )
Lockout working SSSN has priority with respect to Manual, Automatic protection and Force commands.
In the other cases, both commands are served (B).
Lockout protection SSSN / OSAN and Manual or Automatic or Force command are both served
because the switching SSSN / OSAN channels are not managed by the lockout protection: B.
Lockout protection SSAN / OSSN overrides the Manual or Automatic or Force command because the
lockout protection controls the switching channels of the same Node.
Lockout protection SSRN / OSRN and manual or automatic or force command: the lockout protection
prevents the working 18 channels from being inserted into the protecting 916 ones. The lockout
protection is served, because it has a higher priority, the ring protection will be only signalled (pending).
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
407 / 448
Other
points
Automatic
Manual
Ring
Ring
Manual
OS AN
SN
RN
Force
Ring
SN
SS
AN
RN
SN
OS
AN
RN
Lockout Protecting
Lockout Working
SN
SS
AN
RN
SN
OS
AN
RN
SN
SS
AN
RN
SN
OS
AN
RN
Ring
Force
Ring
Lockout
Protection
Working
R
R
R
R
B
R
R
B
R
R
R
R
R
R
RCs
R
B
B
B
B
B
B
B
B
B
C
B
B
B
B
B
B
C
RCs
B
R
RCs
C
C
C
C
B
B
B
B
B
B
C
R
C
B
B
B
B
B
C
B
B
B
B
B
B
C
CRs
C
B
CRs
CRs
C
B
CRs
CRs
C
B
CRs
SN
SS AN
RN
Working
Bs
Bs
Bs
B
Bs
C
C
C
Reference
point
R
B
B
B
B
B
R
B
RCs
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
408 / 448
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 signalled= pending status ).
Automatic switching and external commands are revertive: then when the Events have been cleared,
the MSSPRing configuration comes back to its idle status.
The state boxes visualize the Node Condition Request as a consequence of the equipment/signal failure
or the external commands detected on the corresponding side (Event). The state boxes dont describe
the protection actions provided on the NEs.
The served Events ( B/S=bridges and switches are executed and the network has been updated ) are
completed B/S actions visualized as red box indications
The signalled Events ( the K1/K2 protocol communicates to the network nodes what has happened )
are pending B/S visualized as yellow box indications.
Figure 308. shows the protection status with a served East manual ring command. Any protection status
window is divided in different status fields: Schema description and status, Local Conditions, Node
Conditions and Protocol Exceptions. The first one describes the network configuration and application
type and its status, the second gives the local external commands indications, the third the Events results
on the nodes and the fourth one checks the k1/k2 ring protocol. The window is divided into three parts:
West, Middle and East. On the West there are all the box indications corresponding to the West protections
and commands. In the middle WTRRing refers to West and East sides, No Request corresponding
to Idle Status, and Intermediate Node denotes that the protections and commands dont 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 ADM1West ADM2 nodes, while the 3 and 4
nodes are Intermediate Node. The red color means that the command has been served. A regular
protocol Exceptions is represented with white boxes, a protocol alarm is signalled with red boxes. The
Prot. Unavailable indications are activated when a lockout protection command is applied in a network
node.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
409 / 448
Figure 308. Manual command applied at the Reference Point ring network Figure 305.
Figure 309. reports the Protection Status for external Force and Manual commands in a 3 node ring
(A, B, C). Figure 310. shows the lockout statuses and Figure 311. the automatic protection statuses.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
410 / 448
Force/Manual
Ring W
A
Force/
Manual
Ring
W
Force/
Request
Node
Ring
E
w/p
Request
Node
Ring
E
w/p
A
w/p
w/p
Request
Node
Ring
W
Node
Request
Node
Ring
W
Manual
Ring
E
Intermediate
Node Conditions
Force/Manual
Ring E
Node
Local Conditions
Intermediate
Reference
node: A
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
411 / 448
Lockout
Ring E
w/p
w/p
A
w/p
Lockout
Prot W
Node
Conditions
w/p
Lockout
Prot E
Prot. Unavailable
Lockout
Ring W
Intermediate
Node
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
412 / 448
Prot. Unavailable
Intermediate
Node
Prot. Unavailable
Local
Conditions
Lockout Working
Ring W
Prot. Unavailable
Reference
node: A
Request
Ring
E
w/p
Request
Ring
E
w/p
A
w/p
w/p
Request
Ring
W
Node
Request
Ring
W
Signal fail/degrade
Ring E
Intermediate
Node
Node Conditions
Intermediate
Signal fail/degrade
Ring W
Reference
node: A
The WTR status is visualized on the side where the link has been repaired. The considered network
failures are related to a tailend/headend node connection. The WTR Clear command can be executed
by the user without waiting the WTR setting time.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
413 / 448
Figure 312. Protection status with double ring failure (reference pointSSAN)
Figure 312. reports the protection status with double ring failure (reference pointSSAN. The node 2
isolated, the nodes 23 in switching and the node 4 Intermediate. The box color is white unless otherwise
specified:
Active: green
Request Node Ring West ADM3East ADM1: red (served)
Request Node Ring West ADM2East ADM2: yellow (pending)
Intermediate Node ADM4: red
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
414 / 448
Figure 313. Protection status with double ring failure (reference pointSSRN)
Figure 313. reports the protection status with double ring failure (reference pointSSRN). 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 ADM3East ADM1: red (switching for SF)
Request Node Ring East ADM4East ADM2: red (switching of the opposite nodes)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
415 / 448
Figure 314. Protection status with double ring failure (reference pointOSAN)
Figure 314. reports the protection status with double ring failure (reference pointOSAN). 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 ADM2East ADM1: red (switching for SF)
Intermediate Node ADM3ADM4: red
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
416 / 448
Figure 315. Protection status with double ring failure (reference pointOSAN) recovering to idle
Figure 315. reports the previous protection status with double ring failure (reference pointOSAN)
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 ADM2East ADM1: red
Intermediate Node ADM3ADM4: red
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
417 / 448
Figure 316. reports the protection status with double manual command (reference pointSSAN). Both
the commands can be only pending. The Request ring to 1,2,3 nodes becomes pending while the 4 node
is Intermediate node. The box color is white unless otherwise specified:
Active: green
Request Node Ring
Request Node Ring
Request Node Ring
Intermediate Node
ED
02
East ADM1 West ADM2: yellow ( pending ) for Manual Ring East ADM1
East ADM2 West ADM3: yellow ( pending ) for Manual Ring East ADM2
West ADM1 East ADM3: yellow ( pending ) for switching of the opposite nodes
ADM4: red
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
418 / 448
Figure 317. reports the protection status with double manual command (reference pointOSAN). Both
the commands can be served. The Request Manual ring to ADM1 (East) and to ADM2 opposite side
(West) collapses in the same manual command. Both the manual commands are served. The box color
is white unless otherwise specified:
Active: green
Request Node Ring East ADM1 West ADM2: red ( served )
Intermediate Node ADM3, ADM4: red
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
419 / 448
Figure 318. reports the protection status with a manual command and a lockout protection (reference
pointSSSN). Both the manual and the lockout commands are visualized to the same ADM1 node
(East). Both the commands are served because the bridge/switch points are different. The box color is
white unless otherwise specified:
Active: green
Request Node Ring East ADM1 West ADM2: red ( served )
Intermediate Node ADM3, ADM4: red
Manual Ring and Lockout Prot. commands East ADM1: red
Prot. Unavailable East ADM1 : red .
N.B.
The Prot. Unavailable is not propagated on West ADM2 node because on West ADM2 the
protection switching has been executed.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
420 / 448
Figure 319. reports the protection status with a manual command and a lockout protection (reference
pointSSRN). The manual command is pending while the lockout command is served. The box color
is white unless otherwise specified:
Active: green
Manual Ring command East ADM1: yellow
Request Node Ring East ADM1 West ADM2 : yellow ( pending )
Request Node Ring West ADM1 East ADM2 : yellow ( pending ) for switching of the opposite nodes
Lockout Prot. command: East ADM3 : red
Prot. Unavailable East ADM3 and West ADM4: red (served)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
421 / 448
Figure 320. Automatic working ring and Manual Ring (reference pointOSAN)
Figure 320. reports the protection status with a ring failure and a manual ring command (reference
pointOSAN). The automatic protection has a higher priority with respect to the manual command and
then it has been served. The box color is white unless otherwise specified:
Active: green
Request Node Ring East ADM1 West ADM2 : red (served)
Intermediate Node ADM3 ADM4 : red
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
422 / 448
Figure 321. Automatic working ring and Force Ring (reference pointSSAN)
Figure 321. reports the protection status with a ring failure and a force ring command (reference
pointSSAN). The ADM2 is isolated and the force command is pending. The box color is white unless
otherwise specified:
Active: green
Request Node Ring East ADM1: red (served) the West ADM1 switching is applied for SF
Request Node Ring West ADM3: red (served) the East ADM3 switching is applied for the force command
Request Node Ring West ADM2, East ADM2: yellow (pending) the ADM2 is isolated
Intermediate Node ADM4 : red
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
423 / 448
Figure 322. Automatic working ring and Lockout working Ring (reference pointSSSN)
Figure 322. reports the protection status with a ring failure and a lockout working command (reference
pointSSSN). The Lockout command has a higher priority with respect to the automatic protection
switching and then only the lockout command has been served. The box color is white unless otherwise
specified:
Active: green
Lockout Ring command East ADM1: red
Request Node Ring East ADM1 West ADM2 : red (served)
Intermediate Node ADM3 ADM4 : red
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
424 / 448
Figure 323. Automatic working ring and Lockout Protection (reference pointOSRN)
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. command West ADM3: red
Prot. Unavailable West ADM3 East ADM2 : red (lockout protection is served)
Request Node Ring East ADM1 West ADM2 : yellow (automatic protection is pending)
Intermediate Node ADM4 : red
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
425 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
426 / 448
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
b)
ISA IP Address Configuration ( Called ISA board IP Address) (not needed for ISAPR and
ETHERNET boards)
c)
ISA board TTPs creation (VC4XV , VC12XV, VC3XV, VC44c TTP, VC4 TTP, VC3 TTP, VC12 TTP,
s31 TTP, E1 TTP) (not needed for ISAPR board)
d)
TTPs crossconnection ( refer to paragraph 15.3 on page 270) (not for ISAPR board)
e)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
427 / 448
When the user 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 theCreate button.
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
428 / 448
In the following paragraphs will be explained how to create, delete and modify ISA board TTPs.
To delete a port the user can select a row and push Delete button.
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
429 / 448
PREA4ETH: up to 59 TPs (SDH VC4, SDH VC3, SDH VC12 ) with a maximum throughput of 622
Mbit/s.
PREA1GBE: up to 62 TPs (SDH VC4, SDH VC3, SDH VC12 ) with a maximum throughput of 622
Mbit/s.
Select ISA Port Configuration option from the Configuration menu to open the ISA ports Configuration
(see Figure 326. on page 430).
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.
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
430 / 448
It is possible to see the PR_EA Ports created as above explained by selecting the relevant row in the ISA
configuration window and then click on the Navigate button; Figure 327. on page 431 shows an
example.
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
431 / 448
On the FAST ETHERNET boards can be configurated up to 11 TPs (VC4 TTP, VC3 TTP, VC12 TTP,
VC12XV and VC3XV) on the port card (ETHMB) and up 14 TPs (VC4 TTP, VC3 TTP, VC12 TTP, VC12XV
and VC3XV) on the relevant access card (ETHATX).
Select ISA Port Configuration option from the Configuration menu to open the ISA ports Configuration
(see Figure 328. on page 432).
If the user want to change the port attribute association he can select a filled row, then in the Selected
Item section he can change the fields STM1 number and STM1 Time Slot and than push the Time
Slot Sw. button.
The Ctrl Path Act. button allows to change the state of the concatenated virtual VCs (example VC12XV
or VC3XV) that could be Idle or active.;
Click on Ctrl Path Act. button a new window will be opened (Figure 329. ); for details about the mening
of the field refer to paragraph 11.7.8 on page 165.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
432 / 448
To delete a port the user can select a row and push Delete button.
LCA
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
433 / 448
[1]
10/100Mbit/s Ethernet board (ETHMB)+GBIT Access (GETHAG); this feature is supported only
on 1650SMC and 1660SM.
With this architecture can be configurated up to 2 TPs (VC4XV TTP Type concatenation level=1) on
the GETHAG access card and up to 11 TPs (VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP, E1 TTP Type)
on the ETHMB main board taking into account that the maximum throughput must not exceed 622
Mbit/s.
[2]
GIGABIT board (GETHMB) standalone; this feature is supported on all OMSN (1640FOX,
1650SMC and 1660SM).
With this architecture can be configurated up to 4 TPs (VC4XV Type) on each board taking into
account that the maximum throughput must not exceed 622 Mbit/s in 1640FOX and 1650SMC (for
example it is possible to configure 1 port VC4XV with a max. concatenation level equal to 4 or as
alternative 4 ports VC4XV with concatenation level equal to 1).
The same rule above described are applicable to 1660SM when the GIGABIT board (GETHMB)
is equipped in normal slot (i.e. slot with a throughput of 622 Mbit/s).
In 1660SM are also available slot called enhanced (25, 26,28,29,34,35,37,38) where the
throughput per board is 1.2 Gbit/s.
If the GIGABIT board (GETHMB) is equipped in one of these slot it is possible to reach a max.
concatenation level equal to 7 per port ; of course this means that there is only one VC4XV with
concatenation level =1 available for another port and no resources for the last two ports present on
the board.
For more details read the Gigabit Ethernet description reported in the Technical Handbook.
The Gigabit Ethernet TPs creation follows the same rules described for the 10/100Mbit/s Ethernet Board;
refer to paragraph 20.2.3.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
434 / 448
On the ISA ES18FE up to 8 among VC4 TTP, VC3 TTP, VC12 TTP, VC12XV (XMAX= 21), VC3XV
(XMAX= 2)
On the ISA ES18FX up to 8 among VC4 TTP, VC3 TTP, VC12 TTP, VC12XV (XMAX= 21), VC3XV
(XMAX= 2)
According to the settings made in the Equipment Set procedure (SMII or GMII), the board ISA
ES48FE can be configured with the following TPs:
ISA ES48FE SMII mode: up to 16 TPs among VC4 TTP, VC3 TTP, VC12 TTP, VC12XV
(XMAX= 50), VC3XV (XMAX= 2), VC4XV (Xmax=1).
SA ES48FE GMII mode: up to 2 TPs among VC4 TTP, VC3 TTP, VC12 TTP, VC12XV (XMAX=
63), VC3XV (XMAX= 12), VC4XV (Xmax=4).
On the ISA ES16 (not available on 1640FOX) up to 16 among VC4 TTP, VC3 TTP, VC12 TTP,
VC12XV (XMAX= 63), VC3XV (XMAX= 12) , VC4XV (XMAX= 8)
Select ISA Port Configuration option from the Configuration menu to open the ISA ports Configuration
(see Figure 332. on page 436).
Figure 331. Example of Ethernet Switch (ES18FE) TPs creation (EMPTY FIELDS)
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
435 / 448
Figure 332. Example of Ethernet Switch (ES18FE) TPs creation (WITH DEFEINED TPS)
The ISA ports Configuration window is filled with notebook pages (initially blank), each page is an ES, ATM
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 ISA ports already created) via the 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 theCreate 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.
1AA 00014 0004 (9007) A4 ALICE 04.10
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
436 / 448
The LCAS Cfg.. button allows to Enable / Disable the LCAS scheme protocol selecting the relevant button
(refer to paragraph 11.7.9 on page 167).
The Ctrl Path Act. button allows to change the state of the concatenated virtual VCs (example VC12XV
or VC3XV) that could be Idle or active.;
Click on Ctrl Path Act. button a new window will be opened (Figure 329. ); for details about the mening
of the field refer to paragraph 11.7.8 on page 165.
To delete a port the user can select a row and push Delete button.
To close the dialog box click on the Close push button.
It is possible to see the VCs created on the ETHERNET SWITCH board as above explained by selecting
the relevant row in the ISA configuration window and then click on the Navigate button; Figure 330.
on page 433 shows an example.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
437 / 448
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
438 / 448
LCA
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:
A backup/restore can be also done on the MIB of the NE. Indeed the MIB can be saved to or restored
from the mass storage of the Craft Terminal.
The software download general principle is represented in the following figure.
Software Management
OPERATOR
MANAGER
Download
Control
Event
Report
AGENT
NE
Software Downloading
OPERATOR
Transfer
Request
SERVER
CLIENT
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
439 / 448
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.
Two main functions are involved in the software downloading:
The Software Download Server is only responsible for fulfilling the requests received from NEs and
performing software package file transfer operations to the NE.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
440 / 448
The naming conventions used for Download Management are the following:
Two main different operative condition are defined for this Equipment:
In order to migrate from Release 1.1A to a Higher Release, the download procedure requires
two steps. The first is from 1.1A to 1.1X (intermediate package) and the second is from 1.1X
to the Higher Release (e.g. 1.1B1).
In order to update the following procedure is to be done as explained in the next steps:
a)
Install on the PC the NE Software Package present in the CDROM (refer to 1320CT Basic
Operators Handbook for details).
b)
open a session on Craft Terminal application (startup of the application, start supervision and NE
login)
c)
e)
Select the new software package in the server and triggers the download process, as presented at
para.21.4 on page 443.
A message will indicate the completed download.
f)
g)
h)
If problems are found with the new activated package, activate the previous software package
(revertback operation) to come back to the previous condition and then try to repeat the procedure.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
441 / 448
All the software download operations are carried out from the software download manager.
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:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
442 / 448
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.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
443 / 448
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
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
444 / 448
Click on the OK push button to start the download. From the confirmation dialogue box that opens, you
can confirm or cancel the download. If you confirm the operation, the SW Downloading dialogue box then
disappears and the Software download in Progress dialogue box is displayed (see Figure 339. ) from
which you can if necessary abort the software download.
You can monitor the download progress by means of the Software in Progress dialogue box which also
enables you to possibly abort the current download.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
445 / 448
Select the Activate option of the CurrentState\Action field, to activate the Software package
The Sw units Det. button allows to give more information about a selected software package.
Clicking on it, the following window is displayed:
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
446 / 448
Available backups on local server: gives the list of the backups available on the Craft Terminal,
Backup name: to enter the new backup name.
Three push buttons allow to choose the action with click on:
Backup: performs the backup on the CT of the Mib present on the NE,
Restore: this function allows the managing system to restore the NE configuration database of the
managed system. Only one restore operation can be performed at the same time on a given NE.
Delete: this action allows to delete a backup of the NE database. The NE is not involved in this action.
The only effect is to delete the selected backup version stored in a specific directory of the FT server.
To activate an already restored MIB you click on Activate push button. Only at this point it becomes
operative on the NE.
To exit of the NE MIB management window, you click on Close push button.
To save or load the Mib to/from an external disk follow the indication of the Basic 1320CT Operators
Handbook using the menu options of the Network Element Synthesis.
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
447 / 448
END OF DOCUMENT
ED
02
SC.3:NE MANAGEMENT
3AL 91670 AA AA
448
448 / 448
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5
5
5
5
2 MAINTENANCE INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Maintenance of the PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Problems with Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Purpose of the procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
8
8
8
8
9
9
9
13
17
18
19
20
22
30
37
40
43
44
47
49
50
52
56
02
050414
01
041119
ED
DATE
ECR 23082
CHANGE NOTE
C. FAVERO ITAVE
J.MIR S.MAGGIO
C. FAVERO ITAVE
J.MIR S.MAGGIO
P.GHELFI ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
P.GHELFI ITAVE
METRO OMSN
Rel. 4.4/5.2A
OPERATORS HANDBOOK
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
1 / 76
58
58
59
60
61
61
65
69
69
71
74
ED
02
67
67
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
2 / 76
14
15
16
18
19
22
22
31
32
33
34
35
38
38
39
40
41
42
43
44
45
46
47
51
53
54
55
56
57
62
64
66
70
72
73
75
TABLES
Table 1. Alarms colors and Severity association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. Alarm Synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. Domain Alarm Synthesis indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Management States Control Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 5. Alarm Surveillance information general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6. General aspect of alarms meaning and relevant maintenance actions . . . . . . . . . . . . . . . .
Table 7. Boards alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8. Module alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
20
21
21
23
24
25
29
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
3 / 76
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
4 / 76
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
1 INTRODUCTION
1.1 Scope
1.1.1 Document scope
The Maintenance Manual mainly describes the NE troubleshooting with Craft Terminal.
1.1.2 Target audience
The Maintenance Manual is intended for all users.
The documents that should be read before starting this document are:
The documents of this Handbook that should be read before starting this document are:
Introduction manual
NE Management manual
1.2 Terminology
1.2.1 Acronyms and abbreviations
Refer to the Section Introduction manual.
1.2.2 Glossary of terms
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
5 / 76
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
6 / 76
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2 MAINTENANCE INTRODUCTION
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
7 / 76
The same window is displayed pressing he keys <Ctrl> + <Alt> + <Del> simultaneously.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
8 / 76
QECC interface for Telecommunication Management Network (via DCC channels, linked to
the relevant OS)
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 :
[1]
[2]
[3]
[4]
on site
[1] 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).
[2] 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.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
9 / 76
T URGENT (MAJOR and CRITICAL), T NOT URGENT (MINOR): remote alarms pertaining to
the urgent, not urgent alarm type.
TOR, TAND: remote alarms respectively due to the decrease or loss of one or both station
power supply DC voltages.
INT: Remote alarm pertaining to the local (internal) alarm type
When a second CONGI unit is used the following remote alarms are added:
TORC, TANC: remote alarms respectively due to the loss of +3,3V generated by the on board
converter in of one or both the CONGI units.
IND: Indeterminate alarm synthesis. Indicates synthesis of alarms not associated to others
severities. Not operative.
TUP: remote alarm due to microprocessor fault in the EQUICO unit (for 1660SM), PQ2/EQC
unit (for 1660SM Rel. 5.1) or SYNTH1N/SYNTH4 unit (for 1640FOX,1650SMC)
LOSQ2: remote alarm due to loss of communication with Mediation Device. Not operative.
1640FOX
T URGENT (MAJOR and CRITICAL), T NOT URGENT (MINOR): remote alarms pertaining to
the urgent, not urgent alarm type.
INT (MAJOR or CRITICAL): Remote alarm pertaining to the local (internal) alarm type
INTALM (WARNING): Remote alarm due to alarm detection from the external Converter
SR40R.
TAND (MAJOR or CRITICAL): remote alarm due to the loss of power supply (batteryfail or
3.3VService fail).
FANSOFF1 (WARNING): remote alarm due to failure of FOX fans.
FANSOFF2 (WARNING): remote alarm due to failure of external Converter (SR40R) fans.
Depending on the supervisory center organization, it is possible to locate the equipment in troubles and
to detect the failure type and source.
2)
the equipment is not reachable by the remote manager (TMN or RCT) and is therefore isolated
3)
4)
In case 1 ) , 2 ), 3 ), the alarmed equipment is checked by means of the local Craft Terminal and of rack
LED indications and station buzzers.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
10 / 76
[3] Station supervisory center: the maintenance technician refers to the Remote Alarms received from
the equipment in a centralized office of the station i.e. :
Units Alarms:
Each port card or access card of the equipment is provided with a bicolor LED (green/red) or multicolor
LED (green/red/yellow) at the bottom of the front coverplate.
Bicolor LED indicates:
when red, internal failure (indicates that the unit concerned must be replaced)
when red, internal failure (indicates that the unit concerned must be replaced)
when yellow, means that the unit is part of an EPS schema and its status is standby (only available
on 1650SMC and 1660SM)
Red LED: detection of an INTERNAL alarm (rectifier failure or rectifier fans failure)
Yellow LED: battery charging
Red LED: AC mains off (missing of AC power)
Green LED: rectifier is operating
All the alarm detected on the unit are related to the ATM traffic management; on the front coverplate are
present optical indication (LEDs) with the following meaning (from the top to the bottom):
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
11 / 76
All the alarms detected on the units are collected by the Controller unit (called EQUICO in 1660SM,
SYNHT1N or SYNTH4 in 1640FOX/1650SMC) unit which will deliver centralized optical indications (by
means of LEDs on its front coverplate). Specifically, from the top to the bottom :
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 EQUICO, PQ2/EQC,
SYNTH1N, SYNTH4 unit.
This condition causes:
On the rack
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
12 / 76
The troubleshooting operation proceeds according to the information indicated in the flowcharts:
The flowcharts/tables should be also consulted when the unit LEDs flash, because the flashing condition
might be due to external alarm causes usually related to line problems.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
13 / 76
AN ALARM
IS PRESENT
IS THE
NO
CONTROLLER (*)
BICOLOR LED RED?
IS THE
CONTROLLER(*) UNIT
NO
YES
THROUGH PUSHBUTTON
IS
NO
DOES
THE ALARM
CONDITION
PERSIST ?
NO
TRANSITORY
FAILURE
YES
YES
END
YES
END
IS THE
NO
YES
END
NOTE:
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
14 / 76
START
WARNING!
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Before removing CONGI unit from subrack, switchoff the relevant Station Battery Fuse Breaker
present at the top of the Rack or in the Station Distribution Frame; subsequently remove the
station battery cable if necessary and then extract the CONGI unit.
START
IS
REMOTE ALARM
TAND PRESENT ?
(N.B.)
NO
YES
STATION POWER
SUPPLY FAILURE
YES
ARE LEDS ACTIVE?
TRANSITORY
OVERLOAD
YES
END
NO
REMOVE ALL THE UNITS
FROM THE SUBRACK
AND SUBSTITUTE THE FUSE
IF NECESSARY.
INSERT THEM BACK ONE
AT A TIME TILL THE ONE
CAUSING THE FAILURE IS DETECTED.
HENCE REPLACE IT.
SUBSTITUTE THE FUSE
IF NECESSARY.
END
N.B.
IF THE REMOTE ALARMS ARE NOT UTILIZED CHECK FOR PRESENCE OF STATION POWER SUPPLY.
SHOULD IT HAVE FAILED THEN ALL THE UNITS LEDS WILL BE OFF (FOLLOW OUTPUT YES OF THE
FLOWCHART).
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
15 / 76
START
IS
REMOTE ALARM
TAND PRESENT ?
(N.B.)
NO
YES
STATION POWER
SUPPLY FAILURE.
OR AC/DC RECTIFIER
FAILURE
END
END
N.B.
IF THE REMOTE ALARMS ARE NOT UTILIZED, CHECK FOR PROBLEMS ON STATION POWER SUPPLY (OR ON
AC/DC RECTIFIER)
SHOULD IT HAVE FAILED, THEN ALL THE UNITS LEDS WILL BE OFF (FOLLOW OUTPUT YES OF THE
FLOWCHART).
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
16 / 76
An example of alarms/status view organization is shown in Figure 5. pg. 19. Observe the active
alarms on the Severity Alarm Synthesis, Domain Alarm Synthesis and Management States
Control Panel always present on the window (it resumes all the NE alarms).
Table 2. on page 20 describes the meaning of these alarms/statuses and the relevant maintenance
actions.
b)
in case of alarm presence, access the Alarm Surveillance to troubleshoot. This application gives
the details of the detected alarms and helps for their localization.
Para 3.4.4 on page 22 describes this view.
c)
It is possible to analyze the detailed alarm presence on the TPs of each ports of the NE, following
the indication of para 3.4.5 on page 30.
d)
It is also possible to check alarm and status at Board view, Subrack view and Equipment view
are also supplied following the indication of para 3.4.6 on page 37 and para 3.4.9 on page 44.
e)
Eventual housekeeping alarms can be localized following the indications given in para. 3.4.10 on
page 47.
f)
These above said paragraphs describe general aspect of alarms meaning and relevant maintenance
actions that can be done with the information given in the applications.
g)
The history of past events can be obtained by means of the Event log option of the Diagnosis pull
down menu (see NE management section).
In case of unit replacement, follow the indications reported in Chapter. 4 on page 49.
Troubleshooting with Automatic Laser Shutdown
The Automatic Laser Shutdown (ALS) is used to protect the operator who is working with the optical fiber.
When the ALS is active, it may be difficult to detect the link failed.
To locate it, it is necessary to force on the ALS, thus enabling the optical power transmission on the
opposite direction of the failed link.
WARNING: During this phase the operator has to pay attention when working with fibers and connectors.
The ABNORMAL indication inform the operator of the ALS forced condition.
After having completed the maintenance, enable the ALS.
The ALS states are indicated in the port view, as described in para. 3.4.5 on pg. 30.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
17 / 76
The following concepts and definitions are considered useful to facilitate maintenance operations with the
aid of the previously indicated tables.
The various units specified in the synchronous multiplexing hierarchy imply structuring the Transmission
network into three levels (sublevels of the physical OSI level):
Transmission bearer level. It is the support for the path level and can be further split into physical
level (Transmission media) and Transmission section level. The sections can be either regenerator
or multiplexer and utilized for specific functions associated to the EOW channels of the SDH frame.
The interface alarms (or section alarms, indicated in the tables) belong to this level (example: Line
LOS, LOS, B2etc.).
Path level It concerns the data transfer between the access points and the path. It does not depend
on the service nor on the type of Transmission media. It constitutes the circuit level support. The path
can be either lower order (LO) or higher order (HO) depending on the capacity of data transferring.
Like the regenerator and multiplexer sections, the paths too have specific functions associated to the
EOW channels of the SDH frame. The alarms listed in the cited tables, where path level
troubleshooting is required, belong to this level (example:TUAIS, TU LOP).
Circuit level. This level concerns the transfer of information between the access points and the
circuit proper. It is a direct support for the telecommunication services. It superimposes the SDH
function and is considered as the transport agent hence no SDH orderwire channel associated
functions are required. An example of this level alarm is Tributary LOS.
G.703
STMN
G.703
SDH
MUX
STMN
TRIBUTARIES
SDH MUX
STMN
SDH MUX
TRIBUTARIES
REGENERATOR
RSOH
REGENERATOR
SECTION
RSOH
REGENERATOR
SECTION
MSOH
MULTIPLEXER
SECTION
MSOH
MULTIPLEXER
SECTION
MSOH
MULTIPLEXER
SECTION
POH PATH
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
18 / 76
Severity alarms
synthesis
Menu bar
View title
LCA
Boards
Alarms
View area
Message/status area
Administrative
state indications
Management
status control panel
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.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
19 / 76
The alarms CRI, MAJ, MIN, WNG, IND are part of the Severity Alarms Synthesis area, presented in
Table 2. on page 20.
The alarms EXTP, EQP, TRNS are part of the Domain Alarms Synthesis area, presented inTable 3. on
page 21.
The alarms SUP, ALI, LAC, COM, OS, MGR, NTP and AC are part of the Management States Control
Panel, presented in Table 4. on page 21.
All these indications (except for SUP, ALI, 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: 3.4.4, 3.4.5, 3.4.6, 3.4.7, 3.4.10.
Table 1. reports the association between the colors of the Alarms and their Severity.
For the Domain Alarms Synthesis the color corresponds to the highest severity among the set of the
active alarms for the relevant domain, according to the same rules of previous Table 1.
Table 1. Alarms colors and Severity association
Alarm Color
RED
Severity
CRITICAL
ORANGE
MAJOR
YELLOW
MINOR
CYAN
WARNING
WHITE
INDETERMINATE
GREEN
NO ALARM
Maintenance
CRI
Critical alarm
MAJ
Synthesis of alarms that needs immediate troubleshooting. NB1. See detailed indication in the following para.
MIN
Warning alarm
Indeterminate alarm
WNG
IND
ED
Alarm/Status Description
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
20 / 76
Mnemonic
EXTP
External Point
(Housekeeping alarm)
SYNC
Synchronization alarm
EQP
TRNS
Equipment alarm
Transmission alarm
Maintenance
Check the relevant station alarm associated to the
input housekeeping indication. See detailed indication
in the following para.
Synthesis of alarms of the Synchronization domain.
See unit detailed indication in the following para.
Synthesis of alarms of the Equipment domain.
See unit detailed indication in the following para.
Synthesis of alarms of the Transmission domain.
See unit detailed indication in the following para.
Supervision state
ALI
Alignment state
(not operative on Craft
Terminal)
LCA
COM
NE unreachable/unreachable
MGR
Manager level
NTP
AC
ED
Description
SUP
OS
Alarm/Status Description
02
Abnormal Condition
Maintenance
GREEN: NE is under supervision.
BROWN: NE is not under supervision.
Used in the OS.
GREEN: configuration is aligned (is equal between
EML manager and NE MIB).
ORANGE: configuration is not aligned (is not equal
between EML manager and NE MIB).
GREEN: Indicates that the Craft Terminal has the OS
permission to manage the NE (Granted).
CYAN: Indicates that the Craft Terminal has not the
OS permission to manage the NE (Denied).
BLUE: Indicates that the Craft Terminal has requested OS permission to manage the NE (Requested).
GREEN: Identifies the Enable operational state of
the connection between NE and Craft Terminal (SDH
service link up)
RED: Identifies the Disable operational state of the
connection between NE and Craft Terminal (SDH
service link down)
GREEN: Indicates that the N.E. is not managed by the
1353SH
CYAN: Indicates that the N.E. is managed by the
1353SH.
GREEN: Indicates that the N.E. is not managed by
the 1354RM
CYAN: Indicates that the N.E. is not managed by the
1354RM
GREEN: NTP protocol enabled and both NTP servers
(main and spare) are unreachable.
BROWN: NTP protocol disabled.
CYAN: NTP protocol enabled and at least one NTP
servers (main or spare) are reachable.
GREEN: normal operating condition.
CYAN: detection of an ABNORMAL operative condition. Type: active loopbacks, forcing the unit into service, laser forced ON or OFF, try to restore after ALS
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
21 / 76
Alarm Severity Assignment Profile can modify the assignment of each alarm root to the various
synthesis.
In case of alarm presence, access the Alarm Surveillance (AS) to troubleshoot. For this purpose
select the Diagnosis pull down menu. With the Alarm pull down menu (see Figure 6. ). It is possible
to show all the NE Alarms or filter the alarms report, for example displaying only the alarms of a
specific domain (i.e. only alarms of the Equipment domain).
LCA
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
22 / 76
NB1:
TITLE
DESCRIPTION
Perceived Severity
The severity assigned to the alarm is indicated, with the relevant color,
i.e.: MAJOR, MINOR, WARNING....
Friendly Name
Identify the rack, subrack, board, port, and TP in which the alarm is detected,
i.e.: / r01sr1sl09/#port01E1S
Event Type
Indicates the family type of the alarm as subdivided in the ASAP list, i.e.:
EQUIPMENT, COMMUNICATION,
Probable Cause
The fault/problem is indicated, i.e.: loss of signal, transmitter degraded, replaceable unit missing,resource isolation, ...
Reservation Status
Clearing status
Acknowledge status
Indicates if the alarm has been acknowledge (ACK) with the button on the
Controller unit ( EQUICO/ PQ2/EQC / SYNTH1N / SYNTH4) or not ( NACK).
Correlated notification
Not used
flag
Repetition counter
Not used
The information supplied help the operator during the troubleshooting operation.
Table 6. on page 24 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.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
23 / 76
PROBABLE CAUSE
NAME AND/OR ACRONYM
OF DISPLAYED ALARM
MAINTENANCE
Check line
Replace unit
AIS
Check line
Configuration error
Resource Isolation
Communication Subsystem
Isolation (CSF)
Unequipped (U)
Referred to Signal Label
Configuration error
Unconfigured Equipment
Present (UEP)
Internal Communication Prob- Reset NE. If persists substitute EQUICO / PQ2/EQC SYNTH1N /
lem
SYNTH4 unit according to the NE type.
URU Underlying Resource
Insert the board
Unavailable
PM_AS Performance
Monitoring Alarm Synthesis
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
24 / 76
PROBABLE CAUSE
NAME AND/OR ACRONYM
OF DISPLAYED ALARM
AUXP
Unit missing
(RUM)
Unit Problem
(RUP)
MAINTENANCE
ED
02
BOARD
ACRONYM
A2S1
A21E1
A3E3
A3T3
A4ES1
AFOX
ETHATX
ETHMB
GETHAG
HPROT
L41
L41N
L42
L42N
M4E1
M1E3
M1T3
P3E3/T3
P4ES1N
P4S1
P4S1N
P21E1
P21E1N
P21E1NM4
P63E1
P63E1N
P63E1NM4
S41
S41N
ES18FE
ES48FE
SERVICE
COADM1
COADM2
COWLA2
COMDX8
MAINTENANCE
Replace unit
Insert right unit (unit inserted into a slot set with another type of
unit)
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
25 / 76
Unit Problem
(RUP)
BOARD
ACRONYM
EQUICO
PQ2/EQC
Unit missing
(RUM)
Replace unit
Unit Problem
(RUP)
Replace unit
Insert right unit (unit inserted into a slot set with another type of
unit)
PR16
Power Problem
(POP)
Replace unit
Pump failure
(PF)
Replace unit
Check that the protection cover in front of the unit has been correctly placed.
Unit missing
(RUM)
Unit Problem
(RUP)
Unit type mismatch
(RUTM)
MAINTENANCE
Replace unit
BST10
BST15
BST17
Insert right unit (unit inserted into a slot set with another type of
unit)
Pump failure
(PF)
Replace unit
Check that the protection cover in front of the unit has been correctly placed.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
26 / 76
NAME AND
ACRONYM
OF DISPLAYED
ALARM
NAME AND
ACRONYM
OF DISPLAYED
ALARM
BOARD
ACRONYM
Unit missing
(RUM)
Unit Problem
(RUP)
Unit type mismatch
(RUTM)
GETHMB
ES18FE
ES18FX
ES48FE
ES16
Replace unit
Insert right unit (unit inserted into a slot set with another type of
unit)
Internal
communication
problem
(ICP)
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
Unit missing
(RUM)
Unit Problem
(RUP)
Unit type mismatch
(RUTM)
Version Mismatch
Internal
communication
problem
(ICP)
Unit missing
(RUM)
Unit Problem
(RUP)
Unit type mismatch
(RUTM)
High Laser
Temperature
(HLT)
MATRIX
MATRIXN
MATRIXE
PREA1GBE
PREA4ETH
ATM8X8
ATM4X4
SYNTH1
SYNTH1N
SYNTH4
S161
S161N
S161ND
L161
L161N
L161ND
L162
L162N
L162ND
I161ND
MAINTENANCE
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
Replace unit
Insert right unit (unit inserted into a slot set with another type of
unit)
Replace unit
Unit missing
(RUM)
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
27 / 76
BOARD
ACRONYM
MAINTENANCE
Unit missing
(RUM)
Unit Problem
(RUP)
Replace unit
Insert right unit (unit inserted into a slot set with another type of
unit)
CONGI
LAN problem
(LAN)
Battery Failure
(BF)
Fuse Failure
(FF)
Unit missing
(RUM)
Unit Problem
(RUP)
Replace unit
SERGI
Insert right unit (unit inserted into a slot set with another type of
unit)
Battery Failure
(BF)
Fuse Failure
(FF)
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
28 / 76
NAME AND
ACRONYM
OF DISPLAYED
ALARM
NAME AND
ACRONYM
OF DISPLAYED
ALARM
Unconfigured
Equipment Present
(UEP)
ED
02
MODULE
ACRONYM
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
MAINTENANCE
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
29 / 76
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 8. to Figure 12. are examples of 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); refer
to Figure 11. and Figure 12.
A message under the mouse indicator provides the name of the alarm or object on which it is located, in
this way facilitating the identification of the alarm or status or object.
The nonalarmed condition of an alarm icon is represented by a green color and a sign in the box.
The alarmed condition is represented by the color of its severity (as assigned by the ASAP) and an X
sign in the box.
The alarms which can be found in the Port view are listed in Table 7. on page 25, where the relevant
maintenance actions are reported too.
The information regarding ALS states and Laser state useful for operators safety purpose are
reported in the following:
ALS states:
Inactive = No ALS has been activated (Off) or the laser has been Forced ON/OFF.
In test = The laser restart has been automatically activated .
Active = The ALS has been activated (On).
Undefined = The ALS is not present (not created).
Laser state:
On = all OK or ALS not present (not created).
Off = Laser off (when ALS is created).
Forced on = ALS forced on by operator command.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
30 / 76
Alarms
TPs
Alarms
Mouse message
Protection message
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
31 / 76
Alarms
TPs
Alarms
Mouse message
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
32 / 76
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Alarms
TPs
Mouse message
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
33 / 76
LCA
Alarms
TPs
Mouse message
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
34 / 76
Alarms
LCA
TPs
Alarms
TPs
Mouse message
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
35 / 76
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
36 / 76
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The alarms which can be found in the subboard view are listed in Table 6. page 24, where the relevant
maintenance actions are reported too.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
37 / 76
daughters
Administrative State
Board alarms
Administrative State
Board alarms
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
38 / 76
Administrative State
ED
02
EPS State
Board alarms
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
39 / 76
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).
Figure 16. and Figure 17. are examples of Subrack and Rack view.
An alarm box is displayed on each board, to indicate whether the board is alarmed. This board alarm summarization is activated when one of the board alarms (those reported at the bottom of the Board view) is
active.
A lock symbol on a board indicates that it is inservice. Else, the lack of this symbol indicates its outof
service state . (Administrative State information).
A message under the mouse indicator provides the name of the alarm or object on which it is located, in
this way facilitating the identification of the alarm or status or object.
Severity alarms
synthesis
Menu bar
View title
LCA
Boards
Alarms
View area
Message/status area
Administrative
state indications
Management
status control panel
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
40 / 76
Severity alarms
synthesis
Menu bar
View title
LCA
View area
Fans subrack
Alarms
Administrative
state indications
Management
status control panel
Message/status area
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
41 / 76
To obtain Fan Subrack alarms indications click twice with the mouse on the relevant subrack drawing
in the rack level view.
Figure 18. on page 42 is presented:
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#10 for 1660SM or Connected FAN to
CONGI#5 for 1650SMC)
Fans subrack can only be connected to CONGI#10 in 1660SM
and CONGI#5 in 1650SMC.
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.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
42 / 76
RLV (Rectifier Low Voltage): it indicates loss of AC power > Check AC connection.
BC (Battery Charging).
RCF (Rectifier Failure): it indicates internal fault, or fans failure >
if the remote alarm FANSOFF2 is active, then replace the rectifier fans, as
stated in Technical Handbook.
otherwise, if the remote alarm FANSOFF2 is not active, then replace the AC/
DC Rectifier (in this case all the traffic will be lost).
BD (Battery Degraded) > replace the batteries, as stated in Technical Handbook.
RUM (Replaceable Unit Missing) > check the Rectifier alarms connection.
LCA
Rectifier alarms
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
43 / 76
The alarm indications at Equipment level can be obtained, following the indication of the Equipment View
chapter on the previous Section of this Handbook.
Figure 20. shows the Equipment view, with the alarm indications presented:
Substitute the fuse in the CONGI unit and search for a cause.
Specific Hardware Diagnostic (SHD): 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.
Equipment alarms
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
44 / 76
Fuse Failure
Substitute the fuse in the CONGI or SERGI unit and search for a cause.
Specific Hardware Diagnostic (SHD): Indicate the presence of link failure between the SYNTH1N /
SYNTH4.
ADM and one of the units; for details choose the Internal Link Monitor
option of the Diagnosis menu.
Equipment alarms
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
45 / 76
The alarms indications at Equipment level can be obtained selecting, on the menu bar, the items:
Views > Equipment and then Equipment > Show Supporting Equipment.
Figure 22. shows the Equipment view, where the following alarms indications are displayed
(FF, ABF, BKF alarms are not used):
Specific Hardware Diagnostic (SHD): it indicates the presence of link failure between
the SYNTH1N /SYNTH4 unit and one of the other units; for details check
the fault by means of the Internal Link Monitor option of the Diagnosis
menu.
Equipment alarms
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
46 / 76
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
47 / 76
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
48 / 76
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
No particular indication is given as to spare handling which is left to the Maintenance Administration.
The replacement procedures are executed as follows:
Hardware set the spare unit exactly as the unit to replace. Settings are specified in the MS documents. Here a layout figure indicates the exact location of all the setting arrangements and a table
relate the operations to achieve with the settings.
The cited documents are enclosed in the Technical Handbook.
Simply replace those units not provided with any software settings
With regard to the EQUICO / PQ2/EQC unit refer to paragraph 4.1 on page 50.(Only for 1660SM)
With regard to the COMPACT ADM (also called SYNTH1, SYNTH1N, SYNTH4) unit refer to paragraph 4.2 on page 52.(Only for 1650SMC and 1640FOX)
With regard to the ATM MATRIX 4X4 and 4x4 V2 units refer to paragraph 4.3 on page 56.
With regard to the ATM MATRIX 8X8 unit refer to paragraph 4.4 on page 58.(Only for 1660SM)
With regard to the ISAPR MATRIX and ISAPR_EA MATRIX unit refer to the specific Operators
Handbook.
With regard to the ISAES unit refer to the specific Operators Handbook.
When upgrading an equipment with New Hardware (for example MATRIXN unit) that substitute the
old units (for example MATRIX unit), follow the indication given in paragraph 5 on page 59.
With regard to the CONGI unit refer to paragraph 4.5 on page 58.(Only for 1660SM and 1650SMC)
WARNING!:
When substituting the CONGI unit strictly observe the following procedure:
ED
02
In order to avoid shortcircuit, before substituting the CONGI unit, switchoff the relevant Station battery fuse breaker . Subsequently remove the Station Battery cable
and extract the CONGI unit.
Before inserting the new spare unit carefully check the settings and 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.
Insert the new CONGI unit in the subrack without the Station Battery cable conneted
to it.
Connect the Station Battery cable to the power connector present in front of the
CONGI board.
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
49 / 76
Spares with installed software, belonging to the same type of equipment and with SW release
identical to the unit to replace
Spares with installed software, belonging to the same type of equipment but with SW release
differing from the one of the unit to replace, or belonging to other types of equipment or unknown.
Spares with installed software, belonging to the another type of equipment (example 1670SM)
or unknown SW.
The flowchart of Figure 24. on page 51 illustrates the procedures to follow for the EQUICO or PQ2/EQC
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.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
50 / 76
Substitute EQUICO or
PQ2/EQC unit
THIS PROCEDURE IS
APPLICABLE ONLY ON
1660SM
NEW UNIT HW
CONDITION:
software of the same
release and NE
NEW UNIT HW
CONDITION:
unit with different
software
NEW UNIT HW
CONDITION:
unit without
software
NEW UNIT HW
CONDITION:
unit with wrong or
unknown software
YES
Is the MIB stored
in the Craft Terminal?
NO
NOTES:
NB1
NB2: The Comm/Routing tables are automatically retrieved
only with CONGI starting from version 3AL 78830AAAC
Otherwise the Comm/Routing tables must be
configurated manually using the Craft Terminal
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
51 / 76
N.B.
In this paragraph for COMPACT ADM is generically intended one of the following unit:
SYNTH1
SYNTH1N
SYNTH4
Various procedures are utilized to replace a COMPACT ADM faulty unit. They depend on the following
maintenance conditions:
CONGI unit version (read NOTES in Figure 26. on page 54 and Figure 27. on page 55)
The flowcharts of Figure 25. on page 53, Figure 26. on page 54, Figure 27. on page 55 illustrates the
procedures to follow for the COMPACT ADM substitution.
The procedure aim is to replace the faulty unit without causing configuration changes and/or unwanted
faults; when not possible this is indicated in the flow chart.
Replacement problems:
When replacing the COMPACT ADM unit the traffic of the two SDH ports is lost when not SNCP
protected.
Then it is suggested to replace in low traffic condition.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
52 / 76
THIS PROCEDURE IS
APLLICABLE ONLY TO
1650SMC
PROTECTED
COMPACT ADM unit
FAILURE
ON SPARE
Substitute
COMPACT ADM
FAILURE
ON MAIN
NO
Craft Terminal
manages the NE?
YES
Force EPS on spare
COMPACT ADM
END
Substitute main
COMPACT ADM
NEW UNIT HW
CONDITION:
software of the same
release and NE
NEW UNIT HW
CONDITION:
unit with different
software
NEW UNIT HW
CONDITION:
unit without
software
NEW UNIT HW
CONDITION:
unit with wrong or
unknown software
CONTINUE
REFER TO
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
53 / 76
CONTINUE
FROM
I11 ON
NO
YES
NOTE:
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
54 / 76
THIS PROCEDURE IS
APLLICABLE ONLY TO
1650SMC
NOT PROTECTED
COMPACT ADM unit
Substitute main
COMPACT ADM (NB1)
THIS PROCEDURE IS
APLLICABLE ONLY TO
1650SMC AND 1640FOX
NEW UNIT HW
CONDITION:
software of the same
release and NE
NEW UNIT HW
CONDITION:
unit with different
software
NEW UNIT HW
CONDITION:
unit without
software
NEW UNIT HW
CONDITION:
unit with wrong or
unknown software
I12 OFF
(Reset Data Base and upload Comm/Routing Tables)
INSERT THE NEW UNIT AGAIN
NO
YES
NOTES:
I12 OFF
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
55 / 76
ATM MATRIX 4X4 EPS schema is not supported by 1640FOX so, the flow chart of Figure 29.
cannot be applied to this equipment.
The flowcharts of Figure 28. on page 56 illustrates the procedures to follow for the ATM MATRIX 4X4
when it is not EPS protected.
The flowcharts of Figure 29. on page 57 illustrates the procedures to follow for the ATM MATRIX 4X4
when it is EPS protected.
The procedures aim is to replace the faulty unit without causing configuration changes and/or unwanted
faults.
NOT EPS PROTECTED
ATM MATRIX unit
END
Figure 28. ATM MATRIX 4X4 and 4x4 V2 units replacement without EPS protection
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
56 / 76
Two different procedure are available for ATM MATRIX 4X4 substitution according to the EPS schema.
THIS PROCEDURE IS
APLLICABLE ONLY TO
1650SMC AND 1660SM
FAILURE
ON SPARE
Substitute
ATM MATRIX unit
END
FAILURE
ON MAIN
END
Figure 29. ATM MATRIX 4X4 unit replacement with EPS protection
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
57 / 76
Two different procedure are available for ATM MATRIX 8X8 substitution according to the EPS schema.
For ATM MATRIX 8X8 substitution can be applied the same rules used for ATM MATRIX 4X4 , so refer
to flow chart of Figure 28. on page 56 and Figure 29. on page 57.
When substituting an old CONGI unit (from code 3AL 78830 AAAA to code 3AL 78830 AAAE) with a
new CONGI unit (starting from code 3AL 78830 AAAF) must be taken into account the rules reported
in the following; this is necessary for the right management of the Fuse Broken alarm on the CONGI
(1650SMC and 1660SM) and SERGI (1650SMC) units.
[1]
The alarm Fuse Broken is meaningful (hence it is active) only if two batteries connections (this
means that two CONGI in1660SM or one CONGI and one SERGI in 1650SMC has been equipped)
are present.
[2]
If old CONGI units are present in main slot (slot 10 for 1660SM and slot 4 for 1650SMC) it is mandatory to connect the service battery to the front connector (refer to Installation Handbook for details)
to correctly activate the alarms.
[3]
In presence of configurations having 2 CONGI units composed of an old and new type it is mandatory to open TC5 setting (refer to Technical Handbook for details on Hardware settings) on the soldering side of the old type CONGI if the latter is placed in the spare position (slot 12 in 1660SM and
slot 5 in 1650SMC).
If the old CONGI is maintained in a main slot (slot 10 in 1660SM and slot 4 in 1650SMC), TC5 can
be nevertheless closed or open.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
58 / 76
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
59 / 76
According to the MATRIX EPS protection scheme different procedure are available:
[1]
[2]
ED
Insert the new MATRIX into the subrack slot 23; 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
( MATRIXN) from the list, then click on ok.
Insert the new MATRIXN into the subrack slot previously occupied by the old MATRIX; 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 MATRIXN acronym from
the list then click on ok.
Force the EPS Switching to the Standby MATRIXN by selecting the Switch option from the
EPS menu. For details see the paragraph Switching EPS in the NE MANAGEMENT section
of this Handbook.
After having verify that the MATRIXN (previously in Standby) is now working, remove the MATRIX unit (previously working) from the subrack.
Insert the new MATRIXN into the subrack slot previously occupied by the old MATRIX; 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 MATRIXN acronym from
the list then click on ok.
The decision to force again the EPS MATRIXN switching to restore the original working condition is left to the operator.
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
60 / 76
ED
Before inserting the new SYNTH1N in subrack slot 9, follow the instruction described in
Figure 30. on page 62. At the end of the procedure a RUTM (unit type mismatch) alarm will be
present.
On Craft Terminal in the Subrack level view select the SYNTHN unit in slot 9
Select the Modify option from the Equipment menu and select the SYNTH1N acronym from
the list then click on ok.
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
61 / 76
NEW UNIT HW
CONDITION:
software of the same
release and NE
NEW UNIT HW
CONDITION:
unit with different
software
NEW UNIT HW
CONDITION:
unit without
software
NEW UNIT HW
CONDITION:
unit with wrong or
unknown software
I12 OFF
(Reset Data Base and upload Comm/Routing Tables)
INSERT THE NEW UNIT AGAIN
NO
YES
NOTES:
NB1: The Comm/Routing tables are automatically retrieved
only with CONGI starting from version 3AL 78830AAAC
Otherwise the Comm/Routing tables must be
configurated manually using the Craft Terminal
I12 OFF
Figure 30. 1650SMC: Upgrading with a new SYNTH1N EPS not protected
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
62 / 76
[2]
Supposing that the two STM1 ports are not network protected, their traffic will be lost during the
substitution; the traffic of all the other board will not be lost.
ED
Insert the new SYNTH1N into the subrack slot 10; a RUTM (unit type mismatch) alarm will be
present.
On Craft Terminal in the Subrack level view select the SYNTH1N unit in slot 10
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 SYNTH1N in slot 10 by selecting the Switch option from the EPS
menu. For details see the paragraph Switching EPS in the NE MANAGEMENT section of
this Handbook.
Before inserting the new SYNTH1N in subrack slot 9, follow the instruction described in
Figure 31. on page 64. 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 SYNTH1N unit in slot 9
Select the Modify option from the Equipment menu and select the SYNTH1N acronym from
the list then click on ok.
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
63 / 76
NEW UNIT HW
CONDITION:
software of the same
release and NE
NEW UNIT HW
CONDITION:
unit with different
software
NEW UNIT HW
CONDITION:
unit without
software
NEW UNIT HW
CONDITION:
unit with wrong or
unknown software
I11 ON
NO
YES
END
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
64 / 76
ED
Before inserting the new SYNTHN in subrack slot 2, follow the instructions described in
Figure 32. on page 66 (Compact ADM replacement). At the end of the procedure a RUTM (unit
type mismatch) alarm, relevant to the replaced unit, will be present on the C.T.
On Craft Terminal, in the Subrack level view, select the Compact ADM unit (slot 2).
Select the Modify option from the Equipment menu and select the SYNTHN acronym from
the list then click on ok.
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
65 / 76
NEW UNIT HW
CONDITION:
software of the same
release and NE
NEW UNIT HW
CONDITION:
unit with different
software
NEW UNIT HW
CONDITION:
unit without
software
NEW UNIT HW
CONDITION:
unit with wrong or
unknown software
I12 OFF
(Reset Data Base and upload Comm/Routing Tables)
INSERT THE NEW UNIT AGAIN
NO
YES
I12 OFF
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
66 / 76
5.3 P4S1, S41, L41, L42, S161, L161, L162 substitution with P4S1N,
S41N, L41N, L42N , S161N, L161N, L162N
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
During the substitution the traffic carried by the units will be lost if not SNCP or MSP protected
In the following an example will be given substituting a P4S1 with a P4S1N; the same procedure can
be applied to substitute the S41, L41, L42, S161, L161, L162 units respectively with S41N,
L41N, L42N , S161N, L161N, L162N units; the same procedure can be applied to substitute
a generic xyz unit with its upgraded xyzN version.
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.
In the following an example will be given, substituting a P21E1 with a P21E1N; the same procedure
can be applied to substitute a generic xyz unit with its upgraded xyzN version.
ED
Insert the new unit (example P21E1N) into the subrack slot previously occupied by the old unit;
on Craft Terminal a RUTM (unit type mismatch) alarm, relevant to the replaced unit, 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 P21E1N) from the list, then click on ok.
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
67 / 76
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
68 / 76
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Before to start with the FLASH card substitution ( flowchart of Figure 33. on page 70) execute
the following instruction:
a)
Save the MIB as explained in Section 3 (NE MANAGEMENT), Paragraph Mib management of this Manual.
b)
Create and install the enhanced software package (SDH+ISA) as explained in 1320 CT
Basic Operators Handbook.
The flowchart of Figure 33. on page 70 illustrates the procedures to follow for the FLASH card substitution without causing loss of traffic.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
69 / 76
I12 ON
NO
YES
Is the MIB stored
in the Craft Terminal?
From C.T. send the saved
MIB containing the correct
configuration (NB1)
(see NE management section)
NOTES:
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
70 / 76
N.B.
In this paragraph for COMPACT ADM is generically intended one of the following unit:
SYNTH1
SYNTH1N
SYNTH4
The 80 Mbytes FLASH card (housed on COMPACT ADM unit in slot 9) used up to rel. 2.0A requires to
be replaced with one having a higher size (256 Mbyte) in order to manage the new SDH+ATM/IP services.
N.B.
Before to start with the FLASH card substitution ( flowchart of Figure 34. on page 72 or flow
chart of Figure 35. on page 73 ) execute the following instruction:
a)
Save the MIB as explained in Section 3 (NE MANAGEMENT), Paragraph Mib management of this Manual.
b)
Create and install the enhanced software package (SDH+ATM/IP) as explained in 1320
CT Basic Operators Handbook.
The flowcharts of Figure 34. on page 72 illustrate the procedures to follow for the FLASH card substitution with COMPACT ADM board EPS protected.
The flowcharts of Figure 35. on page 73 illustrate the procedures to follow for the FLASH card substitution with COMPACT ADM board not EPS protected.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
71 / 76
I12 ON
NO
YES
Is the MIB stored
in the Craft Terminal?
From C.T. send the saved
MIB containing the correct
configuration (NB1)
(see NE management section)
END
NOTES:
NB1
NB2: The Comm/Routing tables are automatically retrieved
only with CONGI starting from version 3AL 78830AAAC
Otherwise the Comm/Routing tables must be
configurated manually using the Craft Terminal
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
72 / 76
WARNING: Substituting the FLASH CARD on the SYNTHN board not EPS protected will cause traffic loss!
I12 ON
NO
YES
Is the MIB stored
in the Craft Terminal?
From C.T. send the saved
MIB containing the correct
configuration (NB1)
(see NE management section)
END
NOTES:
NB1
NB2: The Comm/Routing tables are automatically retrieved
only with CONGI starting from version 3AL 78830AAAC
Otherwise the Comm/Routing tables must be
configurated manually using the Craft Terminal
Figure 35. FLASH CARD substitution (COMPACT ADM EPS not protected)
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
73 / 76
The 80 Mbytes FLASH card (housed on COMPACT ADM unit in slot 2) used up to rel. 2.0A requires to
be replaced with one having a bigger size (256 Mbyte), in order to manage the new SDH+ATM/IP services.
N.B.
Before starting with the FLASH card substitution (flowchart of Figure 36. on page 75 ) execute
the following instruction:
a)
Save the MIB as explained in Section 3 (NE MANAGEMENT), Paragraph Mib management of this Manual.
b)
Create and install the enhanced software package (SDH+ATM/IP) as explained in 1320
CT Basic Operators Handbook.
The flowchart of Figure 36. on page 75 illustrates the procedures to follow for the FLASH card substitution.
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
74 / 76
WARNING: Substituting the FLASH CARD on the COMPACTADM will cause traffic loss
I12 ON
NO
YES
Is the MIB stored
in the Craft Terminal?
From C.T. send the saved
MIB containing the correct
configuration (NB1)
(see NE management section)
END
NOTES:
NB1: the Comm/Routing tables are automatically retrieved from the shelf of the equipment
ED
02
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
75 / 76
ED
02
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
END OF DOCUMENT
SC.4:NE MAINTENANCE
3AL 91670 AA AA
76
76 / 76
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
3
3
3
3
5
5
5
11
11
11
11
12
02
050414
01
041119
ED
DATE
ECR 23082
CHANGE NOTE
C. FAVERO ITAVE
J.MIR S. MAGGIO
C. FAVERO ITAVE
J.MIR S. MAGGIO
P.GHELFI ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
P.GHELFI ITAVE
METRO OMSN
Rel. 4.4/5.2A
OPERATORS HANDBOOK
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
1 / 16
FIGURES
Figure 1. SIBDL download procedure step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. SIBDL download procedure step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. SIBDL download procedure step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. SIBDL download procedure step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. SIBDL download procedure step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. SIBDL download procedure step 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. SIBDL download procedure step 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Serial Cable Modem configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Serial Cable Modem configuration step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Serial Cable Modem configuration step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Serial Cable Modem configuration step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Serial Cable Modem configuration step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
02
6
7
7
8
8
9
9
12
13
14
14
15
SC.5: SIBDL
3AL 91670 AA AA
16
2 / 16
1 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:
Download with SIBDL. The complete procedure is indicated. See Chapter 2 on page 5
Configuration for SIBDL. Configurations to be performed for SIBDL operation are described. See
Chapter 3 on page 11.
1.2 Terminology
1.2.1 Acronyms and abbreviations
Refer to the Section Introduction manual.
1.2.2 Glossary of terms
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
3 / 16
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
4 / 16
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Maintenance phase, when substituting the EQUICO (1660SM rel. 4.x), PQ2EQC (1660SM
Rel.5.x) or SYNTH1N/SYNTH4 (1650SMC and 1640FOX) unit with a spare, and the spare one
doesnt contain software.
ATTENTION:
Download with SIBDL program put the EQUICO, PQ2EQC or SYNTH1N/SYNTH4 unit out of
service regarding to the supervision and control function, while the traffic is not lost.
It must not be executed to download a spare unit that contains software; in this case use the
Download option of the EMLUSM, presented in the previous section.
SIBDL tool permits to download the software towards the NE using the Q interface (Ethernet connection)
or the F interface RS232 (serial line) of the NE .
When using the Q interface the time necessary to the operation is reduced to some minute (Q interface
is available only on 1650SMC and 1660SM)
WARNING:
in Windows NT environment, it should have configured, before to use SIBDL:
RAS (Remote Access Service) and Serial Cable Modem presented at chapter 3 on
page 11.
N.B.
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
5 / 16
Note: the example in the following is referred to a 1660SM; the same rules can be applied to
1640FOX and 1650SMC.
1)
when download by means of Q interface, always connect both the F and Q interface
(1650SMC and 1660SM).
2)
3)
In the screen which appears (see Figure 1. ) with the command menu, select automatic mode
command typing 8 and then ENTER.
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 SC.3: NE MANAGEMENT of this Manual.
2) If the software to download manage only the SDH functionality, select the file descriptor
in the directory 1660SM.
(example: /ALCATEL/Q3CT_Pv1.3.05/FTservices/data/1660SM/2.1b.09/1660.dsc)
3) If the software to download manage the SDH + ATM/IP functionality, select the file
descriptor in the directory 1660SME
(example: /ALCATEL/Q3CT_Pv1.3.05/FTservices/data/1660SME/2.1b.09/1660.dsc)
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
6 / 16
C:\ALCATEL\Q3CT_Pv1.3.05/FTservices/data/1660SME/2.1b.09/1660.dsc
Press ENTER
6)
ervices/data/1660SME/2.1b.09/1660.dsc
This step ( see Figure 4. ) ask if the flash card must be formatted.
Type y to format the flash card; as result of this action the program ask for a confirmation (see
Figure 5. )
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
7 / 16
ervices/data/1660SME/2.1b.09/1660.dsc
ervices/data/1660SME/2.1b.09/1660.dsc
8)
ED
02
Type y . The screen shows the automatic download evolution with a final message indicating
the completed download (see Figure 6. ).
On the contrary repeat the procedure.
SC.5: SIBDL
3AL 91670 AA AA
16
8 / 16
Press ENTER.
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
9 / 16
N.B.
Check that no RUTM alarm is present in the slot reserved to the main MATRIXN for
1660SM Rel. 4.3 or SYNTH1N for 1650SMC.
If RUTM alarm is present means that the board type inserted in the subrack (typically
MATRIXN or SYNTH1N in this release) and the board type software configurated
(typically MATRIX or SYNTH1) is not the same; under this condition the user must
change the board type with the Equipment>Set menu.
Select Init download from Download menu
Select the SW package to Download and click on OK button
In this condition the download is executed immediately.
Select Unit info from Download menu
Select the Software Package loaded as explained above and activate it
Press OK to complete the operation
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
10 / 16
14 ) From Craft Terminal ( EMLUSM view) execute the normal download procedure:
Double click on My computer icon on the PC desktop and double click on Control panel icon;
double click on Network icon;
select the folder Services in the Network window and push the button Add: start the Select
Network Service window;
select Remote Access Service (RAS) in the dialog box;
follow the instructions.
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;
push the button Install Modem in Add RAS Device window: start the Install New Modem window;
put a tick against Dont detect my modem; I will select him from a list and push the Next > button;
push the button Have disk...: start the window Install from disk;
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
11 / 16
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 Dont detect my modem; I will select it from a list and push the button Next > ;
Push the button Have disk...: the window Install from disk will appear;
Search the folder where SIBDL is installed and select the file mdmalca.inf, after push the button
Open;
Select the modem named Serial cable into dialog box from Install New Modem window and push
the button Next >;
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
12 / 16
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
13 / 16
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 >;
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The window Digital Signature Not found will appear: push the button Yes, and after the button
Finish to end modem installation;
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
14 / 16
ED
At the end, the Phone and Modem Options window will display the installed modem
02
SC.5: SIBDL
3AL 91670 AA AA
16
15 / 16
END OF DOCUMENT
ED
02
SC.5: SIBDL
3AL 91670 AA AA
16
16 / 16
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Alcatel
METRO OMSN Rel. 4.4/5.2A
OPERATORS HANDBOOK
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
fase
step
ED
da from
a to
24
1/24
24/24
22
1/22
22/22
448
1/448
448/448
76
1/76
76/76
1/16
16/16
TARGHETTE - LABELS
FRONTESPIZIO - FRONT
SC.2: INTRODUCTION
SC.3: NE MANAGEMENT
10
SC.4: NE MAINTENANCE
11
12
SC.5: SIBDL
16
586
293
02
numerate
numbered
RELEASED
3AL 91670 AAAA TQZZA
4
1/ 4
Site
VIMERCATE
FCG
Originators
P. GHELFI
METRO OMSN
REL. 4.4/5.2A
C.T. OPERATORS HANDBOOK
Domain
Division
Rubric
Type
Distribution Codes
:
:
:
:
OND
SDH
METRO OMSN
METRO OMSN REL. 4.4/5.2A OPERATORS HDBK
Internal :
External
:
Approvals
Name
App.
J. MIR
C. FAVERO
S. MAGGIO
Name
App.
Alcatel
METRO OMSN Rel. 4.4/5.2A
1640FOX 1650SMC 1660SM
OPERATORS HANDBOOK
1AA 00014 0004 (9007) A4 ALICE 04.10
VOL. 1/1
ED
02
RELEASED
3AL 91670 AAAA TQZZA
4
2/ 4
Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
1650SMC
1660SM
OPERATORS HANDBOOK
3AL 91670 AAAA Ed.02
VOL. 1/1
Alcatel
METRO OMSN Rel. 4.4/5.2A
1640FOX
1650SMC
1660SM
OPERATORS HANDBOOK
3AL 91670 AAAA Ed.02
VOL. 1/1
Alcatel
METRO OMSN Rel. 4.4/5.2A
1640FOX
3AL 91670 AAAA Ed.02
1650SMC
1660SM
OPERATORS HANDBOOK
VOL. 1/1
Alcatel
METRO OMSN Rel. 4.4/5.2A
1640FOX
1650SMC
1660SM
OPERATORS HANDBOOK
VOL. 1/1
Alcatel
METRO OMSN Rel. 4.4/5.2A
1640FOX
ED
02
1650SMC
1660SM
OPERATORS HANDBOOK
VOL. 1/1
RELEASED
3AL 91670 AAAA TQZZA
4
3/ 4
ED
02
RELEASED
4/ 4
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.