1660sm31_oper_ed01
TRANSCRIPT
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
OPERATOR’S HANDBOOK
Alcatel 1660SM Rel.3.1
STM 16 Multiservice Metro Node
VOL. 1/1
957.140.602 V Ed.01 3AL 80755 BAAA Ed.01
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.END OF DOCUMENT
957.140.602 V Ed.01 3AL 80755 BAAA Ed.01
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
1
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
1660SM REL.3.1 C.T. OPERATOR’S HANDBOOK
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 General information 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Handbook applicability 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Purpose of the handbook 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4 Handbook configuration check 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1 Notes on Ed.01 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 PRODUCT-RELEASE HANDBOOKS 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 SAFETY NORMS AND LABELS 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 First aid for electric shock 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Norms and labels 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 HANDBOOK DESCRIPTION 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Products, product-releases, versions and Customer Documentation 17. . . . . . . . . . . . . . 5.2 Handbook supply to Customers 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Aims of standard Customer Documentation 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Handbook Updating 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Changes introduced in the same product-release (same handbook P/N) 18. . . . . . . . . . . . 5.4.2 Supplying updated handbooks to Customers 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3 Changes due to a new product-release 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 Customer documentation supply on CD–ROM 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.1 Contents, creation and production of a CD–ROM 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.2 Use of the CD–ROM 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.3 CD–ROM identification 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.4 CD–ROM updating 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
01 020520 S.MAGGIO ITAVE P.GHELFI ITAVE
1660SM REL.3.1
C.T. OPERATOR’S HANDBOOK
C. FAVERO
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
2
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
LIST OF FIGURES AND TABLES
Table 1. Handbooks related to the specific product hardware 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2. Handbooks related to the specific product SW management and local product control 7. . Table 3. Handbooks related to ATM specific product SW 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4. Handbooks related to IP specific product SW 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5. Handbooks common to Alcatel Network Elements using 1320CT platform 8. . . . . . . . . . . . . Table 6. Documentation on CD–ROM 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7. Optional handbooks common to 16xxSM 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
3
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK
1.1 General information
WARNING
ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims theimplied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liablefor errors contained herein or for damages, whether direct, indirect, consequential, incidental, orspecial, in connection with the furnishing, performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for informationpurposes only and are subject to change without notice. They do not represent any obligation on thepart of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied,reproduced or disclosed to a third party without written consent.
1.2 Handbook applicability
This handbook applies to the following product-releases:
PRODUCT ANV P/N FACTORY P/N
1660SM 3AL 36301 AAAA 521.203.300
PRODUCT RELEASEVERSION
(N.B.)ANV P/N FACTORY P/N
1660SM Rel.3.1 –– 3AL 80622 AAAA 521.535.200
For further information on the Alcatel software product and its physical distribution support refer to the“Introduction” section.
N.B. NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operator’s Handbooks) are notmodified unless the new software ”version” distributed to Customers implies man–machineinterface changes or in case of slight modifications not affecting the understanding of theexplained procedures.Moreover, should the screen prints included in the handbook contain the product-release’s”version” marking, they are not replaced in the handbooks related to a subsequent version, ifthe screen contents are unchanged.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
4
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
1.3 Purpose of the handbook
This handbook describes the operations concerning commissioning, operation and maintenance that theoperators must carry out as indicated by the specific software application(s) referred to in this handbook(see para. 1.2 on page 3).
This handbook must be used together with the associated Technical Handbook ( see Table 1. on page7) and the 1320CT associated documentation ( see Table 5. on page 8) does not replicate informationcontained into it.In particular, all cautions relevant to safety, rules for EMC and ESD, as well as warnings regardingoperations that may cause damages to the equipment, are not duplicated here, but must be retrieved fromthe Technical Handbook.
When using this handbook it is assumed that the Operators know:
• the structure (hardware composition) and all the possible operating modes of the equipment(product-release) this handbook refers to.
• how to use a PC and the Windows ambient applications
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
5
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
1.4 Handbook configuration check
This handbook is a collection of documents (each contained in a specific section) that can haveeditions 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 thecorresponding original internal document.
HANDBOOK EDITION 01 02 03 04 05
REGISTER AND SECTION TITLE SECTION EDITION
1 HANDBOOK GUIDE 01
2 INTRODUCTION MANUAL 01
3 NE MANAGEMENT MANUAL 01
4 MAINTENANCE MANUAL 01
5 SIBDL MANUAL 01
1.4.1 Notes on Ed.01
Ed.01 issued on May, 2002 is the first released and validated version of the handbook, associated toproduct release 3.1.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
6
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
7
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
2 PRODUCT-RELEASE HANDBOOKS
The list of handbooks given here below is valid on the issue date of this Handbook andcan 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 thisHandbook.
The standard Customer Documentation in the English language for the equipment whoseproduct-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
REF HANDBOOK ANV Part No.FACTORYPart No.
THISHDBK
1660SM Rel.3.1Technical Handbook
3AL 80755 AAAA 955.110.572 E
[1]Provide information regarding Equipment description, Maintenance,Hardware setting documentation.
1660SM Rel.3.1Installation Handbook
3AL 80755 CAAA 955.110.582 Z
[2]Provide information regarding Equipment Installation, according toA–Installation Engineering Dept. rules.
[3]
1660SM Rel.3.1Turnup & CommissionigHandbook
3AL 80755 DAAA 955.110.592 T
[3]
Provide information regarding Equipment Turn–On, Test and Operation,according to A–Installation Engineering Dept. rules.
Table 2. Handbooks related to the specific product SW management and local product control
REF HANDBOOK ANV Part No.FACTORY
Part No.
THIS
HDBK
[4]
1660SM Rel.3.1CT Operator’s Handbook
3AL 80755 BAAA 957.140.602 V[4]
Provides 1660SM “SDH” Craft Terminal screens and operational procedures
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
8
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
Table 3. Handbooks related to ATM specific product SW
REF HANDBOOK ANV Part No.FACTORY
Part No.
THIS
HDBKor note
[5]ATM Rel.1.1Operator’s Handbook
3AL 80730 AAAA 957.140.552 J
[6]ATM Rel.1.2Operator’s Handbook
3AL 80814 AAAA 957.140.652 W
Provides ATM SMART Terminal screens and operational procedures
Table 4. Handbooks related to IP specific product SW
REF HANDBOOK ANV Part No.FACTORY
Part No.
THIS
HDBKor note
[7]IP Rel.1.0Operator’s Handbook
3AL 81062 AAAA 957.140.722 L
Provides IP Terminal screens and operational procedures
Table 5. Handbooks common to Alcatel Network Elements using 1320CT platform
REF HANDBOOK ANV Part No.FACTORY
Part No.
THIS
HDBK
OR
NOTE
1320CTBasic Operator’s Handbook
3AL 79186 AAAA 957.130.542 E
[8]Provides general information and operational procedures common to all 1320CT(Craft terminal) of Alcatel InfoModel Network Elements.
1330AS Rel.5.1Operator’s Handbook
3AL 71079 AAAA 957.130.442 A
[9]Provides detailed information and operational procedures regarding the alarmSurveillance software embedded in the 1320CT software package.Information about Historical Alarms an Network Element SymbolsManagement ( Physical Network Management) are not valid for Craft Terminal.They are only used by Network Management.
ELM Rel.5.0 Operator’s Handbook 3AL 71081 AAAA 957.130.462 E
[10] Provide detailed information and operational procedures regarding the Event LogManagement software embedded in the 1320CT software package.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
9
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
Table 6. Documentation on CD–ROM
See para. 5.5 on page 19
REF CD–ROM TITLE ANV Part No. FACTORY Part No.
1660SM Rel.3.1 CD–ROM–DOC EN 3AL 80761 AAAA 417.100.064
[11] Contains, in electronic format, the following handbooks: REF.[1] and [4]
N.B. Handbooks REF.[2] and [3] are available only on paper support.
1320CT BASIC CD–ROM–DOC EN 3AL 79549 AAAA 417.100.031
[12]Contains, in electronic format, the following handbooks: REF. [8] to [10]
ATM 1.1 CD–ROM–DOC EN 3AL 80739 AAAA 417.100.060
[13]Contains, in electronic format, the following handbook: REF. [5]
ATM 1.2 CD–ROM–DOC EN 3AL 80815 AAAA 417.100.068
[14]Contains, in electronic format, the following handbook: REF. [6]
IP 1.0 CD–ROM–DOC EN 3AL 81063 AAAA 417.100.084
[15]Contains, in electronic format, the following handbook: REF. [7]
Table 7. Optional handbooks common to 16xxSM
REF HANDBOOK ANV Part No.FACTORYPart No.
THISHDBK
S9–16xxSMSystem Installation Handbook
3AL 78901 AAAA 955.100.692 N
[16]Provides general installation rules necessary to install the Optinex familyequipment in the S9 Rack .
Optinex RACK–16xxSMSystem Installation Handbook
3AL 38207 AAAA 955.110.202 L
[17]Provides general installation rules necessary to install the Optinex familyequipment in the Optinex Rack .
N.B. Handbooks REF.[16] and [17] are available only on paper support.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
10
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
11
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
3 SAFETY NORMS AND LABELS
3.1 First aid for electric shock
Do not touch the patient with bare hands until the circuit has been opened.
Open the circuit by switching off the line switches. If that is not possible, protect yourself with drymaterial and free the patient from the conductor.
ARTIFICIAL RESPIRATION
It is important to start mouth to mouth resuscitation at once and seek doctor help immediately.
TREATMENT OF BURNS
This treatment should be used after the patient has regained consciousness. It can also be employed whilethe artificial respiration is being applied (in this case there should be at least two persons present).
WARNING:
• Do not attempt to remove his clothing from the burnt parts;
• Apply dry gauze on the burns;
• Do not apply ointments or other oily substances.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
12
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
Mouth to mouth resuscitation method
1
2
3
4
5
6
Lay the patient supine with his arms parallel with the body, if the patient is layingon an inclined plane, make sure that his stomach is slightly lower than his chest.Open the patient’s mouth and check that there are no extraneous bodies in hismouth (dentures, chewing–gum etc.),
Kneel beside the patient level with his head. Puta hand under the patient’s head and one underhis neck (see fig.) Lift the patient’s head and letit recline backwards as far as possible
Shift the hand from the patient’s neck to is chin:place your thumb between his chin and hismouth, the index along his jawbone, and keep theother fingers closed together (see fig.). Whileperforming these operations take a good supplyof oxygen by taking deep breaths with yourmouth open.
With your thumb between the patient’s chin andmouth keep his lips together and blow into hisnasal cavities (see fig.)
While performing these operations observe if thepatient’s chest rises (see fig.) If not it is possiblethat his nose is blocked: in that case open thepatient’s mouth as much as possible by pressingon his chin with your hand, place your lips aroundhis mouth and blow into his oral cavity. Observeif the patient’s chest heaves. This secondmethod can be used instead of the first evenwhen the patient’s nose is kept closed bypressing the nostrils together using the hand youwere holding his head with. The patient’s headmust be kept sloping backwards as much aspossible.
Start with ten rapid expirations, hence continue at a rate of twelve/fifteenexpirations per minute. Go on like this until the patient has regainedconsciousness, or until a doctor has ascertained his death.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
13
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
3.2 Norms and labels
Refer to the Technical Handbook associated to ALCATEL’s designed and manufactured equipmentto obtain the following information:
– COMPLIANCE WITH EUROPEAN NORMS.
– SAFETY RULES
• General rules
• Harmful optical signals
• Risk of explosion
• Moving mechanical parts
• Heat–radiating Mechanical Parts
– ELECTROMAGNETIC COMPATIBILITY
– ELECTROSTATIC DISCHARGERS (ESD)
– EQUIPMENT LABELS
Identical or similar information on Personal Computer, Work–Station etc., other than ALCATEL’s, loadedwith software applicative described in this Handbook, is supplied in the Constructor’s technicaldocumentation.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
14
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
15
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
4 HANDBOOK DESCRIPTION
This handbook is composed of the following Manuals:
SECTION 1: HANDBOOK GUIDE (This document)
The Handbook Guide gives general information on the application and use of the Handbook. TheHandbook Guide includes the following chapters:– Chapter 1: Handbook structure and configuration check. This chapter gives information on the whole
handbook application, composition and evolution.– Chapter 2: Product-release handbooks. This chapter lists the handbooks the Operator should have
in order to carry out the tasks allowed by the specific product–release this handbook refers to.– Chapter 3: Safety norms and labels– Chapter 4: Handbook description– Chapter 5: General on Alcatel Customer Documentation
SECTION 2: INTRODUCTION Manual
The Introduction Manual describes the main features of the graphical interface and provides a generaloverview of the system architecture and the different functionalities provided by the Craft Terminal. TheIntroduction Manual includes the following chapters:– Chapter 1: Introduction. This chapter gives the structure of this manual.– Chapter 2: General description of the Craft Terminal. The Craft Terminal is introduced and the
software product listed. The Craft Terminal main functionality in the NE management (EML–USM)are listed and briefly described.
– Chapter 3: Acronyms and abbreviations. The acronyms used in all the operator manuals are listed.– Chapter 4: Glossary of terms. Definitions concerning the acronyms.
SECTION 3: NETWORK ELEMENT MANAGEMENT Manual
The aim of this document is to describe the Craft Terminal view, inserting operative information.The Network Element Manual includes the following chapters:
– Chapter 1: Introduction. This chapter gives the structure of this manual.– Chapter 2: General introduction on views and menus. The view organization is presented and the
menus available listed and briefly described.– Chapter 3: NE management supervision. This chapter is dedicated to the NE states and NE access.– Chapter 4: NE management general configuration. In this chapter general configuration referred to
the equipment management are described (CT access, NE Time, Alarm Configuration etc).– Chapter 5: Security Management. In this chapter configuration referred to the Security management
are described (ACD level and Manager list).– Chapter 6: External input and output points management. This chapter describes how to display and
set the input/output environmental alarm (housekeeping alarm).– Chapter 7: Diagnosis management. In this chapter are specified: access to the Alarm Surveillance
to show the alarm condition, abnormal condition list (as result of operator’s command), access to theEvent and Alarm Log file and Internal Link Monitor.
– Chapter 8: Communication and Routing management. In this chapter are presented thecommunication and routing parameters, concerning the OSI and IP communication protocols forthe local NE, the OS and each other related NE in order to provide a global communicationcapabilities inside the network
– Chapter 9: Equipment management. This chapter deals mainly with the setting and changing of theboards 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
16
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
– Chapter 11: Port view. This chapter permits to set and show the transmission resources referred tothe Port.
– Chapter 12: Equipment protection management. This chapter permits to manage the EPS protection,setting the relevant configuration.
– Chapter 13: Multiplex Section protection management. This chapter permits to manage the MSPprotection.
– Chapter 14: Transmission view. This chapter permits to show and set the Termination Point of theequipment, 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 thepaths.
– Chapter 16: Overhead management. This chapter permits to manage the Overhead, setting therelevant configuration.
– Chapter 17: Performance Monitoring management. This chapter permits to set and showPerformance Monitoring parameters and data.
– Chapter 18: Synchronization management. This chapter permits to set and show Synchronizationparameters and status.
– Chapter 19: MS–SPRing Management. This chapter permits to set the MS–SPRing protection of theNE
– Chapter 20: ATM/IP/ETH Configuration. This chapter describes the operations necessary for theATM/IP/ETH boards creation and the ATM/IP/ETH TTPs creation.
– Chapter 21: Software management. This chapter permits to update the NE by means downloadprocedure and to manage NE software.
SECTION 4: NETWORK ELEMENT MAINTENANCE Manual
This document aims at introducing the Maintenance procedure, inserting information useful to identifyalarms and troubleshoot the NE.The Maintenance Manual includes the following chapters:
– Chapter 1: Introduction. This chapter gives the structure of this manual.– Chapter 2: Maintenance introduction. List the maintenance steps.– Chapter 3: Maintenance of the Personal Computer. The Personal Computer manual is referred.– Chapter 4: Problems with Craft terminal. Shut–down and restart of the PC is indicated.– Chapter 5: Troubleshooting (Corrective Maintenance). Detection location and correction of failure
are presented.– Chapter 6: Unit replacement with spare. The replacement procedure is detailed.– Chapter 7: Upgrading with New Hardware. The Hardware upgrading procedure is detailed.– Chapter 8: FLASH card substitution. The FLASH card substitution procedure is detailed.
SECTION 5: SIBDL Manual
This document describes the download procedure with SIBDL.The SIBDL Manual includes the following chapters:
– Chapter 1: Introduction– Chapter 2: Download with SIBDL configuration– Chapter 3: Configuration for SIBDL
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
17
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
5 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION
5.1 Products, product-releases, versions and Customer Documentation
A ”product” is defined by the network hierarchical level where it can be inserted and by the whole ofperformance and services for which it is meant.A ”product” evolves through successive ”product-releases” which are the real products marketed fortheir delivery at a certain ”product-release” availability date.
So, a ”product–release” defines a set of hardware components and a software package which, as a whole,identify the possible network applications and the equipment performance which the specific”product-release” has been designed, engineered and marketed for.
In some cases a ”product-release” has further development steps, named ”versions”, that are born toimprove or add some performance (mainly software) with respect to the previous version, or for bug fixingpurposes.
A ”product-release” has its own standard Customer Documentation, composed by one or morehandbooks.
A new ”version” of a ”product-release” may or may not produce a change in the status of the CustomerDocumentation set, as described in para.5.4 on page 18.
5.2 Handbook supply to Customers
Handbooks are not automatically delivered together with the equipment they refer to.The number of handbooks per type to be supplied must be decided at contract level.
5.3 Aims of standard Customer Documentation
Standard Customer Documentation, referred to hereafter, must be always meant as plant-independent.Plant-dependent documentation, if envisaged by the contract, is subjected to commercial criteria as faras contents, formats and supply conditions are concerned (plant-dependent documentation is notdescribed here).
Standard hardware and software documentation is meant to give the Customer personnel the possibilityand the information necessary for installing, commissioning, operating and maintaining the equipmentaccording to Alcatel–Telecom Laboratory design choices.In particular the contents of the handbooks associated to the software applications focus on theexplanation of the man-machine interface and of the operating procedures allowed by it.
Consequently, no supply to the Customers of design documentation (like software source programs,programming tools, etc.) is envisaged.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
18
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
5.4 Handbook Updating
The handbooks associated to the ”product–release” are listed in para.2 on page 7.Each handbook is identified by:– the name of the ”product-release” (and ”version” when the handbook is applicable to the versions
starting from it, but not to the previous ones),– the handbook name,– the handbook P/N,– the handbook edition (usually first edition=01),– the handbook issue date. The date on the handbook does not refer to the date of print but to the date
on which the handbook source file has been completed and released for the production.
5.4.1 Changes introduced in the same product-release (same handbook P/N)
The edition and date of issue might change on future handbook versions for the following reasons:
– only the date changes (pointed out in the Table of Contents) when modifications are made to theeditorial system not changing the technical contents of the handbook.
– the edition, hence the date, is changed because modifications made concern technical contents. Inthis case:• the table in para.1.4 on page 5 indicates the section(s) edition change;• in each section, the main changes with respect to the previous edition are listed;• in affected chapters of each section, revision bars on the left of the page indicate modifications
in text and drawings (this is done after the first officially released and validated version).
Changes concerning the technical contents of the handbook cause the edition number increase (e.g. fromEd.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition ofa version character (e.g. from Ed.02 to Ed.02A).
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operator’s Handbooks) are notmodified unless the new software ”version” distributed to Customers implies man–machineinterface changes or in case of slight modifications not affecting the understanding of theexplained procedures.Moreover, should the screen prints included in the handbook contain the product-release’s”version” marking, they are not replaced in the handbooks related to a subsequent version, ifthe 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 tocommercial criteria.By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue(supplying errata–corrige sheets is not envisaged).
5.4.3 Changes due to a new product-releaseA new product-release changes the handbook P/N and the edition starts from 01. In this case the modifiedparts of the handbook are not listed.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
19
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
5.5 Customer documentation supply on CD–ROM
In the following ’CD–ROM’ means ’Customer Documentation on CD–ROM’
5.5.1 Contents, creation and production of a CD–ROM
In most cases, a CD–ROM contains the documentation of one product–release(–version) and for a certainlanguage.In some other cases, the same CD–ROM can contain the documentation of differentproduct–release(–version)s for a certain language.
As a general rule:
– CD–ROMs for Network Management products do not contain:
• the Installation Guides
• the documentation of system optional features that Customers could not buy from Alcateltogether with the main applicative SW.
– CD–ROMs for Network Elements products do not contain the documentation of system optionalfeatures (e.g. System Installation Handbooks related to racks that Customers could not buy fromAlcatel together with the main equipment).
A CD–ROM is obtained collecting various handbooks and processing them byInterleaf–World–View–Press after the manual addition of some hyperlinks which make the navigationthrough the various handbooks easier. No additional information is added to each handbook, so that thedocumentation present in the CD–ROMs is exactly the same the Customer would receive on paper.
The files processed in this way are then transferred on a PC where the viewer (Interleaf–World–View) isadded and a master CD–ROM is recorded.
Suitable checks are made in order to have a virus–free product.
After a complete functional check, the CD–ROM image is electronically transferred to the archive of theProduction Department, so that the CD–ROM can be produced and delivered to Customers.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
20
01
957.140.602 V
SC.1:HANDBOOK GUIDE
/3AL 80755 BA AA
20
20
5.5.2 Use of the CD–ROM
The CD–ROM can be used both in PC and Unix WS environments.
The minimum configuration for World View (rel.2.2.2) utilization on a PC is:
– Operative System: Windows 95 or Windows NT 4– Processor: Pentium– RAM: 32 Mbyte– Disk space: 20Mbyte
The set–up procedure is present in the booklet included in the CD–ROM box.After the set–up procedure, which installs the viewer in the PC or Unix WS environment, the Customeris allowed to read the handbooks on the PC/WS screen, using the navigation and zooming tools includedin the viewer, and to print selected parts of the documentation through a local printer.
N.B. Copyright notification
WorldView: Copyright 1981–1996INTERLEAF Inc.All rights reserved.The use of WorldView is permitted only in association with the files containedin the CD–ROMs officially supplied by Alcatel.
Alcatel documents: All rights reserved.Passing and copying of documents and files contained in the CD–ROMsofficially supplied by Alcatel, use and communication of its contents are notpermitted without written authorization from Alcatel.
5.5.3 CD–ROM identification
Each CD–ROM is identified:
1 ) by the following external identifiers, that are printed both on the booklet and the CD–ROM uppersurface:– the name of the ”product–release(s)” (and ”version” when the CD–ROM is applicable to
the versions starting from it, but not to the previous ones),– a writing indicating the language(s),– the CD–ROM P/N (Factory P/N 417.xxx.xxx x and ANV P/N),– the CD–ROM edition (usually first edition=01)
2 ) and, internally, by the list of the source handbooks and documents (P/Ns and editions) by whosecollection and processing the CD–ROM itself has been created.
5.5.4 CD–ROM updating
The list of source handbook/document P/Ns–editions indicated in previous para.5.5.3 point 2 ) , inassociation with the CD–ROM’s own P/N–edition, is also loaded in the Alcatel–Information–System as astructured list.Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive system,the Alcatel–Information–System automatically rises a warning toward the Customer Documentationdepartment, indicating the list of CD–ROMs that must be updated to include the new editions of thesehandbooks/documents.This causes the planning and creation of a new edition of the CD–ROM.Updating of CD–ROMs always follows, with a certain delay, the updating of the single handbookscomposing the collection.
END OF DOCUMENT
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
1
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
1660SM REL.3.1 C.T. OPERATOR’S HANDBOOK
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Scope 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2 Target audience 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Reading rules 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Menu options 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 GENERAL DESCRIPTION OF THE CRAFT TERMINAL 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Introduction 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Alcatel software product and licence delivered to the customer 6. . . . . . . . . . . . . . . . . . .
2.2.1 Software product and licences description 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 Software products and licences list and part numbers 7. . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Craft Terminal main functionalities in the NE management 8. . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 Network Element management supervision 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.2 Network Element general configuration 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.3 Security Management 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.4 External input and output point management 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.5 Diagnosis management 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.6 Communication and routing management 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.7 Equipment and board management 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.8 Port management 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.9 Protection management 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.10 Transmission management 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.11 Cross Connection management 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.12 Performance monitoring management 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.13 Synchronization management 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.14 ATM/IP/ETH Configuration 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3.15 Software management 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 ACRONYMS AND ABBREVIATIONS 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 GLOSSARY OF TERMS 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
01 020520 S.MAGGIO ITAVE P.GHELFI ITAVE
1660SMCREL.3.1
C.T. OPERATOR’S HANDBOOK
C. FAVERO
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
2
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
LIST OF FIGURES AND TABLES
Table 1. Software products part numbers 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2. Software licence part numbers 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
3
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
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 thedifferent functionalities provided by the ELM–USM of the Craft Terminal for Info Model NE.
1.1.2 Target audience
The Introduction Manual is intended for all users.
The documents that should be read before starting this document are:
– 1320CT Basic Operator’s Handbook
1.2 Reading rules
1.2.1 Menu options
All the manuals describe menus, but not necessarily all the options of these menus. When a menu optionis not detailed in a manual, the information are surely given in another manual.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
4
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
5
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
2 GENERAL DESCRIPTION OF THE CRAFT TERMINAL
2.1 Introduction
The Craft Terminal is a project in charge of the local management of single network elements, providingITU– compliant Information Model Interface to the Network Element.Multiple NE management up to 32 Network element is possible obtaining a remote Craft Terminalapplication.
The general information of the Craft Terminal are presented in the Basic Craft Terminal Operator’sHandbook, that the operator have to read before this Handbook.
In the Basic Craft Terminal Operator’s Handbook are described all the general description of use, login,navigation, rules, etc, common to all the NE using the same Craft Terminal.
Further, the same handbook contains the detailed description of common operations as “Installation” andcommon screens as “Network Element Synthesis view”.
The Network Element Synthesis view is the first view presented to the operator entering the application.
Starting from this view it is possible login the NE and than enter the EML–USM views.
This Operator’s Handbook deals with the EML–USM views of the Craft Terminal, which directlypermit to manage the Network Element.
The management main functions of the EML–USM are inserted at para. 2.3 on page 8.
A detailed description of the EML–USM screens is given in Section Ne Management of this handbook.
From the Craft Terminal is possible to run other Specific Software application. These applications are incharge of the ATM and IP management inside the NE such as ATM/IP cross–connection, Backup andRestore configuration files etc.Details information about Specific Application are described in the relevant Operator’s Handbook (seeSection 1 HANDBOOK GUIDE for the code).
The list and part numbers of the SDH software products distributed by Alcatel is inserted in para.2.2 onpage 6.
The Craft Terminal characteristic (computer configuration) are listed in the Basic Craft Terminal Operator’sHandbook.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
6
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
2.2 Alcatel software product and licence delivered to the customer
2.2.1 Software product and licences description
The software products are distributed by Alcatel in a CD–ROM.
In this CD–ROM are contained:
• Software packages for NE management by means of the craft terminal
• Software package of the NE, to be installed in the NE or update the NE (by means of downloadfunction)
The software package used for management permits the dialogue between craft terminal and NE, torealize all the functions of the NES and EML–USM ).
The software package used for updating the NE must be installed on the PC and then downloaded onthe NE, thus following product evolution.
Alcatel typically offers several software licences on the software product (only one for this equipment)
They are referred both to the Network Element software features and to the Craft Terminal softwarefeatures.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
7
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
2.2.2 Software products and licences list and part numbers
Every Software Product is identified by a denomination and a part number, listed on the following table.
Table 1. Software products part numbers
Name ANV Part NumberFactory
Part NumberN.B.
SWP 1660SM R 3.1 CD–ROM 3AL 80676 AA 415.100.664 L
Every Software licence is identified by a denomination and a part number, listed on the following table.
Table 2. Software licence part numbers
Name ANV Part NumberFactory
Part NumberN.B.
SWL–A POINT 60SM Rel. 3.1
LICENCE FEE / STM–13AL 80629 AA 700.200.306 U 1
SWL–B POINT 60SM Rel. 3.1
LICENCE FEE / STM–13AL 80630 AA 700.200.307 V 1
SWL–C POINT 60SM Rel. 2.1
LICENCE FEE / STM–13AL 80631 AA 700.200.308 E 1
SWL–LCT 1660SM Rel. 2.1 LICENCE FEE 3AL 80632 AA 700.200.309 F 2
SWL–RCT 1660SM Rel 2.1 LICENCE FEE 3AL 80633 AA 700.200.310 T 2
N.B. 1 Licence alternative for Network Element software features:• SWL–A: full functionality set• SWL–B: improved functionality set• SWL–C: basic functionality set
N.B. 2 Licence alternative for Craft Terminal software features:• SWL–LCT: local Craft Terminal functionality• SWL–RCT: remote Craft Terminal functionality
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
8
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
2.3 Craft Terminal main functionalities in the NE management
In this chapter, are described the main functionalities of the Craft Terminal, referred to the Network Elementmanagement views, obtained by means EML–USM. The functionalities constitute the heading of each ofthe paragraphs below.
2.3.1 Network Element management supervision
Deals with the NE state and access.
2.3.2 Network Element general configuration
Deals with the general configuration of the equipment.
– Craft Terminal access state (allow or inhibit)– NE Time management– Alarms Configuration
• Alarm Severity Assignment Profile management,• Allow/Inhibit alarm notification,• Alarm re–synchronization.
– Restart NE
2.3.3 Security Management
Deals with the security configuration of the equipment.
– Set Manager list– Set ACD level
2.3.4 External input and output point management
Deals with housekeeping signals input from the external (station alarms) or forwarded (output) towardsthe external.
– Display External points– Configure External points
2.3.5 Diagnosis management
For real time alarm reporting and subsequent fault localization and correction.– Alarm Surveillance
The alarms concerning a particular managed entity will be represented in a synthetic way in all theviews concerning the entity.Alarms information are detailed in the Alarms Surveillance Manual
– Abnormal Condition list ( as result of operator’s commands)
– Event log ManagerPermits to have access to the Event Log file.
– Remote Inventory (”upload” and “view” remote inventory)
– Internal Link Monitor
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
9
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
2.3.6 Communication and routing management
This deals with the configuration parameters concerning the communication protocols for the local NE,the OS and each other related NE. Different types of protection can be managed:
– Local NE and OS addresses– NTP configurations– LAPD, Ethernet, MESA, RAP configurations– IP Configuration– Tunneling Configuration
2.3.7 Equipment and board management
Deals with the presentation of the equipment and the hierarchical tree structure, permitting to define thetypes of boards present. The Board view permits to access the Port view.
– Set / modify / remove boards or subracks– Software information of the selected board.– Remote Inventory
2.3.8 Port management
This permits to set and show the transmission resources (TP) referred only to the port (SDH PDH, HOA,ATM and IP).It is used to check the detailed alarm of each TP and to configure them (many options are the same ofthe Transmission view).
For each port a specific menu is available where various configuration of the specific port can be set, forexample:– Automatic Laser Shutdown– MSP protection– Loopback management and configuration– Single fiber configuration– TP Frame Mode Configuration– Retiming– Ethernet port configuration
Port view is also the entry point of other “management functions” :
– Performance Monitoring management– Cross Connection management
For each port are presented:
– the various ITU–T functional blocks (i.e. PPI, RST, VC4).– details of alarm and state condition– TP role, connection, etc. information
2.3.9 Protection management
This deals with the protection mechanism that is possible to configure in the NE. Different types ofprotection can be managed:
– Equipment protection switching– Multiple Section Protection– MS–SPRing Protection 2 fibers ( 4 fibers is not operative in current release)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
10
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
2.3.10 Transmission management
This permits to cover the management of the transmission resources, opening the views of all the specificports of the NE (SDH and PDH).It supply an overview of the complete signal flow.For all the ports are presented:
– the various ITU–T functional blocks (i.e. PPI, RST, VC4).– synthesis of alarm and state condition– TP role, connection, etc. information
For each port a specific menu is available similar to the Port view where various configuration of thespecific 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 terminatingpoints of a transmission segment. In this way the multiplex structures are created, managing the trafficflow. Similar operation are made on the OverHead cross connections.
– Create / modify cross connections– Activate / deactivate / switch cross connections
2.3.12 Performance monitoring management
This function deals with the set up, collect, log and display performance data associated with the managedNE according ITU–T G.826.It consists of a set of functions that evaluate and report on the behavior of theNEs and their effectiveness relating to the communications taking place on the Network.
– Set up the Performance Monitoring thresholds– Collect and display Performance Monitoring data– Performance Monitoring history
2.3.13 Synchronization management
Deals with the management of the timing.
– Timing source, SSU, T0, T4,T5 and T6 configuration– Protection commands
2.3.14 ATM/IP/ETH Configuration
Describes the operations necessary for the ATM/IP/ETH boards and the ATM/IP/ETH TPs creation.
2.3.15 Software management
Deals with the manipulation of the software package within NE.
– Software download refers to the NE software, permitting to charge the software in the relevant NEto upgrade the NE software, thus following product evolution, or as a consequence of substitutionwith a spare.
– Back–up and restore on the MIB of the NE.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
11
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
3 ACRONYMS AND ABBREVIATIONS
AIS: Alarm Indication Signal
APS: Automatic Protection Switching
ASAP: Alarm Severity Assignment Profile
ATM: Asynchronous Transfer Module
CD–ROM: Compact Disc Read Only Memory
CCITT: Telegraph and Telephone International Consultative Committee
CT: Craft Terminal
DCN: Data Communications Network
ECC: Embedded Communication Channels
EML: Element Management Layer
EPS: Equipment Protection Switching
FAD: Functional Access Domain
Gbit/s: Gigabits per second
GNE: Gateway Network Element
HMI: Human Machine Interface
IEEE: Institute of Electrical and Electronics Engineers
IM: Information Manager
Kbit/s: Kilobits per second
LAN: Local Area Network
LVC: Lower Order Virtual Container
MAC: Media Access Control
Mbit/s: Megabits per seconds
MIB: Management Information Base
MS: Multiplex Section
MSP: Multiplex Section Protection
NAD: Network Access Domain
NAP: Network Access Point
NE: Network Element
NML: Network Management Layer
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
12
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
NTP: Network Time Protocol
OS: Operation System
PI: Physical Interface
SD: Signal Degrade
SF: Signal Failure
TMN: Telecommunications Management Network
TN: Telecommunications Network
TP: Termination Point
USM: User Service Manager
XC: Cross–Connection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
13
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
4 GLOSSARY OF TERMS
Acknowledgment:When an alarm is taken into account by the application, the operator has to acknowledge it to point outthat he has seen it and that he will react in the right way. During alarm configuration it is possible to seta maximum delay for alarm acknowledgement. The operator can decide whether or not the alarm clearhas to be acknowledged.
Administrator:A user who has access rights to all the Management Domains of the Craft Terminal product. He has accessto 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 stateof 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 tail–end node to the head–end node requesting that the head–end perform abridge of the working channels onto the protection channels.
Bridge Request status:A message sent from a tail–end node to all other nodes within the protection system indicating that thetail–end has requested a bridge.
Bridge&switch node:The node that performs the bridge and switch function for a protection event. Where the bridge and switchis performed on a per AU–4 basis, the node executing a bridge and switch of at least one AU–4 is referredto as a bridge and switch node. Note that with a Transoceanic application, a node in the switching statusmay not be a bridge&switch node, whereas a node in the pass–through state may be a bridge&switchnode. 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 itsavailable memory space.
Craft Terminal:Workstation or Personal computer (PC) from which local address to an NE is possible. It can be used toconfigure or perform monitoring tasks on the NE.
Cross–connectionCross–Connections provide the network with the Routing Capabilities, this is the possibility of routing onesignal to a particular destination.
Digital Communication network:Communication Network in which the transmission of data is done in a digitized format.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
14
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
Embedded Communication Channel:Communication channel used in conjunction with packet commuting networks (X25) to manage distantSDH networks. These communication channels are related to the QECC* protocols.
Element Management Layer:This application is responsible for the configuration and management of Network Elements.
Equipment Protection Switching:Used to provide protection for cards within an equipment to protect traffic in the event of card failure.
Extra traffic:Traffic that is carried over the protection trail when it is not used for the protection of working traffic. Extratraffic is not protected and is preempted when the protection trail is required to protect the working traffic.
Filter:They are related to the alarms or events generated on an NE or internally within the OS itself. They canbe configured by an operator to reject specified types of notifications and limit the processing that is appliedto them.
Flushing:This deals with logs. When a log is flushed, all its records are deleted.
Functional Access Domain:It defines the range of functions which are available to a specified user.
Gigabits per second:Unit that corresponds to the transmission of 109 bits every second.
Gateway Network Element:It is a Network Element devoted to the control, from the OS, of those NEs providing a QECC* interface.To do this it uses a QB3* interface and performs the conversion QB3* ↔ QECC*.
Head End:Node executing the bridge (adjacent along the direction where a failure is present)
Human Machine Interface:It is the graphical user interface application through which the operators interact with the system.
History Report:This function enables operators to get information concerning performances, security or alarms on entitiescomposing the network, or on the network itself. The operator specifies the time period for which herequires the report.
Idle:A node that is not generating, detecting or passing–through bridge requests or bridge request statusinformation.
Intermediate node:The node that is not a request node. It is always in the pass–through state. If such a node executes bridgeand switch of at least one AU–4 it is also a bridge&switch node.
International Telegraph and Telephone Consultative Committee:Standard organization for telecommunications. Now called the ITU–T (International TelecommunicationUnion).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
15
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
Isolated Node:A single node that is isolated from a traffic perspective by ring switches on each of its two spans by itsadjacent 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 canundertake signal conversion functions (adapting a signal to two different transmission media) ormultiplexing/demultiplexing functions.
Logs:Logs are files used to store history data concerning the incoming notifications, operator commands andsystem alarms. The size of the log can be configured.
Management Domain:The Craft Terminal product is partitioned into management domains for functional proposes. Eachmanagement 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.
Mis–connection:A condition in which traffic destined for a given node is incorrectly routed to another node and no correctiveaction has been taken.
MSSPRing channels:The range of channels that are part of the MSSPRing operation (i.e. the whole of the working andprotection channels).
Multiplexer:Equipment used to combine several signals to produce a single signal at a higher transmission rate andto 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 usercan manage.
Network Element:Either a telecommunication equipment or groups parts of a Telecommunication Network. Havecharacteristics compliant with CCITT recommendations.
Network Management Level:Designates the management functions performed on networks elements assembled in a network.
Notification:Spontaneous data received by the system concerning an NE.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
16
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
Operation System:A system dedicated to the supervision of NEs in a standard way, using protocols and interfaces. it offers tothe operator a set of functions necessary to supervise the NEs. The 1353SH is an Operation System.
Operator:The end–user of the Craft Terminal. He supervises a part of the network that is dependant on his user profile.
Path:According to ITU–T 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 indicatethe information carried either unidirectionally or bidirectionally between two access points of a ring oneither 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 signalfor further transmission. This functional block also manages clock extraction, signal loss monitoring andloopback functions.
Port:A physical point at which the Network Element can be attached to a transmission medium. A port is eithera 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 SF–R is a bridge request (see ITU–T G841), but LP–S is not: both of them are protocol requests. EvenNR 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 receivedprotocol request.
Protection trail:The trail allocated to transport the working traffic during a switch event. When there is a switch event, trafficon 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 semi–section:The part of multiplex section (i.e. the N/2+1..N channels in a 2–fiber STM–N NE) consisting of protectionchannels.
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 nodessending 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 protectionentities may also be used to carry extra traffic when not used for protection.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
17
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
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 four–fibre rings where working and protectionchannels are contained in separate fibres and the failure only affects the working channels. During a spanswitch, the working traffic is carried over the protection channel on the same span as failure.
Squelched traffic:An all “1”s signal resulting from the squelching process (insertion of AU–AIS in order to guarantee theconnections)
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 multiplexsection switched ring network architecture, this node also performs any necessary squelching ofmisconnected traffic.
Tail End:Node which detects the failure.
Telecommunication Management Network:Defines the concept of interoperable management of TNs. They provide an organized network structureto achieve the interconnection of the different components of the TN and the services to process theinformation.
Telecommunication Network:Describes the network to be managed. Provides the transmission, the transport and the switchingsupports 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 ITU–T G841. Each pair of unprotected channels is made up on one in theworking (semi)section plus one in the protection (semi)section.
Unprotected traffic:See unprotected traffic in ITU–T G841.
User Profile:Identifies the functionalities of the Craft Terminal to which a user has access. A finite number of predefineduser profiles is determined by a fixed set of FADs. To give user access to Craft Terminal functionality, theadministrator must assign a profile to a UNIX user account by choosing one among the predefined profilesinstalled with Craft Terminal.
User Service Manager:These are presentation processes used by the Craft Terminal to manage the Human Machine Interfaceand facilitate the interaction with the product.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
18
01
957.140.602 V
SC.2:INTRODUCTION
/3AL 80755 BA AA
18
18
Working channels:The channels over which working traffic is transported when there are no switch events. An APS systemperforms restoration for the working channels only.
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 semi–section:The part of multiplex section (i.e. the 1..N/2 channels in a 2–fiber STM–N NE) consisting of workingchannels.
Wrapping:Wrapping is the technique that enables the most recent entries in a file to replace the oldest when a fileis full.
END OF DOCUMENT
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
1
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
1660SM REL.3.1 C.T. OPERATOR’S HANDBOOK
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Scope 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2 Target audience 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Acronyms and abbreviations 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.2 Glossary of terms 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 GENERAL INTRODUCTION ON VIEWS AND MENUS 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 EML–USM view organization 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Introduction on the EML–USM menu options 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Views menu introduction 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 Configuration menu introduction 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.3 Diagnosis menu introduction 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.4 Supervision menu introduction 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.5 MS–SPRing menu introduction 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.6 Download menu introduction 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.7 Equipment menu introduction 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.8 Board menu introduction 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.9 Port menu introduction 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.10 EPS menu introduction 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.11 Transmission menu introduction 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.12 Synchronization menu introduction 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.13 External Points menu introduction 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Advices on Navigation principles 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 NE MANAGEMENT SUPERVISION 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 NE management states 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 NE supervision and login 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 NE MANAGEMENT GENERAL CONFIGURATION 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Access state (allow or inhibit NE Craft access) 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Switching from the OS to the Craft Terminal access state 39. . . . . . . . . . . . . . . . . . . . . . . . . 4.1.2 Switching from the Craft Terminal access state back to the OS access state 40. . . . . . . .
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
01 020520 S.MAGGIO ITAVE P.GHELFI ITAVE
1660SM REL.3.1
C.T. OPERATOR’S HANDBOOK
C. FAVERO
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
2
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
4.2 NE Time management 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Alarm Configuration 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 Procedure to modify an ASAP 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2 Alarm Severity Assignment Profile Management (ASAP) 43. . . . . . . . . . . . . . . . . . . . . . . . . 4.3.3 Set SdhNE Alarms Severities 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.4 Allow/Inhibit Alarms Notifications 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.5 Alarms re–synchronization 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Restart NE 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 SECURITY MANAGEMENT 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Set Manager list 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Set ACD level 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 EXTERNAL INPUT AND OUTPUT POINTS MANAGEMENT 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 Displaying external points 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1 Expanding or reducing external points list. 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 External points configuration 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 DIAGNOSIS MANAGEMENT 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 Alarms surveillance 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 Abnormal Condition List 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3 Internal Link Monitor 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4 Log Browsing 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5 Remote Inventory 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5.1 Upload remote Inventory 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.2 View Remote Inventory 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 COMMUNICATION AND ROUTING MANAGEMENT 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1 Overview on Communication and Routing Domain 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1 OSI Protocol on QB3/Qecc 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2 Partitioning into separate Routing Domains 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.3 IP over OSI tunneling for ATM/IP 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.4 OSI over IP tunneling on QB3 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Communication and routing views 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3 Local Configuration 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4 OS Configuration 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5 NTP Server Configuration 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6 LAPD Configuration 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7 Ethernet Configuration 85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8 Reachable Address Prefixes Configuration 87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9 Manual ES Adjacencies table Configuration 88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.10 IP Static Routing Configuration 89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.11 OSPF Area Table Configuration 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.12 IP Address Configuration of Point–to–Point Interfaces 91. . . . . . . . . . . . . . . . . . . . . . . . . . 8.13 ISA board IP Address 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.14 OSI over IP 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.15 IP over OSI 94. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9 EQUIPMENT MANAGEMENT 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 Introduction and navigation 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2 Set and change or remove board/subrack 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3 Connect Fan to CONGI board 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4 Board administrative state 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.1 Setting a board in service 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.2 Setting a board out of service 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
3
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
9.4.3 Consulting a Board’s Administrative state 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.5 Software description 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.6 Remote Inventory 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.7 Show supporting equipment 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 BOARD VIEW 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.1 Introduction 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 Board View Menu 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1 Port Access 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2.2 Change Physical Interface 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2.3 Show Supporting equipment 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 PORT VIEW 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Introduction 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Port View: elements on the TP 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 Port View Menu 120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4 Set Retiming 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.5 AU4 Concatenation 123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6 Physical Media option menu 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6.1 Automatic Laser Shutdown Configuration 126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.2 Show Optical Configuration 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.3 Single Fiber Configuration 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.4 Ms Configuration 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.5 Line Length Configuration 133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6.6 Ethernet Port Configuration 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 Show Supporting Board 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.8 Navigate to Transmission View 137. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.9 Navigate to Monitoring View 138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12 EQUIPMENT PROTECTION MANAGEMENT 139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 Introduction 139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Management: consulting and modifying EPS 140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3 Configuration: revertive and WTR for EPS 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.4 Switching EPS 147. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12.5 EPS Overview 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 MULTIPLEX SECTION PROTECTION MANAGEMENT 155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1 Architecture types 155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2 MSP Options Introduction 156. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.3 MSP Create 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4 MSP Management 161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.1 MSP modification 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.5 MSP Delete 163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6 Display of Protection State 164. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.7 MSP Commands 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.8 MSP overview 168. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 TRANSMISSION VIEW 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1 Overview 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2 View elements 174. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14.3 View Layout 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.1 View Description 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.2 Number of TPs Displayed in Transmission View 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.3 Naming TPs 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3.4 Dynamic View Behavior 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
4
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.4 Transmission view access and menu 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5 Add TP 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.5.1 TP Search 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14.6 TP Configuration 186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6.1 High Order TP Configuration 186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.2 J0 Section Trace management 188. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.3 Low Order TP Configuration 189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.7 TP Frame Mode Configuration 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.8 TP Threshold Configuration 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.9 Terminate/Disterminate TP 194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.9.1 Terminate TP 194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.9.2 Disterminate TP 194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.10 Monitoring Operations 195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.10.1 Creation/Deletion 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.10.2 Configuration 198. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.11 Structure TPs 200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14.12 Loopback 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.12.1 Loopback Configuration 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.12.2 Loopback Management 204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.13 Physical Media 206. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.13.1 Set Domain 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.14 Navigation Commands 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.14.1 Expand 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.14.2 Hide 209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.14.3 Show Supported Board 210. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.14.4 Navigate to Port View 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15 CROSS-CONNECTION MANAGEMENT 213. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1 Introduction 213. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.1.1 Overview 213. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.2 Multiplex Structures for SDH 214. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.3 Definition of Termination Points (TP) 217. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.4 Mapping Tables: TP Names 221. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.5 Cross-Connection Types 222. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.6 Cross-Connection Protection 224. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.2 Operative Sequence to execute Cross-Connections 226. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3 Cross-Connections management 228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.3.1 Search Criteria 229. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.2 Cross-Connection List 231. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.3 Actions available 233. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.4 Create/Modify Cross-Connections 234. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.1 Cross-Connection Parameters 235. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.2 Create a Cross-Connection 240. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.3 Modify a Cross-Connection 246. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.5 Activate/Deactivate/Delete Cross-Connections 249. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.5.1 Activate a Cross-Connection 249. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.5.2 Deactivate a Cross-Connection 249. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.5.3 Delete a Cross-Connection 249. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.6 Split and Join Cross-Connections 250. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.6.1 Split a Cross-Connection 250. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.6.2 Join Two Cross-Connections 252. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15.7 Protection Switching 253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.8 Print 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.9 Show Cross-Connected TPs 256. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
5
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
16 OVERHEAD MANAGEMENT 259. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.1 Introduction 259. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2 OH Connection overview 260. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.3 Overhead views 261. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.4 OH Cross Connection 262. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.5 OH TP creation 266. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.6 OH TP deleting 267. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.7 OH Phone Parameters 268. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17 PERFORMANCE MONITORING 269. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1 Introduction 269. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.1.1 Overview 269. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.2 Supported Performance Counters 270. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.3 Far End (FE) and Near End (NE) Performance Counting 271. . . . . . . . . . . . . . . . . . . . . . . . 17.1.4 Bidirectional counting (24 h Bi) for QoS 272. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.5 End to End (e–e 24h) Performance Counting 272. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.6 Performance Monitoring on AU–PJE 272. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.7 Tandem Connection Termination (TCT) and Monitoring (TCM) 273. . . . . . . . . . . . . . . . . . . 17.1.8 Performance Data Collection 273. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.9 Data Collection 274. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.10 Performance Monitoring History 274. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1.11 Thresholds 274. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.2 Configuration 276. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.3 Display Current Data 281. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.4 Display History Data 284. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.5 PM Threshold Table Selection 286. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.6 PM Threshold Table Create / Modification / Display 289. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17.6.1 Creation 289. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.6.2 Modification 291. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.6.3 Display 291. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18 SYNCHRONIZATION MANAGEMENT 293. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.1 Introduction 293. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2 Synchronization Management 295. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.1 Displaying the Synchronization View 295. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.2 Synchronization View 296. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.3 Timing Source Configuration 299. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.4 Synchronization Protection Commands 302. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.5 Synchronization Configuration for T0/T4 and T4 squelch criteria 303. . . . . . . . . . . . . . . . . . 18.2.6 SSU Configuration 305. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.7 Remove Timing Reference 306. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.8 Change T4 <–> T5 307. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.9 Change 2MHz –>2Mbit 309. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.10 Set and Remove T0 Equal T4 311. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.11 Transmission of SSM Quality Configuration 312. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2.12 Show Timing Source 313. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19 MS–SPRING MANAGEMENT 315. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.1 MS–SPRING introduction 315. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.2 MS–SPRING connection configuration advices 316. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.2.1 2–Fiber MS–SPRING connection configuration advices 316. . . . . . . . . . . . . . . . . . . . . . . . . 19.3 Operative sequence to configure MS–SPRING 317. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.3.1 Operative sequence to configure 2–Fiber MS–SPRING 317. . . . . . . . . . . . . . . . . . . . . . . . . 19.4 MS–SPRING Management 318. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
6
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.4.1 MS–SPRing Main Configuration 319. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.4.2 Squelching Table with 2 fiber Terrestrial applications 325. . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.4.3 Activate, Deactivate and Delete commands 331. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5 MS–SPRING Protection Status and Commands for 2 fiber terrestrial application 332. . 19.5.1 2F MS–SPRing protection commands 332. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.5.2 External commands (2F) 334. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.5.3 2F MS–SPRing dual protection commands 342. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.5.4 2F Protection Status Visualization 347. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20 ATM/IP/ETH CONFIGURATION 365. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.1 Introduction 365. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.2 ATM/IP/ETH board TTPs creation 366. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21 SOFTWARE MANAGEMENT 371. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1 Generalities and descriptions 371. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.1.1 Naming Conventions 372. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 Software download operative sequence 373. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2.1 Software Download upgrade 373. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.2 NE Software package installation procedure 373. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.3 Software Download Manager menu 380. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4 Init download 381. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.5 SW package Activation and Units information 383. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.6 Mib management 385. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
7
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
LIST OF FIGURES AND TABLES
FIGURESFigure 1. EML–USM main view organization. 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2. Menu options flow chart – 1 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3. Menu options flow chart – 2 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4. Menu options flow chart – 3 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5. Menu options flow chart – 4 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6. NE EML–USM Main view. 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7. NE management: setting the access state. 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 8. Consulting and/or setting the local NE time. 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 9. NE Time dialogue box. 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 10. Configuring Alarm Severity Assignment Profile. 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 11. ASAPs Management dialogue box. 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 12. ASAP Edition dialogue box. 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 13. Set ASAP dialogue box. 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 14. Set SdhNE Alarms Severities 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 15. Inhibit alarm notification 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 16. Allow alarm notifications 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 17. Alarm re–synchronization 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 18. Restart NE confirmation 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 19. Set Manager list 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 20. Set ACD level 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 21. Opening the external points view. 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 22. External points view. 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 23. Expanding or reducing the external points list. 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 24. Configuring external points. 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 25. External input point configuration dialogue box. 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 26. External output point configuration dialogue box (MANUAL). 60. . . . . . . . . . . . . . . . . . . . . . Figure 27. External output point configuration dialogue box (FLEXIBLE) 60. . . . . . . . . . . . . . . . . . . . . . Figure 28. Alarm Surveillance 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 29. Alarm Surveillance 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 30. Abnormal condition menu option 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 31. Example of abnormal condition list 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 32. Example of loopback dialog window management 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 33. Internal Link Monitor 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 34. Log Browsing option in Network Element context view 68. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 35. Remote Inventory confirmation request 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 36. Remote Inventory completed 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 37. View Remote Inventory 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 38. Routing subdomain organization example 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 39. OSI over IP tunneling on QB3 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 40. Comm/Routing options 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 41. Local Configuration 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 42. OS Configuration 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 43. NTP Server Configuration 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 44. LAPD Configuration dialog 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 45. Creation LAPD Interface 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 46. Confirmation to change LAPD Role 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 47. Ethernet Configuration 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 48. Ethernet Configuration – L2 only parameter 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 49. RAP Configuration 87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 50. MESA Configuration 88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
8
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 51. IP Static Routing Configuration 89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 52. OSPF Area Table Configuration 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 53. IP Address Configuration of Point–to–Point Interfaces 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 54. ISA Board IP Address 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 55. OSI over IP Tunneling configuration 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 56. IP over OSI Tunneling configuration 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 57. Equipment Overview – Subrack level 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 58. Equipment Overview – Rack level (without Fans subrack) 98. . . . . . . . . . . . . . . . . . . . . . . . . Figure 59. Equipment Overview – Rack level (with Fans subrack) 99. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 60. Equipment Overview – Equipment level 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 61. Equipment menu. 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 62. The list of different boards/subrack relative to an NE slot (examples) 101. . . . . . . . . . . . . . . Figure 63. Connect FAN to CONGI 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 64. Remove FAN connection from CONGI 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 65. Consulting a board’s administrative state. 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 66. Software Description dialogue box. 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 67. Remote Inventory (example) 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 68. Select Printer 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 69. Select Output Format for file 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 70. Equipment Overview – Subrack level 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 71. Equipment view: select the SDH port on a board. 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 72. Example of a Board View 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 73. Example of a Port identification and alarm synthesis 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 74. Board menu options 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 75. After “Port Access” selection (example) 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 76. Change Physical Interface 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 77. Subrack level. 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 78. Example of a Port View 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 79. Termination TP box. 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 80. G.783 Adaptation TP box. 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 81. Examples of port menu options (SDH, PDH and ATM port) 120. . . . . . . . . . . . . . . . . . . . . . . Figure 82. Set Retiming enable (before) 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 83. Set Retiming enable (after) 122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 84. AU4 concatenate/deconcatenate commands 123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 85. Example of a concatenated AU4 transmission view 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 86. Example of a concatenated AU4c 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 87. Physical media menu (SDH port example) 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 88. Automatic Laser Shutdown Management 126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 89. Automatic Laser Shutdown Management (after ALS Function delete) 127. . . . . . . . . . . . . . . Figure 90. ALS and Laser current state (example) 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 91. Visualizing a port optical parameters 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 92. Bidirectional Transmission on a single fiber 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 93. Single Fiber Configuration View 131. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 94. Ms Configuration 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 95. PDH Line Length Configuration View 133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 96. Ethernet Port Configuration options 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 97. Ethernet Port Configuration menu 135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 98. Board View Example. 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 99. After “Navigate to Transmission view” selection 137. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 100. View of Monitoring Operations (example) 138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 101. Consulting EPS 140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 102. EPS Management dialogue box 140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 103. EPS: board selection 143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 104. EPS: choose protected 143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
9
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 105. EPS functional state from protected active board view 144. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 106. EPS functional state from protecting active board view 144. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 107. Configure EPS 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 108. EPS Management dialogue box 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 109. Switching EPS 147. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 110. EPS Switch dialogue box 147. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 111. EPS overview 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 112. EPS overview after Search (Example) 150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 113. Subrack view after “Open Subrack View” command 153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 114. Board view after “Open Board View” command 153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 115. MSP Create Option 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 116. MSP Schema Creation 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 117. MSP schema creation Port dialog 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 118. TP Search 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 119. MSP 1+1 standard protection schema (example) 160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 120. MSP N:1 standard protection schema (example) 160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 121. MSP Management Option 161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 122. MSP Management View 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 123. MSP Delete option 163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 124. MSP Schema Deletion 163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 125. MSP Protection Status Examples 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 126. MSP Commands option 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 127. MSP Commands 167. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 128. MSP overview 168. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 129. MSP overview after Search (Example) 169. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 130. Port view after “Open Port View” command 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 131. Symbols Used in Transmission View 174. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 132. Transmission View Area 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 133. Transmission menu options 178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 134. TP Search Dialog, Initial State 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 135. Information Window 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 136. TP Search Dialog with Various TP Selections 180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 137. TP Search Dialog with Status Information Displayed 181. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 138. Symbols in TP Search 181. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 139. Board History Check List 182. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 140. TP Search Dialog with Different Filtering Options 183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 141. “Information...” Dialog for Search Process 183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 142. Print to Printer 184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 143. Print to File 184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Figure 144. Example Printout 185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 145. High Order TP Configuration 186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 146. J0 Configuration 188. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 147. Low Order TP Configuration 189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 148. TP Frame Mode Configuration 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 149. Degraded Signal Threshold selection 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 150. Monitoring Operations Creation/Deletion 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 151. Display of POM and TCM in Port View (example) 197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 152. Display of POM and TCM/TCT in Port View (example) 197. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 153. Monitor Configuration 198. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 154. Loopback configurations 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 155. Port Loopbacks View 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 156. Loopback Management 204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 157. Set Domain 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Figure 158. Board View (example) 210. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
10
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 159. Port View 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 160. SDH Multiplex Structure according to ITU-T G.707 215. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 161. Frame Construction within the Synchronous Digital Hierarchy 216. . . . . . . . . . . . . . . . . . . . Figure 162. SDH Transport Level Diagram 219. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 163. PDH Transport Level Diagram 220. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 164. Unidirectional Connection 222. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 165. Bidirectional Connection 222. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 166. Example of Broadcast Connection with Three Legs 223. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 167. Protected Unidirectional Connection 224. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 168. Bidirectional Connection – Input Protected 224. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 169. Protected Broadcast 225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 170. Drop and Continue – Normal 225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 171. Cross connection management cascade menu 228. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 172. Cross-Connection Management Dialog (Initial State) 230. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 173. Cross-Connection Management Dialog (After Search) 232. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 174. Protection Criteria 236. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 175. Cross-Connection Icons 239. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 176. Creation of a Unidirectional, Non-Protected Cross-Connection 239. . . . . . . . . . . . . . . . . . . . Figure 177. Create a Bidirectional Protected Cross-Connection 241. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 178. Search for Cross-Connection Output 243. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 179. Create an Unprotected Broadcast Cross-Connection 244. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 180. Create a Protected Broadcast Cross-Connection 245. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 181. Unprotect a Bidirectional Cross-Connection 247. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 182. Protect one Leg of a Broadcast Connection 248. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 183. Split/Join Unprotected Bidirectional Cross-Connection 250. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 184. Split/Join to Protected Bidirectional Cross-Connection 251. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 185. Protection Actions Dialog 253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 186. Select Printer 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 187. Select Output Format 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 188. Show Cross Connected VC4 of an AU4 257. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 189. Overhead options 261. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 190. Cross Connection Management for OverHead dialog 262. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 191. Main Cross-Connection for OverHead dialog 262. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 192. OH TP creation 266. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 193. OH Search TP for creation 266. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 194. OH TP deleting 267. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 195. Phone Parameters dialog window 268. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 196. Far End Performance Monitoring Principles 271. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 197. PM Configuration Dialog (example) 278. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 198. PM question dialog box (example) 278. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 199. Current PM Data Dialog (example) 283. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 200. PM History Data Dialog (example) 285. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 201. PM Threshold Table Select 287. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 202. Create PM Threshold Table 290. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 203. Modify PM Threshold Table 292. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 204. Internal organization of the SETS. 293. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 205. Obtaining the synchronization view. 295. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 206. Synchronization View Example 296. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 207. Synchronization Menu 299. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 208. Timing source configuration for cross–connect equipments 300. . . . . . . . . . . . . . . . . . . . . . Figure 209. Synch. source configuration for ADM equipment 301. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 210. Lockout, Force and Manual commands 302. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 211. Configuring the T0 or T4 SSM algorithm and the squelch criteria 304. . . . . . . . . . . . . . . . . . Figure 212. SSU Configuration 305. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
11
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 213. Synchronization source removing 306. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 214. Synchronization source removing confirmation 306. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 215. Change T4 <–> T5 menu 307. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 216. Change T4 <–> T5 confirmation message 307. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 217. Change T4 <–> T5: command execution 308. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 218. Change 2MHz –>2Mbit menu 309. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 219. Change 2MHz –>2Mbit confirmation message 309. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 220. Change 2MHz –>2Mbit: command execution 310. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 221. T4 equal T0 setting 311. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 222. Transmission SSM Quality 312. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 223. Show Timing Source (example with T2 reference source) 313. . . . . . . . . . . . . . . . . . . . . . . . Figure 224. Display MS–SPRing pull down menu 318. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 225. MS–SPRing Management dialogue box. 319. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 226. Creation Schema dialog box. 320. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 227. Activated MS–SPRing Management 321. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 228. Node Id and associated ring node position. 322. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 229. Ring map configuration 323. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 230. WTR dialog box. 324. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 231. Example of error message 325. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 232. Squelching table 325. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 233. Example of a ring traffic 326. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 234. Connections of the ring of Figure 233. 326. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 235. Squelching table of Node A, West side. 327. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 236. Squelching table of Node A, East side. 327. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 237. Squelching table of Node B, West side. 328. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 238. Squelching table of Node B, East side. 328. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 239. Squelching table of Node C, West side. 329. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 240. Squelching table of Node C, East side. 329. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 241. Squelching table of Node D, West side. 330. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 242. Squelching table of Node D, East side. 330. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 243. Confirmation message 331. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 244. Protection states and commands ”Idle” status (2F) 332. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 245. Ring Protection (2F) 333. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 246. Lockout commands (2F) 334. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 247. Protection and working channels where the lockout command can be activated (2F) 334Figure 248. Tail–end / Head–end association 335. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 249. Tail–end / head–end protection with a lockout working and a one direction ring failure (2F) 336. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 250. Ring protection with a lockout and a ring failure (2F) 337. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 251. Lockout command and non–served failures (2F) 338. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 252. Forced and Manual commands (2F) 339. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 253. Manual and Force Ring command (2F) 339. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 254. Ring Protection with Force and Manual commands (2F) 340. . . . . . . . . . . . . . . . . . . . . . . . . Figure 255. Automatic protection Bridge/Switch (2F) 341. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 256. Example of confirmation dialog box 341. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 257. Clear WTR command (2F) 341. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 258. Ring network reference scheme (2F) 343. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 259. Examples of Double ring failure 344. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 260. 2F Automatic protection (tail/head) for double ring failure visualization 345. . . . . . . . . . . . . Figure 261. Tail / head dual “Events” Protection table (2F) 346. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 262. Manual command applied at the “Reference Point” ring network Figure 259. 348. . . . . . Figure 263. Visualization of the Forced / Manual protection Statuses (2F) 349. . . . . . . . . . . . . . . . . . . . . Figure 264. Visualization of the Lockout command Statuses (2F) 350. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 265. Visualization of Automatic Protection Statuses (2F) 351. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
12
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 266. Protection status with double ring failure (reference point––SS–AN) 352. . . . . . . . . . . . . . . Figure 267. Protection status with double ring failure (reference point––SS–RN) 353. . . . . . . . . . . . . . . Figure 268. Protection status with double ring failure (reference point––OS–AN) 354. . . . . . . . . . . . . . . Figure 269. Protection status with double ring failure (reference point––OS–AN)recovering to “idle” 355. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 270. Double manual ring command (reference point––SS–AN) 356. . . . . . . . . . . . . . . . . . . . . . . . Figure 271. Double manual ring command (reference point––OS–AN) 357. . . . . . . . . . . . . . . . . . . . . . . Figure 272. Manual ring and Lockout Protection (reference point––SS–SN) 358. . . . . . . . . . . . . . . . . . Figure 273. Manual ring and Lockout Protection (reference point––SS–RN) 359. . . . . . . . . . . . . . . . . . Figure 274. Automatic working ring and Manual Ring (reference point––OS–AN) 360. . . . . . . . . . . . . Figure 275. Automatic working ring and Force Ring (reference point––SS–AN) 361. . . . . . . . . . . . . . . Figure 276. Automatic working ring and Lockout working Ring (reference point––SS–SN) 362. . . . . Figure 277. Automatic working ring and Lockout Protection (reference point––OS–RN) 363. . . . . . . . Figure 278. ATM/IP/ETH ports Configuration (examples) 366. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 279. ATM ports Configuration (example) 367. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 280. ATM board view (example) 368. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 281. ATM PSEUDO–SUBBOARD view (example) 368. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 282. ETHERNET board view (example) 369. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 283. ETHERNET port view (example) 369. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 284. Software Download general principle 371. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 285. Software Administration menu 374. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 286. Software Package Administration view 374. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 287. SDH software package installation 375. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 288. ATM software package installation (example) 376. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 289. OMSN enhanced software package creation (part A) 377. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 290. OMSN enhanced software package creation (part B) 378. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 291. Enhanced software package (SDH + ATM) 379. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 292. Equipment view 380. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 293. Download menu 380. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 294. SW Downloading dialogue box example 381. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 295. Software download in progress (example) 382. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 296. Software Package Information dialogue box (example) 383. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 297. Detail software package (example) 384. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 298. NE MIB management 385. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLESTable 1. MSP commands and Auto–switch protection priority 167. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2. Default value for C2/V5 Signal Label 187. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3. PDH TPs 221. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4. SDH TPs 221. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5. Optional and Mandatory Configurable Parameters for Cross-Connection Creation 237. . . . . . Table 6. Modifiable Parameters 246. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7. Threshold table entities association 288. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8. Maximum Performance Parameter Values 291. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
13
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
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.
1.1.2 Target audience
This document is intended for the operators whose role is to manage the Network Elements.
The documents that should be read before starting this document are:
– 1320CT Basic Operator’s Handbook
The documents of this Handbook that should be read before starting this document are:
– Introduction manual
1.2 Terminology
1.2.1 Acronyms and abbreviations
Refer to the Section Introduction manual.
1.2.2 Glossary of terms
Refer to the Section Introduction manual.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
14
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
15
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2 GENERAL INTRODUCTION ON VIEWS AND MENUS
In this chapter the organization of the EML–USM screen, presented after the NE login, is described.
First is introduced the view organization, than the accessible menu options are listed.
At the end some further advice are given for Navigation principles.
2.1 EML–USM view organization
The EML–USM view (see Figure 1. ) is the first window presented to the operator after the login.
It contains the following fields, that provide you with information needed to manage the NE:
• Severity alarm synthesis,• Domain alarm synthesis,• Management status control panel• View title,• View area• Message/state area
The Menu bar and the View area contained in the same NE view permits to performs all the configurationand supervision and display the specific selected item.
The view organization is detailed in the Basic Craft Terminal Operator Handbook to which refer for thedescription, except for the following information, that differs according the NE type:
– Domain alarm synthesisThe different alarm domain type in which can be subdivided the NE are: Synchronization, ExternalPoint, Equipment, Transmission.
Information about the alarms and status is given in the Maintenance section of this handbook.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
16
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Severity alarmssynthesis
Message/state area
View area
View title
Domain alarm synthesis
Managementstates control panel
Menu bar
Figure 1. EML–USM main view organization.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
17
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.2 Introduction on the EML–USM menu options
The menu bar allows to perform configuration and supervision functions on the Network Element.
This paragraph list all the menu options and then more details on the relevant contained entries.
For each of them the relevant operative function are briefly introduced and it is referred the paragraphswhere it is detailed or the introduction to the options of each menu inserted in next paragraphs of thischapter.
The flow charts of Figure 2. on page 31, Figure 3. on page 32, Figure 4. on page 33 and Figure 5. onpage 34 summarize the menu options.
From chapter 3 on details and operative information on the all the views are given. They are not presentedaccording the menu option sequence but according a functional subdivision.
In the menu bar there are permanent menu items always displayed. Staring from the left , the menus are:
– Permanent Menus
• Views (first column). See para.2.2.1 on page 19.
To navigate among the views and set TMN and OverHead parameters.
• Configuration (second column). See para.2.2.2 on page 20.
To set general configuration of the NE, set TMN and OverHead parameters and to show ormodify some parameters (performance monitoring, ATM/IP/ETH configuration, MSP, EPS andcross–connection).
• Diagnosis (third column). See para.2.2.3 on page 21.
To get information about the NE (alarms, performance monitoring, remote inventory, internallink monitor).
• Supervision (fourth column). See para.2.2.4 on page 22.
To set the supervision states (i.e. Craft Terminal enabling).
• MS_SPRing (fifth column). See chapter 19 on page 315.
To manage the 2 fiber MS_SPRing protection, setting the relevant configuration.
• Download (sixth column). See chapter 21 on page 371.
To manage the NE software (download, MIB management).
• Help (last column).
To activate the help.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
18
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Further, in the menu bar there are other menus, presented as an alternative, only when a particular objector option is selected.
– Other Menus
• Equipment (eighth column). See chapter 9 on page 97
To manage the NE as a whole, setting subracks and boards which compose it. From theEquipment view the Board view can be accessed.From the Equipment menu is also possible to start the Specific Terminal application for theATM/IP traffic configuration.
• Board (eighth column). See chapter 10 on page 111.
To show the physical port available in a specific board. It is the entry point for the Port view.
• Transmission (seventh column). See chapter 14 on page 173.
It permits to show and set the Termination Point of the equipment, thus having an overview ofthe complete signal flow of the various port.The menu permits to define all the Cross Connections and manages the transmissionresources, 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). See chapter 11 on page 117.
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). See chapter 12 on page 139.
To manage the EPS protection, setting the relevant configuration.
• Synchronization (seventh column). See chapter 18 on page 293.
To show and modify synchronization parameters.
• External Points (seventh column). See chapter 6 on page 55.
To show and modify housekeeping (environmental) alarms.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
19
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.2.1 Views menu introduction
This menu permits to navigate among the views and set some parameters, by means of the followingentries:
– Backward: Go back to the previous view.
– Forward: Go to the next view.
– Equipment: Open the Equipment view. See chapter 9 on page 97.The “Equipment” menu and the”EPS” menu are then available on the menu bar.
– External Points: Open the External Point view. See chapter 6 on page 55.The “External Point” menu is then available on the menu bar.
– Transmission: Open the Transmission view. See chapter 14 on page 173.The “Transmission” menu is then available on the menu bar.
– Synchronization: Open the Synchronization view. See chapter 18 on page 293.The “Synchronization” menu is then available on the menu bar.
– Refresh: The aim of the refresh feature is to avoid a misalignment between the CT andthe managed NE.This misalignment is due to a loss of notifications coming from the NE.
– Open Object: Navigate and show the contents of the selected object: the current view change.It is equivalent to a double click on the selected object in the view area.
– Open in Window: Navigate and show the contents of the selected object.The current view doesn’t change but a new window with a new view is opened.
– Close: Close the EML–USM view, without stopping the supervision of the NE
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
20
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.2.2 Configuration menu introduction
This menu permits to set general configuration of the NE and to show or modify some parameters, bymeans of the following entries:
– Alarm Severities: Manage the Alarm Severity Assignment Profile.See para. 4.3.2.1 on page 43.
– Set Alarm severities: Send the Alarm Severity Assignment Profile to the selected objectSee para. 4.3.2.2 on page 47.
– Set SdhNe Alarm severities: Send the Alarm Severity Assignment Profile referred to theequipment level.See para. 4.3.2.2 on page 47.
– NE Time: Display and set the NE local time. See para. 4.2 on page 41.
– Performance: Manage the the Performance Monitoring domain.Used to define the PM parameters, opening the following menu options:• Threshold table: See para.17.5 on page. 286.
– EPS overview : Allows to display as well as search for EPS states.See paragraph 12.5 on page 149.
– Set ACD level: See para.5.2 on page 54.
– Cross Connection Management: Manage the connection of the paths.See para.15.3 on page 228
– Loopback Management: Enter the loopback management. See para. 14.12 on page 201.Used to configure the loopback command for commissioning ormaintenance purposes.
– Comm/Routing: Enter the Communication and Routing management.See paragraph 8 on page 73.Used to define the parameters for NE and OS in the TMN, opening thefollowing menu options:
• Local configuration
• OS Configuration
• NTP Server Configuration
• Interfaces Configuration– LAPD Configuration– Ethernet Configuration
• OSI Routing Configuration– RAP Configuration– MESA Configuration
• IP Configuration– IP Static Routing Configuration– OSPC Area Configuration– IP Address Configuration of point–to–point interfaces– ISA board IP address
• Tunnelling Configuration– OSI Over IP– IP Over OSI
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
21
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– Overhead: Handle the operation on the Overhead bytes. See para.16 on page 259.Used to define the parameters in the following menu options:• OH Cross Connection• OH Phone Parameter• OH TP creation• OH TP deleting
– MSP overview : Allows to display as well as search for MSP states.See paragraph 13.8 on page 168.
– ATM/IP/ ETH Configuration : It allows to create the TPs for the ATM/IP/ETH connections.See paragraph 20.2 on page 366.
2.2.3 Diagnosis menu introduction
This menu permits to get information about the NE, by means of the following entries:
– Alarms: Display the Alarms Surveillance information of the NE.See para. 7.1 on page 63.It opens the following menu options:• NE alarms• Object alarms• Subtree alarms• Equipment alarms• Transmission alarms• External Points alarms
– Performance data: Not operativeIt opens the following menu options:• 15 Minutes• 24 Hours
– Log Browsing: Manage the events stored in the NE. See para. 7.4 on page 68It opens the following menu options:• Alarm Log• Event Log• Software Trace Log
– View Remote Inventory: Display the remote inventory data, previously stored in the Craft Terminalby means the “upload remote inventory” performed in the “Supervisory”menu. See para 7.5.2 on page 70.
– 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 65.
– Internal Link Monitor: Indicates the presence of failure on Rx or Tx side for the signalincoming/outgoing from/to the active/standby MATRIX board.Refer to paragraph 7.3 on page 67.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
22
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.2.4 Supervision menu introduction
This menu permits to set the supervision states of the NE, by means of the following entries:
– Access State: Manage the supervision access to the NE, with CT or OS.See para.4.1 on page 39.It opens the following menu options:• OS• Requested
– Alarms: Manage the alarms supervision of the NE.It opens the following menu options:• Resynchronize. See para. 4.3.5 on page 51.• Allow / Inhibits Notifs. See para. 4.3.4 on page 50.
– Upload Remote Inventory:Store the Remote Inventory data in the Craft Terminal.See para. 7.5.1 on page 69.
– Set Manager list: See para.5.1 on page 53.
– Restart NE: Reset the NE software.See para.4.4 on page 52.
2.2.5 MS–SPRing menu introduction
This menu permits to manage the 2 fiber and 4 fiber MS–SPRing protection (the last is not operative incurrent release) , setting the relevant configuration, by means of the following entries:
– Main dialog for MS–SPRing management: Contains all the command to set and manage theMS–SPRingSee para. 19.4.1 on page 319.
2.2.6 Download menu introduction
This menu permits to manage the NE software, by means of the following entries:
– Init download: Manage the software download, upgrading the NE.See para.21.4 on page 381.
– Units info: Show the status of the software package installed in the NE memory banks.See para.21.5 on page 383.
– Mib management: Permits backup of NE software configuration and restore of backupped file.See para. 21.6 on page 385.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
23
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.2.7 Equipment menu introduction
This menu permits to manage the NE as a whole, setting the boards which compose it, by means of thefollowing entries:
– Set: Add or change the board type (a list is proposed).See para. 9.2 on page 101.
– Modify: Change the board type without previously remove it. It is only possiblebetween compatible board or modules (ex. it is possible to change froman Long and Short 1.1 optical module)See para. 9.2 on page 101.
– Remove: Remove the board.See para. 9.2 on page 101.
– Set in service: Insert a lock symbol in the board. See para. 9.4.1 on page 105.
– Set out of service Delete the lock symbol in the board, enabling changes.See para. 9.4.2 on page 105.
– Reset: Not operative.
– Software description: Show information on the software of the board. See para. 9.5 on page 106.
– Remote Inventory: Show the Remote Inventory data inserted in the equipment.See para. 9.6 on page 107.It opens the following menu options:• Subrack level• Board level
– ISA Board IP Address: Used to define the ISA board IP address. See paragraph 8.13 on page 92.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 109.
– ISA navigate: Start the Specific Craft Terminal application for the ATM/IP trafficmanagement configuration.For details refer to the specific IP or ATM Operator’s Handbook.
– Connect FAN to CONGI#10: Enable the management of the Fan subrack alarms on CONGI inserted in slot10.N.B. This option is available only after having selected a CONGI
board at Subrack level view.
– Connect FAN to CONGI#12: Enable the management of the Fan subrack alarms on CONGIinserted in slot12.N.B. This option is available only after having selected a CONGI
board at Subrack level view.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
24
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.2.8 Board menu introduction
This menu permits to show the physical port available in a specific board (alarm synthesis and port symbol)and to access the port view, by means of the following entries:
– Port Access: Access the “Port view”. See para. 10.2.1 on page 114.
– Change Physical Interface Change the SPI or PPI object into PPI or SPI (and viceversa) on thebi–mode port( 140Mbi/s/ STM–1 switchable). See para. 10.2.2 onpage 115.
– Show supporting equipment: Navigate to the upper subrack level. See para. 10.2.3 on page 116.
– ATM/IP/ETH Configuration: It allows to create the TPs for the ATM/IP/ETH connections.See paragraph 20.2 on page 366.N.B. This menu is available only if an ATM/IP/ETH board has
been equipped in the subrack.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
25
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.2.9 Port menu introduction
This menu permits to set and show the transmission resources (TP) referred to the Port, by means of theentries indicated in the following list.
The menu differs according the port type (SDH, PDH, HOA, ATM, IP and ETHERNET).
The “Port view” is reached by means the Equipment menu and Board view to check the detailed alarmspresented, but the available menu permits to configure the port (many setting options listed in the portmenu are common with the “Transmission” view).In these views are presented only the TP specific of the port.
It permits navigation to the Transmission view.
– TP configuration: Set parameters for the Overhead (Signal Label and Path Trace) onSynchronous TP’s.See para 14.6 on page 186.
– TP Threshold Configuration: Set B2 excessive BER and Signal Degraded parameter.See para 14.8 on page 193.
– TP Frame Mode Configuration: Set parameters for 2Mbit/s G.703/704 or ISDN–PRAmanagement.Only for PDH ports views. See para 14.7 on page 191
– Set Retiming: Set the retiming feature applies to the outgoing 2Mbit/s. See paragraph 11.4 on page 121.It opens the following options:
• Enable• Disable
– AU4 Concatenation: Only for SDH ports views. See para. 11.5 on page 123.
– Cross Connection: Manage the connection of the paths. See para.15 on page 213.It opens the following menu options:• Cross Connection Management• Create Cross Connection• Modify Cross Connection
– Monitoring Operation: Set parameters for POM, SUTSee para. 14.10 on page 195.Not available for PDH port.It opens the following menu options:• Creation / Deletion• Configuration
– Performance: Set and show Performance Monitoring parameters and data.See chapter 17 on page 269.It opens the following menu options:• Configure Performance Monitoring• Display Current Data• Display History Data
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
26
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– Loopback: Enter the loopback management. See para. 14.12 on page 201.Used to configure the loopback command for commissioning ormaintenance purposes:
• Port Loopback Configuration• Loopback management
– MSP Manage the Multiplex Section Protection of the NE.See Chapter 13 on page 155.Only for SDH ports view.It opens the following menu options:
• MSP Create• MSP Management• MSP Commands• MSP Delete
– Physical Media: Manage the physical setting of the TP of the ports. Not applicable to HOAport. See para.11.6 on page 125.It opens a menu which differs according the port type:
– SDH port:• ALS Management• Show Optical Configuration• TX Quality Configuration• Single Fiber Configuration• LAPD Configuration• Ms Configuration
– PDH port:• Line Length Configuration• HDSL Configuration• NT G703/704 Configuration• NT X21 Configuration
– ETHERNET port:• Remote Laser Management• ALS Management• Ethernet Port Configuration• ATM/IP/ETH Configuration
– Show supporting board: Navigate to the upper board level.See para.11.7 on page 136.
– Navigate to Transmission view: permit to show a complete overview about the signal flow, openingall TP’sSee para.11.8 on page 137
– Navigate to Monitoring view: permit to show for a selected TP the related POM/SUT/TCM and TCTobject if present.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
27
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.2.10 EPS menu introduction
This menu permits to manage the EPS protection, setting the relevant configuration, by means of thefollowing entries :
– Management: Set EPS protections. See para.12.2 on page 140.
– Configure: Set revertive / not revertive and WTR parameters.See para. 12.3 on page 145.
– Switch: Manage the EPS operator commands (Force, Manual, Lockout)See para.12.4 on page 147.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
28
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.2.11 Transmission menu introduction
This menu permits to show and set the Termination Point of the equipment, thus having an overview ofthe complete signal flow of the various port.
The menu permits to define all the Cross Connections and manages the transmission resources, settingthe relevant configuration.
Further access the Performance Monitoring and manage Multiplex Section Protections and Loopbacksfunctions.
It permits navigation to the Port view.
The menu lists the following entries:
– Add TP: Search and add TP to the transmission view, than presented in the screen.See para.14.5 on page 179.
– Expand: Display the TP’s related to a selected TP. See para.14.14.1 on page 208.It opens the following menu options:• Next level of lower TP• All lower TP• Next level of upper TP• All upper TP
– Hide: Remove the TP from the screen of the Transmission view.See para.14.14.2 on page 209.It opens the following menu options:• Lower TP• Upper TP• Selected TP
– TP configuration: Set parameters for the Signal Label and Path trace.See para.14.6 on page 186.
– TP Frame Mode Configuration: Set parameters for 2Mbit/s G.703/704 or ISDN–PRAmanagement.Only for PDH ports views. See para 14.7 on page 191
– TP Threshold Configuration: Set B2 Ex BER and Signal Degrade threshold.See para. 14.8 on page 193.
– Terminate TP: Terminate the AU4–CTP paths. See para.14.9 on page 194.
– Disterminate TP: Disterminate the AU4–CTP paths. See para.14.9 on page 194
– AU4 Concatenation Only for SDH ports views. See para. 11.5 on page 123.
– Cross Connection: Manage the connection of the paths. See para.15 on page 213.It opens the following menu options:• Cross Connection Management• Create Cross Connection• Modify Cross Connection• Port Switch Over• Show Cross Connected TP’s
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
29
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– Monitoring Operation: Set parameters for POM, SUT and Tandem Connection TP’s.See para.14.10 on page 195It opens the following menu options:• Creation / deletion• Configuration
– Performance: Set and show Performance Monitoring parameters and data.See chapter 17 on page 269.It opens the following menu options:• Configure Monitoring• Display Current Data• Display History Data
– Structure TP’s: Define the structure of a selected TP (TU2, TU3, TU12, VC3/VC4, VC12)See para.14.11 on page 200.
– Loopback : Enter the loopback management. See para. 14.12 on page 201.Used to configure the loopback command for commissioning ormaintenance purposes:It opens the following menu options:• Port Loopback Configuration• Loopback management
– Physical Media: Manage the TP physical setting. See para.14.13 on page 206.It opens the following menu options:• ALS Management• Show Optical Configuration• TX Quality Configuration• Single Fiber Configuration• Extra traffic• Regeneration Section management• Line Length Configuration• Set Domain• HDSL Configuration• NT Configuration• X21 Configuration
– MSP Manage the Multiplex Section Protection of the NE.It opens the following menu options:• MSP Create• MSP Management• MSP Commands• MSP Delete• NE MSP synthesis
– Show supported board: Navigate to the board supporting the selected TPSee para.14.14.3 on page 210.
– Navigate to Port view: Navigate to the port supporting the selected TPSee para.14.14.4 on page 211.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
30
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.2.12 Synchronization menu introduction
This menu permits to set and show the Synchronization parameters and status, setting the relevantconfiguration, 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 299.
– Protection Command: Manage commands (force, manual, lockout) for the selected timingreference. See para.18.2.4 on page 302.
– T0 Configuration: Enable/disable SSM and WTR on the T0 synchronization source.See para.18.2.5 on page 303.
– T4 Configuration: Enable/disable SSM, WTR and Squelch Criteria on the T4synchronization source. See para.18.2.5 on page 303.
– SSU Configuration: Set NE single or with SSU. See para.18.2.6 on page 305.
– Transmitted SSM Quality Configuration: Set SSM quality transmitted on the selected T1 SDHtiming reference. See para.18.2.11 on page 312.
– Frame Mode Configuration: Set parameters for 2Mbit/s G.703/704 or ISDN–PRAmanagement.Only for PDH ports views. See para 14.7 on page 191
– Remove Timing Reference See para.18.2.7 on page 306.
– Change T4<–>T5: Change the synchronization physical interface from 2MHz (T4) to2Mbit/s (T5) without traffic” and vice–versa (see para18.2.8 on page307.
– Change 2MHz–>2Mbit Change the source of a protection unit from 2Mhz (T3) to2Mbit(T6) and viceversa (see para. 18.2.9 on page 309).
– Set T0 Equal T4 See para.18.2.10 on page 311.
– Remove T0 Equal T4 See para.18.2.10 on page 311.
– Show Timing Source: Show the “port view” related to the selected timing reference.See para.18.2.12 on page 313.
2.2.13 External Points menu introduction
This menu permits to display and set the input/output environmental alarm (housekeeping alarm), bymeans of the following entries:
– Configuration: Set the input/output environmental alarm.See para. 6.2 on page 59.
– Display: Show the list of the input/output environmental alarm.See para. 6.1 on page 56.It opens the following menu options:
• Show external Input Points• Show external Output Points• Show all external Points
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
31
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ËËËËËËËËËËËË
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ËËËËËËËËËËËË
ËËËËËËËËËË
Vie
ws
Co
nfi
gu
rati
on
D
iag
no
sis
Bac
kwar
d
Eq
uip
men
t
Ext
ern
al P
oin
ts
Tran
smis
sio
n
Syn
chro
niz
atio
n
Co
mm
/Ro
uti
ng
Ove
rhea
d
Ope
n O
bjec
t
Ope
n in
Win
dow
Clo
se
Loca
l Con
figur
atio
n
OS
Con
figur
atio
n
NT
P S
erve
r
Inte
rfac
es
OS
I Rou
ting
IP C
onfig
urat
ion
OH
Cro
ss
OH
TP
Cre
atio
n
OH
TP
Del
etin
g
Con
figur
atio
n
Con
figur
atio
n
Con
nect
ion
Ala
rm S
ever
ities
Set
Ala
rm S
ever
ities
NE
Tim
e
Per
form
ance
Set
AC
D le
vel
Cro
ss C
onne
ctio
nM
anag
emen
t
ÇÇÇÇÇÇÇÇÇÇÇÇ
Thr
esho
ld ta
ble
Ala
rms
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
NE
ala
rms
Obj
ect a
larm
s
Equ
ipm
ent a
larm
s
Tran
smis
sion
ala
rms
Ext
erna
l Poi
nts
Per
form
ance
dat
aÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
15 M
inut
es
24 H
ours
Lo
g B
row
sin
g
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
Ala
rm L
og
Eve
nt L
og
Vie
w R
emot
eIn
vent
ory
Sub
tree
ala
rms
alar
ms
DCBA E
Abn
orm
alC
ondi
tion
List
ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ
Oh
Pho
neP
aram
eter
s
Loop
back
Man
agem
ent
Sev
eriti
esS
et S
dhN
e A
larm
MS
P o
verv
iew
For
war
d
Ref
resh
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
LAP
D C
onfig
urat
ion
Eth
erne
t
RA
P C
onfig
urat
ion
ME
SA
Con
figur
atio
n
Con
figur
atio
n
Con
figur
atio
n
ÇÇÇÇÇÇÇÇÇÇÇÇ
Tunn
elin
gC
onfig
urat
ion
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IP S
tatic
Rou
ting
OS
PF
Are
a
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IP A
ddre
ss C
onfig
.
IP o
ver
OS
I
EP
S o
verv
iew
AT
M/IP
/ET
H
ÇÇÇÇÇÇÇÇÇÇÇÇ
Sof
twar
e Tr
ace
Log
No
te: A
,B,C
,D a
nd
E S
ee n
ext
fig
ure
s
Con
figur
atio
n
Con
figur
atio
n
of P
oint
–toP
oint
inte
rfac
es
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ISA
boa
rd IP
ad
dres
sÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OS
I ove
r IP
Con
figur
atio
nIn
tern
al L
ink
Mon
itor
Figure 2. Menu options flow chart – 1
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
32
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ËËËËËËËËËË
ËËËËËËËËËË
Su
per
visi
on
Do
wn
load
Acc
ess
Sta
te
ÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇO
S
Req
uest
ed
Ala
rms
ÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇR
esyn
chro
nize
Allo
w N
otifs
Upl
oad
Rem
ote
Set
Man
ager
list
Inve
ntor
y
Init
dow
nloa
d
Uni
ts in
fo
Mib
Res
tart
NE
ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇI
nhib
it N
otifs
Man
agem
ent
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
ËËËËËËËËËËËË
Eq
uip
men
t
Set
Mod
ify
Rem
ove
Set
in s
ervi
ce
Set
out
of s
ervi
ce
Sof
twar
e
Rem
ote
Inve
nto
ry
Sho
w s
uppo
rtin
g
Res
et
desc
riptio
n
equi
pmen
t
Sub
rack
leve
l
Boa
rd le
velA
G
ËËËËËËËËËË P
ort A
cces
s
Sho
w s
uppo
rtin
g
Bo
ard
equi
pmen
tG
F
Cha
nge
Phy
sica
lIn
terf
ace
No
te: A
, See
pre
vio
us
fig
ure
s
ISA
Nav
igat
e
F, S
ee n
ext
fig
ure
ËËËËËËËËËËM
S_S
PR
ing
Mai
n D
ialo
g fo
r M
S_S
PR
ing
man
agem
ent
ISA
Boa
rd IP
A
ddre
ss
Con
figur
atio
nA
TM
/IP/E
TH
Con
nect
FA
N to
C
ON
GI#
10
Con
nect
FA
N to
C
ON
GI#
12
NB
.1
NB
.1
NB
.1 a
vaila
ble
on
ly if
CO
NG
I bo
ard
has
bee
n s
elec
ted
in t
he
Su
bra
ck le
vel v
iew
Figure 3. Menu options flow chart – 2
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
33
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ËËËËËËËËËËËËT
ran
smis
sio
n
Add
TP
Exp
and
Hid
e
ÇÇÇÇÇÇÇÇÇÇ
Nex
t Lev
el o
fLo
wer
TP
s
ÇÇÇÇÇÇÇÇÇÇ
Nex
t Lev
el o
f
ÇÇÇÇÇ
All
Low
er T
Ps
ÇÇÇÇÇÇÇÇÇÇ
All
Upp
er T
Ps
Upp
er T
Ps
ÇÇÇÇÇÇÇÇÇÇ
Low
er T
Ps
ÇÇÇÇÇÇÇÇÇÇ
Upp
er T
Ps
ÇÇÇÇÇÇÇÇÇÇ
Sel
ecte
d T
Ps
TP
con
figur
atio
n
AU
4C
onca
tena
tion
Cro
ss C
on
nec
tio
n
ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ
Cro
ss C
onne
ctio
nM
anag
emen
t
ÇÇÇÇÇÇÇÇÇÇ
Cre
ate
Cro
ss
Con
nect
ions
ÇÇÇÇÇÇÇÇÇÇ
Mod
ify C
ross
Con
nect
ions
ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ
Sho
w C
ross
C
onne
cted
TP
sÇÇÇÇÇÇÇÇÇÇ
Por
t Sw
itch
Ove
r
Mo
nit
ori
ng
ÇÇÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇÇÇ
Cre
atio
n / D
elet
ion
Con
figur
atio
n
Per
form
ance
Str
uctu
re T
Ps
ÇÇÇÇÇÇÇÇÇÇS
how
Opt
ical
ÇÇÇÇÇÇÇÇÇÇA
LS M
anag
emen
t
Con
figur
atio
n
ÇÇÇÇÇÇÇÇÇÇT
X Q
ualit
yC
onfig
urat
ion
ÇÇÇÇÇÇÇÇÇÇS
ingl
e F
iber
Con
figur
atio
n
ÇÇÇÇÇÇÇÇÇÇE
xtra
traf
fic
ÇÇÇÇÇÇÇÇÇÇR
egen
erat
ion
Sec
tion
man
age ÇÇ
ÇÇÇÇÇÇÇÇN
E M
SP
syn
thes
isÇÇÇÇÇÇÇÇÇÇL
ine
Leng
htC
onfig
urat
ion
Sho
w S
uppo
rted
Boa
rds
Nav
igat
e to
Por
t Vie
w
Ph
ysic
al M
edia
:
ÇÇÇÇÇÇÇÇÇÇÇÇ
Sho
w O
ptic
alC
onfig
urat
ion
ÇÇÇÇÇÇÇÇÇÇÇÇ
ALS
Man
agem
ent
ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ
Tx
Qua
lity
Con
figur
atio
n
ÇÇÇÇÇÇÇÇÇÇM
SP
Man
agem
ent
MS
P c
omm
ands
ÇÇÇÇÇÇÇÇÇÇ
Por
t Loo
pbac
kC
onfig
urat
ion
ÇÇÇÇÇÇÇÇÇÇ
Loop
back
man
agem
ent
TP
con
figur
atio
n
Cro
ssC
on
nec
tio
nw
ith S
DH
por
t
ÇÇÇÇÇÇ
LAP
D c
onfig
.
with
PD
H p
ort
ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ
Con
figur
atio
n
ÇÇÇÇÇÇÇÇÇÇ
Por
t Loo
pbac
kC
onfig
urat
ion
ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ
Loop
back
man
agem
ent
AU
4C
onca
tena
tion
ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ
Cro
ss C
onne
ctio
nM
anag
emen
t
ÇÇÇÇÇÇÇÇÇÇ
Cre
ate
Cro
ss
Con
nect
ion
ÇÇÇÇÇÇÇÇÇÇ
Mod
ify C
ross
Con
nect
ion
Set
Ret
imin
g
ÇÇÇÇÇÇÇÇÇÇ
Ena
ble
ÇÇÇÇÇÇÇÇÇÇ
Dis
able
ÇÇÇÇÇÇÇÇÇÇÇÇ
Per
form
ance
Con
figur
eP
erfo
rman
ce
ÇÇÇÇÇÇÇÇÇÇÇÇ
Dis
play
Cur
rent
Dat
a
ÇÇÇÇÇÇÇÇÇÇÇÇ
Dis
play
His
tory
Dat
a
Nav
igat
e to
Tran
smis
sion
vie
w
ÇÇÇÇÇÇÇÇÇÇ
Con
figur
eM
onito
ring
ÇÇÇÇÇÇÇÇÇÇ
Dis
play
Cur
rent
Dat
a
ÇÇÇÇÇÇÇÇÇÇ
Dis
play
His
tory
Dat
a
Ph
ysic
al M
edia
:
ÇÇÇÇÇÇÇÇÇÇÇÇ
Sin
gle
Fib
erC
onfig
urat
ion
Sho
w s
uppo
rtin
gbo
ard
C
F
ËËËËËËËËËË
Po
rtF
No
te:
F a
nd
C, S
ee p
revi
ou
s fi
gu
res
TP
Thr
esho
lds
conf
igur
atio
n
ÇÇÇÇÇÇÇÇÇÇ
nb
2
nb
1: o
nly
fo
r P
DH
po
rt
nb
2: o
nly
fo
r S
DH
po
rt
MS
P C
omm
ands
Lo
op
bac
k
Lo
op
bac
k
ÇÇÇÇÇÇÇÇÇÇ
Set
Dom
ain
ÇÇÇÇÇÇÇÇÇÇ
ÇÇÇÇÇÇÇÇÇÇ
MS
P
MS
P
C
Cre
atio
n / d
elet
ion
Con
figur
atio
n
TP
Thr
esho
ldC
onfig
urat
ion
Term
inat
e T
P
Dis
tern
inat
e T
P
TU
2
TU
3
TU
12
VC
3/V
C4
VC
12
ÇÇÇÇÇÇ
Ms
Con
figur
atio
n
ÇÇÇÇÇÇÇÇÇÇÇÇ
HD
SL
Con
figur
atio
n
ÇÇÇÇÇÇÇÇÇÇÇÇ
NT
G70
3/G
704
Con
figur
atio
n
ÇÇÇÇÇÇÇÇÇÇÇÇ
NT
X21
C
onfig
urat
ion
ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ
HD
SL
Con
figur
atio
n
ÇÇÇÇÇÇÇÇÇÇ
NT
Con
figur
atio
n
ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ
X21
Con
figur
atio
n
Line
Len
ght
TP
Fra
me
mod
eco
nfig
urat
ion
nb
1
TP
Fra
me
mod
eco
nfig
urat
ion
ÇÇÇÇÇÇÇÇÇÇM
SP
Del
ete
ÇÇÇÇÇÇÇÇÇÇ
MS
P C
reat
e
nb
1
Op
erat
ion
s
Mo
nit
ori
ng
Op
erat
ion
s
Nav
igat
e to
Mon
itorin
g vi
ew
Mon
itorin
g
with
ET
HE
RN
ET
por
t
ÇÇÇÇÇÇÇÇÇÇÇÇ
ALS
Man
agem
ent
ÇÇÇÇÇÇÇÇÇÇÇÇ
Rem
ote
lase
rM
anag
emen
t
ÇÇÇÇÇÇÇÇÇÇÇÇ
Eth
erne
t po
rtC
onfig
urat
ion
ÇÇÇÇÇÇÇÇÇÇÇÇ
AT
M/IP
/ET
HC
onfig
urat
ion
nb
2
Figure 4. Menu options flow chart – 3
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
34
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ËËËËËËËËËË
Ep
s
Man
agem
ent
Con
figur
e
Sw
itch
ËËËËËËËËËËËËËË
Syn
chro
niz
atio
n
T0
Con
figur
atio
n
T4
Con
figur
atio
n
SS
U C
onfig
.
Set
T0
Equ
al T
4
Tim
ing
Sou
rce
Con
figur
atio
n
Pro
tect
ion
Com
man
d
Rem
ove
Tim
ing
Ref
eren
ce
Tran
smitt
edS
SM
Qua
lity
Con
figur
atio
n
Sho
w T
imin
gS
ourc
e
ËËËËËËËËËËËËE
xter
nal
Po
ints
Con
figur
atio
n
Dis
pla
y
ÇÇÇÇÇÇÇÇÇÇÇÇ
Sho
w E
xter
nal
Inpu
t P
oint
s
ÇÇÇÇÇÇÇÇÇÇÇÇ
Sho
w E
xter
nal
Out
put P
oint
s
ÇÇÇÇÇÇÇÇÇÇÇÇ
Sho
w A
llE
xter
nal P
oint
s
Rem
ove
T0
Equ
al T
4
ED
B
No
te:
B, D
an
d E
, See
pre
vio
us
fig
ure
s
Cha
nge
T4
<–>
T5
Fra
me
Mod
e C
onfig
urat
ion
Cha
nge
2MH
z–>
2M
bit
Figure 5. Menu options flow chart – 4
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
35
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
2.3 Advices on Navigation principles
Navigation rules are the same for all the NE using the same Craft Terminal Info Model.
This general rules are described in the “Basic Craft Terminal Operator Handbook”.
In this paragraphs are instead inserted menu options typical for this NE involved in Navigation andexample of Navigation.
To reach a particular view of the NE there are several ways (navigation is also possible mixing the differentways):
• double click on the selected object
• select the object and use the Open object or Open in Window option of the View pull downmenu
• use the Menu option tree structure. The View pull down menu permits to show the followingmenus:
– Equipment– Transmission– Synchronization– External Points
The menu structure permits to open the same window following several menu paths.
EXAMPLE: to obtain the “Create Cross Connection” window:
– First navigation path:Open View – Transmission pull down menuOpen Transmission – Cross Connection – Cross Connection Management pull downmenuSelect Create option in the presented window
– Second navigation path:Open View – Equipment pull down menuDouble click on Board bodySelect the Board to access the Board viewOpen Board – Port Access pull down menuOpen Port – Cross Connection – Create Cross Connection pull down menu
– Third navigation path:Open Configuration – Cross Connection Management pull down menuSelect Create option in the presented window
The menu structure also permits to pass from a view menu to another (i.e. from “port view” to”board view”or to “transmission view”) thus facilitating the operators activity.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
36
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
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 16).The Equipment view enables a fast navigation through all levels of the equipment hierarchy.Navigation is done from higher to lower levels. The NE hierarchy is generally organized in the followingway: subrack > board > port > TP.
The navigation through different levels of the NE hierarchy is performed by double clicking on the objects:(see also para 9.1, pg. 97)
• the first level shows the subrack level of the Equipment view (see Figure 1. on page 16);• 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, Figure 1. on page 16 ) the Showsupporting equipment option from the Equipment menu, the Rack level view is presented.
In the Rack Level view two subrack are presented:
– at the top the 1660SM Subrack, named SR60M– at the bottom the Fans Subrack, named SRFAN.
The Fans Subrack presence is managed with the Set option as for the boards of the1660SM Subrack (refer to paragraph 9.2 on page 101 for details)
Further, selecting in the Rack level view the Show supporting equipment option from theEquipment menu, the Equipment level view is presented.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
37
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
3 NE MANAGEMENT SUPERVISION
This chapter is dedicated to the NE states and NE access.
3.1 NE management states
The elementary building blocks of any telecommunication network are the Network Elements (NEs).
Operating with the Craft Terminal the NE can present different management states according to thecondition of the connection (supervision, local access, connection state, etc). Also general Alarm statusare presented.Management states are present at Network Element Synthesis view level and at USM–EML view level.All the information referred to the management states are inserted in the Basic Craft Terminal Operator’sHandbook.Any disruption in the communication link between the CT and the NE results in an update of themanagement states when the CT has detected the communication failure.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
38
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
3.2 NE supervision and login
The Network Element Synthesis views enable you to get access to the current NE EML–USM viewdescribed in this handbook.
The Network Element Synthesis views enable you to work on local or remote NE, selecting it and activating“Supervision” and “Login”, as described in the Basic Craft Terminal Operator’s Handbook.
The EML–USM Main view is presented as for the following figure.
Figure 6. NE EML–USM Main view.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
39
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
4 NE MANAGEMENT GENERAL CONFIGURATION
In this chapter general configuration referred to the equipment management are described (Craft Terminalaccess, NE Time, Alarms configuration, etc).
4.1 Access state (allow or inhibit NE Craft access)
The NE can be managed by the OS or by the Craft Terminal. To control the competition of the OS and theCT, a Local Access Control (LAC) is available.If the LAC is “granted” that means the CT is allowed to manage the NE. In the view the icon with a keysymbol has a rectangular shape.
If the LAC is ”access denied” that means the OS manages the NE and the CT is not allowed to modify NEconfiguration (it can only “read”). In the view the icon with a key symbol has a circular shape.
If the LAC is ”requested” that means the CT has requested permission from the OS and is waiting for areplay.However the OS does continue to provide a certain number of services. These services includes:
– Reception and processing of alarms,– Performance processing on TPs,– Switching back to the OS access state.
The access state of an NE can be modified from two types of views:
4.1.1 Switching from the OS to the Craft Terminal access state
Select the Supervision pull down menu. Then select the Requested option from the Access Statecascading menu as shown in the following figure.
Figure 7. NE management: setting the access state.
From the confirmation dialogue box that opens you can confirm or cancel the ”Craft access” operationusing the Yes or No push buttons. the request is up to the OS which accept or refuse it.If the OS doesn’t answer in a predefined time it is assumed that the NE is in the Craft access stateand can be managed from a Craft Terminal.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
40
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
4.1.2 Switching from the Craft Terminal access state back to the OS access state
Select the Supervision pull down menu. Then select the OS... option from the Access Statecascading menu in Figure 7. 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 ismanaged 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 theNE. When communication is lost with the NE, the OS automatically recovers the communicationand put the state that was set before the loss of communication (therefore the Craft Terminalaccess can be denied or granted).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
41
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
4.2 NE Time management
The NE local time of a selected NE can be visualized and/or re–aligned on the OS time basis.In this view the OS indication identifies the Craft Terminal.The status of the Network Time Protocol can be checked
Select the NE Time... option from the Configuration pull down menu.
Figure 8. Consulting and/or setting the local NE time.
The following dialogue box is opened from which you can get and/or set the local NE time and check theNTP Status.
Figure 9. NE Time dialogue box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
42
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The following fields are available:
– NTP Status section (read only) with the following parameters:
• NTP protocolIt can be enabled (in the NTP Server Configuration option at para 8.5 on page 81) or disabledor empty (greyed).
• NTP Main and NTP SpareIt displays the status of the Main and Spare NTP: reachable or unreachable.
– Time section with the following data:
• NE Time and OS TimeIt displays (read only) the time of the Network Element and of the OS (Craft Terminal).
• Set NE Time With OS TimeIt permits to align the NE time with the time of the Craft Terminal.
Two different operative conditions can be defined:
– NTP protocol enabledIn this case, NTP Main and NTP Spare will be reachable or unreachable. When both are reachablethe NE uses the Main.The Set NE Time With OS Time message is not operative and the user cannot set manually the NETime.
– NTP protocol disabledIn this case, the NTP Main and NTP Spare are empty (greyed); the Set NE Time With OS Timemessage is operative and the user can set manually the NE Time (i.e. change the NE time with theTime of the Craft Terminal).
If you do not want to set the NE local time, click on the Close push button to close the dialogue box.
To re–align the NE time on the OS time basis click in the Set NE Time With OS Time radio button and eitherclick on the Apply push button to validate or on the Close push button to cancel and close the dialoguebox. The OS time comes from the PC date configuration which corresponds to the legal GMT time.
N.B. When the NTP is not present, the OS system re–aligns the time of all supervised NEsperiodically and automatically with a configured periodicity. This periodicity is common for allthe NEs.If you set the NE time, you will force the change, with an immediate effect on the NE. Howeverit will not have any effect on the periodic and automatic mechanism.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
43
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
4.3 Alarm Configuration
The operations described in this chapter, mainly related to alarm setting, are:
– Alarm Severity Assignment Profile management,– Allow/Inhibit alarm notification,– Alarm re–synchronization.
4.3.1 Procedure to modify an ASAP
a ) Select the TP (or the board/port/etc...) whose ASAP is to be changedb ) from the menu click on “Configuration” –> “Alarms Severities...”c ) (see Figure 11. on page 44 ) select one of the “user” profiles (#10001 or #10002) and click on
“Modify”d ) (see Figure 12. on page 46) click on the “Probable Cause Families” associated to the alarme ) select the relevant alarm in the list of “Probable Cause Name”f ) in the “Service affecting/non–affecting” fields select the needed severity (critical/major/minor...)g ) click on “OK”h ) (see Figure 11. ) click on “Close”i ) select the relevant TP and then “Configuration” –> “Set Alarms Severities...”j ) in the box that appears select the just modified ASAP (eventually check it by means of “Detail”)k ) click on “OK”
For further details see paragraphs 4.3.2, 4.3.2.1, 4.3.2.2.
4.3.2 Alarm Severity Assignment Profile Management (ASAP)
Managed entities yield alarms when they malfunction. This section deals with the configuration of ASAPs.An ASAP is a list of Alarm probable causes to which Severities Profiles are assigned, predefined orsettable by the operator.
Three important notions are:
– The Probable Cause of the alarm,– The Severity of the alarm.– The Alarm Type (communication alarm, equipment alarm).
4.3.2.1 Alarm Severities
This option permits to configure and display the ASAP.
Select the Alarm Severities... option from the Configuration pull down menu.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
44
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 10. Configuring Alarm Severity Assignment Profile.
The ASAP Management dialogue box is displayed.
Figure 11. ASAPs Management dialogue box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
45
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The default presented profiles are:
• Profile ”All Alarms”. With this profile all the alarms are enabled (only Sfwr Download Failureis not alarmed).This ASAP enables the emission of all alarms.
• Profile “No Remote Alarms”shows the alarm criterion configuration defined for ”path alarms”(only AIS and RDI and 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)
• Profile “No Alarms” : (i.e. all alarms disabled).This ASAP inhibits the emission of any potential alarm.
• Profile “10001” can be set by the user.Each single alarm can be classified with a criterion selected by the operator.A default standard configuration is set (Battery Degraded, Battery Failure, CommunicationSubsystem Failure, Path Trace Mismatch are not alarmed).NOTE: if this profile is not already present in the list, it is necessary to create it, by using thedialog of Figure 11. , selecting one existing profile and then clicking on the Clone button.
You can select an ASAP.
For ASAP “10001” it is then possible to choose Detail, Modify, Clone or Delete buttons.For ASAP “No Alarms” , ”Primary alarms”, “No Remote Alarms” and ”All Alarms” it is only possible tochoose Detail, or Clone buttons.Clone selection can be used to create new ASAP.
Click on Detail, Modify, or Clone button, the ASAP edition dialogue box is displayed.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
46
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 12. ASAP Edition dialogue box.
The alarm severity assignment profile dialogue box displays a list of probable causes and a list of alarmseverity.The Probable Cause Families check buttons allows to filter the probable causes that will appear in theProbable Cause Name list. NOTE: it is necessary to choose one or more of these filters to have the list.To find a particular probable cause, enter its name in the Search entry box at the bottom.
ASAPs are already defined in the system with default values for the assigned severities.You can modify the severity associated with each probable cause. To do this, select the probable causewhose severity level you wish to modify.Then click on the option button: Service Affecting (not protected probable cause), and then Non ServiceAffecting (protected probable cause) and then Service Independent (don’t used, it is not operative). Foreach the severity can be chosen from ”Critical”, ”Major”, ”Minor”, ”Warning”, ”Non–alarmed” or “Not used”.A ”Non–alarmed” probable cause corresponds to no alarm emitted for this probable cause.When selecting Details the assigned severity are only shown and it isn’t possible to modify.When you have finished configuring ASAP, press the OK button to confirm the settings and close thedialogue box or the Cancel push button to cancel the new settings and close the dialogue box.
When Clone an ASAP the created one is identified with next number (10002, ....).The max number of ASAP is six.
N.B. The number of severities and the number of probable causes is fixed. The ASAP function onlyenables the modification of the severities assigned to the probable causes, it does not allow theaddition, removal or modification of these severities and causes.
N.B. To take into account a profile modification, it is mandatory to perform a re–synchronization ofthe alarms (see para. 4.3.5 on page. 51). During this re–synchronization, the severity of eachalarm is updated. Otherwise, the severities are updated only when the modified or new alarmsare emitted by the NE.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
47
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
4.3.2.2 Set Alarm Severities
To assign an alarm severity to a TP or equipment, select the TP or equipment in the related view and thenselect the Set Alarm Severities... option from the Configuration pull down menu.
The Set ASAP dialog opens.
Figure 13. Set ASAP dialogue box.
The List of ASAPs on the left side lists all available ASAPs (Alarm Severity Assignment Profiles).
If an object was selected in a view before opening this dialog, its ASAP is highlighted in the list. Using theDetail button or double–clicking on a list item opens the ASAP Edition dialog which displays detailedinformation on this ASAP.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
48
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Within the “Apply to” section on the right side, the user specifies the objects (TP or equipment) the ASAPselected in the List of ASAPs (new ASAP) should be applied to:
Choose Scope
– Selected object onlyThe new ASAP is only applied to the object currently selected in the view.This is the default if an object is selected in the view.
– Network elementThe 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 “ExecutionMonitoring”.This is the default if no object is selected in the view.
– Selected object and subordinatesThe new ASAP is applied to the selected object and those of its subordinates matching the criteriaspecified in “Choose Classes” and “Choose current ASAP”.Since this application process takes some time, its progress is shown in the Section “ExecutionMonitoring”.
N.B. Due to system architecture, AU–4 CTPs are no subordinates of MSTTPs. Therefore, if theAU–4 CTP should be included as subordinate, select the related OSTTP (OpS) or ESTTP(ElS) as main object.
Choose Class(es)
Enabled if one of the scopes “Network element” or “Selected object and subordinates” is selected.
– All classes
– Specific class(es)Select one or more object classes the new ASAP shall be applied to.
Choose current ASAP
The new ASAP is only applied to objects which are currently assigned to this ASAP.
Execution Monitoring
Continuously shows the number of modified objects during the ASAP application process if one of thescopes “Network element“ or “Selected object and subordinates“ is chosen.
Press Ok to confirm the ASAP assignment and close the dialog. Press Close to close the dialog anddiscard any changes.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
49
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
4.3.3 Set SdhNE Alarms Severities
Selecting the Set SdhNE Alarms Severities option from the Configuration pull down menu only thealarms at Equipment level (FF, BKF, SHD and ABF) are managed.
Figure 14. Set SdhNE Alarms Severities
If an object was selected in a view before opening this dialog, its ASAP is highlighted in the list. Using theDetail button or double–clicking on a list item opens the ASAP Edition dialog which displays detailedinformation on this ASAP.
Press Ok to confirm the ASAP assignment and close the dialog. Press Close to close the dialog anddiscard any changes.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
50
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
4.3.4 Allow/Inhibit Alarms Notifications
The system provides the possibility to allow/inhibit the spontaneous incoming alarm notifications.
l ) To inhibit alarm notification,Select the Supervision pull down menu. You can then select the Inhibit Notifs option from the Alarmspull down menu as shown in the following figure.
Figure 15. Inhibit alarm notification
From the confirmation dialogue box that opens you can confirm or cancel the operation using the Okor Cancel push buttons respectively.To inform the operator that alarms have been inhibited, the labels of the alarm panel are greyed out.
N.B. Inhibiting the alarms notification means that they are not forwarded to the CT but alarmsare still generated by the NE.
m ) To allow alarm notificationSelect the Supervision pull down menu. You can then select the Allow Notifs option from the Alarmspull down menu as shown in the following figure.
Figure 16. Allow alarm notifications
From the confirmation dialogue box that opens you can confirm or cancel the operation using the Okor Cancel push buttons respectively.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
51
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
4.3.5 Alarms re–synchronization
The system provides the possibility to recover alarms present on the NE and to update the current problemlist of the NE. After this operation CT and NE current alarms are consistent.
To re–synchronize the alarms, select the Supervision pull down menu. You can then select theResynchronize option from the Alarms pull down menu as shown in the following figure.
Figure 17. Alarm re–synchronization
From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok orCancel push buttons respectively.
N.B. This functionality has to be used only if there is any perturbation. Never use this operation duringa correct behavior.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
52
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
4.4 Restart NE
The restart operation is a software reset and can be executed in normal traffic conditions.
The restart operation in any case activates the Commit (active) version.
Select the Restart NE option from the Supervision cascading menu.
The following dialogue box is opened.
Figure 18. Restart NE confirmation
Click on the OK push button to perform the restart NE.
Click on the Cancel push button to abort the restart NE.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
53
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
5 SECURITY MANAGEMENT
In this chapter are inserted setting options referred to the SECurity management:
5.1 Set Manager list
This option is referred to the SECurity management and allows the user to set the Manager list and theAccess Control Domain of the NE.
Select the Set Manager list option from the Supervision pull down menu.
The dialog–box contains the following fields:
– Manager list: each connected manager to the NE is highlighted in the list. The user can set amanager 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 EML–USM administrator (SH or Craft Terminal) should set the Manager List only to remove amanager in case of emergency (i.e. the Manager misses the NE connection).
– NE Domain field allow to select the domain among that displayed in the list, assigning it to the NE.The different domains could be assigned to different operators.
OK button is used to validate the selection.
Cancel button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
Figure 19. Set Manager list
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
54
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
5.2 Set ACD level
This option allows the user to select the level of the Access Control Domain.
The ACD manage the concurrence of access among several different managers (i,e. RM and EML).This only acts on the functions that can be used by different manager.
Select the Set ACD level option from the Configuration pull down menu.
The dialog–box contains the following fields:
– Current ACD levelShow the Access Control Domain level currently set.
– The Access Control Domain check levelPermit to set one of two level checks. By the way, this is an operation that should be performed onlyduring the EML–USM installation phase:• NE level, the ACD is performed on all the NEs• No Check, the ACD is not managedThe default value is NE level. If it is changed, it is necessary to restart the EML–USM.
OK button is used to validate the selection.
Close button close the dialog without changes of the data.
Figure 20. Set ACD level
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
55
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
6 EXTERNAL INPUT AND OUTPUT POINTS MANAGEMENT
This chapter describes how to display and set the input/output environmental alarm (housekeeping alarm),
An external input point is an environmental alarm (also called housekeeping alarm). It corresponds to anexternal event which is monitored by the NE. Number of relays on the NE are dedicated to checkmodification 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 externaloutput point is independent from external input point.
The operations that can be undertaken in this section are:
– Displaying external points,
– Expanding or reducing external points list,
– Configuring input and output external points.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
56
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
6.1 Displaying external points
Select the External Points option from the Views pull down menu as shown in the following figure.
Figure 21. Opening the external points view.
After selecting this menu option the external points view is displayed into the current window instead ofthe current view.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
57
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 22. External points view.
The external points view displays a list of all input and output points.
The following information is given for each external point:
– the external point Type: Input or Output.– the User Label: a user–friendly label associated to the configurable external point (see further the
paragraph External points configuration).– the External State: represents the alarm state. ”On” when the alarm is raised, else ”Off”. If the external
point is active (On), a little red flag is represented near the status of the concerned point.
Only for the “Output” external point there is the following information:
– the Output criteria: if configurated, display the alarm event and the board affected associated to theOutput point (see further the paragraph External points configuration).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
58
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
6.1.1 Expanding or reducing external points list.
The external points view displays a complete list of the external points but it can also be restricted to theinput or to the output points.
To see either the input points, the output points or all the external points, select the appropriate option fromthe External Points pull down menu as shown in the following figure.
Figure 23. Expanding or reducing the external points list.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
59
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
6.2 External points configuration
The configuration operations available on external points are:
• “user labels” configuration• “external state”. Can be set for output points (ON or OFF)• “Output criteria” associated to the External output point
To configure an external point, click on the concerned row of Figure 22. on page 57 and then select theConfiguration option from the External Points pull down menu as shown in the following figure.
Figure 24. Configuring external points.
The following dialogue box is then opened, displaying information about the selected external point (Inputor Output).
Figure 25. External input point configuration dialogue box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
60
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 26. External output point configuration dialogue box (MANUAL).
Figure 27. External output point configuration dialogue box (FLEXIBLE)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
61
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Opening the dialog the current state of the selected External Point is shown.
[1] External Input Point Configuration
• User Label: this field can be filled by the user with a Label that indicate the associated eventthat must be taken under check (for example presences of water or fire in the room where theEquipment is placed)
• External State: this field is set to off and can’t be changed by the operator
• Probable Cause: this field is set to housekeeping and can’t be changed by the operator
[2] External Output Point Configuration
• User Label: this field can be filled by the user with a Label that indicate the alarm detected orthe action that must be executed if a specific event occur (for example a “Pump” activation whenwater 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 beenselected in the “Output Criteria” field.
• Output Criteria can be configured as :
– Manual (forced). The output contact is set in a fixed way , not depending on a particularevent.For example the output contact could be used to “Manually” activate a pump to drain waterfrom the room where the equipment is placed ; in this case is also necessary to set theoption “On” in the field “External State”.
– Flexible. It is possible to define from CT the couple event/CPO#, where the event ischosen between a set of Output Criteria (LOS, RDI and LOF) and specifies the STM–Ninterface which the Output Criteria refers to by clicking on Choose button; subsequentlythe TP search dialog box will be opened.
When the configuration of the external point is completed, click on the OK push button to validate thechoice and close the dialogue box. The Cancel push button cancels the configuration and closes thedialogue box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
62
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
63
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
7 DIAGNOSIS MANAGEMENT
Alarms are always present on the operator’s workspace. The different types of alarms, their number and theirseverity level, are represented in all Equipment views (NE views, Board views and Port views). An iconrepresentation is used, which change color when the relevant alarm is active. Thus, at all times, you know thenumber of alarms and their severity relating to the equipment.Access to the Alarm Surveillance to show the alarm condition is detailed in the following paragraph.Than is presented the abnormal condition list (as result of operator’s command such us loop, laser forcedon etc.).At the end the Event log access is introduced.Information about the significance of equipment alarms and status is given in the Maintenancesection of this handbook.
7.1 Alarms surveillance
In this chapter is described the access to the Alarm Surveillance information of the NE.
It is possible to show all the Alarms or filter the alarms report.
Select the Diagnosis pull down menu. You can then select the following option from the Alarms pull downmenu (see the following figure):
– NE Alarms: all the NE alarms are listed in the Alarm Surveillance report which isactivated
– Object Alarms: only the alarms of the selected object are listed in the Alarm Surveillancereport
– Subtrees Alarm: only the alarms of the selected object and of the relevant subtrees arelisted in the Alarm Surveillance report
– Equipment Alarms: only the alarms of the equipment management are listed in the AlarmSurveillance report
– Transmission Alarms: only the alarms of the transmission management are listed in the AlarmSurveillance report
– External Points Alarms: only the alarms of the input external point management are listed in theAlarm Surveillance report
Figure 28. Alarm Surveillance
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
64
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Selecting any of the previously seen options, the Alarm surveillance report is displayed as for the exampleof the following figure.
This view shows first a synthesis of the NE alarms (Counter Summary) with the sum of all alarms, thena detailed list of alarms of the selected filter (Alarms Sublist).
Figure 29. Alarm Surveillance
Detailed information for each alarm is supplied.
For example the board in which the alarm is detected, the status of the alarm, the alarm type, the probablecause.
The information supplied help the operator, typically during troubleshooting operation, presented in nextsection of this handbook. (Maintenance section, where more details about alarms are given).
Detailed description is given in the AS Operator’s Handbook.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
65
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
7.2 Abnormal Condition List
The abnormal condition provides the synthesis of NE “not normal conditions” listinig the events thatcontribute to abnormal condition. Select Diagnosis–>Abnormal Condition List ( see Figure 30. on page65). Figure 31. on page 65 is opened.
Figure 30. Abnormal condition menu option
Figure 31. Example of abnormal condition list
The abnormal condition are the following:
• Loopback
• ALS is disable and the laser is forced on or off
• Protection units (in case of EPS, SNCP and MSP ) are in lockout or in forced status
• Board (or sub–board) is placed in a not configured slot
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
66
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Select an abnormal condition and click on “OK” to open the relative dialog window. Figure 32. on page66 is opened.
Figure 32. Example of loopback dialog window management
The other abnormal condition types will open the corrisponding management window or will open thewindow to navigate towards the management window.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
67
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
7.3 Internal Link Monitor
This function improves, at the user interface level, the diagnostic associated to the hardware failure.The presence of a failure on RX or TX side for the signal incoming/outgoing from/to the active MATRIXis detected; Internal Link Monitor displays a detailed localization of the link failure: a graphicalrepresentation of all NGI link status, for the active and stand–by MATRIX is shown.
Select the Internal Link Monitor option of the Diagnosis menu.
As shown in Figure 33. on page 67 the first page displays the link status for the main MATRIX, the secondone concern the spare MATRIX.
In detail, each page contains the following functional blocks and graphical objects:
• the tab of the page displays the user label of the MATRIX board;• the left side of the page displays the block representing the MATRIX board;• the right side of the page displays the list of blocks representing the equipped boards; each
block displays a string contained the user label of the associated board;• two arrows are displayed between the MATRIX block and each board block; the two arrows
represent the link status in Rx and Tx side:– a red arrow indicates a ”link failure”– a green arrow indicates a ”working link”
• the Refresh button allows 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 arerepresented 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 theactive MATRIX;
• the MATRIX is represented by a red block if a link problem is detected in one of the NGI Tx fromone of the possible ”port” board.
Figure 33. Internal Link Monitor
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
68
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
7.4 Log Browsing
From the Network Element context views, perform the following operations to have access to the EventLog file:
– In the Diagnosis pull–down menu, select the Log Browsing option. The following options areproposed:
Figure 34. Log Browsing option in Network Element context view
The proposed option:
• Select the Alarm Log option (Log Id # 1 ) to access the Event Log file.
The Configuration and Log Browsing ELM Windows open, permitting to analyze all alarmsstored in the NE.Refer to the “ELM Operator’s Handbook”
• Select the Event Log option (Log Id # 2 ) to access the Event Log file.
The Configuration and Log Browsing ELM Windows open, permitting to analyze all eventsstored in the NE.Refer to the “ELM Operator’s Handbook”
• Software Trace Log option is reserved to Alcatel personnel only.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
69
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
7.5 Remote Inventory
This paragraph describes the access to the remote inventory of this NE.In the Remote Inventory are stored information of identification, construction data 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 Terminalby 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 107.
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.
Figure 35. Remote Inventory confirmation request
Clicking on OK after a while an information dialog box is presented.
Figure 36. Remote Inventory completed
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
70
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
7.5.2 View Remote Inventory
This command displays the remote inventory previously stored in the Craft Terminal by means the Uploadremote inventory.Select the View Remote Inventory option of the Diagnosis pull down menu.The Remote inventory data appears as for the following figure.
Figure 37. View Remote Inventory
Data is displayed in specific fields:
• CompanyIt indicates the Company’s (Alcatel’s branch) which designs the unit.Refer to Alcatel for the abbreviation’s meaning (four characters).
• Unit TypeIt indicates the units’ acronym
• Unit Part NumberIt indicates Alcatel or Factory product’s Part No.. The number indicated is that printed on thelabels or on the units’ front coverplate.
• Software Part NumberIt indicates the id. of the unit’s resident software
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
71
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
• CLEI CodeIt indicates the CLEI code according to Bellecore specs. TR–ISD–325
• Manufacturing plantIt indicates the Company’s manufacturing plant id. within the company, producing the unit.Refer to Alcatel for the abbreviation’s meaning (four characters).
• Serial NumberIt indicates the product’s serial number as specified by the NR 130 Norm.
• Date identifierIt indicates the meaning of the date that follow.It is a two–digit code supplying the following information:
00 date of construction at the time of final testing01 production order data02 construction date of the unit lot03 date product has been forwarded to customer04 customer order date
• Date (YYMMDD)The identification of the date depends on the indications stated in the previous field. When onlythe year is displayed, the format must be ”YY– – – – ”
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
72
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
73
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8 COMMUNICATION AND ROUTING MANAGEMENT
8.1 Overview on Communication and Routing Domain
The purpose of the communication and routing domain is to define configuration parameters concerningthe communication protocols for the local NE, the OS and each other related NE in order to provide aglobal communication capabilities inside the network.
8.1.1 OSI Protocol on QB3/Qecc
A brief description of basic concepts and terms involved in the communication and routing domain follows.
During the TMN design process, a network is partitioned into domains; each domain can consist of acollection of two types of nodes:
• nodes supporting a link state routing protocol IS–IS; these nodes will be called adaptiverouters; IS–IS protocol floods the network with link state information in order to build a completeconsistent picture of the network topology. Use of IS–IS routing protocol in a TMN facilitatesinstallation and operation due to the ”self learning” capabilities of these protocols and automaticnetwork reconfiguration in case of failure; moreover the use of these standardized routingprotocols 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 otherscan be made End Systems
For the description of the following paragraphs use is made of Figure 38. on page 74. It is not a networkplanning example, it is only used to describe L1 ,L2, RAP and MESA.
8.1.1.1 Partitioning into Routing Subdomains
In order to reduce the overhead associated with distributed adaptive routing, it may be useful to dividea adaptive routing domain into smaller routing subdomains, called areas or level 1 subdomain. A level1 subdomain should fulfill the following requirements:
• a level 1 subdomain should form a connected subnetwork; this subnetwork should have onlya 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 ISin the same area; obviously, there must be at least one level 2 intermediate system per level1 subdomain;
• Level 2 intermediate systems must form a connected network, because level 1 paths cannotbe 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 ifthe 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 followedby two neighboring level 1 intermediate systems within a subdomain: there must be at least one areaaddress in common between their two synonymous list, otherwise they are not able to communicate witheach other.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
74
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.1.2 Partitioning into separate Routing Domains
In certain situations it may be necessary to partition a given network into separate routing domains, whereno routing information is exchanged between these domains. The major benefits of this partitioning arereduction of memory, processing and traffic overhead, because there is no exchange of routinginformation between the domains. Communication between separate routing domains must be achievedthrough the use of Reachable Address Prefixes (RAP).A Reachable Address Prefixes represents static routing information. It can only be associated with a linkof a level 2 intermediate system, whereby this link crosses routing domain boundaries. A ReachableAddress Prefixes is handled in the same way as information about a foreign level 1 subdomain within theown domain. The Reachable Address Prefixes indicates that any packet whose destination networkaddress NSAP matches the prefix may be forwarded via the link with witch the prefix is associated.
For example, consider network which is split into two separate routing domains:• routing domain A resides in a level 1 subdomain with area address ”a”• routing domain B resides in a level 1 subdomain with area address ”b”
In order to enable the communication, the Reachable Address Prefixes in routing domain A must containthe area address ”b” and the Reachable Address Prefixes in routing domain B must contain the areaaddress ”a”.On the other hand, within a given level 1 subdomain, there can be some NEs not supporting IS–IS norES–IS protocol (static routing). In such condition, the communication can be achieved through the useof Manual End System Adjacencies (MESA).A prerequisite for the use of manual end system adjacencies is that the area addresses of the connectednodes must be the same; as a consequence the nodes must belong to the same level 1 subdomain.Within a pure Alcatel network there is no need to use any kind of static routing. Therefore normally RAPand MESA shall never be used.
ÉÉÉÉ
AREA (subdomain) 1
AREA (subdomain) 3
AREA (subdomain) 2
= NE
L1
ÉÉÉÉ
= NE not supporting IS–IS
L1
L1
L1
L1
L1
L1
L1L2
L1
L1
L1
L1
L2L2
L2
ÉÉÉÉ
with MESA
with RAP
with MESA
L1
L1
L1
L1
L1
L1 L1 L1
L2 L2
Figure 38. Routing subdomain organization example
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
75
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.1.3 IP over OSI tunneling for ATM/IP
This feature is applicable to NEs with ATM/IP board.It permits to manage”ATM/IP” traffic encapsulating SNMP messages of the TCP/IP protocols over the OSIstack using CLNP/LAPD/ECC protocols.
8.1.4 OSI over IP tunneling on QB3
This feature allows the Element Manager to reach the GNEs (and all the relevant NEs behind them) byusing IP networking.
This would permit to use an external DCN based on IP only. Hence, no OSI networking would be requiredon the external DCN.
OSI over IP technique is used to meet the target. OSI packets leaving the SH are encapsulated into IPpackets within the SH system itself. Hence, packets leaving the SH are IP packets, containing the originalOSI 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 flowinside 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 theQB3/QECC communication protocol suite; the choice is software switchable at NE level. Theimplementation 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 fullISO/OSI communication protocols, in the complete DCN network or at least in a consistent portion of it.
Figure 39. depicts the protocol architecture.
Figure 39. OSI over IP tunneling on QB3
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
76
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.2 Communication and routing views
To access select Comm/Routing option from the Configuration pull down menu as shown in thefollowing figure.
The Communication and Routing Views allows to perform the following operations:
• Local Configuration: definition of the local NE addresses
• OS Configuration: addressing of the main and spare OSs connected to the local NE
• NTP Server Configuration:addressing of the main and spare NTP servers connected to the local NE
• Interfaces Configuration subdivided in:
– LAPD Configuration: definition of the LAPD port parameters for each LAPD channelon the local NE
– Ethernet Configuration: definition of configuration parameters needed to manage a local NE which provides a LAN ethernet interface
• OSI Routing Configuration subdivided in:
– RAP Configuration: configuration of parameters necessary to the addressing of NEconnected by Reachable Address Prefixes in a domain differentfrom the one of the local NE. These information are stored in RAP table.
– MESA Configuration: configuration of parameters necessary to the addressing of nonIS–IS NE in the same domain as the one of local NE.These information are stored in MESA table.
• IP Configuration subdivided in:
– IP Static Routing Configuration: definition of Host/Network destination address for IPstatic routing
– OSPF area Configuration: definition of Open Shortest Path First address
– IP Address Config. of Point–to–Point interfaces: definition of the Equipment Controller IPaddress
– ISA board IP address: definition of the ISA board IP address
• Tunneling Configuration subdivided in:
– OSI over IP: definition of destination IP address for OSI over IP tunneling.
– IP over OSI: definition of destination NSAP address and type of IP routing forIP over OSI tunneling
All the previously cited operation can be entered choosing the relevant option of the menu, as shown inthe Figure 40.
The options are described in next paragraphs.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
77
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 40. Comm/Routing options
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
78
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.3 Local Configuration
Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascadingmenu the Local Configuration option.
The dialog–box opens (Figure 41. ) and allows to configure the local address of the NE.
The following fields are present:
– a Local Address section contains the following graphical object:
• a Presentation Selector (P.Sel) identifies a presentation entity at the location identified by theNSAP Address. The presented value must not be modified.
• a Section Selector (S. Selector) identifies a section entity at the location identified by the NSAPAddress. The presented value must not be modified.
• a Transport Selector (T. Sel) identifies a transport entity at the location identified by the NSAPAddress. The presented value must not be modified.
• a Network Service Access Point (NSAP) Address identifies a location in the network. The firstfield 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, thelength of NSAP address is variable from 16 characters to 40 characters:– the value of AFI 49 identifies the local format of variable length (from 16 characters to 40
characters).– the value of AFI 39 identifies the ISO–DCC format of 40 characters long.– the value of AFI 47 identifies the GOSIP–V2 format of 40 characters long.
In all cases the last two fields of the NSAP address are:– System Id: uniquely identifies a NE in an area and is 12 characters long
It might be the equipment MAC Ethernet address, level 2, inserted in the NE (check thevalue in the para. 8.7 on page 85 ) or it might be selected by the operator.
– Network Selector: provides the distinction among users of the network service and is 2characters long (value is “1d”).
In the view, the NSAP is managed as simple strings of characters without any pre–formattingbecause of the variable format:– a first string of two characters that identifies the AFI field– a second string of variable length that identifies the remaining NSAP address
– Synonymous Area Addresses section allows to have multiple synonymous area addresses within alevel 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 synonymousaddresses must be the same.
– System Type section determines whether the local NE acts as a “intermediate system level 1” or asa “intermediate system level 2” or as a “End System”. Note that a level 2 intermediate systemperforms functions of a level 1 too. End System is not operative.
Ok button is used to perform a configuration change of the data contained in the dialog–box and closesit; 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
79
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 41. Local Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
80
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.4 OS Configuration
Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascadingmenu the OS Configuration option.
The dialog–box opens (Figure 42. ) and allows to configure the addresses of the Main and Spare OSsconnected to the local NE.
The following fields are present:
– Main OS Address section contains the same graphical object of the Local Address Section in theLocal Configuration dialog–box.
– Spare OS Address section contains the same graphical object of the Local Address Section in theLocal Configuration dialog–box.
Ok button is used to perform a configuration change of the data contained in the dialog–box and closesit; the dialog is visible until the end of the operations and a wait cursor is displayed.Cancel button close the dialog without changes of the data.Help button provides some useful information about the dialog.
Figure 42. OS Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
81
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.5 NTP Server Configuration
Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascadingmenu the NTP Server Configuration option.
The dialog–box opens (Figure 43. ) 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 inthe 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 Sectionin the Local Configuration dialog–box.
– Spare NTP Server Address section contains the same graphical object of the Local Address Sectionin the Local Configuration dialog–box.
If the NTP server is coincident with the OS (same hardware), the same NSAP address of the OS must beassigned.
Ok button is used to perform a configuration change of the data contained in the dialog–box and closesit; the dialog is visible until the end of the operations and a wait cursor is displayed.Cancel button close the dialog without changes of the data.Help button provides some useful information about the dialog.
Figure 43. NTP Server Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
82
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.6 LAPD Configuration
Select the Configuration pull down menu. Select the Comm/Routing–>Interfaces Configurationoption and then from the cascading menu the LAPD Configuration option.
The ”LAPD Configuration” dialog opens (see Figure 44. on page 83, this example has one LAPD Interfaceconfigured).It contains the following functional block and graphical objects:
– a section named LAPD Interfaces List that allows the user:
• to display the list of configured LAPD Interfaces using a graphical table;• to change the role of the LAPD Interface selected in the LAPD Interface List;• to delete the LAPD Interface selected in the LAPD Interface List;• to create a new LAPD Interface.
This section contains the following graphical objects:
• the number of LAPD interface displayed in the LAPD Interface List;• the LAPD Interface List that lists all the configured LAPD Interfaces; for each LAPD Interfaces,
the table displays:– the user label of the TTP containing the configured LAPD Interface (MS/RS TTP);– the LAPD role that contains one of the following value:
• User• Network
• Delete button that allows to delete the LAPD Interface selected in the LAPD table;• Change Role button that allows to change the role (User or Network) of the LAPD Interface
selected in the table (after selection the Figure 46. on page 84 is shown to confirm actionrequired);
• Create button that allows to create a new LAPD Interface; this button starts a new dialog (seeFigure 45. on page 84) named Create LAPD Interface; it is disabled when the maximumnumber of LAPD Interface has been configured.This Create LAPD Interface dialog contains the following functional blocks and graphicalobjects:
– a Choose button that allows the operator to select the superior TTP of the LAPD Interfaceto be created; this button starts the TP Search dialog; the TP Search dialog will beconfigured in order to display in the right tree only the allowed TTP of the LAPD Interface;
– a section LAPD Role that allows to configure the role (User or Network) of the LAPDInterface to be created.This connection is a must to establish connection between two NE’s: if one is configuredwith User role, the other one connected must be configured with Network role.
– a section named Search Criteria that allows the user to display only the LAPD’s of the selected typein the LAPD Table; the section contains the following graphical objects:
• the field Interface Type that allows to select the type of the LAPD’s to be displayed in the LAPDTable; the field will manage both ADM and WDM DCC type; the value ”Ignore” will allow todisplay all the LAPD types;
• the Search button starts the search of the selected LAPD type; this buttons can be used torefresh the LAPD table too.
The LAPD Interface List will be updated on reception of the Delete/Create/Change DCC CTPnotification. 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).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
83
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 44. LAPD Configuration dialog
Close button close the dialog without changes of the data.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
84
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 45. Creation LAPD Interface
Figure 46. Confirmation to change LAPD Role
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
85
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.7 Ethernet Configuration
Select the Configuration pull down menu. Select the Comm/Routing –> Interfaces Configurationoption and then from the cascading menu the Ethernet Configuration option.
The dialog–box opens (Figure 47. ) and allows to define the parameters needed to manage a NE whichprovide 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 theData Communication Network.
– MAC Address section allows to display the address of the Network Element in the Ethernet LAN;it is a read–only field.
– OSI Section:
• L2 only Parameter field indicates if the port shall be used for level 2 traffic only, thus avoidingtransmitting 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 48. on page 86.
• L1 Default Metric is a not modifiable field , Priority field can be set ( default value for ethernetis 64)
• L2 Default Metric is a not modifiable field , Priority field can be set ( default value for ethernetis 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 OSPFArea” must be set.
Apply button performs a configuration change of the data.
Close button close the dialog without changes of the data.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
86
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 47. Ethernet Configuration
L2 L2
NENo
AREA 1
AREA 2
AREA 3
LAN
NENo
L2
NEYes
OS
Figure 48. Ethernet Configuration – L2 only parameter
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
87
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.8 Reachable Address Prefixes Configuration
Select the Configuration pull down menu. Select the Comm/Routing –> OSI Routing Configurationoption and then from the cascading menu the RAP Configuration option.The dialog–box opens (Figure 49. ) 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 separatedomain; the separate domain is selected by the address Prefixes. If the addressed element is the OS, theLAN port will be used.The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointingdevice (upper part of the figure); each page represents a particular element of the RAP table and therespective pointing device displays the element counter.
In detail, each page contains the following data:– Physical Interface button
• if the element is empty, displays the ”none” value and allows to select a LAPD ports or a LANport which will be used to reach the addressed area.
• if the element isn’t empty, displays the selected port and allows to change it.– Area Address Prefix section allows the user to address the separate domain. The Area Address
Prefix represents a NSAP address without the fields System Id and Network Selector.– MAC Address section allows to address the element of a domain to be reached the Ethernet LAN;
the field is managed as a simple strings of 12 digit.
Apply button is used to perform a configuration change of the data contained in the complete RAP tableand 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.
Figure 49. RAP Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
88
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.9 Manual ES Adjacencies table Configuration
Select the Configuration pull down menu. Select the Comm/Routing –> OSI Routing Configurationoption and then from the cascading menu the MESA Configuration option.The dialog–box opens (Figure 50. ) and allows to configure the Manual ES Adjacencies table.Each element of the MESA table allows to link a LAPD port or a LAN port of the local NE to a End Systemelement; the ES element must be in the same area as the one of the local NE. If the addressed elementis 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 pointingdevice (upper part of the figure); each page represents a particular element of the MESA table and therespective pointing device displays the element counter.
In detail, each page contains the following data:– Physical Interface button
• if the element is empty, displays the ”none” value and allows to select a LAPD ports or a LANport which will be used to reach the End System element.
• if the element isn’t empty, displays the selected port and allows to change it.– System Id section represents the System Id of the ES element.– MAC Address section allows to address the element in the Ethernet LAN; the field is managed as
a simple strings of 12 digit.
Apply button is used to perform a configuration change of the data contained in the complete MESA tableand 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.
Figure 50. MESA Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
89
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.10 IP Static Routing Configuration
Select the Configuration pull down menu. Select the Comm/Routing–>IP Configuration and then fromthe cascading menu, the IP Static Routing Configuration option.The dialog–box opens (Figure 51. ) and allows to configure the parameters for IP Static RoutingConfiguration.
The following fields and data are present:
[1] Destination Host IP Address: allows to define the IP address necessary to reach a specific Host
[2] Destination Network: it is alternative to Destination Host IP Address; allows to define theIP Address and IP Mask to reach a network.
[3] Default Gateway IP Address: allows to define the address of the next hop gateway
[4] CLNP (Connection Less Network Protocol): allows to use a pre–define IP over OSI tunnel towardsa gateway.
[5] IP Point–to–Point Interface Id: allows to use point to point interfaces made available by EC
N.B. Points from [3] to [5] are alternative
Apply button is used to perform a configuration change of the data contained in the complete table andclose 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.
Figure 51. IP Static Routing Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
90
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.11 OSPF Area Table Configuration
Select the Configuration pull down menu. Select the Comm/Routing–>IP Configuration and then fromthe cascading menu, the OSPF Area Table Configuration option.The dialog–box opens (Figure 52. ) and allows to configure the parameters for OSPF (Open Shortest PathFirst) Area Table Configuration.
The following fields and data are present:
– OSPF Area IP Address
– OSPF Area Range Mask
Both fields gives a synthetical information that includes all the addresses (specific to a NE and to aNetwork) in an Area.
Apply button is used to perform a configuration change of the data contained in the complete RAP tableand 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.
Figure 52. OSPF Area Table Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
91
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.12 IP Address Configuration of Point–to–Point Interfaces
Select the Configuration pull down menu. Select the Comm/Routing–>IP Configuration and then fromthe cascading menu, the IP Address Configuration of Point–to–Point Interfaces option.The dialog–box opens (Figure 53. ) and allows to set the Equipment Controller IP Address used tocommunicate with the ISA board.
Ok button is used to perform a configuration change of the data contained in the dialog–box and closesit; 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.
Figure 53. IP Address Configuration of Point–to–Point Interfaces
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
92
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.13 ISA board IP Address
Select the Configuration pull down menu. Select the Comm/Routing–>IP Configuration and then fromthe cascading menu, the ISA Board IP Address option.The dialog–box opens (Figure 54. ) and allows to set the IP Address of the ISA Board that communicatewith the Equipment Controller (EC).
Ok button is used to perform a configuration change of the data contained in the dialog–box and closesit; 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.
Figure 54. ISA Board IP Address
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
93
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.14 OSI over IP
Select the Configuration pull down menu. Select the Comm/Routing–>Tunneling Configuration andthen from the cascading menu, the OSI over IP option.The dialog–box opens (Figure 55. ) and allows to configure the Remote Destination IP Address of theEquipment Controller.
Figure 55. OSI over IP Tunneling configuration
Apply button is used to perform a configuration change of the data contained in the complete table andclose 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
94
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
8.15 IP over OSI
Select the Configuration pull down menu. Select the Comm/Routing–>Tunneling Configuration andthen from the cascading menu, the IP over OSI option.The dialog–box opens (Figure 56. ) and allows to configure the Destination NSAP Address and the IPRouting Type.
The following fields are present:
– Destination NSAP Address:
a Network Service Access Point (NSAP) Address identifies a location in the network. The firstfield 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, thelength of NSAP address is variable from 16 characters to 40 characters:– the value of AFI 49 identifies the local format of variable length (from 16 characters to 40
characters).– the value of AFI 39 identifies the ISO–DCC format of 40 characters long.– the value of AFI 47 identifies the GOSIP–V2 format of 40 characters long.
In all cases the last two fields of the NSAP address are:– System Id: uniquely identifies a NE in an area and is 12 characters long
It might be the equipment MAC Ethernet address, level 2, inserted in the NE (check thevalue in the para. 8.7 on page 85 ) or it might be selected by the operator.
– Network Selector: provides the distinction among users of the network service and is 2characters long (value is “1d”).
In the view, the NSAP is managed as simple strings of characters without any pre–formattingbecause of the variable format:– a first string of two characters that identifies the AFI field– a second string of variable length that identifies the remaining NSAP address
– IP Routing:allows to choose the type of IP routing supported as follows;– OSPF (Open Shortest Path First)– RIP (Routing Information Protocol)– Both– None
If “OSPF” or “Both” options are selected, also the “Associated OSPF Area” must be set.
Apply button is used to perform a configuration change of the data contained in the complete table andclose 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
95
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 56. IP over OSI Tunneling configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
96
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
97
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
9 EQUIPMENT MANAGEMENT
9.1 Introduction and navigation
This section deals mainly with the setting and changing of the boards present on the Equipment andundertaking board protection operations.
Using the menu options, select the Equipment option from the View pull down menu
The first level of the “Equipment Overview” representation will be displayed directly into the current window(see the following figure).The Equipment Overview enables a fast navigation through all levels of the equipment hierarchy.Navigation is done from higher to lower levels.The NE hierarchy is organized in the following way: subrack > board > port > TP
The navigation through different levels of the NE hierarchy is performed by double clicking on the objects:
• the first level shows the subrack level of the Equipment view (see Figure 57. );
• further, by double clicking on a board body, the board level of the Equipment view can bereached (as described in chapter 10 on page 111).
• further, by double clicking on a port body contained in the board, the port level of the Equipmentview can be reached (as described in chapter 11 on page 117). The port view displays the innerTPs.
• it is possible to go back to the upper level of representation by pressing the <ESC> key on thekeyboard;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, Figure 57. ) the Showsupporting equipment option from the Equipment menu, the Rack level view of Figure 58. is presented.
In the Rack level view, two subrack are presented:
– at the top the 1660SM Subrack, named SR60M– at the bottom the Fans Subrack, named SRFAN.
The Fans Subrack presence is managed with the Set option as for the boards of the1660SM Subrack (refer to paragraph 9.2 on page 101 for details)
Further, selecting in the Rack level view the Show supporting equipment option from theEquipment menu, the Equipment level view of Figure 60. is presented.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
98
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 57. Equipment Overview – Subrack level
Figure 58. Equipment Overview – Rack level (without Fans subrack)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
99
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 59. Equipment Overview – Rack level (with Fans subrack)
Figure 60. Equipment Overview – Equipment level
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
100
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
In the Subrack view it is possible use the options offered by the Equipment menu (see following figure)clicking on it in the menu bar.
Alarms indications are present at every NE level.Details about these alarms indications are given in the Maintenance section.
All the options offered by equipment menu are described in the next paragraphs.
Set and change the boards present on the Equipment is the main function.Board administrative state that decide on the “in/out of service” of the board is also described.
Figure 61. Equipment menu.
Equipment setting operation are defined according the following sequences:
– configuration of a new board• Configure the board using the option “Set”
– change of board type• “Set out of service” the board• Configure the board using the option “Set”
– remove a board• “Set out of service” the board• “Remove” the board.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
101
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
9.2 Set and change or remove board/subrack
The boards can be set, changed or removed using the menu options of the Equipment view.
a ) Setting or changing a board/subrack
A new board/subrack may be created in either an empty slot or it may replace an existing Out of Serviceboard/subrack (without the lock symbol). In fact, the Set option is available only after selecting an emptyslot or an Out–of–service board.– Click on the empty slot in which a board/subrack has to be added, or on an existing Out of Service
board in order to change it (see next para. 9.4 on page 105 for “in /out of service” info). The contourbecomes highlighted to show that operations can be done on it.
– Select the the Set option of the Equipment pull down menu of Figure 61. on page 100.
– The following example of dialogue box containing a list of the different types of boards/subrack isdisplayed.
PORT LIST
ACCESS CARD LIST
SUBRACK LIST
Figure 62. The list of different boards/subrack relative to an NE slot (examples)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
102
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
N.B. The list of boards/subrack displayed during a ”Set” operation is restricted to those which theequipment may accept in the selected slot. Therefore the list will vary depending on which slothas been selected.For details on the board/subrack identified by acronyms and NE physical composition pleaserefers to the Technical Handbook.
– Choose the board/subrack type required, by clicking on the corresponding item in the list. The nameof the board is highlighted. Click on the OK push button to validate the choice.
– The board/subrack representation appears on the NE view in the slot when the board change iseffective.A lock representation appears over the boards (”in–service”, see next para. 9.4 on page 105)
– In the Create/Modify dialogue box, the Cancel push button cancels the operation and closes thedialogue box. The Help push button opens a Help view giving information about the context.
b ) Removing a board/subrack
– Click on the board/subrack to remove (Out of Service board/subrack, as for next para. 9.4 on page105).The outline of the slot becomes highlighted. This indicates that the board is selected and thatoperations can be done on the slot.
– If the slot you are working on is already empty no name appears under the slot.
– Select the Remove option the Equipment pull down menu of Figure 61. on page 100.
– From the confirmation dialogue box that opens you can confirm or cancel the ”Remove” operation.
N.B. It is possible to remove a board only if it is not involved in any type of cross connection (OHbytes included) or Performance monitoring.
c ) Modify a board
N.B. This procedure can be done to replace an existing optical module with another of differenttype without previously remove it.
– Click on the optical module to replace. The outline of the slot becomes highlighted to show thatoperation can be done on it.
– Select the Modify option of the Equipment pull down menu of Figure 61. on page 100 .
– A dialog box containing a list of different types of optical module is displayed.
– Chose the optical module type required by clicking on the corresponding item in the list; the nameof the module is highlighted.
– Click on OK push button to validate the choice.
– The board representation appears on the N.E. view in the slot when the board change is effective.A padlock representation appears over the board.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
103
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
9.3 Connect Fan to CONGI board
This command enable the Fan Subrack alarms management from CONGI in slot 10 or slot 12 accordingto the option selected in the Equipment menu.
Figure 63. shows an example
Select the CONGI board
To enable this function select the Connect Fan to CONGI#10 option ( or as alternative Connect Fanto CONGI#12) of the Equipment menu if the supervision Fan Subrack cable is connected to CONGI unitinserted in slot 10.
Figure 63. Connect FAN to CONGI
It is possible to disable this function by selecting the relevant CONGI board and than choosing theRemove Fan connection from CONGI#10 option of the Equipment menu (refer to Figure 64. ).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
104
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 64. Remove FAN connection from CONGI
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
105
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
9.4 Board administrative state
The operator decides to set a board in service or out of service, if it is allowed by the NE.
N.B. In the equipment view, a lock representation appears over the boards which are in ”in service”state.
9.4.1 Setting a board in service
– In the Subrack NE view, click on the board in order to select it.– Select the Set in service option of the Equipment pull down menu of Figure 61. on page 100.
A lock representation appears over the boards.
9.4.2 Setting a board out of service
– In the Subrack NE view, click on the board in order to select it.– Select the Set out of service option of the Equipment pull down menu of Figure 61. on page 100.
Select the Ok push button in the confirmation window which appears.
A lock representation disappears, substituted by the symbol over the boards..
9.4.3 Consulting a Board’s Administrative state
The board’s administrative (”in service” or “out of service”) state is indicated on the board view as shownin the following figure.
Administrative
State Information
Figure 65. Consulting a board’s administrative state.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
106
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
9.5 Software description
This function allows the operator to visualize information about the software(s) which is (are) present in theselected board.
– Click on a board in which the software is wanted to know (EQUICO or MATRIX unit). The outline ofthe slot becomes highlighted. This indicates that the board is selected and that operations can bedone on the slot.
– Select the Software description option of the Equipment pull down menu of Figure 61. on page100.
The following window opens.
Figure 66. Software Description dialogue box.
The dialogue box contains as many folder sheets as there are softwares in the selected board.
Click on the Close push button to close the dialogue box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
107
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
9.6 REMOTE INVENTORY
This command displays the remote inventory data present in the Subrack and Boards.– Select the Remote Inventory option of the Equipment pull down menu.
Two options are available (see the following figure):• Subrack level: prints or write on a file the remote inventory data of the subrack.• Board level: show the remote inventory data of the selected board
For the Board level a dialog similar to Figure 67. appear.
Figure 67. Remote Inventory (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
108
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The remote inventory data of the Subrack level can be printed on the default printer ( Figure 68. ) or to afile in postscript or ASCII format ( Figure 69. ).
Figure 68. Select Printer
N.B. If no printer is installed, there is no error message displayed to indicate this.
Figure 69. Select Output Format for file
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
109
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
9.7 Show supporting equipment
Click on Show Supporting Equipment menu option of the Equipment menu to navigate to theequipment that supports the selected board.
Figure 70. (example) opens.
Figure 70. Equipment Overview – Subrack level
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
110
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
111
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
10 BOARD VIEW
10.1 Introduction
The Board View permits to show the physical port available in a specific board and to access the Portview.
The “Board view” is reached selecting the Equipment option in the View pull down menu, then doubleclicking on the selected board to show the relevant Board view, presenting the ports.
In case of board with multi access SDH another view permits to select the SDH port (see example ofFigure 71. )
An example of “board view” with the presented port is in Figure 72.
Alarms and Status indications referred to the board level are present at the bottom of the view, as indicatedin the example (Administrative State and Board Alarms/Status).
This information are “In/Out of service” of the board (Administrative State) and board alarms and statuslike “missing” (RUM) or “mismatch” (RUTM), EPS condition if supported and other indications typical ofeach unit .
In the Maintenance section details on this indication are given.
Administrative stateBoard Alarms/Status
Figure 71. Equipment view: select the SDH port on a board.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
112
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 72. Example of a Board View
A port type is described with a board rectangular view and a port identification.
The port identification is usually internal to the rectangular board (see Figure 73. one example of opticalport).
Figure 73. Example of a Port identification and alarm synthesis
The following information is available:
– type of port (name)– state of port (alarm status synthesis)– symbol of the port
The operator is provided with a representation of the port alarm synthesis on each port.
The messages displayed at the top view provide port denomination.
The messages displayed at the bottom provide information about Board alarms.
A message under the mouse facility provides the name and the port type or the alarms name. A messageappears 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 11on page 117).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
113
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
10.2 Board View Menu
Selecting the “Board” option in the menu bar of Figure 72. on page 112 the complete pull down Boardmenu is presented (Figure 74. ):
– Port Access: Access the “Port” view. See para.10.2.1 on page 114 .Note: this option is accessible after the selection of a port containedin the view.
– Change Physical Interface: Change the SPI or PPI object into PPI or SPI (and viceversa) on thebi–mode port( 140Mbit/s / STM–1 switchable).See para. 10.2.2 on page 115.
– Show supporting equipment: Navigate to the upper subrack level.See para.10.2.3 on page 116.
– ATM/IP/ETH Configuration: It allows to configure the TPs for the ATM/IP/ETH connections.Note: this is available only if an ATM/IP/ETH board has beenequipped in the Subrack.
Figure 74. Board menu options
These options are described in next paragraphs.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
114
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
10.2.1 Port Access
Click on Port Access menu option of the Board menu to access the “Port View” ( see chapter 11 on page117).
Navigation to the Port view permits to show a detailed alarm presentation of the port and to set the relevantconfigurations as for the example of the following figure.
Figure 75. After “Port Access” selection (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
115
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
10.2.2 Change Physical Interface
This command allows to change the type of physical interface in a bi–mode port (140 Mbit/s / 155 Mbit/sswitchable port) i.e it changes the SPI or PPI object into PPI or SPI.
Select the Symbol of the port in the “Board view”.
Click on Change Physical Interface menu option of the Board menu (see Figure 76. on page 115)
Figure 76. Change Physical Interface
The following dialog box is opened:
Click on the OK push button to change the physical interface.
Click on the Cancel push button to abort the change of the physical interface.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
116
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
10.2.3 Show Supporting equipment
Click on Show Supporting Equipment menu option of the Board menu to navigate to the subrack thatsupports the selected port view.Figure 77. (example) opens.
Figure 77. Subrack level.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
117
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11 PORT VIEW
11.1 Introduction
This section describes the operations necessary for the consultation, modification and configuration ofeach port.
The Port View permits to set and show the transmission resources (i.e. the Termination Point, TP) referredto the specific Port; it permits to check the detailed alarms presented by each TP of the Port, and theavailable menu permits to configure the port, (many setting options listed in the port menu are commonwith the “Transmission” view).In these views are presented only the TP specific of the port.
The menu differs according the port type (SDH, PDH, HOA, ATM/IP/ETH).
The Port View can be accessed from the Equipment or Transmission Views.
The “Port view” is reached selecting the Equipment option in the View pull down menu then doubleclicking on the presented rack/subrack to present the subrack view, as described in chapter 9 on page 97.Double clicking on the selected board the relevant Board view is available presenting the ports (seechapter 10 on page 111).By double clicking on a board view, the corresponding port view is opened (see Figure 78. ).
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 descriptionat para. 14.5 on page 179).
On the transmission view which appears select the TP and on the Transmission menu select theNavigate to a port view option.The HOA port view can only be reached from the Transmission view, selecting a VC or TU TP.The ATM/IP/ETH TPs are not automatically created when the board is inserted in the subrack but mustbe created as explained in Chapter 20 on page 365.
From the Port view It is possible to Navigate to Transmission view.
The port types contain the following TP:
• SDH port: Electrical or Optical SPI TTP, RS TTP, prot TTP (MSP TTP), AU4 CTP, Trail Monitor(only with enabled POM)
• PDH port: PPI TTP, En CTP, VCn TTP
• HOA port: VC4 TTP, TUG3, TUG2, TU3, TU12, Trail Monitoring (only with enabled POM)
• ATM port: VC4C TTP, VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP and E1 TTP
• IP port: VC4 TTP, VC3 TTP and VC12 TTP
• ETHERNET port: MAU, VC4 TTP, VC3 TTP and VC12 TTP
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
118
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 78. Example of a Port View
On the port view, the messages displayed at the top view in the form of message boxes provide moreinformation concerning the type and the alarms of the port.
On the other hand the messages displayed at the bottom provide information about MSP protection andALS state ( if they are supported ).
A message under the mouse facility provides the name and the port type. A message appears in themessage area in the bottom left corner of the view.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
119
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.2 Port View: elements on the TP
The symbols of the TPs (see Figure 79. ) have the following meaning:
– Alarm Icon AreaThe icon boxes represent alarms. The color of the boxes changes according to the alarm severity.
– TP RoleThe icon boxes represent the function: Adaptation, Termination or Compound Adaptation andTermination.
– Cross-connected stateIf the condition of the resource is cross-connected, an icon with a x appears beneath the box.
– Performance stateIf the condition of the resource is under performance monitoring, an icon with a P appears beneaththe box.
– Loop stateIf the condition of the resource is under loop, an icon with a L appears beneath the box.
– Selected stateAn orange frame around the box identifies the TP selection, so port menu refers to the selected TP.
Alarm icon area
TP identifier
Crossconnected stateSelection indication
G.783 TP Role (Termination)
TP under Performance monitoring
Figure 79. Termination TP box.
Figure 80. is another example of TP with different G.783 function role.
Alarm icon area
G.783 Functional block acronym
G.783 TP Role (Adaptation)
Figure 80. G.783 Adaptation TP box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
120
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.3 Port View Menu
Selecting the “Port” option in the menu bar of Figure 75. on page 114 the complete pull down Port menuis presented (Figure 81. )
The menu differs according the port type (SDH, PDH, HOA and ATM), and is introduced in the following:
– TP configuration: Set parameters for the Signal Label and Path Trace overhead onSynchronous TP’s.See para 14.6 on page 186.
– TP Threshold Configuration: Set B2 excessive BER and Signal Degraded parameterSee para. 14.8 on page 193.
– TP Frame Mode Configuration: Set parameters for 2Mbit/s G.703/G.704 or ISDN–PRAmanagement
See para 14.7 on page 191.
– Set Retiming: Enable/disable the retiming feature on the outgoing 2 Mbit/s signal. Seeparagraph 11.4 on page 11.4.
– AU4 Concatenation: Only for SDH ports views. See para 11.5 on page 123
– Cross Connection: Manage the connection of the paths. See para.15 on page 213
– Monitoring Operations: Set parameters for POM/SUT and TC (Tandem Connection) TP’s. Not available for PDH port. See para.14.10 on page 195
– Performance: See and Show Performance Monitoring parameters and data.See Chapter 17 on page 269.
– Loopback: Manage the loopback commands, for commissioning or maintenancepurposes. See para. 14.12 on page 201.
– MSP Manage the Multiplex Section Protection of the NE.See Chapter 13 on page 155.
– Physical Media: Manage the physical setting of the TP of the port. Not applicable to HOAport. It is described in the following paragraph.
– Show supporting board: Navigate to the upper board levelIt is described in this chapter, see para.11.7 on page 136
– Navigate to Transmission view: permit to show a complete overview about the signal flow, openingall TP’s.It is described in this chapter, see para.11.8 on page 137
– Navigate to Monitor view: permit to show an overview about the monitoring operation (POM, SUT,TC) all TP’s. It is described on paragraph 11.9 on page 138.
SDH Port PDH port ATM Port
Figure 81. Examples of port menu options (SDH, PDH and ATM port)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
121
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.4 Set Retiming
The Retiming feature applies to the outgoing 2 Mbit/s and its purpose is to absorb the jitter /wander thatis transferred to the PDH signal when SDH pointer justification occur. The feature is set individually perport
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 brownand the label “Retiming State Disable” is written.
Select the Set Retiming–>Enable option from the Port menu (see Figure 82. )
Figure 82. Set Retiming enable (before)
As result of this operation the state information color become green and the label “Retiming State Enable”is written (see Figure 83. )
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
122
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 83. Set Retiming enable (after)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
123
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.5 AU4 Concatenation
Select a STM–16 or STM–4 optical interface to configure as AU4 concatenation structure.
Zoom in to open the board and then the port view menu.
Select the AU4 Concatenation option from the Port menu to open Figure 84. on page 123 (in thisexample a STM–16 view is shown)
The STM16 stream appears divided into different groups: not all AU4s can be chosen as first AU4 but onlyAU4#1, AU4#5, AU4#9, AU4#13 for AU4c. Therefore for concatenated action of four AU4s in one AU4cthese AU4 streams are deleted and substituted by the new AU4c component.
Select the supported concatenation Number =4 (selection 64 is not operative) to visualize the availablegroup/groups then select the group to concatenate and click on the Concatenate push button.
Click on the Cancel key to exit and come back to the previous window.
Figure 84. AU4 concatenate/deconcatenate commands
The Concatenate button will be enabled and the Deconcatenate button will be disabled when is selecteda non concatenated AU4, viceversa when is selected a concatenated AU4.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
124
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 85. Example of a concatenated AU4 transmission view
The port view represented in Figure 85. shows an STM16 interface with four AU4 concatenated in oneAU4c. The AU4c appears as a single icon that has the same size of the actual AU4 blocks. The AU4cstreams support the Alarm synthesis, Cross–Connection states and Performance Monitoring informationas standard AU4 streams.
To deconcatenate an AU4c select again the “AU4 Concatenation” option in the Port View menu and thenselect the AU4c to deconcatenate (see Figure 86. ). Click on the Deconcatenate push button to applythe command or on Cancel to exit.
Figure 86. Example of a concatenated AU4c
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
125
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.6 Physical Media option menu
The Port –> Physical Media options permit to set physical configuration of each TP of the port.
The Physical Media options are also accessible from the Transmission menu.
It opens a menu which differs according the port type:
• SDH port:
– ALS Management– Show Optical Configuration– Tx Quality Configuration:see para. 18.2.11 on page 312– Single Fiber Configuration– LAPD Configuration: see para.8.6 on page 82.– Ms Configuration
• PDH port:
– Line Length Configuration.– HDSL Configuration. Not operative– NT G703/704 Configuration. Not operative– NT X21 Configuration. Not operative
• ETHERNET port:
– Remote Laser Management. Not operative– ALS Management. Not operative– Ethernet Port Configuration.– ATM/IP/ETH Configuration. Refer to Chapter 20 on page 365.
These options are described in next paragraphs except the previously referenced.
Figure 87. Physical media menu (SDH port example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
126
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.6.1 Automatic Laser Shutdown Configuration
The aim of this paragraph is to describe the optical port hence the laser sources.
Automatic laser shutdown (ALS) is useful in case of a loss of communication between two NEs due tooptical fiber breakdown. For safety reasons it may be necessary to shutdown the laser to enable the fixingof 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 88. ).
Figure 88. Automatic Laser Shutdown Management
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
127
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The dialogue box enables the ALS Management and the Restart parameters. The following actions areavailable:
a ) Allow Automatic Laser Shutdown.
To allow the automatic laser shutdown functionality, select the ALS Enabled option of the ALSFunction: option button.
b ) Forcing the Laser to start or stop.
When the laser is forced to ON or OFF, it is restarted or stopped and the Automatic Laser Shutdownis disabled, if it was not already so.
1 ) Force laser ON.To carry out a laser forced ON, select the Laser Forced ON option of the ALS Function thenclick on Apply and then or Close push button to close the dialogue.
2 ) Force laser OFF.To carry out a laser forced OFF, select the Laser Forced OFF option of the ALS Function thenclick on Apply and then or Close push button to close the dialogue
c ) Delete : this option deactivates the ALS function, returning to the state shown in Figure 89. on page127.From this window it is only possible to create the ALS function (all the ALS commands are greyed).
Figure 89. Automatic Laser Shutdown Management (after ALS Function delete)
d ) Enabling or Disabling Automatic / Manual Laser Restart.
To enable (disable) an automatic laser restart following an automatic laser shutdown (periodicrestart), select the Enabled (Disabled) option of the ALS Auto Restart. The laser will be ON for2 secs and OFF for 70 secs, in periodic mode. The same procedure is applicable for the ALS Manualrestart : while the ALS auto Restart is disabled,the manual restart permits to perform a laser restartfor a single time period.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
128
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
e ) Wait to restart time
The Wait To Restart Time: field indicating the delay period in seconds, occurring before anautomatic laser restart is launched (following an automatic shutdown). The restart time period forthis equipment is fixed to 70 secs.
f ) ALS Manual restart
When the ALS Manual Restart is Enable it is possible to enter two different commands: Manual orTest Restart. The Manual command immediately activates a single laser restart: this commandoverrides the wait to restart time. The Test restart is similar to the manual restart but the laserremains “ON” for a longer time in order to make a measurement of the received optical power.
When all the different parameters have been configured, select the Apply button to confirm the settingand close the dialogue box.Selecting only the Close button allows you to cancel the choices made.
Note that the ALS procedure is activated ( if enable ) only when the fiber has been interrupted and theALS state has not to be confused with the laser state.
ALS states (see example of Figure 90. ), displayed by the functional state message area of the opticalport, are:
ALS states:
Inactive = No ALS has been activated (Off) or the laser has been Forced ON/OFF.
In test = The laser restart has been automatically activated .
Active = The ALS has been activated (On).
Undefined = The ALS is not present (not created).
Laser state:
On = all OK or ALS not present (not created).
Off = Laser off (when ALS is created).
Forced on = ALS forced on by operator command.
Forced off = ALS forced off by operator command.
Figure 90. ALS and Laser current state (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
129
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.6.2 Show Optical Configuration
This command permits to get detailed information on the optical characteristics of the port that isvisualized.
Firstly select an optical board and the SPI block, then click on Show Optical Configuration option fromthe Physical media pull down menu to visualize the parameters of the selected optical port.
Figure 91. shows an example of the parameters of the selected interface.
N.B. This dialogue box can only be read. You cannot write in the entry boxes.
Figure 91. Visualizing a port optical parameters
The laser ports are identified by three major characteristics:
– STM Level: describes the input/output optical interface types: STM1/STM4/STM16
– The wavelength of the laser source: the units are nanometers (nm = 10–9 m).
– The use of the port: describes whether the laser port is used for intraoffice transmissions on longdistances (Long Haul � 40 km) or for infraoffice transmissions on short distances (Short Haul �15 km).
The Colored Interface Parameters section is not applicable in the current releaseTo close the dialogue box click on the Cancel push button.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
130
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.6.3 Single Fiber Configuration
The single fiber configuration can be realized with passive optical couplers (see Figure 92. )The optical coupler must not loop the Tx signal onto the local Rx .For this purpose and in general to avoid a low Tx/Rx decoupling also when the optical line is interrupted,an identification label has been assigned to the local Tx side ; the Rx part in the remote receive side checksthe congruency between the received and the expected labels. If a signal label mismatch is recognizedon the received section, an alarm (AIS and RDI) will be generated. Example of Figure 92. shows that isaccepted the label “1” from Tx1 to Rx2 while is accepted label “2” from Tx2 to Rx1.
Tx1 Tx2
Tx1 Label : 1 Tx2 Label : 2
Rx1 Rx2
OPTICALPASSIVE
COUPLER
OPTICALPASSIVE
COUPLER
Rx1: accepted label=2 Rx2: accepted label=1
Single bidir
Figure 92. Bidirectional Transmission on a single fiber
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
131
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Select the Physical media option and then from the cascading menu the SDH Single FiberConfiguration option .
Figure 93. opens. The following fields have to be considered:
– Allow Single Fiber: select the transmit mode on the single fiber (enable or disable).
– Transmitted Section:
• Transmitted Media Byte – assigned label to Tx (0–14).
• Transmitted Media Type – overhead byte used for the communication:
– Media Dependent byte of Regeneration Sectionor
– S1 byte of Multiplex Section (the part not used for the SSM)
– Received Section:
• Received label
• Expected label (0–14).
Figure 93. Single Fiber Configuration View
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
132
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.6.4 Ms Configuration
The Ms Configuration menu allows the SS bit provisioning for Multiplex Section Object (MSTTP) inSONET/SDH network interworking.
Select the MSP TP.
Click on Ms Configuration menu option of the Port menu. Figure 94. opens.
This dialog allows to select between SDH or SONET networks. After the selection click on Apply and thenon Close to close the dialog.
Ms Forced AIS is not supported in the current release.
Figure 94. Ms Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
133
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.6.5 Line Length Configuration
To manage the Line Length configuration click on Line Length Configuration menu option of thePhysical Media menu. Figure 95. opens.
This dialog allows to configure the line length for a PDH PPI TP of a 45 Mbit/s port.
The OK button validate the configuration and close the dialog box.
The Cancel button removes the dialog
Figure 95. PDH Line Length Configuration View
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
134
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.6.6 Ethernet Port Configuration
To set the Ethernet port parameters, select the Ethernet Port Configuration option of the Port –>Physical Media menu as shown in Figure 96.
Figure 96. Ethernet Port Configuration options
Subsequently Figure 97. on page 135 will be opened.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
135
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 97. Ethernet Port Configuration menu
For the Ethernet port it is possible to choose between two “Configuration Type”:
[1] “Auto Negotiation” : enable allows to configure the “Rate” to be negotiated (10 or 100 Mb/s).The “Directionality” (Full Duplex) and the “Flow Control” (Activated) are always enable and can’tbe changed.It is possible to Restart the “Auto Negotiation” by depressing the relevant button.
[2] “Manual”: allows to force the “Rate “ at 10 or 100 Mb/s .The “Directionality” is always Full Duplex.
In both cases in the Port view is possible to check the the “Auto negotiation Current State”, the “InterfaceType” and the current “Bit Rate” (refer to Figure 96. on page 134).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
136
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.7 Show Supporting Board
Select a TP.
Click on Show Supporting Board menu option of the Port menu to navigate to the board that supportsthe selected port view.
Figure 98. (example) opens.
Figure 98. Board View Example.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
137
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.8 Navigate to Transmission View
Select a TP.
Click on Navigate to Transmission View menu option of the Port menu to navigate to the correspondingTransmission 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 theexample of the following figure..
Figure 99. After “Navigate to Transmission view” selection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
138
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
11.9 Navigate to Monitoring View
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 correspondingMonitoring 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 100. on page 138 is shown an example of Monitoring View of a TP with POM and TCM bothbefore and after matrix.
Figure 100. View of Monitoring Operations (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
139
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
12 EQUIPMENT PROTECTION MANAGEMENT
12.1 Introduction
It is unthinkable to launch a telecommunications system, handling millions of communications, without thepossibility of replacing equipment in a real time way, consequent to equipment failure. Everything mustbe done so that the communications can continue smoothly and so that the equipment failure remainstransparent to the users. Protection management deals with this aspect of the EML–USM.
The protection is performed by switching the board supporting the protected service when this board failsto a protecting board capable of supporting the same service. This protection is realized according to aprotection scheme.
An equipment protection scheme is composed of the following parameters which can be configured:
• Group type: 1+1 or 1+nthe group type specifies if one or more unreliable resources for protection can be assigned toone or more reliables resources. 1+1 group type means that a working element is protected byone protecting unit. 1+n group type means that n working elements are protected by only oneprotecting unit.
• Protection priority:A priority can be assigned to protected units in 1+n protection schemes. This priority can be be1, 2, ... or n, 1 being the highest priority.
• Configuration type: revertive or non revertiveIn revertive mode, a protected service will be switched back to its protected element when it hasrecovered from its failure.In non revertive mode, the switch to the protecting element is maintained even after a recoveryfrom failure.
• Protection wait to restore time:Used when revertive mode is active, the protection wait to restore time prevents severalprotection switches due to an intermittent failure. A protected element must be fault free duringthis fixed period of time before a protected service is switched back to it.
Board duplication remains the easiest way to ensure equipment protection in a system.The actions that can be undertaken are of the following type:
– Consult and modify an Equipment Protection Scheme (EPS),– Force Switch EPS,
In Board view, the board whose contents is represented is considered as implicitly selected.
EPS protection states are displayed by the functional state message area of the boards involved in anequipment protection scheme.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
140
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
12.2 Management: consulting and modifying EPS
In order to consult EPS, perform the following operations:
The “Port view” is reached selecting the Equipment option in the View pull down menu to present thesubrack view, as described at chapter 9.1 on page 97.
– Select the Equipment option in the View pull down menu.– Select the EPS pull down menu. Then select the Management... option as show in the following
figure.
Figure 101. Consulting EPS
The following dialogue box is opened.
r01sr1/board#40
r01sr1/board#23
r01sr1/board#32
r01sr1/board#27
Figure 102. EPS Management dialogue box
The EPS Management dialogue box shows the current NE protection schemes in the left side. Thelist gives for each protecting board the protected board(s).
The available protection schemes are coherent with the NE type and release.
The right side of the dialogue box allows to modify the EPS configuration.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
141
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The current release of this NE fix the following protection:
• N+1 (with N ≤ 6)“P63E1 or P63E1N” protection
– board of slot MAIN (protected): P63E1 or P63E1N, slots 24–27–30–33–36–39
– board of slot SPARE (protecting): P63E1 or P63E1N, slot 32
• N+1 (with N ≤ 15) “P3E3/T3” protection
– board of slot MAIN (protected): P3E3/T3, from slot 25 to 39
– board of slot SPARE (protecting): P3E3/T3, from slot 24 to 38
• N+1 (with N ≤ 15) “P4ES1N” protection
– board of slot MAIN (protected): P4ES1N, from slot 25 to 39
– board of slot SPARE (protecting): P4ES1N, from slot 24 to 38
N.B. For P3E3/T3 and P4ES1N more than one protection group N+1 revertive can be created,depending on the equipment configuration.The spare board position can be assigned in a flexible way .The only constraint are thefollowing:
• the access card corresponding to the protecting board must be an HPROT card• the HPROT card has to be plugged at the left side of the access card group• the main/spare boards have to be adjacent.• the protecting board has to be plugged at the left side of the protected group of boards• the protecting/protected group of ports have to be of the same type
• 1+1 “ATM MATRIX 4x4” protectionThe ATM MATRIX board can be protected in 1+1 equipment protection scheme.In this configuration the ATM MATRIX and all indirect interfaces connected to it are protectedagainst ATM module failure. This does not apply to the local STM–1 interface so the traffic onit is lost.A maximum of two protection group 1+1 not revertive can be created.The spare card position can be assigned in a flexible way; no restriction for position of main andspare ATM MATRIX are present.
• 1+1 “ATM MATRIX 8x8” protectionThe ATM MATRIX board can be protected in 1+1 equipment protection scheme.In this configuration the ATM MATRIX and all indirect interfaces connected to it are protectedagainst ATM module failure.A maximum of two protection group 1+1 not revertive can be created.The spare card position can be assigned in a flexible way; no restriction for position of main andspare ATM MATRIX are present.
• 1+1 “MATRIX” protection
– board of slot 23, MATRIX main (protected)
– board of slot 40, MATRIX spare (protecting)
N.B. for each type of failure on the MATRIX main board ( CRU, Shelf Controller) a switch isperformed to the spare boards.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
142
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The MATRIX protection is automatically presented in the left side of the dialog box whenthe SPARE MATRIX is created in the Set option of the Equipment menu. It is not createdwith the EPS menu described in this chapter.
This right side is divided into two parts.The upper part provides a message field with the name of the Protecting board and a choose button todisplay the list of boards available.The lower part provides a list to display the Protected boards currently in the displayed scheme.A choose button is provided to display the list of boards which could be added as protected.A delete button enables user to remove a protected board from a scheme.
a ) Scheme displaying
To display a specific scheme, user selects an item on the left list.This operation fills the protecting element text field and the protected list with the board user name. If userclicks where there is no item displayed, the right part is displayed empty.The Cancel push button closes the dialog box.
b ) Scheme creation
To create a new protection scheme,don’t click on item in the left list.In this way the right part is displayed empty and the Choose Protecting button is sensitive.Press this button to displays a window to choose a board in the “Board Selection” list (see Figure 103. onpage 143). The board are listed opening the NE>rack>subrack levels.
After that operation, Choose Protecting button becomes insensitive and Choose Protected becomessensitive (see Figure 104. on page 143)The user can add, always using the same “Board Selection” list dialogue box presented, as manyprotected boards as wanted (max.15 in this NE, N+1).
When the right part of window is correctly filled, the OK button close the dialog box and create the scheme(the new list is update re–opening the EPS Management dialogue box).The Cancel push button cancels the creation and closes the dialog box.
c ) Scheme deletion
To delete an existing protection scheme, the user selects a scheme in the left list. Using the Delete button,user could delete the scheme.
d ) Scheme modification
To modify an existing protection scheme by adding or removing protection units, the user selects a schemein 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 protectedelements from scheme. When the right part of window is correctly filled, the OK button close the dialogbox and modify the scheme.The Cancel push button cancels the creation and closes the dialog box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
143
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 103. EPS: board selection
Figure 104. EPS: choose protected
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
144
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The EPS functional state of a board selected in the board view is displayed at the bottom of the view asshown in the following figures.
Protection role Protection status Switch Type
Figure 105. EPS functional state from protected active board view
Figure 106. EPS functional state from protecting active board view
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
145
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
12.3 Configuration: revertive and WTR for EPS
This functionality configure Revertive and Wait Time to Restore in a protection scheme.
In order to configure, perform the following operations:
– Select a transmission board in the Equipment view.
– Select the EPS pull down menu. Then select the Configure option as show in the following figure.
Figure 107. Configure EPS
The following dialogue box is opened.
Figure 108. EPS Management dialogue box
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
146
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The dialog box provides configuration for elements such as :
– the name of the protecting element as a label– the Equipment Type (board) of the protecting element as a label– a list displaying the protected elements owned by the scheme– the Revertive Mode flag as an option menu. The available values are revertive and non revertive– the wait time to restore time value (steps of 30 seconds, from 60 to 600). Only for N+1 EPS.
Notes: in the current release the Wait Time to Restore is fixed to 5 minutes.
For this NE:
• 1+1 ATM MATRIX 4x4 is Not Revertive only
• 1+1 ATM MATRIX 8x8 is Not Revertive only
• 1+1 MATRIX is Not Revertive only
• N+1 63 x 2 Mbit/s (P63E1 or P63E1N) protection is Revertive
• N+1 3x34/45 Mbit/s (P3E3/T3) protection is Revertive
• N+1 4x STM–1 ELECTRICAL port (P4ES1N) protection is Revertive
When the configuration of the equipment protection scheme is completed confirm closing the dialog boxby clicking on the OK push button. The Cancel push button cancels the configuration and closes the dialogbox.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
147
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
12.4 Switching EPS
This functionality enables to force a protecting board to work even if there is not failure.
The forced switch will fail if the other board is already forced switched or if the protecting board has a failurecondition.
In order to switch an EPS, perform the following operations:
– Select a transmission board in the Equipment view.
– Select the EPS pull down menu. Then select the Switch option as show in the following figure.
Figure 109. Switching EPS
The following dialogue box is opened.
Figure 110. EPS Switch dialogue box
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
148
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
This dialogue box displays in its left part the EPS of the selected board.
From this dialogue box the operator can configure, in the current release, only the Lockout options, byclicking on the relevant radio button.
The Manual to command perform the “manual” switch, active only if the other board is not alarmed.
Clicking on the OK push button will initiate the switch and close the dialogue box. The Cancel push buttoncancels the operation and closes the dialogue box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
149
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
12.5 EPS Overview
EPS Overview allows to display as well as search for EPS states.
Selecting the EPS Overview option from the Configuration pull down menu Figure 111. opens
Figure 111. EPS overview
To Search the EPS groups two different ways of filtering are supported; a filtering for all protection unitslocated on a dedicated Board Type as well as a filtering for protection units carrying a specific Status.
The search criteria can be chosen with the help of a combo box:
– Board Type: allows to filter for the EPS protected boards; the following filters values should beoffered (examples):• Ignore• MATRIX• MATRIXN• P3E3/T3• P63E1• P63E1N• P4ES1N• ATM4X4
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
150
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– Status: allows to filter for all possible EPS protection states;the following filters values should beoffered (examples):
• Ignore• Normal• DNR• Auto–Fail• Auto–WTR• Manual• Force• Lockout
After the filter selection click on Search button to start; the field below the Search button will be updated(see Figure 112. )
Figure 112. EPS overview after Search (Example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
151
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Each protection unit is presented with the following information:
– Protection Group (example protection GroupId, 40)
– Board Id (example r01sr1/board#40 )
– Board Role:
• Ped (Protected)• Ping (Protecting)
– B Status (board status):
• A (Active)• S (StandBy)• F (Faulty)
– Protection Status: defines the current state of the protection unit as follow
• Normal• DNR (Do Not Revert)• Auto–Fail (Autoswitch Equipment Fail)• Auto–WTR (Autoswitch Wait Time to Restore)• Manual (Manual switch)• Force (Force switch)• Lockout
The colors used for each row have the following meaning:
– Green (OK): for protected protection units active
– Red (Critical): for protected protection units in fail condition, protection unit in lockout or activeon autoswitch or commands
– Orange (Major): for protected units in standby after a command and protecting protection unitin 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 theEPS management views and subrack view, board view.In this way the operator has a quick link towards the views showing the correlation between the alarmsand the protection states.
N.B. Before to click on one of the five buttons select a row
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
152
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The buttons available are:
– Open Subrack View: opens the Subrack view showing the protection states with icons on theboards (see Figure 113. )
The possible protection states and the relevant symbols are explained inthe following:
Symbol EPS protection status
No RequestDo not Revert
Lockout
Auto Switch (WTR, Fail)ManualForced
– Open Board View: opens the board view showing the alarm and the board administrative states (see Figure 114. )
– Open Commands: opens the EPS Switch dialog box. See 12.4 on page 147 and the relevant description.
– EPS Management: opens the EPS Management dialog box. See Figure 102. on page 140and the relevant description.
– EPS Parameters: opens the EPS Configuration dialog box. See 12.3 on page 145and the relevant description.
Click on Close button to exit from the EPS Overview window
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
153
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 113. Subrack view after “Open Subrack View” command
Figure 114. Board view after “Open Board View” command
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
154
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
155
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
13 MULTIPLEX SECTION PROTECTION MANAGEMENT
13.1 Architecture types
The Multiplex Section Protection is the connection between two NEs protected by a cable and portduplication. At the source the signal is duplicated and sent to the sink via two independent cables. Whenoccurs a multiplex section failure, the system switches to the other cable and port.
The MS Linear Trail Protection can be applied to any NE where it is possible to configure a linear APS(single ended/dual ended) line protection. For this NE is applicable the APS 1+1 Proprietary, the APS1+1 Standard and the APS 1 :1 Standard dual ended.
The APS 1 +1 (not revertive) feature permits a 1+1 protection in a linear link, where a path signal isprotected by another dedicated path carrying the same signal. The protection can be set both in single(unidirectional) and in dual (bidirectional) ended mode.In single ended mode (unidirectional) the protection is accomplished by switching only the signal affectedby the failure.In dual ended mode (bidirectional) the protection is accomplished by switching both the affected and theunaffected signals.
Architecture 1+1 or N+1 StandardDescribed in ITU–T Rec. G783/G841. The refence switching criteria are SF and SD. It provides ak1/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 thusthis protection can be only single ended.
Architecture 1+1 Optimized (not used )
Architecture 1 : 1 Standard (not used )Described in ITU–T Rec. G783/G841 as architecture 1 : n ( with n=1 ). The refence switching criteriaare SF and SD. It provides revertive mode managed by k1/k2 protocol and thus this protection canbe 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 recognizedon the working port. The SD threshold reference value depend on the NE selected threshold on the MStermination point. This threshold value is configured as explained in the para.14.8 on page 193.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
156
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
13.2 MSP Options Introduction
All the MSP options are available starting from the Port View following the step explained below:
– Select Equipment from the Views menu
– Double click on the SDH optical board to configure to open the port icon
– Double click on the port icon to open the port view
– Select the MSP block in the port view and then choose the MSP options by clicking on Port –> MSPmenu; the possible choice are:
• MSP Create see para 13.3 on page 157.
• MSP Management see para 13.4 on page 161.
• MSP Commands see para 13.7 on page 166.
• MSP Delete see para 13.5 on page 163.
MSP Create, MSP Management, MSP Commands and MSP Delete can also be accessed from theTransmission –> MSP menu.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
157
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
13.3 MSP Create
Select the MSP Create option from the Port –> MSP menu ( see Figure 115. on page 157) to open theMSP Schema Creation (see Figure 116. on page 157).
Figure 115. MSP Create Option
Figure 116. MSP Schema Creation
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
158
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
In this release two MSP Protection Schemas are supported:
– MSP 1+1 standard
– MSP N:1 standard
Select one and then click on Add Port button in the Ports field to create a MSP schema.Figure 117. on page 158 is opened.Following steps are necessary:
– choose Port
– select a Port Role (protected or protecting)
– define Channel Id (mandatory for MSP N:1)
– define SDH Priority (type of traffic, High or Low)
Figure 117. MSP schema creation Port dialog
Select the Choose Port button to define the “Protected Port” and “Protecting Port” units.Figure 118. on page 159 is opened.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
159
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 118. TP Search
Click on Rack–Subrack and select the Board ( Protected / Protecting ) on the “Equipment” window (leftside).The “termination Points” list (right side) is available.
On this right side select the OpS TP of the chosen board and then click on the OK button. It is possibleto select the board through the “Board History” button selecting the board list menu.
The “Filter Section” is divided into different fields. It permits to visualize a reduced TP Class. If used, OpSclass must be selected. The complete TP research description is reported in the “Transmission View”chapter 14.5.1.2 on page 182.Click on the OK button and repeat the operation for both “Protected Port” and “Protecting Port”. If it hasbeen selected a Protected/Protecting port configured in a previously MSP schema protection an errormessage of access denied will be appear on the screen.
In the dialogue of Figure 116. on page 157 also configure the MSP protection schema with the chosenProtection Schema and enter the related Schema Parameters according the following rules:
• 1+1 Standard can be dual–ended or single–ended, Not Revertive.
• N+1 Standard can be only dual–ended Revertive.
At the end click on the OK button to confirm the MSP protection schema configuration. An error messagewill be appear if the selected schema is not supported by the NE.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
160
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 119. MSP 1+1 standard protection schema (example)
Figure 120. MSP N:1 standard protection schema (example)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
161
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
13.4 MSP Management
Select the MSP Management option from the Port –> MSP menu ( see Figure 121. on page 161 ) toopen the MSP Schema Configuration (see Figure 122. on page 162).
Figure 121. MSP Management Option
The MSP Schema Configuration dialog shows the current state of the MSP schema, settings and state(protected or protecting) of the current SDH-n port.
This dialog allows to set the configuration parameters for the designated multiplex section:
– Protection Schema reported in the previous paragraph 13.1 on page 155.
– Schema Parameters:
• Dual Ended / Single Ended protection switch and directionality.
• Revertive/Non Revertive mode.
• The WTR Time (Wait To Restore) is the delay time for switching protection and protecting portafter recovery from failure / defect.
• Enable Switch on SD is not operative in current release.
– Ports area display the current MSP schema:
• Port Id: identify the location of the board
• Role: identify the role of the board (“Protecting” or ”Protected”)
• Channel Id: mandatory for MSP N:1 (max. value is 14)
• Priority: type of traffic, High or Low
Configure the MSP protection Schema with the chosen protection schema and enter the related schemaparameters. At the end click on the OK button to configure the MSP protection schema. An error messagewill be appear if the selected schema is not supported by the NE.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
162
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 122. MSP Management View
13.4.1 MSP modification
The same MSP Management option can be used to modify the schema parameters of an active MSPconfiguration.
Before changing a single ended (unidirectional) schema into a dual ended (bidirectional), all activeswitches must be cleared (manual switch, lockout,... ). If the operator wants to change the protectionschema architecture or the ports involved in the MSP schema, the current schema must be removed andre–created.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
163
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
13.5 MSP Delete
Select the MSP Delete option from the Port –> MSP menu (see Figure 123. on page 163) to open the“MSP Schema Deletion” (see Figure 124. on page 163).
Figure 123. MSP Delete option
Figure 124. MSP Schema Deletion
Click on “OK” button to delete the selected MSP Schema Configuration
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
164
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
13.6 Display of Protection State
The MSP protection state of a port is displayed at the bottom of the Port view. Some examples are reportedin Figure 125.
The following states are always displayed:
Port Status – Active (red color) or Standby (orange color). The active protection status is referredto a protected/protecting port ( where the traffic is transported): when a failure is detected, theprotecting port is ready to save the traffic (and becomes active). The standby protection status isreferred to a protecting/protected port that is ready to save the traffic.
MSP Protection Role – Protected (green color) or Protecting (ochre color). The protection roledepends on the selected port type (Protected / Protecting).
MSP Group Status, MSP Own Unit and MSP Related Unit – (green color) Displayed if an automaticswitch is requested. “Own Unit” stands for the currently displayed unit in the port view, “Related Unit”stands for the related unit of the same protection group . The status indications are:
NR: (abbreviation of No Request); normal, idle condition, the traffic is on the main portDNR:(abbreviation of Do Not Revert); the SF or SD have been recovered but the traffic isswitched on the spare portPF: a protection failure has been detected on the portRF: a release command has been failedFOP: a failure of protocol has been detected
complete: = the bridge/switch actions are completedpending: = the bridge/switch actions are pending
The “complete” and “pending” indications precede the following statuses:AS: automatic protection switching enabledMS: a manual local protection command has been activatedFS: a forced local protection command has been activatedLO: a lockout local protection command has been activated
SF/SD: Signal Failure or Signal Degraded has been detectedWTR: wait time to restore status
MSP Request Source – (green color) indicates where the operator commands (force/manual/lockout)have been performed. Only present when a command is operative.– Local: switch due to near end SD/SF or local user switch command– Remote: switch due to received K1/K2 bytes.
A remote switch cannot be released locally, but can be overwritten by a switch with higher priority.
MSP Protocol Status
This parameter indicates the current APS Protocol status.The following values are possible:– OK– Failure (in case of FOP)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
165
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
MSP statuses displayed in a normal conditions
MSP statuses displayed after an automatic protection switching
MSP statuses displayed after a forced command
Figure 125. MSP Protection Status Examples
Figure 125. represents a MSP configuration with a normal condition, with an automatic protectionswitching and with a forced command. In any situation are represented the statuses displayed on bothprotected/protecting Port views. The Active status indication, with a forced command on the protectinggroup, shows where the forced command is applied.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
166
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
13.7 MSP Commands
Select the MSP Commands option from the Port –> MSP menu ( see Figure 126. on page 166 ) toopen the “MSP Commands window” (see Figure 127. on page 167).
Figure 126. MSP Commands option
Protecting Port : the location of the board hosting the protecting port is displayed.
Protected Port : the location of the board hosting the protected port is displayed.
The Lockout of protection command denies working channel access to the protection section by issuinga “Lockout” of protection request (on the “Protection Status” of MSP Management).It is possible to “Lockout the Protecting Port” or “Lockout the Protected Port”; to remove the lockoutcommands select Release Ping (for the protecting) and Release Ped (for the protected).
The Force to command switches the working channel (Protected port) to the protection section(Protecting port), unless an equal or higher priority switch command is in effect or SF condition exits onthe protection section, by issuing a “Forced” switch request for that port (on the “Protection Status” ofMSP Management). It is also possible to switch back to the working channel using again the “Force to”Protected port command.For 1+1 non–revertive system, forced switch no working channel transfers the working channel back fromprotection to working section, unless an equal or higher priority request is in effect. Since forced switchhas higher priority than SF or SD on working section, this command will be carried out regardless of theworking 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 priorityswitch 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 “Manualto” Protected port command.For 1+1 non–revertive system, manual switch no working channel transfers the working channel back fromprotection to working section, unless an equal or higher priority request is in effect. Since manual switchhas lower priority than SF or SD on working section, this command will be carried out only if the workingsection is not in SF or SD condition
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
167
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The Clear WTR command cancel the delay time for switching protection and protecting port afterrecovery from failure/defect.
The Exercise command issues an exercise request for protection channel and checks responses on MSPbytes, unless the protection channel is in use. This check controls the k1/k2 communication protocolfunctionality 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.
Figure 127. MSP Commands
The priority levels for the MSP commands are (from the higher to the lower one): Lockout, Force to,Auto–switch (SF&SD), Manual to.
Table 1. on page 167 gives the priority rules when are occurred two different commands. The first columnon the left and the first row at the top report the switch protection and the external MSP commands. Therow/column crossing gives the command or protection result (i.e.: if an “Auto–switch” and a “Manual to”command are present, “Auto–switch” is operative.
Table 1. MSP commands and Auto–switch protection priority
Lockout ofprotection
Forced to Auto–switch Manual to
Lockout ofprotection
–––––––––– Lockout Lockout Lockout
Forced to Lockout –––––––––– Forced Forced
Auto–switch Lockout Forced ––––––––––– Auto–switch
Manual to Lockout Forced Auto–switch –––––––––––
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
168
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
13.8 MSP overview
MSP Overview allows to display as well as search for MSP states.
Selecting the MSP Overview option from the Configuration pull down menu Figure 128. opens
Figure 128. MSP overview
To Search the MSP groups two different ways of filtering are supported; a filtering for all protection unitslocated on a dedicated Board Type as well as a filtering for protection units carrying a specific Status.
The search criteria can be chosen with the help of a combo box:
– Board Type: allows to filter for the MSP protected boards; the following filters values should beoffered (examples):
• Ignore• P4ES1N• P4S1N• P4E4N• P4S4N• P16S1N• S–41N• L–41N• L–42N• S–161• S–161N
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
169
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
• S–161ND• L–161• L–161N• L–161ND• L–162• L–162N• L–162ND• MATRIX• MATRIXN
– Status: allows to filter for all possible EPS protection states;the following filters values should beoffered (examples):
• Ignore• NR (Normal)• DNR• Auto–SF• Auto–SD• Auto–WTR• Manual• Force• Lockout• APS Invalid (Fail)• Bad channel (Fail)
After the filter selection click on Search button to start; the field below the Search button will be updated(see Figure 112. )
Figure 129. MSP overview after Search (Example)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
170
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Each protection unit is presented with the following information:
– Protection Group (example protection GroupId, 137)
– Port Id (example r01sr1sl33/port#02–OpS )
– Role:
• Ped Protected• Ping Protecting
– Status (board status):
• A (Active)• S (StandBy)• F (Faulty)• ET Extra Traffic (Not operative)
– Protection Status: defines the current state of the protection unit as follow
• NR (Normal)• DNR (Do Not Revert)• Auto–SF (AutoSwitch Signal Fail)• Auto–SD (AutoSwitch Signal Degrade)• Auto–WTR (AutoSwitch Wait Time To Restore)• Manual (Manual Switch)• Force• Lockout• APS Invalid (Protection fail condition APS invalid)• Bad channel (Protection fail condition Channel Mismatch)
The colors used for each row have the following meaning:
– Green (OK): for protected protection units active
– Red (Critical): for protected protection units in fail condition, protection unit in lockout or activeon autoswitch or commands
– Orange (Major): for protected units in standby after a command and protecting protection unitin 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 theMSP 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 correlationbetween the alarms and the protection states.
N.B. Before to click on one of the five buttons select a row
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
171
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The buttons available are:
– Open Port view: opens the port view showing the correlation between the alarm and the MSPprotection states. See Figure 130. on page 171.
– MSP Create: opens the MSP Create dialog box. See Figure 116. on page 157 and the relevant description.
– MSP Delete: opens the MSP Delete dialog box. See Figure 124. on page 163 and the relevant description.
– MSP Management: opens the MSP Management dialog box. See Figure 122. on page 162 andthe relevant description.
– MSP Commands: opens the MSP Commands dialog box. See Figure 127. on page 167 and therelevant description.
Click on Close button to exit from the EPS Overview window
Figure 130. Port view after “Open Port View” command
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
172
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
173
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14 TRANSMISSION VIEW
14.1 Overview
This section describes the operations necessary for the consultation, modification and configuration ofTPs, providing a representation of the entire signal flow.
The generic Transmission View, described in this chapter, offers the possibility of displaying a single TPor 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 searchdialog or access the view directly from another view, e.g. by navigating from the Port View.
The Transmission View provides the following features:
– Brief overview regarding transmission resources.
• An overview concerning all TPs belonging to a port can be called in by activating the functionto expand the selected TP. TP names are listed in an additional information area if the mousepointer is positioned over it. The following states are indicated:
– the alarm state is indicated by the alarm synthesis icon– the cross-connection state is indicated by a cross– whether a TP can be structured is indicated by a circle– whether a TP is under Performance Monitoring indicated by a blue “P” letter– whether a TP is involved in a loop action, it is indicated by an arrow
• An overview concerning signal flow can be requested by a user action. The user can selecta TP and apply the action Show Cross-connected TPs. The result is that the objects relatedto the TP are displayed and lines indicate the connections. Expanding and hiding TPs that arerelated to the currently selected TP (e.g. show all TPs that are above the TU-12 CTP) enablesall related TPs to be added to the view, thus providing a representation of the entire signal flow.
– Display of single or multiple termination points.
• Search for and select a termination point in a TP search dialog and display it in the TransmissionView.
• Pop-up the Transmission View from the board view. All TPs/compound TPs associated with thephysical port are displayed (i.e. TPs down to AU-4).
– Provide the functionality to create/show cross-connections.
– Provide the functionality to create/show Multiplex Section Protection
– Provide the functionality to create/show Loopback commands.
– Provide the possibility of configuring a selected TP. This functionality is accessed by calling theconfiguration 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
174
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.2 View elements
The Transmission View uses the symbols illustrated in Figure 131.
��������������� ������������
���������������
�������������������
��������������������������������������
�����������������
������������������������� ���������������
���
���������� ����������
� ������������������������������
Figure 131. Symbols Used in Transmission View
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
175
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.3 View Layout
The Transmission View is a main view. It provides views of specific areas, which display the transmissionresources, and the specific Transmission View pulldown menu which provides the Transmission Viewoperations.
14.3.1 View Description
Figure 132. illustrates the Transmission View area. TPs that are received from the network element aredisplayed in the Transmission View with the respective TP and connection symbols described inFigure 131. The number of TPs presented initially depends on whether the Transmission View is poppedup from a board view, whether a TP has been selected in another view or whether it is called without aselected TP.
When the “Transmission view” is reached selecting the Transmission option in the View pull down menuin its initial state contains no objects.
Figure 132. Transmission View Area
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
176
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.3.2 Number of TPs Displayed in Transmission View
It is possible both to expand a VC-4, thus displaying all underlying TPs, and to hide TPs which are of nointerest. The objects initially displayed depend on the situation/definition.
14.3.3 Naming TPs
The following rules are applied in order to identify the TPs displayed:
– the root node contains the full user label,
– all child nodes contain a short label indicating the position inside the tree.
14.3.4 Dynamic View Behavior
The following section describes the view states and provides a short description of events that affect theview.
14.3.4.1 Initial state of the view
In its initial state, the Transmission View contains no objects. Objects can be searched for and displayedusing the Add TP dialog.
14.3.4.2 Working state of the view
In its working state, the Transmission View already contains objects. If the operator searches for anddisplays a TP using the TP Search dialog, the view is first initialized again and then the TP is displayed.The same applies in the case of navigation from another view to the Transmission View – the TransmissionView is always initialized and the corresponding objects are then displayed in it.
14.3.4.3 Navigation to Transmission View from other views
If the Transmission View is popped up from the Port View, only the selected TP is displayed.
14.3.4.4 Alarm notification
Alarms concerning the TPs displayed are indicated graphically by the alarm synthesis icons of the TPobjects. The TP objects are updated accordingly.
14.3.4.5 Object deletion
All kinds of object deletion events related to TPs displayed are indicated by the TP objects. The graphicalobjects are removed accordingly from the Transmission View. Example: modification of the payloadstructure from 63 TU-12 to 3 TU-3.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
177
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.4 Transmission view access and menu
The “Transmission view” can be reached selecting the Transmission option in the View pull down menu.In this case, in its initial state, the Transmission View contains no objects.
In the case of navigation from another view (example the “Port view”) to the Transmission View, theTransmission View is always initialized and the corresponding objects are then displayed in it (see forexample Figure 132. on page 175.
Selecting the “Transmission” option in the menu bar of Figure 132. on page 175. the complete pull downTransmission menu is presented (Figure 133. )
The following menu items are available:
– Add TP Select the TP to show on the Transmission view.It is described in the following paragraph.
– Expand Display TPs that are related to the selected TP.It is described in this chapter, see para 14.14.1 on page 208.
– Hide Hide TPs that are related to the selected TP or the selected TP.It is described in this chapter, see para 14.14.2 on page 209
– TP Configuration Set parameters for the Overhead on Synchronous TP’s.It is described in this chapter, see para 14.6 on page 186
– TP Frame Mode Configuration: Set parameters for 2Mbit/s G.703/G.704 or ISDN–PRAmanagementSee para. 14.7 on page 191
– TP Threshold Configuration Set B2 ExBER and Degraded Signal parameters.It is described in this paragraph, see para.14.8 on page 193.
– Terminate TP Terminate a path on a AU-4 CTPIt is described in this chapter, see para 14.9 on page 194
– Disterminate TP Disterminate a path on a AU-4 CTPIt is described in this chapter, see para 14.9 on page 194
– AU4 Concatenation: See paragraph 11.5 on page 123
– Cross-Connection Manage the connection of the paths. See para. 15 on page 213
– Monitoring Operations Create, configure and delete POM, SUT and TC TP’s.It is described in this chapter, see para 14.10 on page 195
– Performance Set and show Performance Monitoring parameters and data.See chapter 17 on page 269.
– Structure TPs Provides the possibility of structuring and destructuring selected TPIt is described in this chapter, see para 14.11 on page 200
– Loopback Manage the loopback commands, for commissioning ormaintenance purposes. See paragraph 14.12 on page 201.
– Physical Media Manage the physical TP setting. See para 14.13 on page 206.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
178
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– MSP Manage the Multiplex Section Protection of the NE. Not available for PDH port
See paragraph 13.4 on page 161. In this paragraph is not describedthe MSP>NE MSP synthesis option of the Transmission menu, notused in this NE.
– Show Supported Board Navigate to the upper board level.It is described in this chapter, see para 14.14.3 on page 210
– Navigate to Port View Permit to show the detailed alarm of the TP.It is described in this chapter, see 14.14.4 on page 211
These options are described in next paragraphs except the previously referenced.
Figure 133. Transmission menu options
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
179
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.5 ADD TP
Select the Transmission –> Add TP option.
This menu item opens the TP Search dialog (see Figure 134. ). The TP Search dialog enables the userto search for and add a TP to the Transmission View (e.g. search for all TPs on a board with PM enabled).
14.5.1 TP Search
14.5.1.1 Default Mode
In this mode, the dialog displays the structure of the equipment tree. After double-clicking, e.g. on a port,the contents of the port appear on the right-hand side of the dialog (TP list). To keep the number of itemsdisplayed small, they are displayed in a hierarchical order. Double-click again to recall the next level (seeFigure 136. ).
Figure 134. TP Search Dialog, Initial State
After double-clicking on an object, an Information window appears (see Figure 135. ). The message textcorresponds to the object selected.
Figure 135. Information Window
The search can be stopped with Cancel.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
180
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
It is possible to select several individual TPs from the TP list by clicking on them while holding down theCtrl key on the keyboard. To select a block of TPs, click on the first TP and then click on the last TP in theblock while holding down the Shift key on the keyboard. But only the first TP selected in the list will beshown in the Transmission View.
Figure 136. TP Search Dialog with Various TP Selections
After clicking on Show CC State, a more detailed TP list is displayed (see Figure 137. ) containing TPcross connection status information.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
181
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 137. TP Search Dialog with Status Information Displayed
The symbols in the TP list have the following significance:
����������
�����������������
�����������������������������
����������
Figure 138. Symbols in TP Search
The background color of the symbols represents the status of the TP:
– grey = inactive
– green = active
An easy way to recall to previously displayed boards is to use Board History. Select the relevant boardfrom the list.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
182
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 139. Board History Check List
14.5.1.2 Search Mode
Use Search Mode together with the filtering options provided below the TP list (see Figure 140. ). Thefollowing options are available:
– Class:
Ignore, TU-12, VC-12, VC-12+TU-12, TU-3, VC-3, VC-3+TU-3, AU-4, VC-4, VC-4+AU-4.
– Connection State (Current connectivity status):
Ignore, not connected, connected
– Alarm State (Path Trace):
Ignore, critical, major, minor, warning, not alarmed
– Assign State:
Ignore, NML, EML
– Perf. Monitoring (Performance Monitoring condition):
Ignore, enabled
– TTI expect: not used
– TTI receive: not used
– TTI transmit: not used
– Location:Permits to insert the location of the TP in the following format:r<rack#>sr<subrack#>sl<slot#><port#>
– Name: not supported
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
183
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 140. TP Search Dialog with Different Filtering Options
After activating the search process with the Search TP button, the following dialog box appears. Thesearch can be interrupted by clicking on Cancel.
Figure 141. “Information...” Dialog for Search Process
N.B. When searching for PM-enabled TPs on NE, Rack or Subrack, the time for the request can bevery high. It is recommended to search for PM-enabled TPs at the board level (a board isselected for the search).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
184
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.5.1.3 Common Buttons
The following buttons are available in all modes:
14.5.1.3.1 Ok
Closes the dialog and opens the Transmission View containing the selected TP, as for the example ofFigure 132. on page 175.
14.5.1.3.2 Close
Closes the dialog without updating the Transmission View.
14.5.1.3.3 Print
This command is used to generate and print a list of TPs according to the current filter selection (refer toFigure 144. for an example of a printout).
The command opens the following dialog:
Figure 142. Print to Printer
Select the desired printer from the list box and click on Ok to start the print job or abort with Cancel.
The dialog changes after clicking on File:
Figure 143. Print to File
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
185
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Enter the name of the output file in the input field or select a file name from the File Select dialog by clickingon Select file. Select if the output format should be Postscript or ASCII.
The output file is generated after clicking on Ok. Use Cancel to stop the process.
Figure 144. Example Printout
14.5.1.3.4 Help
This command opens the online help for the TP-Search dialog.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
186
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.6 TP Configuration
Select the Transmission –> TP Configuration option .
TP Configuration can also be accessed from the “Port” view menu.
14.6.1 High Order TP Configuration
Depending on the TP selected, a dialog appears for the configuration of the main parameters of thefollowing objects:
– VC-4 TTP (140 Mbit/s PDH)
– VC-3 TTP (34 and 45 Mbit/s PDH)
– Mod VC-4 TTP (matrix resource)
The main parameters are:
– C2 Signal Label: “Automatic” (decided by the NE) or “Equipped not specific”.
– J1 Path Trace.
The dialogs of the following figure appears:
Figure 145. High Order TP Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
187
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.6.1.1 J1 Path Trace
Operative only on VC–4 in current release.
If the Path Trace is 16 bytes long, the first byte is a CRC7 checksum calculated by NE.
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 2. Default value for C2/V5 Signal Label
TP VC–4 TTP / AU4 CTP(SDH)
VC–4 TTP(PDH)
VC3–TTP VC–12 TTP
Significant Byte C2 C2 C2 V5
Default value 2 18 4 2
14.6.1.2 C2 Signal Label
Received and Expected fields are read only.They can display the following number, according the G.707 recommendations for the C2 Signal Label:– 0: Unequipped– 1: Equipped non-specific– 2: TUG structure– 3: Locked TU-n– 4: Asynchronous 34/45Mbyte– 18: Asynchronous 140Mbyte– 19: ATM– 20: MAN, DQDB– 21: FDDI.
In the Transmitted field it is possible to select the values:• Automatic: the C2 Signal Label value is automatically selected by the NE according the VC
structure.• Equipment not specific (it corresponds to number 1)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
188
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.6.2 J0 Section Trace management
Select RST block and then select Port–> TP Configuration.
The fields of the following figure appears:
Figure 146. J0 Configuration
This function is implemented in order to manage the J0 Trace configuration.This dialog shows the current values for received, expected and transmitted trail trace and it allows theoperator to change only the values of expected and transmitted trail trace.The received trail trace is read–only.Expected and Transmitted fields are editable by the operator.With the relevant button it is possible to enable or disable TTI Monitoring.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
189
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.6.3 Low Order TP Configuration
Depending on the TP selected, a dialog to configure the main parameters of the following objects:
– VC-12 TTP.
The main parameters are:
– V5 Signal Label. “Automatic” (decided by the NE) or “Equipped not specific”.
– J2 Path Trace. Not operative in current release.
The following dialogs appears:
Figure 147. Low Order TP Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
190
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.6.3.1 J2 Path Trace
Not operative in current release.
If the Path Trace is 16 bytes long, the first byte is a CRC7 checksum calculated by the NE.If the Path Trace is shorter than 16 bytes, it is filled with zero bytes (“0” hexadecimal).
Expected and Transmitted fields are editable by the operator.Mode1 enable the 16 bytes long sequence for Path traceOne 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.
14.6.3.2 V5 Signal Label
Received, Expected and Transmitted fields are read only.
They can display the following number, according the G.707 recommendations for the V5 Signal Label:
– 0: Unequipped– 1: Equipped non-specific– 2: Asynchronous– 3: Bit Synchronous– 4: Byte Synchronous
In the Transmitted field it is possible to select the values:
• Automatic: the C2 Signal Label value is automatically selected by the NE according the VCstructure.
• Equipped not specific (it corresponds to number 1)
To replace modified with the default, enter the default manually according to the value reported inTable 2. on page 187.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
191
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.7 TP Frame Mode Configuration
This command is available for:
– P12
Select the Transmission –>TP Frame Mode Configuration option.
TP Frame Mode Configuration can also be accessed from the “Port” and “Synchronization” view menu.
This menu item enables the configuration of the most important transmission parameters concerning thePrimary Rate Access and G.703/G.704 frame management.
The following dialog appears:
Figure 148. TP Frame Mode Configuration
The windows contains the following graphical objects:
– ”Framed Signal Mode” that allows to configure the attribute framed Signal Mode; the user canchoose one of the following value:
• ”Not Framed” (G.703 interface): the PRA function cannot be activated ;
• “Framed without PRA” (G.704): the behavior according to ETS 300–233 is applied in thehandling of bits of Time Slot 0 in terms of state, defect detection and consequent action;
• ”Framed with PRA” : PRA function are activated
• ”Framed with leased line PRA” : a proprietary leased line behavior is applied.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
192
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– “CRC4 Mode“ that defines the monitoring capabilities applied to the signal with a CRC multiframe:
• “Enabling”: enable or disable the CRC–4 error counting
• ”Remote Indication”: read–only field that indicates if status of CRC–4 error countingfunctionality of far–end NE is enabled or disabled
– “Frame Status” that reports an indication of the received signal:
• ”no indication”
• “the 2Mb/s signal is multi–frame”
Press Ok to apply the parameters or Cancel to close the dialog.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
193
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.8 TP Threshold Configuration
This menu allows the operator to set the alarm thresholds for MST and VCi layer.
Select the MST or the VCi block.
Select the Transmission –> TP Threshold Configuration option.
Figure 149. will be opened.
The user can select one of the two different Defect distribution:
– Poisson distribution enable configuration of the Excessive Bit Error Ratio (ExBER on MST, VCi)threshold and of the Signal Degrade (SD on MST, VCi) threshold of the TP’s related countedprimitives.
– Bursty distribution enable configuration of the maximum number of errored frames and the totalamount of bad block per frame.
– ExBER – Threshold : 10–3 to 10–5
– Enable Consequent Actions : fixed to enabled
– Signal Degrade – Threshold : 10–5 to 10–9
– Bursty Parameters – Threshold : 1 or 10 or 100 or 1000
– Bursty Parameters – Consecutive Bad Seconds : 2 to 10
Figure 149. Degraded Signal Threshold selection
Click on Ok to confirm the chosen parameters.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
194
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.9 Terminate/Disterminate TP
Select the Transmission –> Terminate TP or Disterminate TP option.Only one command in the menu is available, depending on whether a TP is terminated or not.
14.9.1 Terminate TP
Use this action to terminate a path. It can be performed on a AU-4 CTP.A cross-connection between the selected AU-4 CTP (= aTP) and a modifiable VC-4 TTP (= bTP) iscreated. Three TUG-3 and TU-3 are created if the modifiable VC-4 TTP was not already structured.A cross appears in the icon of the terminated TP:
If the TP is already cross-connected a error message appears.
14.9.2 Disterminate TP
Use this action to disterminate a path. It can be performed on a AU-4 CTP. The related cross-connectionis deleted.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
195
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.10 Monitoring Operations
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/TC (Path OverheadMonitoring, Supervised Unequipped Termination and Tandem Connection).
This command is available for:
– AU-4 CTP
– TU-3 CTP
– TU-12 CTP
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
196
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.10.1 Creation/Deletion
This dialog allows multiple object creation/deletion.The dialog shown in the following Figure 150. opens:
Figure 150. Monitoring Operations Creation/Deletion
The Path Overhead Monitoring has the following parameters:
– Before Matrix (available only on AU–4 CTP)– After Matrix
The Supervisory Unequipped Termination, not operative in current release, has the following parameters:
– Sink (before matrix)– Sink (after matrix)– Source– Bidirectional
The Tandem Connection has the following configurable parameters:
• Tandem Connections Monitoring (TCM):– TCM Before Matrix– TCM After Matrix
• Tandem Connection Termination (TCT):– TCT Bidirectional Before Matrix– TCT Bidirectional After Matrix
Press Ok to apply the parameters or Close to close the dialog and discard the not with Ok appliedchanges.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
197
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
When select and apply the Path Overhead Monitoring, the changes will be displayed in the Port View inthe following manner:
Figure 151. Display of POM and TCM in Port View (example)
When select and apply the Tandem Connection Monitoring / Tandem Connection Termination, thechanges will be displayed in the Port View in the following manner:
Figure 152. Display of POM and TCM/TCT in Port View (example)
Also refer to para. 11.9 on page 138, about navigation to Monitoring View.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
198
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.10.2 Configuration
Depending on the parameters selected in the Monitoring Operations Creation/Deletion dialog, not allsections of the dialog are available.
NOTE: It is possible to open the POM and TCT/TCM Configuration dialog for a CTP even if neitherPathOverheadMonitor nor Tandem Connection was created before (SUT isn’t available in thisrelease). No changes can be made in this case and the values displayed can be ignored.
Figure 153. Monitor Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
199
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– TTI Definition
The TTI (Trail Trace Identifier) has a maximum length of 16 characters.
The following TTI Definitions are available:
• TTI Expected• TTI Received without the display• TTI Sent
The following TTI Types are available:
• TTI Enabled• TTI Disabled• TTI Repeated Byte
– Error Distribution
Poisson and Bursty error distribution are supported.
– TCM/TCT ConsActions
It is needed to support explicit consequent action activation (AIS insertion) for TCT sink andbidirectional.
– Thresholds
Set the thresholds of the following parameters:
• Signal DegradePoisson mode only: from 10–5 to 10–9.
• Excessive ErrorPoisson mode only: from 10–3 also if presented a selection from 10–3 to 10–5
• Bursty DegradeSelect a value between 1 and 1000 errors/sec for the Bursty Degrade threshold.
• Bursty ConsecutiveSelect 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
200
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.11 Structure TPs
Select the Transmission –> Structure TPs option as for the following figure.
This menu item provides the possibility of structuring and destructuring a selected TP. The level that isselected defines how the signal is to be structured, e.g. if a VC-4 TTP is selected and the menu item TU-12is chosen, the signal is structured down to 63 TU-12 CTPs. The following menu items represent all thosepossible:
– TU-2. Not supported.
– TU-3.
– TU-12.
– VC-3/VC-4. Not supported.
– VC-12. Not supported.
The following items are available for synchronous TPs:
– modifiable VC-4 TTP: TU-3, TU-12
– TUG-3: TU-3, TU-12
– TUG-2: TU-12.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
201
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.12 Loopback
The commands of this menu item are for the management of the loopback commands, for commissioningor maintenance purposes.
14.12.1 Loopback Configuration
The loopbacks can be applied at line (external to equipment) level or at internal equipment level. Theloopback commands are used to separate the communication network into independent part checking theline/equipment functionality during the network installation or maintenance operation.
The loopback architecture provides four configurations ( see Figure 154. ).Line Loopback And ContinueLine Loopback And AISInternal Loopback And ContinueInternal Loopback and AIS
Line Internal Line
Line
Destination
Destination
Initial
Initial
Destination
AIS
Internal Line
AIS
Internal loop And Continue Internal loop And AIS
Line Loop And Continue Line Loop And AIS
Initial Destination
Initial
Figure 154. Loopback configurations
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
202
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Select a TP that supports the Loopback Configuration
Loopbacks act on the following TPs:
• PDH board (only from the Port View):– Line loopback performed on:
• P for 2/34/45/140 Mbit/s PPI
– Internal loopback performed on:• p12 for 2 Mbit/s CTP• p31 for 34/45 Mbit/s CTP• p4 for 140Mbit/s CTP
• SDH board:
The loopback configuration can be done only on SDH ports with the acronym endingwith a “ N” letter (i.e. P4S1N, S–4.1N, L–4.1N, L–4.2N, etc.)
– Line loopback performed on:• EIS for electrical STM–1 SPI• OpS for optical STM–1, STM–4, STM–16 SPI
– Internal loopback performed on:• MsT TTP for STM–1, STM–4, STM–16 ports
Select the Transmission –> Loopback –> Port Loopback Configuration option as for the followingfigure.
Port Loopback Configuration can also be accessed from the “Port” view menu.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
203
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 155. opens.
Figure 155. Port Loopbacks View
Choose the TP clicking on the “Choose TP” button. Select the TP where to apply the loopback command.For the TP selection procedure, follow the TP research description reported in para. 14.5.1 on page 179.For this NE the “Timed Loopbacks” field is not managed and thus Start/Stop loopbacks time is noteditable.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
204
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.12.2 Loopback Management
To manage the loopback configuration select the Transmission –> Loopback –> LoopbackManagement option as for the following figure.
Loopback Management can also be accessed from the “Port” view menu and from the “Configuration”menu.
Figure 156. opens.
Figure 156. Loopback Management
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
205
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The configured loopback are listed into the current loopbacks table. This table can be managed by the“Search” criteria, “Delete” and “Create” commands.
– Search Criteria (not operative): to configure the filter select the “Loop and Continue” type (Yes= LoopAnd Continue, No= Loop And AIS) then select the “Directionality” Internal or Line and edit the InitialTP Id (write: rack, subrack, board, port# and the TP type: EIS (SPI/PPI Electrical), OpS (SPI/PPIOptical), 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/Disablebutton. Click on the “Search” button to start the configured loopback research into the currentloopback table.
– The “Delete” command permits to delete a loopback listed in the Current loopbacks Table: select aloopback in the list and click on the “Delete” button.
– The “Create” command permits to create a new loopback configuration: clicking on “Create” theprevious figure ( Figure 155. ) opens. Follow the previously paragraph indications to create a newloopback configuration.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
206
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.13 Physical Media
Select the Transmission –> Physical Media option as for the following figure.
The Physical Media options permit to set physical configuration of each TP.
It opens a menu in which the various options will be available according the TP’s type (for the optioncommon with the “Port view” reference is made to the relevant paragraph):
– ALS Management. See para. 11.6.1 on page 126.
– Show Optical Configuration See para.11.6.2 on page 129.
– TX Quality Configuration See para.18.2.11 on page 312.
– Single Fiber Configuration. See para.11.6.3 on page 130.
– Extra traffic Not operative
– Regeneration Section management Not operative
– Line Length Configuration See para.11.6.5 on page 133.
– Set Domain See para. 14.13.1 on page 207.
– HDSL Configuration Not operative
– NT Configuration Not operative
– X21 Configuration Not operative
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
207
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.13.1 Set Domain
This option is referred to the SECurity management and allows the user to set the Manager list and theAccess 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 dialog–box contains the following fields:
– NML Assignment: each connected manager to the TP is highlighted in the list. The user can set amanager 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. TheEML–USM administrator (SH or Craft Terminal) should set the Manager List only to remove amanager 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 tothe TP.The different domains could be assigned to different operators.
OK button is used to validate the selection.
Cancel button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
Figure 157. Set Domain
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
208
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.14 Navigation Commands
14.14.1 Expand
Select the Transmission –> Expand option as for the following figure.
This menu item provides the possibility of displaying TPs that are related to the selected TP. These maybe TPs that are contained by the TP or TPs which belong to the physical port that is actually connectedto the TP.
– Show next level of lower TPs,
– Show all lower TPs,
– Show next level of upper TPs,
– Show all upper TPs.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
209
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.14.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 ofa selected TP.
– Lower TPs,
– Upper TPs,
– Selected TPs.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
210
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.14.3 Show Supported Board
Select the Transmission –> Show Supported Board option.This menu provides the possibility of navigating directly to the board that supports the TP.
The Board View appears:
Figure 158. Board View (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
211
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
14.14.4 Navigate to Port View
Select the Transmission –> Navigate to Port View option.
This menu provides the possibility of navigating to the corresponding Port View related to the selectedTP in order to access a detailed overview of alarms quickly.
The Port View appears:
Figure 159. Port View
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
212
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
213
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15 CROSS-CONNECTION MANAGEMENT
15.1 Introduction
15.1.1 Overview
The purpose of this domain is to manage the connection of the high and low level path.
The following chapters provide the user with information concerning operations on cross-connections:
– Para. 15.1.2 on page 214 “Multiplex Structures for SDH”gives an overview on the SDH technology
– Para. 15.1.3 on page 217 “Definition of Termination Points”gives an overview about the termination points implemented on the NE
– Para. 15.1.5 on page 222 “Cross-Connection Types”provides information concerning cross-connection types supported by the NE
– Para. 15.1.6 on page 224 “Cross-Connection Protection”provides information concerning cross-connection protection supported by the NE
– Para. 15.2 on page 226 “Operative sequence to execute Cross-Connections”details the complete procedure to realize cross-connection
– Para. 15.3 on page 228 “Cross-Connections Management”details the contents of the main cross-connections view
– Para. 15.4 on page 234 “Create/Modify Cross-Connections”describes the creation and modification of cross-connections
– Para. 15.5 on page 249 “Activate/Deactivate/Delete Cross-Connections”describes the activation, deactivation and deletion of cross-connections.Activation and deactivation not supported in current release.
– Para. 15.6 on page 250 “Split and Join Cross-Connections”describes how to split or join bidirectional cross-connections.
– Para. 15.7 on page 253 “Protection Switching”deals with switching actions (force, manual, lockout protection) on cross-connections
– Para. 15.8 on page 255 “Print”deals with printing out list entries on printers or into files
– Para. 15.9 on page 256 “Show Cross-Connected TPs”describes the possibility of showing connections between two or more TPs of different differenthierarchies, e.g. connection between au4 and vc4.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
214
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.1.2 Multiplex Structures for SDH
By introducing the Synchronous Digital Hierarchy (SDH), a standardized transmission has been created,matching the European with the American standard. The SDH signal structure contains an extendedoverhead as well as a fixed pointer controlled assignment of the user signal elements, thus improving thepossibilities of the network management.
Signals of the Synchronous and Plesiochronous Digital Hierarchy (PDH) are packed by synchronousmultiplexers into Virtual Containers (VC). The STM-1 signal structure is achieved by using the multiplexstructure complying with ITU-T and ETSI, (see Figure 160. ). Each of the user channels (2 Mbit/s, 34Mbit/s, 45 Mbit/s and 140 Mbit/s) is packed into a container synchronous to the STM-1 frame accordingto a predefined structure.
To adjust the plesiochronous signals to the synchronous network clock, certain filling algorithms areavailable. 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 VirtualContainer (VC). With the pointer pointing to the start of the VC, in respect of the STM-1 frame, anAdministrative 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 aVC. The AU of the signal, together with the Section Overhead (SOH), finally make up the STM-1 frame.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
215
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
STM
–NST
M–1
AU
–4V
C–4
C–4
TU
G–3
AU
–3V
C–3
C–3
TU
G–2
TU
–2V
C–2
C–2
TU
–12
VC
–12
C–1
2
TU
–11
VC
–11
C–1
1
TU
–3V
C–3
140
Mbi
t/s
(45
Mbi
t/s)
34 M
bit/s
6 M
bit/s
2 M
bit/s
(1,5
Mbi
t/s)
Leg
end:
C VC
TU
TU
GA
U
: Con
tain
er: V
irtu
al C
onta
iner
: Tri
buta
ry U
nit
: Tri
buta
ry U
nit G
roup
: Adm
inis
trat
ive
Uni
t
x1x3
x3
x3x1
x7
x7
x4
x1xN
Poin
ter
-Pro
cess
ing
not i
mpl
emen
ted
Figure 160. SDH Multiplex Structure according to ITU-T G.707
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
216
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The STM-1 frame consists of:
– a Section Overhead (SOH)– an AU Pointer area– a payload area
Payload
Section Overhead
SOH
AU – Pointer
Section Overhead
SOH
270 Columns (Bytes)
9 rows
1 9 270
1
9
3
4
5
Figure 161. 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 VirtualContainer. These Virtual Containers are of different size and may be nested or packed differently.
Virtual Containers for the European bit rates:
– the STM-1 frame contains a VC-4,– a VC-4 may contain one C-4 or three TUG-3,– each TUG-3 may contain one VC-3 or seven TUG-2,– each TUG-2 contains three VC-12 or one VC-2.
An STM-1 user signal can be constructed of:
– either 1 x VC-4– or 3 x VC-3– or 2 x VC-3 + 7 x VC-2– or 2 x VC-3 + 21 x VC-12– or 1 x VC-3 + 14 x VC-2– or 1 x VC-3 + 7 x VC-2 + 21 x VC-12– or 21 x VC-2– or 14 x VC-2 + 21 x VC-12– or 7 x VC-2 + 42 x VC-12– or 63 x VC-12.
STM-N signals are constructed by integer multiples of the basic signal STM-1 of 155.520 Mbit/s. Forexample an STM-16 signal of 2.488.320 Mbit/s is generated by combining sixteen STM-1 signals byteinterleaved.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
217
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.1.3 Definition of Termination Points (TP)
When ports are depicted on the user interface, the following abbreviations are used.
This section concerns the multiplex structure (see Figure 160. ) as well as on the information model ofobject-oriented programming which was used when forming the user interface. As a rule, a TerminationPoint (TP) is the starting and terminating point of a transmission segment. A distinction is made betweenthe following types of TPs:
– CTP (Connection Termination Point)The CTP represents the termination of a connection. The transmission signal is ”terminated”, i.e.,the received signal is monitored and the error signaling evaluated, while own-code signaling isinserted in the transmitted signal.
– TTP (Trail Termination Point)The TTP represents the termination of a transmission segment. The signal is monitored and passedon after modification in one form or another.
Both TP types exist on the SDH level and the PDH level.
– CTPs on SDH levelOn SDH level (see Figure 162. ) a distinction is made between the following CTPs:
• AU-4 (Connection Termination Point)The AU-4 CTP represents both the creation and termination of an STM-1 connection. TheHigh-order Connection Supervision (HCS) function is included.
• TU-x (Connection Termination Point), i.e. TU-12 CTP, TU-2 CTP, TU-3 CTP.The TU-x CTP represents both the creation and termination of a VC-x connection. TheLow-order Connection Supervision (LCS) function is included.
– CTPs on PDH levelOn PDH level (see Figure 163. ), a distinction is made between the following CTPs:
• E4 (Connection Termination Point)The E4-CTP represents the non–intrusive monitoring of incoming 140 Mbit/s PPI.
• S4 (Connection Termination Point)The S4-CTP represents the non–intrusive monitoring of outgoing 140 Mbit/s PPI .
• E32 (Connection Termination Point)The E32-CTP represents the non–intrusive monitoring of incoming 45 Mbit/s PPI.
• S32 (Connection Termination Point)The S3-CTP represents the non–intrusive monitoring of outgoing 45 Mbit/s PPI .
• E31 (Connection Termination Point)The E31-CTP represents the non–intrusive monitoring of incoming 34 Mbit/s PPI.
• S31 (Connection Termination Point)The S31-CTP represents the non–intrusive monitoring of outgoing 34 Mbit/s PPI .
• E1 (Connection Termination Point)The E1-CTP represents the non–intrusive monitoring of incoming 2 Mbit/s PPI. TheMon.(Monitoring) label indicates that is possible to enable the CRC4 control signal.
• S1 (Connection Termination Point)The S1-CTP represents the non–intrusive monitoring of outgoing 2 Mbit/s PPI . TheMon.(Monitoring) label indicates that is possible to enable the CRC4 control signal.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
218
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– TTPs on SDH level
On SDH level (see Figure 162. ) a distinction is made between the following TTPs:
• ES (Electrical Section TTP)An ESTTP displays the physical characteristics of a port with electrical access (level and codemonitoring and conversion).
• OS (Optical Section TTP)An OSTTP displays the physical characteristics of a port with optical access (level and codemonitoring and conversion).
• RST (Regenerator Section TTP)An RSTTP displays the creation and/or termination of an RSOH (Regenerator SectionOverhead), i.e., rows 1 to 3 of the first 9xN columns of an STM-N frame.
• MST (Multiplexer Section TTP)An MSTTP displays the creation and/or termination of an MSOH (Multiplexer SectionOverhead), i.e., rows 5 to 9 of the first 9xN columns of an STM-N frame.
• VC-4 (Trail Termination Point)A VC-4 TTP represents both the creation and termination of a VC-4 path.
– TTPs on PDH levelOn PDH level (see Figure 163. ) a distinction is made between the following TTPs:
• PPI (Trail Termination Point)On the PDH side, an PPITTP corresponds to the ESTTP of the synchronous side. Dependingon the type, it can either display the characteristics of a 140 Mbit/s, a 45MBit/s, a 34 Mbit/s ora 2 Mbit/s port.
• E4 (Trail Termination Point)The E4-TTP represents the creation and/or termination of a 140 Mbit/s connection.
• E3 (Trail Termination Point)The E3-TTP represents the creation and/or termination of a 34 Mbit/s connection.
• E2 (Trail Termination Point)The E2-TTP represents the creation and/or termination of an 8 Mbit/s connection.
• VC-4 (Trail Termination Point)A VC-4 TTP represents both the creation and termination of a VC-4 path.
• VC-3 (Trail Termination Point)A VC-3 TTP represents both the creation and termination of a VC-3 path.
• VC-12 (Trail Termination Point)A VC-12 TTP represents both the creation and termination of a VC-12 path.
– MSP definitionTransmit side, the MSNP (AU4–CTP) input enters two different MSNP/MSN (unProtected CTP)sources and then the MSN–TTP working and protection sources (to insert the K1–K2 bytes) are sentto the own SPI interfaces. Receive side, the working and protection MSN/MSNP outputs (AU4–CTP)enter in the switching selector. The MSNP–TTP terminates the selected signal and checks the SSFand the MSP protocol failure.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
219
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
!����"#����
$����
�������� %�&�����
��'(
���(����
��')
���)����
���*)����
+����
��'( ��'(
��')
��')��')��')
��') ��')
���*)�������*)����
Figure 162. SDH Transport Level Diagram
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
220
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
!�����
%�������
!����� !(����
!)����
%��(����!(����
!*����
%��*)����
!)����
!*����
%��*)����
%��*)����
!*����
�
�
�
�
�
�������������� ��
*�,�+���"� )�+���"�
��-���
(��+���"�
%��(����
�.�+ ��"�
!()&��� !(*&���
Figure 163. PDH Transport Level Diagram
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
221
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.1.4 Mapping Tables: TP Names
The TP names on the 1660SM reflect the software model the user interface is based on. Therefore theydiffer from the TP names given in the ITU-T recommendations. The following tables list the TP namesmapping conventions in the “Transmission” View.
Table 3. PDH TPs
����� �� ��� �� � ���
������ �
�� ��� ����
�� ��� �
�� ��� ����
�� ��� �
�� ��� ����
�� ��� �
�� ��� ����
�� ��� �� ��
�� ��� ��� �������
� ��� ��� �������
�� ��� ��� �������
���� ��� ���
��� ��� ��
����� ��� ����
Table 4. SDH TPs
����� �� ��� �� � ���
����� ���
����� ��
����� ���
���� ��
�� ��
���� ��� ��������
������� ��� �������
���� ��� ���
���� ��!
����� ��!�
��� ��� ��
���� ��� ���
����� ��� ����
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
222
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.1.5 Cross-Connection Types
A cross-connection represents the logical connection between the input and output of the matrix, calledthe matrix port.
The matrix only receives and transmits signals in GTI format. The Generic Transport Interface GTI,Alcatel’s standardized signal format for internal interfaces, is similar to the STM-1 format. The incomingsignals are mapped or converted to GTI format on the plesiochronous and synchronous I/O boards. Thisframe is based on the STM-1 frame specified by ITU-T Recommendation G.707. It enables the transportof all signals in the US hierarchy and ETSI hierarchy levels 1 to 4 (1.5 Mbit/s to 140 Mbit/s) mapped toVirtual Containers (VCs) (see Figure 160. ).
The VCs are sent from the I/O boards to both copies of the Matrix (A and B) via the GTI. The matrixperforms the cross-connection on the VC-4, VC-3, VC-2 or VC-12 level and transfers the VCs to therelevant 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 norouting in reverse direction.
ÀÀÀÀÀÀÀÀÀÀÀÀ
ÈÈÈÈÈÈÈÈÈÈÈÈ
input TP output TP
Figure 164. Unidirectional Connection
15.1.5.2 Bidirectional Connection
Information is transmitted between input port and output port in both directions (point-to-point).
ÀÀÀÀÀÀÀÀ
ÈÈÈÈÈÈÈÈ
input TP output TP
Figure 165. Bidirectional Connection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
223
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.1.5.3 Broadcast Connection (Multi-leg / Multipoint)
In contrast to a cross-connection between just two points (point-to-point), one source and one sink, abroadcast connection consist of one source and several sinks, different ‘legs’ that share the same sourceTP.
In the example below, information is broadcast from one input to outputs A, B and C on three legs.
ÀÀÀÀÀÀÀÀÀÀÀÀ
ÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈ
input TPÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈ
output A
output B
output C
leg 1
leg 2
leg 3
Figure 166. Example of Broadcast Connection with Three Legs
A warning box indicates when the resources available for broadcast connections are exhausted.
N.B. Non-intrusive MonitoringAdding a protection leg to a unidirectional cross-connection offers the ability to performnon-intrusive monitoring on this cross-connection. No errors are introduced to the originalcross-connection with applying or removing the protection leg.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
224
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.1.6 Cross-Connection Protection
15.1.6.1 Protected Unidirectional Connection
A unidirectional connection is routed from Input A to the Output (primary route). In the case of a failure,the system automatically switches to the protection path from protection Input B to the Output. This secondconnection is permanently kept in hot standby operation (see Figure 167. ).
in case of
ÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈ
ÈÈÈÈÈÈÈÈÈÈÈÈprot.
input B
input A
output TP
failure
Figure 167. Protected Unidirectional Connection
15.1.6.2 Protected Bidirectional Connection
A bidirectional connection is routed from Input A to the Output C (primary route). Input A (input protected– see Figure 168. ) can be protected:
ÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈ
ÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈ
A
B
C
in case of failure
Figure 168. Bidirectional Connection – Input Protected
N.B. By means of this connection are created links with SNCP protection.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
225
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.1.6.3 Protected Broadcast Connection
The protected broadcast is realized as a set of independent, protected, unidirectional connections usingthe same pair of input termination points, as illustrated in Figure 169. Each protection can be forced,locked out or switched independently. Therefore, if a failure occurs at a certain input, it is possible that onlysome of the protections of the protected broadcast actually switch to the protection input.
����������
ÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈ
ÈÈÈÈÈÈÈÈÈÈÈÈ����/
�����
����� �
������
�������
ÈÈÈÈÈÈÈÈÈÈÈÈ
������ �
ÈÈÈÈÈÈÈÈÈÈÈÈ
������ �
��� �
��� �
��� �
Figure 169. Protected Broadcast
Figure 169. shows a broadcast connection from input A to outputs A, B and C. Leg 2 and 3 are protectedvia input B, whereas leg 1 is not protected.
In current release only one out of N legs can be protected.
15.1.6.4 Drop and Continue Connection
A Drop and Continue connection is a composed by: (see Figure 170. )
• a unidirectional connection routed from Input A to the Output C and also to Input protecting B.
• a unidirectional connection from Input protecting B to Output C.
• a unidirectional connection from Output C to Input A.
Output C is protected; when receive from Input main the connection is defined normal, when receivefrom Input Protecting main the connection is defined inverse.
All the connections are created in a single step of configuration.
ÈÈÈÈÈÈÈÈÈÈÈÈ
ÈÈÈÈÈÈÈÈÈÈÈÈ
ÈÈÈÈÈÈÈÈÈÈÈÈ
A
Input Pro
Output
t. input
B
C
Figure 170. Drop and Continue – Normal
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
226
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.2 Operative Sequence to execute Cross-Connections
This paragraphs list the complete procedure to realize cross-connection moving among the variousmenus.
Three main cases have been considered:
• an high order signal cross connection (AU4)• an high order concatenated signal cross connection (AU4c)• a low order signal cross connection (example : TU12)
Procedure for high order signal (AU4)
– Select ”Transmission” option from the ”View” menu
– Select ”Transmission” → ”Cross Connection” →”Cross Connection Management”
– Click on ”Create” in the Cross Connection Management windows; a new window called ”Main CrossConnection” is opened.
• Select the correct value in the fields ”Type” and ”Protection”
– Click on ”Choose” relative to the ”Input” field; a new window called ”TP search” is opened.
• On the ”Equipment” field select the Board, in the ”Termination Points” field select the AU4
– Click on ”OK”; the ”TP search” window is closed.
– In the ”Main Cross Connection” window repeat the same on the “Output” field and on the ”Prot. Input”field for protected connections
– Click on ”OK” in the ”Main Cross Connection” window to terminate the creation and subsequentlyclick on ”Cancel” to go to the ”Cross Connection Management” window.
– Click on ”Search” in the ”Cross Connection Management” window to see the new cross–connectioncreated.
Procedure for AU4 concatenated (AU4c)
N.B. Before to create an AU4 concatenated cross–connection is necessary to define that the AU4son a STM–4 or STM–16 board are concatenated as explained in para 11.5 on page 123.
– Select ”Transmission” option from the ”Views” menu
– Select ”Transmission” → ”Cross Connection” → ”Cross Connection Management”
– Click on ”Create” in the Cross Connection Management window; a new window called ”Main CrossConnection” is opened.
• Select the correct value in the fields ”Type” and ”Protection”
– Click on ”Choose” relative to the ”Input” field; a new window called ”TP search” is opened.
• On the ”Equipment” field select the Board, in the ”Termination Points” field select theconcatenated AU4c (syntax example: r01sr1sl24/port#01–#01AU4P–4c )
– Click on ”OK”; the ”TP search” window is closed.
– In the ”Main Cross Connection” window repeat the same on the “Output” field and on the ”Prot. Input”field for protected connections
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
227
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– Click on ”OK” in the ”Main Cross Connection” window to terminate the creation and subsequentlyclick on ”Cancel” to go to the ”Cross Connection Management” window.
– Click on ”Search” in the ”Cross Connection Management” window to see the new cross–connectioncreated.
Procedure low order signal (example TU12)
– Select ”Transmission” option from the ”View” menu
– Select ”Transmission” →”Add TP”; a new window called ”Tp search” is opened.
• On the ”Equipment” field select the Board, In the ”Termination Points” field select the AU4 andclick on ”OK”;In the transmission window the AU4 block is displayed;
– Select ”Transmission” → ”Terminate TP” ; a cross is displayed on the AU4 block
– Click twice on the AU4 block and on the VC4 block that appears, then selecting the showed TUG3
– Select ”Transmission” → ”Structure TPs” → then selecting the structure
N.B. The AU4 is then terminated on a VC4 of the MATRIX unit.The VC4 is automatically choosed and indicated as “port # n”, where “n” is the VC4number.This connection will appear on the Cross Connection Management view in a independentline.
– If TU12 (example) are selected, in the transmission window clicking twice on the TUG3 and TUG2blocks the TU12 are displayed
– Select the TU12 to be used
– Select ”Transmission” → ”Cross Connection” → ”Cross Connection Management”; a new windowcalled ”Cross Connection Management” is opened.
– In the ”Cross Connection Management” window click on ”Create” button; a new window called ”MainCross Connection” is opened.
• Select the correct value in the fields ”Type” and ”Protection”
– Click on ”Choose” relative to the ”Input” field; a new window called ”TP search” is opened.
• On the ”Equipment” field select the Board, In the ”Termination Points” field select the structuredTP (example: TU12 1.1.1)
– Click on ”OK”; the ”TP search” window is closed.
– Repeat the same on the “Output” field and on the ”Prot. Input” field for protected connections
– Click on ”OK” in the ”Main Cross Connection” window to terminate the creation and subsequentlyclick on ”Cancel” to go to the ”Cross Connection Management” window.
– Click on ”Search” in the ”Cross Connection Management” window to see the new cross–connectioncreated.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
228
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.3 Cross-Connections management
A list of cross-connections can be displayed in the Cross-Connection Management dialog (seeFigure 173. on page 232). The dialog can be accessed via the Transmission or Port view or viaConfiguration menu as indicated in Figure 171.
Transmission view is presented with the View → Transmission pull down menu.
Port view is presented with the View → Equipment pull down menu, then clicking on the presentedobjects with the sequence board>port.
Figure 171. Cross connection management cascade menu
The Cross-Connection Management dialog is initially empty (see Figure 172. on page 230).
A list of cross-connections is displayed in the Cross-Connection Management dialog after selecting theSearch 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 existingcross-connections,
– enter Search Criteria (one or more) and then press the Search button to display a selection ofcross-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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
229
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.3.1 Search Criteria
– Name (not supported in current release)
Number of the cross–connection (automatically assigned)
– ACD (not supported in current release)
Enter the Access Control Domain of the relevant cross-connections: E= connection made with1353SH, M= connection made with 1354RM, empty= connection made with CT.This filter option can only be used, if at least one ACD is defined on the NE and one or morecross-connections are assigned to this ACD(s).
– TypeSelect the connection type:
• Unidirectional• Bidirectional• Multipoint• Drop&Continue
– ProtectionSelect protection functionality:
• Protected• Not protected
– TP ClassSelect one of the TP types involved in the requested cross-connection.
– StateSelect the connection state:• Activated• Deactivated (not operative in current release, the connection state is always Activated)
– Prot. StateSelect the protection state (for more detailed information, refer to Chapter 9.5):• Forced to Input• Forced to Protecting• Manual Switch to Input• Manual Switch to Protecting• Auto. Switch to Input• Auto. Switch to Protecting• Lockout• Normal I• Normal P
– TP ID PrefixEnter the TP type and physical location of the port, or only the physical location at least down to boardlevel, according to the following format:r<rack#>s<subr.#>b<board#>/port#<port#>-TP (see Figure 173. on page 232)The # within brackets identifies a number.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
230
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 172. Cross-Connection Management Dialog (Initial State)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
231
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.3.2 Cross-Connection List
After a successful search, a read only list of cross-connections matching the search criteria appears(see Figure 173. ). The number of matching cross-connections is displayed in the upper left corner of thelist. The list contains information concerning the following parameters for each cross-connection:
– Prot. Statedetailed 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 iscurrently located. The reason for the automatic switch was Signal Degrade in the Protecting input.The switch was completed.
– Stateconnection 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)
– Inputsignal source; contains the TP type and physical location of the port according to the format<rack#>–<subr.#>–<board#>–<port#>,<port#>#TP (see Figure 173. on page 232)The # within brackets identifies a number.
– Protecting Inputprotecting source (for protected cross-connections only); contains the TP type and physical locationof the port according to the formatr<rack#>s<subr.#>b<board#>/port#<port#>-TP (see Figure 173. on page 232)The # within brackets identifies a number.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
232
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– Outputsignal destinationfor point-to-point cross-connections, the TP ID of the destination is specified according to the formatr<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. Beforestarting 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 firstcross-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 whilemoving 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 theuser has to confirm the requested action.
Figure 173. Cross-Connection Management Dialog (After Search)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
233
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.3.3 Actions available
The following actions are available:
– Create a cross–connection (see chapter 15.4 on page 234)
The Main Cross-Connection dialog (see Figure 177. on page 241) is opened.
– Modify a Cross-Connection (see chapter 15.4 on page 234)Available if just one cross-connection is selected from the list. The Main Cross-Connection dialog(see Figure 177. on page 241) is opened.
– Activate a Cross-Connection (see chapter 15.5 on page 249)Available if at least one cross-connection is selected from the list. Not operative in current release.
– Deactivate a Cross-Connection (see chapter 15.5 on page 249)Available if at least one cross-connection is selected from the list. Not operative in current release.
– Delete a Cross-Connection (see chapter 15.5 on page 249)Available if at least one cross-connection is selected from the list.
– Split a Cross-Connection (see paragraph 15.6.1 on page 252)Available if at least one bidirectional cross connection is selected from the list.
– Join Cross-Connections (see paragraph 15.6.2 on page 252)Available if two cross connections are selected.
– Protection Switching (see chapter 15.7 on page 253)Available if exactly one protected cross-connection is selected from the list. The Protection Actionsdialog is opened.
– Print (see chapter 15.8 on page 255)Prints the filtered list of cross-connections.
The dialog has to be closed explicitly.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
234
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.4 Create/Modify Cross-Connections
Creation and modification of cross-connections are performed in the Main Cross-Connection dialog. Thedialog can be accessed via the Transmission or Port view as for the following menus example or by usingthe Create or Modify buttons (chapter 15.3.3 on page 233) in the Cross-Connection Managementdialog (see Figure 172. on page 230).
The dialog box of Figure 177. on page 241 is presented ( “Main Cross Connection” view).
To prevent operation faults, the system is designed according to the following guidelines:
– All operations that may affect traffic must be confirmed. The subsystem provides a confirmationdialog box before the operation can be executed.
– If the window displays an existing cross-connection, the OK button is insensitive when thiscross-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 canbe used (not assigned to NML and assigned to the user profile) after the OK button is pressed. If aspecified TP is not permitted, the corresponding message box appears.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
235
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.4.1 Cross-Connection Parameters
The “Main Cross Connection” view of Figure 177. on page 241 permits to create the cross connections.
A cross-connection is defined through a set of parameters which depend on the connection and protectiontype. Only those parameters which are permitted within the current context can be accessed. All othersare disabled (faded gray).
To create a cross-connection, one or more of those parameters must be defined according to thecross-connection type. Table 5. gives an overview about the optional and mandatory input parameters forthe various cross-connection types. Activate the relevant entry boxes first of all by clicking on them withthe mouse.
Configurable Parameters
– TypeSelect the connection type:• Unidirectional• Bidirectional• Drop&Continue
– D&C TopologySelect the direction for Drop&Continue:• Normal• Inverse
– ProtectionDefine protection state:• Protected• Not Protected
– Prot. Criteria (only available for protected connections)
Clicking on the Prot. Criteria button, Figure 174. for the Protection Criteria dialog is opened, wherethe user can display and configure the SNCP Type Protection. No protection criteria for automaticprotection switching can be configured.
The following SNCP Type are available:
• SNCP–I (Inherently monitored Sub–Network Connection Protection)
• SNCP–N (Non–intrusively monitored Sub–Network Connection Protection)
• SNCP–S (Sub–layer Sub–Network Connection Protection) (Not operative in current release)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
236
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 174. Protection Criteria
– Revertive (available only for protected connections)Select whether protection is to be revertive or not.In Revertive mode, a protected service is switched back to its initial, protected element when the faulthas been eliminated.When Revertive mode is active, the Wait To Restore protection period prevents several protectionswitches being initiated as a result of an intermittent failure. The protected element must be error-freeduring this defined period of time before a protected service is switched back to it.In the current release the Wait To Restore time period is fixed to 5 minutes.In Non-revertive mode, switchover to the protecting element is maintained even after the fault hasbeen eliminated.
– HOT (available only for protected connections) Not operative in current releaseTo enter the Hold Off Time expressed in msec. HOT is the time between declaration of SignalDegrade or Signal Fail, and the initialization of the protection switching algorithm.
– InputTo enter the input TP, click the relevant Choose button and select the TP in the TP Search dialog(see Figure 136. on page 180). Otherwise, select the input field and enter the name of the TP directly.
– Prot. InputTo enter the protecting TP, click the relevant Choose button and select the TP in the TP Searchdialog. Otherwise, select the input field and enter the name of the TP directly.
– OutputIt 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 describedpreviously and press button Add afterwards. The previously chosen TP is then moved to the list boxlocated 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 destinationTP. 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
237
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
N.B. Non-intrusive MonitoringAdding a protection leg to a unidirectional cross-connection offers the ability to performnon-intrusive monitoring on this cross-connection. No errors are introduced to the originalcross-connection with applying or removing the protection leg.
Table 5. Optional and Mandatory Configurable Parameters for Cross-Connection Creation
���� � ������
������������ ������������� � ����� ����������
��� �� �� ����� ����������
������������
��������� ������������
���������
���� ������������"����������� ������������
12� �������� ������"��3���� & &
��������� ��� ������� ������� ��� ������� �������
�����������������
& ����&-
����&�
& ����&-
����&�
4#� 5����������3�6
& 7 & 7
������� & & & &
$�3����3� & 7 & &
-���� ��� �� ��� �� ��� �� ��� ��
��������� -���� & ��� �� & ��� ��
#����� ��� �� ��� �� ��� �� �������
��� �� �������
& ��� �3�������7 ������������ ��������
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
238
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Non-configurable Parameters
– CC Topology
The topology of the cross-connection is indicated via two icons. The left-hand icon displays thecurrent topology and the right one displays a view of the topology following confirmation of the currentmodifications.
In addition, the color of an icon indicates the connection state of the cross-connection:
green –> active
brown –> inactive
The icon is set according to the entries made in Type and Protection:
TPs not cross-connected
Unidirectional, not protected
Bidirectional, not protected
Unidirectional, protected
Bidirectional, protected
Broadcast, not protected
Broadcast with one protected leg
Drop & Continue normal
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
239
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Drop & Continue inverse
Loopback connection:unidirectional, same input and output TP
Figure 175. Cross-Connection Icons
current state:TPs are not connected
state after creation:unidirectional, non-protected cross-connection
Example:
Figure 176. Creation of a Unidirectional, Non-Protected Cross-Connection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
240
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.4.2 Create a Cross-Connection
This chapter lists the steps the user has to take to create a cross-connection using The “Main CrossConnection” view of Figure 177. on page 241.
For a detailed description of the single parameters, refer to the previous para. 15.4.1 on page 235.
For information on cross-connection types, refer to para. 15.1.5 on page 222.
N.B. After creation of a cross-connection, the cross-connection list in the Cross ConnectionManagement dialog is not automatically updated. Use button Search in this dialog to updatethe list.
Create a Point-to-Point Cross-Connection (uni- or bidirectional)
1 ) Select the cross-connection Type.
2 ) Select the Protection state.
3 ) Select or type in the Input TP.
To enter the TP, click the Choose button and select the TP in the Search for Cross ConnectionInput dialog (see Figure 178. ), 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 todifferent filter criteria. E.g. to obtain a list of all not connected AU-4 TPs of a rack, first select therack 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 theinput TPs in the list and confirm with Ok.
For a more detailed description on the Search for Cross Connection dialog see para. 14.5.1on page 179.
4 ) Select or type in the Output TP as described in Step 3 ).
The following steps only apply to protected cross-connections:
5 ) Select or type in the Protecting Input (Prot. Input) TP as described in Step 3 ).
6 ) Configure the Revertive mode.
7 ) Configure the Protection Criteria (Prot. Criteria)
8 ) The HOT (Hold Off TIme) is not operative in current release
Press the button Ok to confirm the creation.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
241
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 177. Create a Bidirectional Protected Cross-Connection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
242
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Create a Broadcast Connection
1 ) Select the cross-connection Type “unidirectional”
2 ) Select the Protection state.
3 ) Select or type in the Input TP.
To enter the TP, click the Choose button and select the TP in the Search for Cross ConnectionInput dialog (see Figure 178. ) or select the input field and enter the name of the TP directly.
This dialog offers the possibility to list TPs according to different filter criteria. E.g. to obtain alist of all TU12 TPs of a board, first select the board in the left list box, then select the filter criteriaConnection State “Ignore” and Class “TU12” and click on button Search TPs. The matchingTPs are listed in the right listbox (see Figure 178. ). Select the input TPs in the list and confirmwith Ok.
For a more detailed description on the Search for Cross Connection dialog see para. 14.5.1on page 179.
4 ) Select or type in the Output TPs as described in Step 3 )
Press the button Add Leg in the Main Cross Connection dialog and all output TPs are displayedin the list box under the Output field (Figure 179. on page 244).
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 broadcasthas to be assigned to the same protecting input.
Proceed as described in Step 3 ). Afterwards, select the protected output TP in the output list boxand click button Protect Leg. The leg is then marked as “protected” in the list box. Repeat thisprocedure 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 Legbutton.
Examples are in Figure 179. and Figure 180.
6 ) Configure the Revertive mode.
7 ) Configure the Protection Criteria (Prot. Criteria)
8 ) The HOT (Hold Off TIme) is not operative in current release
Press the button Ok to confirm creation.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
243
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 178. Search for Cross-Connection Output
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
244
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 179. Create an Unprotected Broadcast Cross-Connection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
245
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 180. Create a Protected Broadcast Cross-Connection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
246
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.4.3 Modify a Cross-Connection
When modifying a cross-connection, note that some of the transformations involved may affect traffic(because the system may have to destroy and re-create the cross-connection to perform the necessarytransformation). As mentioned at the beginning of this chapter, the user is required to confirm operationsaffecting traffic, i.e. a confirmation window warns the user.
Within the Main Cross Connection dialog, modification of a cross-connection is restricted to theprotection state and the parameters required by the protection. Refer to Table 6. for an overview of theaccessible parameter when the protection state has been changed from “not protected” to “protected” andvice versa. For a description of the parameters, please refer to the previous para. 15.4.1 on page 235.
To modify a cross connection select one from the connection list of Figure 173. on page 232. and then clickon the Modify button.
N.B. After modification of a cross-connection, the cross-connection list in the Cross ConnectionManagement dialog is not automatically updated. Use button Search in this dialog to updatethe list.
Table 6. Modifiable Parameters
��� � � ������ ������� ����
��� �������� ����������
�������� �� �����������
���� & &
12� �������� ������"��3����
������"��3����
��������� ������� ��� �������
��������� �������� 7 &
��������� & 7
������� 7 &
$�3����3� 7 &
-���� 7 7
��������� -���� 7 &
#����� 7 7
& ��� ��������7 ��������
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
247
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The following few facts should be taken into consideration when modifying connections.
– Unprotect a protected cross-connection (see Figure 181. ):
When a protected cross-connection is being unprotected (protection changed to “not protected”), thedialog 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 TPis selected (i.e. check the protection state in the Cross-Connection Management dialog).
An example is in the following Figure 181.
In addition, a question box appears, asking the user to confirm the unprotect action.
Figure 181. Unprotect a Bidirectional Cross-Connection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
248
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– Protect an unprotected cross-connection:
When an unprotected cross-connection is being protected, the Prot. Input button is available toselect the protection input connection to insert.
An example is in the following Figure 182.
Protection principle are given in para. 15.1.6 on page 224.
Figure 182. Protect one Leg of a Broadcast Connection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
249
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.5 Activate/Deactivate/Delete Cross-Connections
15.5.1 Activate a Cross-Connection
Not supported in current release.
The Cross Connection Management dialog provides the possibility of displaying a selection of existingcross-connections (see Chapter 15.3 on page 228). The connection state (Act = A or D) is indicated in thisconnection list.
To activate a cross-connection, select one from the connection list (see Figure 173. ) and then click on theActivate button to initiate the process. A confirmation box appears in which to confirm the state changerequest. The connection in the list is automatically updated to indicate the new connection state (Act = A).
If the set of cross-connections selected from the list includes both activated and deactivatedcross-connections, clicking the Activate button only initiates actions on the deactivatedcross-connections which were selected.
15.5.2 Deactivate a Cross-Connection
Not supported in current release.
After creation, a cross-connection is automatically in an active state. To deactivate a cross-connection,select one from the connection list (see Figure 173. ) and then click on the Deactivate button to initiatethe process. A confirmation box appears in which to confirm the state change request. The connectionin the list is automatically updated to indicate the new connection state (Act = D).
If the set of cross-connections selected from the list includes both activated and deactivatedcross-connections, clicking the Deactivate button only initiates actions on the activatedcross-connections which were selected.
15.5.3 Delete a Cross-Connection
Only deactivated cross-connections should be deleted. However, deletion of active cross-connections ispossible.
To delete a cross-connection, select the corresponding connection from the list and click on the Deletebutton. To prevent operation errors, the user must confirm the deletion request.
The deleted cross-connection automatically disappears from the connection list when the operation issuccessful.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
250
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.6 Split and Join Cross-Connections
15.6.1 Split a Cross-Connection
Precondition
Only bidirectional cross-connections can be split.
Split
Select one or more bidirectional cross connections from the list in the Cross Connection Managementdialog and press Split. The cross-connections are split without further confirmation from the user.
The original cross connection(s) disappear from the list in the Cross Connection Management dialogafter a successful action. The user has to press Search to see the new cross connections.
Depending on the protection state of the original cross-connection, the split action has the following effect:
a ) Unprotected Cross-Connection
An unprotected bidirectional cross-connection is split into two unidirectional cross-connections withthe input TP in one of them being the output in the other and vice versa (see Figure 183. ).
The new cross connection has the same name and activation status as the old bidirectional one.
ÀÀÀÀÀÀÀÀÀ
ÀÀÀÀÀÀÀÀÀ
�
ÀÀÀÀÀÀÀÀÀ
ÀÀÀÀÀÀÀÀÀ
� ÀÀÀÀÀÀÀÀÀÀÀÀ
ÀÀÀÀÀÀÀÀÀ
�
�����8���5��� *6
Figure 183. Split/Join Unprotected Bidirectional Cross-Connection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
251
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
b ) Protected Cross-Connection
Splitting a protected connection results in one protected unidirectional cross-connection and onebroadcast 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 theoriginal protected cross-connection.
ÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈ
ÈÈÈÈÈÈÈÈÈ
�
�
ÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈ
ÈÈÈÈÈÈÈÈÈÈÈÈ
�
�
ÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈÈ
ÈÈÈÈÈÈÈÈÈÈÈÈ
�
�
�����
������� ������������ ������������� ������� ��������
8���5��� )6
Figure 184. Split/Join to Protected Bidirectional Cross-Connection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
252
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.6.2 Join Two Cross-Connections
Precondition
Two cross-connections can be joined if they match the following characteristics:
– The connections are either
1 ) both unprotected, unidirectional and the input is the output of the other one, or
2 ) one of them is protected and unidirectional, and the other one a broadcast with two legs.Restriction: the input of the broadcast connection has to be the output of the protectedconnection and the legs of the broadcast match the input and the protection input of theunidirectional connection, also refer to Chapter Split a Cross-Connection, effect b).
– Both cross-connections have the same connection state (activated or deactivated).
– Both cross-connections have the operational state “enabled”, i.e. they are listed in black color in theCross Connection Management dialog.
Join
Select exactly two cross connections in the Cross Connection Management dialog and press the Joinbutton. 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 dialogafter a successful action. Press Search to see the new cross-connections in the list.
The result is either a bidirectional (case 1, see Figure 183. ) or a protected bidirectional (case 2, seeFigure 184. ) cross-connection.
If the original cross-connections have different names, the new name is a concatenation of the names ofboth of them.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
253
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.7 Protection Switching
The Protection Actions dialog is displayed after clicking on the Protection button in the CrossConnection Management dialog (see Figure 173. ).
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 parameteris set to “protected”).
The three protection actions Force, Lock Out and Manual Switch belong to different levels, wherebyLock 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. ForceTo Protecting can be reverted with Release but not with Manual Switch To Input.
Figure 185. Protection Actions Dialog
The dialog window enables the user to perform protection- related operations on protectedcross-connections. These are:
– Force to Input (not operative in current release)
The cross-connection is switched to the protected input regardless of signal quality. Automaticprotection is disabled.
– Force to Protecting (Input)
The cross-connection is switched to the protecting input regardless of signal quality. Automaticprotection is disabled.
– Release Force
Forced switching is disabled and automatic protection switching re-enabled.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
254
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– Manual Switch to Input (not operative in current release)
The user can switch over to the protected input manually. Switching over is not executed if the signalquality on the protected path is worse than on the protecting path.
– Manual Switch to Protecting Input (not operative in current release)
The user can switch over to the protecting input manually. Switching over is not executed if the signalquality on the protecting path is worse than on the protected path.
– Release Manual Switch (not operative in current release)
A manual switch is disabled and automatic protection switching re-enabled.
– Lock Out to Invoke
The connection path is locked for protection switching, i.e. neither forced nor manual switching canbe performed.
– Release Lock
The protection lock is disabled.
N.B. All the operations listed are context-dependent and are enabled or disabled (“grayed”)accordingly.
After completion of protection switching, the list entry in the Cross Connection Management dialog isupdated automatically.
After clicking on an action button and completing the action initiated, the dialog disappears automatically.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
255
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.8 Print
This option is used to print the currently filtered cross-connection list and the related filter settings on thedefault printer or to a file in postscript or ASCII format (see Figure 186. and Figure 187. )
Figure 186. Select Printer
N.B. If no printer is installed, there is no error message displayed to indicate this.
Figure 187. Select Output Format
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
256
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
15.9 Show Cross-Connected TPs
An overview of signal flow can be requested by means of a user action. The user can select a TP andinitiate the action Show Cross Connected TPs from the Transmission view.
The result is that all other TPs connected to the currently selected TP are displayed (see the example ofFigure 188. on page 257). 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 areabove the TU12CTP) enables all the related TPs to be added to the view so that the complete signal flowcan be illustrated.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
257
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 188. Show Cross Connected VC4 of an AU4
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
258
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
259
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
16 OVERHEAD MANAGEMENT
16.1 Introduction
The purpose of this set of dialogs is to handle the operations on the Overhead (OH) bytes of the NE.
The possible operations are:
• Overhead cross–connection
– Cross–connection between 2 or more OH bytes– Termination of an OH byte onto an auxiliary port or vocal channel– Total Pass–through of the MSOH bytes for some cards– Definition of the Phone Parameters
There is a TP associated to every OH byte and to every auxiliary port, so TP could be used instead ofOH bytes or auxiliary port, depending on the context.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
260
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
16.2 OH Connection overview
Here are described the possible OH connections
For OH Phone Parameters directly refer to the para 16.7 on page 268.
– OH Cross–connection
The operator has to be able to cross–connect 2 or more OH bytes on 2 different boards.
The possible cross–connection types are:• unprotected bidirectional point to point
The steps an operator has to do in order to perform the cross–connection are the following:
• create the OH TPs involved in the operation• create the OH cross–connection:
– select type of cross–connection– select the input OH TP involved in the operation– select the output OH TP involved in the operation
After having deleted an OH cross–connection, the involved TPs have to be deleted.
– OH Termination
The operator has to be able to terminate one OH byte onto an auxiliary port or vocal channel.
The steps an operator has to do in order to perform the OH bytes termination are the following:• create the OH TP involved in the operation• create the OH byte termination:
– select the created OH TP– select the auxiliary port/vocal channel TP involved in the operation
After having deleted an OH byte termination, the involved TP have to be deleted.
– Total MSOH Pass–through
For STM ports it make sense to allow the operator to perform a total pass–through of the MSOH bytes.A total msoh pass–through connection (connection between msPassThroughCTP points) is set–up onlyif no single msoh pass–through connection are set and if no single msoh cross–connection are set. If atotal msoh pass–through connection is set, a single msoh pass–through connection or a single msohcross–connection cannot be set.
The steps an operator has to do in order to perform the total MSOH pass–through are the following:• create the msPassThroughCTP points involved in the operation• create the total MSOH pass–through:
– select the input msPassThroughCTP point involved in the operation– select the output msPassThroughCTP point involved in the operation
After having deleted a total MSOH pass–through, the involved msPassThroughCTP points have to bedeleted.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
261
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
16.3 Overhead views
The Overhead Views allows to perform the previously presented operations.
To access select Overhead option from the Configuration pull down menu; the following options arepresented in the cascading menu, as shown in the following figure:
• OH Cross Connection See next para.
• OH Phone Parameters See para.16.7 on page 268.
• OH TP creation See para.16.5 on page 266.
• OH TP deleting See para.16.6 on page 267.
Figure 189. Overhead options
The options are described in next paragraphs.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
262
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
16.4 OH Cross Connection
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menuthe OH Cross Connection option.The Cross-Connection Management for OverHead dialog opens (see Figure 190. on page 262 ) andallows to start the configuration.
Figure 190. Cross Connection Management for OverHead dialog
It is similar to the dialog used for the cross–connection of the TP for paths, then the samedescription and functions are valid.Next configuration steps use the Main Cross-Connection for OverHead (see Figure 191. on page 262)dialog and the TP Search dialog (see Figure 136. on page 180), also in this case already described forpath management.
Figure 191. Main Cross-Connection for OverHead dialog
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
263
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
For all details, navigation and sequences on these views refer to chapter 15 on page 213.
There is one big difference between the OH TPs and the other kinds of TPs: the OH TPs have to be:• created ONLY BEFORE a cross–connection/termination operation involving them has been
performed.• deleted AFTER a cross–connection/termination deleting involving them has been confirmed.
The current implementation of the TP Search Dialog (TPSD) works only with created TPs.In the following a description of the main functions and commands is given, also to list the Supported andNot Supported operation.
16.4.1 Cross-Connection Management for OverHead dialog
See Figure 190. on page 262
– Supported operations
• Search cross connections/terminations according to one or more of the following filteringattributes: type, TPs . The operator can set the filtering criteria, can start the search and selectone or more cross connections/terminations among those presented in a read–only list as aresult of the search operation. For each crossconnection/termination matching the filteringcriteria, the following information is shown: direction (bidirectional) and the input, output TPsinvolved;
After choosing one or more cross connections/terminations, this dialog allows to:
• Delete the selected xconnection/termination
Note: this dialog disappears only when the user explicitly clicks on the close button.
Delete operations can be performed on several cross connections/termination at the same time.Modify operations can be performed only on single cross connections/terminations.The OH xconnections are automatically active at the moment of their creation.
The operation buttons availability follows some rules:
• The Delete and Print buttons are enabled only if at least one item is selected from the list.A special dialog will ask the user for a confirmation.
• the 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 confirmationdialog must be answered to carry on/cancel the operation. The choices for this dialog are: yes/no forsingle items, yes to all/cancel for multiple items
– Not Supported operation
When used for OH purposes, the Cross-Connection Management dialog doesn’t support the followingfunctionalities:
• Protect cross connections/terminations: all the OH cross connections/terminations areunprotected
• Activate/Deactivate cross connections/terminations: all the OH crossconnections/terminations are automatically active since their creation
• Split cross connection/termination
• Modify Cross Connection Termination
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
264
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
16.4.1.1 Main Cross-Connection for OverHead dialog
See Figure 191. on page 262.
According to the philosophy of offering only meaningful operations to the user, and being the OHcrossconnection operations a subset of those applying to the general cross connections (e.g:protectionsare 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 theoperations hereafter listed:
• selection of the cross–connection type
• selection of the input TP involved in the cross–connection
• selection of the output TP involved in the cross–connection
In order to do that the operator can either type in the involved TPs ID or use the TP Search dialog.
– Supported operations
• When creating a new cross connection, some or all of the following operations are available,depending on the NE type characteristics:
– Choose one input TP
– Choose one output TP
It is possible to directly type in the TP name or to click on the Choose button to select aTP from the TP Search dialog box
16.4.1.2 TP Search dialog
The TP Search dialog (see Figure 136. on page 180) currently offers:
• navigation rack/subrack/board/port
• a list of TPs to choose from
When used in the OH domain, this dialog is a subcase of the most generic TP Search.
The operator can choose among a list of:
• all the possible OH TPs belonging to a specified class: no board selected and MS, RS or VCclass selected
• all the possible OH TPs belonging to a specified board/port: board/port selected and no TPclass selected
• all the possible OH TPs belonging to a specified board/port and class: board/port selected andMS, RS or VC class selected
• all the OH TPs already connected (also accordingly to the connection type)
• all the OH TPs not yet connected
• a combination of the above options
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
265
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
In this Network Element to connect the auxiliary / vocal channels and the Overhead bytes thefollowing operative indication must be observed:
– the auxiliary and vocal channels TPs are in the SERVICE board of slot 11
The auxiliary channels are:
• 2 x G.703 2 Mbit/s; in the screen are indicated as:
– r01sr1sl11/port#05–PExpanding this TP, 31 referred TPs are presented
– r01sr1sl11/port#06–PExpanding this TP, 31 referred TPs are presented
• 4 x G.703 64Kbit/s; in the screen are indicated as:
– r01sr1sl11/port#07–P– r01sr1sl11/port#08–P– r01sr1sl11/port#09–P– r01sr1sl11/port#10–P
• 4 x V11; in the screen are indicated as:
– r01sr1sl11/port#01–#01–v11TTP– r01sr1sl11/port#02–#01–v11TTP– r01sr1sl11/port#03–#01–v11TTP– r01sr1sl11/port#04–#01–v11TTP
• 4 x V24; in the screen are indicated as:
– r01sr1sl11/port#01–#01–v24TTP– r01sr1sl11/port#02–#01–v24TTP– r01sr1sl11/port#03–#01–v24TTP– r01sr1sl11/port#04–#01–v24TTP
• 1 x phonic interface (voice channel); in the screen are indicated as:
– r01sr1sl11/port#01–#01–q23TTPExpanding this TP, four referred TPs are presented:• r01sr1sl11/port#01–#001–q23TTP• r01sr1sl11/port#01–#002–q23TTP• r01sr1sl11/port#01–#003–q23TTP• r01sr1sl11/port#01–#004–q23TTP
These TPs permit to connect the voice channel toward four directions.
– The other boards used to terminate or cross–connect the OH bytes are the STM–n boards.The OH TP are present in MS, RS and VC4 TP Class.In these TPs the indication “......#0011 to 0099 (MS or RS) are referred to the coordinates of theSection 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 forNational 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
266
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
16.5 OH TP creation
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menuthe OH TP creation option.The OH TP creation dialog opens (see Figure 192. ) and allows to create the OH TP to cross connect.
In detail, the dialog–box contains the following graphical object:
– a Choose button is used to display a list of OH Tps to be created. The Choose button startsthe TP Search (see Figure 193. ) with predefined filtering; the TP Search dialog allows theoperator to visualize only not created OH Tps.To visualize the OH TP in the TP Search view double click on the MS, RS or VC4 Tp.
– OH Tp field displays the label of the selected OH Tp to be created.
Apply button is used to perform a create request of the tp displayed in the OH Tp field. After havingperformed the create request, the OH Tp field is set to empty.Close button close the dialog without changes of the data.Help button provides some useful information about the dialog.
Figure 192. OH TP creation
Figure 193. OH Search TP for creation
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
267
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
16.6 OH TP deleting
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menuthe OH TP deleting option.The OH TP deleting dialog opens (see Figure 194. ) and allows to delete the OH TP no more involvedin an OH cross–connection.
In detail, the dialog–box contains the following graphical object:
– a Choose button is used to display a list of OH Tps to be deleted. The Choose button startsthe TP Search with predefined filtering; the TP Search dialog allows the operator to visualizeonly created and not cross–connected OH Tps.
– OH Tp field displays the label of the selected OH Tp to be deleted.
Apply button is used to perform a delete request of the tp displayed in the OH Tp field. After havingperformed the delete request, the OH Tp field is set to empty.
Close button close the dialog without changes of the data.
Help button provides some useful information about the dialog.
Figure 194. OH TP deleting
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
268
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
16.7 OH Phone Parameters
The OH phone parameters option permits to configure the telephone number and to manage theparameter “phonic extension”.
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menuthe OH Phone Parameters option. Figure 195. opens.
r01sr1sl11/port#01–#01–q23TTP
Figure 195. Phone Parameters dialog window
In the window are presented:
– the interface field (at the top) where can be selected the phonic interfaces to be configured.It identifies a TP indicated as “q23TTP”, referred to the physical voice connection on the SERVICEunit 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.Not operative in current release.
Apply button performs the configuration change of the modified phone parameters of the selected phonicinterface without close the dialog
Close button close the dialog without changes of the data.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
269
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17 PERFORMANCE MONITORING
17.1 Introduction
The Performance Monitoring domain on the NE covers the monitoring of counter values for trailtermination points and connection termination points.
Examples of these counters are Errored Seconds (ES) and Severely Errored Seconds (SES).
The Performance Monitoring domain counts these errors during specified granularity periods (15 min,24h) and stores the values in history data logs.
For the purpose of quality supervision, the values of the error counters can be compared to user-definedthreshold levels. If a counter value has crossed a threshold level, a notification (threshold crossing alarm)is issued.
The principle performance management functions are:
– Configuration of the counting interval for each performance measurement point.
– Collection of the performance data.
– Configuration of the quality thresholds that generate alarms and log records when predefined valuesare exceeded.
17.1.1 Overview
These functionalities are described in the following chapters in addition to general information concerningperformance monitoring on the NE.
– Chapter Configuration deals with the configuration of performance monitoring
– Chapter Display Current Data deals with displaying current performance data
– Chapter Display History Data deals with displaying history performance data
– Chapter PM Threshold Table Selection deals with the selection of threshold tables
– Chapter PM Threshold Table Modification/Display deals with the modification of threshold tablesand permits to display the same
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
270
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17.1.2 Supported Performance Counters
The NE uses performance counters to count transmission errors.
A set of performance counters is provided according to the Termination Point (TP), where performancemeasurement occurs.
The user can start performance monitoring on one or more subsets of counters for each TP; it is notpossible to start individual performance counters.
Near end performance monitoring events are:
– Background Block Error (BBE): A BBE counter measures the number of errored blocks which donot 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, orat 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 theUnavailable Time.
The corresponding Far End (FE) performance monitoring events are:
– Far End Background Block Error (FEBBE): A far end errored block which does not occur as partof an FESES.
– Far End Errored Second (FEES): Identifies, at a terminal, a one second period with one or moreerrored 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 whichcontains > 30% of errored blocks, or at least one Severely Disturbed Period (SDP) which wasreceived/detected by the Far End Terminal. An FESES is counted as an FEES.
– Far End Unavailable Second (FEUAS): An Unavailable Second is a second which is part of theUnavailable 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 pathlayers and for the multiplex section layer. For the regenerator section, no far end information istransmitted 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 terminalthat the far end terminal has detected an incoming failure.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
271
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– Unavailable Time (UAT): A period of unavailable time begins at the onset of 10 consecutive SESevents. These 10 seconds are considered to be part of unavailable time. A new period of availabletime 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 , togetherwith 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 frameevents 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 thiscounter is deprecated by ETSI and will be removed from international standards.
17.1.3 Far End (FE) and Near End (NE) Performance Counting
Far end performance monitoring parameters are derived from Remote Defect Indicators (RDI) andRemote Error Indicators (REI) (refer to Figure 196. ).
far endcounter
far endcounter
near endcounter
RDI insertion
signifi-cant bits
signifi-cant bits
near enddefect
far enddefect
signifi-cant bits
signifi-cant bits
far enddefect
Source
Sink
Sink
Source
Node A Node B
near enddefect
RDI inser-tion
trans-missionsignal
trans-missionsignal
near endcounter
Figure 196. Far End Performance Monitoring Principles
– At Node A, the near end information represents the performance of the unidirectional section/pathfrom B to A, while the far end information represents the performance of the unidirectionalsection/path from A to B.
– At Node B, the near end information represents the performance of the unidirectional section/pathfrom A to B, while the far end information represents the performance of the unidirectionalsection/path from B to A.
Near end performance data at Node A and far end performance data at Node B correspond as long asneither 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 endfailures.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
272
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17.1.4 Bidirectional counting (24 h Bi) for QoS
As specified in G.826, G.784 and ETSI 300417, the bidirectional PM collection for Quality of Service hasbeen supported by combining the information on each direction of transport to assess a singleunavailability state: the bidirectional path is in the unavailable state if either one or both directions are inthe unavailable state.PM data are collected by a single UAS plus two sets of three event counters (BBE,ES,SES) for NE–PMand FE–PM respectively. When the path transports unidirectional payload just the four counters for theNE–PM are activated (BBE, ES, SES and UAS).Data collection is performed only on 24 hours registers and the NE maintains a buffer of two registers: the24hours current registers and the historical one.
17.1.5 End to End (e–e 24h) Performance Counting
VCn trails can be monitored in intermediate node through the activation of performance monitoringprocess on Monitoring function.
As the trails are often responsible of the end–to–end customer service, the end to–end monitoring can berequested to provide monitoring for Quality of Service purposes and , in addition, for network Maintenanceapplications.
If SNCP is configured the Quality of Service collection have to be enable in the monitoring functions afterthe matrix .
End to end monitoring is achieved by activation of Performance monitoring on the two direction of pathand using far–end primitives. This process can be unidirectional (for Monitoring) or bidirectional process(for QoS).
In case of unidirectional process one direction can be monitored end to end and both 15minute and 24h collection can be activated 15min./ 24H FE_BBE, FE–ES, FE–SES, FE–UAS on incoming or egresssignal depending of the POM is enable. The TCA are also evaluated in both 15 minute and 24 H counters.
The bidirectional process needs the presence on the two Monitoring functions in the two directions in oneNE and among the two monitoring function a 24 hour collection can be activated with the collection ofincFE_BBE, incFE–ES, IncFE–SES, UAS, eFE–BBE, eFE–es, eFE–SES.
17.1.6 Performance Monitoring on AU–PJE
AU PJE (Administrative unit point justification event) is an optional parameters request in G.784.
For AU PJE counters , the positive and negative PJE shall be counted separately on one selectable AUwithin an STM–N signal, after the AU has been resynchronized to the local clock. Refer to G.783.
The number of positive and negative outgoing PJE per second are collected in 15 minutes and 24 Hcounters. A history of 16 x 15minutes counters and 2x 24H are stored in the NE for each AU selected.
No Threshold crossing mechanism is supported on AU–PJE counters.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
273
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17.1.7 Tandem Connection Termination (TCT) and Monitoring (TCM)
TCM allows monitoring within the operator domain. The quality within the operator’s own domain can beproven regardless of the received quality of the signal at the entry point of the network. At the input pointthe reference value is set to zero by using the TCM feature.
Tandem Connection Monitoring is applicable to VC–4–nc (n=1, 4, 16, ...), VC–4, VC–3 and VC–12 layers.
TCM provides:
– Incoming error count (IEC);– TC_REI to indicate errored blocks within the TC to the far end;– OEI to indicate errored blocks of the egressing VC–n;– TC_API as access point identifier complying with generic 16–byte string format;– TC_RDI indicating to the far end that defects have been detected within the TC at the near end TC
sink;
17.1.8 Performance Data Collection
Near end and far end performance monitoring events are counted over fixed monitoring periods of 15minutes and 24 hours.
The 24-hour monitoring periods start at 00 : 00 (UTC) and the 15-minute monitoring periods start atxx : 00, xx : 15, xx : 30 and xx : 45.
Performance monitoring can be enabled and disabled at any time during a monitoring period. An entityof all near end or far end performance monitoring events is always counted, it is not possible to startindividual performance counters (e.g. SES only). BBE, ES and SES counting is stopped duringUnavailable Time.
Event Counting
The performance events (e.g. SES) are counted in a counter per event. These counters are called thecurrent registers. At the end of the monitoring period, the contents of the current registers are transferredto the first of the recent registers, together with a time stamp to identify the period (including the day). Timestamping is performed using UTC (as for all alarms). After that, the current register is reset. It is alsopossible to reset an individual current register manually.
Suspect Flag
A suspect interval flag is set as an indication that the data of the corresponding register may be eitherincomplete or invalid.
Zero Suppression
Zero suppression is a basic mechanism to remove irrelevant PM information and to reduce the amountof PM reports in the system. A PM report is suppressed and hence no history record is created by the entitywhich is responsible for PM reporting when all of the following conditions are true for the monitoring period:
– an interval is error-free (all PM counter values are zero)– PM was enabled during the entire monitoring interval (the elapsed time equals its nominal value, i.e.
900 for 15 min. and 86400 for 24 h)– PM was running properly (the suspect interval flag is not set)
By default, zero suppression is active for all PM enabled TPs. The number of suppressed intervals isindicated.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
274
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17.1.9 Data Collection
N.B. PM data is not counted on boards that were plugged out at the moment of enabling datacollection (see PM Configuration dialog). Nevertheless, PM data is counted on boards thatwere plugged in at the moment of enabling data collection, but were plugged out and back insome time during data collection.
Performance Monitoring can be started at any time.
As soon as Performance Monitoring is started on the Craft Terminal, current PM data is collected on theI/O boards, incrementing the performance counters each time an error is detected.The performance data counted is evaluated every quarter of an hour or every 24 hours and stored therein a history record.
When the user disables the monitoring of a TP within the first 10 minutes of a 15-minute period, it ispossible that have still not been received the PM data of the previous monitoring interval.Since PM data is not stored after monitoring is disabled, the PM data of the previous interval is lost in thiscase.
If equipment or line protection switching occurs during a counting interval, the NE does not providecomplete performance measurement for the protected TPs.Only the period between the last switch and the end of the counting window is counted.The interval is marked for suspect data and the elapsed time indicates the length of the measured period.
17.1.10 Performance Monitoring History
Performance Monitoring history data is necessary to assess the recent performance of transmissionsystems. Such information can be used to sectionalize faults and to locate the source of intermittent errors.History data, in the form of performance monitoring event counts, is stored in registers in the NE. All thehistory registers are time stamped.
In compliance with ETSI and ITU-T standards, the history registers operate as follows:
The history data is contained in a stack of registers. There are sixteen 15-minute period registers and one24-hour period registers per monitored event. These registers are called the recent registers. At the endof 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.
17.1.11 Thresholds
For quality supervision purposes, the recorded errors through the performance counters can be comparedto 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 whethercrossing 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 24hours.
The TCA only reports the value of the counter which has crossed the threshold, it does not provide acomplete set of all counters. Therefore, the user has to explicitly retrieve all current performance data afterreceiving the alarm. The user can retrieve this information from the Current Performance ManagementData Dialog.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
275
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Two thresholds mechanism are supported:
– For 24–hour (implicit clearance) monitoring periods, one threshold value is defined: if the event countreaches or exceeds the threshold value during the monitoring period, a TCA is generated. To cleara TCA, the alarm must be manually acknowledged by the user.
– For 15–minute (explicit clearance) monitoring periods, two threshold values (set, reset) are defined:a TCA is generated during the monitoring period when the event count reaches or exceeds the setthreshold value the first time. This TCA is automatically cleared by the system at the end of thefollowing monitoring period in which the event count is less than or equal to the reset threshold valueand there was neither an unavailable nor a suspect period during this monitoring period
The following limitations apply for explicit clearance:
– The value of the low threshold is fixed to “0” (only a single threshold is provided by a threshold table).
– An SES threshold crossing is cleared at the end of the interval if no unavailability was detected andSES 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 lowthreshold had not been reached.
Additionally an explicit clearance of TCAs for all granularity periods is executed if one of the followingevents occurs during the current interval:
– deletion of the current data instance (TP),
– resetting of counters (only for 24 h),
– increased thresholds (higher than current value of counters) (only for 24 h).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
276
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17.2 Configuration
Use menu item Add TP to display a special TP in the Transmission menu (see para.14.5 on page 179).
Select the TP and open the PM Configuration dialog (see Figure 197. ) by clicking on the menu itemConfigure Monitoring.
This “PM Configuration” dialog serves as the main interface to all PM services. Everyconfiguration 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 openingthe same Performance > Configure Monitoring option in the Port pull down menu (see para.11 on page117).
N.B. To configure PM for au4CTPs and tuxCTPs, Path Overhead Monitoring (POM) ,SupervisedUnequipped Termination (SUT, not supported) or Tandem Connection (TCT, TCM) must becreated first (see description in para. 14.10 on page 195 ).
The PM Configuration dialog is designed as a notebook consisting of a text field, to identify the selectedTP, and page labels.
The selected TP is indicated in the first box at the top of the screen: TP Identifier.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
277
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
In case of au4CTP tuxCTPs and VcxCTP, the PM Configuration dialog also contains a cascading menuthat allows to configured the POM/SUT/TC options as follow:
– PathOverhMon After Matrix
– PathOverhMon Before Matrix
– TP (Performance is made on AU–PJE )
– TCM After Matrix
– TCM Before Matrix
– TCT Bidirectional After Matrix
– TCT Bidirectional Before Matrix
When more than one of the above options is chosen, a Question dialog box is displayed (see Figure 198. );click on Cancel to continue or OK to interrupt any action.
N.B. As long as the PM Configuration dialog is open, a modified POM/SUT/TC configuration is notautomatically recognized and displayed. This may lead to rejections or confirmations offorbidden PM configuration. Therefore make sure to reopen the PM Configuration dialog eachtime the POM/SUT/TC configuration is changed.
Each page label presents a range of parameters for one near end or far end granularity period (15 min.or 24 h) which together form a dataset. To select a special page label, click on the top part of the label:
• NE15, near end 15 minutes page
• NE24, near end 24 hours page
• FE15, far end 15 minutes page
• FE24, far end 24 hours page
• 24hBi , near and far end 24 hours page bidirectional (UAS is the sum of far end and near end)
• e–e 24h , end to end 24 hours page (enable only on HPOM)
Each dataset has to be configured independently. For AU–4 CTP and TU–x CTP the highest criteria isPOM 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
278
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 197. PM Configuration Dialog (example)
Figure 198. PM question dialog box (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
279
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Activate any item within the page label by selecting the respective radio button.
– Mode
• Data Collection
Select this button to activate performance monitoring. Disabling Data Collection leads toclearance of the current and all history data of this entity.
• Create History Data
If this item is selected, history data collection is performed in the selected entity for thecorresponding TP.
Note that on disabling this mode item, no history data is available. Nevertheless, datasetscollected prior to deactivation are not cleared and are displayed after re-enabling the item, aslong as the number of displayed datasets does not exceed 16 for 15 min. granularity and onefor 24 hours granularity.
• Lock Data Collection. Not supported
If Lock is selected, PM remains enabled but data collection is stopped. All history performancedata remain available. All current values are set to zero.
– EML OS Monitoring (only accessible from SH)
Not available for Craft Terminal.
– Notifications
• UAT (only available for 24 h granularity)
For 24 h granularity, UAT (UnAvailable Time) notifications are created if enabled. Thisnotification results in an UAT alarm in the Alarm Surveillance.
N.B. This parameter can only be selected during creation and cannot be subsequentlymodified.
• Suppress Additional Threshold
Disabled: the alarm is generated every time the value exceed the upper threshold (value up).
Enabled: after a first alarm generation, the alarm is generated again when the value exceed theupper threshold (value up) after the lower threshold (value down) has been exceeded.
– Threshold Table
Attach a threshold table to the selected TP. Only assign threshold tables that match the granularityperiod 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 PMConfiguration window and the Transmission view.Click on button Attach... to open the PM Threshold Table Select dialog (see Figure 201. ) andconfigure the threshold table (see Chapter 17.5 on page 286).Select button Remove to disassociate the threshold table from the entity.
N.B. A threshold table can only be attached if Data Collection is enabled.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
280
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
– Set Alarm Severity UAT
• ASAP Id
This field shows the label of the ASAP pointer assigned to the UAT alarm
• Set ASAP
Allows to set a new ASAP pointer for the UAT alarm. The Set ASAP button opens the windowdisplayed in Figure 13. on page 47.
Confirm the configuration with the button Apply before closing the dialog. Otherwise the configuration islost.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
281
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17.3 Display Current Data
Use menu item Add TP to display a special TP in the Transmission view (see para.14.5 on page 179).
Select the TP and open the Current PM Data dialog (see Figure 199. ) by clicking on the menu itemDisplay Current Data.
This “Current PM Data” dialog serves to show the results and status of the PerformanceMonitoring counters.It is possible to access the same “Current PM Data” dialog selecting a TP in the “Port view” and openingthe same Performance > Display Current Data option in the Port pull down menu (see para.11 on page117).The Current PM Data dialog is designed as a notebook consisting of a text field, to identify the selectedTP, 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 thatallows to choose the POM/SUT/TC options to display as follow:
– PathOverhMon After Matrix
– PathOverhMon Before Matrix
– TP (Performance is made on AU–PJE )
– TCM After Matrix
– TCM Before Matrix
– TCT Bidirectional After Matrix
– TCT Bidirectional Before Matrix
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
282
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Each page label presents a range of parameters for one “near end and far end” granularity period (15min.or 24h) which together form a dataset. To select a special page label, click on the top part of the label:
• 15 min, near end and far end 15 minutes page• 24 h, near end and far end 24 hours page• 24hBi, far end 24 hours page bidirectional (UAS is the sum of far end and near end)• e–e 24h, end to end 24 hours page (enable only on HPOM)
All datasets available which are related to the selected TP and recorded in the current monitoring intervalare displayed in this dialog.
The following items are indicated for each entity:– Administrative State
Indicates whether the PM collection is locked for the local user or not.– Operational State
Indicates whether PM is enabled or disabled.– Suspect Data
Indicates if collection errors occurred during the collection period.– Threshold Table– Indicates which threshold table is assigned to the entity.– Current Problem List
Indicates current UAT (“Unavailable”) and TCA (“ThresholdCrossed”) alarms.
N.B. The entry “Unavailable ThresholdCrossed” indicates, that both alarms are active. Sincethe text field is too small to display the full text at a time, use the cursor to scroll the textfield in this case.
– Elapsed TimeIndicates the time which has elapsed since the monitoring interval was started. This information tellsthe user whether the data collection covers the whole period.
At the bottom the PM results are listed.
Reset button is used to restart the counting period. Two buttons are present for near–end and far–endperiods.Press the Refresh button to update the window contents and display the latest data.Using the Print button, PM data can be saved to a file or printed on paper.
N.B. If no printer is installed, there is no error message displayed to indicate this.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
283
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 199. Current PM Data Dialog (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
284
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17.4 Display History Data
Use menu item Add TP to display a special TP in the Transmission view (see para.14.5 on page 179).
Select the TP and open the PM History Data dialog (see Figure 200. ) by clicking on the menu itemDisplay 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 openingthe same Performance > Display History Data option in the Port pull down menu (see para.11 on page117).
The PM History Data dialog is designed as a notebook consisting of a text field, to identify the selectedTP, 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 thatallows to choose the POM/SUT/TC options to display as follow:
– PathOverhMon After Matrix
– PathOverhMon Before Matrix
– TP (Performance is made on AU–PJE )
– TCM After Matrix
– TCM Before Matrix
– TCT Bidirectional After Matrix
– TCT Bidirectional Before Matrix
Each page label presents a range of parameters for one “near end and far end” granularity period. To selecta special page label, click on the top part of the label.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
285
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All available datasets (entities), which are related to the selected TP, are displayed in the table:
• 15 min, near end and far end 15 minutes page• 24 h, near end and far end 24 hours page• 24hBi, far end 24 hours page bidirectional (UAS is the sum of far end and near end)• e–e 24h, end to end 24 hours page (enable only on HPOM)
The PM data is displayed containing information concerning:
– Interval End Timein the format dd.mm.yyyy hh:mm:ss.
– The number of recorded events concerning an entity is divided into near end and far end data
– Elapsed Timeindicating whether the data collection was complete (see para. 17.1.9 on page 274)
– suspindicating 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 oldestset in the list is cleared when the next data set arrives.
Using the Print button, PM data can be saved to a file or printed on paper.
N.B. If no printer is installed, there is no error message displayed to indicate this.
Figure 200. PM History Data Dialog (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
286
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17.5 PM THRESHOLD TABLE SELECTION
The PM Threshold Table Select dialog (see Figure 201. ) pops up if the Attach button is clicked in thePM Configuration dialog (see Figure 197. ).
In addition, this dialog can be accessed using the Configuration menu:
N.B. Do not open several dialogs at the same time using both possibilities. Since those dialogs arenot synchronized, they could display different contents.
The dialog presents a list of existing threshold tables.
The tables are individually indicated with a number.
Each table is dedicated to a specific entities, as reported in Table 7. Each table can be modified accordingthe operator selections.
The filtering criteria are not operative.
The user can perform the following actions:
– Create / Modify / Display a threshold table.
– Delete an existing threshold table
Mark the table in the list and click on the Delete button.
Note that a threshold table cannot be deleted if it is attached to a PM entity. An error message informsthe user of this situation.
– Attach the selected threshold table to a TP entity. It is only available entering from the PMConfiguration dialog (see Figure 197. )
The user has to close the dialog explicitly by clicking on the button Close.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
287
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 201. PM Threshold Table Select
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
288
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Table 7. Threshold table entities association
N layer TP’s ASSOCIATED granularity
1 STM16 RS 15 minutes
2 STM16 RS 24 hours
3 STM4 RS 15 minutes
4 STM4 RS 24 hours
5 STM1 RS 15 minutes
6 STM1 RS 24 hours
7 STM16 MS Near End / Far End 15 minutes
8 STM16 MS Near End / Far End 24 minutes
9 STM4 MS Near End / Far End 15 hours
10 STM4 MS Near End / Far End 24 hours
11 STM1 MS Near End / Far End 15 minutes
12 STM1 MS Near End / Far End 24 hours
13 VC4 Path Termination Near End / Far End 15 minutes
14 VC4 Path Termination Near End / Far End 24 hours
15 VC3 Path Termination Near End / Far End 15 minutes
16 VC3 Path Termination Near End / Far End 24 hours
17 VC12 Path Termination Near End / Far End 15 minutes
18 VC12 Path Termination Near End / Far End 24 hours
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
289
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17.6 PM Threshold Table Create / Modification / Display
17.6.1 Creation
The PM Threshold Table Create dialog (see Figure 202. on page 290) pops up when the Create buttonis clicked in the PM Threshold Table Selection dialog (see Figure 201. on page 287).
Carry out the following steps to create a threshold table:
1 ) Enter the table name in input field Name.Leaving the input field blank or entering only blanks is not allowed and rejected.
2 ) Select a Granularity of 15 min. or 24 h for the entity.
3 ) Enter the set (Value Up) and the reset (Value Down) threshold values. Note that the reset valueif supported, will be available with 15 min. monitoring periods.Table 8. on page 291 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 crossedthreshold.
6 ) Confirm the entries with Apply to create the threshold table. A number of threshold tables canbe created from the same window.
Explicitly close the window with button Close.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
290
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 202. Create PM Threshold Table
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
291
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
17.6.2 Modification
The PM Threshold Table Modify dialog (see Figure 203. ) pops up if a threshold table is selected in thePM Threshold Table Selection dialog (see Figure 201. ) 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 8. 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 crossedthreshold.
Note that the Name (really “number”) cannot be changed.
4 ) Confirm the modifications with Apply.
5 ) To modify more than one threshold table, do not close the dialog, but select the next thresholdtable in the PM Threshold Table Selection dialog and press the Modify button(see Figure 201. ).
Explicitly close the dialog with button Close.
17.6.3 Display
The PM Threshold Table Display dialog (similar to Figure 203. ) pops up if a threshold table is selectedin the PM Threshold Table Selection dialog (see Figure 201. ) and the Display button is clicked.
Refer to the previous chapter for a description of the attribute values and types.
Table 8. Maximum Performance Parameter Values
Performance Parameter Max. Value for 15-min.period
Max. Value for 24-h period
BBE, FEBBE on STM-16 34,559,100 3,317,673,600
BBE, FEBBE on STM-4 8,639,100 829,353,600
BBE, FEBBE on STM-1 2,159,100 207,273,600
BBE, FEBBE 539,100 51,753,600
OFS, ES, UAS, FEES, 900 86,400
SES, FESES 810 78,760
PJC high, PJC low 1,800,000 172,800,000
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
292
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 203. Modify PM Threshold Table
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
293
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18 SYNCHRONIZATION MANAGEMENT
18.1 Introduction
All SDH NEs require timing in order to generate the necessary synchronization and frame phase referenceinformation. 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 framestructure.
Follows a brief description of the heart of the NE clock known as the Synchronization Equipment TimingSource (SETS).
It can be divided into 2 parts:
– OSC: the internal oscillator.– SETG: the Synchronization Equipment Timing Generator.
The SETG is responsible for the generation of the external timing source for the Frame structure and theclock, whilst the internal oscillator is useful only in the abnormal functioning ”Free–running” mode that willbe explained later.The simplified figure that follows represents the internal organization of the SETS.
SelectorA
OSC
SETG
SelectorC
SquelchA
SquelchB
T1T2
T3/T6Selector
B
S15 Y
T0
T4/T5
SETS
Figure 204. Internal organization of the SETS.
The internal sources (inputs) are:
– T1: Reference obtained from incoming STM–N signals,– T2: Reference obtained from incoming 2 Mbits signals,– T3/T6: Reference obtained from an external incoming 2.048 MHz (T3) or 2.048 Mbit/s (T6) signal.– OSC: the internal oscillator.
The number of timing reference inputs depends on the configuration of the NE.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
294
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The external sources (outputs) are:
– T0: is the reference output signal for the clock and signal frames,– T4: is the reference output for the external equipment synchronization.– T5: is the 2 Mbit/s reference output for the external equipment synchronization.
Other reference points:
– Y: is used for communication of Synchronization Status Message (SSM) between SETS and MSTfunctional blocks.
– S15: is used to provide notifications and loss of incoming timing reference reporting to theSynchronous Equipment Management Function (SEMF).
Selector A provides the capability to select timing reference from available T1 inputs, either automaticallybased on the priority and quality level of the candidate sources (SSM algorithm), or manual as a result ofcommands issued from the managing system.
Selector B is capable of selecting timing reference from T1, T2, or T3/T6 inputs, according to the SSMalgorithm. 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 timingreference.
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 (Priorityalgorithm) 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 staticinformation. On the other hand, the quality of the source is dynamic information, dependantof the quality of the reference clock generating the timing.In an SDH signal frame, the quality of the timing source is located in the Section Overhead.
The SETG has 3 modes of operation:– Locked mode:
The SETG output is fully controlled by the external timing references (T1, T2 and T3/T6).– Hold–Over mode:
The external timing reference is malfunctioning. The SETG during normal functioning storesregularly the value of the external timing reference. In this case the SETG output is controlled by thismemorized value.
– Free running mode:This is not a normal operating mode. The external timing reference and the memorized timingreference are malfunctioning. In this case the SETG output is controlled by the internal clock source.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
295
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2 Synchronization Management
The operations that can be done on the synchronization sources are the following:
– Timing Source Configuration,– Protection Commands,– T0 Configuration,– T4 Configuration,– SSU Configuration,– Transmitted SSM Quality Configuration,– Frame Mode Configuration (see para. 14.7 on page 191)– Remove Timing Reference,– Change T4<–> T5– Set T0 Equal T4,– Change 2 MHz –> 2 Mbit (available only if T3 has been configured as timing source)– Remove T0 Equal T4,– Show Timing Source.
Before any other operation the synchronization view has to be displayed.
18.2.1 Displaying the Synchronization View
The synchronization view can be normally opened using the menu Views options (see Figure 205. ).
Using menu options, select the Synchronization option from the Views pull down menu as shown in thefollowing figure.
Figure 205. Obtaining the synchronization view.
Selecting this menu option the synchronization representation will be displayed directly into the currentwindow instead of the current view. All the operations that can be done on the synchronization sourcesare performed from this synchronization view.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
296
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.2 Synchronization View
The Synchronization view shows the external timing reference sources and the T0, T4 or T5, generation.The selection is based on the SSM algorithm or on the priority of the incoming timing sources. Activatingthe SSM algorithm implies that the selection of the source is before done on the quality criteria and thenon the priority criteria for sources at the same quality level.
After selecting the Synchronization option from the Views menu the Synchronization View is visualizedin Figure 206.
Figure 206. Synchronization View Example
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
297
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Synchronization View Description
The synchronization view provides two list of allowable timing references:
• one for T0 timing output; T0 list is always present;• one for T4 or T5 timing output; the presence of the T4/T5 list is configurable using resource files.
T0 list contains :
– a timing reference associated to the Internal Oscillator timing source; it is always presentand it cannot be removed or redefined.
– 6 max timing reference for candidate inputs belonging to the allowable timing referenceT1, T2 or T3/T6 configurable by the operator.
T4 list contains :
– 6 timing reference for candidate inputs belonging to the allowable timing reference T1configurable by the operator.
The T0 and T4/T5 lists are used for the management of reference timing source protection; a 1:n protectionlike mechanism is used for the selection of the timing source from T0 (T4/T5) list of the allowable timingreferences, . The protection system chooses the timing reference to generate the output T0 (T4/T5) eitherautomatically, basing on the priority and quality level of the candidate sources according a selectionalgorithm or manually under control of the managing system.
View elements description
Here after, the basic component contained in the synchronization view are described:
• Timing referenceEach 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 timingreference) the following information (if the timing source has been declared by the user):
– the name of the selected timing source– the status of the synchronization source: (lockout, manual switch, force switch, automatic
switch, no request, failure)– the label of the quality level of the timing input source– the priority of the timing input source– 2 small boxes representing the SSF (Los) and DRIFT alarms detected on the timing
source;DRIFT means that the Frequency Offset between the external signal source and theinternal clock is high then the maximum tolerance value.SSF means that the Server Signal Failure is sending a wrong reference signal to the NE.In case of alarm indication the operator can select Show Timing Source ( Figure 223. )to visualize the alarm detail.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
298
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
In the timing reference graphical object associated to the Internal Oscillator the followinginformation are displayed :
– the name of the timing source: Internal Oscillator– a small box representing the LOS alarm; the small box will be lighted up when all the
selected timing source are lost, indicating the Holdover or Free Running operation mode;– a label field representing the abnormal clock operation modes; one of the following strings
can be displayed in the label field:• Holdover, displayed when the clock operates in Holdover mode;• Free Running, displayed when the clock operates in Free Running mode• empty string is displayed when the clock operates in Lock
– a label ”0” representing the priority of the Internal Oscillator
• Selectorssmall ellipse are used to represent respectively:– the selector A;– the selector B;– the selector C;
• Squelch Statusboxes contained a label field are used to represent the squelch statuses T0/T4 and T4. The boxdis plays the configured quality level threshold and it is lighted up when the output timing signalis inhibited.
• Output Signalan arrow and a label field are used to represent respectively:– the output signal T0;– the output signal T4/T5;
• line Typethe following different line type are used to link the output signals and the respective allowabletiming 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 isdrawn when T0 signal is used to generate T4/T5.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
299
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.3 Timing Source Configuration
This functionality allows to configure the input synchronization sources and configure or modify the timingsource priority and quality.
Figure 207. Synchronization Menu
The menu options are greyed according to the current state of the dialogue box that the user can open.
Firstly select a synchronization source reference and after the Synchronization menu to open theSynchronization Option List ( Figure 207. ). Then select the Timing Source Configuration option from thecascading menu, as shown in the above figure.
The following dialogue box is opened.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
300
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 208. Timing source configuration for cross–connect equipments
The Timing source configuration dialogue box displays the extracted quality of the selected timing source.It permits to configure the following timing source information:
– Quality level,– Priority level
Select an empty synch. source reference and click on Timing Source Configuration and then on the InputSource Choice. Figure 209. shows the opened windows.
Following the TP Search procedure described in para.14.5.1 on page 179 ( rack, subrack, board, port )enter the physical board termination point (TP) value; these TP are : EIS for electrical SDH port, OpS foroptical SDH port.
This operation can be repeated for all the available empty synch. sources both for T0 clock and for T4clock.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
301
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 209. Synch. source configuration for ADM equipment
Click on the Input Quality Configuration: the option button opens the option menu to select the desiredquality level.
Timing source may have, in increasing order, five quality levels : G.811, G.812T, G.812L, G.813, Q. Don’tuse (where the highest quality level is G.811 ).If Input Quality Configuration is set to a value other than ”Extracted”, Rx quality is forced to this value.
Click on the Priority: the option button opens the option menu to select the desired priority level.The internal oscillator timing source will have the lowest priority (priority=0) and its priority can not bechanged. The other timing sources will have a priority of 1 to n.
Priority of 1 is the highest priority. Levels 6,...2 are intermediate levels between level 0 and 1, in increasingorder of priority (i.e. 0 6 5 4 3 2 1).
When the configuration of the timing source is completed, click on the OK push button to validate thechoice and close the dialogue box. The Cancel push button cancels the configuration and closes thedialogue box.
Positioning the mouse on the synch. source box “Port#” test, the corresponding physical interfacedenomination (rack–subrack–board–port) is written on the window bottom left.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
302
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.4 Synchronization Protection Commands
Select the timing reference from the synchronization view. As in Figure 207. , select the Synchronizationpull down menu. You can then select the Protection Commands to open the Figure 210. Menu optionsare greyed according to the current state of the selected timing source.
Figure 210. Lockout, Force and Manual commands
a ) Invoke/Release Lockout: Locking or unlocking a timing source enables or disables the timingsource from being considered as a possible timing source for T0 or T4/T5.
b ) Invoke/Release Force and Manual Selection of Timing Source
General selection
A timing source can be selected manually or automatically. Furthermore, the selection of a particularincoming 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 lockoutor unavailable, this operation is impossible. A timing source is considered to be available if it is not lockoutand 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 aresufficient. 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 tobe done:– Select the T0 or T4/T5 source.– Click on the Synchronization menu.– Select the Protection Commands option then invoke/Release the Lockout, Forced or manual
Selection option.– Click on Apply in the displayed confirmation box.
Manual selection is not operative in the current release.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
303
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.5 Synchronization Configuration for T0/T4 and T4 squelch criteria
Select the available T0 or T4 synchronization sources and then the T0 or T4 Configuration... command.This command permits to select/deselect the SSM algorithm, to set the wait time to restore and to enablethe revertive procedure if all these features are available.
In this NE revertive mode is hardware set, with fixed WTR.
In Revertive mode the internal selector A/B (Figure 204. ) changes every time to the best reference clockwith the highest quality; on the same quality level basis the reference clock Source with the best prioritywill be selected. The changing mechanism of the reference inputs is controlled by the wait time to restore:this time sets a delay before to change the input source.
Selecting the T0 or T4 Configuration set the SSM algorithm and the Wait To Restore Time in the dialogbox upper part of Figure 211.
Click on the SSM Algorithm to select/deselect it.
Wait To Restore Time button and Revertive option button are disabled
Selecting T4 Configuration it is possible to set the T4 squelch criteria in the bottom dialog box ofFigure 211.
This functionality allows to configure the external timing reference (T4) squelch criteria. The squelchfunction mutes the relevant timing references in the presence of a failure condition.Squelch may be forced by the Operator or according to squelch criteria which consists in a choice of qualitylevel.Different squelch criteria may be applied:
• when T0 is selected to generate T4 (squelch B Figure 204. ): T0 may be squelched if all theallowable timing references of Selector B have Quality Level lower than the programmablethreshold.
• when T1 is selected to generate T4 (squelch A Figure 204. ) :T1 may be squelched if T1 QualityLevel is lower than the programmable threshold or if it becomes unavailable.
The T0/T4 and T1/T4 squelch fields enables you to configure the quality level of the T0 or T4 timingsource, opening the relevant option menu.
When the configuration of T0/T4 Configuration is completed, click on the OK button to validate the choiceand close the dialogue box.
The T5 output field allows to select the bit used (from #4 to #8) for SSM.
The Cancel button cancels the configuration and closes the dialogue box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
304
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 211. Configuring the T0 or T4 SSM algorithm and the squelch criteria
The T4 squelch configuration dialogue box enables you to configure the quality level of the T4 timingsource.
Click on the T0: option button to open the option menu and select the desired quality level.Click on the T4: option button to open the option menu and select the desired quality level.
The T4 Force Squelch enables you to activate the T4 forced squelch.
When the configuration of T0/T4 Configuration is completed, click on the OK push button to validate thechoice and close the dialogue box.
The Cancel push button cancels the configuration and closes the dialogue box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
305
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.6 SSU Configuration
The SSU configuration command allows either to configure the single NE or the NE with SSU. In the lastcase the SSU quality has to be defined.
Selecting SSU Configuration from the Synchronization menu is presented Figure 212.
Figure 212. SSU Configuration
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
306
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.7 Remove Timing Reference
Select the synch. source to remove and click on the Remove Timing Reference option (Figure 213. ).To remove the selected source click on “OK” button of the confirmation message (Figure 214. ).
Figure 213. Synchronization source removing
To remove the selected source click on “OK” button of the confirmation message (Figure 214. ).
Figure 214. Synchronization source removing confirmation
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
307
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.8 Change T4 <–> T5
This menu allows the change of the synchronization physical interface from 2Mhz (T4 ) to 2 Mbit/s (T5)and viceversa.
This menu is enable only if the SERGI board is present in the subrack.
Select Change T4 <–> T5 from the Synchronization menu as shown in Figure 212.
Figure 215. Change T4 <–> T5 menu
A confirmation message appears (see Figure 216. on page 307)
Figure 216. Change T4 <–> T5 confirmation message
Click on ok to confirm; the new window display T5 instead of T4 (see Figure 217. on page 308)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
308
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 217. Change T4 <–> T5: command execution
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
309
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.9 Change 2MHz –>2Mbit
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 218.
Figure 218. Change 2MHz –>2Mbit menu
A confirmation message appears (see Figure 219. on page 309)
Figure 219. Change 2MHz –>2Mbit confirmation message
Click on ok to confirm;
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
310
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The label of the protection unit will be changed depending on the kind of source selected (see Figure 220. on page 310):
• If the selected protection unit is a 2 MHz, then the label will be changed into 2Mbit/s (2 MbpsT6#A in the example of Figure 220. )
• If the selected protection unit is a 2 Mbit/s, then the label will be changed into 2MHz (2MHz T3#Afor example)
Figure 220. Change 2MHz –>2Mbit: command execution
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
311
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.10 Set and Remove T0 Equal T4
To connect T0 internal synch. select a synch. source and click on Set T0 Equal T4 menu option. Theconnection between T0/T4 will pass from a shaped to a continue line as in the example of Figure 221.
Figure 221. T4 equal T0 setting
To separate T4 from T0 click on the “Remove T0 Equal T4” menu option. The T0/T4 connection willbecome shaped while the connection between T1/T4 will pass from a shaped to a continue line.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
312
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.11 Transmission of SSM Quality Configuration
Select the T1 SDH Reference Source in the Synchronization View (Figure 206. ) hence the TransmissionSSM Quality Configuration is enabled. This selection allows, with the Inserted option, to transmit thesystem internal T0 clock quality towards the external SDH interface. It is also possible to transmit differentquality level selecting a different value.
Click on Transmitted SSM Quality Configuration of the Synchronization menu option.Figure 222. opens.
Figure 222. Transmission SSM Quality
This Transmission SSM Quality window can be also opened from any SDH boards. Select the Equipmentoption of the View menu, then access the Board view> Port view> Physical Media> SDH Tx QualityConfiguration; it is also possible to open the window selecting the Transmission option of the Viewmenu, then access the Physical Media> SDH Tx Quality Configuration option.
In both cases select the MST block
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
313
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
18.2.12 Show Timing Source
Selecting any T1 or T2 Reference Source in the Synchronization View (Figure 206. ) hence the ShowTiming Source is enabled. This selection allows to analyze the input source considering its payloadstructure and the related alarms (Port view is presented) .
Click on Show Timing Source of the Synchronization menu option. Figure 223. opens.
Figure 223. Show Timing Source (example with T2 reference source)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
314
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
315
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19 MS–SPRING MANAGEMENT
19.1 MS–SPRING introduction
Different MS–SPRING protections architectures are provide: 2–Fiber (Terrestrial), and 4–Fiber NPE(Transoceanic). See ITU–T Rec. G.841.
The description of the MS–SPRING protections is inserted in the Technical Handbook.
4 Fiber MS–SPRING is not operative in this release.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
316
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.2 MS–SPRING connection configuration advices
In the following paragraphs 2–Fiber advices are reported, to follow before to implement the MS–SPRingprotection: there are some limitations concerning the aggregate types or the AU4s cross–connections tobe considered.
19.2.1 2–Fiber MS–SPRING connection configuration advices
The following suggestions must be considered in the MS SPRING connection configuration:
• SNCP, 4 Fiber MS SPRING and MSP protection connections cannot be installed in a 2 FiberMS–SPRING network. This leads to an unprotected connections installation.
• AU4s from #9 to #16 don’t have to be used for connections nor considered in any parameterof ”Squelching table” provisioning. Only AU4s from #1 to #8 must be used and configured forpath installation.
• AU4 permutation (change of AU4 allocation) is not allowed. The AU4 allocated to pass–throughin HVC connections must be the same through the node.
• AU4 cross–connection line side, i.e. paths received from the line and looped–back to the sameline are not allowed.
• Follow the “Squelching Table Configuration” in order to define the ”Squelching Table HO” forEast and for West Side describing, for each connection installed, as Source Node, the NodeIdentifier of the node generating the considered AU4 and as Destination Node, the NodeIdentifier of the node terminating the AU4.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
317
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.3 Operative sequence to configure MS–SPRING
19.3.1 Operative sequence to configure 2–Fiber MS–SPRING
Next paragraphs list the operative sequence according the type of procedure to obtain.
– Activation procedure
a ) Create an MS–SPRING schema with WTR, Node Identifier, Ring map and the related SquelchingTable 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 MS–SPRing management select “ACTIVATE” in each node of the ring, in thedesired order.Consider that, in this step, “Default K byte West or East” detection by View Protection StatusParameter (under MS–SPRing label –> “Protocol exception”), will occur on those Ports connectedto the nodes not provisioned yet with the MS–SPRing protection “created” (active).
c ) Verify in the View Protection Status Parameter screen, at the end of the provisioning update, that allthe nodes of the ring are in “MS–SPRing active” and “No request” state.
– Deactivation procedure
a ) In the Main dialog for MS–SPRing management select “DEACTIVATE” in each node of the ring.Consider that, in this step, “Default K byte West or East” detection by View Protection StatusParameter (under MS–SPRing label –> “Protocol exception”), will occur on those Ports of theactivated nodes connected to the nodes just deactivated.
b ) In the Main dialog for MS–SPRing management select “DELETE” in each node of the ring.
– Removing a node
a ) In the Manage ring Map view select the node and click on the”Remove Node” button.
b ) Modify the table in the Configure Squelch Table view according the new Ring Map.
c ) Opening the View Protection Status Parameter screen, send “Force Ring” command to both NE’sadjacent to the node to be removed.
d ) Physically remove the node.
e ) Connect the fibers and send the “Release” command of the relevant “Force Ring” to both NE’sadjacent to the removed node.
– Adding a node
a ) In the Manage ring Map view insert the node in the selected position. Next nodes are automaticallyshifted.
b ) Modify the table in the Configure Squelch Table view according the new Ring Map.c ) Opening the View Protection Status Parameter screen, send “Force Ring” command to both NE’s
adjacent to the node to be added.d ) Physically add the node and configure with 2–Fiber MS–SPRING activated with the right
configuration (Ring Map, Squelching table, WTR, Node Identifier).e ) Connect the fibers and send the “Release” command of the relevant “Force Ring”to both NE’s
adjacent to the added node.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
318
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.4 MS–SPRING Management
In the current release the NE supports the MS–SPRING protection as “Terrestrial architecture“.The Transoceanic application with 4–Fiber is not supported in current release.
For the 2–Fiber Terrestrial application a max. of 16 nodes are available.
The available tables permit to visualize for the same NE the architecture 2 x 2–Fiber.
Figure 224. shows the MS–SPRing pull down menu.
Figure 224. Display MS–SPRing pull down menu
The first Main Dialog for MS–SPRing management option contains all the commands to configure andmanage the MS–SPRing.
In any dialog box is present the Cancel or Close buttons. When the user clicks on these buttons the dialogbox will close without starting any operation.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
319
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.4.1 MS–SPRing Main Configuration
Select the MS–SPRing pull down menu. Then select the Main Dialog for MS–SPRing management option from the pull down menu.
The following dialogue box is displayed (Figure 225. ) when no protection have been previouslyconfigured.
Figure 225. MS–SPRing Management dialogue box.
The only command available is Create. The name of Schema Selection is not editable but is fixed to “NoSchema”.
Click on Create to start the MS–SPRing configuration. Figure 226. opens.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
320
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 226. Creation Schema dialog box.
The user can select the “MS–SPRing Application” and the “Architecture types” supported by the NetworkElement.
Terrestrial MS–SPRing Application is a 2 Fiber architecture.
Transoceanic MS_SPRING is a 4 Fiber architecture (not supported in current release)
The “Port Selection” depends on the Architecture type: if the architecture is a 2F MS–SPRing, the workingand protection port on each side is the same and the “Protecting West and East” fields are disabled(greyed).
If the architecture is a 4F MS–SPRing, the working and protection ports on each side are different.
The label r(xx)sr(y)sl(zz)port#(hh) where r=rack, sr=subrack, sl=slot give the position of the physical port.In the same board it is generally possible to have different port numbers.
The OK button will start the selected operation. The cursor is displayed busy up to receiving a reply. Thenthe dialog window will be closed. Figure 227. opens and all commands are now available.
The Holdoff Time command is not operative in current release.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
321
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 227. Activated MS–SPRing Management
Click on Ring Map to configure the network node connection. Figure 228. opens.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
322
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 228. Node Id and associated ring node position.
The Ring Map sets the connection sequence of the nodes within the ring. The matrix represents up to 64nodes for transoceanic application and up to 16 nodes for terrestrial application.
Select Current NodeId (it means the NE where the operator is acting) in the box and enable ( � ) ChangeNodeId button (Id means Node Identifier).
Select Available NodeId in the pull down list (0 to 63 for transoceanic application, 0 to 15 for terrestrialapplication) releasing the left mouse button or pushing the stepper arrows and enter keys to select theNodeId value.
This will be displayed in the Available NodeId box then click on Add Node button.
Clicking on the Add Node button the selected “Ring position” will shift one step on the right starting from“1” position and in the “NodeId” field the Available NodeId value is inserted. In the same time the AvailableNodeId will be updated to a new value.
The default association for a four node ring related to the fourth node (NodeId=3; Ring Position=4) isdepicted in Figure 229.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
323
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 229. Ring map configuration
Repeat the procedure for all nodes of the ring selecting the different NEs and edit the different CurrentNodeId value.
To remove a node, select the node and click on Remove Node button. The following Ring Position ofthe nodes on the right decreases by one and the erased NodeId is inserted into Available NodeId , soit can be assigned to other nodes.
The OK button will start the selected operation, displaying the busy cursor up to receiving the reply to theactions. Then the dialog window will be closed.
Click on the WTR button. Figure 230. opens.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
324
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 230. WTR dialog box.
Click on the push mouse button on the up/down Seconds arrows to select the required delay for therelevant WTR. The step value is 60 sec.The range value accepted is from 60 sec. to 900 sec. (in current release is fixed to 300 sec.)
Click on OK to apply the WTR Configuration.
The same WTR Time Ring must be set on each Node of the ring.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
325
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.4.2 Squelching Table with 2 fiber Terrestrial applications
With a 2 fiber Terrestrial application can be selected the Squelching Table while with a 4 fiberTransoceanic application (not supported in current release) can be selected the Ring Traffic (seeFigure 227. on page 321).
If the operator tries to select a different table a error message is visualized. Figure 231. shows the errormessage visualized when is selected the Ring Traffic with a Terrestrial application.
Figure 231. Example of error message
Click on Squelching Table of see Figure 227. on page 321 to configure the AU4 (AU4#1 to AU4#8 for2F Architecture,) connection between the different nodes. Figure 232. opens. The same opens clickingon Configure Squelch Table of the MS–SPRing pull down menu of Figure 224. on page 318.
Figure 232. Squelching table
When the window is opened for the first time the squelching table is N/A ( not available ) because the NEhas never been configured. Point the mouse on the matrix position and click on the right mouse buttonto open the node list menu. Select the node identification number (0 to 15) from the available list usingthe slider or the stepper arrows on the right scroll region.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
326
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.4.2.1 Squelching table example
Figure 233. is an example of ring traffic.
Figure 234. represent in a table the connections of the ring example.
Figure 235. to Figure 242. show how to configure the relative squelching table.
AU4#1
AU4#2
AU4#3
AU4#1
AU4#2
AU4#3AU4#3
West West
WestEast
East East
WestEast
AU4#2 AU4#3
AU4#1
B
CD
A
Figure 233. Example of a ring traffic
The squelching table is applicable only for HO–VC signals.
AU west Node eastNumber
1
2
3
4
5
6
VC
VC
VC
B C DA A
Figure 234. Connections of the ring of Figure 233.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
327
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Node A: 1660SM – MS–SPRING–Squelch Table Configu...
Figure 235. Squelching table of Node A, West side.
Node A: 1660SM – MS–SPRING–Squelch Table Configu...
Figure 236. Squelching table of Node A, East side.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
328
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Node B:1660SM–MS–SPRING–Squelch Table Configu...
Figure 237. Squelching table of Node B, West side.
Node B:1660SM–MS–SPRING–Squelch Table Configu...
Figure 238. Squelching table of Node B, East side.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
329
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Node C:1660SM–MS–SPRING–Squelch Table Configu...
Figure 239. Squelching table of Node C, West side.
Node C:1660SM–MS–SPRING–Squelch Table Configu...
Figure 240. Squelching table of Node C, East side.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
330
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Node D:1660SM–MS–SPRING–Squelch Table Configu...
Figure 241. Squelching table of Node D, West side.
Node D:1660SM–MS–SPRING–Squelch Table Configu...
Figure 242. Squelching table of Node D, East side.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
331
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.4.3 Activate, Deactivate and Delete commands
The Main Activities commands ( Figure 227. on page 321) manage the MS–SPRing configuration. TheMS–SPRing status can be Enable, Active, Disable and Inactive.
After having configured the protection schema by means of the Create button, the status becomes Enable .
The Activate button selection enables the MS–SPRing protection mechanism on the selected schemaconfiguration.
To change from Active to Enable click on the Deactivate button. This command starts the request todeactivate the MS–SPRing protection mechanism.
When the selected protection schema is Enable the Delete button starts the request to remove it. Thedelete action is started after confirming the window message Figure 243. .
Figure 243. Confirmation message
During the activation procedure on different ADMs some of these can be in Active status , others in Inactivestatus. The statuses, the protocol request and the protocol protection errors are described in the chaptersdescribing the“MS–SPRing Protection Status and Commands” .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
332
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.5 MS–SPRING Protection Status and Commands for 2 fiber terrestrialapplication
19.5.1 2F MS–SPRing protection commands
If a protection schema is Active it is possible to select one of the above commands.
Clicking on the Prot. Commands button in the MS–SPRing –>Main Dialog for MS–SPRing management( see Figure 227. on page 321), Figure 244. is opened.
8
Figure 244. Protection states and commands ”Idle” status (2F)
The working/protection span state boxes are not available (greyed) for the 2Fiber MS–SPRingarchitecture.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
333
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
In the MSPRing 2 Fiber configuration, the 1–8 working channels are inserted into the 9–16 protectionchannels in the opposite side of the failure event as shown in Figure 245.
A
E W E
BX w/p
W
Ring Protection:
by the ring protection channels ”p” (AU4 9 to 16)( B on East side )( A on West side )
the working channels (AU4 1 to 8) are substituted
w/p w/p
w/p
Figure 245. Ring Protection (2F)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
334
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.5.2 External commands (2F)
The external protection commands are : Lockout, Force, Exercise (not operative in currentrelease),Manual, WTR.
The lockout commands disable the MS–SPRing management.
The lockout section presents six lockout commands, four operative ( Figure 246. ). Each lockoutcommand is applicable on different points where the lockout actions has to be performed ( Figure 247. )and any “Lockout” command is associated to a “Release “ command to come back to the previous status.
Term “Span” identifies the section interested by the command, it doesn’t assume the Span meaning of thefour fiber protection.
Figure 246. Lockout commands (2F)
Ap
p=protection (AU4 9 to 16) w= working (AU4 1 to 8)
wpw
wp
wp
EastWest
Figure 247. Protection and working channels where the lockout command can be activated (2F)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
335
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The protection events can be equipment/signal failure, signal degrade or external command or acombination of them.
The “Events” will be served if some actions (B/S=bridges and switches) are executed and the networkhas been updated.
The “Events” will be signalled if the K1/K2 protocol communicates to the network nodes what hashappened, without execute actions.
A single ring failure is completely restored but not two ring failures. When are present multiple ring failuresthe automatic B/S protection will try to maintain on all the possible connections.
The K1/K2 communication protocol MS–SPRing is generated from the two nodes adjacent to “Event” viathe protection communication channels. A node is defined tail –end when it firstly receives the “Event”,the second node is defined head–end when it receives back the protocol answer. Figure 248. shows theassociation of tail–end / tail–end or head–end / tail–end.
Some network protection mechanisms are accepted or rejected depending on the end type (tail/head)(lockout command,...)
B
W E W E W E
A C
Tail–end Tail–endTail–end/Head–end
w/p
w/pX X
w/p
w/p
Figure 248. Tail–end / Head–end association
If the node is tail–end, the lockout working ring command disable the protection MS–SPRingmechanisms, while if the node is head–end, it serves the request node protection (protection notdisable). See Figure 249. on page 336.
With the lockout protecting span command and a ring failure, the ring protection is served if this ring failureoccurred along the same section; the ring protection is disabled if the ring failure has occurred inanother 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 250.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
336
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
W E
W
E
A
B
Lockout working
w/p
w/p
failure
ring protection
W E
W
E
A
B
Lockout workingw/p
w/p
failure
no ring protection
tail
head
tail
head
Figure 249. Tail–end / head–end protection with a lockout working and a one direction ring failure (2F)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
337
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
W EW
E
A
B
Lockout protecting Span
w/p
w/p
failure
ring protection
W
A
Lockout protecting Span
failure
no ring protection
W
E
C
W EW
E
A
B
w/p
w/p
failure
w/p
w/p
ring protection
W
A
failure
W
E
C
w/p
w/p
W EW
E
A
B
w/p
w/p
failure
no ring protection
ring protection
E
E
Lockout working Lockout working Lockout working
Lockout working
Figure 250. Ring protection with a lockout and a ring failure (2F)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
338
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 251. shows a ring with three nodes and the actions performed by the lockout commands. Thiscommand disables the acknowledgment of the signal failure/degrade on the receiving ports.
A N
od
e
B
WE
WE
WE
AC
A N
od
eA
No
de
A N
od
e
Rin
g E
Lo
cko
ut
Pro
tect
ion
Rin
g W
Lo
cko
ut
Pro
tect
ion
Rin
g E
failu
res
and
of
no
n–s
erve
d”1
””2
”
Lo
cko
ut
Wo
rkin
g
Rin
g W
Lo
cko
ut
Wo
rkin
g
1
2
4
ring
prot
ectio
n on
the
oppo
site
sid
eth
e op
posi
te s
ide
if th
e rin
g fa
ilure
if
the
ring
failu
reoc
curs
bet
wee
nA
–C o
r C
–B n
odes
occu
rs b
etw
een
A–B
or
B–C
nod
es
ring
prot
ectio
n on
Com
bina
tions
exte
rnal
com
man
ds
3w
/p
w/p
w/p
w/p
Figure 251. Lockout command and non–served failures (2F)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
339
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
The Force command ( Figure 252. ) executes a forced protection. The Force Ring command substitutesthe working channels (AU4 1 to 8) with the opposite direction protection channels (AU4 9 to 16) betweentwo adjacent nodes (Figure 253. ).The Force Span command is not operative in 2 fiber MS–SPring.
Figure 252. Forced and Manual commands (2F)
AEW
w1–8
Manual/force Ring East
BW E
W. 1–8 channels are substituted by P. 9–16 channelson the opposite side for both adjacent nodes
A1
w1–8
w1–8
p9–16
w1–8
p9–16
p9–16
p9–16
w1–8
p9–16
w1–8
p9–16
W/P
W/P
B1
w1–8
p9–16
w1–8
p9–16
W/P
Manual/force Ring West
Figure 253. Manual and Force Ring command (2F)
The Manual command is similar to Force command but it is at a lower priority level with respect toautomatic MS–SPRing. The general priority scale that can be applied to solve antithetical situationsstarting from the lowest priority level is: manual ring – automatic working ring – force ring – lockoutWorking Ring – lockout Protecting Span.
When a force ring command is applied a next working failure is not able to modify the forced configurationapplied. That is because force ring command has a higher priority respect to the “Automatic” workingprotection. In this condition the ring can be split according the location of command and event. Vice versathe “Manual” protection is exceeded by the “Automatic” protection. Figure 254. visualizes the ringprotection with a Force/Manual command and a signal failure. FS–R is for “Force Switching Request”,SF–R is for “Signal Failure Request”.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
340
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
W E
W
E
A
B
Force Ring East
w/p
w/p
failure
W
A
failure
ring protection for FS–R
W
E
C
W E
W
E
A
B
w/p
w/p
failure
w/p
w/p
ring protection for SF–R
W
A
failure
W
E
C
w/p
w/p
ring protection for SF–R
Force Ring East
Manual Ring East
W
E
C
BW
E
CW
E
”A” node is isolated
E
Manual Ring East
E
ring protection for SF–R and FS–R
Figure 254. Ring Protection with Force and Manual commands (2F)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
341
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
A node
Signal fail/degrade
A node
B/S actions
Ring WSignal fail/degrade
Ring E
1–2 w. channels aresobstituted by 3–4 p.
3–4 w. channels are
B
W E W E W E
A C
w/p1
2w/pw/p
w/p
3
4
sobstituted by 1–2 p.channels channels
Figure 255. Automatic protection Bridge/Switch (2F)
Each command starts when the proper button is selected. A dialog box ( Figure 256. ) has to be confirmedbefore the command is performed.
From each command exists its own Release button to cancel the previously selected command and comeback to normal MS–SPRing protection.
Figure 256. Example of confirmation dialog box
Clicking on the WTR command (of Figure 227. on page 321) next figure opens. If the WTR box, in theLocal Condition field of Figure 244. on page 332, becomes red a waiting time has been activated afterrepairing the ring failure. The waiting time, set in the configuration menu, can be cleared selecting theClear WTR Ring command. A confirmation dialog box opens and, if the operator clicks OK, the WTRbox turns off and the protection status window is updated.
Figure 257. Clear WTR command (2F)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
342
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.5.3 2F MS–SPRing dual protection commands
In general dual contemporary “Events” can be:
two external commands
an external command and a ring failure
two contemporary ring failures
Dual “Events” can appear on the same side W/W (West/West) or E/E (East/East) (SS= same side) or onthe opposite side W/E or E/W (OS= opposite site) of the ring network. In the SS or OS the “Events” canappear on the same node (SN) or on the different nodes (DN), the different node can be an adjacent node(AN) or a remote node (RN). Figure 258. depicts a clockwise ring network . The network propagationK1–K2 protocol signals are according to the following legend :
C = served the column element
R = served the row element
B = served both row and column elements
Cs = signalled (not served) the column element
Rs = signalled (not served) the row element
Bs = signalled (not served) both row and column element
when a command (Manual switch, Force switch) is neither served nor signalled, it is erased ( it isnot pending at the node)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
343
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
W E
W
E
1
2
w/p
w/p
w/p
w/p
WE
3
W
E
4
Reference point
SS SNclockwise
OS AN
SS AN
OS SN
OS RNSS RN
SS RN
OS RN
Figure 258. Ring network reference scheme (2F)
Figure 258. visualizes the ring reference scheme: the adjacent node (AN) is the node connected to thereference point.
The automatic protection for dual ring failures is represented in Figure 260. Consider the networkreference scheme of Figure 259. with a tail–end / head–end alarm propagation. In this figure are depictedthe node switches for any reported double events.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
344
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
W EW
E
1
2
w/p
w/p
failure
W
E4
failureWE
3
W EW
E
1
2
w/p
w/p
failure
W
E4
failure
WE
3
W EW
E
1
2
w/p
w/p
failure
W
E4
failure
WE
3
W E W
E
1
2
w/p
w/p
failure
W
E4
failure
WE
3
W EW
E
1
2
w/p
w/p
failure
W
E4
failure
WE
3
SS–AN
SS–RN
OS–AN
OS–RN
OS–SN
Figure 259. Examples of Double ring failure
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
345
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Rin
gP
rote
ctio
n
point
Otherpoints
SN
AN
RN
SN
AN
RN
Reference
Au
tom
atic
SS
OS
Automatic Protection Ring
Nodes 1,2,3,4 in switching for SF alarm =B
Node 4=intermediate
Node 2: isolated=BsNode 1,3 in switching for SF alarm=BNode 4 = intermediate
Node 1,2 in switching for alarm=BNodes 3,4 = intermediate
Node 1: isolated=BsNodes 2,4 in switching for SF alarm=BNode 3= intermediate
Node 2 : isolated = BsNode 1–3 in switching for SF alarm =B
Figure 260. 2F Automatic protection (tail/head) for double ring failure visualization
The same reference Figure 258. and Figure 259. 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 261. ) shows the “Events” at the reference point. Foreach of them the associated “Event” is listed on the first column at the left of the table.
Two manual ring commands can be only signalled: Bs (Manual SS–SN and OS–AN commands give thesame 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 notapplied on the SS–SN. In this last case has to be considered the priority level. The behavior is that seenfor two automatic protection switching ( Figure 259. )
Lockout working SS–SN has priority with respect to Manual, Automatic protection and Force commands.In the other cases, both commands are served (B).
Lockout protection SS–SN / OS–AN and Manual or Automatic or Force command are both servedbecause the switching SS–SN / OS–AN channels are not managed by the lockout protection: B.
Lockout protection SS–AN / OS–SN overrides the Manual or Automatic or Force command because thelockout protection controls the switching channels of the same Node.
Lockout protection SS–RN / OS–RN and manual or automatic or force command: the lockout protectionprevents the working 1–8 channels from being inserted into the protecting 9–16 ones. The lockoutprotection is served, because it has a higher priority, the ring protection will be only signalled (pending).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
346
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Rin
g
Ring
Manual
Ring
Automatic
Ring
ForceF
orc
eR
ing
Man
ual
LockoutWorking
Protection Working
SS
OS
SN
SS
OS
SN
SS
OSSN
AN
RN
AN
RN
AN
RN
SS
OS
SN
AN
RN
Lo
cko
ut
Wo
rkin
gL
ock
ou
t Pro
tect
ing
SN
RN
AN
SN
AN
RN
SN
AN
RN
SN
AN
RN
Bs
BsBs
B
BsCCC
CCCCBBBBBBC
CRsC
CRsB
point
Otherpoints
Reference
RR
RRR
R
RR
RRR
R
CBBBBB
CBBBBB
CBBBBB
BBBBB
BC
CRsC
CRsB
BC
CRsC
CRsB
B
B
BR
RCsRB
RCsBRRCs
RBRCs
RB
BB
B
B
RBBBBB
Figure 261. Tail / head dual “Events” Protection table (2F)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
347
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.5.4 2F Protection Status Visualization
The protection statuses ring network are:
– 1 – Lockout Switching
– 2 – Forced Switching
– 3 – Automatic Switching ( MS–MSPRing protection for equipment/signal failure ).
– 4 – Manual Switching
– 5 – Idle ( regular operation without MS–SPRing protection )
These protection states are represented with the following color state boxes:
– Green: Active State, No Request condition.
– Red: Inactive State and any external or protection executed command ( that has been served ).
– Yellow: ordered but not executed command ( that has only been signalled= pending status ).
– Greyed: not available state box.
Automatic switching and external commands are revertive: then when the “Events” have been cleared,the MS–SPRing configuration comes back to its idle status.
The state boxes visualize the “Node Condition Request” as a consequence of the equipment/signal failureor the external commands detected on the corresponding side (”Event”). The state boxes don’t describethe protection actions provided on the NEs.
The served “Events” ( B/S=bridges and switches are executed and the network has been updated ) arecompleted 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 262. shows the protection status with a served East manual ring command. Any protection statuswindow is divided in different status fields: Schema description and status, Local Conditions, NodeConditions and Protocol Exceptions. The first one describes the network configuration and applicationtype and its status, the second gives the local external commands indications, the third the “Events” resultson 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 protectionsand commands. In the middle “WTR–Ring” refers to West and East sides, “No Request” correspondingto “Idle Status”, and “Intermediate Node” denotes that the protections and commands don’t concern thenode involved. The Manual Ring command visualizes “Manual Ring” on the local node and “RequestNode Ring” in the both “Local Conditions adjacent East ADM1–West ADM2 nodes, while the 3 and 4nodes are “Intermediate Node”. The red color means that the command has been served. A regularprotocol “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 networknode.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
348
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 262. Manual command applied at the “Reference Point” ring network Figure 259.
Figure 263. reports the “Protection Status” for external “Force and “Manual” commands in a 3 –node ring(A, B, C). Figure 264. shows the lockout statuses and Figure 265. the automatic protection statuses.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
349
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Local Conditions Force/
WRing
A
Force/Manual Force/Manual
B C A B C
Node ConditionsNode
WRing
RequestNode
ERing
Request
Nod
e
Inte
rmed
iate
Force/
ERing
Node
ERing
RequestNode
WRing
Request
Nod
e
Inte
rmed
iate
B
W E W E W E
A C
w/p
w/p
w/p
w/p
Ring W Ring E
Manual Manual
Referencenode: A
Figure 263. Visualization of the Forced / Manual protection Statuses (2F)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
350
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
LocalRing W
A
Lockout Working Lockout Protecting
B C A B C A B C A B C
Node
Ring E
Nod
eIn
term
edia
te
Nod
eIn
term
edia
te
Ring W Span W Span ELockout Working
Ring ELockout Protecting
Lockout Lockout LockoutProt W
LockoutProt E
Referencenode: A
Pro
t. U
nava
ilabl
e
Pro
t. U
nava
ilabl
e
Pro
t. U
nava
ilabl
e
Pro
t. U
nava
ilabl
e
B
W E W E W E
A C
w/p
w/p
w/p
w/p
Conditions
Conditions
Figure 264. Visualization of the Lockout command Statuses (2F)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
351
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
A
Signal fail/degrade
B C A B C
Node Conditions
Ring WSignal fail/degrade
Ring E
WRing
Request
ERing
Request
Nod
e
Inte
rmed
iate
WRing
Request
ERing
Request
Nod
e
Inte
rmed
iate
Referencenode: A
B
W E W E W E
A C
w/p
w/p
w/p
w/p
Figure 265. Visualization of Automatic Protection Statuses (2F)
The WTR status is visualized on the side where the link has been repaired. The considered networkfailures are related to a tail–end/head–end node connection. The “WTR Clear” command can be executedby the user without waiting the WTR setting time.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
352
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.5.4.1 Double ring failure
The double ring failure visualization of Figure 259. are here following reported.
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 266. Protection status with double ring failure (reference point––SS–AN)
Figure 266. reports the protection status with double ring failure (reference point––SS–AN. The node 2isolated, the nodes 2–3 in switching and the node 4 Intermediate. The box color is white unless otherwisespecified:
“Active”: green“Request Node Ring” West ADM3–East ADM1: red (served)“Request Node Ring” West ADM2–East ADM2: yellow (pending)“Intermediate Node” ADM4: red
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
353
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 267. Protection status with double ring failure (reference point––SS–RN)
Figure 267. reports the protection status with double ring failure (reference point––SS–RN). The nodes1,2,3,4 are being switched for signal failure alarm and both the two signal failures are served. The boxcolor is white unless otherwise specified:
“Active”: green“Request Node Ring” East ADM3–East ADM1: red (switching for SF)“Request Node Ring” East ADM4–East ADM2: red (switching of the opposite nodes)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
354
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 268. Protection status with double ring failure (reference point––OS–AN)
Figure 268. reports the protection status with double ring failure (reference point––OS–AN). The nodes1,2 are being switched for signal failure alarm and both signal failures are served: B. The box color is whiteunless otherwise specified:
“Active”: green“Request Node Ring” West ADM2–East ADM1: red (switching for SF)“Intermediate Node ” ADM3–ADM4: red
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
355
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 269. Protection status with double ring failure (reference point––OS–AN) recovering to “idle”
Figure 269. reports the previous protection status with double ring failure (reference point––OS–AN)while the ring protection comes back to its “idle” status. The “WTR (Wait To Restore) Ring” on ADM1 nodebecomes red to signal that the SF disappears at the “reference point” . The box color is white unlessotherwise specified:
“Active”: green“WTR Ring” : red (to signal the SF recovering)“Request Node Ring” West ADM2–East ADM1: red“Intermediate Node ” ADM3–ADM4: red
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
356
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
19.5.4.2 Double external command or an external command and a ring failure
Some more significative double events of Figure 261. are here following reported.ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 270. Double manual ring command (reference point––SS–AN)
Figure 270. reports the protection status with double manual command (reference point––SS–AN). Boththe commands can be only pending. The “Request ring” to 1,2,3 nodes becomes pending while the 4 nodeis “Intermediate node”. The box color is white unless otherwise specified:
“Active”: green“Request Node Ring” East ADM1– West ADM2: yellow ( pending ) for Manual Ring East ADM1“Request Node Ring” East ADM2– West ADM3: yellow ( pending ) for Manual Ring East ADM2“Request Node Ring” West ADM1– East ADM3: yellow ( pending ) for switching of the opposite nodes“Intermediate Node ” ADM4: red
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
357
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 271. Double manual ring command (reference point––OS–AN)
Figure 271. reports the protection status with double manual command (reference point––OS–AN). Boththe 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 coloris white unless otherwise specified:
“Active”: green“Request Node Ring” East ADM1– West ADM2: red ( served )“Intermediate Node ” ADM3, ADM4: red
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
358
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 272. Manual ring and Lockout Protection (reference point––SS–SN)
Figure 272. reports the protection status with a manual command and a lockout protection (referencepoint––SS–SN). Both the manual and the lockout commands are visualized to the same ADM1 node(East). Both the commands are served because the bridge/switch points are different. The box color iswhite 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.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
359
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 273. Manual ring and Lockout Protection (reference point––SS–RN)
Figure 273. reports the protection status with a manual command and a lockout protection (referencepoint––SS–RN). The manual command is pending while the lockout command is served. The box coloris 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)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
360
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 274. Automatic working ring and Manual Ring (reference point––OS–AN)
Figure 274. reports the protection status with a ring failure and a manual ring command (referencepoint––OS–AN). The automatic protection has a higher priority with respect to the manual command andthen 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
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
361
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 275. Automatic working ring and Force Ring (reference point––SS–AN)
Figure 275. reports the protection status with a ring failure and a force ring command (referencepoint––SS–AN). The ADM2 is isolated and the force command is pending. The box color is white unlessotherwise 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
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
362
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 276. Automatic working ring and Lockout working Ring (reference point––SS–SN)
Figure 276. reports the protection status with a ring failure and a lockout working command (referencepoint––SS–SN). The Lockout command has a higher priority with respect to the automatic protectionswitching and then only the lockout command has been served. The box color is white unless otherwisespecified:
“Active”: green“Lockout Ring” command East ADM1: red“Request Node Ring” East ADM1 – West ADM2 : red (served)“Intermediate Node” ADM3 – ADM4 : red
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
363
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
ADM4: 1660SM –– MS–SPRING–Protection States and Commands ADM1: 1660SM –– MS–SPRING–Protection States and Commands
ADM3: 1660SM –– MS–SPRING–Protection States and Commands ADM2: 1660SM –– MS–SPRING–Protection States and Commands
Figure 277. Automatic working ring and Lockout Protection (reference point––OS–RN)
The lockout protection has a higher priority with respect to the automatic ring protection. The box coloris 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
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
364
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
365
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
20 ATM/IP/ETH CONFIGURATION
20.1 Introduction
This Chapter describes the operations necessary for the ATM/IP/ETH boards creation in the Equipmentview and the ATM/IP/ETH TTPs creation; as a matter of fact ATM/IP/ETH boards does not crate TTPswhen they are configurated.
The ATM/ETH/IP board creation is performed (following the same rules of all the other SDH/PDH portsas explained in paragraph 9.2 on page 101) when a CT user sets an ATM/IP/ETH board and then configurethe IP Address (as described in paragraph 8.13 on page 92).
For the TTPs creation refer to paragraph 20.2 where all the operation are explained.
For the ATM/IP/ETH traffic configuration (for example creation of Hard/Soft cross connection, PNNIconfiguration etc.) refer to the relevant OPERATOR’S HANDBOOK (ATM or IP) where “Specific Terminal”application is explained in details.
The operational sequence to follow to manage ATM/IP/ETH cross–connection is:
a ) ATM/IP/ETH board declaration (Equipment Set)
b ) ATM/IP/ETH IP Address Configuration ( Called ISA board IP Address)
c ) ATM/IP/ETH board TTPs creation (VC4–4c TTP, VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP, E1 TTP)
d ) TTPs cross–connection ( refer to paragraph 15.3 on page 228)
e ) ATM/IP/ETH traffic configuration with “Specific Terminal” application
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
366
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
20.2 ATM/IP/ETH board TTPs creation
In this paragraph will be explained how to create, delete and modify ATM/IP/ETH TTPs.
ATM board
On the ATM 4X4 board can be configurated up to 16 TPs (VC4 TTP, VC3 TTP, VC12 TTP, s31 TTP, E1TTP) with the following restriction:
– In this release it is not possible to manage structured and unstructured TPs on the same board
– the maximum throughput is 622 Mbit/s
On the ATM 8X8 board can be configurated up to 32 TPs (VC4–4c TTP, VC4 TTP, VC3 TTP, VC12 TTP,s31 TTP, E1 TTP) with a maximum throughput is 1.2 Gbit/s.
IP board
On the IP boards (IP 4X4 and IPGETH) can be configurated up to 31 TPs (VC4 TTP, VC3 TTP, VC12 TTP).
ETHERNET board
On the ETHERNET board can be configurated up to 11 TPs (VC4 TTP, VC3 TTP, VC12 TTP) on the portcard and up 14 TPs (VC4 TTP, VC3 TTP, VC12 TTP) on the relevant access card.
Select ATM/IP/ETH Configuration option from the Configuration menu to open the ATM/IP/ETH portsConfiguration (see Figure 278. on page 366).
ATM 4X4 MATRIXETH–MB
Figure 278. ATM/IP/ETH ports Configuration (examples)
The ATM/IP/ETH ports Configuration window is filled with notebook pages (initially blank), each page isan ATM, ETH or IP board with relevant ports;
The user can “create” a new port, “delete” an existing one and “change” port associations (that meansmodify the STM1 number and STM–1 Time Slot on ATM ports already created) via the three buttonscontained in the notebook page.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
367
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
When the user want to create a new ATM, IP or ETH port he can select an empty row, then in the “SelectedItem” section , he can fill the field ”Signal” choosing among the available options and push the”Create”button.The STM1 Number and the STM1 Time Slot are automatically assigned.
An example of ATM port creation is depicted in Figure 279. on page 367.
If the user want to change the port attribute association he can select a filled row, then in the “SelectedItem” section he can change the fields ”STM1 number” and ”STM1 Time Slot” and than push the ”TimeSlot Sw.” button.
To delete a port the user can select a row and push ”Delete” button.
Figure 279. ATM ports Configuration (example)
To close the dialog box click on the “Close” push button.
It is possible to see the ATM, IP or ETH Ports created as above explained by selecting the relevant boardin the Equipment view and double clicking on it; Figure 280. on page 368 shows an example.
Subsequently select the PSEUDO SUBBOARD icon in the Equipment view and double click on it,Figure 281. on page 368 opens showing the ATM ports.
Figure 282. and Figure 283. show other examples for Ethernet ports.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
368
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Pseudo Subboard icon
Figure 280. ATM board view (example)
Figure 281. ATM PSEUDO–SUBBOARD view (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
369
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 282. ETHERNET board view (example)
Figure 283. ETHERNET port view (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
370
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
371
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
21 SOFTWARE MANAGEMENT
21.1 Generalities and descriptions
The Craft Terminal provides a set of functions which allow software packages manipulation within NEs.The downloading operation consists in the establishment of session between the NE and a softwareserver for the purpose of file transfer.
Actions can then be performed on the NE software version as update and activation operation, or roll backto the previous software version operation. In this way the NE can follow the product evolution with “inservice” equipment.The same function is used during maintenance phase, to update spare boards for substitution aftertroubleshooting.
The operations that can be undertaken in this section are:
– display Software Download Information,– initiate / Abort Software Package Download,– manage Software Packages within NEs, activating the downloaded Software Package or coming
back to the previous condition.
A backup/restore can be also done on the MIB of the NE. Indeed the MIB can be saved to or restoredfrom the mass storage of the Craft Terminal.
The software download general principle is represented in the following figure.
MANAGER
SERVER
CLIENT
AGENT
NE
DownloadControl
EventReport
TransferRequest
Binary & DataFiles
Software Management
Software Downloading
OPERATOR
OPERATOR
Figure 284. Software Download general principle
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
372
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
21.1.1 Naming Conventions
The naming conventions used for Download Management are the following:
– Software Package: Software Package stands for a piece of software which can be executed by anNE of a particular type. It consists in one or more Software Units and a Descriptor File. A softwarepackage is identified by its name, release, version and edition.On the NE (i.e. once downloaded) a software package can be:
– the active version: the software package currently running on the NE– a standby version: a software package which is neither the active version nor the boot
version
– Software Unit: A Software Unit is a part of a software package which can be either executable codeor 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 andlists the composing software units. Each software package must have a descriptor file otherwise itwould not be possible to interpret the content of the package.
– Software Management Function: The Software management function offers information about allcurrent software packages present in an NE. Indicators enable software management (runningpackage, activated package, etc...).
The following software version states are available:• Commit (active) version: the software version currently running on the NE.• Standby version: is a software version which has been downloaded on the NE but which is
not in the active state.
Two main functions are involved in the software downloading:– Software Download Manager function– Software Download Server function
The Software Download Manager function takes the downloading and management requests of theoperator and sends them to the NE. Thus, this function enables a download process to be initiated andmonitored by the operator. It manages the NE software releases and initiates software downloadoperations.
The Software Download Server is only responsible for fulfilling the requests received from NEs andperforming software package file transfer operations to the NE.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
373
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
21.2 Software download operative sequence
Two main different operative condition are defined for this Equipment:
• First installation of a 1660SMThe NE is received without the relevant software install. The software download must be doneas described in the SIBDL section of this Handbook.
• Updating a 1660SM with an already installed software.Follow the operative indications of para. 21.2.1 on page 373 .
21.2.1 Software Download upgrade
N.B. In order to migrate from Release 1.1A to a Higher Release, the download procedure requirestwo steps. The first is from 1.1A to 1.1X (intermediate package) and the second is from 1.1Xto the Higher Release (e.g. 1.1B1).
In order to update the following procedure is to be done as explained in the next steps:
a ) Install the CD ROM with the NE Software Package on the PC, as for the procedure of para 21.2.2on page 373.
b ) open a session on Craft Terminal application (start–up of the application, start supervision and NElogin)
c ) Check the present status of the software on a selected NE.
Download should not be performed in presence of unstable alarms
d ) Open the Download menu as for para. 21.3 on page 380.
e ) Select the new software package in the server and triggers the download process, as presented atpara.21.4 on page 381.A message will indicate the completed download.
f ) Activate the package as presented at para.21.5 on page 383.
g ) Check that the activated package is in the “Commit” status.
h ) If problems are found with the new activated package, activate the previous software package(revert–back operation) to come back to the previous condition and then try to repeat the procedure.
21.2.2 NE Software package installation procedure
The following procedure allows the NE software package installation. According to the customerrequirement two types of installation are possible:
[1] If only SDH software package installation is required follow the instruction from point a ) to point e )and than download the software package SDH (example 1660SM 2.1B.09) from the EML–USM(refer to paragraph 21.4 for details).
[2] If SDH+”Specific Software” package installation is required follow the instruction from point a ) topoint n ). In the example that follows will be described the ATM specific software installation; followingthe same rule will be possible to install also the IP specific software.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
374
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Procedure
a ) Install from CD ROM the NE Software Package on the Personal Computer, as explained in the“1320CT Basic Operator Handbook”.
b ) Run the 1320CT V.x platform
c ) From Network Element Synthesis (NES) choose the Software Administration option of theSupervision –> File Administration menu (see Figure 285. )
Figure 285. Software Administration menu
After the selection Figure 286. will be opened.
Figure 286. Software Package Administration view
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
375
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
d ) Select the <SDH> tag
e ) Press the <INSTALL> button to install the relevant software package.In the window that opens select the directory where the NE software package file has been installed(typically is Alcatel/usm/ect/swdw/<equipment name>/<version>/<descriptor file>) and execute (seeFigure 287. )
Figure 287. SDH software package installation
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
376
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
f ) Insert the ATM CD ROM in the computer
g ) Select the <SERV. SPEC.> tag
h ) Press the <INSTALL> button to install the ATM software package present on the ATM CD ROMIn the window that opens select the directory where the ATM software package file has been installed(typically is /ect/swdw/<atm>/<version>/<descriptor file>) and execute (see Figure 288. )
Figure 288. ATM software package installation (example)
Click on Ok to continue;
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
377
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
i ) Select the <SDH> tag
j ) Select the SDH software package base onto which ATM software package has to be merged
k ) Press <Create Enhanced> to launch the software merging process and create the SDH+ATMsoftware package
The New Software package will be created (see Figure 289. )
Figure 289. OMSN enhanced software package creation (part A)
Click on Yes button to continue; Figure 290. will be opened.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
378
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
OMSN name
OMSN version
Figure 290. OMSN enhanced software package creation (part B)
The originated “Enhanced” software package has a new label as follows:
OMSN name = is the SDH name + “E” letterOMSN version = is the SDH version
Example: Starting from SDH SWP 1660SM ver. 3.xy.wz will be created the OMSN SWP1660SME ver. 3.xy.wz
l ) Select the previously created software package (example 1660SME 3.1.08)
m ) Select the ATM software package (in the right view) (example ATM 1.01.07)
n ) Press the <ADD> button , so the new software package will be created (refer to Figure 291. )
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
379
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Figure 291. Enhanced software package (SDH + ATM)
It is now possible to download the enhanced software package (SDH + ATM) from the EML–USM(refer to paragraph 21.4 for details).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
380
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
21.3 Software Download Manager menu
All the software download operations are carried out from the software download manager.
Figure 292. Equipment view
To display the software download manager menu from the main view, select the NE on which you want toperform download operations, then select the Download pull down menu. The following menu is displayed:
Figure 293. Download menu
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
381
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
21.4 Init download
You can request the NE to start / abort a software download operation. After selecting the desired NE youmust choose an available software package and then start the download process. All these operationscan be performed from the SW downloading dialogue box.
Select the Init download option from the Download cascading menu.
The Software download initiate dialogue box is opened.
Figure 294. SW Downloading dialogue box example
The following fields are available to search a specific package:
– Server filter: to enter the server name selected,– Package filter: to enter the package name selected.
To use the filter and display the selection, push on Apply filter(s) button. The SW packages existing onthe Craft Terminal are displayed.
In the next field the list of the packages is displayed:
– Server: name of the server,– Package: name of the package,– Version: version number of package.
Click on Forced push button to set the forced download attribute: then all software units of the Descriptorfile 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 dialoguebox to close it.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
382
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Click on the OK push button to start the download. From the confirmation dialogue box that opens, youcan confirm or cancel the download. If you confirm the operation, the SW Downloading dialogue box thendisappears and the Software download in Progress dialogue box is displayed (see Figure 295. ) fromwhich you can if necessary abort the software download.You can monitor the download progress by means of the Software in Progress dialogue box which alsoenables you to possibly abort the current download.
Figure 295. Software download in progress (example)
The Software download in Progress dialogue box displays the name and type of the NE and the SWpackage 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 confirmationdialogue 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 softwaredownload.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
383
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
21.5 SW package Activation and Units information
This item permits to activate the downloaded software package and to get information about the softwareof the various units of the equipment.
The operator is able to get information about the software package of the NE at any moment, even if nodownload operations have been performed previously.
For this, select the Units info option from the Download pull down menu.
The following dialogue box is opened.
Figure 296. Software Package Information dialogue box (example)
The SW Information dialogue box displays the name and type of the NE, and the respective package nameand status of the committed and (if existing) the uncommitted software.
You can select one software package by clicking on the name.
The following fields are displayed:
– Software package: name, release, version, edition of the package,– Service Specific Components: name, release, version, edition of the Service Specific Components
(example ATM, IP etc.)– Operational state: enabled or disabled,– Activation date: date and hour of the last activation– Vendor: the supplier of the product,– Current state\Action: commit or stand–by and with the option button; none/Force/Activate/Delete
current state = standby means the package is not active on the NEcurrent state = commit means the package is active on the NEaction = (none) means no action to doaction = activate serves to activate the selected SW packageaction = force
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
384
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
Select the Activate option of the “CurrentState\Action” field, to activate the Software package
The Sw units Det. button allows to give more information about a selected software package.
Clicking on it, the following window is displayed:
Figure 297. Detail software package (example)
Clicking on [–] symbol behind each software package all details disappear.
When you click on Close the previous view is displayed (Figure 296. ).
In Figure 296. when you click on the:
– OK push button you close dialogue box,– Cancel push button you close the SW Information dialogue box,– Help push button you access to help on context.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
385
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
21.6 Mib management
This function allows to make a backup and/or a restore of the Mib.. (MIB is a data base pertaining theconfiguration of the equipment).
Select the Mib management option from the Download pull down menu. The following window is displayed:
Figure 298. NE MIB management
The following fields are displayed:
– Available backups on local server: gives the list of the backups available on the Craft Terminal,– Backup name: to enter the new backup name.
Three push buttons allow to choose the action with click on:
– Backup: performs the backup on the CT of the Mib present on the NE,– Restore: this function allows the managing system to restore the NE configuration database of the
managed system. Only one restore operation can be performed at the same time on a given NE.– Delete: this action allows to delete a backup of the NE database. The NE is not involved in this action.
The only effect is to delete the selected backup version stored in a specific directory of the FT server.
To activate an already restored MIB you click on Activate push button. Only at this point it becomesoperative on the NE.
To exit of the NE MIB management window, you click on Close push button.
To save or load the Mib to/from an external disk follow the indication of the “Basic 1320CT Operator’sHandbook” using the menu options of the Network Element Synthesis.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
386
01
957.140.602 V
SC.3:NE MANAGEMENT
/3AL 80755 BA AA
386
386
END OF DOCUMENT
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
1
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
1660SM REL.3.1 C.T. OPERATOR’S HANDBOOK
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Scope 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2 Target audience 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Acronyms and abbreviations 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.2 Glossary of terms 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 MAINTENANCE INTRODUCTION 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 MAINTENANCE OF THE PC 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 PROBLEMS WITH CRAFT TERMINAL 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Purpose of the procedure 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Procedure 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 CORRECTIVE MAINTENANCE (TROUBLESHOOTING) 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Purpose of the procedure 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Troubleshooting organization 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 On site Troubleshooting 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Troubleshooting by means of the Craft Terminal. 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Preliminary Concepts and Definitions 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 Alarms/states view Organization (subrack view) 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3 Alarm synthesis indication 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.4 Alarm Surveillance (AS) 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.5 Port View alarms 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.6 Board view alarms and states 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.7 Subrack and Rack view alarms 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.8 Equipment View alarms 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9 External Points alarms (HouseKeepings) 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6 UNIT REPLACEMENT WITH A SPARE 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 EQUICO unit replacement 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 ATM MATRIX 4X4 unit replacement 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
01 020520 S.MAGGIO ITAVE P.GHELFI ITAVE
1660SM REL.3.1
C.T. OPERATOR’S HANDBOOK
C. FAVERO
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
2
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
6.3 ATM MATRIX 8X8 unit replacement 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4 IP MATRIX unit replacement 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 UPGRADING WITH NEW HARDWARE 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 MATRIX substitution with MATRIXN 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 P4S1, S–41, L–41, L–42, S–161, L–161, L–162 substitution with P4S1N, S–41N,L–41N, L–42N , S–161N, L–161N, L–162N 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 FLASH CARD SUBSTITUTION 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
3
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
LIST OF FIGURES AND TABLES
FIGURESFigure 1. General Flow–chart for on site troubleshooting 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2. Power supply alarm 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3. Transmission network level structure 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4. Alarms/status view Organization (subrack view) 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5. Alarm pull down menu. 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6. Alarm Surveillance 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7. Example of SDH Port View alarms (without MSP schema) 29. . . . . . . . . . . . . . . . . . . . . . . . . Figure 8. Example of SDH Port View alarms (with MSP schema) 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 9. Example of ATM Port View alarms 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 10. Example of Ethernet Port View alarms 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 11. Example of SDH Board View alarms and status 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 12. Example of PDH Board View alarms and status 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 13. Example of Subrack view alarms and status 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 14. Example of Rack view alarm and status 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 15. Fans subrack alarms view 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 16. Example of Equipment View alarms and status 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 17. Example of External Points alarms and status 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 18. EQUICO unit replacement 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 19. ATM MATRIX 4X4 unit replacement without EPS protection 43. . . . . . . . . . . . . . . . . . . . . . . Figure 20. ATM MATRIX 4X4 unit replacement with EPS protection 44. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 21. FLASH CARD substitution 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLESTable 1. Alarms colors and Severity association 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2. Alarm Synthesis indication 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3. Domain Alarm Synthesis indication 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 4. Management States Control Panel. 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5. Alarm Surveillance information general description 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6. General aspect of alarms meaning and relevant maintenance actions 26. . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
4
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
5
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
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:
– 1320CT Basic Operator’s Handbook
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
Refer to the Section Introduction manual.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
6
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
7
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
2 MAINTENANCE INTRODUCTION
The maintenance procedures consist of the following steps:
– Maintenance of the PC. See Chapter 3 on page 9
– Problems with Craft terminal (shut–down and restart of the PC). See Chapter 4 on page 11.
– Corrective Maintenance (Troubleshooting). See Chapter 5 on page 13.
– Unit replacement with a spare. See Chapter 6 on page 41.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
8
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
9
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
3 MAINTENANCE OF THE PC
With regard to maintenance PC, refer to the constructor’s documentation.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
10
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
11
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
4 PROBLEMS WITH CRAFT TERMINAL
4.1 Purpose of the procedure
This procedure describes the Shut–down and restart the PC should the Craft Terminal SoftWare Productnot be working properly or not responding to the operator’s commands.
4.2 Procedure
In order to shut down the PC execute the command :
Start > Shut down
A window (Windows NT Security user dialog) is displayed. It permits to shut down the computer or restartit.
The same window is displayed pressing he keys <Ctrl> + <Alt> + <Del> simultaneously.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
12
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
13
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5 CORRECTIVE MAINTENANCE (TROUBLESHOOTING)
5.1 Purpose of the procedure
Troubleshooting involves the detection, location and correction of failures in the equipment and thereplacement of the defective parts.
5.2 Troubleshooting organization
The troubleshooting procedure is carried out with the help of some flow–charts and tables, reportedhereinafter. Anyway this method does not deal with the following aspects (which are to be deduced in otherways):
– faulty electronic alarm indication, processing and detection circuits– faulty wiring (back–panel, connectors, etc.)
The following interfaces are present to troubleshoot the equipment :
• Q3 interface for Telecommunication Management Network• F interface for Craft Terminal (Local or Remote)• Remote Alarm for Supervisory Center• LEDs on the units of the NE
Usually maintenance is firstly done via software (TMN or Remote Craft Terminal) to locate the faultyequipment and the faulty unit or the faulty path and then on site to physically solve the trouble.
The Maintenance can be done :
• from a TMN network management center• from a Remote Craft Terminal (RCT) management center• from a station supervisory center• on site
TMN network management center: by means of the TMN the maintenance technician can see thealarms sent by each equipment of the managed network (see the relevant TMN handbooks).
Remote craft terminal: the operator, connected to a local NE , can remotely manage and troubleshootinga network composed of max 32 NEs included itself. This handbook is used.
Station supervisory center: the maintenance technician refers to the Remote Alarms received from theequipment in a centralized office of the station i.e. :
– T URGENT (MAJOR and CRITICAL), T NOT URGENT (MINOR): remote alarms pertaining to theurgent, not urgent alarm type.
– TOR, TAND: remote alarms respectively due to the decrease or loss of one or both station powersupply DC voltages.
– INT: Remote alarm pertaining to the local (internal) alarm typeWhen 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– LOSQ2: remote alarm due to loss of communication with Mediation Device. Not operative.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
14
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Depending on the supervisory center organization, it is possible to locate the equipment in troubles andto detect the failure type and source.
On site : the operator is on site in case :
1 ) the equipment is not managed by a TMN or by a Remote Craft terminal (RCT)
2 ) the equipment is not reachable by the remote manager (TMN or RCT) and is therefore isolated
3 ) link problems are present
4 ) the trouble has been located and a substitution is necessary
In case 1 ) , 2 ), 3 ), the alarmed equipment is checked by means of the local Craft Terminal and of rackLED indications and station buzzers.
The NE is provided with LEDs which indicate:
Units Alarms:
Each port card or access card of the equipment is provided with a bicolor LED (green/red) or multicolorLED (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 green, in service unit
Multicolor LED indicates:– when red, internal failure (indicates that the unit concerned must be replaced)– when green, in service unit– when yellow, means that the unit is part of an EPS schema and its status is “standby”
ATM unit Alarms:
All the alarm detected on the unit are related to the ATM traffic management; on the front coverplate arepresent optical indication (LEDs) with the following meaning (from the top to the bottom):
• Red LED : detection of an MAJOR or CRITICAL (URGENT) alarm
• Red LED : detection of a MINOR (NOT URGENT) alarm
• Yellow LED : alarm condition ATTENDED
• Yellow LED : detection of an ABNORMAL operative condition.
• Yellow LED : detection of an WARNING (INDICATIVE) alarm
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
15
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Centralized Equipment Alarms:
All the alarms detected on the units are collected by the EQUICO unit which will deliver centralized opticalindications (by means of LEDs on its front coverplate). Specifically, from the top to the bottom :
• Red LED: detection of an URGENT (MAJOR and CRITICAL) alarm
• Red LED: detection of a NOT URGENT (MINOR) alarm
• Yellow LED: alarm condition ATTENDED
• Yellow LED: detection of an ABNORMAL operative condition. Type: active loopbacks, forcingthe unit into service, laser forced ON or OFF, try to restore after ALS
• Yellow LED: detection of an INDICATION (WARNING) alarm
The analysis of these LEDs permits to detect the alarm type (Urgent – Not Urgent – Indication) andrelevant condition (Abnormal condition, Attended).In case of URGENT or NOT URGENT alarm, after having located the alarmed equipment, the alarmcondition can be ”attended” by pressing the relevant alarm storing push button on the EQUICO unit.
This condition causes:
– On the rack
• the YELLOW LED to light up• the RED LED to go off
– On the front coverplate:
• yellow LED (ATTENDED) to light up• red LEDs NOT URGENT (MINOR) and URGENT (MAJOR and CRITICAL) to turn off (free to
accept other alarms)If both LEDs are on, the Attend command should be given twice : one for attending the NOTURGENT (MINOR) alarm and one for attending the URGENT (MAJOR) alarm.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
16
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.3 On site Troubleshooting
The trouble–shooting operation proceeds according to the information indicated in the flow–charts:
– Figure 1. on page 17: General flow–chart
– Figure 2. on page 18: Power supply alarm
and according to para.5.4 on page 19.
As indicated in the flow–charts the troubleshooting operation is done by means of the Craft Terminal, andof the optical indicators (LEDs) present on the NE.
The Craft Terminal is cord–connected to the relative connector on the EQUICO unit front coverplate (Finterface).
The Craft Terminal applications provide detailed information on the alarm state thus facilitating faultlocation and subsequent removal as indicated in para. 5.4 on page 19.
To correctly execute the troubleshooting operations the technician must know the exactequipment configuration (see Equipment Configuration applications on the Craft Terminal).
The aim of the flow–charts which follow and of the maintenance tables is to locate the faulty unit and toreplace it with a spare as well as to locate a failure along the link.
The flow–charts/tables should be also consulted when the unit LEDs flash, because the flashing conditionmight be due to external alarm causes usually related to line problems.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
17
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
START
AN ALARMIS PRESENT
IN CASE OF URGENT OR NOT URGENT ALARM
ON THE EQUICO UNIT
IS THE
EQUICO
BICOLOR LED RED?
NO
IS THE
RED LED URGENT (MAJOR)
NO
ON ?
THROUGH PUSH–BUTTON
RESET THE UNIT
DOESTHE ALARM
CONDITIONPERSIST ?
NO TRANSITORY
FAILURE
THE UNIT IS FAULTY. REPLACE IT ACCORDINGTO THE DESCRIBED PROCEDURE
IS
ONE OF THE BICOLORLEDS INDICATING UNIT
FAILURE RED?
NO
YES
REPLACE THE UNIT IN ALARM.BY CONNECTING THE PC AND
ACCORDING THE TYPE OF FAILURE
THE FAULTY UNIT CAN BEREPLACED (OR NOT) IN CASE
OF LOW TRAFFIC .
END
CONNECT THE PC TO THEEQUIPMENT AND, ACCORDING TOTHE TYPE OF DETECTED ALARM,
PROCEED AS STATED IN
END
IS THE
NOT URGENT (MINOR) YELLOW
LED ON ?
NO
YES
CONNECT THE PC TO THE EQUIPMENT,
END
AFTER HAVING DETECTED THE TYPEOF FAILURE, ESTABLISH IF
INTERVENTION MUST BE IMMEDIATE ORNOT AS STATED IN THE RELATIVE
YELLOW ALARM IS ON. MAINTENANCE OPERATION
MUST BE PERFORMEDON THE EQUIPMENT CONNECTED
TO THE LOCAL ONE. CONNECT THE PC AND ACCORDING TO
THE TYPE OF ALARM PROCEEDAS INDICATED IN
YES
YES
YES
YES
YES(see chapter 6 on page 41)
PARA 5.4 ON PA GE 19
ATTEND IT WITH THE BUTTON
EQUICO UNIT
AND THE TRAFFIC DAMAGE
EQUICO UNIT
IN EQUICO UNIT
THE INDICATION (WARNING)
PARA 5.4 ON PA GE 19
PARA 5.4 ON PA GE 19
Figure 1. General Flow–chart for on site troubleshooting
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
18
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
START
ISREMOTE ALARM
TAND PRESENT ?
(N.B.)
NO
STATION POWER
SUPPLY FAILURE
END
OVERLOAD LIKELY TO HAVEBEEN CAUSED BY ONE OF THE
ASSEMBLY UNITS.
REMOVE ALL THE UNITS
INSERT THEM BACK ONEAT A TIME TILL THE ONE
CAUSING THE FAILURE IS DETECTED.HENCE REPLACE IT.
END
ALL LED’S OFF
N.B. IF THE REMOTE ALARMS ARE NOT UTILIZED CHECK FOR PRESENCE OF STATION POWER SUPPLY.
SHOULD IT HAVE FAILED THEN ALL THE UNIT’S LEDS WILL BE OFF (FOLLOW OUTPUT “YES” OF THEFLOW–CHART).
IF POWER SUPPLY IS PRESENT PROCEDE WITH OUTPUT “NO”.
NO
YES
YES
SUBSTITUTE THE FUSE ON THE CONGI UNIT
ARE LEDS ACTIVE?YES
TRANSITORY OVERLOAD
FROM THE SUBRACKAND SUBSTITUTE THE FUSE
IF NECESSARY.
SUBSTITUTE THE FUSE IF NECESSARY.
WARNING!
Before removing CONGI unit from subrack, switch–off the relevant Station Battery Fuse Breakerpresent at the top of the Rack or in the Station Distribution Frame; subsequently remove the station battery cable if necessary and then extract the CONGI unit.
Figure 2. Power supply alarm
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
19
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4 Troubleshooting by means of the Craft Terminal.
The troubleshoot proceeds checking the detailed information on the NE alarm by means of the craftterminal.
The information on the NE alarm will be mainly obtained by means of the craft terminal through the AlarmSurveillance data and the alarms/status indications presented in the various views, depending on thelevel of the structure under observation.Navigation across the various level views is done from higher to lower levels, by double clicking on theobjects (see instructions on “NE management” section).The NE hierarchy is organized in the following order: NE > rack > subrack > board > port > TP.
The troubleshoot procedure with the the Craft Terminal consists of the following steps:
a ) The alarms/status view organization for the equipment is shown in Figure 4. pg. 21. Observe theactive alarms on the Severity Alarm Synthesis, Domain Alarm Synthesis and ManagementStates Control Panel always present on the window (it resumes all the NE alarms).Table 2. on page 22 describes the meaning of these alarms/statuses and the relevant maintenanceactions.
b ) in case of alarm presence, access the Alarm Surveillance to troubleshoot. This application givesthe details of the detected alarms and helps for their localization.Para 5.4.4 on page 24 describes this view.
c ) It is possible to analyze the detailed alarm presence on the TPs of each ports of the NE, followingthe indication of para 5.4.5 on page 28.
d ) It is also possible to check alarm and status at Board view, Subrack view and Equipment vieware also supplied following the indication of para 5.4.6 on page 33 and para 5.4.8 on page 38.
e ) Eventual housekeeping alarms can be localized following the indications given in para. 5.4.9 onpage 39.
f ) These above said paragraphs describe general aspect of alarms meaning and relevant maintenanceactions 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 pulldown menu (see “NE management” section).
In case of unit replacement, follow the indications reported in Chapter. 6 on page 41.
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 theopposite direction of the failed link.WARNING: During this phase the operator has to pay attention when working with fibers and connectors.The ABNORMAL indication inform the operator of the ALS forced condition.After having completed the maintenance, enable the ALS.The ALS states are indicated in the port view, as described in para. 5.4.5 on pg. 28.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
20
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4.1 Preliminary Concepts and Definitions
The following concepts and definitions are considered useful to facilitate maintenance operations with theaid of the previously indicated tables.
The various units specified in the synchronous multiplexing hierarchy imply structuring the Transmissionnetwork 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 physicallevel (Transmission media) and Transmission section level. The sections can be either regeneratoror 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: LineLOS, LOS, B2etc.).
– Path level It concerns the data transfer between the access points and the path. It does not dependon the service nor on the type of Transmission media. It constitutes the circuit level support. The pathcan 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 theEOW channels of the SDH frame. The alarms listed in the cited tables, where path leveltroubleshooting is required, belong to this level (example:TUAIS, TU LOP).
– Circuit level. This level concerns the transfer of information between the access points and thecircuit proper. It is a direct support for the telecommunication services. It superimposes the SDH function and is considered as the transport agent hence no SDH order–wire channel associatedfunctions are required. An example of this level alarm is Tributary LOS.
The above level structuring in the Transmission network is depicted in Figure 3.
TRIBUTARIES SDH MUX
G.703
STM–NREGENERATOR
SDHMUX
STM–N
TRIBUTARIESSDH MUX
G.703
STM–N
RSOHREGENERATOR
SECTION
RSOHREGENERATOR
SECTION
MSOHMULTIPLEXER
SECTION
MSOHMULTIPLEXER
SECTION
POH PATH
MSOHMULTIPLEXER
SECTION
Figure 3. Transmission network level structure
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
21
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4.2 Alarms/states view Organization (subrack view)
Severity alarmssynthesis
Message/status area
View area
View title
Domain alarms synthesis
Managementstatus control panel
Menu bar
Administrativestate indications
Boards
Alarms
Figure 4. Alarms/status view Organization (subrack view)
the critical (CRI) or major (MAJ) alarms indicate severe alarms that could have impact on thecurrent traffic (interruption or degrade). Thus requiring a rapid intervention to restore theregular working condition of the equipment.
A message under the mouse facility provides the alarm or status complete denomination. A messageappears in the message area in the bottom left corner of the view.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
22
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4.3 Alarm synthesis indication
Alarms and Statuses synthesis are given in all the screens.
The alarms CRI, MAJ, MIN, WNG, IND are part of the Severity Alarms Synthesis area, presented inTable 2. on page 22.
The alarms EXTP, EQP, TRNS are part of the Domain Alarms Synthesis area, presented inTable 3. onpage 23.
The alarms SUP, LAC, COM, OS, MGR, NTP and AC are part of the Management States Control Panel,presented in Table 4. on page 23.
All these indications (except for SUP, LAC, COM, OS, MGR and NTP) are the summaries of particulartypes of alarms detected by the equipment, hence the specific cause of alarm is to be found as indicatedin the following paragraphs: 5.4.4, 5.4.5, 5.4.6, 5.4.7, 5.4.9.
Table 1. reports the association between the colors of the Alarms and their Severity.
For the Domain Alarms Synthesis the color corresponds to the highest severity among the set of theactive alarms for the relevant domain, according to the same rules of previous Table 1.
Table 1. Alarms colors and Severity association
Alarm Color Severity
RED CRITICAL
ORANGE MAJOR
YELLOW MINOR
CYAN WARNING
WHITE INDETERMINATE
GREEN NO ALARM
Table 2. Alarm Synthesis indication
Mnemonic Alarm/Status Description Maintenance
CRI Critical alarmSynthesis of alarms that needs immediate trouble-shooting (typical: NE isolation). NB1.See detailed indication in the following para.
Synthesis of alarms that needs immediate trouble-MAJ Major (Urgent) alarm shooting. NB1. See detailed indication in the follow-
ing para.
MIN Minor (Not urgent) alarmSynthesis of alarms for which a delayed troubleshoot-ing can be defined. NB1.See detailed indication in the following para.
WNG Warning alarmSynthesis of alarms due to failure of other NE in thenetwork. NB1.See detailed indication in the following para.
IND Indeterminate alarmSynthesis of alarms not associated to the previousseverities. Not operative.See detailed indication in the following para.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
23
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Table 3. Domain Alarm Synthesis indication
Mnemonic Alarm/Status Description Maintenance
EXTPExternal Point
(Housekeeping alarm)
Check the relevant station alarm associated to theinput housekeeping indication. See detailed indicationin the following para.
SYNC Synchronization alarmSynthesis of alarms of the Synchronization domain.
See unit detailed indication in the following para.
EQP Equipment alarmSynthesis of alarms of the Equipment domain.
See unit detailed indication in the following para.
TRNS Transmission alarmSynthesis of alarms of the Transmission domain.
See unit detailed indication in the following para.
Table 4. Management States Control Panel.
Mnemonic Description Maintenance
SUP Supervision state
GREEN: NE is under supervision.
BROWN: NE is not under supervision.
Used in the OS.
Local Access State
GREEN: Indicates that the Craft Terminal has the OSpermission to manage the NE (granted).
CYAN: Indicates that the Craft Terminal has not theOS permission to manage the NE (denied).
COM NE unreachable/unreachable
GREEN: Identifies the “Enable” operational state ofthe connection between NE and Craft Terminal (SDHservice link up)
RED: Identifies the “Disable” operational state of theconnection between NE and Craft Terminal (SDH ser-vice link down)
OS Operational System Isolation
GREEN: Indicates that the N.E. is not managed by the1353SHCYAN: Indicates that the N.E. is managed by the1353SH.
MGR Manager level
GREEN: Indicates that the N.E. is not managed bythe 1354RM
CYAN: Indicates that the N.E. is not managed by the1354RM
NTP Network Time Protocol
GREEN: NTP protocol enabled and both NTP servers(main and spare) are unreachable.
BROWN: NTP protocol disabled.
CYAN: NTP protocol enabled and at least one NTPservers (main or spare) are reachable.
AC Abnormal Condition
GREEN: normal operating condition.
CYAN: detection of an ABNORMAL operative condi-tion. Type: active loopbacks, forcing the unit into ser-vice, laser forced ON or OFF, try to restore after ALS
NB1: Alarm Severity Assignment Profile can modify the assignment of each alarm root to the varioussynthesis.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
24
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4.4 Alarm Surveillance (AS)
– In case of alarm presence, access the Alarm Surveillance (AS) to troubleshoot. For this purposeselect the Diagnosis pull down menu. With the Alarm pull down menu (see Figure 5. ). It is possibleto show all the NE Alarms or filter the alarms report, for example displaying only the alarms of aspecific domain (i.e. only alarms of the Equipment domain).
Figure 5. Alarm pull down menu.
After the selection a list with a synthesis of the Alarm Surveillance is presented and immediately after alsothe detailed list of the Alarm Surveillance (see Figure 6. ).In the synthesis list it is possible to filter the data to show with the detailed view, double clicking on theselected row of the sublist of Figure 6.
Figure 6. Alarm Surveillance
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
25
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Detailed information of each alarm are supplied.The alarms scenario is indicated by the colors of the alarms and by the information displayed in the table.For instance, if an alarm is still active, the whole row has the same color of its relevant “Perceived Severity”;else if it has been cleared, the color of the row is green (except the “Perceived Severity”). The sameinformation is reported in the “Clearing Status” column.
In the following are shortly described the main information obtained in the AS view, starting from the leftcolumn:
Table 5. Alarm Surveillance information general description
TITLE DESCRIPTION
– Perceived SeverityThe severity assigned to the alarm is indicated, with the relevant color,i.e.: MAJOR, MINOR, WARNING....
– Event date and time Indicates year, month, day and hour of the alarm.
– Friendly NameIdentify the rack, subrack, board, port, and TP in which the alarm is detected,i.e.: / r01sr1sl09/#port01–E1S
– Event TypeIndicates the family type of the alarm as subdivided in the ASAP list, i.e.:EQUIPMENT, COMMUNICATION,
– Probable CauseThe fault/problem is indicated, i.e.: loss of signal, transmitter degraded, re-placeable unit missing,resource isolation, ...
– Reservation StatusIndicates if the alarm is reserved (RSV) or not (NRSV) according security ma-nagement.
– Clearing statusIndicates if the alarm condition is terminated (CLR) or is still active (NCLR).If cleared it has a green background,
– Acknowledge statusIndicates if the alarm has been acknowledge (ACK) with the button on theEQUICO unit or not ( NACK).
– Correlated notification flag
Not used
– Repetition counter Not used
The information supplied help the operator during the troubleshooting operation.
Table 6. on page 26 supply general indications of alarms meaning and relevant maintenance actions thatcan 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. Theyare available for the customer by connecting them to a dedicated subrack connector.
Detailed description of this application is given in the AS Operator’s Handbook.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
26
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Table 6. General aspect of alarms meaning and relevant maintenance actions
PROBABLE CAUSE
NAME AND/OR ACRONYMOF DISPLAYED ALARM
MAINTENANCE
Loss of signal (LOS) Check line
Transmitter Signal (TF) Replace unit
Transmitter degraded (TD) Replace unit when possible (laser degrade)
Loss of frame (LOF) Check line (alignment problems due to line error)
AIS Check connected equipment
Excessive BER (EBER) Check line (excessive line BER)
Degraded Signal (DS) Check line (line signal degrade)
Loss of Pointer (LOP) Check line
Payload Mismatch (PLM) Configuration error
Far End Received Failure(FERF)
Check far–end equipment
Server Signal Failure (SSF) Check all the TU path. Alarm indicates AIS signal received onthe TU
Frequency offset (DRIFT) Check reference and connection between it and the equipment
Loss of timing source (LOSS) Check reference and connection between it and the equipment
Resource Isolation Check connection between NE and Craft Terminal
Communication SubsystemIsolation (CSF)
Check Communication configuration (LAPD)
Unequipped (U)
Referred to Signal LabelConfiguration error
Unconfigured EquipmentPresent (UEP)
Unit inserted but not declared
Internal Communication Prob-lem
Reset NE. If persists substitute EQUICO unit
URU – Underlying ResourceUnavailable
Insert the board
PM_AS– PerformanceMonitoring Alarm Synthesis
Check path / line section interested to the indication.
CPE–Communication protocolerror
Check MSP protocol (architecture type, switch fail)
LOMF – Loss Of MultiFrame Check payload structure
PTM– Path Trace Mismatch Not operative in current release
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
27
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
MAINTENANCEPROBABLE CAUSE
NAME AND/OR ACRONYMOF DISPLAYED ALARM
AUXP Check far–end equipment
Remote Node Transmissionerror (RNTE)
Check far–end equipment
PROBABLE CAUSE
NAME AND/OR ACRONYMOF DISPLAYED ALARM
MAINTENANCE
Board alarms
Unit missing (RUM) Insert missing unit
Unit Problem (RUP) Replace unit
Unit type mismatch (RUTM) Insert right unit (unit inserted into a slot set with another type ofunit)
Version mismatch (VM) Update software version by means of download
Cooling Fans Failure (CFF) Check the fan units and substitute the faulty one
LAN problem (LAN) Check LAN interconnection or substitute CONGI unit
Internal communicationproblem (ICP)
Internal dialogue problem in the EQUICO unit. It indicates a tempo-rary condition which will be restored. If the condition persists it is dueto a unit hardware failure: in this case it will activate the RUP alarm
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
28
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4.5 Port View alarms
It is also possible to analyze the detailed alarm presence on the TPs of each ports of the NE, followingthe indication of the Port View chapter on the previous Section of this Handbook.
Figure 7. to Figure 10. are examples of a Port view.For each TP of the Port a detail of the relevant alarms is presented.
On the port view the messages displayed at the bottom provide information about:
– MSP protection (if enable); refer to Figure 8.
– Automatic Laser Shutdown state; refer to Figure 7.
– State of the connection for Ethernet port (available only if an ethernet port has been selected); referto Figure 10.
A message under the mouse indicator provides the name of the alarm or object on which it is located, inthis way facilitating the identification of the alarm or status or object.
The non–alarmed condition of an alarm icon is represented by a green color and a “–” sign in the box.The alarmed condition is represented by the color of its severity (as assigned by the ASAP) and an “X”sign in the box.
The alarms which can be found in the Port view are listed in Table 6. pg.26, where the relevantmaintenance actions are reported too.
The information regarding ALS states and Laser state useful for operators safety purpose arereported in the following:
ALS states:
Inactive = No ALS has been activated (Off) or the laser has been Forced ON/OFF.
In test = The laser restart has been automatically activated .
Active = The ALS has been activated (On).
Undefined = The ALS is not present (not created).
Laser state:
On = all OK or ALS not present (not created).
Off = Laser off (when ALS is created).
Forced on = ALS forced on by operator command.
Forced off = ALS forced off by operator command.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
29
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Alarms
Protection message
Mouse message
TP’s
Alarms
Figure 7. Example of SDH Port View alarms (without MSP schema)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
30
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Alarms
Mouse message
TP’s
Alarms
MSP Iinformation message
Figure 8. Example of SDH Port View alarms (with MSP schema)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
31
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Alarms
Mouse message
TP’s
Figure 9. Example of ATM Port View alarms
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
32
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Alarms
Mouse message
TP’s
State of connection for Ethernet port
Figure 10. Example of Ethernet Port View alarms
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
33
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4.6 Board view alarms and states
The alarm and status indications at Board level can be obtained, following the indication of the Board Viewchapter on the previous Section of this Handbook.
Figure 11. and Figure 12. show a examples of Board view.
The alarm and status indications depend on the unit type; for example SDH units is organized on two levelsof presentation (in the first is selected one of the available ports) and each view contains dedicatedindications.An alarm box is displayed on each port, to indicate whether the port is alarmed.
An indication in the ”message/status area” provides information about the board Administrative State:“in–service” or “out–of–service”.
The alarms of the board are reported at the bottom of the ”message/status area”, by means of variousboxes containing relevant acronyms.The non–alarmed condition of an alarm icon is represented by a green color.The alarmed condition is represented by the color of its severity (as assigned by the ASAP).
A message under the mouse indicator provides the name of the alarm or object on which it is located, inthis way facilitating the identification of the alarm or status or object.
In the view is present the Administrative State information: “in service” or “out of service”.
The alarms which can be found in the Board view are listed in Table 6. page 26, where the relevantmaintenance actions are reported too.
In the view can also be present EPS indications.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
34
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
port alarm synthesis
Board alarms
Administrative State
Figure 11. Example of SDH Board View alarms and status
Board alarms
Administrative StateEPS State
Figure 12. Example of PDH Board View alarms and status
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
35
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4.7 Subrack and Rack view alarms
The alarms and status indications at subrack and rack level can be obtained, following the indicationsgiven on the previous Section of this Handbook (”NE management”).
Figure 13. and Figure 14. show an examples of Subrack and Rack view.
An alarm box is displayed on each board, to indicate whether the board is alarmed. This board alarmsummarization is activated when one of the board alarms (those reported at the bottom of the Board view)is active.
A “lock” symbol on a board indicates that it is “in–service”. Else, the lack of this symbol indicates its“out–of–service” state . (Administrative State information).
A message under the mouse indicator provides the name of the alarm or object on which it is located, inthis way facilitating the identification of the alarm or status or object.
Severity alarmssynthesis
Message/status area
iew area
View title
Domain alarms synthesis
Managementstatus control panel
Menu bar
Administrativestate indications
Boards
Alarms
Figure 13. Example of Subrack view alarms and status
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
36
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Severity alarmssynthesis
Message/status area
View area
View title
Domain alarms synthesis
Managementstatus control panel
Menu bar
Administrativestate indications
Fans subrack
Alarms
Figure 14. Example of Rack view alarm and status
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
37
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4.7.1 Fans Subrack alarms view
To obtain Fan Subrack alarms indications click twice with the mouse on the relevant subrack drawingin the rack level view.
Figure 15. on page 37 is presented:
– Battery Failure (BF): check that the station battery cables are right connected
– Cabling Problem (CAP): check that the alarms cable between the Fans Subrack and the CONGIunit is right connected; check also the configuration in the Equipmentmenu (Connected FAN to CONGI#10 or Connected FAN to CONGI#12)
– Temperature Out of Range (TOOR): verify the Fan unit alarm and in presence of faulty substitute therelevant unit; clean also the Dust filter if necessary.
Figure 15. Fans subrack alarms view
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
38
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4.8 Equipment View alarms
The alarm indications at Equipment level can be obtained, following the indication of the Equipment Viewchapter on the previous Section of this Handbook.
Figure 16. shows the Equipment view, with the alarm indications presented:
– Fuse Failure (FF): Substitute the fuse in the CONGI unit and search for a cause.
– AND Battery Failure (ABF): Failure of the Service Power Supply connected to the CONGI Rackconnector.
– Backplane Failure (BKF): Substitute the Termination BUS
– Specific Hardware Diagnostic (SHD): Indicate the presence of link failure between the MATRIX andone of the units; for details choose the Internal Link Monitor option of theDiagnosis menu.
These alarms can be observed at OS level.
Equipment alarms
Figure 16. Example of Equipment View alarms and status
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
39
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
5.4.9 External Points alarms (HouseKeepings)
The alarms and status indications relevant to External Points (housekeepings) can be obtained, followingthe indication of the External Points chapter on the previous Section of this Handbook.
The external state represents the alarm state. ”On” when the alarm is raised, else ”Off”.If the external point is active (On), a red flag is represented near the state of the concerned point.
In case of input point the alarm state is reported also in the user label column, by the box near its name:green color and sign “–” –––> means non–alarmed condition.the change of color, as assigned by the severity (ASAP) –––> means alarmed condition.
Figure 17. Example of External Points alarms and status
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
40
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
41
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
6 UNIT REPLACEMENT WITH A SPARE
No particular indication is given as to spare handling which is left to the Maintenance Administration.
The replacement procedures are executed as follows:
– Hardware set the spare unit exactly as the unit to replace. Settings are specified in the MSdocuments. Here a layout figure indicates the exact location of all the setting arrangements and atable 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 unit refer to paragraph 6.1 on page 41.
– With regard to the ATM MATRIX 4X4 unit refer to paragraph 6.2 on page 43.
– With regard to the ATM MATRIX 8X8 unit refer to paragraph 6.3 on page 45.
– With regard to the IP MATRIX unit refer to paragraph 6.4 on page 46.
– When upgrading an equipment with “New Hardware” (for example MATRIXN unit) that substitute theold units (for example MATRIX unit), follow the indication given in paragraph on page .
WARNING: In order to avoid short–circuit, before substituting the CONGI unit,switch–off the relevant Station battery fuse breaker . Subsequently remove the StationBattery cable and extract the CONGI unit.
WARNING: before inserting the new spare unit carefully check the integrity of the relativeconnectors.Don’t insert the units that have been damaged during the transport/storing or in a phasebefore their replacing.
6.1 EQUICO unit replacement
Various procedures are utilized to replace a EQUICO faulty unit. They depend on the type of sparesavailable:
• Spare without software installed. This is the normal condition.
• Spares with installed software, belonging to the same type of equipment and with SW releaseidentical to the unit to replace
• Spares with installed software, belonging to the same type of equipment but with SW releasediffering from the one of the unit to replace, or belonging to other types of equipment orunknown.
– CONGI unit version (read NOTE in Figure 18. on page 42)
– MIB store in the Craft Terminal or O.S.
The flow–chart of Figure 18. on page 42 illustrates the procedures to follow for the EQUICO substitution.
The procedure aim is to replace the faulty unit without causing configuration changes and/or unwantedfaults; when not possible this is indicated in the flow chart.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
42
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ
ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ
ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ
unit without software
Download the NE relevant software releasewith SIBDL procedure
(see SIBDL section)
software of the same release and NE
END
unit with different software
Download the NErelevant software release
(see NE management section)with normal dowload procedure.
”Activate” the sent MIB
I1–1 OFF I1–2 OFF
INSERT AGAIN THE NEWEQUICO
NOTES:
NB2: The ”Comm/Routing” tables are automatically retrievedonly with CONGI starting from version 3AL 78830AAACOtherwise the ”Comm/Routing” tables must be configurated manually using the Craft Terminal
Is the MIB storedin the Craft Terminal?
YESNO
MIB containing the correctconfiguration (NB1)
From O.S. send the saved
MIB containing the correctconfiguration (NB1)
From C.T. send the saved
(see NE management section)
”Activate” the sent MIBFrom O.S.
From C.T.
NEW UNIT HW CONDITION: NEW UNIT HW CONDITION: NEW UNIT HW CONDITION:
I1–1 ON I1–2 OFF
HW–PRESET THE NEW UNIT WITH:
I1–1 OFF I1–2 ON
REMOVE AND HW PRESET THE NEW UNIT WITH:
Substitute EQUICOunit
NB1
INSERT THE NEW UNIT
INSERT THE NEW UNIT AGAIN
(Reset Data Base)
(Reset Data Base and upload Comm/Routing Tables)
REMOVE AND HW PRESET THE NEW UNIT WITH:(Normal operating condition)
Figure 18. EQUICO unit replacement
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
43
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
6.2 ATM MATRIX 4X4 unit replacement
Two different procedure are available for ATM MATRIX 4X4 substitution according to the EPS schema.
The flow–charts of Figure 19. on page 43 illustrates the procedures to follow for the ATM MATRIX 4X4when it is not EPS protected.
The flow–charts of Figure 20. on page 44 illustrates the procedures to follow for the ATM MATRIX 4X4when it is EPS protected.
The procedures aim is to replace the faulty unit without causing configuration changes and/or unwantedfaults.
NOT EPS PROTECTEDATM MATRIX unit
END
From SMART application ”Restore” The Data Base
I1–4 OFF
HW–PRESET THE NEW
I1–4 ON
UNIT WITH:
REMOVE AND HW–PRESET THE NEW UNIT WITH:
Substitute the faulty unit
INSERT THE NEW UNIT ANDWAIT UNTIL THE ACCESS
WILL BE RETURNED TO THE C.T.
with a spare ATM MATRIX
TO RESET THE DATA BASE
INSERT THE NEW UNIT ANDWAIT UNTIL THE ACCESS
WILL BE RETURNED TO THE C.T.
previously saved (see ” ATM OPERATOR’S HANDBOOK)
or otherwise re–configure all the ATM connections
Figure 19. ATM MATRIX 4X4 unit replacement without EPS protection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
44
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
EPS PROTECTEDATM MATRIX unit
END
The ”Spare ” unit become active
FAILUREON SPARE
FAILUREON MAIN
SubstituteATM MATRIX unit
END Substitute the faulty uni
Figure 20. ATM MATRIX 4X4 unit replacement with EPS protection
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
45
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
6.3 ATM MATRIX 8X8 unit replacement
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 referto flow chart of Figure 19. on page 43 and Figure 20. on page 44.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
46
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
6.4 IP MATRIX unit replacement
For IP MATRIX unit replacement refer to the specific Operator’s Handbook.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
47
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
7 UPGRADING WITH NEW HARDWARE
In the next paragraphs is indicated the procedure to follow when upgrading an equipment with “NewHardware” .
The new Hardware is identify by the “N” letter at the end of the acronym unit (for example MATRIXN isthe new version, MATRIX without “N” is the old version).
This procedure permits, if the equipment is EPS protected and inserted in a protected network (linear orring protection), to maintain the system “in service”
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
48
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
7.1 MATRIX substitution with MATRIXN
According to the MATRIX EPS protection scheme different procedure are available:
[1] Upgrading with a new MATRIXN EPS not protected
Substituting the old MATRIX all the traffic is lost!
• Remove the old MATRIX in slot 23 from the subrack
• 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.
• Verify that the RUTM alarm disappear
[2] Upgrading with a new MATRIXN EPS protected
• Remove first the Stand–by MATRIX 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 fromthe list then click on ok.
• Verify that the RUTM alarm disappear
• Force the EPS Switching to the Stand–by MATRIXN by selecting the Switch option from theEPS menu. For details see the paragraph “Switching EPS” in the “NE MANAGEMENT” sectionof this Handbook.
• After having verify that the MATRIXN (previously in Stand–by) is now working, remove theMATRIX 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 fromthe list then click on ok.
• Verify that the RUTM alarm disappear
• The decision to force again the EPS MATRIXN switching to restore the original workingcondition is left to the operator.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
49
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
7.2 P4S1, S–41, L–41, L–42, S–161, L–161, L–162 substitution with P4S1N,S–41N, L–41N, L–42N , S–161N, L–161N, L–162N
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 canbe applied to substitute the S–41, L–41, L–42, S–161, L–161, L–162 units respectively with S–41N,L–41N, L–42N , S–161N, L–161N, L–162N units.
• Remove the old unit( example P4S1 ) from the subrack
• Insert the new unit (example P4S1N) into the subrack slot previously occupied by the old unit;on Craft Terminal a RUTM (unit type mismatch) alarm will be present.
• On Craft Terminal in the Subrack level view select the slot where the new unit has been inserted
• Select the Modify option from the Equipment menu and select the acronym of the new unit( in our example P4S1N) from the list, then click on ok.
• Verify that the RUTM alarm disappear
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
50
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
51
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
8 FLASH CARD SUBSTITUTION
The FLASH card used up to rel. 2.0A (80 Mbytes) 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 ( flow–chart of Figure 21. on page 52) executethe following instruction:
a ) Save the MIB as explained in Section 3 (NE MANAGEMENT), Paragraph “Mibmanagement” of this Manual.
b ) Create and install the enhanced software package (SDH+ATM/IP) as explained in Section3 (NE MANAGEMENT), Paragraph “ NE Software package installation Procedure“ of thisManual.
The flow–chart of Figure 21. on page 52 illustrates the procedures to follow for the FLASH cardsubstitution without causing loss of traffic.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
52
01
957.140.602 V
SC.4:NE MAINTENANCE
/3AL 80755 BA AA
52
52
Download the NE relevant software packagewith SIBDL procedure
(see SIBDL section)
END
”Activate” the sent MIB
I1–1 OFF I1–2 OFF
INSERT AGAIN THEEQUICO IN THE SUBRACK
NOTES:
NB2: The ”Comm/Routing” tables are automatically retrievedonly with CONGI starting from version 3AL 78830AAACOtherwise the ”Comm/Routing” tables must be configurated manually using the Craft Terminal
Is the MIB storedin the Craft Terminal?
YESNO
MIB containing the correctconfiguration (NB1)
From O.S. send the saved
MIB containing the correctconfiguration (NB1)
From C.T. send the saved
(see NE management section)
”Activate” the sent MIBFrom O.S.
From C.T.
I1–1 ON I1–2 OFF
HW–PRESET THE EQUICO UNIT WITH:
I1–1 OFF I1–2 ON
Extract the EQUICOunit
NB1
INSERT THE EQUICO UNIT IN THE SUBRACK
SUBSTITUTE THE OLD FLASH CARDWITH A NEW ONE
EXTRACT AND HW PRESET THE EQUICO UNIT WITH:
INSERT THE EQUICO UNIT IN THE SUBRACK
EXTRACT AND HW PRESET THE EQUICO UNIT WITH:
(Reset Data Base)
(Normal operating condition)
(Reset Data Base and upload Comm/Routing Tables)
Figure 21. FLASH CARD substitution
END OF DOCUMENT
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
1
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
1660SM REL.3.1 C.T. OPERATOR’S HANDBOOK
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Scope 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2 Target audience 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Acronyms and abbreviations 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.2 Glossary of terms 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 DOWNLOAD WITH SIBDL 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Purpose of the procedure 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.1 SIBDL download procedure 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 CONFIGURATION FOR SIBDL 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Purpose of the procedure 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 Remote Access Service configuration (only needed for Windows NT environment) 11. . 3.1.2 Serial Cable Modem configuration for Windows NT environment 11. . . . . . . . . . . . . . . . . . 3.1.3 Serial Cable Modem configuration for Windows 2000 environment 12. . . . . . . . . . . . . . . . .
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
01 020520 S.MAGGIO ITAVE P.GHELFI ITAVE
1660SM REL.3.1
C.T. OPERATOR’S HANDBOOK
C. FAVERO
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
2
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
LIST OF FIGURES AND TABLES
Figure 1. SIBDL download procedure – step 1 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2. SIBDL download procedure – step 2 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3. SIBDL download procedure – step 3 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4. SIBDL download procedure – step 4 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5. SIBDL download procedure – step 5 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6. SIBDL download procedure – step 6 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7. SIBDL download procedure – step 7 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 8. Serial Cable Modem configuration – step 1 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 9. Serial Cable Modem configuration – step 2 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 10. Serial Cable Modem configuration – step 3 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 11. Serial Cable Modem configuration – step 4 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 12. Serial Cable Modem configuration – step 5 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
3
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
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 Finterface.
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. SeeChapter 3 on page 11.
1.1.2 Target audience
The SIBDL Manual is intended for all users.
The documents that should be read before starting this document are:
– 1320CT Basic Operator’s Handbook
1.2 Terminology
1.2.1 Acronyms and abbreviations
Refer to the Section Introduction manual.
1.2.2 Glossary of terms
Refer to the Section Introduction manual.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
4
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
5
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
2 DOWNLOAD WITH SIBDL
2.1 Purpose of the procedure
This procedure describes how to download a NE software with the SIBDL (Standard Image BinaryDownLoad) program.
2.1.1 SIBDL download procedure
Download with SIBDL program is performed in the following phases:
• Turn on phase, when activating the NE.
• Maintenance phase, when substituting the EQUICO unit with a spare, and the spare onedoesn’t contain software.
ATTENTION:
Download with SIBDL program put the EQUICO unit out of service regarding to the supervisionand 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 theDownload option of the EML–USM, presented in the previous section.
SIBDL tool permits to download the software towards the NE using the Q interface (Ethernet connection)or the F interface RS232 (serial line) of the NE .
When using the Q interface the time necessary to the operation is reduced to some minute.
WARNING:
in Windows NT environment, it should have configured, before to use SIBDL:
• TCP/IP protocol, Protocol Service, TEL NET Accessory, defined by the NTAdministrator.
• RAS (Remote Access Service) and Serial Cable Modem presented at chapter 3 onpage 11.
in Windows 2000 environment, it should have configured, before to use SIBDL:
• TCP/IP protocol, Protocol Service, TEL NET Accessory, defined by theAdministrator.
• Serial Cable Modem refer to paragraph 3.1.3 on page 12.
N.B. RAS (Remote Access Service) is not necessary in Windows 2000 environment
To download with SIBDL execute the following steps:
1 ) Connect the Craft Terminal with the NE:
• when download by means of Q interface, always connect both the F and Q interface.
• when download by means of F interface, connect only the F interface.
2 ) Start SIBDL, selecting Start > Program>Alcatel>SIBDL”version”>SIBDL
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
6
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
3 ) In the screen which appears (see Figure 1. ) with the command menu, select “automatic mode”command typing 8 and then ENTER.
Figure 1. SIBDL download procedure – step 1
4 ) In the field “source file” at the bottom write the path name of the NE descriptor file (seeFigure 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 Softwarepackage installation procedure” SC.3: NE MANAGEMENT of this Manual.
2) If the software to download manage only the SDH functionality, select the file descriptorin 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 filedescriptor in the directory 1660SME(example: /ALCATEL/Q3CT_Pv1.3.05/FTservices/data/1660SME/2.1b.09/1660.dsc)
C:\ALCATEL\Q3CT_Pv1.3.05/FTservices/data/1660SME/2.1b.09/1660.dsc
Figure 2. SIBDL download procedure – step 2
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
7
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
5 ) Press ENTER
6 ) This step (see Figure 3. ) ask for the “IP Address” insertion.
In the field “NE_IP_address[ PPP TEL NET]” at the bottom:
– with F interface: write PPP and press ENTER
– with Q interface:
• first possibility: write TELNET and press ENTER
In next step which appears write the IP Address of the Craft Terminal
• second possibility: write the IP Address of the NE and press ENTER
ervices/data/1660SME/2.1b.09/1660.dsc
Figure 3. SIBDL download procedure – step 3
7 ) This step ( see Figure 4. ) ask if the flash card must be formatted.
Type “y” to format the flash card; as result of this action the program ask for a confirmation (seeFigure 5. )
ervices/data/1660SME/2.1b.09/1660.dsc
Figure 4. SIBDL download procedure – step 4
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
8
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
ervices/data/1660SME/2.1b.09/1660.dsc
Figure 5. SIBDL download procedure – step 5
8 ) Type “y” . The screen shows the automatic download evolution with a final message indicatingthe completed download (see Figure 6. ).On the contrary repeat the procedure.
Figure 6. SIBDL download procedure – step 6
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
9
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
9 ) Press ENTER.
10 ) In the presented screen type 4 (see Figure 7. ) and ENTER.
Figure 7. SIBDL download procedure – step 7
11 ) Extract and re–insert the EQUICO unit to complete the operation.
12 ) Extract and re–insert again the EQUICO unit to complete the operation.
13 ) Run the 1320CT application, execute Start supervision and NE login
14 ) From Craft Terminal ( EML–USM view) execute the normal download procedure:
N.B. Check that no RUTM alarm is present in the slot reserved to the main MATRIXN.If RUTM alarm is present means that the board type inserted in the subrack (typicallyMATRIXN in this release) and the board type software configurated (typicallyMATRIX) is not the same; under this condition the user must change the board typewith the Equipment–>Set menu.
– Select Init download from Download menu– Select the SW package to Download and click on OK button
In this condition the download is executed immediately.– Select Unit info from Download menu– Select the Software Package loaded as explained above and activate it– Press OK to complete the operation
In this condition the download is executed immediately.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
10
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
11
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
3 CONFIGURATION FOR SIBDL
3.1 Purpose of the procedure
This chapter describes the configurations to be performed for SIBDL operation.
3.1.1 Remote Access Service configuration (only needed for Windows NT environment)
To install a new modem, the user should have administrator privileges and need the installation CD–ROMof Windows NT, then execute:
– Double click on ”My computer” icon on the PC desktop and double click on ”Control panel” icon;– double click on ”Network” icon;– select the folder ”Services” in the ”Network” window and push the button ”Add”: start the ”Select
Network Service” window;– select Remote Access Service (RAS) in the dialog box;– follow the instructions.
3.1.2 Serial Cable Modem configuration for Windows NT environment
To install a new modem, the user should have administrator privileges, then execute:
– Double click on ”My computer” icon on the PC desktop and double click on ”Control panel” icon;
– double click on ”Network” icon;select the folder ”Services” in the ”Network” window;
– select ”Remote Access Service” and push button ”Properties...”;
– push the button ”add” in ”Remote Access Setup” window;
– push the button ”Install Modem” in ”Add RAS Device” window: start the ”Install New Modem” window;
– put a tick against ”Don’t detect my modem; I will select him from a list” and push the ”Next > ” button;
– push the button ”Have disk...”: start the window Install from disk;
– push the button ”Browse...;search the folder where SIBDL is installed (Alcatel / SIBDL “version” / SIBDL /)and select the file”mdmalca.inf”, after push the button ”Open”;
– push the button ”OK” in window ”Install from disk”;select the modem named ”Serial cable” in the dialog box of window ”Install New Modem” and pushthe button ”Next >”;put a tick against ”Selected ports” and select only one port (the port must be available, i.e. not usedby another RAS modem) and push the button ”Next >”;
– follow the instructions;
– push the button ”OK” in ”Add RAS Device” window;
– push the button ”Continue” in ”Remote Access Setup” window;
– push the button ”OK” in ”Network” window;
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
12
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
3.1.3 Serial Cable Modem configuration for Windows 2000 environment
To install a new modem, you should have administrator privileges;
– Double click on ”My computer” icon on your PC desktop and double click on ”Control panel” icon;
– Double click on ”Phone and Modem Options” icon and select the ”Modems” folder;
– Push the button ”Add”: ”Add/Remove Hardware Wizard: Install New Modem” window will appear;
– Put a tick against ”Don’t detect my modem; I will select it from a list” and push the button ”Next > ”;
Figure 8. Serial Cable Modem configuration – step 1
– Push the button ”Have disk...”: the window ”Install from disk” will appear;
– Push the button ”Browse...;
– Search the folder where SIBDL is installed and select the file ”mdmalca.inf”, after push the button”Open”;
– Push the button ”OK” on the ”Install from disk” window;
– Select the modem named ”Serial cable” into dialog box from ”Install New Modem” window and pushthe button ”Next >”;
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
13
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
Figure 9. Serial Cable Modem configuration – step 2
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
14
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
– Put a tick against ”Selected ports” and select only one port (the serial port must be available, i.e. notused by another RAS modem) and push the button ”Next >”;
Figure 10. Serial Cable Modem configuration – step 3
– The window ”Digital Signature Not found” will appear: push the button ”Yes”, and after the button”Finish” to end modem installation;
Figure 11. Serial Cable Modem configuration – step 4
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
15
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
– At the end, the ”Phone and Modem Options” window will display the installed modem
Figure 12. Serial Cable Modem configuration – step 5
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
16
01
957.140.602 V
SC.5: SIBDL
/3AL 80755 BA AA
16
16
END OF DOCUMENT