Beruflich Dokumente
Kultur Dokumente
Alcatel 1300NM
Network Management
1354RM Rel.7.2
Regional Network Manager for SDH and Optical Networks
Volume 1/1
TABLE OF CONTENTS
1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Handbook applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
3
3
2 PRODUCT-RELEASE HANDBOOKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Handbooks related to the products software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Handbooks related to the products hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Handbook configuration check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Handbooks related to the products hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5
7
8
9
9
4 LIST OF ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
15
15
15
15
16
16
16
17
17
18
18
18
01
050207
ED
DATE
CHANGE NOTE
M.RAGNI ITAVE
V.PORRO ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
1354RM REL.7.2
OPERATORS HANDBOOK
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
1 / 18
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
2 / 18
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ANV P/N
1354RM
PRODUCT
RELEASE
VERSION (N.B.)
ANV P/N
1354RM
7.2
KERNEL
For NR7
N.B.
ED
PRODUCT
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
3 / 18
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
4 / 18
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2 PRODUCT-RELEASE HANDBOOKS
The list of handbooks given here below is valid on the issue date of this Handbook and
can be changed without any obligation for ALCATEL to update it in this Handbook.
Some of the handbooks listed here below may not be available on the issue date of this
Handbook.
The standard Customer Documentation in the English language for the equipment whose product-release-version is stated in para.1.2 on page 3 consists of the following handbooks:
REF
HANDBOOK
[1]
[2]
THIS
HANDBOOK
SAFETY RULES
General rules
Harmful optical signals
Risk of explosion
Moving mechanical parts
Heatradiating Mechanical Parts
ELECTROMAGNETIC COMPATIBILITY
ELECTROSTATIC DISCHARGERS (ESD)
EQUIPMENT LABELS
2.3 History
Ed.01
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
5 / 18
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
6 / 18
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
This handbook is a collection of documents (each contained in a specific section) that can have
editions different from one another.
The Edition of the whole handbook is that of section 1 (HANDBOOK GUIDE).
The edition of the enclosed documents indicated in the following table is that of the corresponding original internal document.
HANDBOOK EDITION
01
ED
03
04
05
SECTION EDITION
HANDBOOK GUIDE
01
GETTING STARTED
01
OPERATION
01
MAINTENANCE
01
TECHNICAL ANNEXES
01
01
RMNP INTERWORKING
01
RMGMRE INTERWORKING
01
01
02
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
7 / 18
In particular refer to such handbooks to obtain the following information (where applicable):
SAFETY RULES
General rules
Risk of explosion
ELECTROMAGNETIC COMPATIBILITY
EQUIPMENT LABELS
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
8 / 18
The aim of this document is to describe the operations related to the RMGMRE INTERWORKING
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
9 / 18
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
10 / 18
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
4 LIST OF ABBREVIATIONS
ADM
AIS
ALMIM
ALMAP
AP
Access Point
APS
AS
Alarm Surveillance
AU
Administrative Unit
BN
Backbone Network
BR & SW
Browser
CAP
Client Access Point. It represents a point where a client layer can access a server layer
( i.e. a VC4 that is configured to carry lower order signals is a HOCAP)
CI
Communication Infrastructure
CMISE
CMOT
CTP
DB
Data Base
DBMS
DCI
DCN
D&C
DWDM
ECC
EM
Element Manager
EML
EML domain
EMOS
EMS
EPS
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
11 / 18
Elementary Subnetwork
ET
FAD
FM
Fault Management
FOX
HOAP
HOPLN
HOPL
HP
HPOV
HP-OVw
IAP
Inventory Application
ISA
Isn
Link
Connection
(lc )
LOAP
LOF
LOP
Loss of Pointer
LP
LSP
Link single fault protection index (LSP). The LSP index is determined (in a way similar
to NSP for nodes) taking into account of both the number (C) of archs belonging to the
main route and the number (D) of archs belonging to the main and spare routes.
Map
MIB
MSAP
MSRDI
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
12 / 18
ESN
MSL
MS Spring
MS SIGDEG
MSLN
NAP
NE
NetView
Application based on OVW, used to display, create, keep updated view of the SDH
Network Through maps.
NM
Network Manager
NML
Node
NSP
Node single fault protection index (NSP). The NSP index is determined taking into
account of both the number (A) of Nodes belonging to the main route and the number
(B) of Nodes belonging to the main and spare routes, except the end nodes.
OS
Operations System
PCMAP
PDH
Physical
Connection
A Physical Connection connects two SDH ports in the network. These two ports belong
to different NEs and must have the same transmission rate.
PM
Performance Monitoring
POH
Path Overhead
Port
PRC
Q3
Qnn
sbn
SDH
SENIM
SD
Signal Degrade
SF
Signal Failure
SMF
SNML
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
13 / 18
SONET
STM
TCA
TM
Terminal Mode
TN
Transport Network
TP
Termination Point
Trail
Trail
termination
TSDIM
Same as QB3 protocol. Information Model for interworking between Network Managers
and Network Elements.
TTP
TU
Transport Unit
UPA
URU
VC
Virtual Container
WTR
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
14 / 18
SNCP
Consequently, no supply to the Customers of design documentation (like software source programs, programming tools, etc.) is envisaged.
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
15 / 18
the name of the product-release (and version when the handbook is applicable to the versions
starting from it, but not to the previous ones),
the handbook issue date. The date on the handbook does not refer to the date of print but to the date
on which the handbook source file has been completed and released for the production.
5.4.1 Changes introduced in the same product-release (same handbook P/N)
The edition and date of issue might change on future handbook versions for the following reasons:
only the date changes (pointed out in the Table of Contents) when modifications are made to the editorial system not changing the technical contents of the handbook.
the edition, hence the date, is changed because modifications made concern technical contents. In
this case:
the table in para. 1.2 on page 3 indicates the section(s) edition change;
in each section, the main changes with respect to the previous edition are listed;
in affected chapters of each section, revision bars on the left of the page indicate modifications
in text and drawings (this is done after the first officially released and validated version).
Changes concerning the technical contents of the handbook cause the edition number increase (e.g. from
Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition of
a version character (e.g. from Ed.02 to Ed.02A).
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operators Handbooks) are not modified unless the new software version distributed to Customers implies manmachine interface
changes or in case of slight modifications not affecting the understanding of the explained procedures.
Moreover, should the screen prints included in the handbook contain the product-releases version marking, they are not replaced in the handbooks related to a subsequent version, if the
screen contents are unchanged.
5.4.1.1 Supplying updated handbooks to Customers
Supplying updated handbooks to Customers who have already received previous issues is submitted to
commercial criteria.
By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue
(supplying erratacorrige sheets is not envisaged).
5.4.2 Changes due to a new product-release
A new product-release changes the handbook P/N and the edition starts from 01.
In this case the modified parts of the handbook are not listed.
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
16 / 18
the documentation of system optional features that Customers could not buy from Alcatel together with the main applicative SW.
the documentation of system optional features (e.g. System Installation Handbooks related to
racks that Customers could not buy from Alcatel together with the main equipment).
After a complete functional check, the CDROM image is electronically transferred to the archive of the
Production Department, so that the CDROM can be produced and delivered to Customers.
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
17 / 18
The minimum configuration and the setup procedure are present in the README.TXT file included in
the CDROM.
After the setup procedure, which installs the viewer in the PC or Unix WS environment, the Customer
is allowed to read the handbooks on the PC/WS screen, using the navigation and zooming tools included
in the viewer, and to print selected parts of the documentation through a local printer.
N.B.
Copyright notification
WorldView:
Copyright 19811996
INTERLEAF Inc.
All rights reserved.
The use of WorldView is permitted only in association with the files contained
in the CDROMs officially supplied by Alcatel.
Alcatel documents:
by the following external identifiers, that are printed both on the booklet and the CDROM upper
surface:
the name of the productrelease(s) (and version when the CDROM is applicable to
the versions starting from it, but not to the previous ones),
2)
and, internally, by the list of the source handbooks and documents (P/Ns and editions) by whose
collection and processing the CDROM itself has been created.
Updating of CDROMs always follows, with a certain delay, the updating of the single handbooks
composing the collection.
END OF DOCUMENT
ED
01
SC.1:HANDBOOK GUIDE
3AL 61348 AA AA
18
18 / 18
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
7
7
2 1354RM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 The Regional Manager in the controlled network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Topological Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Transport Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 1330AS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4 System Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.6 Performance Monitoring Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
10
12
12
12
15
17
17
17
17
18
20
20
20
21
21
22
25
29
32
4 GLOSSARY OF TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
5 PRELIMINARY OPERATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Logging in to the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Workspace description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
45
46
01
050207
ED
DATE
CHANGE NOTE
M.RAGNI ITAVE
V.PORRO ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
1354RM REL.7.2
OPERATORS HANDBOOK
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
1 / 142
47
48
49
49
50
52
54
55
56
56
60
61
62
63
66
67
69
7 VIEWS DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Management Tools windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.1 Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
71
72
72
73
73
74
76
9 BROWSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 Browser main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 Icon bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 Counters area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.4 Work area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.5 Object filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.6 DEFINE QUERY FOR (the selection/filter window) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.7 Show/Set Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.8 Items selection in the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.9 Generic Browser pulldown menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.10 Actions: Search: Main Related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.11 Actions: Search: All Related items... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.12 Actions: Search: Parent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.13 Actions: Select: Related Items.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.14 Actions: Select: All related Items.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.15 Actions: Select: Unselect All.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.16 Actions: Close: Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.17 Actions: Close: Item by Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.18 Actions: Close: All related items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.19 Actions: Align item(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.20 Actions: Details: Show/set attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.21 Actions: Details: Displayed info... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.22 View:Displayed info.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.23 View:Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.24 Options: Filtered presentation / Not filtered presentation . . . . . . . . . . . . . . . . . . . . . . . . .
85
85
87
88
89
90
90
92
93
94
95
95
96
96
96
96
97
97
97
97
97
98
98
99
99
101
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
2 / 142
102
102
102
102
102
103
103
104
104
105
106
106
107
108
109
113
119
120
121
123
123
124
124
125
125
126
127
128
128
128
129
129
131
135
135
137
137
140
140
140
14 ONLINE DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
141
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
3 / 142
FIGURES
Figure 1. Path configuration status states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Alarm navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Mouse pointer representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Example of a window layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Window menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. Scroll bar components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. Examples of push buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Examples of radio buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Window view showing the menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Window view with Pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Window view with Cascading menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Unselectable menu items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Highlighted menu item indicating selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Example of a dialogue box having Entry Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Multiple List box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Error dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Question dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Information dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Confirmation Dialogue Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Login panel view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. The SDH Manager workspace Front Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Locking the screen using a manual lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. Screen lock Password: entry box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Logging out using the front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. HPCDE Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. TMNOS manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. Selfhiding vertical palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Active task subpanel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. System Menus started from the logo icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Panel Close confirmation window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. System menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. System Menus: Path Provisioning menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. System Menus: Network Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. System Menus: Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. System Menus: OS Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. Create New Panel submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Create: New Corner Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Create: New Edge Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. Task bar popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Panel Properties: Edge Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Panel Properties: Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. Global Panel Configuration: Animation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. Global Panel Configuration: Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. Utility popup menu on each system menu item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Utility buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Utility button: Add this as menu to panel for a group of commands . . . . . . . . . . . . . . . . .
Figure 48. Customized user menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. System menus: Path Provisioning: Path Creation Wizard: Add this to launcher panel .
Figure 50. Window icon popup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
01
11
14
19
20
21
22
23
24
25
26
27
28
29
30
33
34
34
35
35
45
46
47
47
48
49
50
54
55
56
57
57
58
58
59
59
60
60
61
61
61
62
63
64
65
67
68
68
69
70
70
SC.2:GETTING STARTED
3AL 61348 AA AA
142
4 / 142
73
74
75
76
77
78
79
80
81
81
82
83
87
90
91
92
94
99
100
101
102
103
109
110
111
113
114
115
116
116
117
117
118
119
120
121
128
129
130
135
136
138
139
TABLES
Table 1. Items selection in the Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
95
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
5 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
6 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
1 INTRODUCTION
1.1 Introduction
This document aims at introducing the 1354RM working environment, to the users of the system, in terms
of getting access to the system, the environment utilities, the existing 1354RM functionalities and
navigation through the system.
ED
1354RM Overview
Windows
Glossary
Logging Operation
Workspace description
Logout
View Description/Wizards
Map Navigation
Drawing Introduction
Browser List
Locate
Help System
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
7 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
8 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2 1354RM OVERVIEW
2.1 The Regional Manager in the controlled network
Main Product are: (please refer to the relevant documentation for further info).
1353NM is the Common Element Management Layer OS which can manage more than 100 NE versions
and types.
1354BM is the NML application for managing ATM services available in OMSNs.
1354SN is the NML application for managing Submarine Line Systems.
1354NP is the Fast Restoration NML application for controlling DXC meshed backbone networks.
1355VPN permits to manage Optical Virtual Private Networks at the end Customer premises.
1355ONE (Optical Network Engineering) is a network analyser.
1354RM provides the management of SDH/SONET and DWDM subnetworks. Via the 1353NM 1354RM
controls the Network Elements.
Network:
A path that crosses two Networks cannot be managed by 1354RM as a single transport entity (i.e.
it will be represented with two paths)
Subnetwork:
A Network can be composed by more than one subnetworks)
Node:
It represents the image of a Network Element.
Physical Connection:
It is the logical representation of fibers and coaxial cables, between network ports
EML Domain:
It represents one EMLIM component of 1353NM.
NE:
It represents a physical NE.
Network port:
It represents the physical port where e.g. the fiber is connected.
Example:
A STM16 port of a SDH NE.
An OTS port of a DWDM NE.
Access port:
It represents the physical port where the client signal is added/dropped.
Example:
a PDH port of a SDH NE.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
9 / 142
Section:
It is a trail at Multiplex Section Layer.
Example:
MSTrail between two STMn ports of two adjacent SDH NEs.
OMSTrail between two OTS ports of two adjacent DWDM NEs.
Path:
A path (can be at either HO or LO path layer) is a route established in the SDH/SONET network. It
is delimited by NAPs (Network Access Points).
Example:
A VC12 path delimited by two VC12 NAPs
Link Connection:
It is an arc delimited by the two CTPs with the same timeslot and it is supported by the same server
Trail
Example:
An Au4 Link Connection is delimited by two corresponding AU4 CTPs and it supported by a MS
Trail.
Define the Network Protection Architectures one per each 2nd level subnetwork
To each access port the related Network Access Point is available.
Moreover the following feature is available:
The map provides a network view partitioned in subnetworks, which can be partitioned in 2nd
level subnetworks, and nodes (submaps may have a geographical background). This map
representation is created during the network construction process.
The different views are organized in hierarchical trees. Zooming operations allow the user to navigate
through a tree of hierarchical views.
2.1.2.2 Path Management
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
10 / 142
A path can be in the defined, allocated, implemented, and commissioned state. The picture describes the
admitted state transitions.
Create
Allocate
Defined
Delete
Implement
Allocated
DeAllocate
Commission
Implemented
DeImplement
Commissioned
DeCommission
Path name
Path type (i.e. unidirectional, bidirectional or point to multipoint)
Protection type
Rate
AEnd and ZEnd points
Allocation/implementation rules
Alarm enable/disable for the involved path up to the commissioning state.
When this activity is successfully terminated, the selected resources are locked; please notice that at the
end of this phase the path does not yet exist in the network.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
11 / 142
Operator Administration functions: Add Operator, Remove Operator, List Operators, Change
Password, List Current Login, List Successful Login and List Unsuccessful Login.
Console Administration functions: Add Operator Console, Remove Operator Console, List Operator Consoles, Lock Operator Console and Unlock Operator Console.
System Log functions: List System Messages, List Archived Messages and List restored Messages.
Periodic Actions functions: Show Scheduling Time, Set Scheduling Time and Cancel Scheduling
Time, bearing in mind that the term periodic actions here refers to System Management Functions.
Also, the communication between the 1354RM and the registered Element Managers is tested periodically, being an alarm generated when a communication test fails.
Backup & Restore functions: It is possible to automatically backup data periodically, since online
full backup is supported. It is possible to do a complete full backup on Operator request and to get
information on planned actions. It is possible to disable automatic operation and restore a full or an
incremental backup. Restore is offline and 1354RM shall be previously shutdown.
System Start/Stop functions: Start System, Stop System, Show System State, Autostart Enable/
Disable and Show Autostart State.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
12 / 142
Only if this scenario is successfully completed, the path becomes implemented, i.e. a real connection between the selected endpoints exists in the network.
In this state it is possible to activate loopbacks on ports, in order to validate the path itself.
Each network alarm (X.733 compliant) provides information about the affected resource, alarm type, probable cause, severity, timestamp and so on.
All the current network alarm information is shown to the operator in the current alarms list. The alarm fields
are customizable by the user. After the operator acknowledgement and alarm clearing the network alarm
is moved into the historical alarm log. As default, the system provides alarms counters related the total
alarms in the domain and to each managed alarm severity (critical, major, minor, warning, indeterminate),
and cleared alarms. The user can define other type counters according his needs.
Starting from the alarm list it is possible for a specific network alarm to retrieve information about the elementary alarms correlated to it.
Network management topological objects (NE, ring, subnetwork,...) containing the alarmed object (TP,
port, ...) are graphically displayed according the color of the highest alarm severity.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
13 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
14 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
15 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
16 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Keyboards: the different keys and the actions they induce will be defined.
Mouse: the operation of the different buttons will be explained.
Workspace: A workspace is the screen area where you bring the applications needed for your work,
arrange them to suit your preferences, and put them away after finishing your job. Each workspace
occupies the entire display, and you switch from one workspace to another using a control.
Icon: A small, graphic representation of an object on the workspace. Objects can be iconified
(turned into icons) to clear a cluttered workspace and normalized (returned to their original
appearance) as needed. Processes executing in an object continue to execute when the object is
iconified.
Windows: the windows general layout, menu and configuration (size) will be described.
Dialogue Boxes: the different types of boxes and their aspect is defined so that the user will be
familiar with them.
Alphabetic Keys:
They represent the letters of the alphabet, the punctuation marks and textformatting functions such
as Tab, Return and the Space bar.
Numeric Keys:
They represent the numbers from 0 to 9. They are located near the top of the keyboard and in a
numeric keypad on the right side of the keyboard.
Modifier Keys:
Used in conjunction with other keys to modify the meaning of these keys. They are Ctrl, Shift or Alt keys.
In particular the Control button, used in conjunction with the Selection button ( left mouse button )
is used to extend the object selection.
Function Keys:
They provide extra or general functions. They are labelled F1, F2, F3..etc... and are located across
the top of the keyboard. They can be used as accelerator keys, giving the possibility to select menu
options rapidly using the keyboard. For example, under certain conditions, the F1 key generates a
HELP dialogue box.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
17 / 142
The mouse is associated with a mouse pointer. This pointer represents the current position of the mouse
on the screen. Any movement of the mouse, on the mouse pad, moves the pointer on the screen in an
identical way. The mouse can be moved anywhere on the workspace.
3.1.3.1 Mouse buttons
There are 3 Mouse buttons. The actions that are undertaken using the different mouse buttons depends
on their configuration.
With a left handed mouse configuration, button 3 becomes the select button.
3.1.3.2 Select/Deselect/DragandDrop functionalities
Selecting an object: first move the mouse pointer to the object. Then select the object by clicking
on it with the Select mouse button. The object appearance changes indicating that it has been
selected.
Draganddrop mouse functionality: used for displacing objects or icons on the workspace. To
use it, first move the mouse pointer to the object you wish to move. Then press, and hold down, the
Drag mouse button and drag the object to the chosen area using the mouse. When the object has
reached the chosen area, release the mouse button.
The shape of the mouse pointer gives an indication of what actions can be undertaken in that particular
mouse position. The user will soon understand the different functionalities related to the mouse pointer
form. To help him, a list of the mouse pointer forms is given in the figure below.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
18 / 142
3.1.3 Mouse
This arrow pointer indicates that in the actual mouse position an action can
be undertaken. For example, open a menu, resize or move a window...
This arrow pointer is usually associated with menus. It indicates that a menu
is open and that a menu item can now be selected by clicking.
This Ibeam pointer is usually associated with windows and entry boxes.
They indicate that a written entry can be performed here.
The X pointer shape indicates that the mouse is outside an application area
(for example a window).
The work in progress pointer symbol indicates that some action is in progress.
The cross pointer is used to select a window to be printed as part of a screen
hardcopy process.
The 4directional arrow pointer indicates a move operation or a resizing operation can be undertaken on a window.
The hand sign means that the pointer is over the object ( browser context)
The Caution sign indicates that the graphical object under the mouse is not
selectable. For example, during a logout process, this pointer appears when
the mouse pointer is outside the confirmation dialogue box.
Numerous actions can be undertaken by double clicking using the mouse. For example, opening windows
related to objects (this is of importance during the construction of the Network Topology as shall be seen
in the Operation Manual) and opening iconified windows.
a)
Place the mouse pointer over the object you wish to open.
Click twice, rapidly, using the Select mouse button on the object.
The mouse pointer will take the work in progress representation until the object should open.
b)
To open a symbol submap or the object view (this refers to the Operation Construction manual).
Place the mouse pointer over the symbol whose submap you wish to open.
Click twice, rapidly, using the Select mouse button on the object.
The mouse pointer will take the work in progress representation until the symbols submap should open.
c)
To select from a list of selectable feature or function and confirm by pressing OK ( SMF context )
d)
To get the selectable list of the object related items (browser context)
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
19 / 142
3.2 Windows
This section defines the attributes of windows and describes their general aspects.
3.2.1 Dimensions and layout
The figure below indicates the standard window layout.
Window menu button
Window title
Maximize
button
Menu Bar
Client area
Resize borders
The Client area is the area in which you work. You can write text, insert or construct images or display
Network views. The window title gives the name of the window.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
20 / 142
Restore: restores the window from the iconified state to its normal size (in this case the window is
already opened so this menu option is greyed. Greyed menu options are explained in chapter
3.2.6.5).
Move: displaces the window around the workspace,
Size: changes the size of the window,
Minimize: iconifies the window,
Maximize: gives the window the full screen size,
Lower: places the window at the back of the workspace (this is helpful if many windows are opened
and overlap on the workspace),
Occupy Workspace...: gives you the possibility of selecting the workspace on which the window is
shown,
Occupy All Workspaces: places the window on all the workspaces,
Unoccupy Workspace: removes the window from the workspace from which this option is selected,
There are vertical and horizontal scroll bars as shown in the figure below.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
21 / 142
Slider
Stepper
arrows
Scroll Region
Figure 6. Scroll bar components
There are three ways to use scroll bars:
3.2.5 Buttons
In any working application related to the SDH Manager, the operator will have to confirm, cancel, select
options or ask for help using buttons. Different types of buttons exist and are described in this section.
3.2.5.1 Push buttons
Push buttons are identified by two characteristics:
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
22 / 142
The graphical image representing the button. The buttons are generally of rectangular or square shape.
The label identifying the action associated with the button. The label is placed on the button.
Examples of the different types of push buttons are described in the figure below.
To apply the action related to a push button, position the mouse pointer over the button you wish to select
and click using the Select mouse button.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
23 / 142
Each radio button represents a single choice selection. Selecting one radio button automatically deselects
the others in the set.
To select a radio button, place the mouse pointer over the button needed and click on it using the Select
mouse button.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
24 / 142
3.2.6 Menus
In this section we describe an important aspect of the user interface. The user constantly has to open windows, select icons and navigate through the different functionalities of the SDH Manager. To do this he
will use menus.
A menu consists of a title, that usually identifies the nature of the actions that can be undertaken, and a
list of options associated with actions.
There are different menu types that can be classed as follows:
menu bars,
pull down menus,
cascading menus,
tear_off menus,
popup menus.
These types of menus are described in detail below. The details concern a view of the menu types on real
windows.
3.2.6.1 Menu bars
They are present at the top of a window, under the title of the window. They appear automatically along
with the window. An example is given in the figure below. They contain the titles from which pull down menus and cascading menus are opened.
Window title
Menu Bar
Tool bar
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
25 / 142
A pull down menu is pulled down from a menu item present in a menu bar. To open a pull down menu, click
on the title of the menu you need to open with the Select mouse button.
Pulldown menu
A menu option followed by ... means that selecting this option opens another view.
N.B.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
26 / 142
Cascading menu
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
27 / 142
In an opened menu (pull down or cascading), any item that is greyed indicates that you do not have access
to the menu item. Clicking on it will not activate it. You have access to all the items that are not greyed.
An example of an inaccessible or greyed menu item is shown below.
Greyed menu
option showing
non selectability
To select an item from a menu (any type of menu) place the mouse pointer over the item and click using
the Select mouse button. The item will appear highlighted.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
28 / 142
Selected menu
item highlighted
Entry boxes are windows in which you can consult, add or modify information or data. Figure 14. gives
you examples of the general representation of an Entry Box.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
29 / 142
Entry box
(text entry
area)
Entry Box Label: Indicates what is entered or what is to be entered in the entry area concerned.
Entry Box: When selected, enables you to enter a text.
N.B.
ED
The text entry areas may not be accessible for entering text. In this case they have a different
colour than other entry areas in which text can be entered. In the example above, the Name of
Open Map entry box may not be used for text entry. Its colour is lighter than the other entry areas.
Furthermore the text cursor is dotted, indicating that text cannot be entered.
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
30 / 142
To access an entry box and enter text, click on the text entry area. The text cursor begins to blink. The text
cursor has an Ibeam shape. The following keys are useful when entering text.
Key
Function
Back Space
Del
, , ,
To access another entry box, you can either click in the entry box using the Select mouse button or use
the Tab key on the keyboard.
Selecting the Tab key, on the keyboard, enables you to pass to an entry box situated beneath the one from
which the Tab key is pressed. Selecting the Shift+Tab keys gives you access to an entry box situated
above the one from which the action is launched.
N.B.
The Tab key does not give you access to those entry boxes that are read only and in which you
cannot write. Therefore, when a dialogue box containing entry boxes opens, the Tab key takes
you directly to the first entry box in which you can write.
This concerns the use of upper case and lower case characters when entering text.
The text entered is redisplayed in its original form.
This means that if upper case characters are given to a Log file name, the name will appear in upper case
characters in the save directory.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
31 / 142
Dialogue boxes provide an interface between the SDH Manager and the user. They enable to confirm operations or consult information, displayed by the system, following an action of the user.
There are many types of dialogue boxes. They generally combine several of the graphical controls described previously (scroll bars, push buttons...). The principal dialogue boxes are described below.
3.2.8.2 List dialogue boxes
A list dialogue box is generally a window that enables you to consult and select items from an existing list.
They have a Title heading indicating the purpose or contents of the List box. Depending on the size of the
List box, scroll bars are present or not.
Different types of List boxes can be distinguished.
a)
b)
They display the data in the form of multiple columns. An example is given below.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
32 / 142
3.2.8.1 Generalities
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
33 / 142
A question dialogue box requests additional confirmation following a command previously launched. The
Cancel push button cancels the operation.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
34 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
35 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
36 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
4 GLOSSARY OF TERMS
Add and Drop Multiplexer:
Equipment used to combine several signals to produce one signal at a higher rate and to decompose it
back to the original lower rate signals.
Administrator:
A user who has access rights to all the Management Domains of the SDH Manager product. He has access
to the whole network and to all the management functionalities.
Alarm:
An alerting indication to a condition that may have an immediate or potentially negative impact on the state
of an equipment or the OS. An alarm is characterized by an alarm begin and an alarm end.
Alarm Indication Signal:
Alarm linked to the physical interface, associated with a probable alarm occurrence in the normal
transmission of the signal.
Automatic laser Shutdown:
Functionality provided by the SDH Manager to cut the laser source automatically in case of system failure.
Automatic Protection Switching:
Functionality related to Network Elements that automatically switches from the degraded resources to the
redundant or spare resources. This assures the best quality of transmission service.
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.
Administrative Unit:
Entity composed of a high order virtual container (VC4) to which is added a pointer indicating the position
of the virtual container in the STMN frame.
Administrative Unit pointer Justification Counter:
Counter indicating whether positive, negative or null justification is undertaken in the administrative unit.
This counter enables the management of the synchronization and the coherence of the transmitted signal.
Bit Error Rate:
This determines the number of errored bits in a signal frame. If the value exceeds a certain threshold then
an alarm is generated.
Board:
A board is part of an NE. They are electronic cards that fit into slots in the NE.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
37 / 142
Crossconnect (XC)
CrossConnects provide the network with the Routing Capabilities, this is the possibility of routing one
signal to a particular destination.
Digital Communication network:
Communication Network in which the transmission of data is done in a digitized format.
Degraded Signal:
Alarm sent when the number of errors detected in a received signal frame exceeds a certain threshold.
Embedded Communication Channel:
Communication channel used in conjunction with packet commuting networks (X25) to manage distant
SDH networks. These communication channels are related to the QECC* protocols.
Element Management Layer:
This apllication is responsible for the configuration and management of Network Elements.
Equipment Protection Switching:
Used to provide protection for cards within the ADM to protect traffic in the event of card failure.
Filter:
They are related to the alarms or events generated on an NE or internally within the OS itself. They can
be configured by an operator to reject specified types of notifications and limit the processing that is applied
to them.
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.
Far End Receive Failure:
Alarm linked to the multiplex section termination functional block, indicating that a receiving problem is
occurring at the far end of a communication link.
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.
High Order Assembler:
Function of the SDH Manager that is composed of the Higher Order Path Adaptation and the Higher Order
Path termination functions.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
38 / 142
Craft Terminal:
Workstation or Personal computer (PC) from which local address to an NE is possible. It can be used to
configure or perform monitoring tasks on the NE.
Loss Of Signal:
Alarm linked to the physical interfaces, associated with the absence of a received signal.
Loss Of Tributary Signal:
Alarm linked to the PDH physical interface, indicating the loss of a tributary signal.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
39 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
40 / 142
Severity:
Linked to alarms, severities indicate the magnitude related to the failure.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
41 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
42 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
43 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
44 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
5 PRELIMINARY OPERATIONS
5.1 Logging in to the System
This is the first operation you will have to undertake to access the Regional Manager system. The view
that will greet you, called the Login panel is presented below.
N.B.
You are assigned the login name by the Regional Manager administrator.
Enter your password.
After a correct login, the login view is replaced by a transition view giving certain software copyright
indications. This view is automatically replaced by the normal workspace view containing the Front Panel
from which you will be able to access the SDH Manager functionalities.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
45 / 142
Your workspace is described as the functionalities that appear on your workstation screen after login.
The workspace Front Panel is described below.
WS
activity
Clock
Date
Padlock
Text
Editor
Workspaces
Exit
Printer
Letter
Terminal
File
Manager
TMNOS
Manager
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
46 / 142
This utility enables you to lock the screen to prevent other users from using your working environment.
Padlock
icon
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
47 / 142
Logging out from the workstation will automatically quit all the Regional Manager graphical applications
that you opened and give place to the Login panel. Notice the the Regional Manager processes are still
running.
Using the Front Panel.
Click on the EXIT icon on the front panel, using the Select mouse button, as shown in the figure
below.
EXIT icon
A dialogue box opens from which you can confirm or cancel the Logout operation.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
48 / 142
6.1 Introduction
The 1354RM graphical interface is based on:
Task subpanel.
The HP_CDE Tool panel ( See Figure 25. ) has been customized to contain the TMNOS Manager
(righthand side).
WS
activity
Clock
Date
Padlock
Text
Editor
Workspaces
Exit
Printer
Letter
Terminal
File
Manager
TMNOS
Manager
Clicking on the Manager icon you can open the TMNOS Management. ( See Figure 26. )
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
49 / 142
green
red
blue
yellow
The window contains a pulldown menu bar comprising the following menus:
File
Edit
View
OS
Start System. This submenu is present both for RM and SH. The Start option is available
if the selected OS is in the Stop state.
Stop System. This submenu is present both for RM and SH. The Stop option is available
if the selected OS is in the running state.
Both options are provided if the selected OS is in the Wrong state (partially stopped).
System Config. This submenu is available both for RM and SH. It allows to configure the
system in terms of processes
Process Monitoring. This submenu is available both for RM and SH. It opens the Process
Monitor window.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
50 / 142
Actions
(active only for resident Manager) containing a list of menus that vary
depending on the OS type (RM or SH) and on its actual status. The relevant OS icon must be
selected. The available submenus are:
User Interface. This submenu is present both for RM and SH. It permits to launch the user
interface
Performance Monitoring. This submenu is present both for RM and SH. It permits to
launch the Performance Monitoring display window.
Alarms. This submenu is only available for SH. It permits to launch the AS application.
SMF. This submenu is present both for RM and SH. It contains the following options:
Operator
Log
Trace
Failure
Scheduler
Backup
Restore
Cleanup
Initiator
Global Actions
(active only for resident Manager) It permits to launch the entire
system actions. It contains the following submenus:
Operator. It contains the following options:
Global Operator Actions
Change Password
Session management
Max Operator Logged Administration
Set Personal Printer
Synchronize Systems
Alarm Federations
The window contains a tool bar (active only for resident Manager) which allows to launch the most
frequently used applications. They are:
ALARM
SURVEILLANCE
1AA 00014 0004 (9007) A4 ALICE 04.10
SYSTEM
EXIT
CONFIG
PROCESS
MONITORING
ED
01
PERFORMANCE
HELP
MONITORING
BROWSER
SC.2:GETTING STARTED
3AL 61348 AA AA
142
51 / 142
Exit
System Config
Process Monitoring
Help
1354RM Browser
Performance Monitoring
Alarm Surveillance
ED
1)
2)
3)
4)
MS TRAIL IN SERVICE
CONNECTION )
5)
6)
PATH IN SERVICE
COMMISSIONED)
7)
8)
EML
9)
NE
1)
2)
3)
ALL HO TRAILs
4)
ALL MS TRAILs
5)
6)
ALL PATHs
7)
01
( IMPLEMENTED OR PARTIALLY
( IMPLEMENTED OR PARTIALLY
IMPLEMENTED OR
IMPLEMENTED OR
SC.2:GETTING STARTED
3AL 61348 AA AA
142
52 / 142
8)
PRC
9)
BACKBONE NETWORK
From the Counter summary window open the Alarm sublist clicking twice on the relevant row of the
Counter summary window. As an alternative select the row and issue the Sublist: Open pulldown
menu item.
The Alarm sublist is presented.
b)
Select the alarm from the sublist and navigate it by selecting the Navigation: 1354RM pulldown
menu item. A confirmation dialog box appears. Click on OK to confirm.
The following cases are possible:
for O/MS TRAIL object the physical connection structure window is presented
Notice that in each view the alarmed object is marked by an alarm icon. By clicking on this icon a window
is presented, which gives details on the selected alarm.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
53 / 142
Alcatel logo
The task subpanel (see Figure 28. ).starts automatically at browser startup.
upper arrow
Create connection
Create Path
task buttons
Active counters
Netview
Browser
lower arrow
upper arrow. If you click with the left mouse button on it, the icons contained in the layered icon area
will shift to the top side of the area itself.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
54 / 142
TASK BAR. It contains the Alcatel logo and the icons of the tasks customized by the user. If you click
with the left mouse button on the icon of task, this causes the task to start. The task bar is customizable by the user, i.e. the user can add task buttons of the most frequently used applications by means
of the utility popup menu, available on each system menu item. See example in the following pages.
On the other hand the user can remove a less frequently used application icon by means of the task
bar popup menu ( Remove item ). The user can drag these icons by pressing the middle mouse
button.
Left arrow
Right arrow
TASK BAR
LAYERED ICON AREA
iconified windows
It contains:
left arrow. If you click with the left mouse button on it, the icons contained in the layered icon area
will shift to the lefthand side of the area itself.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
55 / 142
TASK BAR. It contains the Alcatel logo and the icons of the tasks customized by the user. If you click
with the left mouse button on the icon of task, this causes the task to start. The task bar is customizable by the user, i.e. the user can add task buttons of the most frequently used applications by means
of the utility popup menu, available on each system menu item. See example in the following pages.
On the other hand the user can remove a less frequently used application icon by means of the task
bar popup menu ( Remove item ). The user can drag these icons by pressing the middle mouse
button.
layered icon area. This area contains the icons of the browser windows actually opened. If you click
with the left mouse button on the icon of a browser window, this causes the window to open.
6.5.2 Menus
INTRODUCTION
To lauch the application/function associated to a single item, select the item with the left mouse button
MENU DESCRIPTION
Point with the right mouse button to an empty area of the horizontal task bars.The main popup menu is
displayed. See below figure.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
56 / 142
System menus. System menus contains a cascode menu of the main system applications.
User menus. This menu is customizable by the user by means of the utility popup menu, available
on each system menu item. See example in the following pages.
Close main panel. This menu item closes the panel. The panel opens automatically at browser startup.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
57 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
58 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
59 / 142
Figures which follow show the icons of the corner and edge panel
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
60 / 142
Move applet. If you click on this menu, you will be able to move the involved icon by dragging it by
means of the left mouse button. It is the same as using the middle mous button ( pressed ) to drag
icons
Properties...
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
61 / 142
Background:
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
62 / 142
The Global Properties menu item, if selected, allows to display/modify panel configuration. Figure which
follows shows the Global Panel Configuration first dialog box: Animation.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
63 / 142
Auto hide animation speed ( in ms ) = delay to disappear of the panel when you move the pointer outside
the panel. This modality is in effect if you previously selected AutoHide in the Panel Properties: Edge
Panel view. ( see previous paragraph.)
Explicit hide animation speed ( in ms ) = delay to disappear of the panel when you move the pointer
outside the panel and a window overlaps the panel. This modality is in effect if you previously selected
AutoHide in the Panel Properties: Edge Panel view. ( see previous paragraph.)
Drawer animation speed= N.A.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
64 / 142
Auto Hide minimize delay ( in ms. )=delay to appear of the panel when you move the pointer inside the
panel. This modality is in effect if you previously selected AutoHide in the Panel Properties: Edge Panel
view. ( see previous paragraph.)
Auto Hide minimized size ( pixels )=size of the remaining bar when the most part is hidden ( the survivor,
look carefully...)
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
65 / 142
keep menus in memory. This option can be used to speedup panel performance.
Remaining options are not applicable.
.
BUTTONS...
On the other hand the user can remove a less frequently used application icon by means of the task bar
popup menu ( Remove item )
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
66 / 142
Tooltips enabled=enables the display of the icon help textstrigs which appear when you move the mouse
pointer over the icon
Point with the mouse to an empty region of the panel, press the right mouse button to open the
popup menu. Select Global Properties menu item.
b)
From the Global Panel Configuration window click on Miscellaneous button. The Miscellaneous
dialog box page is displayed. Select option Show...buttons. Click on OK button to confirm and close
the dialog box. If you click on Apply to confirm, the dialog box remains open.
c)
Select the command or the group of commands you want to customize, marked by the button shown
in the figure below.
ED
01
a)
If you select Add this as drawer to panel, the Path Provisioning icon will be added to the
panel, as in Figure 46. herebelow. Clicking on the icon a vertical panel is raised, containing
the icons of the commands included in the subgroup of commands.
SC.2:GETTING STARTED
3AL 61348 AA AA
142
67 / 142
If you select Add this to personal menu, the Path Provisioning icon will be added to the
panel, as in figure herebelow. Clicking on the icon a vertical panel is raised, containing the
icons and the textstrings of the commands included in the subgroup.
Figure 47. Utility button: Add this as menu to panel for a group of commands
c)
ED
01
If you select Add this as menu to panel, the Path Provisioning icon will be added to the
personal menu. Clicking on the icon a vertical panel is raised, containing the icons and the
textstrings of the commands included in the subgroup.
SC.2:GETTING STARTED
3AL 61348 AA AA
142
68 / 142
a)
If you select Add this launcher to panel, the Path Creation wizard icon will be added to the
panel. Clicking on the icon with the left mouse button, the application starts.
b)
If you select Add this to personal menu, the Path Creation wizard icon will be added to the
panel.
With reference to Figure 49. , if you want to add the icon of the path create to the task bar, select System
menus: Path Provisioning: Path Creation Wizard: Add this to launcher panel
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
69 / 142
Figure 49. System menus: Path Provisioning: Path Creation Wizard: Add this to launcher panel
NOTE
The window icon popup menu allows to close or restore the window
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
70 / 142
7 VIEWS DESCRIPTION
7.1 Overview
The User Interface of the 1354RM is the Browser. It allows to open many applications.
Netview allows to create and display the topological objects (Network, Subnetwork, Ring, Node, SDH
Port) and the physical connections involved.
In any submap, by clicking twice on an object, the submap associated to the object proper opens.
The different submaps are described in next Chapter Navigation. It describes the Navigation procedures
among the Netview submaps.
The available submaps are:
Network submap.
Subnetwork submap.
Link submap.
a main view which allows to navigate among all the topological and connectivity objects;
LO Paths in a HOTRAIL
Node view
Nap view
ED
Path List
Trail List
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
71 / 142
NAP List
CTP List
CAP List
Port List
Performance Measure List
Alarmed Object List
Alarm Profile List
Path Constraints
PM Measure Create
PM Measure Correlate
transports (trail/path)
Event logger
7.2.1 Wizard
Wizards make use of a driven approach to better help the user in executing the requested procedures.
In the fact each wizard is constituted by a fixed sequence of dialog boxes. Per each dialog box the user
is requested to enter some parameters or names or values, and after filling the box the user passes to the
subsequent box by clicking on Next button.
Each box ( with the exception of the first one ) contains also the button Previous, which allows the user
to check / change the previously entered values.
The last dialog box contains the button Finish, which launches the execution of the procedure concerned.
Wizards are easy and friendly to the user, since they do not require to navigate through the browser to
select objects to be dropped: namely they contain dedicated selection buttons, which provide lists of the
objects suitable to be inserted to fill the wizard dialog boxes. Notice that these lists are filtered according
to the parameters entered in the previous dialog boxes.
It is also possible to navigate through Netview map to select the objects to insert into the dialog boxes.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
72 / 142
PULL_DOWN MENU
SHOW/SET
ATTRIBUTES
GET PARENT
GET PARENT
OBJECT
EXIT
POPDOWN
ALIGN ITEMs
SHOW USER
ZOOM TOOLS
HIGHLIGHT
CREATE TOOLS
SAVE
COORDINATES
MOVE NODE
HIDE BACKGROUND
RESIZE OBJECT
SAVE
BACKGROUND
OPEN
SECONDARY VIEW
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
73 / 142
Menus and tool buttons change according to the selected object. By moving the mouse over
the tool button icon, a ballon help is shown, explaining the operation invoked by the button itself.
This item allows the operator to zoom into a defined view rectangle. Click on Activate Window Zoom
button. Click on the first corner of the area to zoom and drag to the second corner of the area to zoom,
thus drawing a rectangle on the map. See following figure.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
74 / 142
N.B.
Release mouse button. The selected rectangle fits the working area. See following figure.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
75 / 142
a)
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
76 / 142
The display of the physical connections can be filtered by means of the Available Layers button, present
on the tool button palette, which allows to display separately the map connectivity.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
77 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
78 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
b)
ED
Clicking twice on the network icon, the network map is opened. It contains the subnetwork symbols
along with their physical connections (see example in Figure 57. )
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
79 / 142
Clicking twice on the subnetwork icon, the submap of the objects belonging to that subnetwork is
opened (see example in Figure 58. )
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
c)
d)
ED
Clicking twice on the icon of the 2nd level Subnetw, the submap of the objects belonging to it is
presented (see example in Figure 59. on page 81)
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
80 / 142
Clicking on the Physical Connection group, the Physical Connection list opens.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
81 / 142
Select the Physical Connection and click on icon Physical Connection structure. The Physical Connection
structure opens.
On each object represented in the map, the object popup menu can be opened. See Figure 62.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
82 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
83 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
84 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
9 BROWSER
9.1 Introduction
The Browser is a Motif based application which provides multiple navigation views. It supports full view
of MIB data objects or tailored views. The commands available in the browser depend on users profile.
The Browser supports:
Help on item (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button/object.
Contextsensitive help. If you select the object and the pulldown menu Help on selected
object, the Worldview application starts and displays automatically the description of the
selected object class.
The Browser is based on the approach to enable navigation into all, a portion or a view of the containment
tree.
Objects are presented with:
An icon related to the class (a bitmap) that can be related to one or more attribute values.
Example:
An alarm icon that appears only when the object is alarmed, whose color is related to the alarm
status value.
ED
Indentation
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
85 / 142
Details
Select
ED
Search (Display)
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
86 / 142
pulldown menu
window title
counters
item
balloon
help
area
info
work area
ED
SC.2:GETTING STARTED
3AL 61348 AA AA
142
87 / 142
logo
values of displayed attributes.You get this information moving the mouse to the
involved object in the work area.
function button description. You get this information moving the mouse to the
involved button in the button box.
events flag indicator (Create not processed, Delete and Update processed).
Display parent item. It corresponds to the pulldown command Actions:Search:Parent and/or to the
popup command Search:Parent.
Align item(s). It corresponds to the pulldown command Actions::Align item(s) and/or to the popup
command Align item(s).
Topology tools. If you click on this button a submenu is opened. It includes the following buttons:
go to parent menu
go to home menu
Create Node
Create Physical Connection
Shared Risk Group Management
Configuration Tools (CFG). It shows the configuration tools. If you click on this button a submenu
is opened. It includes the following buttons:
ED
go to parent menu
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
88 / 142
go to home menu
Payload configuration
Concatenated rates setup
create HO trail
add/remove protection
Path tools. If you click on this button a submenu is opened. It includes the following buttons:
go to parent menu
go to home menu
Create path
Add Constraints to a path/trail
Add leg to a path
Show scheduled operations
WDM Connectivity Tool
Add/Remove protection
Alarms tool. If you click on this button a cascode submenu is opened. It includes the following
buttons:
PM. It shows the performance monitoring tools. If you click on this button a submenu is opened. It
includes the following buttons:
Create Measure
Correlate transport to a measure
Merge measure
Show PM Data
Tools
go to parent menu
go to home menu
Active counters
Event Log. It starts the Event Log application.
In the Total, Visible and Selected field are shown respectively the total number of displayed items, the
number of visible items and the number of selected items.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
89 / 142
Label
Item
Object filtering and scoping is supported throught the Search:Main related items and Search:All related
items.Filtering can be performed with:
Using the popup Search:Main related items or Search:All related items, or selecting one or more items
and using the icon button Display Related Items or the pulldown Actions:Search:Main related items or
Actions:Search:All related items a Chooser window of available navigation is shown:
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
90 / 142
Clicking on the Options ... button the Define Query For window is shown (see next paragraph)
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
91 / 142
Window label
The window label is: DEFINE QUERY FOR <object class name >
Selection parameters
Control buttons
The lefthand column contains the list of all the attributes of the selected object
The central column (option button) specifies the filter condition. A popup menu can be opened, which
allows to select among the options.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
92 / 142
If attribute is of type string the popup menu which can be opened is the following:
None.
No filtering is specified.
Start with.
This filter condition provides the instances which start with the speci
fied string in the relevant MIB data.
Match exactly.
Contains.
This filter condition provides the instances which contain the speci
fied string in the relevant MIB data.
End with.
This filter condition provides the instances which ends with the speci
fied string in the relevant MIB data.
Doesnt contain.
This filter condition provides the instances which do not contain the
specified string in the relevant MIB data.
If the attribute is of the type enumerated, the popup menu which can be opened is the following:
None
Equal to
Not Equal to
If the attribute type is date, the popup menu is:
None
Before
Since
Exactly
If the attribute type is integer the popup menu is:
None
Equal to
Not equal to
The righthand column contains the attribute values. The value can be entered in text field, for the types
integer, date and string. The value can be entered as option for the type enumerated.
The function of the filter is an AND of all the previously specified conditions.
In case the selection is handled by pointers instead of containment tree, the filter is disabled.
9.1.7 Show/Set Attribute
The Show attribute operation is startable from popup Details:Show/Set attributes, from the pulldown
Actions:Details:Show/Set attributes and from Show/Set attributes icon and allows to display the
ATTRIBUTE VALUES FOR window that shown the item attributes retrieved.
The ATTRIBUTE VALUES FOR window is quite similar to the DEFINE QUERY window and is used to
display or change value in MIB of the selected objects attributes. This window has a standard structure,
( see Figure 67. ) described in the following:
ED
Window label
01
The window label is: ATTRIBUTE VALUE FOR <class> <item label>
SC.2:GETTING STARTED
3AL 61348 AA AA
142
93 / 142
Parameters
Control buttons
group
buttons
non modifiable attribute
set button
select within a path list already displayed in the browser, all the paths where the configuration state
is allocated and the customer name matches a given value or pattern. After the selection, the
configuration action required can be issued.
The available commands and the behavior result from the following table:
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
94 / 142
Command
Select All
Browser
Main Window
Not available
Browser
Multi Column Lists
Browser
Graphical Views
Select
All the children of the given Not available
All related items selected object are selected
Unselect All
Not available
All the selected objects All the selected objects All the selected objects
are unselected
are unselected
are unselected
Select
related A mask with the possible Not available
items ....
children classes for the selected object is presented.
From this mask, the user
can select a class and, optionally, the detailed filter
to be applied (see description for multicolumn
view)
Select ....
N.B.
Not available
This operation can be executed either from the Actions pulldown menu, that starts the get operation of
all selected objects (they MUST belong to the same class) or from the object popup menu that starts the
get operation only on that object.
This operation can also be launched by doubleclicking the object or clicking on the Get object from MIB
icon of the icon bar.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
95 / 142
SEQUENCE
Select (left click) one or more object to browse and Actions: Search: Main Related items....
The related item selection window is displayed. This window contains the list of child classes of the
selected object.
b)
Select the class to display and the search mode (Filter/No Filter). If you select No Filter the related
objects (children) of the selected object are displayed below the father icon.
If you select Filter the Define Query window is displayed (See Figure 66. ).
The box containing the available related objects is indentated with respect to the symbol of the father.
c)
You can continue displaying related items for an object selecting again Search: Main related items
popup or pulldown menu item, according to the database hierarchical tree.
NOTE
The output of the Search Main Related items operation can be in normal format, i.e. displayed indentated
in graphical way, or in multicolumn format or by means of dedicated views, i.e. giving a compacted list
of the browsed objects.
9.1.11 Actions: Search: All Related items...
This command is analog to the command Actions: Search: Main Related items... (see paragraph
9.1.10)The only difference is that all related items are available to be displayed.
9.1.12 Actions: Search: Parent.
The purpose of this procedure is to retrieve from the MIB data base information related to objects that
contains the selected one. The relationship between the selected object and its parent is described in the
object containment tree. More in detail, this relationship can be though as a fatherchild relationship or
a pointer relationship.
This operation can also be launched by clicking on the Get parent object from MIB icon of the icon bar or
from the object popup menu.
a)
b)
The Parent object is displayed in the Browser window below the icon of the child object.
9.1.13 Actions: Select: Related Items....
This menu, if selected, provides a mask with the possible children classes for the selected object.
From this mask the user can select a class and, optionally, the detailed filter to be applied.
This operation can be executed also from the object popup menu.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
96 / 142
a)
b)
Select (left click) one/ more object/s whose child class has to be forgotten.
b)
Make use of the Actions pulldown menu. Select Close: Items by Class.
c)
The child selection window is displayed. One/more child class can be selected (left click).
d)
Pressing the OK button the select classes are removed from the screen.
Select (left click) one/more object/s whose related items have to be removed.
b)
This operation can be executed from the object popup menu and the pulldown menu.
a)
b)
Select Actions: Align item(s) or by using the right mouse button, select Align item(s)
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
97 / 142
This allows to show attributes of an object or modify the value of the simple attributes (Modifiable at UI)
in the MIB data base.
This operation can also be executed by clicking on the Show/Set attributes icon of the icon bar or from
the object popup menu.
a)
b)
Select Show/Set attributes. A dialog box is presented. It contains the objects attributes.
The attribute that cannot be modified is displayed without any
If the user selects the option Set, will enter the new value in the area of the field (string, integer and
date type) or set the new enumeration value.
If the user selects the option Set to default, the attribute will be set to the default value.
c)
After entering the modifications, select Apply. The attribute will be modified.
The Show/Set dialog box also contains the Cancel button, which causes to abort the procedure and
close the window and the button Help providing the relevant Help information.
a)
b)
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
98 / 142
Report full...
Report short...
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
99 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
100 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
PROCEDURE
a)
Select Options:Deferred Actions. Select the action to schedule. A dialog box is displayed (lefthand
side of Figure 71. ).
b)
c)
d)
Click on the scrollbar. A selectable list is displayed (rigthhand side of Figure 71. )
Select the time value and click on OK. The selected value is copied into the lefthand side box.
Selecting OK the action on path will be executed at the specified time.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
101 / 142
popup ( or double click ). This menu, if selected, causes the redisplay of the iconified window on
the screen.
popdown. This menu, if selected, iconifies in the browser working area the relevant window.
close. This menu closes the window.
9.1.28 Specific
It contains menus which depends on the selected item (typically specific actions).
9.1.29 Windows
It contains the list of opened windows (views and multi column lists). Iconified windows can be deiconified,
deiconified windows can be iconified.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
102 / 142
9.1.30 Tools
9.1.31 Navigations
It allows to open views containing items built after AS navigation and navigation from external tools
(eg: setup trail, path creation). The menu has following submenus:
ED
from AS. It opens a browser instance containing objects navigated from the Alarm Surveillance
application.
from Others. It opens a browser instance containing objects navigated from the Netview application.
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
103 / 142
The Active Counters feature offers a way to monitor objects that match a given condition (defined on the
objects attributes) and to detect objects matching the condition
A simple but complete GUI allows the user to perform these tasks (creating/modifying/deleting counters
(with their conditions) and monitoring objects) easily and quickly.
9.2.1 Overview
This section briefly describes how Active Counters feature works while illustrating the structure of this document.
Every counter is defined by a name (its identifier), a description (generally longer than the name and useful
to understand/remember the meaning/use of the counter) and a condition.
A counters condition is defined by the class to which is applied (route, high order CTP, TMLSTrail, etc.)
and a list of terms that represents the subconditions to apply to the single attributes of the class elements (see 3.1 Conditions).
In addition to schema classes, metaclasses (see 2 Metaclasses) can be used to define conditions
Given the counters condition, if we define a time origin that we call epoch, at a given time (equal or subsequent to the epoch) we can calculate four values:
the number of objects losing the condition since the epoch (out)
the number of objects taking the condition since the epoch (in)
the objects repeatedly losing and taking the condition since the epoch (upsanddowns)
These four values are called subcounters (of the counter) and are the values that the user will monitor.
The Active Counters feature uses as an epoch the time at which the user activated it. While the feature
is active the user can reset the epoch of any of the counters (or all of them) to the current time, so to restart
the count.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
104 / 142
9.2.2 Metaclasses
Metaclasses are virtual groups of classes, in order to handle counters defined on more than one class
Metaclasses have no real disadvantages over multiple classes while having two main advantages:
the logic of the feature is simpler, thus keeping the design simple and, therefore, lowering the cost
of implementation and maintenance;
from a user perspective, conditions that spawns multiple classes behave exactly as singleclass conditions. Moreover the user doesnt need to know whether hes dealing with a single class or a metaclass.
Metaclasses are configured on a per USM machine basis, so they are stored in the file system of the machine that hosts the USM. This means, amongst other things, that, if there is more than one USM machine,
is to the administrator to supply every machine with its own copy of the metaclasses configuration file.
Metaclasses can only be defined/modified/removed by the administrator while other users can only use
them.
In this document we will talk of simple classes when we wish to refer to schema classes, we will talk of
metaclasses when we wish to refer to metaclasses and we will talk of classes referring to both schema
classes and metaclasses.
9.2.2.1 Structure of a metaclass
A metaclass is made of the following components:
metaattributes: a set of virtual attributes that group the attributes of the joining classes;
joining classes: a set of simple classes that join the metaclass and, for each simple class, the attributes of that class that join the metaattributes.
A metaclass is subject to the following constraints:
the name of the metaclass must be unique among class name, i.e. it cant have the same name of
an existing simple class or of another metaclass;
two metaattributes (of the same metaclass) cant have the same name: while two metaattributes of
different metaclass can;
only countable simple classes may join metaclasses: metaclasses and noncountable simple
classes cant;
a joining class associates one (and only one) of its attributes to each metaattribute, if a joining class
does not associate any attribute to one or more metaattributes, we say that the joining class does
not handle the metaattribute;
the simple attributes joining a metaattribute must be of compatible, i.e. one of the following condition
must be true:
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
105 / 142
As already told, metaclasses have been designed to minimize their impact on design, while needing some
support at implementation level.
In practice, a counter based on a metaclass is implemented creating one counter for each joining class.
Each derived counter has a condition obtained converting the original (meta)condition, in this way:
the terms of the derived condition are the original terms, except that:
if the metaattribute of the original condition is handled by the joining class, the attribute of the
derived condition is the joining attribute for that joining class;
if the joining class does not handle the metaattribute of the original condition, the term is not
included in the derived condition.
In spite of all this deriving/translating work, the end user only sees the original counter, while the derived
counters are invisible to him.
9.3 Counters
Every counter is defined by:
a description: generally longer than the name and useful for the user to understand/remember the
meaning/use of the counter;
a condition: a counters condition is defined by the class to which is applied (route, high order CTP,
TMLSTrail, etc.) and a list of terms that represents the subconditions to apply to the single attributes of the class elements
Given the counters condition, if we define a time origin that we call epoch, at a given time (equal to the
epoch or after it) we can calculate four values:
the number of objects losing the condition since the epoch (out)
the number of objects taking the condition since the epoch (in)
the objects repeatedly losing and taking the condition since the epoch (upsanddowns)
These four values are called subcounters (of the counter) and are the values that the user will monitor.
The epoch is the time at which the user activated the Active Counters feature. While the feature is active
the user can reset the epoch of any of the counters (or all of them) to the current time, so to restart the
count.
In addition to the concise view of subcounters, the user can inspect the situation with greater detail displaying the list of the items that are counted by a specific subcounter. These lists are implemented using the
standard Browsers list, with the notable exception of lists opened for counters base on metaclasses. In
this case, in fact, we have implemented a special multilist widget that, visually similar to a standard browsers list, is capable of displaying multiple lists of items in the same window.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
106 / 142
Active Counters are defined and used on a per user basis, so that every user will have/will be able to create
its own counters independently from other users. Note that different Unix logins, even impersonating the
same operator, are considered different users.
A requirement for Active Counters is persistency for different sessions of the same user.
This current implementation supplies a per USM machine persistency, i.e. the counter definitions are
stored in the file system of the machine that hosts the USM. This means that different machines hosting
the USM will have different counter definitions. Moreover, because of the per user nature of the counters
a unique configuration file in the users configuration directory will store its definitions.
9.3.1 Conditions
A condition is defined by the class to which is applied (route, high order CTP, TMLSTrail, etc.) and a list
of terms that represents the subconditions to apply to the single attributes of the class elements.
Classes that can make part of conditions can either be simple classes or metaclasses. But non all simple
classes can make part of conditions: in fact, not all simple classes are suitable/sensible to be counted (e.g.
classes that are never instantiated, but serves only as base classes to derive from). The subset of countable classes is not configurable by the end user.
The conditions are generic and are based on AND/OR of terms.
A condition is of the form:
(term1 OR term2) AND term3 OR Term4
(term1 OR term2) AND term3 OR Term4...AND termn
where termi (for i=1,...,n) is of the form:
termi = attri opi value
so, termi is true if applying opi to attri and valuei returns true.
Not all attributes of countable classes are allowed to make part of terms, in fact, only enumerated or string
attributes are allowed and only if they are primitive attributes (so IATTR and XATTR are excluded).
For what regards the operators:
if the terms attribute is an enumerated one, the possible operators are: equal and not equal;
if the terms attribute is of string type, the possible operators are: starts with, matches exactly, contains, ends with, doesnt contain and differs from.
Finally the value must be compatible with the attribute, so:
if the attribute is of enumerated type, the value must be one of the enumerated values;
9.3.2 NAD
From an NAD point of view, active counters created by a certain user take into account only objects that
such user can access (or at least objects on which it has some visibility). Then:
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
107 / 142
every objects security label is known: i.e. AVC events (and also other events) must bring security
label;
a function that, knowing the users rights, filters incoming events basing on the users access rules.
Currently these two requirements cant be achieved, therefore, at least for this first release, the active
counters feature will behave differently, depending on user type:
for administrators: objects handled by the feature will be all the object accessible by the operator (i.e.
all);
for nonadministrators: each counter will count every object satisfying its condition (also those not
visible/accessible by the user), but only accessible objects will be displayed by lists.
9.3.3 FAD
As for NAD, there is a different access/use of functions whether the operator is an administrator or not:
if the operator is an administrator:
operator will be able to define new metaclasses and/or modify existing ones , to be used by all the
operators;
all the lists opened through the Status Window will update in realtime, thus reflecting the respective
counters status ;
any lists opened through the Status Window will not update, unless the user requests a refresh.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
108 / 142
the Status window: a flying window that allows the user to display and manage the counters;
the Create/Modify/Show Counter widget: a widget that will allow the user to create, show and/or
modify existing active counters;
the Multilist widget: a modified Browsers list that displays items from different classes.
9.4.1 Monitoring
The Status Window is a standard window provided with its own menu, its own toolbar and the list of active
counters defined by the user.
The user will open the Status Window through the Tools menu of the Browsers main window .
Each counter can be selected by the user to perform a specific action on it. The selection is single, so only
one by one actions can be performed on active counters (e.g. is not possible to delete multiple counters
with a single action).
The counters are presented in a tablelike layout, showing for each active counter the following items:
the Counter name: a user defined label used to identify the counter
the Tot (Total) count: the absolute number of objects that match the condition;
the In count: the number of objects taking the condition from the last reset command;
the Out count: the number of objects losing the condition from the last reset command
the Up&Dw (Upsanddowns) count: the number of objects doubleflipping the condition from the
last reset command.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
109 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
110 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
PULLDOWN MENUS
POPUP MENU
Figure 75. Status window menus
The monitor window displays all the active counters defined by the user and allows him to:
show an existing counter definition either via the Actions menu (that will show the selected counter),
via the popup menu (that will show the active counter on which the right click has been performed)
or using the toolbar;
modify an existing counter definition either via the Actions menu, via the popup menu or using the
toolbar;
remove an existing active counter either via the Actions menu, via the popup menu or using the toolbar;
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
111 / 142
reset an existing active counter (resetting In, Out and Upsanddowns values) (via the Actions
menu, via the popup menu or using the associated toolbar icon);
reset all existing counters (via the Actions menu, via the popup menu or using the associated toolbar
icon), after a user confirmation;
create a new active counter (via the File menu or using the associated toolbar icon)
counter save (via the File menu or using the associated toolbar icon); If a counter is changed and
the operator doesnt use this save, when he will close the Status Window a popup will point out the
loss of modification if the save is not invoked and the confirm of the exit operation.
show the list of counted items via the Actions/Lists menu, via the Lists submenu of the popup menu
or as follows:
double clicking on the In value will open the list of objects taking the condition of the active
counter from the last reset;
double clicking on the Out value will open the list of objects losing the condition of the active
counter from the last reset;
double clicking on the Tot (Total) value will open the list of objects that match the condition of
the active counter;
double clicking on the Up&Dw (Upsanddowns ) value will open the list of objects doubleflipping the condition of the active counter from the last reset.
The lists opened are not uptodate, they can be uptodate using the refresh function.
Even if not shown in the above figures, the columns for the four subcounters have different background
colors, in order to quickly recognize them. In addition, when a subcounter leaves the reset state its cell
is highlighted to capture the attention of the user.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
112 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
113 / 142
When the class is chosen, more elements of the window are enabled and is possible to create the condition terms.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
114 / 142
In this form all is disabled but the two text fields (name and description of counter), the option box for the
choice of the class to monitor and the cancel button to annul the counter creation.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
115 / 142
ED
if the attribute is an enumerated one, an option box with the two foreseen operators (equals, not
equals) is followed by a list box with the attribute possible values:
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
116 / 142
if the attribute is of type string, an option box with the string operators (Starts with, Matches exactly,
Contains, Ends with, Doesnt contain and Differs from) is followed by a text box in which the
user will type the string to compare to the attribute:
the list with the multiple selection Subconditions, lists all terms created by user and all partial condition created joining two or more terms;
in every moment, it is possible to create new terms clicking on Add new up to the maximum limit of
six terms;
if a term is selected in Subconditions and you click on Modify, the term modify form is opened.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
117 / 142
if one or more elements (simple terms or partial condition) are selected, it is possible to delete clicking
on Remove (with a confirm by the user);
if two or more elements (simple terms or partial condition) are selected, it is possible aggregate them
using AND Join or OR Join, so a new partial condition with the selected elements joined by AND
or OR (according to the push button selected) is obtained. Moreover, the original elements are eliminated. If, for example, we select the fist two terms and clicking on AND Join we obtain:
ED
if one or more elements that represent partial condition are selected, it is possible to decompose
them using the Split button. See above figure. Split cancels the previous aggregation operation. So,
selecting on the first row of the above figure and clicking on Split, the following arises:
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
118 / 142
since the partial condition can became long, can be difficult for the user examine a partial condition
only using the Subconditions list, so the last partial condition selected is displayed completely in
Selected subcondition field;
the Overall condition shows as would be the final condition if all partial conditions were aggregated
using the function button (AND or OR) ;
the OK button confirms the counter creation with the condition shown in condition
9.5.1 Modification
The form of counter modification is equal to the creation one but the differences described below:
The form shows counter data (name, description, class and condition);
Modifications that involve attributes and values (i.e. all except renaming), if successfully completed, reset
the counter (i.e. the Total counter is recomputed and the In, Out and Upsanddowns counters are reset).
To modify the active counter, first select the counter and the issue the Modify popup menu. See
Figure 84. herebelow.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
119 / 142
9.5.2 Visualization
For the visualization of Active Counters, issue the popup item Show. The same form of modification is
used except that user cannot modify values. See figure which follows.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
120 / 142
Lists are displayed using the standard Browsers lists, sole exception are lists for metaclasses that are
displayed using the special Browsers multilists that allow to display multiple list of objects of different
classes into the same window.
The lists opened from Status Window (with double click on the column chosen) have as title the column
name (In, Out, Tot, Up&Dw) followed by the counter name.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
121 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
122 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
10.1 Introduction
Drawing windows support:
Help on item (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button/object.
Contextsensitive help. If you select the object and the pulldown menu Help on selected
object, the Worldview application starts and displays automatically the description of the
selected object class.
ED
Icon bar
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
123 / 142
Close window. It forget the window and all its opened ones. This operation can also be executed
from the pulldown menu (File:Close).
Hide window. It hides the window. It can be redisplay without any reget. This operation can also
be executed from the pulldown menu (File:Popdown).
Go to the parent window. It goes to window from which this one has been opened. The current
drawing is hidden or not, depending the status of Options:Close window going to parent on browser
main window (see paragraph 9.1.27)
Display Main Related Items. It navigates the selected object(s) on browser main window. The
children chooser is automatically proposed (Main related items). This operation can also be executed
by double click on object or from the object popup menu (Search:Main related items)
Show/set attributes. This allows to show attributes of an object or modify the value of the simple
attributes (Modifiable at UI) in the MIB data base. This operation can also be executed from the object
popup menu (Details:show/Set attributes) or from pulldown menu (Actions:Details:show/Set
attributes)
Align items (s). It alignes the data displayed on the screen to MIB data. Almost one object must be
selected. This operation can also be executed from the object popup menu (Display:Align items(s))
or from pulldown menu (Actions::Align item(s))
Refresh this window. It deletes all items and regets all data. Note that all children
views/multicolumns lists are closed.
Order Items. It allows to manage the order and size of the table columns
Hide/Show attribute counter. It allows to display the attribute counters referred to the displayed
list
The second row depends on the specific view. It typically allows to open an application (eg. Setup trail,
Payload configuration, Path/Trail constraints) or views to create instances or to correlate objects to each
others).
The third row depends on selected class. It dynamically shows icons to open view/multicolumn list
associated to selected object.
10.1.2 Work area
In the Drawing window, the work area displays the retrieved items typically located on graphic background
to show the relation to each other. Inside the work area are often displayed particularly items (named
group) from which other view/multicolumn lists can be opened).
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
124 / 142
The Icon bar area is subdivided in three rows. The first one contains the following buttons:
11.1 Introduction
Multicolumn lists windows support:
Help on icons (Balloon help). A textstring describing the function is presented if you leave the
mouse more than one second on the functional button
Contextsensitive help. If you select the object and the pulldown menu Help on selected
object, the Worldview application starts and displays automatically the description of the
selected object class
Multicolumn lists windows have the following look (see Figure 88. on page 128 )
ED
Icon bar
Title area
Counters area
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
125 / 142
Save all as. This command saves the lists content on specified file
Save selected as. This command saves the selected items on specified file
Views: Save. It allows to save the view. To redisplay the saved view, issue from the task bar
the menu Saved Views selecting the desired view from the item list.
Close. This command closes the multicolumn list window. The group icon displayed on Browser
main disappears, the one displayed on drawing window change its colour.
Search
Select
Details
Align item(s)
Align view
Remove from RM
ED
Columns.This option allows to perform a column reordering. If you select this option, a column
reordering window is presented, containing the fields which allow to move the columns, perform
text string justification and change the column width. After executing the changes you can select
Apply, to apply the changes to the list, OK to apply the changes while closing the column
reordering window or Cancel, to close the window without any change.
Sorting. This option allows to perform a list sorting. If you select this option, the Sorting window
is displayed, containing the fields Priority and Condition.The priority field allows to assign a
sorting priority among the object attributes. The field Condition allows to assign an increasing
or decreasing sorting condition. After executing the changes you can select Apply, to apply the
changes to the list, OK to apply the changes while closing the sorting window or Cancel, to close
the window without any change.
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
126 / 142
Report. For Path/Trail is available the Report: Route and the command file generator used to
save the list of path/trail that can be reused to rebuild the circuit.
Go to the parent window. It goes to window from which this one has been opened. The current
multicolumn lists window is hidden or not, depending the status of Options:Close window going to
parent on browser main window (see paragraph 13.1.28)
Display related items. It navigates the selected object(s) on browser main window. The children
chooser is automatically proposed (Main related items). This operation can also be executed from
pulldown menu (Actions:Search:Main related items)
Display Parent item. It navigates the selected object(s) on browser main window.
Show/set attributes. This allows to show attributes of an object or modify the value of the simple
attributes (Modifiable at UI) in the MIB data base. This operation can also be executed from the
pulldownmenu (Actions:Details:show/Set attributes)
Align items (s). It alignes the data displayed on the screen to MIB data. Almost one object must be
selected. This operation can also be executed from the pulldown menu (Actions:Align item(s))
Change filter criteria. It allows to change the filter criteria and retrieve again the list using the new
criteria
Refresh window. It deletes all items and regets all data. Note that all children views/multicolumns
lists are closed. This operation can also be executed from the pull down menu(Actions:Align view)
The second row depends on the specific multicolumn list. It typically allows to open external
application (eg. Setup trail, Payload configuration, Path/Trail constraints) or views to create
particularly instances or to correlate objects to each others).
The third row depends on selected class. It dynamically shows icons to open view/multicolumn list
associated to selected object.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
127 / 142
It contains icons related to parent class and the displayed class (with their names), the title of list, the total
number of displayed items and the number of selected ones.
11.1.4 Counters area
It contains counters related to most significant attributes with their values. To change displayed attributes
please open Ordering items window.
11.1.5 Work area
In the multicolumn list window, the work area displays the retrieved items in according to selected order
and sorting criteria, and to specified filter criteria (if any).
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
128 / 142
Double clicking on the single row, the relevant browser window is opened.
On the selected object it is also possible to start all the objects specific actions (e.g. for Path:
Allocate/Implement, Protect/ Unprotect, Delete, ect...)
11.1.6 Counters and graphs on Browser MultiColumn Lists
A dedicated button is available (see Figure 88. on page 128 ).
Clicking on Hide/Show counters, defined counters are displayed. For each displayed attribute a set of
counters is presented.
11.1.7 Multicolumn list window configuration
11.1.7.1 Ordering items
Open the relevant view following procedure described in paragraph 11.1.1 or paragraph 11.1.2
The view contains in the upper area an option button that allows to read/save user configuration file (active
after Apply button pressing)
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
129 / 142
The scale Fixed columns allows to set the number of fixed columns on multicolumn (to have partial
horizontal scrolling)
The Multicolumn counters and Browser counters buttons allow to display/hide specified counters on
multicolumn or browser
For each attibute of displayed class, it is possible to define the position (to hide attribute choose Ignore),
the justify and the displayed size of name (width).
To change the list, press OK button (the interface will be closed) or Apply button, to abort press Cancel
11.1.7.2 Sorting items
Open the relevant view following procedure described in paragraph 11.1.1 or paragraph 11.1.2.
For each attibute of displayed class, it is possible to define the priority used in sort (Ignore value doesnt
take in account the attribute) and the Condition (Ascending or Descending)
To change the list, press OK button (the interface will be closed) or Apply button, to abort press Cancel
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
130 / 142
All nodes
available from Root Domain (for MultiRM), Network Domain, Network, Subnetwork
Ports
available from ne
SDH Ports
available from ne
PDH Ports
available from ne
Payloadable HOTTP
available from node
CTPs
available from node
Measures
available from pm domain
Monitored NEs
available from pm domain
TCA profiles
available from pm domain
Counter reports
available from pm domain
Threshold reports
available from pm domain
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
131 / 142
Archive session
available from pm domain
PM Transports
available from measure
Paths in Topology
available from root domain, network domain, network, subnetwork, et, node
Alarmed objects
available from network, subnetwork, et, node
Ports in node
monitoring Measures
available from path, trail
Alarms in route
available from path, trail
HO Trail
available from physical connection
Path in Trail
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
132 / 142
Counter reports
available from measure
Related NE
available from pm NE
Restoration rule
available from restoration Domain
Eml domain
available from network Domain
Related NE
available from Eml Domain
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
133 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
134 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
From the Node list ( see Figure 91. ) select the node and click on Navigation button. The Node icon
is displayed in the Browser main window. ( already selected ).
HIGHLIGHT BUTTON
b)
ED
With the node already selected click on button Highlight ( see NO TAG). The node is highlighted in
the Netview submaps as in Figure 92.
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
135 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
136 / 142
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Topology views
Once the correct plugin is installed, you can load the application pointing your browser to the following
URL http://hostname:10 where hostname is the name of the 1354 RM server or alternatively its IP number.
When the Java applet has been completely loaded a security warning appears asking to acknowledge the
necessary permission to the application.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
137 / 142
Clicking yes the application starts and shows an input box asking for username and password to login.
Please insert a username and password registered in the 1354 RM server. If the login is accepted you
should see in the application client area, a window with the server you are connecting to. Right clicking
on this server will present you all the possible starting navigations inside the RM MIB.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
138 / 142
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
139 / 142
The navigation mechanism is quite similar to the unix browsers one. Starting from one of the displayed
views, the element to browse must be selected. Clicking the right mouse button, a popup menu appears
containing all possible navigation that can be required to RM Server. Selecting a navigation, after a while
(there is a progress bar in the right bottom corner of the applet), the new requested view is opened.
The browsed objects and the related (performed) navigations are inserted in the application tree (on the
left side of the applet).
Excel
CSV
13.4 Restrictions
the attribute icons of the graphic views are not yet updated
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
140 / 142
14 ONLINE DOCUMENTATION
14.1 Overview
The help is based on world wide web technologies. The topics are written in html. Netscape Gold is the
browser used to navigate through the html pages and it is also used to edit the user personal pages.
Navigation through the help is also possible using a customized navigation bar permanently displayed in
the left of the help screen
The menu options are in fact entry points to the main help system. Once you have entered the help system
via one of these menu options, hyperlinks enable you to navigate to other parts of the help system and
to view other help topics.
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
141 / 142
INDEX
Browser Main, 85
Buttons
Push buttons, 22
Radio buttons, 24
Actions, 18, 19
Buttons, 18
Pointer, 18
Multicolumn Windows, 125, 135
N
Navigation to/from, Alarms, 52
C
Cascading menus, 27
P
Path List, 131
Popup menus, 27
Pull down menus, 26
D
Drawing Windows, 123
Screen, Lock, 47
SDH Manager, Main functionalities, 49
U
M
Upper case/Lower case characters, 31
User Interface, Standard elements, 17
Menu bar, 25
Menus
Cascading menu, 27
item, 28
Menu bar, 25
Mnemonics, 29
Popup menu, 27
Pull down menu, 26
Mnemonics, 29
Mouse
W
Windows
Layout, 20
Menu, 21
Scroll bars, 21
Workspace, Types of, 46
END OF DOCUMENT
ED
01
SC.2:GETTING STARTED
3AL 61348 AA AA
142
142 / 142
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Interrelationships with 1353NM during Network Construction . . . . . . . . . . . . . . . . . . . . .
1.5 System Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
9
12
12
2 NETWORK CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Network Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Start the Netview application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Save Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Create the network objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 Creating the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 Creating the Subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.3 Creating the 2nd level Subnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.4 Creating Nodes and ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 External Network Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Create the External Network Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 Create Connection to External network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Create Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5.1 Example of SDH create connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6 Introduction to NPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.1 Topology definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.2 Network Protection Architecture Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.3 NPA display & Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.4 NPA modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.5 NPA Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.6 NPA: Specify Ring Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6.7 NPA Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7 Create a 4F STM16 NPE Ring with 1664SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7.1 Creating the Connections between Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8 Takeover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.9 Create a 4Fibre STM64 NPE Ring with 1670SM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
14
14
16
16
18
20
22
27
27
27
30
35
40
40
41
51
57
59
61
62
63
63
64
65
01
050207
ED
DATE
CHANGE NOTE
M.RAGNI ITAVE
V.PORRO ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
1354RM REL.7.2
OPERATORS HANDBOOK
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
1 / 258
67
68
68
68
69
70
70
70
70
72
78
79
84
86
86
88
88
90
90
92
93
95
95
95
103
107
3 TRANSPORT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Path Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Path Create management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 Path Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 10/100Mbits Ethernet management (point to point) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 Multi Path Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.5 Path Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 1 Gigabit path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 1 Gigabit transparent path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 1 Gbit/s Ethernet Rate Adaptive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 LCAS Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 Path creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 Optimized diverse routing of server trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3 Path removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.4 Add/remove bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.5 Activation/deactivation of an intermediate server trail . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.6 LCAS enabling/disabling on an already defined path . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Compatibility tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1 Path creation using 16xGbE boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2 Rate adaptive path : Modification: Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.3 Path: Ethernet mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6 Path Allocate,Implement, Commissioning and Display . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.1 Path Allocate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.2 Path Implement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.3 Path Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
109
109
109
112
112
122
124
125
126
127
127
132
135
135
137
138
138
138
138
141
148
149
156
157
157
158
158
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
2 / 258
159
167
169
173
177
178
180
180
185
190
191
192
192
196
204
204
206
209
209
213
215
215
218
221
221
230
231
231
231
232
233
233
233
237
237
238
239
239
4 NETWORK MODIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Adding a Network Element in a SCNP network, case 1 . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Adding a Network Element (NE) to a SNCP ring case 2 . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.3 Removing a Network Element (NE) from a SNCP ring . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.4 Add Q3 NE to a 2F MS Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.5 Add QB3 STAR NE to 2F MS Spring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.6 Remove Q3 NE / Remove QB3 STAR NE from a 2F MS Spring . . . . . . . . . . . . . . . . . .
4.1.7 Add NE to a 4Fiber NPE ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.8 Remove NE from a 4Fiber NPE ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Add/Remove Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Remove a PDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Removing an SDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.3 Adding a PDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.4 Adding an SDH Tributary Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
241
241
242
243
244
244
245
246
247
247
249
249
249
249
249
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
3 / 258
251
251
251
253
253
254
255
256
257
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
4 / 258
ED
01
14
15
16
17
17
18
19
19
20
21
21
22
23
24
25
26
26
27
28
28
29
30
31
32
33
34
35
36
37
38
39
42
44
45
45
46
46
47
48
51
52
52
54
55
56
57
58
59
60
61
62
SC.3:OPERATION
3AL 61348 AA AA
258
5 / 258
ED
01
63
65
66
67
71
72
73
74
74
75
75
76
76
77
77
80
81
82
83
85
86
87
88
90
90
91
91
92
93
93
95
96
98
99
100
101
102
103
104
105
105
106
110
111
113
114
114
115
116
116
117
118
119
120
122
SC.3:OPERATION
3AL 61348 AA AA
258
6 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
7 / 258
ED
01
188
189
190
191
192
193
194
196
197
198
199
200
201
202
204
205
206
207
208
209
210
210
211
211
212
212
213
214
214
215
216
216
217
219
220
222
223
224
224
225
226
227
228
230
231
233
234
235
236
239
242
243
SC.3:OPERATION
3AL 61348 AA AA
258
8 / 258
1 INTRODUCTION
1.1 Purpose of the document
This document describes al the procedures usually executed by the operator. It refers to a no faults
environment.
ED
NETWORK CREATE
Introduction
Network Construction
Create Connection
Introduction to NPA
NPA modify
Takeover procedure
Takeover procedure
Upload Connectivity
01
SC.3:OPERATION
3AL 61348 AA AA
258
9 / 258
MOVE NODE
NETWORK IMPLEMENTATION
ED
Network implementation
CONFIGURATION
Payload Configuration
AU4 Concatenation
Upload NAPs
Takeover of retiming
TRANSPORT MANAGEMENT
Introduction
Path Provisioning
1 Gigabit path
LCAS Management
Compatibility tables
Join/Split Path
JoinSplit Trail
01
SC.3:OPERATION
3AL 61348 AA AA
258
10 / 258
4 x ANY
NETWORK MODIFICATIONS
Introduction
Introduction
The paragraphs which follow briefly describe the Interrelationships with 1353NM during Network
Construction and System startup.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
11 / 258
This paragraph summarizes the macroactivities to be executed at NM and RM side during Network
Construction. The detailed description of the operations to be carried out at NM side is contained in the
1353NM Operators Handbook, while the paragraphs which follow describe the operations at RM side.
The macroactivities to be executed at NM and RM side are:
On 1353NM: Create NE Directory: Create NE. The NE which has been just created appears
browncolored in the map window
On 1353NM: Select the NE and Start: Supervision: Align Up. The NE is uploaded and assumes the
alarm synthesis color in the map. Check the uploaded hardware with Supervision: Show Equipment.
If needed, complete the hardware provisioning ( command Equipment:Board: Set Board )
CONFIGURATION.
b)
Select TMNOS Manager icon from the horizontal palette: the TMNOS window opens.
c)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
12 / 258
2 NETWORK CONFIGURATION
Network Construction
Payload Configuration
Upload NAPs
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
13 / 258
a)
Start the Netview application. From the browser point to the Network domain icon and issue the
popup menu Search: Related Items. Select Network Map. The Netview opens.
For each submap you can add a background. Select Save Background, select the suitable background
and click on OK.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
14 / 258
SELECT BACKGROUND
SAVE
BACKGROUND
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
15 / 258
During this activity, the operator has to create all the submaps according to the network partitioning levels
and insert inside them all the objects (network, subnetworks, 2nd level subnetworks, nodes, ports and connections).
The following steps have to be executed:
2.3.1 Creating the Network
SEQUENCE
a)
From browser, point to the 1354RM network domain and issue the Create: Network popup menu.
See Figure 4. on page 17
b)
In the Create dialog box enter the Network name and click on Create button. See Figure 3. The Network icon appears in the New Object Holding Area. Drag ( holding the middle mouse button) the icon
into the window.
Many networks can be created. It is not possible to interconnect the networks to each other
N.B.
Alternatively, from browser, point to the 1354RM network domain and issue the Create: Network popup menu. See Figure 4. on page 17
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
16 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
17 / 258
a)
The subnetwork objects are created in the Network submap pointing to the network icon and issuing
the Create: Subnetwork popup menu.
b)
In the Create:Subnetwork dialog box ( see Figure 7. ) enter the Subnetwork name and click on Create
button. The Subnetwork icon appears in the New Object Holding Area
c)
N.B.
Alternatively, from browser, point to the network icon and issue the Create: Subnetwork popup
menu.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
18 / 258
SEQUENCE
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
19 / 258
a)
The 2nd level Subnetwork objects are created in a Subnetwork submap pointing to the subnetwork
icon and issuing the Create: 2nd level Subnetwork popup menu. See below figure.
a)
ED
The Create dialog box is presented. See Figure 10. Enter the following values:
name
01
SC.3:OPERATION
3AL 61348 AA AA
258
20 / 258
SEQUENCE
b)
Click on Create button. The 2nd level Subnetwork icon appears in the New Object Holding Area
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
21 / 258
Drag the icon to the center of the window. See following figure. Double click on the icon to open the
submap.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
c)
The Node object is the representation of the network element in the 1354RM map. A node can be inserted
either in the Subnetwork submap or in the 2nd level submap.
a)
ED
Select the Subnetwork or the ET where the new node has to be inserted and issue the menu Actions:
Create: Node. See Figure 13. The Node Creation wizard is displayed. See Figure 14. Notice that
NAP automatic upload is the default.
01
SC.3:OPERATION
3AL 61348 AA AA
258
22 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
23 / 258
Click on NE list button. The list of the available NEs is displayed. Select the NE and click on Apply
button. The selected NE icon is now present in the list of the wizard.
c)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
24 / 258
available NE list
NE list button
the NE is pasted to the map in the new object holding area( See Figure 16. ) and its related node is
created in the data base. At this time NE SDH ports are automatically uploaded from the controlled network.
d)
Drag the node/s just created to the map working area. See Figure 17. on page 26
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
25 / 258
ED
01
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
new object
holding area
SC.3:OPERATION
3AL 61348 AA AA
258
26 / 258
Select from the map the topology ( subnetwork or ET ), which will contain the new External Network
and issue: Create : External Network.
b)
The Create External Network wizard is displayed. Enter userlabel and location and click on Finish
button. See below figure.
The External Network Reference is created and displayed in the New Object Holding area. You can
drag the object to the center of the map.
From the map select the external network/s to connect and issue Actions: Create: Physical Connection.
b)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
27 / 258
c)
Select the connection type, enter the connection name and click on next button
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
28 / 258
Select the real node from the node list and enter the external network name. Click on Finish button.
d)
NOTE
The user can modify, by means of the Show/Set Attributes window, the userlabel of an external network
and the userlabel of a port belonging to an external network.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
29 / 258
The Create Connection wizard allows to select the connection type among:
SDHCBR/WDM interworking, where CBR=constant bit rate. See Figure 25. on page 33
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
30 / 258
If you select connection type=SDH, you will further select the STM type
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
31 / 258
OPS ( Optical Physical Section ) is used for connections within the same WDM node, originated and terminated to the same node.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
32 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
33 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
34 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
SEQUENCE
a)
From the create connection wizard, select connection type=SDH, STM type and enter the connection name. Click on Next button.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
35 / 258
PORT
LIST
PORT
LIST
Click on ATerm Node List. From the Atermination Node list ( upperright part of ), select the node
to connect and click on Apply button. The icon of the selected Node is now present in the Create connection dialog box.
c)
Click on ATerm Port List. From the Atermination Port list select the port to connect and click on
Apply button. The icon of the selected Port is now present in the Create connection dialog box.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
36 / 258
d)
Execute the selection of the terminating node/port following the modality explained at above points
b) and c). Click on Next button.
e)
f)
Wait... After the connection create the physical connection structure view, if required, is displayed.
See below figure.
g)
ED
Physical connections are implemented during network implementation; however it is possible to implement individually a certain physical connection by means of the command Configuration: Implement. See below figure.
01
SC.3:OPERATION
3AL 61348 AA AA
258
37 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
38 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Having created the connection, an external connection symbol is created in the submaps which
contain the connected objects. The external connection symbol label contains the name of the
object connected at the other end plus the connection name.
The physical connection is created in the map and the parent link is also created, if no other connections between the involved nodes were present. The link label indicates the number of present physical connections.
h)
Linear MSP schemes need to be carefully managed by the operator. For detail see paragraph
which follows.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
39 / 258
A NPA is a set of NEs, protections blocks, physical connections working together to create a dedicated
protection mechanism or grouped together to establish path layer protections
NPAs are:
SNCP, 2f MSSPRings, 4f MSSPRings, Linear MSPs (e.g. 1:n, 1+1), ASON /Fast Restoration
SNCP rings do not use any dedicated protection mechanism related to the ring itself, but, RM treat them
in a special mode for the path routing and protection.
2.6.1 Topology definition
The RM operator builds the network defining:
The partitioning topologies (i.e. network, first / second level subnetworks)
The placement of NEs into the subnetworks (> Nodes)
The interconnections between the Nodes (physical connections) entered manually or using the autodiscovery function (based on J0 or on NE cables)
As a further, independent step, the operator needs to build the NPAs.
No strict relation exist anymore in RM between topologies (used for partitioning) and protections. In previous RM, ET topologies were used to represent both a protection and partitioning of the network
The ET (Elementary topology) can be considered a second level subnetwork removing the payload configuration capability and the statistics related to the configuration
N.B.
For the scenario adding a DXC NE in an MSSPRing (with split operation), the workaround
is to configure the MSSPRing on SH before enabling the download on DXC NE.
N.B.
For the scenario removing a DXC NE from an MSSPRing (with join operation) the work
around is to deconcatenate the concerned AU4s from CT before enabling the download on
DXC NE.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
40 / 258
SCOPE
The scope of this procedure is to create a Network Protection Architecture ( NPA )
The NPA creation tool allows to specify:
the type,
the involved physical connections and, if applicable, their associated role (e.g. Working or Protection for
4fMSSPRing, and Linear MSP).
For ASON NPA, the user must specify also the physical connections used for the interworking with the rest
of the network
A NPA can be defined independently from the Topologies used for the partitioning of the Network. This
means that a NPA can belong to different Topologies of different levels and that Topology can have NEs
and links involved in multiple NPAs
The creation tool can be started from :
A topology: Network, Subnetwork (lev.1 or lev.2)
Within the tool, the involved physical connections can be retrieved browsing from the initial topology(*) or
from a different one reached through up & down navigations.
The NPA definition ends with the creation in RM of a NPA and its visualization on the user Interface
The NPA can be created even if not valid (e.g. a ring can be open or even empty) but RM always provides
to the users the proper warnings.
Dependently from the type of NPA to be created, the creation activity requires different information and
performs different checks:
A SDH physical connection can only belong to one NPA with the following exceptions:
ASON internal / linear MSP
ASON interworking / any other NPA
SNCP / linear MSP (To Be Confirmed )
A SDH physical connection is present in RM also when supported by a WDM network. The server OTS
or OPS physical conn. Are, in RM, not part of any NPA
SNCP rings must have the same uniform rate and east/west sequence is checked for first gen. NEs
SEQUENCE
a)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
41 / 258
The Create: Npa: Step 1: dialog box opens. The following cases may arise:
1)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
42 / 258
By default the NPA Usage Cost cost is set to an RM installation default value but can be modified by the
user. For example if L is the default cost of a physical connection, a meaningful default value for the NPA
Usage Cost can be L/2+1 ( i.e. (L/2+1)*2 )
Applications of the NPA Usage Cost
With the proposed NPA Usage Cost, the routing algorithm behaves for stacked and not stacked ring configuration in a similar way (i.e. for the routing, it is like to have a physical link between two stacked rings)
An additional example of the stability effect of the NPA Usage Cost is the behaviour in case of stacked and
unbalanced rings.
NPA Cost Factor:
The NPA cost factor is an additional parameter of each NPA, enabling a percentage cost reduction for its
links. This cost reduction has the target to balance the NPA Usage cost and makes more attractive the
routing inside a NPA compared to the one outside at least for route longer than a given number of arcs.
In the fact, it is an indicator on how much a Main/Spare routing in a NPA has to be preferred compared
to an external route. It works together with the NPA Usage Cost making more attractive long routes in a
NPA.
If equal 0 it has no effect.
As bigger is set as more the cost of NPA internal route is reduced and as more the NPA attracts the routing.
Changing the default physical conn. cost
In case of particular unbalanced configurations, if the NPA Usage Cost is not enough to avoid the ring
changing, the user needs to properly set the costs of physical connections
RM Rules for Main & Spare in 2f MSSpring
These routing rules are used by RM in order to fulfil the requirements:
The NPA Usage Cost for the rings used by the main is set to 0 and the cost of all its routing resources
(e.g. physical conn). is reduced by a parametric cost factor k (the Main & Spare cost gravity factor)
This is equivalent to say that it is preferred a routing in the ring compared to the best route if its nominal
cost is no more that k times the external optimal route
If the spare uses the same links and passthrough connection of the main, the cost is considered zero.
This tries to prefer main and spare overlapped and finally gives more priority to a D&C configuration
The overlapping on Drop/Insert connections between main and spare is forbidden.This is the driver to differentiate main and spare and has its effect mainly forcing a diversity outside the ring
The cost of using the ring for the spare in opposite direction compared to the main is increased of a cost
n. In the previous versions of RM this opposite direction was totally disabled.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
43 / 258
Selection of NPA type=2 F MS Spring or 4 F MS Spring. Enter NPA name and click on Apply
3)
Selection of NPA type=Linear plus, i.e. 1 + 1 protection. In this case the user must enter:
Mode of operation
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
44 / 258
Selection of NPA type=Linear colon, i.e. 1 to N protection. Enter NPA name and click on Apply
5)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
45 / 258
Selection of NPA type=Fast restoration. Enter NPA name and click on Apply
c)
ED
The NPA Create step 2 dialog box is presented, asking to specify the physical connections to include
in the NPA. Click on Physical connection list button. The Physical connection list opens.
01
SC.3:OPERATION
3AL 61348 AA AA
258
46 / 258
PHYSCON List
APPLY button
Figure 38. Selection of the Physical connections
Select the relevant Physical connections and click on Apply button. The icon(s) of the Physical connections are now present inthe main window. Click on Finish button to launch the creation.
N.B.
ED
In case of 1 to 1 NPA or 1 to N NPA the selection dialog box contains two subwindows, one to
select the main Physical connection (s), one for the protecting one. See example of 1 to N NPA
in the following figure
01
SC.3:OPERATION
3AL 61348 AA AA
258
47 / 258
Figures which follow show the action creation report and the NPA highlight on the map.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
48 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Actions available after NPA create are Modify NPA, Modify Ring Map, Implement and Unlock physical connections
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
49 / 258
NPA highlight
NPA highlight shows on the map the nodes connected by physical connections involved in the NPA.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
50 / 258
a)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
51 / 258
b)
c)
ED
Select option NPA
01
SC.3:OPERATION
3AL 61348 AA AA
258
52 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
53 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
54 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
55 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
56 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
SNCP Rings, 2f MSSPRings, 4f MSSPRings can be modified adding or removing physical links
Linear MSPs can only be modified adding and removing members of the linear 1:n protection.
The command is performed using a tool similar to the creation/modification wizard
ASON NPA can be modified adding and removing internal or interworking physical links
The command is performed using a tool similar to the creation/modification wizard
ASON NPA can not be modified by splitting / Joining existing internal physical links. This is due to limitation
on the interface between RM and GMRE.
As a specific tool for MSSPRings, the user can also visualize and modify the NE sequence numbers in
the NPA ring to allow a hitless takeover.
The form display the current sequence of the NE protection blocks and allows the definition of a new consistent one.
NOTE: Only a defined NPA can be modified.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
57 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
58 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
This limitation can be removed in future RM versions allowing a simple migration of protections. In the current release, it simplify the implementation since no path related information (e.g. squelching tables) are
sent to the NEs during NPA implementation
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
59 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
60 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
NPA: Specify ring map allows to change/display the Node position in NPA ring and the Node Id in NPA.
The user can change these attributes, according to the NPA ring.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
61 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
62 / 258
SCOPE
The scope of this procedure is to create a 4Fibre NPE ring with 1664SM equipment.
SEQUENCE
a)
The ring (Elementary Topology) objects are created in a Subnetwork submap using the command
Construction:Create:
b)
TX
RX
SLOT 17
AGGR. WEST 1
WORKING
SLOT 19
AGGR. WEST 2
PROTECTION
SLOT 18
AGGR. EAST 1
WORKING
SLOT 20
AGGR. EAST 2
PROTECTION
The 1644SM network element, when inserted in a NPE ring is equipped with 4 STM16
aggregate boards, as shown in Figure 52. This figure is part of the 1353NM equipment view.
N.B.
West 1 and East 1 aggregate ports support the working capacity, West 2 and East 2 aggregate
ports support the protection capacity.
c)
d)
Implement NPA
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
63 / 258
SEQUENCE
a)
Create the NPA 4f for the topology which represents the existing ring
b)
At the NE/EML layer read the information of Node Id and Node Position per each node of the ring
and move these information to 1354RM map.
c)
Issue NPA: Specify Ring map setting Node Position and Node Id.
d)
e)
f)
g)
Enable download
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
64 / 258
CONDITIONS
SCOPE
The scope is to create and implement a STM64 4Fibre NPE ring with 1670SM equipment.
SEQUENCE
a)
b)
Create all the connections main (clockwise). The following assignment is suggested:
1)
Create the connection main A to B, selecting board 24 on node A and board 32 on node B
2)
Create the connection main B to C, selecting board 24 on node B and board 32 on node C
3)
Create the connection main C to D, selecting board 24 on node C and board 32 on node D
4)
Create the connection main D to A, selecting board 24 on node D and board 32 on node A
d)
Create all the connections spare (clockwise). The following assignment is suggested:
1)
Create the connection spare A to B, selecting board 28 on node A and board 36 on node B
2)
Create the connection spare B to C, selecting board 28 on node B and board 36 on node C
3)
Create the connection spare C to D, selecting board 28 on node C and board 36 on node D
4)
Create the connection spare D to A, selecting board 28 on node D and board 36 on node A
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
65 / 258
The first port, which has been selected while creating the A to B connection ( board 28 on node A
) is now distinguished by the attribute SDHPORTROLE=EAST MAIN. The second port, which has
been selected while creating the A to B spare connection ( board 36 on node B ) has now the attribute
SDHPORTROLE=EAST MAIN. The remaining ports of the NPE ring are marked accordingly.
WEST SPARE
EAST SPARE
slot b28
slot b36
WEST MAIN
EAST MAIN
slot b24
slot b32
Assignments are visible only at 1353NM interface ( 4Fibre NPE ring main dialog box ). See below
figure
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
66 / 258
The first port, which has been selected while creating the A to B main connection ( board 24 on node
A ) is now distinguished by the attribute SDHPORTROLE=WEST MAIN. The second port, which has
been selected while creating the A to B main connection ( board 32 on node B ) has now the attribute
SDHPORTROLE=EAST MAIN. The remaining ports of the NPE ring are marked accordingly.
SEQUENCE
a)
Create the NPA 4f for the topology which represents the existing ring
b)
At the NE/EML layer read the information of Node Id and Node Position per each node of the ring
and move these information to 1354RM map.
c)
Issue NPA: Specify Ring map setting Node Position and Node Id.
d)
e)
f)
g)
Enable download
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
67 / 258
This paragraph summarizes the main guidelines for the correct set up of linear MSP schemes, 1+1 and
1:1, in SDH Q3 NEs in NR5.0x, NR5.1A and 5.1B, i.e. in all the NRs where, according to the current planning of 1354RM, the creation of the linear MSP scheme is provided only via 1353SH. The paragraph describes also the undesired behaviours (in any case, without loss of traffic) that may occur if those guidelines are not followed.
The procedures described in this document apply especially for the Q3 NEs where it is possible to explicitly
setup/dismiss linear MSP schemes, namely ADMs
2.11.1 Linear 1+1 MSP
Step 1: SH operator shall set up the protection scheme before RM establishes any physical connection
between the ports of the main and of spare sections. This operation shall be performed before RM takes
into charge the involved resources, or after a temporary deassignment by RM of the involved resources,
or within a privileged operator session.
Step 2: RM operator shall create the physical connection between the ports of the main section only. It has
to be noted that in this situation RM application prevents the creation of a physical connection between
the ports of the spare section.
What happens if this procedure is not followed: if RM operator sets up a physical connection
between the ports of the spare section before establishing the MSP scheme, there are two possibilities, both critical
a) If also paths are defined over the spare section before the MSP scheme is set up via SH, the establishment of the MSP scheme will fail.
b) If no paths are defined on the spare section, the establishment of the MSP scheme will succeed but
there will be an inconsistency between RM representation and the actual configuration. Moreover, if RM
operator tries setting up a path over the spare section after the MSP scheme is established, the path implementation will succeed but the new path will be immediately alarmed. As a further side effect, there will
be an inconsistent representation of connectivity in SH (the path connections over the spare section are
shown in the crossconnection view but not on the corresponding port view, which will only display the
main section). The final result is that it will be difficult for an operator to understand that the path over the
spare section is alarmed because of a wrong configuration sequence.
2.11.2 Linear 1:1 MSP
Step 1: RM operator shall create in advance the physical connections both between the ports of the main
section and between the ports of the spare section. This operation is necessary to allow the set up of extra
traffic paths on the spare section.
Step 2: NM operator (administrator) shall set up the protection scheme. This operation shall be performed
within a privileged operator session because the physical connections shall be left assigned to RM.
Once the protection scheme is established as described above, RM can set up paths, i.e. traffic, on both
the main (protected) and spare (extratraffic) sections. It has to be noted that RM does not characterize
as low priority traffic the spare section.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
68 / 258
What happens if this procedure is not followed: if steps 1 and 2 of the sequence are reversed, after the
MSP is established the RM application will prevent to set up a physical connection between the ports of
the spare section. As a result, it will not be possible to set up extra traffic.
2.11.3 Alarm Behaviour
2.11.3.1 Linear 1+1 MSP
By convention, RM represents the protected multiplex section as a single section between the main ports.
The spare resources are not shown. A MSP switch does not affect the supported paths provided there are
no failures in the protecting multiplex section.
The supported paths will be affected in case both the protected and protecting multiplex sections are failed
and there are no further protection schemes on a different layer (e.g. SNCP). It has to be noted that for
this situation RM affects the paths relying on SSF that should be generated autonomously by the NEs on
the impacted path layer TPs.
2.11.3.2 Linear 1:1 MSP
On RM, the main and the spare sections are handled as if they were independent. In case of MSP switch,
the low priority traffic will be lost and the related paths will then be alarmed. It is up to the human operator
to correlate this situation with a MSP switch.
KNOWN ISSUES
Failure on consistency audit
It has to be noted that, even if the above procedures are followed, in case RM performs a consistency audit
after the linear MSP scheme has been established, the spare ports will be marked as failed (anyway,
without impacts on the traffic).
Degraded protection indication on RM
RM can not perform any realtime correlation between failures in the main/spare sections and the position
of the switch inside the NE to deduce the degree of availability of the protection.
When the linear MSP is set up on a QB3* NE, the realtime correlation is performed inside NM MIB to
generate a degraded protection alarm on the port of the main (protected) section in case of a failure in
the spare (protecting) section. This alarm is then emitted by NM and represented at RM.
When the linear MSP is set up on a Q3 NE, neither NM (MIBless for Q3 NEs ) nor the NE perform such
a correlation. As a consequence, the degraded protection alarm is not generated.
Proper provisioning of low priority traffic in 1:1 MSP
RM does not characterize the traffic priority for the physical connections at MS level. It is the responsibility
of the human operator to define properly the highpriority traffic paths over the main (protected) multiplex
section and the lowpriority ones over the spare section.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
69 / 258
2.12.1 JO SETUP
J0 setup can be entered from the Network, Subnetwork or Node, issuing the command Actions: Configuration: Upload Tools.
From the Upload Tools dialog box ( see following Figure 56. ), select option Automatic Generation of Trace
Identifier, which means J0 definition and click on Finish button to confirm. The following string is automatically entered:
R$NDMPORTIDENTI
where NDM=Network Domain Id ( 3 characters) , PORTIDENTI=port identifier (10 characters)
As an alternative, sent and expected J0 can be entered by the operator by using the CT/NM when the
fiber pair in put in service.
2.12.2 Upload Physical Connectivity
SCOPE
The scope of this procedure is to upload the physical media adjacency of the network. This means that
SDH/SONET physical links are automatically created in RM, when a fiber pair is connecting two ports.
The discovery is performed by using the trace identifier J0
SEQUENCE
a)
The upload command is performed on one of the two NEs. Issue Configuration: Upload Tools. Select
option Upload Physical Connectivity
It is possible to issue this command on the whole network or on a subnetwork.
b)
a)
The upload command is performed on one of the two NEs. Issue Configuration: Upload Tools. Select
option Upload of Protection Schema
It is possible to issue this command on the whole network or on a subnetwork.
b)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
70 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
71 / 258
N.B.
Alternatively,the user can move nodes using dedicated scripts and an offline tool, such as
Excel program, without interaction with the User Interface. See details in the 1354RM
Administrators Guide.
SEQUENCE
a)
From the source map point to the node to move and issue Node: Modification: Move Node. The Move
node dialog box opens. See Figure 58. on page 73.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
72 / 258
SCOPE
SELECTION OF
DESTINATION
TOPOLOGY
From the Move dialog box click on button Selection of the Destination topology. The map opens in
selection modality.
c)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
73 / 258
ED
Click twice on the target subnetwork. The 2nd level subnetwork map opens.
01
SC.3:OPERATION
3AL 61348 AA AA
258
74 / 258
Select the Destination topology and confirm by pressing button selection. The Destination topology
icon is present in the Move dialog box. See Figure 63. on page 76
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
75 / 258
f)
Issue the Move command by clicking on Finish button. The moved node is present in the destination
submap in the New Object holding area.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
76 / 258
Drag the moved node from the New Object holding area to the center of the window. The connections
are drawn automatically.
g)
N.B.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
77 / 258
RM allows to manage a Physical Connections between ports of the same NE: this is mainly for WDM NE
management but it can be used in particular SDH application.
The following commands/actions are available:
Note that Physical Connection(s) between ports of the same Node are not displayed on the maps.
Internal Physical Connections can be retrieved through inventories requiring all Physical Connections that
are present in the topology where the Node is included, or that are startingending in the Node.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
78 / 258
SCOPE
The scope of this procedure is to enable/disable the retiming functionality, i.e. to manage a 2Mb/s synchronous timing source going out from a certain NE port, used to synchronize the PDH network, in order to
reduce the pointer justification wander.
This procedure includes also the configuration of the action to perform in case of loss of synchronization.
The consequent actions that can be configured are:
timingPDH (default) . Timing of the outgoing signal is synchronized by the incoming signal
CONDITIONS
The functionality is applied at path level. The functionality can be enabled/disabled on the ports related
to the path. The retiming can be defined only for an already implemented or partially implemented path.
The retiming functionality is applicable only for 2Mbit/s signals and on ports belonging to Q3 NEs
SEQUENCE
a)
ED
Point to the path whose port is to be used as synchronization source and open the popup menu.
Select Configuration: 2Mbit/s Retiming management. See Figure 67. The Path Retiming wizard
step 1 is displayed. See Figure 68.
01
SC.3:OPERATION
3AL 61348 AA AA
258
79 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
80 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
c)
ED
Click on Next button. The Path Retiming wizardstep 2 is displayed. See Figure 69. You can enter
the following:
01
SC.3:OPERATION
3AL 61348 AA AA
258
81 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
82 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The Operator can modify the retiming and the related consequent action on the displayed ports. For unidirectional or broadcast path, only the sink ports supporting the retiming functionality are presented to the
Operator. In addition it is possible to navigate on the 1353NM in order to get further information.
The consequent actions are applicable only for ISDNPRA or Leased Line signals and can be configured
only for bidirectional paths and only if the retiming functionality has been enabled.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
83 / 258
In case of NPE MSSpring the Topology Implementation process performs the following steps:
a)
starting from the sequence number in et node attribute (it provides the position of each node in the
et), it builds the string corresponding to the ring map info attribute of the 4f MS Protection Block MOC
b)
a)
ED
1)
it creates, contained in the node, the MS Protection Block MOC filling the Configuration State
attribute with the virtual value
2)
it submits to the proper TSDIM Front End Processor (in charge of the node) the request to
change on the MS Protection Block (contained in the node and related to the et) the
Configuration State attribute to the active value and the ring map info attribute to the string set
up at step a ). In case the topology is modified adding/removing a node and the et is requested
to be implemented again, the topology implementation process submits the request to change
the ring map info attribute only.
01
SC.3:OPERATION
3AL 61348 AA AA
258
84 / 258
N.B.
In case of NPE MSSPRING the operator can excute the following checks:
1)
From the Subnetwork map point with the mouse at the NPE ring and issue the popup menu
Main Items: All Protection Blocks in MSSPRING 4 F. The relevant graphical window is
displayed, including all protection blocks.
3)
ED
01
From 1354RM 4 FMS Spring window select a node and click on the Show/Set Attributes icon
( lens ). The Ring Map Info Attribute lists the sequence of the connected Node IDs in ET. The
Show/Set Attributes window contains also the values of the attributes Node Position in ET and
Node Id in ET. Notice that:
VALUE at NM interface = VALUE at RM interface + 1
SC.3:OPERATION
3AL 61348 AA AA
258
85 / 258
At the end of the network implementation the network is automatically configured at higher order, i.e. the
MIB contains all the HOLCs with the HOCTPs.
Payload configuration consists of:
modifying the existing payload configuration (e.g. from 63 x 2 Mb/s to 3 x 34 Mb/s payload structure)
Physical connection
Higher order link connection
Higher order trail
N.B.
The payload configuration is not required for NPE Ring, since the 1664SM network element can
implement only connections at VC4 level.
a)
2)
Click on Payload Configuration tool button. The Payload Configuration window is presented.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
86 / 258
b)
FROM BROWSER
1)
Select the object from the Browser window and launch the Configure Payload application by
selecting the appropriate Tool button.
The virtual container fields are shown on the Payload Configuration window. The operator can write
the new configuration into these fields or can choose it using the selection box on the right of the
VC fields (Dictionary). Enter the configuration and click on OK.
If the object to be payloaded is an HO trail or an HOLC, the list of configurable TUG is presented.
Choose the TUG combination and click on OK. For example the TU12, TU12, TU3 combination
means 21 TU12+ 21 TU12+ 1 TU3.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
87 / 258
When the payload configuration is in progress, the operator can supervise the operations performed by
the process. It mainly means:
a)
Verify in the Browser that the working state of the object (e.g. a ring) changes to Configuring.
b)
If the object to configure is a ring, the working state of all the contained physical connections must
be configuring. To do this enter command: Display:Related items:Physical Connections, starting
from a ring.
c)
If the operator wants to supervise the other objects involved in payload configuration, he can issue
a Display:All Related items command on mstrails, Client Link Connections, HOtrails, Low Order Link
Connections, etc.
At the end of the configuration process the working state of the configured objects must return to normal;
otherwise the working state becomes Fail to Configure.
2.17.3 Payload Configuration supervision
When the payload configuration is successfully completed, the user can supervise it in the following ways:
a)
From the map select the Physical Connection and use the popup menu Payload Configuration. The
relevant drawing window is opened; the Payload Configuration is represented graphically.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
88 / 258
b)
From the browser display the ring or the physical connection: both objects have dedicated fields
displaying the actual configuration of the Physical Connection. You can also use the Display: Related
items: Physical Connection Structure option to display the relevant drawing window. In addition, you
can select an HO trail and issue the Actions: Display Related Items to display the views and/or the
lists of the children objects: Paths in trail, Client link connections, ...
c)
From the browser or from the Physical Connection drawing window you can also open the graphical
window on the SDH Port, which displays the payload configuration supported by the port.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
89 / 258
From the map select the physical connection to configure and issue Browse: Object(s). The browser
opens on the selected object. See Figure 75.
b)
Point with the mouse at the physical connection and issue Display: Related Items: physical
connection structure. See Figure 76. The relevant view is displayed. See Figure 77. on page 91.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
90 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
91 / 258
From the view select the MS trail and click on Payload Configuration button. The Payload
Configuration window opens. The actual payload structure is displayed in the bottom section of the
window.
d)
Click on the AU4 which will be the first AU4 of the concatenated stream. A subwindow is displayed
( see Figure 79. ), which allows to select the payload structure. If the operator selects AU44C and
presses OK, the concatenated configuration is set up in the Payload Configuration window.
e)
Click on SETUP button to confirm. The configuration is sent to the Network Elements and a Report
Log is displayed.
a)
ED
Select the relevant Physical Connection and issue Display: Related Items: Physical Connection
Structure. The graphical window is displayed in Figure 80. herebelow.
01
SC.3:OPERATION
3AL 61348 AA AA
258
92 / 258
From the browser select the MS trail to configure and click on Payload Configuration button. The
Payload Configuration window is presented. See Figure 81.
b)
The actual payload structure is displayed in the bottom section of the window.
c)
Click on the first AU4 of the concatenated stream. A subwindow is displayed ( see Figure 81. on
page 93 ), which allows to select the payload structure. If the operator selects AU4 and presses OK,
the concatenated configuration is removed from the Payload Configuration window.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
93 / 258
Click on SETUP button to confirm. The configuration is sent to the Network Elements and a Report
Log is displayed.
Notice that the operation of physical connection remove comprises the removal of the physical
connection, MS trail and link connections. The involved ports are deassigned. No action is made
on the AU4s at NE level, which hold the last setting ( concatenated or not concatenated ).
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
94 / 258
d)
The user creates a network with different subnetworks.The user tries to select simultaneously
two NEs between two subnetworks and it is possible. But, once opened the trail window, only
one element is present, the first one selected. This is due to the structure of ilog maps. Namely,
it is possible to select a couple of nodes only if they belong to the same map view.
2.19.2 Operation
a)
Select the Trail Termination points to be created on the map and then on the menu Actions: Create:
Trail. A sequence of boxes will openup together with a browser window (if not already open).
On the upper part of Step1 box figure, there are helpfull notes about choosing/selecting the parameters
and values.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
95 / 258
not specified
specified
ED
Setup mode: a question button asks the user if he wants to proceed with automatic allocation,
implementation and payload ( Yes / No )
01
SC.3:OPERATION
3AL 61348 AA AA
258
96 / 258
None
SNCP
D&C SNCP
SNCP type
SNCP/N preferred
This feature allows the managing of different type of SNCP protection schemes for a path/
trail. The allowed schemes are:
SNCP/I (Inherent)
SNCP/N (Notintrusive)
The two schemes are related to the switch criteria. In particular:
SNCP/I switch criteria: AIS and LOP
SNCP/N switch criteria: Server Signal Failure, Signal Degraded, Trace Identifier Mismatch, Excessive BER and Unequipped
The user can specify the preferred type of SNCP protection using the Path Creation (for
paths) and Set up Trail (for trails) commands. Anyway, the type of SNCP protection can
be modified, in a second step, even if the path/trail is implemented.
If the user wants to add the protection to an unprotected path/trail, he has to use the Add
Protection command. The preferred type of SNCP protection has to be previously chosen
by the user modifying the related attribute of the path.
Since this feature is not supported by all the NEs, a path/trail may have SNCP/I and SNCP/
N protections.
RM does not provide provisioning of SNCP/N switching criteria (i.e. Excessive BER, Signal
Degraded).
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
97 / 258
ED
Routing subwindow. See below figure, which contains the explanation of:
01
SC.3:OPERATION
3AL 61348 AA AA
258
98 / 258
b)
ED
Click on Next button. On Step 2 box there is the source/sink selection of Node/Ctp.
01
SC.3:OPERATION
3AL 61348 AA AA
258
99 / 258
Note that the CTP selection can be avoided; the system selects the first idle CTP. If the user
wants to select manually the CTP, the possible CTP names can be individuated from the Physical Connection Structure.
Note that the selection of only one ctp is sufficient: in this case the same tp will be chosen on the far end.
c)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
100 / 258
d)
ED
A warning alerts to refresh manually the window, as per Figure 87. . The trail structure is shown in
Figure 88.
01
SC.3:OPERATION
3AL 61348 AA AA
258
101 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
102 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
This command can be issued for the whole network, for a subnetwork only, an Elementary Topology (ring)
or a single Node.
It can be launched from Browser or Netview.
2.20.1 Upload NAPs
SEQUENCE
a)
From the browser window point with the mouse at the topological object whose NAPs are to be
uploaded and open the popup menu. Select menu item Configuration: Upload NAPs. See
Figure 89. A dialog box alerts that the action has been correctly started.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
103 / 258
The operator can monitor in real time the upload in progress by means of the browser, which displays the
working state=uploading of the involved topological object. See Figure 90.
Working state=
uploading
a)
ED
From the browser point the mouse at the topological object to verify and open the popup menu.
Select menu option Display: Main related items...
2)
From the selection dialog box of Figure 92. on page 105 click on option NAPs and click on No
Filter. The NAP list is displayed. See Figure 93. on page 106
01
SC.3:OPERATION
3AL 61348 AA AA
258
104 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
105 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
106 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
SCOPE
This feature allows to upload the retiming configuration from an existing network.
CONDITIONS
This feature is useful when the retiming has already been configured in the network (e.g. from SH) and
RM has to take in charge this configuration
SEQUENCE
a)
the Synchronize NE command has to be executed on all the NEs that can support 2Mbs ports. As
a consequence, the retimingSupported attribute of the port is aligned
b)
c)
a dedicated script has to be executed. This script contains the following steps:
the Consistency Audit (notify modality) has to be performed on all the ports involved in a path and with
the retimingSupported attribute different from notSupported. (through a dedicated script). As a consequence, the consistency status of all the ports with the retiming enabled in the NE is set to consistencyMismatch.
the retimingStatus attribute of the paths involving ports with the consistencyStatus attribute equal to consistencyMismatch is aligned (set to enabled. As a consequence, the retiming attribute of the involved ports
is aligned (set to enabled)
N.B. As the NE is in Download disabled mode, the consistencyStatus attribute of the involved ports is equal
to notAligned. Performing a new Consistency Audit (notify modality), the consistencyStatus attribute will
be set to normal. At the end, the NE has to be put in Download enabled mode. the batch file has to be
executedPM on regenerator section monitoring function (WDM/PM/B1)This feature deals with the Performance monitoring of client path (B1 monitoring).
2.21.1 Measurement types
The supported types of PM measurements are:
PM 15 minutes for Maintenance (unidirectional)
PM 24 hours for Maintenance (unidirectional)
2.21.1.1 Creation of PM TPs
When a raw connection is transformed in a client path, RM automatically creates, for each end point of
the created client path, the following PM TPs:
24 hour / 15 minutes ingressing unidirectional for the boundary CTP
24 hoursminutes ingressing unidirectional for the adjacentBoundary CTP
PM TPs are created taking into account NE restriction. For example, in case of 1696MS, only the PM TP
for the adjacentBoundary CTP can be created.
N.B. The automatic creation of PM TPs can be disabled thought an environment variable set at installationtimeManual Management of OADM Connectivity
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
107 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
108 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
3 TRANSPORT MANAGEMENT
Path Constraints
Add Leg
OS driven restoration
Join/Split path
Join/Split trail
N.B.
After a 1354RM merge operation the Join/Split procedures will be used in the following order:
1join path 2join trail 3join physical connection
ISDN management
path allocate. make reservation of the route within the network. The route includes all relevant
elementary connections ( connections in topology ). Path deallocate is the reverse operation
The allocation algorithm chooses the less costly route by appliyng the Dijkstra algorithm
path implement. transmit to the network the commands to activate all included connections in
topology, thus implementing ( i.e. activating ) the whole path. Path deimplement is the reverse
operation
path Commission, Decommission is only a lock which can be set / removed to / from an implemented
path
path constraints. Used by the allocation algorithm, which is forced to follow users preferencies in
selecting the path route
You can then display the path route using the SDH netview or browser application.
Examples of path create commands (pulldown and popup, respectively), are shown in Figure 94. and
Figure 95.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
109 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
110 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
111 / 258
path allocate. make reservation of the route within the network. The route includes all relevant elementary connections ( connections in topology )
path implement. transmit to the network the commands to activate all included connections in topology, thus implementing ( i.e. activating ) the whole path
path constraints. Used by the allocation algorithm, which is forced to follow users preferencies in
selecting the path route
Launch the path create application. The path create wizard is displayed. See Figure 96.
N.B.
ED
The user creates a network with different subnetworks. On these subnetworks, the user creates
some Ets with many adms. The user tries to select simultaneously two adms between two Ets
and it is possible. But, once opened the path window, only one element is present, the first one
selected. This is due to the structure of ilog maps. Namely, it is possible to select a couple of
nodes only if they belong to the same map view.
01
SC.3:OPERATION
3AL 61348 AA AA
258
112 / 258
INTRODUCTION
1)
ED
01
If you select PDH, selectable service rates are those shown in Figure 97.
SC.3:OPERATION
3AL 61348 AA AA
258
113 / 258
If you select ATM, selectable service rates are the same as for PDH service type
3)
If you select Service type=Ethernet, selectable service rates are summarized in the below
table.
SERVICE TYPE
SERVICE RATE
TRANSPORT RATE
ETHERNET
AU4nV
(concLevel=8)
AU4nV
(concLevel=17)
4)
If you select Service type=DATA, selectable service rates are shown in figure which follows:
ED
01
a)
SC.3:OPERATION
3AL 61348 AA AA
258
114 / 258
Service type=Ethernet
path name
b)
SNCP type
it describes different types of SNCP protection schemes for a path/trail. Allowed schemes are:
SNCP/I (Inherent)
SNCP/N (Notintrusive)
The two schemes are related to the switch criteria. In particular:
SNCP/I switch criteria: AIS and LOP
SNCP/N switch criteria: Server Signal Failure, Signal Degraded, Trace Identifier Mismatch,
ExcessiveBER and Unequipped
The user can specify the preferred type of SNCP protection using the Path Creation (for paths) and Set
up Trail (for trails) commands. Anyway, the type of SNCP protection can be modified, in a second step,
even if the path/trail is implemented.
If the user wants to add the protection to an unprotected path/trail, he has to use the Add Protection
command. The preferred type of SNCP protection has to be previously chosen by the user modifying the
related attribute of the path.
Since this feature is not supported by all the NEs, a path/trail may have SNCP/I and SNCP/N protections.
RM does not provide provisioning of SNCP/N switching criteria (i.e. Excessive BER, Signal Degraded).
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
115 / 258
NOTE: For a path/trail, the management of this feature foresees the introduction of the following new
attributes:
sncpType: it specifies the type of the protection of the path/trail. The allowed values are:
sncpIpreferredNoAlr: the SNCP/I type has to be preferred for all the protected connections of the
path/trail
sncpIpreferredAlr: the SNCP/I type has to be preferred for all the protected connections of the
path/trail.The alarms have to be enabled on the unreliable CTPs involved in the protection
(default
value)
sncpNpref: the SNCP/N type has to be preferred for all the protected connections of the path/trail
The D&C must use only the resources of the NPA and protects only one direction.
D&C related to adjacent NPAs are merged together producing dual node crossconnections in the involved NEs
Unneeded changes of rings is one of the possible source of wrong D&C protections
The NPA can be used as a type of constraint for paths & trails. The constraint types are:
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
116 / 258
Use main. The main route of the path must use at least one of the physical links belonging to the NPA.
At Lower Order the LC satisfying this constraint must be completely contained in the NPA (i.e. its server
trail must use only physical connections internal to the NPA)
Use spare. (as before changing main with spare)
Dont use main
Dont use spare
The add protection and D&C can now be performed without any limitation related to the partitioning (i.e.
to the involved topologies):
any Node of the main can be selected as a starting or ending point of an added spare protection.
No constraint exists anymore on the way to perform the network construction in order to allow path/trail
protections
The add/remove protection and add/remove D&C is performed from a wizard that allows to select the right
TPs or Nodes for the specified operation (protection in a NPA to be confirmed)
MS Protection Usage Profile. For details see explanation at section Technical Annexes.
c)
ED
Click on Next button. The wizard presents now the Step 2 dialog box.
01
SC.3:OPERATION
3AL 61348 AA AA
258
117 / 258
B
NODE
A
NODE
A TTP LIST
MAP
B TTP LIST
LIST
B
NODE
A
NODE SELECTION
LIST
MAP
By clicking on the node selection button, you will get the list of the nodes, suitable to create the
connection. From the node list, select the node and click on Apply button. The icon of the selected
node is now displayed in the source node drop area. This step can be skipped if the node has been
already selected on Netview or on Browser.
e)
Select the terminating node and of the terminating NAP. It is analogous to the point above described
for source node/source NAP selection.
f)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
118 / 258
g)
Select the NAP and click on Apply button. The NAP icon is displayed in the NAP drop area. See below
figure.
ANODE
BNODE
ANAP
BNAP
ANAP LIST
BNAP LIST
Figure 104. Example of NAP selection
N.B.
h)
ED
if it is a virtual node, a PDH port and corresponding NAP are created associated to
the node, with the required rate and with name derived from the path name
Click on Next, passing to Step 3Attributes selection. See figure which follows. Select:
01
SC.3:OPERATION
3AL 61348 AA AA
258
119 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
120 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
CONFIGURATION
Allocation Rule: it specifies if the path has to be allocated automatically after its definition
or subsequently upon users command.
Implementation Rule: it specifies if the path has to be implemented automatically after having been allocated or following an users request.
Algorithm ( Automatic )
ALARM
Propagation rule ( when defined / when allocate / when implemented /when commissioned )
ROUTING
Routing parameters for paths and trails
Main & Spare Cost gravity Factor
It indicates how strongly Main & Spare have to be forced to go in the same NPA
If equal 0 it has no effect.
As bigger is set as more the cost of NPA internal routes used by the Main is decreased attracting the spare.
Disjoint ness is in any case considered.
D&C Cost Factor
It has effect only in 2f MSSPRings and it is an indicator on how much the D&C has to be preferred
compared to another route without D&C. A value of 3 means that D&C is preferred only if has at most three
times the cost of the optimised root.
It works increasing the cost of the arcs in the direction where the D&C cannot be performed (opposite
direction of the main). In previous RMs was always forced producing in some conditions not optimised
routes
N.B.
If the user, when creating the path, selects Alarm Enabling Rule: Manual, for this Path it will be
possible to enable / disable the involved alarms ( from the Path List: menu Actions: SDH/PDH
Alarms enable/disable.
USER
Path Group , to be used when defining multiple paths belonging to the same path group
Automatic Monitoring ( True/ False ). If true starts the 24 h PM activity on path implementation
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
121 / 258
i)
Click on Finish button. The path is created and the routing view is displayed.
CP RESTORATION. It contains:
Fast Ethernet boards have been already correctly setup on the Equipment via 1353NM.
upload the Data ports. The uploaded ports are created in the RM MIB. The technology of the ports
is Data
b)
upload the Data NAPs. As a consequence of this operation the generic Data NAPs are created in
the RM MIB (no interaction with the NE)
c)
create a path connecting two Data NAPs. The user enters the following information:
the two Data NAPs
the type of the server SDH container (tu12, tu3 or au4) or ( tu12nV tu3nV ). If the user selects
the virtual concatenation ( tu12nV tu3nV ), he will enter the number n ( no. of TUs ).
In the fact the path creation includes the specification of the VCs. As a consequence, data NAPs are
created in the NEs accordingly.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
122 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
123 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
124 / 258
If Append is selected, the path sequential numbering is added as a suffix to the name of the path.
If you want to insert the sequential numbering in the inner of the path name, the userlabel containing the
%nd characters should be written where n corresponds to the numbering field size. In this case you have
to select Replace.
The Associate feature is provided (same route) if the following are selected:
number of paths
>1
starting
any
This feature allows to associate as constraint the first created path. The user can carefully setup the
first created path. The remaining ones will have the same route.
NOTE: Only nodes must be specified in this procedure.
3.2.4 Constraints
SDH routing is performed on a cost basis. This means that a route having the least cost will be used when
setting up a path.
The user can specify some constraints to be used by the allocation algorithm either during the path allocation or the path add protection activities. These constraints are used to:
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
125 / 258
Path constraints allows the user to specify the constraints to be used by the allocation algorithm during either the allocation or the protection activity or the addition of a leg in a broadcast path (i.e. Allocate path and Protect path services broadcast path end point add). The user specified constraints
overrides the cost based allocation policy.
The constraints are defined by the following characteristics:
Involved resources : they can be subnetworks, ETs, nodes, link connections, physical connections, CTPs, server trails and routing links.
Constraint type : it specifies whether the path must use the specified resources or not
Route Type : it specifies if the constraint is applied for the main route only, for the spare route
only or for both routes.
UPON CREATING A PATH AND SPECIFYING THE NOT ALARMED RESOURCES ONLY OPTION, RM ONLY TAKES INTO ACCOUNT THE ROUTING RESOURCES AND NOT THE NAP
ONES.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
126 / 258
specify if the constraint has to be applied to the path main route or to the spare one or both;
SERVICE RATE
TRANSPORT RATE
ETHERNET
AU4nV
(concLevel=8)
AU4nV
(concLevel=17)
LC
AU48V
CTP
CAP1
CAP8
CTP
hotrail1
hotrail8
AU41
AU48
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
127 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
128 / 258
The path routing display is shown in the following figure. Notice that the link connection configuration
state is implemented. Click on Server trail icon. The trail list of the 8 virtually concatenated trails is
displayed. See Figure 117.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
129 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
130 / 258
If only some trails are allocated, the attribute Server connectivity of the path is equal to partially connected. In this case the operator may add resources and subsequently allocate trails whose working
state is fail to allocate.
d)
Launch path implementation. The system executes the implementation of the 8 trails.
It is possible to launch path implementation also on a path having some trails allocated and some
defined. In this case the path goes implemented, its defined trails remain defined, the allocated trails
go implemented or partially implemented.
3.3.1.3 EXAMPLES
EXAMPLE 1
A path has 7 trails allocated and 1 trail fail to allocate. By launching the implementation on the trail failed
to allocate, the server connectivity of the path goes fully connected.
EXAMPLE 2
A path has 1 trail allocated and 7 trails defined. By launching the deallocation on the allocated trail , the
path goes defined and all involved trails are deleted.
EXAMPLE 3
A path is allocated. By launching the implementation on one trail , the path goes partially implemented
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
131 / 258
The 1 Gbit/s Ethernet Rate Adaptive path can have rate AU4nV with n=17.
An example is shown in figures which follow.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
132 / 258
TRAIL LIST
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
133 / 258
The User, directly to a Server HO Trail, can perform the Allocation, Deallocation, Implementation, Deimplementation, Add protection, and Remove protection operations.
The operations allowed on the server HO Trail depend only on their configuration state, regardless the
GbE concatenated path configuration state. The path working state is checked in order to avoid concurrent
operations.
The configuration state and server connectivity of AU41v link connection and concatenated path are always reevaluated. After an add/remove protection applied to a server trail, also the path protection type
is reevaluated.
3.3.2.2 GbE Path Route, Server HO Trails and GbE Path Attributes display
The Operator can visualize the routing of a GbE Path and from the route display of GbE paths, starting
from the AU41v LC, it is possible to retrieve all the server HO Trail.
In addition for the HO Trail participating in the virtual concatenation group (also if only in this particular
case), it is possible to retrieve the client GigE Path or the AU41v LC.
3.3.2.3 Redolog
The system will trace in the redolog all the operations performed by the User on a concatenated path and
on the server HO trail.
3.3.2.4 GbE Path and Server HO Trail Alarms
Elementary Alarms related to the GbE Ports, NAPs, CAPs, CTPs are correlated to the Server HO Trail
and GbE Path, which affect the GbE functionality.
Alarms related to the HO Trail are managed as usual, while alarms related to a GbE Paths are issued when
the GbE service is affected.
3.3.2.5 GbE Path Highlight
The system, as for all the other type of paths, allows to highlight on the Map where a GbE Path is passing
through.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
134 / 258
LCAS (Link Capacity Adjustment Scheme), is a protocol that improves Virtual Concatenation.
This protocol applies to the following boards:
boards belonging to the Integrated Service Adapter (ISA) board family, named ES1 and ES4. The
ES1 board has a throughput, towards the SDH network, of 155Mb/s while the throughput of the ES4
one is 622Mb/s.
The management of these boards makes use of LCAS (Link Capacity Adjustment Scheme), which is a
protocol that improves Virtual Concatenation, allowing to:
hitless increase/decrease the capacity of a Virtual Concatenation Group ( VCG ) link
temporarily remove a member link that was affected by a failure (this member is hitless added again after
failure recovery)
This paragraph describes the following procedures:
Path creation
serviceType=Ethernet
serviceRate of the path eth1GbRateAdapt / eth10or100MbRateAdapt
type of the server SDH container to be used to transport the traffic (transportRate). The allowed values
are:
all the other information required for the path creation (user label, ...)
The list of the NAP is available to the user, satisfying the following conditions:
napRate attribute matching the service rate of the path
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
135 / 258
If the user selects the NAPs, the compatibility of the two selected NAPs is verified accordingly.
N.B. The user can select the node instead of one or two NAPs. The compatibility of the two NAPs is automatically verified.
At this point, the lcasControl and the diversesrvTrailsRoutingPreferred attributes of the path are set
according to the following table:
Aend type
Zend type
LCAS control
virtual node
virtual node
enabled
diverseRoutingPreferred
virtual node
real node
enabled
diverseRoutingPreferred
virtual node
nap
not available
conc type DIFFERENT FROM virtualLCAS
uniformRoutingPref
virtual node
nap
not available
conc type = virtualLCAS
diverseRoutingPreferred
real node
real node
NOTE 1
real node
nap
not available
conc type DIFFERENT FROM virtualLCAS
uniformRoutingPref
real node
nap
NOTE 1
conc type = virtualLCAS
NOTE 1
nap
conc type DIFFERENT FROM virtualLCAS
nap
not available
conc type DIFFERENT FROM virtualLCAS
uniformRoutingPref
nap
nap
not available
conc type DIFFER- conc type = virtualENT FROM virtual- LCAS
LCAS
uniformRoutingPref
napconc type
virtualLCAS
diverseRoutingPreferred
ED
01
NOTE 1
= nap
enabled
conc type = virtualLCAS
SC.3:OPERATION
3AL 61348 AA AA
258
136 / 258
NOTE 1. The values of the two attributes are calculated by the TRS (Transport Management process)
taking into account the type of the two NAPs chosen by the TRS itself.
NOTE 2. The Y value in the column means that the values specified in the two previous columns are presented to the user and he can modify them in the path creation phase; the N value means that the values
specified in the two previous columns are not presented to the user and are automatically set by the TRS.
b)
N.B. The user can modify the srvTrailsRouting attribute of an already created path in any allowed configuration state (confSt equal to defined, allocated, implemented, ...). In this case the new provided value will
be taken into account for the allocation of new trails (the already allocated trails are not rerouted).
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
137 / 258
The lcasControl attribute allows the interworking between an NE not providing the LCAS protocol and
another providing it. This means that a path can be allocated between an end point supporting the LCASprotocol and another no: the LCAS protocol has to be disabled on the end point supporting it.
To have the LCAS functionality, the LCAS protocol has to be enabled on both the end points.
The user, on the User Interface, has to select the path and to choose the LCAS control command.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
138 / 258
N.B. LCAS protocol can be enabled/disabled also in the path creation phase. See following figure.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
139 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
140 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
The following tables list the compatibility between the NAPs rate, the Ethernet mapping, the Transport rate
and the Service rate of the path.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
141 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
142 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
143 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
144 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
145 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
146 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
147 / 258
The ports supported by the 16xGbE board in the 1678MCC R3.1A or later are compatible with all the portsproviding a 1GbEth Rate Adapter service. The particularity of these ports is that they can work only with
a fixed rate (vc47V).
To create a path involving one or both these ports, the usual information to create a normal eth1GbRateAdapt path have to be provided by the user. Concerning the concatenation level value, RM does not check
that it has to be equal to 7. This means that if the user specifies a different concatenation level value RM
does not return any error: the error will be returned only by the NE.
It has to be noted that the server trails related to the path (or only a part of them or none) can cross the
ASON domain.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
148 / 258
SCOPE
The scope of this procedure is to modify the banwidth of a rate adaptive path.
SEQUENCE
a)
From the path list point to the rate adaptive path and select Path: Modification: Bandwidth. The wizard
dialog box opens.
b)
ED
1)
2)
Increase bandwidth
01
SC.3:OPERATION
3AL 61348 AA AA
258
149 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
150 / 258
From the path routing display, clicking twice on the DISPLAY SERVER TRAILS icon, you can display the
trail list of the involved path.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
151 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
152 / 258
ADDED TRAIL
Figure 129. Server trail list
The created trails are added as the last items of the trail list
Decrease bandwidth
Activate trails
Trails are activated sequentially starting from the first idle trail.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
153 / 258
Deactivate trails
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
154 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
155 / 258
This procedure allows to define the Protocol format to be used for an Ethernet path.
CONDITIONS
Path status is defined or allocated
SEQUENCE
a)
Point to the Ethernet path and select Configuration: Ethernet mapping. The relevant wizard is displayed.
linear extension header with FCS (used in case of grooming Ethernet interfaces into a single vcn)
linear extension header without FCS (used in case of grooming Ethernet interfaces into a single
vcn)
c)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
156 / 258
SCOPE
This paragraph describes the commands used to modify path configuration state and to display the path.
3.6.1 Path Allocate
The Path state is defined after having been created. The operator can allocate the path, i.e. the network
resources can be assigned to it.
a)
Open the Path list: from the Browser point to the Network icon and issue the Display: Related items
pop up command. From the list of the available items select Paths in Topology and click on button
No Filter.
From the list select the path to allocate and select the Actions: Configuration: Configuration State
Modification: Allocate pulldown menu. This command is also available as popup menu.
A warning box alerts: Action correctly started... .
The Path working state changes from allocating to normal at the end of the allocation.
The Path configuration state changes from defined to allocated at the end of the allocation.
N.B.
The Path Allocation can be executed only if the network is properly configured.
N.B.
The allocation of a certain path can be prioritized with respect to the allocation already
requested for other paths if you enter Configuration: Configuration State Modification: Allocate
with Priority
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
157 / 258
a)
From the Path List select the path and the Actions: Configuration: Configuration State Modification:
Implement pulldown menu item. This command is also available as popup menu.
The Path Implement activity consists in sending commands to the NEs in order to set up the NE internal
connections.
The Path working state changes from implementing to normal at the end of the implementation.
The Path configuration state changes from allocated to implemented at the end of the implementation.
3.6.3 Path Commissioning
a)
From the Path List select the path and the Actions: Configuration: Configuration State
Modification:Commission pulldown menu item.
When the path is in this state no other operations are possible except for path decommissioning and
performance monitoring and TCAs enabling/disabling. (Threshold crossing).
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
158 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
159 / 258
From the Path Routing view you can display the route report of the path by entering the command View:
Report: Route full. An example of report is shown in Figure 134.
The Path Routing view wholly represents the connectivity objects belonging to a defined path.
The view is subdivided into vertical columns (named Main, Spare, Service), each of which represents a
whole route.
Some cases can be distinguished:
Main
Spare (more than one spare route can be present)
different service routes
The number of service and spare connections depends on how the path has been constructed.
Moreover if the path is broadcast, the different legs are separately represented.
The main and spare routes are represented for each leg if the path is of the broadcast and protected type.
3.6.4.3 Main Route
The Main route graphical representation comprises (in the area relevant to the first column):
on the upper lefthand side the connection in topology icon at network level
From the first row on are listed the connections in topology at subnetwork level and eventually the
first connection in topology at level of Elementary Topology (ET).
Note that for each connection in topology, a continuous vertical line permits to identify the end points.
If one connection in topology is inside one route only, the vertical line directly connects the TPs (TTPs
or CTPs) involved.
On the righthand side of the different connections in topology the first end point (NAP) is depicted, hence
in the column are displayed the CTPs and the link connections connecting the CTPs belonging to different
nodes.
The link connection icon contains the label describing the relevant payload position.
The representation of the Switch connections in topology ( either Switch or Bridge & Switch ) contains
an icon (Resource Type) indicating the actual switch status. It can be:
M
S
Main
Spare
The connection in topology of the Switch, B&S, or Service type may also contain the Operation Mode
information (bidirectional arrow) which can be Revertive or not Revertive.
N.B.
ED
The Path Routing View permits to display the actual route of the path. For this purpose the
switch Resource Type indications should be analyzed. In the following Figure 135. are given
two examples:
01
SC.3:OPERATION
3AL 61348 AA AA
258
160 / 258
This view displays the complete path route including the main resources dedicated to the selected path.
MAIN
M
MAIN
SPARE
SPARE
Figure 135. Actual route
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
161 / 258
N.B.
For a path crossing a NPE Ring the path routing view displays the Main route: the link
connection label contain a R or a U to identfy if the path is a High Priority (HP=Reliable)
or a Low Priority (LP=Unreliable). HP paths make use of the Working capacity; LP paths make
use of the Protection capacity.
For a path crossing a NPE Ring, the user can verify the connections on the traffic map.
a)
From the path list select the path to display and click on Highlight/Locate button.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
162 / 258
Clicking on Nap view button inside the icon bar it is possible to open the view to display all paths
terminations.
1)
If the transport is not protected the following are displayed: ( see icons in the figure below)
mainnap
mainnapservice
mainsparenap
mainspareservicenap
Parent Flag
Object Flag
LOCATE
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
163 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
164 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
MAIN
SPARE
ED
Sometimes happens that asking for Path Status in Physical Connection the status of the path
is indeterminate even if the traffic is stable in the physical connection.
01
SC.3:OPERATION
3AL 61348 AA AA
258
165 / 258
an operation is already in progress on the PATH/TRAIL. TRS agent inhibited the operation
NE_G/NE is unreachable
NE fault
The first case is a tipical situation when different users execute at the same time the same operation. The
same situation is also reached if the same user asks many times the same operation.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
166 / 258
A path is indeterminated when it is not possible to synchronize switches on the NEs. The reason of the
failure of the synchronization could be:
DEFINITION
This feature allows to declare the Service State ( INSERVICE or NOT_IN_SERVICE) for a transport entity.
The transport entities involved are:
client/path
Alarms on INSERVICE or on NOT INSERVICE entities are automatically acknowledged by AS. Separate counters are provided, namely:
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
167 / 258
a)
Point to the physical connection to modify and issue the popup menu item Configuration: Service
State Modification
b)
c)
ED
It is possible to supervise the successful Service State Modification on the AS Counter Summary.
01
SC.3:OPERATION
3AL 61348 AA AA
258
168 / 258
SEQUENCE
SCCPE
This procedure allows to setup constraints on a path or trail, i.e. to get/exclude the use of certain
resources for a path or trail.
CONDITIONS
The use of the constraint/s allows the operator to execute:
fully manual allocation. The path route can be fully specified, including the payload position. Namely the
user can specify the lower order link connection as constraint.
partially automatic allocation. The user specifies only a part of the route. The allocation algorithm
completes the research of the route resources.
WARNING
The constraint is accepted as mandatory condition by the allocation algorithm, so the path/trail allocation
will fail if a constraint cannot be satisfied. If a path/trail allocation fails, the user is fully informed by the Path
Fail to Allocate tool. See Section Maintenance of this Handbook.
OPERATION
The Path Constraints can be always issued but they will be taken into account during the path allocation
phase: so if the path is implemented, the operator must deimplement and deallocate it and subsequently
issue a new allocation.
Trail Constraints can be always issued but they will be taken into account during the trail setup phase:
so if the trail is set, the operator must deimplement and deallocate it and subsequently issue a new
allocation.
SEQUENCE
a)
In order to create a new constraint, select the path from Path List and click on the Path Constraints
tool button.
b)
The Path Constraints dialog box is opened. See Figure 144. on page 170 Two possibilities are
available:
1)
From Browser select the object to utilize as a constraint. The objects available are:
2)
From the map (Netview) create the constraint by selecting the object to utilize as a constraint
and the Path: Constraint pulldown menu .
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
169 / 258
ED
Use Main
Use Spare
Not use Main
Not use Spare
Use Main and Spare
Not use
Use Service (for a D&C protected path)
Not use Service (for a D&C protected path)
Overlapped if the object utilized as a constraint is a path
Disjointed if the object utilized as a constraint is a path
01
SC.3:OPERATION
3AL 61348 AA AA
258
170 / 258
Use Main as A. This constraint can be applied only to a CTP, used as constraint to a unidirectional
or broadcast path. See Figure 145.
NAP
source
A
CTP
CTP
CTP
CTP
CTP
Use Main as Z. This constraint can be applied only to a CTP, used as constraint to a unidirectional
or broadcast path. See Figure 145.
Use Main and Spare as A, if the main and spare route are using the same CTP as A termination.
If the user selects Use Service Backwards, the object dropped as constraint will be used as service
route/termination to protect the backward transmission direction (from Z to A or from the right to the
left or the RX). See Figure 146. herebelow.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
171 / 258
FORWARD
BACKWARD
AS CONSTRAINT:
AS CONSTRAINT:
Figure 146. Use Service Forward/Backward for Dual Node SNCP network
Example of Path Constraint create
Select the defined path from Naps view or from browser and click on Add Constraint button. The
Add Constraints window is displayed, already containing the defined path which will follow the
constraint
b)
Select the constraint to add, e.g. from the trail list select the trail and drag it with the middle mouse
button to the below region ( the constraint region ) of the Constraints window.
c)
By releasing the mouse button the constraint is placed in the Constraints window.
d)
N.B.
ED
The drag and drop operation must be used to declare the constraint, while the Add
Constraint button starts the Add Constraints application on the selected object.
01
SC.3:OPERATION
3AL 61348 AA AA
258
172 / 258
From the Path List or from browser select the path (monodirectional/broadcast)
b)
Enter the command Add: Leg either by selecting the relevant tool button or by using the menu
Modification: Add Leg . See Figure 147. The Add Leg dialog box opens. The path icon is contained
in the path drop area. See Figure 148.
c)
Select the node from the browser/node list or the NAP from the nap list and enter the command Add:
Leg either by selecting the relevant tool button or by using the menu Modification: Add Leg. The
selected node now appears in the Leg drop area of the Add Leg dialog box. Alternatively you can
drag the node from browser to the Add Leg window, as per Figure 149.
d)
Click on button Add Leg. See Figure 150. The leg is allocated and implemented.
e)
Removing a leg
Select the sink NAP to remove and issue the action Broadcast Path Modify: Remove Leg. It is possible
to release the NAP or to keep it associated to the path.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
173 / 258
ED
01
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
SC.3:OPERATION
3AL 61348 AA AA
258
174 / 258
BROWSER / MAP
DRAG
Add Leg
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
175 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
176 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Server MS protection usage profile: it represents the profile of the MS resources to be used in
allocating the path.
The possible values are:
ED
Normal
(default)
For 1664SM rings, the RIP mechanism is used, i.e. when crossing 4 Fibers MSSpring,
the path uses only working (high priority) resources, except for primary and secondary
nodes of the double interconnection with another ring, because these nodes are
characterized by the Drop & Continue protection ( RIP )
as a result, in the segment between service nodes:
if the path is bidirectional, the used resource (nodes E, D, H, I) can be only the
protection one: a bidirectional D&C IC on protection is performed in the primary
nodes (D, H);
protection if the signal flows into the service nodes (B, C): a unidirectional D&C IC
on protection is performed in the primary node (B);
working if the signal flows out of the service nodes (E, D): a multipoint connection
is performed in the primary node (E); this allows the user to perform subsequent add
leg operation;
it is possible to use the protection resource instead of the working (nodes E, D), e.g.
forced by a constraint ;
protection if the signal flows into the service nodes (B, C) like in a unidirectional
pointtopoint path: a unidirectional D&C IC on protection is performed in the primary
node;
working if the signal flows out of the service nodes (E, D): a multipoint connection
is performed in the primary node);
it is not possible to use the protection resource instead of the working one.
As a result of the previous rules defined for unidirectional and broadcast paths, a
unidirectional pointtopoint path can become broadcast only if the working
resources are used between service nodes (nodes E, D ).
For 1670SM rings the path uses only working resources ( RIW )
Protection preferred
When crossing a 4 Fibre MSSpring, the path uses protecting (low priority) resources.
If the routing algorithm must use the working resource in one span of the 4F MSspring (e.g.
no free resources in the protection, or a constraint is applied), all working resources are used
in the ring, in order to avoid jumps between working and protection resources (jumps not
foreseen for the management of ring traffic map).
If the path is protected and main and spare routes are crossing the same MSSpring, each route
crosses separately the ring itself since D&C connection are not available for protecting
resources.
As a consequence of this behavior and of the fact that the SNCP connection is not available on
a 4f MSSpring, if the protected HO path is completely inside a 4f MSSpring, the allocation
will always fail.
Protection only
the path uses only protecting (low priority) resources.
01
SC.3:OPERATION
3AL 61348 AA AA
258
177 / 258
The procedure used to create a path crossing a NPE Ring is the same as described in the
previous paragraphs.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
N.B.
SNCP
RX
NPE
F
SNCP
SNCP
RX
B
NPE
Equipment=1664SM
SNCP
TX
Figure 152. Bidir. Path, 1664SM, RIP
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
178 / 258
TX
SNCP
ED
01
B
E
C
NPE
RX
SNCP
SNCP
RX
A
B
NPE
C
F
E
D
Equipment=1670SM
SNCP
TX
SC.3:OPERATION
3AL 61348 AA AA
258
179 / 258
unidirectional passthrough
protected drop
D/CW INSW
D/CE INSW
D/CE INSE
D/CW INSE
D/C stands for Drop and Continue, the letter after it (W=West, E=East) indicates the drop protected side
(e.g., W means West main side, and spare side is the EAST one).
The end letter (INSE or INSW) indicates the insert side.
The Unidirectional passthrough is always in the direction opposite to that of the insert side (e.g., when
INS E the passthrough is from East to West).
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
180 / 258
For further information refer to Figure 154. on page 181 which shows the D/CW INSW configuration.
WEST
AGGREGATES
EAST
Tx
Rx
Tx
Rx
TRIBUTARY
Tx
Rx
indicated in
The operative switch is on node 8 and the previous pass through between nodes 4 and 3 is no more used.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
181 / 258
ED
5
01
D/CW
3
INSW
D/CW
E
W
INS
W
INSW
D/CE
4
6
D/CE
258
INSE
INS
W
TRIB
3AL 61348 AA AA
INS
E
TRIB
E
INS
E
INSE
10
9
SC.3:OPERATION
182 / 258
ED
01
5
3
4
6
10
7
9
2
5
3
4
6
10
SC.3:OPERATION
3AL 61348 AA AA
258
183 / 258
a)
With reference to a network like the one shown in Figure 155. select the end nodes and issue Tools:
Create Path.
b)
In the path create wizard select protection = D & C SNCP. Execute the complete sequence of path
create, as required by the wizard. Finally click on Finish button.
c)
d)
e)
Clicking on Routing view button it is possible to display main, spare and service routes.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
184 / 258
3.11.1.1 Path create in D & C network with ADMs (4node D & C network)
ET1
1
1
2
ET2
1
ET3
1
Figure 158. Network submaps of the 3 2nd level subnetworks (ET1 , ET2, ET3) for 2 Node D & C
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
185 / 258
2N D&C
ET3
ET1
tpA
tpAZ
tpZ
tpZA
tpAZ
tpA
tpZA
tpZ
ET2
SIDE A
SIDE B
The path create procedure described at para 3.11.2.1 herebelow refers to the example network of
Figure 158. and Figure 159.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
186 / 258
Rate=140 Mb,
main route
spare route
The graphical appearance of this figure has been changed while contents maintain their validity
Figure 160. Routing view for 2N D & C path.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
187 / 258
If you click on the icon of the Switch status, the system opens a subwindow which displays the switch
status. Figure 161. shows the subwindows relevant to the routing display view of Figure 160.
Z
Z
ZA
ZA
AZ
AZ
A
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
188 / 258
ZA
AZ
N.B.
ED
The drawing of the switch shows the main switch position (line) and spare switch position (
dashed line). The actual switch position is marked by a M ( switch turned on main ) or S ( switch
turned on spare ). See above Figure 162.
01
SC.3:OPERATION
3AL 61348 AA AA
258
189 / 258
BOARD
NODE NAME
SUBRACK
RACK
PORT
Channel (N.A.)
PAYLOAD POSITION
The CTP name ( see above figure ) contains the port name; then from the CTP issue Display:
Related items: Ports. From the Port issue Display: Related items: Physical Connection.
tp A: comprises a switch for the connections coming from tp Z and tp ZA, one point to point from tp
A to tp Z, one point to point from tp A to tp AZ
tp Z: comprises a switch for the connections coming from tp A and tp AZ, one point to point from tp
Z to tp A, one point to point from tp Z to tp ZA
tp ZA: comprises one point to point from tp ZA to tp A, one point to point from tp Z to tp ZA
tp AZ: comprises one point to point from tp AZ to tp Z, one point to point from tp A to tp AZ
The default switch type is NOT revertive.
N.B.
As in the case of the normal D&C, it is not possible from the User Interface to select the TPs
involved in the D&C but they are automatically selected by the algorithm. The TPs can be
selected from the command mode because this is needed to support the redolog
functionality.
It is also possible to add or to remove the D&C protection to path without or with D&C protection. Relevant
commands are under menus:
Protection: Add submenu
Protection: Remove popup submenu
3.11.3 Path Constraints in a 2Node SNCP network
The values Use Service Forwards and Use Service Backwards are significant for paths crossing a
Dual Node SNCP network.
The user drops as constraint one of the Physical connections between the two D& C nodes, or a link
connection, or a CTP, then must select between Use Service Forwards and Use Service Backwards.
If the user selects Use Service Forwards, the object dropped as constraint will be used as service
route/termination to protect the forward transmission direction (from A to Z or from the left to the right
or the TX). See Figure 164.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
190 / 258
If the user selects Use Service Backwards, the object dropped as constraint will be used as service
route/termination to protect the backward transmission direction (from Z to A or from the right to the
left or the RX). See Figure 164.
FORWARD
BACKWARD
AS CONSTRAINT:
AS CONSTRAINT:
Figure 164. Use Service Forward/Backward for Dual Node SNCP network
In fact, a path supported by a single virtual ring between the end points A and Z, is not able to survive to
a double failure. See Figure 165. herebelow.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
191 / 258
Rate=140 Mb,
main route
spare route
If you click on the icon of the Switch status, the system opens a subwindow which displays the switch
status. shows the subwindows relevant to the routing display view of Figure 160.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
192 / 258
The graphical appearance of this figure has been changed while contents maintain their validity
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
193 / 258
Figure 167. shows the involved connections . The default switch type is NOT revertive
N.B.
The drawing of the switch shows the main switch position (line) and spare switch position
(dashed line). The actual switch position is marked by a M ( switch turned on main ) or S ( switch
turned on spare ). See above Figure 167.
The implementation of the enhanced SNCP causes the creation of 4 unidirectional SNCP in the NE: .
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
194 / 258
tp A: comprises a switch for the connections coming from tp Z and tp ZA, one point to point from tp
A to tp Z, one point to point from tp A to tp AZ
tp Z: comprises a switch for the connections coming from tp A and tp AZ, one point to point from tp
Z to tp A, one point to point from tp Z to tp ZA
tp ZA: comprises one point to point from tp ZA to tp A, one point to point from tp Z to tp ZA
tp AZ: comprises one point to point from tp AZ to tp Z, one point to point from tp A to tp AZ
N.B.
As in the case of the normal D&C, it is not possible from the User Interface to select the tps
involved in the D&C but they are automatically selected by the routing algorithm. The tps can
be selected from the command mode because this is needed to support the redolog
functionality.
It is also possible to add or to remove the D&C protection to path without or with D&C protection by either
pointing to the topology where the interconnection NEs are included (e.g. the ET which contains the Cross
connect equipment) or to the whole path.
By using an enhanced SNCP the protection level of the path increases.
The default switch type is not revertive .
the enhanced SNCP is automatically inserted at path/trail allocation time for protected paths/trails
when the main and the spare are crossing the same NE and the equipment supports this type of
protection.
The user can add / remove the enhanced SNCP protection in two different ways:
ED
applying the add/remove service to the whole path/trail: the enhanced SNCP protection is also
removed
applying the add/remove service to the connection in topology at NE level: the enhanced SNCP
protection is modified only at NE level.
No limitation should be present on the NE support of the connection since the result in this case
is the failure in implementing the protected path
01
SC.3:OPERATION
3AL 61348 AA AA
258
195 / 258
The Add / Remove Protection command can be executed on a path/trail or directly on the connections in
topology.
The following paragraphs give examples of usage of this command.
The resources needed for a successful command completion could be used by other paths; it is
advisable to create protected paths instead of adding subsequently the protection; namely in
this case the allocation algorithm makes the reservation of nonoverlapped routes.
In case of overlapping of an existing route with the new protection route required by the Add
Protection command, it is possible to find the existing route by using the Paths in trail view
invoked on the trails terminated to the nodes where terminates the path to be protected.
locate
routing view
PATH
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
196 / 258
a)
Select the path from the path list and click on Add/Remove Protection Tool button. The Add/Remove
Protection Tool wizard is displayed. See below figure. Possible options are:
Add Service. This item is selectable only if the path protection type is D & C. The service route is
allocated and implemented.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
197 / 258
Remove Service. This item is selectable only if the path protection type is D & C. The service route
is removed
b)
Select option item Add Protection Spare. Click on Next button. The Add/Remove Protection wizard
step 2, allowing the selection of the switch is presented. See following figure.
path routing button
SELECT button
Click on upper path routing button which retrieves the path routing view. From this view select the
switch where you want to start the protection and click on button Select to confirm. The routing view
automatically closes and the selected switch is displayed in the main window
d)
Click on lower path routing button which retrieves again the path routing view. From this view select
the switch where you want to end the protection and click on button Select to confirm. The routing
view automatically closes and the selected switch is displayed in the main window. See following
figure.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
198 / 258
e)
ED
Click on Finish to confirm. The action is started and the report is displayed. See following figure.
01
SC.3:OPERATION
3AL 61348 AA AA
258
199 / 258
f)
ED
01
3AL 61348 AA AA
258
REFRESH
Click on Refresh button. The routing view is updated. See following figure.
SC.3:OPERATION
200 / 258
REPORT
g)
ED
Click on Report button to display the route report. See following figure.
01
SC.3:OPERATION
3AL 61348 AA AA
258
201 / 258
Select the path icon from the routing display and move the mouse to Remove protection menu item.
Two options are selectable:
1)
Keeping main. If the actual route corresponds to the main one, the protection route ( the spare
one ) is removed and the path remains on the main route .
Keeping spare. If the actual route corresponds to the spare one, the protection route ( the main
one ) is removed and the path remains on the spare route .
Service. If the actual route corresponds to the main/spare route, the service route is removed
and the path remains on the main/spare route.
2)
ED
01
202 / 258
Keeping main. The protection route ( main or spare one ) is removed and the path remains/is
routed on the main route .
Keeping spare. The protection route ( main or spare one ) is removed and the path remains/is
routed on the spare route .
Service. The service route is removed and the path remains/is routed on the main/spare route.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
203 / 258
From the path list or trail list select an HO path or an HO trail and select button Create Restoration
Rule. See Figure 175. The Create Restoration Rule is displayed. See Figure 176. on page 205
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
204 / 258
optimized add protection (for point to point transports only) .This strategy does not cause
a complete path rerouting but only finds a spare route inside the lowest level topology
( e.g. a ring ) affected by the fault.
end to end add protection. (for point to point and broadcast transports) This strategy
causes a complete path rerouting by allocating the path spare route.
remove protection + end to end add protection (for point to point transports only). It
removes the protections and adds one end to end spare route. For paths protected by the
D&C mechanism both spare and spare+service connections are removed; only one end
to end spare route is allocated.
Hold Off Time (sec) . This time is the waiting time before starting the restoration subprocess.
3)
4)
all objects. This option will successfully restore the transport upon repair of the related
resources.
ED
01
205 / 258
c)
use default constraints. This option sets the usage of the spare constraints for the
transport restoration. The spare constraints are added by means of the Path Constraints
application.
Click on the functional button Create. The restoration rule is created. Its name coincides with the
transport name.
From the browser point to the network domain and issue the command Display: Related Items. Select
Restoration Rules. The icon of the restoration domain is displayed in the browser window ( see
Figure 177. ) and the restoration rule list opens. See Figure 178.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
206 / 258
b)
ED
hold off active. The restoration activity will start at hold off time expiration.
failed. The restoration process did not complete the allocation because of lack of resources.
not performed. The restoration process did not complete the allocation because of external
conditions.
date of the last successful restoration result
You can display other attributes by selecting the transport and issuing the command
Actions:Details:Show/Set Attributes. The dialog box of Figure 179. is presented.
01
SC.3:OPERATION
3AL 61348 AA AA
258
207 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
208 / 258
Join/Split path are used to merge a pair of paths into one single path or to split a path into a pair of paths.
3.14.1 Join Paths
SCOPE
The scope of this procedure is to merge a pair of paths into one single path.
CONDITIONS
a)
In the example which follows a path crossing R1 must be merged to a path crossing R2. T
b)
ED
By clicking twice on the icons of R1 and R2 it is possible to display the two ring submaps. See
Figure 181.
01
SC.3:OPERATION
3AL 61348 AA AA
258
209 / 258
Both RING1 and RING2 are crossed respectively by path P1 and path P2 which physically are the
same path. Namely both P1 and P2 are terminated to virtual nodes NE_V1 and NE_V2. The Path
List containing P1 and P2 is shown in Figure 182. To display the Path List, from the browser, point
to the Network icon and issue Actions: Display: Related items: Paths in Topology + No Filter.
The Path List is displayed. See Figure 182. on page 210
HIGHLIGHT
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
210 / 258
c)
From the path list (see Figure 183. herebelow) join paths P2+P3. Select the paths and issue Actions:
Modification: Join.
a)
b)
In the Join path dialog box enter the name of the joined path (e.g. P ) and click on the functional button
Join path. After a few seconds paths P2 and P3 are deleted and the new path P is created and
implemented.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
211 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
212 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
SCOPE
The split path is the reverse operation of the join path.
SEQUENCE
a)
Select the path P to split from the path list and issue Actions: Modification: Split
b)
In the Split path dialog box enter the names of the two paths which are replacing the path to split and
click on Split path button. The system presents to the user the list of the nodes along the path route.
c)
Select the node where the path must be split and confirm. Path P is deleted and the new paths are
created and implemented.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
213 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
214 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
b)
ED
in the Split trail dialog box enter the trail names of the new trails and click on Start Split button.
01
SC.3:OPERATION
3AL 61348 AA AA
258
215 / 258
c)
The system presents the list of the possible splitting nodes. Select the node and click on OK.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
216 / 258
The LOPaths crossing the splitting Node are modified by adding LO passthrough connection.
The related protection indexes are updated.
The payload structure and the LO connections of the 2 nodes at the end of the involved HO trails are not
modified during the operations: modifications to connections and payload structure are applied only to the
splitting node.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
217 / 258
SEQUENCE
a)
From the trail list select the HOTrails to join. See Figure 194.
b)
Select the command Actions:Modification: Join. The Join trail dialog box is presented, containing the
two selected trails, as per Figure 195. Enter the name of the new joined trail.
c)
all LOpaths using the original HOTrails are crossing with passthrough connections the
intermediate NE without LO timeslot interchange.
As a consequence of the operation:
the LOPaths crossing the original HOTrails are modified by removing the passthrough
connections in the intermediate NE. The related protection indexes are updated.
The payload structure and the LO connections of the 2 nodes at the end of the involved HO trails are not
modified during the operations: modifications to connections and payload structure are applied only to the
intermediate node.
The operation reduces the impacts on the existing traffic: LOPaths client of the involved HO trails are
disconnected only for the time necessary to perform the operation and only in the segment of network
between the end nodes of the involved HO trails.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
218 / 258
Two HOTrails entering in a given NE can be joined in order to reduce the LO usage of resources.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
219 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
220 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
a)
ED
From browser interface point to the icon of the Physical Connection to split and issue the command
Topology Modification: Split.
01
SC.3:OPERATION
3AL 61348 AA AA
258
221 / 258
b)
ED
The guided interface structure ( the so called wizard ) opens. See Figure 197. herebelow. It contains
in the upper part of the window the icons of the physical connection to split and the connected ports.
01
SC.3:OPERATION
3AL 61348 AA AA
258
222 / 258
The central part of the window allows to select the node to insert. Click on the selection button ( three
points ). The node list is presented. See Figure 198.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
223 / 258
c)
Select the node to insert and click on Apply button. The icon of the selected node appears in the wizard. See Figure 199. herebelow. You can also display the node in the map by clicking on the Highlight
button.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
224 / 258
d)
Click on Next button to continue the procedure. The wizard now presents the first port of the physical
connection being splitted and the node being inserted. Click on the selection button in order to select
the port of the new node to connect to the first port of the physical connection being splitted. The relevant port list is displayed. See Figure 201.
e)
ED
Select the port to connect and click on Apply button. The icon of the selected port is presented in the
wizard. See Figure 202.
01
SC.3:OPERATION
3AL 61348 AA AA
258
225 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
226 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Enter the new connection name and click on Next button to continue.The wizard now presents the
second port of the physical connection being splitted and the node being inserted. Click on the selection button in order to select the port of the new node to connect to the second port of the physical
connection being splitted. The relevant port list is displayed.
g)
Select the port to connect and click on Apply button. The icon of the selected port is presented in the
wizard.
h)
Enter the new connection name and click on Next button to continue.The wizard now presents the
summary view of the operations executed by the user. See Figure 203. herebelow.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
227 / 258
i)
ED
If you click on Finish button the existing physical connection is deimplemented and deleted, while te
new physical connections are created, implemented and structured accordingly. In particular, the following steps are performed:
1)
2)
3)
Insert node in ET
4)
MSTP structure
5)
6)
01
SC.3:OPERATION
3AL 61348 AA AA
258
228 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
229 / 258
From browser interface point to the icon of the Physical Connection to slit and issue the command
Topology Modification: Join. The Join Physical Connections dialog box is displayed. See
Figure 204. on page 230
b)
From browser window drag and drop the second physical connection to join, enter the connection
name and click on Start Join button.
c)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
230 / 258
SCOPE
If following a join/slit physical connection procedure, the physical connection enters the Fail to disconnect
state, the operator can select the Connect path action or repeate the failed action.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
231 / 258
If following a join/slit physical connection procedure, the physical connection enters the Fail to connect
state, the operator can select the Connect/Disconnect Path/Trail
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
232 / 258
From the path popup menu select item Client Alarms: PDH alarm monitoring. The ISDNPRA dialog
box is presented. See Figure 207. on page 234. The dialog box is structred in two sequential views.
The first window allows to select the PDH alarm monitoring type. See Figure 207. on page 234 .
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
233 / 258
framed. The pdh signal frame is monitored and consequent alarms are generated. The monitoring
direction ( ingressing / egressing, both or none )
ISDNPRA ( Integrated Service Data NetworkPrimary Access=2 Mb/s ). This option is allowed for
bidiectional paths only. Only one of the two ports must be marked as NT ( Network Termination ). PDH
monitoring ( frame monitoring ) will be activated only on the port marked as NT, which is the one connected to the TE ( Terminal Equipment = Users premises
leased line PRA. This option is allowed for bidiectional paths only. One or both of the two ports can
be marked as NT ( Network Termination ). PDH alarm monitoring will be applied only on NT ports.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
234 / 258
c)
ED
Select the desired option and click on Next button.
01
SC.3:OPERATION
3AL 61348 AA AA
258
235 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
236 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
3.18 4 x ANY
3.18.1 Introduction
The 1696MetroSpan provides the 4XANY TDM card.
The 4XANY TDM card is a TDM concentrator board, based on the following concepts:
The following client signals can be transported:
The board accepts at most 4 signals and mapping is performed into a STM16 (2.5 Gbit/s) port
The architecture of TDM concentrator board is based on the concept of virtual concatenation, and on the
mapping of SDH on OTN:
Data traffic is packet into VC4 structures (virtually concatenated)
The following table resumes the traffic that can be transported and the number of VC4 required:
Traffic
Speed
FDDI
125 Mb/s
VC41v
Fast Ethernet
125 Mb/s
VC41v
ESCON
200 Mb/s
VC42v
DV
270 Mb/s
VC42v
STM1
155 Mb/s
VC42v
STM4
622 Mb/s
VC45v
FC
1.062 Gb/s
VC48v
Gigabit Ethernet
1.25 Gb/s
VC48v
N.B.
Applicable for STM1 and STM4 terminations. Only the SDH physical connection between the 2 SDH NE is described in RM and the manual correlation function can permit
to associate the underlying DATA PATH to it. Fiber cut on the fiber connecting the
SDH NE adjacent to the SDH port of the 4xany card will be detected on SDH NE side and
will impact the mentioned above SDH physical connection.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
237 / 258
Connected inside the 1696MetroSpan to the OPC card to perform the SNCP protection of the RS
client path in the OTH network (Optical protection).
Alone inside the 1696MetroSpan (CPE configuration case). In this case, 1696MetroSpan, configured as CPE, could be connected to either another 1696MetroSpan (not configured as CPE), a
1686WM or a 1640WM (either through B&W or coloured interface), an SDH NE (through B&W interface).
Due to the fact that the RS signal is terminated on the 4XANY, the 1696MS hosting this board has to be
visible both in SDH and OTH domain, i.e. the STM16 port of the 4XANY board has to be managed as:
UNI B&W or coloured port of an SDH NE. In particular in the first and second above listed cases,
the STM16 port will be connected by the user, through an internal physical connection, to the OPS
port of respectively the transponder or the OPC card.
In the third case, the user will create a physical connection connecting the STM16 port of the 1696WM
(CPE) and the OPS port of either a 1686WM or a 1640WM.
On the client side (data port) the 4XANY can be physically connected to an OMSN NE to transport an
STM1/STM4/GigabitEthernet traffic, coming from the SDH network, into the OTH network. It is not possible to describe in the RM this physical connectivity (between an STM1/STM4/GigabitEthernet port of
the 4xANY and an OMSN NE port at the same rate); the user has to correlate through the correlation function the SDH physical connection between the two external OMSN NEs to the Data path terminated on
the two 1696MS NEs.
3.18.2 Upload of the Data ports
When uploading a gMAUTTP port of the 1696MS, the system automatically creates the following objects:
A RM port characterized with:
Technology: Data
Physical Port Type: is set according to the value of the dataClientType attribute of the
gMAUCTPBid MOC retrieved from the NE
Au4maxSupportedConcLevel and concLevelMode are set according to the following table
physicalPortType
Au4Supported ConcLevel
concLevelMode
Eth/100Mbtransp
notModifiable
Eth/1Gbtransp
notModifiable
Fddi
notModifiable
Escon
notModifiable
DigitalVideo
notModifiable
FiberChannel
notModifiable
Stm1
notModifiable
Stm4
notModifiable
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
238 / 258
Connected inside the 1696MetroSpan to the Transponder card to transport Data traffic on the RS
signal (STM16) on the OTH network.
To create a path involving a 4XANY board, the user, during the path creation activity, has to select:
Service Type either Ethernet or Data.
According to the selected Service Type all consistent values of Service Rate attribute are presented to
the user.
In case of Service Type =Ethernet and Service Rate =1Gbit/s Ethernet Transparent , the list of NAP
s available on either 1670SM or 1696MS(4XANY) is provided. For all the other cases, only NAP s on
1696MS will be listed. The path is created with Transport Rate attribute equal AU4nV, concLevel attribute equal to the concLevel attribute of NAP s and concLevelMode equal notModifiable.
3.18.4 Example
a)
From the browser node list select the node which houses the 4XANY board and issue Search: Main
Related items: Ports in Node
STM16 board
DATA boards
STM16 board
DATA boards, according to the table explained above at para 3.18.1 on page 237
c)
The path using these ports is Ethernet with Service rate=AU4nV (concatenated).
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
239 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
240 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
4 NETWORK MODIFICATIONS
4.1 Introduction
The main procedures described in this Chapter are:
Add Q3 NE to a 2F MS Spring
N.B.
The execution of the RedoLog file does not cause the allocation of the path/trail; however
some checks take into account the topological modifications:
in case of node insertion the passthrough connection is added in the new node.
in case of node remove the passthrough connection thru the removed node is ignored.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
241 / 258
SCOPE
The new Network Element must be inserted in the network as shown in Figure 211.
NE2
NE3
NE1
NEW NETWORK ELEMENT
The upload of the EML info from EML to RMMIB is automatically performed.
b)
c)
By means of the command Create Connection, create the connection between the involved
NEs/topologies.
d)
Execute the Implementation of the new Physical Connection. (This causes also the NE
implementation, i.e. the reset of the NE )
Payload Configuration
Path Management
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
242 / 258
SCOPE
The scope of this procedure is to insert a NE into a SNCP ring.
CONDITIONS
The new Network Element must be inserted in the network as shown in Figure 212.
NE2
NE3
NE1
The user can protect paths using the physical connection to be interrupted ( NE1 Thru NE3 ). The
user can verify by means of the command Physical Connection: ( display ) Paths active in
physical connection which is the path actual route.
If traffic survivability is required, from the path list select all paths and protect them by means of Add
Protection: Spare. Verify, with reference to Figure 212. ,that the upper route is working for all paths.
Execute the force operation to the upper route for all involved paths and verify that all paths have been
successfully forced and are operational.
b)
Move all paths from the physical connection to be interrupted (NE1 thru NE3)
1)
2)
For paths protected at above point a ), select them and use option Remove Protection: Keeping
Spare.
For paths previously protected, reroute manually on the main or spare route according to the
route type crossing the physical connection.
c)
If the node to be inserted is a QB3* node, put the node in download disable condition.
d)
Execute the split physical connection procedure. See paragraph 3.16.1 on page 221.
e)
If the node to be inserted is a QB3* node, put the node in download enable condition and execute
Global Download on QB3* NE.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
243 / 258
SCOPE
The scope of this procedure is to remove a Network Element from a SNCP ring.
CONDITIONS
The SNCP reference ring is shown in Figure 212. on page 243. Some paths are crossing the NE being
removed.
SEQUENCE
a)
On the node issue the command Display: Paths active starting/ending from a node
b)
The user can protect paths using the physical connection to be interrupted ( NE1 Thru NE3 ). The
user can verify by means of the command Physical Connection: ( display ) Paths active in
physical connection which is the path actual route.
If traffic survivability is required, from the path list select all paths and protect them by means of Add
Protection: Spare. Verify, with reference to Figure 212. ,that the upper route is working for all paths.
Execute the force operation to the upper route for all involved paths and verify that all paths have been
successfully forced and are operational.
c)
Move all paths from the physical connection to be interrupted (NE1 thru NE3)
1)
2)
d)
For paths protected at above point a ), select them and use option Remove Protection: Keeping
Spare.
For paths previously protected, reroute manually on the main or spare route according to the
route type crossing the physical connection.
1354RM
Execute the Join Physical Connection Procedure
a)
Execute the Force Switch operation on adjacent protection blocks, where the new NE must be
inserted: Force West on one side and Force East on the other side.
The information of Node Position in ET and Node Id in ET can be displayed by issuing the Show/Set
Attributes command on the Protection Block.
b)
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
244 / 258
1)
Execute the command Configure Download: Disable on QB3 STAR Network Elements.
2)
3)
Click twice on the physical connection group ( line between the two nodes involved. The
physical connection list opens.
Select the Physical Connection and issue Topology Modifications: Split Physical Connection.
Execute the split connection procedure.
c)
Change the Run Level to Network Consistency. From the Process Monitor select Actions: Set Run
Level: 3 Ntw Consistency
d)
Select all QB3 STAR NEs and execute Consistency Download: Global.
e)
f)
g)
h)
Execute all cable unplug and plug operations NOW, before activating the MS Spring on the inserted
NE.
i)
Execute the Force Switch operation on adjacent protection blocks, where the new NE must be
inserted: Force West on one side and Force East on the other side.
The information of Node Position in ET and Node Id in ET can be displayed by issuing the Show/Set
Attributes command on the Protection Block.
b)
ED
Execute the command Configure Download: Disable on QB3 STAR Network Elements.
2)
Execute the command Configure Download: Disable on QB3 STAR Network Elements and on
Q3 Network Elemets
3)
Click twice on the physical connection group ( line between the two nodes involved. The
physical connection submap opens. Select the physical connection and browse it by means of
Supervion: Browse: Object.
01
SC.3:OPERATION
3AL 61348 AA AA
258
245 / 258
c)
Change the Run Level to Network Consistency. From the Process Monitor select Actions: Set Run
Level: 3 Ntw Consistency
d)
Select all QB3 STAR NEs and execute Consistency Download: Global.
e)
f)
g)
h)
Execute all cable unplug and plug operations NOW, before activating the MS Spring on the inserted
NE.
i)
j)
Release switches
Execute the Force Switch operation on adjacent protection blocks, where the NE must be removed
Force West on one side and Force East on the other side.
The information of Node Position in ET and Node Id in ET can be displayed by issuing the Show/Set
Attributes command on the Protection Block.
b)
Execute the command Configure Download: Disable on QB3 STAR Network Elements.
2)
c)
d)
ED
1)
From the map click twice on the first physical connection group. The physical connection list
opens. Select the physical connection.
2)
From the map click twice on the second physical connection group. The physical connection
list opens. Select the physical connection.
01
SC.3:OPERATION
3AL 61348 AA AA
258
246 / 258
From the browser select the Physical Connection and issue Topology Modifications: Split
Physical Connection.
Select the two Physical Connections to join and issue Topology Modifications: Join Physical
Connection. Execute the join physical connection procedure.
e)
Change the Run Level to Network Consistency. From the Process Monitor select Actions: Set Run
Level: 3 Ntw Consistency
f)
Select all QB3 STAR NEs and execute Consistency Download: Global.
g)
h)
i)
j)
k)
b)
c)
d)
e)
f)
Set Download Enable mode on the node, which has just been inserted
g)
h)
i)
Remove the Forced Ring Switch on the nodes adjacent to the inserted node
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
247 / 258
a)
b)
c)
Set Forced Ring Switch on the nodes adjacent to the node being removed
d)
Remove the physical fibers from the node being removed, by respecting the following order:
1)
remove RX spare
2)
remove TX spare
3)
remove RX main
4)
remove TX main
e)
f)
g)
Remove the Forced Ring Switch on the nodes which were adjacent to the removed node
h)
Set Download Enable mode on the node, which has just been inserted
ED
01
SEQUENCE
SC.3:OPERATION
3AL 61348 AA AA
258
248 / 258
On the relevant NAP List verify that no path is using any trib. port of the board being removed i.e.
the nap idle indicator should be Idle.
b)
On the relevant NAP List select the NAP related to the trib. ports to be removed and issue the
command Actions:Remove:Remove NAP. The relevant ports pass from Assigned to Observed.
On the 1353NM station delete the relevant board. The board is no longer present in the views.
In the NE port list the ports deleted are no longer present.
c)
d)
c)
d)
On the 1353NM station delete the relevant board. The board is no longer present in the views.
SEQUENCE
a)
b)
On the map execute Upload NE Ports. From this point on you can use the port in the network
construction.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
249 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
250 / 258
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
On 1354RM: Remove the VC4 NAP associated to the 140 Mb port. The detailed sequence is:
1)
From browser point to the involved node and issue Actions: Display: Main related Items: NAPs.
2)
The NAP list is displayed. Select the VC4 NAP and issue Actions: Remove NAP.
3)
4)
b)
c)
d)
Point to the Node and issue Actions: Display: Main Related Items: Ports. The Port List is
displayed. The 140Mb port assignment status is OBSERVED.
On 1353SH: Execute the payload structure configuration to VC12.
On 1354RM: Execute the EML: Synchronize command. The 140 Mb Port (OBSERVED) is replaced
by the 2 Mb ports ( OBSERVED ).
On 1354RM: Execute the Upload NAPs command. The detailed sequence is:
1)
From browser point to the involved node and issue Actions: Configuration: Upload NAPs.
2)
The user can display the uploaded NAPs, e.g. from browser, pointing to the node and issuing
the command Actions: Display: Main Related Items: NAPs. The NAP List now contains the
VC12 TTPs ( NAPs).
N.B.
a)
On 1354RM: Remove the VC12 NAPs associated to the 140 Mb port. The detailed sequence is:
1)
From browser point to the involved node and issue Actions: Display: Main related Items: NAPs.
2)
The NAP list is displayed. Select the VC12 NAPs and issue Actions: Remove NAP.
3)
Point to the Node and issue Actions: Display: Main Related Items: Ports. The Port List is
displayed. The assignment status of the 64 2Mb ports is OBSERVED.
b)
c)
On 1354RM: Execute the EML: Synchronize command. The 2Mb Ports (OBSERVED) are replaced
by one 140 Mb port ( OBSERVED )
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
251 / 258
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
252 / 258
ED
Add operator
01
SC.3:OPERATION
3AL 61348 AA AA
258
253 / 258
a)
b)
c)
two textlines: RM Initiator and Initiator Name where the Administrator operator can digit the
RM Initiator ( integer ) and the Initiator Name (it must be unique in the file).
The Initiator Identifier must be given according to the following rules:
The Initiator Name is added to the possible values of the NAD attribute. The NAD attribute
is used to mark Network Resources (using the change NAD command) and to evaluate
Access Rules.
d)
Enter the suitable RM Initiator and Initiator Name and select the rules to be associated. Click on
the Rule button. The list of the available rules opens. Each item of the list has a toggle button, i.e.
you can select many rules per each Initiator. The following rules can be selected:
AC_R_VPN
AC_R_EVPN
AC_R_RVPN
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
254 / 258
SEQUENCE
SCOPE
This function allows the Administrator to create a new operator at a time on WSs belonging to the network
configuration.
SEQUENCE
a)
b)
c)
d)
VPN Operator name. It is the same name which will be inserted by the VPN Administrator while
executing the VPN Handling procedure.
e)
Initiator: the Initiator Name previously specified at paragraph 5.1.1 on page 254.
A subsequent confirmation box containing all data relevant to the New Operator being created is
presented. If you press OK the Operator is created. This dialog box also contains the button Abort
to abort the procedure.
you can confirm the Operator creation by pressing button Add.
f)
ED
1 couple of radiobuttons, with label: All WS to select all WS on which to add operator, and
Select WS to allow selection from the listbox of WS;
1 button above the WS listbox, with label Apply : it gives effect to WS selection for operator
creation, and filters the users list;
Data entering
1 listbox, unselectable, which contains the list of users existing on selected WS. The list is
equipped of an header indicating the composition of items line:
Workstation
Username
Profile
Real Name
Initiator
;
1 popdown menu for choosing among available profiles, with label Profiles;
1 popdown menu for choosing among available initiators, with label Initiators;
2 buttons: Add to create described operator, Close to close the window and return to the
Main.
01
SC.3:OPERATION
3AL 61348 AA AA
258
255 / 258
SCOPE
The scope of this procedure is to assign the desired NAP to a certain NAD ( Initiator Name ), which
corresponds to a certain RM Operator, which in turn will correspond to a certain VPN.
CONDITIONS
This assignment is required for all VPN types ( Standard / Enhanced / Restricted )
SEQUENCE
1)
Select the NAP(s) from the Nap list and issue the command NAD (Network Assignment
Domain): Change.
2)
In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD ( the Initiator Name mentioned at
paragraph5.1.1 and confirm by clicking on OK. Click again on OK of the dialog box.
This assignment can be executed for VPN types Standard and Enhanced
SEQUENCE
1)
Select the link connection from the lc list and issue the command NAD (Network Assignment
Domain): Change.
2)
In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD ( the Initiator Name mentioned at
paragraph 5.1.1 and confirm by clicking on OK. Click again on OK of the dialog box.
As a result of this operation, the boundary CTP is assigned to the above NAD.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
256 / 258
This assignment can be executed for all VPN types ( Standard / Enhanced /
Select the NAP(s) from the Nap list and issue the command NAD (Network Assignment
Domain): Change.
2)
In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD ( the Initiator Name mentioned at
paragraph 11.2 and confirm by clicking on OK. Click again on OK of the dialog box.
2)
In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD ( the Initiator Name mentioned at
paragraph 5.1.1 on page 254 and confirm by clicking on OK. Click again on OK of the dialog
box.
2)
In the Change NAD dialog box select the icon dictionary. The NAD selection box opens. Select
the domain corresponding to the previously specified NAD ( the Initiator Name mentioned at
paragraph 11.2 and confirm by clicking on OK. Click again on OK of the dialog box.
The NAP and the boundary CTP are not assigned automatically: the operator must execute the
procedures described at paragraphs 5.1.3.1 and 5.1.3.2 on page 256.
ED
01
SC.3:OPERATION
3AL 61348 AA AA
258
257 / 258
Constraints, 169
Implementation, 84
ED
01
Ring, 63
Startup, 12
Subnetwork, 18
Leg, 173
N
U
NAP, 103
Upload, 103
INDEX
Payload, 86
Path, 109
END OF DOCUMENT
SC.3:OPERATION
3AL 61348 AA AA
258
258 / 258
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
10
2 FAULT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Elementary Alarms and RM Probable Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Alarm Enabling/Disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Q3 Alarm Enabling/Disabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 QB3* Enabling UPA on specific CTP/CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3 Enable / Disable frame supervision alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.4 ISDNPRA alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Alarm Severity Assignment Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1 ASAP list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2 ASAP create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.3 ASAP correlate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.4 ASAP modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 SDH Object Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
14
14
16
18
19
20
20
21
22
28
29
41
41
41
42
43
46
46
46
48
48
4 INTRODUCTION TO MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Alarm navigation and fault localization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Path in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Physical link in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
51
53
55
01
050207
ED
DATE
CHANGE NOTE
M.RAGNI ITAVE
V.PORRO ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
1354RM REL.7.2
OPERATORS HANDBOOK
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
1 / 268
56
59
60
61
62
63
64
66
67
71
75
77
78
78
78
78
78
79
80
82
82
82
82
83
83
84
85
87
89
91
91
92
92
93
106
107
107
107
107
111
113
113
113
113
123
124
127
129
130
131
131
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
2 / 268
132
132
132
134
147
147
147
148
149
151
155
155
155
155
156
156
158
159
9 MAINTENANCE TRACING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1 J0 Section Trace Identifier Set / Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.1 J0 Trace Identifier Set/Modify Virtual to real NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.2 J0 Trace Identifier Set/Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1.3 J0 Trace Identifier Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 J1/J2 Trace Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 Path Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.1 Send Trace Identifier Definition/Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.2 Reading Received Trace Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 Tandem Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.1 Tandem Connection Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.2 Tandem Connection display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.3 Tandem Connection Implement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.4 TCT/TCM deImplement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.5 TCT/TCM global automatic deimplementation ( upon path/trail deimplement ) . . . . . . .
9.5 Manual remove of TCTs and TCMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6 Monitoring function (POM) on intermediate points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.7 Loopback on PDH port / NAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.8 Loopback commands on CTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.9 Craft Terminal Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
161
161
161
161
166
167
171
171
174
175
175
182
185
186
187
187
189
193
196
198
10 PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1 SNCP path layer switch management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 Multiplex Section Layer switch management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.1 Automatic Protection Switch in 2fiber MSSPRING . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.2 Squelching in case of isolated nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.3 MSSPRING Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2.4 Provisioning of the APS Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3 Management of switches at RM interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.1 Display of the Protection blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.2 4F NPE RING Switch Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
199
199
204
204
209
210
212
218
219
221
11 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 Creating the Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
223
223
225
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
3 / 268
229
233
237
239
240
244
247
249
249
250
250
251
253
254
255
256
259
260
260
260
260
261
262
262
263
264
12 LOGGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
265
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
4 / 268
ED
01
15
16
17
17
20
21
22
23
24
25
26
27
28
47
52
52
53
53
54
54
55
55
56
57
58
58
59
59
60
61
62
62
63
64
64
65
65
91
92
93
94
95
95
96
96
97
98
99
99
99
SC.4:MAINTENANCE
3AL 61348 AA AA
268
5 / 268
ED
01
100
101
102
103
104
105
106
108
109
109
116
117
117
118
124
124
125
127
128
128
129
129
130
130
130
131
131
132
132
132
135
136
137
138
139
140
141
142
143
144
145
146
146
149
149
150
151
152
153
153
154
154
162
163
SC.4:MAINTENANCE
3AL 61348 AA AA
268
6 / 268
ED
01
164
165
167
168
169
172
173
174
178
179
180
180
181
182
183
183
184
184
185
187
190
191
192
193
194
195
196
197
199
201
202
202
203
204
205
205
206
208
209
211
213
219
219
223
225
227
228
229
230
231
231
232
234
234
SC.4:MAINTENANCE
3AL 61348 AA AA
268
7 / 268
ED
01
235
236
237
239
239
239
241
242
242
243
245
246
246
247
248
252
253
254
256
257
258
263
265
267
SC.4:MAINTENANCE
3AL 61348 AA AA
268
8 / 268
1 INTRODUCTION
1.1 Purpose of the document
The aim of this document is to describe the operations related to the maintenance of the protection network
controlled by the 1354RM.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
9 / 268
Alarm Enabling/Disabling
ASAP
Alarm Propagation
DIAGNOSTICS
Alarm Navigation
Diagnostic
JoinSplit trail
NPE Diagnostic
MAINTENANCE TRACING
POM
TANDEM
SECTION TRACE
PATH TRACE
LOOPBACK
PROTECTION MANAGEMENT
ED
2F MSSPRING
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
10 / 268
PERFORMANCE MONITORING
Performance Monitoring
Create Measure
PMPT Attributes
Measure Activation/Stop/Consistency
Measure Merging
PM data Display
pmNE
PM Archive
Archive Session
LOGGER
ED
Logger
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
11 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
12 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2 FAULT MANAGEMENT
Alarm messages on elementary objects (nap, cap, ctp, port, mstp) are received from EML, processed and
propagated to the affected objects.
These alarms are propagated to the following objects:
a)
b)
Alarms are generated on paths, Physical Connections, Trails (both HO and MS).
Elementary Alarms are received from EML layer and processed by RM in order to determine the RM object
to be marked as faulty ( RM Object Impacted ). RM provides for the impacted object the Alarm Severity,
the Operational State and the Probable Cause.
SENIM and TSDIM are the protocols, respectively used for QB3* and QB3 equipments, which describe
the EML to NML communication.
Elementary Alarms are described in the documentation of the Network Elements and in the documentation
of the EML NE.
N.B.
Transport Failure means that the path is not working endtoend. The managed domain could
be not interested to this alarm if it is not interested to the endtoend service. In this case, this
alarm can be squelched using an appropriate ASAP.
N.B.
Transport Incoming Failure means that a failure is entering the managed domain. This alarm
alone does not tell if the endtoend path works or not, it just tells that a wrong signal is entering.
The managed domain could be able to recover to the failure if the path is protected.
N.B.
Transport Outgoing Failure means that the managed domain is providing to the outside at
least one flow that is in error. This alarm does not tell if the endtoend path works or not. The
endtoend path could be protected outside the managed domain in such a way that the failure
can be recovered.
N.B.
Only when the path is not working endtoend, the operational state of the path itself is set to
disable.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
13 / 268
Alarms can be enabled or disabled only for TSDIM Network Elements. For QB3* Network Elements only
the propagation of the selected alarms can be enabled / disabled at RM level.
2.2.1 Q3 Alarm Enabling/Disabling
Q3 alarms can be enabled/disabled on the involved Network Element for a certain path.
SEQUENCE
a)
On path creation
1)
2)
If the user, when creating the path, selects Alarm Enabling Rule: Manual, for this Path it will be
possible to enable / disable the involved alarms ( from the Path List: menu Actions: Alarms:
Configuration: enable/disable for Client or Transport.
b)
After path creation, from the Path List the user can modify the Client/Transport alarm enabling rule
by selecting the menu Actions: Alarms: Configuration: Client/Transport Enable/Disable rule, as in the
case of path creation.
c)
A dialog box is presented, which allows the enabling rule selection by means of a dictionary.
Alarms on PDH ports, NAPs, boundary CTPs are enabled if the Client/Transport ( Q3 only) Alarm
Enabling rule= on Implementation.
d)
To verify the successful change of this values the user can issue a Show/Set Attributes on the
selected path. See Figure 1.
N.B.
N.B.
from the HO Trail List the user can modify the Transport alarm enabling rule by selecting the
menu Actions: Alarms: Configuration: Transport Enable/Disable.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
14 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
15 / 268
This includes the ability of RM to setup alarm propagation rules other than the default ones defined for
physical connections related to virtual elements or based on Line Systems / Radio Links. By default AIS
and UPA on CTPs are never received by RM and this prevents a correct alarm from being propagated on
not terminated paths.
To enable the UPA alarm you can enter the Alarm enabling: LOP,EXBER,UPA command on the selected
CAP. See Figure 2.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
16 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
17 / 268
The operator can select a PDH port and execute the command to enable or disable the frame supervision.
The command is available on 1641SX (managed by WX 1.7.1) on configurable 140, 34, 2 Mbit/s PDH
ports.
By default the frame supervision alarm and the consequent action (AIS) are disabled.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
18 / 268
This feature allows enabling and disabling frame supervision on bulk or structured PDH flows.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
19 / 268
RM Object Severity is the RM Object ALARMSTATUS field value, which depends on the correlated ASAP
(Alarm Severity Assignement Profile) .
ASAP is managed for Physical Connections, MSTrails, HOTrails, paths.
The main operations relevant to ASAP are LIST, CREATE, CORRELATE and MODIFY.
2.3.1 ASAP list
The ASAP class is inserted under the Network Domain. From the browser the operator points with the
mouse to the Network Domain, issuing Search: Related Items: Alarm Profiles . The list of the current
profiles is displayed. See Figure 5. as an example.
N.B.
ED
A default ASAP is available; when a path, a trail or a physical connection is created, the default
ASAP is assigned.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
20 / 268
The user can create new ASAPs. The command is also available at the user interface from the path,
trail or physical connection views. The sequence is as follows:
1)
From the browser point with the mouse to the Network Domain and issue the command Alarm:
Create Alarm Profile. The ASAP Creation dialog box is displayed. See Figure 6.
2)
Enter via keyboard the ASAP userlabel and assign the suitable severity to the relevant probable
cause/s. Click on button Create to confirm the creation.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
21 / 268
A correlation action is available in order to assign a new ASAP to relevant objects. The command
is also available at the user interface from the path, trail or physical connection views. One of the
possible sequences is as follows:
1)
Select the path/paths from path list and select Actions: Alarm: Management... as indicated in
the window shown in Figure 7. Figure 8. shows an other example. The object correlation to an
alarm profile dialog box is displayed ( See Figure 9. on page 24 ).
This dialog box contains
also the ASAP create button. See above paragraph 2.3.2 on page 21.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
22 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
23 / 268
REFRESH
END POINT LIST
ASAP LIST
EQPT ALARM
ENABLE/DISABLE
The Alarm profile list window is presented ( see Figure 10. on page 25).
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
24 / 268
3)
ED
01
Select the involved profile and click on button Apply. The selected ASAP icon is displayed in
the Correlate ASAP dialog box, as per Figure 11. Click on Next button to continue.
SC.4:MAINTENANCE
3AL 61348 AA AA
268
25 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
26 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Monitored (the detected defects are reported. This is achieved using an ASAP enabling the reporting).
Auto: the port is not monitored but waiting to go to the monitored state (provided the ASAP is different
than no alarm). The trigger to go from auto to monitored state is the first detection of the signal (i.e. the
clearing of the LOS defect) or a command from the NMS (e.g. RM).
The Auto state is initialized by means of a NMS command.
4)
ED
01
27 / 268
The user can modify a profile simply issuing a Show/Set Attributes of the profile. See Figure 13.
By default this alarm is deactivated since the default ASAP sets it to notAlarmed.
To activate it, a new ASAP has to be created and correlated to the involved path.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
28 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
29 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
30 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
31 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
32 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
33 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
34 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
35 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
36 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
37 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
38 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
39 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
40 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
SEC Administration
secim process, which is the agent of the Security Subsystem and keep all the informations related
to the users and the system. Secim process is running only on 1354RMIM.
lss process, which is a kind of gate for applications related to user Security profile. One lss process
is instantiated for each workstation/server belonging to the 1354RM system (1 for each presentation
and each IM).
These permanent processes are configured to automatically run after the installation.
The SEC integration on 1354RM, as a first step, is intended only for the integration of Security
Management within AS (Alarm Surveillance). This means that each 1354RM operator using AS is able
to view/manage only alarms coming from Network resources that it can manage.
In order to have inside SEC Subsystem all the informations concerning Security, SEC is also integrated
in SMF, in order to get informations related to new users, user removal, and initiator management .
Moreover the integration of SEC in SMF is also related to the Backup operation. Each time a new Operator
backup is performed also SEC database is backuped.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
41 / 268
SEC Subsystem is provided with a default customization for which on an RM is automatically configured
to run secim process if RMIM and lss process for each kind of RM (IM|US.
The default configurations are put in the directory /usr/sec/1354RM_<NTWDOMAIN>.
In order to distinguish 1354RM SEC processes from the 1353SH ones the RM processes are called
<process_name>_1354RM_<NTWDOMAIN>.
The SEC configuration is also related to the automatic start of SEC process: in the /etc/inittab file is inserted
1
line
for
each
permanent
SEC
process.
This
line
invokes
the
script
run_SECIM|LSS_1354RM_<NTWDOMAIN> that checks for SEC abilitation to run and launch the
secim|lss_1354RM_<NTWDOMAIN> process. The automatic start of SEC processes is set on runlevel
4 that is the 1354RM runlevel default. No checks are performed on the 1354RM effective runlevel (it
is supposed to be 4).
During Operator Backup and Restore the SEC subsystem is stopped in order to add to the Operator
Informations also Informations related to SEC. The actions related to SEC start and stop are automatically
launched by SMF.
If some problem occurs during SMF>Operator Administration and SEC DB is not updated by the changes
done on RM through the SMF, it is possible to launch the script as snml user :
/usr/sec/integration/script/alignsecdb
This procedure starts from the last successful SEC command and alignes the SEC DB to the actual RM
Security definitions.
If at login time the user is alerted by the Message Box:
Security for 1354RM_<NTWDOMAIN> is not activated.
Please contact your System
Administrator, the problem is that the user is not defined in the SEC DB, or the SEC Subsystem has been
stopped (Restore proc.) or internal error.
N.B.: If the Message doesnt say 1354RM it is belonging to the SEC installed for SH
RESTRICTIONS
SEC 5.0 doesnt manage the scheduling time. This means that if an user has a scheduled rule this rule
is applied everytime. This limitation is not due to the integration level but to the fact that SEC 5.0 doesnt
support it.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
42 / 268
Depending on 1354RM user definitions the following AS Access Rights are granted:
Where:
AS Access Rights means the AS accessability in terms of AS Administration:
ADMIN: Users can invoke AS Administration and Synchronization
VIEW: Users can invoke AS Synchronization but cannot interact with AS Administration functionalities
Alarm Access Rights shows the Alarm accessability rules that are allowed to user:
MGT: Users that have this capability, if allowed by the NAD Rule (see below), can manage accessible
alarms ( acknowledgement)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
43 / 268
Where:
Alarm AccessType shows the alarm accessibility
MGT means that user have the possibility to Acknowledge alarms (ManaGemenT)
RO means that user can only access alarms in a view mode (ReadOnly)
The MGT Alarm Accessability is granted if allowed by the System Profile (previous table) otherwise (for
LookOnly users) is set to RO.
X show which alarm types that can be accessed by user with the corresponding NAD Rule associated
X* show alarm types (only marked with user NAD) that can be accessed by user with the corresponding
NAD Rule associated
In order to provide a flexible way to configure AS Access on Alarm the configuration file
/usr/snml/conf/sec/1354RM_Ruler is provided.
This file drives the user Access Rights definition in the SECDB and have to be changed before the SEC
installation in order to keep coherent user creations.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
44 / 268
In particular in order to give to LookOnly users the possibility to manage all the Alarms without keeping
into account the RM Rule change the line:
System_Profile
:
LookOnly
ASHISTUSM_FAD@AsHistoricalUsm :
ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,
as follows:
System_Profile
:
LookOnly
:ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm,
ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm, ASHISTUSM_FAD@AsHistoricalUsm
On the other side, if the LookOnly users Accessability have to be extended to manage alarms depending
on 1354RM Access Rules (second table), change the line:
System_Profile
:
LookOnly
ASHISTUSM_FAD@AsHistoricalUsm :
ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,
as follows:
System_Profile
:
LookOnly
:
ASCURUSM_ALARM_VIEW_FAD@AsCurrentUsm,
ASHISTUSM_FAD@AsHistoricalUsm : ASCURUSM_ALARM_MANAGER_FAD@AsCurrentUsm
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
45 / 268
b)
c)
Point with the mouse at the Network Domain and issue the command Alarm: Create Alarm Profile.
d)
e)
Change to Indeterminate the severity associated to all the proposed probable causes.
f)
The path has been created with Implementation Rule = User (default) and Propagation Rule = When
Implemented (default).
b)
As soon as the path is created a new window is opened reporting the path icon with its Naps (Naps
View). Click on Alarm icon making available all the icons relevant for alarm management.
c)
d)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
46 / 268
If in the ASAP space the Indet_Alarm_Profile is already present go to step h). (N.B. the ASAP
possibly provided is not the ASAP currently associated to the path, but it is the last referred ASAP).
f)
Click on Alarm Profile list button; the list of the available ASAP is provided.
g)
h)
Click on Next button, then on Finish button. At this point the path is correlated to the relevant ASAP.
i)
From this point in time on alarms are reported to the path and visible by means of 1354RM USM, but no
alarm on this path is reported to 1330AS. Tests can be performed on the path without affecting
maintenance people.
b)
c)
d)
Click on Alarm Profile list button; the list of the available ASAP is provided.
e)
f)
Click on Next button, then on Finish button. At this point the path is correlated to the relevant ASAP.
g)
At this point the path is correlated to the default ASAP. Since this point in time alarm on the path(s)
are reported also to 1330AS.
h)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
47 / 268
a)
Setup the trail setting Setup Rule = User (N.B. Default value is Automatic).
b)
As soon as the trail is defined a new window is open (Paths in Trail View).
c)
Open the popup menu on the trail icon (pressing right button of the mouse) and select the command
Alarms: Management... A new window is open (correlation wizard).
d)
If the Indet_Alarm_Profile is already present within the correlation window go to step g).
e)
Click on Alarm Profile list button; the list of the available ASAP is provided.
f)
g)
Click on Finish button. At this point the trail is correlated to the relevant ASAP .
h)
i)
There is no explicit commissioning on HOTrail. The scope of this phase is to cause the trail to report
alarms to 1330AS.
b)
On the Trail list window (possibly filtered on HOTrail) select the relevant trail(s).
c)
d)
e)
If in the ASAP space the default ASAP is already present click on Next button and go to h).
f)
Click on Alarm Profile list icon; the list of the available ASAP is provided.
g)
Select the default ASAP and click on Next button. The ASAP icon is inserted into the correlation
window.
h)
On the correlation window click on the icon Finish (the same as before). At this point the trail(s)
is(are) correlated to the default ASAP. From this point in time on alarms on trail(s) are reported also
to 1330AS.
Activate the Physical Connection; this action causes that alarms possibly present on it are
immediately reported to 1330AS too.
b)
c)
From the popup menu associated to the Physical Connection (on browser) select the command
Configuration: Implement to create the associated MSTrail; this action causes that alarms possibly
present on the MSTrail are immediately reported to 1330AS too.
The Physical connection implementation creates the MSTrail(s)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
48 / 268
d)
From the popup menu associated to the Physical Connection select the command Display: All
Related Item.
e)
f)
Press No filter button; the associated MSTrail is provided below the Physical connection.
g)
From the popup menu associated to the Physical connection select the command Alarm:
Management; a new window is open (correlation window).
h)
i)
Click on Alarm Profile list button; the list of the available ASAP is provided )
j)
Select the Indet_Alarm_Profile ASAP and click on the icon Next. The ASAP icon is inserted into the
correlation window
k)
On the correlation window click on Finish button . At this point both the Physical Connection and the
MSTrail are correlated to the relevant ASAP. Alarm possibly sent to 1330AS are automatically
cleared (but must be acknowledged by operator to make them disappear).
l)
command
m ) On the correlation window click on the icon Start correlating all the specified objects . At this point
both the Physical Connection and the MSTrail are correlated to the relevant ASAP. Alarm possibly
sent to 1330AS are automatically cleared (but must be acknowledged by operator to make them
disappear).
3.2.4.2 Physical Link/MSTrail commissioning
There is no explicit commissioning of these entities. The mean of this phase is to cause both Physical Link
and MSTrail to report alarms to 1330AS.
a)
b)
c)
d)
e)
f)
g)
h)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
49 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
50 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
4 INTRODUCTION TO MAINTENANCE
Maintenance operations consist of several functions that have to be executed following failures on the
network.
Note that the protection network comprises:
The maintenance operations inherent to the Routers and Bridges are described in the documentation of
the Routers and Bridges.
A1330AS application.
Notice that from 1354RM Rel.5.2.B on, alarms reported at 1330AS application are ONLY those
affecting the resources managed by the actually logged operator. This mainly applies to VPN
operators.
the browser
The navigation from the Counter summary window is the first level maintenance procedure.
This procedure which is described in the following, applies to each row of the Counter summary window.
a)
ED
From the Counter summary window open the Alarm sublist clicking twice on the relevant row of the
Counter summary window. As an alternative select the row and issue the Sublist: Open pulldown
menu item. See Figure 15.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
51 / 268
The relevant Alarm sublist is presented. Figure 16. shows an example of Physical Connection Alarm
sublist.
b)
ED
Select the alarm from the sublist and navigate it by selecting the Navigation: External Application:
1354RM pulldown menu item.( See Figure 17. ). A confirmation dialog box appears. Click on OK
to confirm.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
52 / 268
For the Path object the Nap view window and relative navigation window is presented:
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
53 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
54 / 268
For the Physical connection object the physical connection structure window is presented:
Alarmed objects are marked by an alarm icon. By clicking on this icon a window is presented, which
gives details on the selected alarm. See Figure 22.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
55 / 268
For the HOtrail object the path in trail window and the relevant navigation window is presented:
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
56 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
57 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
58 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
For the MStrail object the physical connection structure and relative navigation window is presented:
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
59 / 268
Alarmed objects are marked by an alarm icon. By clicking on this icon, the Alarms details window is
displayed. See Figure 29.
Fro the OMS trail alarm sublist select the alarm and issue the navigation command. The OMS trail
structure window is presented.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
60 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
61 / 268
4.1.7 EML
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
62 / 268
From the Client path alarm sublist select the alarm and open the navigation. The relevant client path
routing view is displayed. See below figure.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
63 / 268
4.1.9 NE
In the following is presented the Alarm processing sublist:
For Alarm processing (NE object), only the navigated object is presented in the browser window.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
64 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
65 / 268
This paragraph describes the diagnostic procedures to be executed for the main RM objects in case of
malfunction.
path
trail
EML Domain
NE
Physical Connection
SDH Port
Subnetwork
Node
Payload
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
66 / 268
The Path Alarm Status is Cleared if the path operational status is Enabled ( InService ), this
implies that a path using its spare route is not alarmed.
failed to Alllocate
failed to Deallocate
failed to Implement
failed to Deimplement
failed to connect
failed to disconnect
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
67 / 268
CONDITIONS
The path involved is of the broadcast type. The Operator entered an Add Leg
command on the Path involved.
CAUSES
Lack of resources
ACTIONS
The path involved is of the unprotected type. The Operator entered command
Add Protection.
CAUSES
Lack of resources, i.e. the spare resource corresponding to the main one is
not available.
ACTIONS
CAUSES
ACTIONS
CAUSES
The cause may be due to the fact that the path section deimplementation has
failed (leg to be removed).
ACTIONS
After having entered the command, perform an inspection at EML and NE layer
level.
CAUSES
ACTIONS
ED
01
1)
if the command has been entered through the With check option, the
failed attempt to remove the protection may be due to the fact that the path
is utilizing the spare route.
2)
if the command has been entered through the No check option, the failed
attempt to remove the protection is due to the unsuccessful spare route
deimplementation.
In the second case above described, inspect the EML and NE layers.
SC.4:MAINTENANCE
3AL 61348 AA AA
268
68 / 268
CAUSES
Lack of resources.
ACTIONS
NOTE
PATH/TRAIL
ALLOCATION FAILURES
4.2.1.9 Path: Failed to Deallocate
CONDITIONS
CAUSES
ACTIONS
CAUSES
ACTIONS
After having entered the command, inspect at EML and NE layer level.
CAUSES
ACTIONS
After having entered the command, perform an inspection at EML and NE layer
level.
The Operator has previously entered a Set revertive/Set not revertive command
on the SNCP Operation mode attribute.
CAUSES
ACTIONS
After having entered the command, perform an inspection at EML and NE layer
level.
The operation has been automatically launched by the system which aligns the
paths and trails whose attribute is SNCP status=unknown. It can be launched
in a manual mode by the Operator via command Synchronize Switch on
logically protected Path/trail/connInTopol.
CAUSES
ACTIONS
1)
2)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
69 / 268
CONDITIONS
CAUSES
ACTIONS
After having entered the command, perform an inspection at EML and NE layer
level.
CONDITIONS
HO trail join
HO trail split
HO trail connect/disconnect
path connect/disconnect
CAUSES
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
70 / 268
Alarm status
Working status
failed to Alllocate
failed to Deallocate
failed to Implement
failed to Deimplement
failed to configure
failed to Remove
failed to connect
failed to disconnect
failed to split
failed to join
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
71 / 268
CONDITIONS
The trail involved is of the unprotected type. The Operator entered command
Add Protection.
CAUSES
Lack of resources, i.e. the spare resource corresponding to the main one is
not available.
ACTIONS
CAUSES
ACTIONS
CAUSES
ACTIONS
1)
if the command has been entered through the With check option, the
failed attempt to remove the protection may be due to the fact that the trail
is utilizing the spare route.
2)
if the command has been entered through the No check option, the failed
attempt to remove the protection is due to the unsuccessful spare route
deimplementation.
In the second case above described, inspect the EML and NE layers.
CAUSES
Lack of resources.
ACTIONS
NOTE
PATH/TRAIL
ALLOCATION FAILURES
CAUSES
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
72 / 268
CAUSES
ACTIONS
After having entered the command, inspect at EML and NE layer level.
CAUSES
ACTIONS
After having entered the command, perform an inspection at EML and NE layer
level.
The Operator has previously entered a Set revertive/Set not revertive command
on the SNCP Operation mode attribute.
CAUSES
ACTIONS
After having entered the command, perform an inspection at EML and NE layer
level.
The operation has been automatically launched by the system which aligns the
paths and trails whose attribute is SNCP status=unknown. It can be launched
in a manual mode by the Operator via command Synchronize Switch on
logically protected Path/trail/connInTopol.
CAUSES
ACTIONS
1)
2)
CAUSES
ACTIONS
After having entered the command, perform an inspection at EML and NE layer
level.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
73 / 268
CAUSES
1)
2)
3)
1)
2)
3)
ACTIONS
CAUSES
ACTIONS
CAUSES
2)
ACTIONS
After having entered the command, perform an inspection at EML and NE layer
level.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
74 / 268
CONDITIONS
Alarms Aligned
Alarms alignment. It can be: Normal, Failed, In progress. This attribute reflects the consequences
of the Synchronize command launched by the Operator.
CAUSES
1)
2)
3)
TCPIP problems
1)
2)
Restart EML
3)
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
75 / 268
CONDITIONS
From Browser the attribute EML Alarms Aligned is false / the attribute EML
Alarms Alignment is Failed / the attribute EML Domain Alignment is Failed.
CAUSES
ACTIONS
ED
01
1)
2)
SC.4:MAINTENANCE
3AL 61348 AA AA
268
76 / 268
4.2.4 NE Diagnostic
Alarm status
Not aligned.
Failed to align
Consistency Mismatch
NE unreachable.
Fail to Disable
Fail to Enable
NE DB modified by CT. ( for TSDIM ONLY). The CT has been automatically enabled because of
isolation problem and some modifications have been made by the CT operator.
neNotEmlAligned_auditfailed
neNotEmlAligned_misaligned
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
77 / 268
CONDITIONS
CAUSES
ACTIONS
CAUSES
ACTIONS
CAUSES
ACTIONS
Inspect the browser Error Log and eventually execute a consistency download:
( i.e. global) toward the NE
NOTICE THAT FOR TSD_IM NE THE RUN LEVEL CHANGE TO EXECUTE THE
CONSISTENCY DOWNLOAD IS NOT REQUIRED .
CAUSES
The NE did not answer following a certain operation executed by RM. ( E.g. an
operation on a path, trail,...). The polling toward the NE is automatically started
and an automatic download is then executed.
ACTIONS
Verify, by means of the Error Log the last operation executed on the involved
connectivity object of the NE.
CAUSES
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
78 / 268
CONDITIONS
CAUSES
1)
2)
3)
TCPIP problems
1)
2)
Restart EML
3)
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
79 / 268
Failed to Configure
Failed to Implement
Failed to Remove
All the object statuses, the description of which contains suffix ing are of the workinprogress type and
as a consequence are temporary.
4.2.11.3 PhysCon Failed to Configure
CONDITIONS
The working state is Fail to Configure. The user has previously started to modify
the payload.
CAUSES
1)
2)
3)
1)
2)
3)
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
80 / 268
CONDITIONS
CAUSES
1)
2)
Communication error
1)
2)
Verify that EML is running and launch again the Physical Connection
Implementation operation.
ACTIONS
CAUSES
1)
2)
Communication error
1)
2)
Verify that EML is running and launch again the Remove operation.
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
81 / 268
The SDH ports are displayed from Browser by utilizing command NE: Display Related Items: SDH Ports.
The attribute involved are
Consistency status ( for SENIM ONLY). The values relevant to diagnostic are:
Not found. The board has been extracted. Objects assigned to RM belong to this board. Verify
alarms on related objects at RM and NM level.
Upload status ( for TSDIM ONLY). The values relevant to diagnostic are:
Not found. The board has been extracted. Objects assigned to RM belong to this board. Verify
alarms on related objects at RM and NM level.
The icon displayed from the browser is distinguished by a bar and there is an
alarm icon near it.
CAUSES
ACTIONS
CAUSES
The board has been extracted. Objects assigned to RM belong to this board.
ACTIONS
CAUSES
ACTIONS
CAUSES
The board has been extracted. Objects assigned to RM belong to this board.
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
82 / 268
CAUSES
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
83 / 268
failed to Implement
failed to Remove
CAUSES
ACTIONS
After having entered the command perform an inspection at EML and NE layer
level.
CAUSES
ACTIONS
After having entered the command perform an inspection at EML and NE layer
level.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
84 / 268
The Subnetwork diagnostic concerns the Working status attribute when assumes the following values:
Failed to Configure
Failed to Implement
Failed to Remove
All the statuses whose description contains the ing suffix are of the workinprogress type. Hence the
object is in this status only for a certain period of time.
The Working state is Failed to configure. The user has previously launched
the Payload Modify operation.
CAUSES
1)
2)
3)
1)
2)
3)
ACTIONS
CAUSES
1)
2)
Communication error.
1)
2)
Verify that EML is running and launch again the Implementation operation.
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
85 / 268
CAUSES
1)
2)
Communication error.
1)
2)
Verify that EML is running and launch again the Remove operation.
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
86 / 268
CONDITIONS
CT access status:
Working status:
Failed to Remove
Failed to Reset
Reachable/Not reachable
CAUSES
1)
2)
Communication error.
1)
2)
Verify that EML is running and launch again the Remove operation.
ACTIONS
CAUSES
1)
2)
Communication error.
1)
2)
Verify that EML is running and launch again the Implementation operation.
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
87 / 268
CAUSES
1)
2)
Communication error.
1)
2)
Verify that EML is running and launch again the Implementation operation.
ACTIONS
CAUSES
1)
2)
3)
TCPIP problems
1)
2)
Restart EML
3)
ACTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
88 / 268
CONDITIONS
PhysConn
HOlc
HOtrail
The working state of the above listed objects is Normal after the successful completion of the
configuration. The working state can be Fail to Configure for unsuccessful completion.
4.2.21.2 Fail to Configure
CONDITIONS
CAUSES
ACTIONS
Inspect the browser Show additional information to display the cause of the
problem and execute one of the following actions:
ED
01
1)
2)
SC.4:MAINTENANCE
3AL 61348 AA AA
268
89 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
90 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
OBSTACLES AND UNSATISFIED CONSTRAINTS are managed with the following structure:
OBSTACLES. This problem type is described by a problem description which helps in solving
the problem.
For OBSTACLES AND UNSATISFIED CONSTRAINTS Problem description and Constraint List are
presented with the support of a simple graphical representation of the path/trail routing.
The tool usage is described in the following paragraphs.
ALLOCATION FAILURE
OTHER
ERRORS
OBSTACLES AND
UNSATISFIED CONSTRAINTS
UNSATISFIED
OBSTACLES
CONSTRAINTS
OBSTACLES
&
UNSATISFIED
CONSTRAINTS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
91 / 268
Select the involved path/trail and click on the Show Failure Information Tool button. This button
is also present in the path/trail routing view. The Netscape browser application starts and displays
the Netscape Path/Trail allocation failure window. See paragraph 5.2.3
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
92 / 268
In case of Obstacles and Unsatisfied Constraints, the complete netscape view is provided.
SEQUENCE
a)
Select the involved path/trail and click on the Show Failure Information Tool button. This button is
also present in the path/trail routing view. The Netscape browser application starts and displays the
Netscape Path/Trail allocation failure window. See Figure 40. herebelow.
PROBLEM
WINDOW TITLE
SUMMARY
FAILED OBJECT
FRAME
FRAME
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
93 / 268
The Netscape Path/Trail allocation failure window shown in detail in Figure 42. on page 95 .
contains the following frames:
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
failure date
failure time
no. of failed legs ( for broadcast paths only )
PROBLEM TYPE, reference to the html Problem Detail frame. The following cases
are possible:
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
94 / 268
Two columns are displayable: MAIN (problems on the main route) and SPARE (problems
on the spare route, only for protected paths/trail)
Figure 42. Netscape Path Trail allocation failure: problem summary frame.
b)
At this point you can select the problem type, or in case of unsatisfied constraints you can select the
constraint list. See Figure 43. herebelow.
If you click on the Problem Type, reference to the html Problem Detail frame ( named
OBSTACLES and CONSTRAINTS PROBLEMS), the Problem Detail frame view will display the
selected leg. See Figure 46. on page 97.
The Problem Detail frame contains:
header ( upper lefthand side), constituted by:
Leg no. ,i.e. the selected leg number. This field is not present for point to point paths
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
95 / 268
node icon (green triangle) with node name or link connection icon (yellow icon)
with link connection name: node A name node B name AU/TU pointer No.
END 1 name and END 2 name. See Figure 45. on page 96.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
96 / 268
Problem Type ( yellow string which is the html reference to the Path/Trail allocation
failure description window of Figure 47. on page 98.
ED
From the Problem Detail frame of Figure 46. select the problem type. The Path/Trail allocation failure
description window is displayed. See Figure 47. on page 98.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
97 / 268
FRAME
Generic Help on Allocation Failure. See Figure 48. on page 99. It contains a generic
description of the allocation failure.
A Main wiindow reload button is present in this frame,allowing the operator to display the main
window.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
98 / 268
Problem description. See example in Figure 50. herebelow. It contains the detailed problem
description (Title and Explanation) of the problem and suggestions ( Hints ) how to solve the
problem.
Figure 49. Generic Help on allocation failure.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
99 / 268
Infinite Cost
Unsatisfied Constraints
Explanation: One or more of the constraints given to the path/trail cannot be satisfied
Hints: The only way to allocate the path/trail is to remove/modify some constraints
The left hand side frame contains the Problem menu list. Each menu item, if selected, will display its
problem explanation and some hints to solve it.
PROBLEM MENU
Figure 52. and Figure 53. herebelow display an example of protected path allocation failure.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
100 / 268
Explanation: The routing algorithm has found a route which uses a routing link with infinite cost
MAIN ROUTE
SPARE ROUTE
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
101 / 268
SPARE
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
102 / 268
If you click on the Constraint List icon, as per Figure 43. on page 95, the Constrain List is
presented. See Figure 54. on page 103. Per each leg its Constraint List can be displayed in case
of Unsatisfied Constraints.
2)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
103 / 268
title: PROCESSED CONSTRAINTS LIST ( route ), where route is equal to Main or Spare
constraint usage in the main route. The oneway icon means USE while the no entry icon
means NOT USE.
constraint usage in the spare route. The oneway icon means USE while the no entry icon
means NOT USE.
topology used as constraint. It includes the icon and the userlabel of the topological object
An example of interpretation of some rows is given in Figure 56. on page 105
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
104 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
105 / 268
OTHER ERRORS are not described in detail. They indicate errors for which no other information is
provided.
An example of other error display is shown in Figure 57. herebelow.
OTHER ERROR
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
106 / 268
the user specifies the trail to split: RM checks in which nodes of the trail the split can be performed
(i.e. nodes where LO capability is available, nodes not belonging to protected parts of the trail ...) and
prompts to the user the list of these nodes; no other action is accomplished by RM neither in RM MIB
nor in the NEs;
b)
the user selects the splitting node and the operation can be executed.
The LOPaths crossing the splitting Node are modified by adding LO passthrough connection.
The related protection indexes are updated.
The payload structure and the LO connections of the 2 nodes at the end of the involved HO trails are not
modified during the operations: modifications to connections and payload structure are applied only to the
splitting node.
The operation reduces the impacts on the existing traffic: the LOPaths client of the involved HO trails are
disconnected only for the time necessary to perform the operation: only the segment of network between
the end nodes of the involved HO trails is affected.
6.1.2 Join two HOTrails
Two HOTrails entering in a given NE can be joined in order to reduce the LO usage of resources.
all LOpaths using the original HOTrails are crossing with passthrough connections the intermediate NE without LO timeslot interchange.
As a consequence of the operation:
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
107 / 268
The payload structure and the LO connections of the 2 nodes at the end of the involved HO trails are not
modified during the operations: modifications to connections and payload structure are applied only to the
intermediate node.
The operation reduces the impacts on the existing traffic: LOPaths client of the involved HO trails are
disconnected only for the time necessary to perform the operation and only in the segment of network between the end nodes of the involved HO trails.
6.1.2.1 Description of the operations
Both split and join HO Trails are complex operations: they are composed of elementary operations (payload configuration, trail implementation,...), as described in the following state diagram.
JOIN
A
B
C
D
split trail C into A,B
SPLIT
E
implement trail C
F
deconfigure trail C
configure trail C
connect client paths
from 1W to 4 E
H
Figure 58. state diagram
The join trails is an operation that changes the state from A to H, passing through intermediate states.
The split trails is an operation that changes the state from H to A, passing through intermediate states.
The states are described below.
ED
state A (see below): HO trails A and B are implemented and LO configured; some LO LCs (e.g. LC
A and B) and their CTPs are busy because they belong to a path; LO CTPs in the transit node 2 are
connected with pointtopoint connections in topology without timeslot interchange; these connections can be allocated or implemented;
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
108 / 268
NAP
LO CTP
LO CTP
A1
A2
LO LC A
HO trail A
HO LC A
1
W
LO CTP B1
NAP
LO CTP B2
LO LC B
HO trail B
HO LC B1
2
E
HO LC B2
3
E
4
E
state B: HO trails A and B are implemented and LO configured; for all the LO paths that before used
LO LCs A and B:
the connections in topology in node 2 are removed, both on EML and on RM database;
the LO CTPs in node 2 are idle; in nodes 1 and 4 are still busy;
LO CTP A1
HO LC A
1
W
HO trail C
HO LC B1
2
E
NAP
LO CTP B2
LO LC C
HO LC B2
3
E
4
E
in a single step: a new action is defined in order to perform automatically all the activities that join or
split trails (i.e. that move, if successful, from A to H or viceversa);
Join and split trails are completely reversible: if a join trails is interrupted after an action, e.g. in the state
B after the first action, it is possible to go back to previous state, applying the action connect client paths
from 1W to 4E. It is also possible to continue the join trails, applying the same action (i.e. join trails) or
the remaining actions (deconfigure trail A, B, deimplement connections ...).
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
109 / 268
a)
b)
implement trail B;
configure trail B;
connect client paths from 1W to 4E;
to go back, executing the join trails (A, B) or performing the following steps:
1)
2)
3)
4)
The state transitions C D and E F are not symmetrical: the deimplementation is applied to a single connection in topology for each trail (the one in the common node), while the implementation is applied to the
whole trail: this is due to the fact that, in MSSPRING, the implementation could modify the squelching
tables in the connections in topology contained in the other nodes of the same MSSPRING, while the deimplementation of a single connection leaves those squelching tables to the old values.
A report is presented to the user indicating in real time which phase of the operation is in progress and
its result when completed. All the LOPaths impacted by the operation (supported by the involved HO
Trails) are reported too.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
110 / 268
Also when an action is not completed (e.g. it fails, an agent crash occurs, ...), it is always possible to continue or to go back. For example, if during the split trail the implementation of trail B fails leaving this trail
partially implemented, while the trail A has been successfully implemented and configured, it is possible:
In case the Join operation is blocked in the B,C,D statuses, the possible user operations are:
or
the user can try to relaunch the join operation, since the probable reason of the interruption is the
condition of EML/NE not reachable
In case the Join operation is blocked in the E,F,G statuses, the possible user operations are:
the user wants to complete the join operation by manually proceeding (step by step) to H status
or
the user wants to manually revert (step by step) to A status by reissuing the split command
N.B.
In case the Split operation is blocked in the G,F,E statuses, the possible user operations are:
or
the user can try to relaunch the split operation, since the probable reason of the interruption is the
condition of EML/NE not reachable
In case the Split operation is blocked in the D,C,B statuses, the possible user operations are:
the user wants to complete the split operation by manually proceeding (step by step) to A status
or
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
111 / 268
the user wants to manually revert (step by step) to H status by reissuing the join command
Connect/Disconnect commands must be executed from the HO trail/s
N.B.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
112 / 268
Serving nodes: the two nodes that talk to each other on the K1K2 channel, sending their protocol
messages in order to serve their requests. If more than one request is served on the ring, the serving
nodes may be more than two.
Intermediate nodes: the nodes that are not directly interested by the fault.
MSSPRING request (trigger): any kind of valid input to the MSSPRING machine:
equipment/signal failure, signal degrade, external commands, and protocol requests/replies.
protocol request: a protocol message issued by a Tail node toward its peer request node (that may
either be a Tail node or Head node, depending on the nature of the trigger).
protocol reply: a protocol message issued by a Head node back to its peer Tail node to acknowledge
a Tail nodes protocol request.
protocol message: a K1K2 code sent on the K1K2 channel that may either be a protocol request
or protocol reply.
Lockout of Working channels ring (LWR): command that disables the node capability to issue
a ring protocol request of any kind. The node is anyway allowed to issue ring protocol replies. The
command is local, i.e. it is not forwarded to the other nodes through K1K2 channels.
Lockout of Working channels span (LWS): command that disables the node capability to issue
a span protocol request of any kind. The node is allowed to issue span protocol replies. The
command is local, i.e. it is not forwarded to the other nodes through K1K2 channels.
Lockout of Protection channels span (LPS): command that prevents the use of the protection
channels over the addressed span. The command is not local, i.e. it is forwarded through K1K2
channels also to the other nodes that, as a consequence, do not take any action involving the
addressed span.
Routing in Working ( RIW). For 1670SM equipment. The protection route is within the working
capacity
Routing in Protection (RIP). For 1664SM equipment. The protection route is within the protection
capacity
7.1.2 4f MSSpring
The ring can be made up of a maximum of 64 ADMs. 1664SM equipments can build 4Fiber STM16 rings
with Routing in Protection mechanism.
1670SM equipments can build 4Fiber STM64 rings with Routing in Working mechanism.
For Paths and Trails an attribute enables the usage of low priority resources. This attribute is taken into
account during path allocation.
The protection capabilities of the ring are based on the information stored in the Ring Traffic Map and
evaluated by each NE in order to take the appropriate decisions in case of fault.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
113 / 268
In order to avoid misconnections, RM, during implementation phase, sends the update of the ring traffic
maps before the creation of connections, and viceversa, during the deimplementation phase, updates
the maps only after the deletion of connections.
The ring traffic map is not shown to the RM operator, because the same information are provided by the
path/trail route display functionality.
The D&C is performed using protecting resource between Service Nodes while using 1664SM with RIP
mechanism and using working resource between Service Nodes while using 1670SM with RIW
mechanism.
As a consequence of limitations existing on equipment side:
for 1664SM rings D&C on interconnected NPE rings is not always able to survive to double
failures, a failure per ring, (this happens when the primary node of one ring is connected to the
secondary node of the other ring)
7.1.2.1 Path
The attributes relevant to NPE features are:
Server MS protection usage profile: it represents the profile of the MS resources to be used in
allocating the path.
The possible values are:
Normal
ED
01
(default)
For 1664SM rings, the RIP mechanism is used, i.e. when crossing 4 Fibers MSSpring,
the path uses only working (high priority) resources, except for primary and secondary
nodes of the double interconnection with another ring, because these nodes are
characterized by the Drop & Continue protection ( RIP )
as a result, in the segment between service nodes:
if the path is bidirectional (Figure 61. ), the used resource (nodes E, D, H, I) can be
only the protection one: a bidirectional D&C IC on protection is performed in the
primary nodes (D, H);
protection if the signal flows into the service nodes (B, C): a unidirectional D&C IC
on protection is performed in the primary node (B);
working if the signal flows out of the service nodes (E, D): a multipoint connection
is performed in the primary node (E); this allows the user to perform subsequent add
leg operation;
it is possible to use the protection resource instead of the working (nodes E, D), e.g.
forced by a constraint (Figure 63. );
protection if the signal flows into the service nodes (B, C) like in a unidirectional
pointtopoint path: a unidirectional D&C IC on protection is performed in the primary
node;
working if the signal flows out of the service nodes (E, D): a multipoint connection
is performed in the primary node);
SC.4:MAINTENANCE
3AL 61348 AA AA
268
114 / 268
The component of the ring traffic map related to each path and trail is evaluated and sent to all NEs in
the ring.
it is not possible to use the protection resource instead of the working one.
As a result of the previous rules defined for unidirectional and broadcast paths, a
unidirectional pointtopoint path can become broadcast only if the working
resources are used between service nodes (nodes E, D in Figure 64. ).
ED
For 1670SM rings the path uses only working resources ( RIW )
Protection preferred
When crossing a 4 Fibre MSSpring, the path uses protecting (low priority) resources.
If the routing algorithm must use the working resource in one span of the 4F MSspring (e.g.
no free resources in the protection, or a constraint is applied), all working resources are used
in the ring, in order to avoid jumps between working and protection resources (jumps not
foreseen for the management of ring traffic map).
If the path is protected and main and spare routes are crossing the same MSSpring, each route
crosses separately the ring itself since D&C connection are not available for protecting
resources.
As a consequence of this behavior and of the fact that the SNCP connection is not available on
a 4f MSSpring, if the protected HO path is completely inside a 4f MSSpring, the allocation
will always fail.
Protection only
the path uses only protecting (low priority) resources.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
115 / 268
7.1.2.1.1 Trail
Server Ms protection usage profile is added to HO trails (see the description given for paths).
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
working
protection
NPE
F
NPE
N
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
116 / 268
working
protection
SNCP
B
NPE
SNCP
Figure 62. unidirectional protected path (using working resource between nodes E and D)
working
protection
SNCP
B
NPE
C
D
SNCP
Figure 63. unidirectional protected path (using protection resource between nodes E and D)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
117 / 268
working
protection
B
NPE
SNCP
SNCP
An attribute specifies if the Physical Connection is Working (i.e. it connects main ports, involved in a MS
protection mechanism) or Protecting (i.e. it connects spare ports) or Normal (i.e. it connects ports not
involved in any MS protection mechanism.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
118 / 268
Configuration State. It is the state requested at the interface Functional Agent / TSDIM Front End
Processor and can assume the following values:
virtual.
The MSSPRING et topology is only planned inside the RM (i.e. is in the state defined) and
is not established inside the NE (the ring coordinator object is not present in the NE)
active.
The MSSPRING et topology is active in the NE, i.e. it is implemented in RM (see also
Transition State)
Transition State. It describes the transition state of the MSSPRING in the NE during the
configuration phase. The following values are possible:
idle. It is the value corresponding to the value virtual of the Configuration State
defined. The ring has been defined by the action applied on the Protection Manager MOC in
NE: the information on working/protecting east/west msTTPs have been provided to the NEs.
As a result the Ring Coordinator object is created in the NE and all other objects (Ring Map, Ring
Traffic Map or Squelch Table, Ring Protection Group, Ring Protection Units ...) are created and
correlated to the Ring Coordinator. The Ring Coordinator has the status enabled
populated map. The Ring Map has been populated according to the information contained in
the ring map info attribute through the populate action applied to the Ring Coordinator. As a
result, the information describing the map of the nodes inside the ring have been stored both
inside the Ring Map and in the Ring Traffic Map accordingly.
activated. The Ring Coordinator has been activated (activate action). As a result, the protected
msTTPs, unprotected CTPs, working/protecting east/west side have been put in relation
according to the ring type (2/4 fiber with/without extratraffic) and the MSSpring mechanism
is active
The Configuration State attribute active is consistent with the NE status if the 4F protection block
entered the sequence defined, populated map, activated, i.e. if the Ring Coordinator is
activated. In this case the attribute value is activated and the Consistency Status is normal .
node id: it refers to the node id attribute inside the node entity
ring map info: it is a string representing the sequence of node identifiers following the direction
eastwest in the ring. It is used to provide to the NE the information usefull when filling the Ring Map
object (e.g.: x,y,z,w. Starting from the node x and moving to east the found nodes are in the
sequence y, z, w, where x,y,z,w are the identifiers of the nodes).
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
119 / 268
traffic map: the attribute is a sort of token used to apply the alignment of the Ring Traffic Map inside
the NE, according to the info, if any, contained in the AU4 Transport Map, plus the implicit information
that, when the au4(s) or piece(s) of au4(s) are not contained inside the AU4 Transport Map, no
connection has to be present inside the Ring Traffic Map.
West Reliable ( protected ) Resource: it is the id of the reliable msCtpCap on the west main port
East Reliable Resource: it is the id of the reliable msCtpCap on the east main port
West Working Unreliable Resource: it is the id of the unreliable msCtpCap on the west main port
East Working Unreliable Resource: it is the id of the unreliable msCtpCap on the east main port
West Protecting Unrealiable Resource: it is the id of the unreliable msCtpCap on the west spare
port
East Protecting Unreliable Resource: it is the id of the unreliable msCtpCap on the east spare port
Ring WTR (Wait To Restore time): it containes the value to provide to the NE during the MSSpring
provisioning phase.
West Span WTR (Wait To Restore time): it contains the value (west side) to provide to the NE during
the MSSpring provisioning phase.
East Span WTR (Wait To Restore time): it contains the value (east side) to provide to the NE during
the MSSpring provisioning phase.
Current User Command. The attribute indicates the command (none, lockout working west, lockout
working east, west ring force switch...) requested by the RM user.
no command: null
exercise
ED
the WTR has been put together with the possible active commands because, even
if it is not a user command, it can be cleared through a user command as well as the
others.
no command: null
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
120 / 268
exercise
no command: null
exercise
no command: null
exercise
ED
inconsistent code
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
121 / 268
ED
the protection MS on the West / East side of the node is unavailable or locked out (via LPS
only): protUnav
the node is serving an external commandring or failure/degradering that involves its West /
East side, the protection MS on the West / East side is unavailable or locked out: ( ext )
RingProtUnav
thRingExrcRingProtUna the node is serving an exercise command that involves its West /
East side, the protection MS on the West / East side is unavailable or locked out
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
122 / 268
triggers =external commands and/or failure/degrade conditions. The nodes whose triggers are being
served are named served nodes. A served node has at least one trigger served and may have some
pending triggers.
the reaction of the ring to those triggers, namely what triggers are being served, and which ones are
pending. (waiting to be served, either because they are at lower priority, or there are specific protocol
rules). The nodes that have no triggers or only pending ones are called intermediate nodes.
N.B.
The protection status reporting screen is neither intended to display the status of the K1K2
signaling, nor the status of the physical switches. With the 2F MS SP ring application, the
bridge&switch at multiplex section level always occurs at served nodes, whereas protection
channels passthrough is made by intermediate nodes. With the 4F MS SPring application,
bridge&switch at AU4 level may take place at whatsoever node, depending on traffic
distribution.
It should be noted that according to the MSSPring protocol rules any of the following scenarios may occur:
no trigger is present, no protocol request (namely, K1K2 code other than noRequest) is signaled on
the ring;
N (>1) triggers are present, N protocol requests are signaled, only 1 is served (higher priority);
N triggers are present, N protocol requests are signaled and served (same priority);
N triggers are present, N protocol requests are signaled, none is served (same priority, but not
allowed to coexist).
M (>1) triggers are present, N (<M) protocol requests are signaled, only 1 is served (higher priority);
M triggers are present, N (<M) protocol requests are signaled and served (same priority);
M triggers are present, N (<M) protocol requests are signaled, none is served (same priority, but not
allowed to coexist).
(1) The Lockout of Working channels commands make the scenario even more complicated, as those
commands are not signaled but are actually served, in the sense that they influence the behavior of
the node to which they are addressed.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
123 / 268
The node icon always reports the actual condition of the node in terms of the protocol role the node
is playing to react to the MSSPRING triggers, and the external commands being stored to the
node. If the condition required by the RM and the actual node condition do not match, the not
aligned indication is displayed along with the node icon.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
124 / 268
virtual
topology implementation
topology deimplementation
MSSPRING activation
enabled
active
MSSPRING deactivation
The following table describes the rationale that drives the display of the various icons according to the
ConfigurationState state diagram (see Figure 67. ).
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
125 / 268
node condition
displayed icons
operation
virtual
active
active
node unreachable
enabled
(not managed in this
version release)
enabled
enabled
(not managed in this
version release)
active
active
active
node icon +
other icons on top to
show protocol role and
stored commands
active
enabled
node icon +
MidProtocolRole =
standby icon on top +
not aligned indication
The node icon is a rectangle plus arrows that represent the fiber optics to connect the nodes to each other.
Plus, the node icon features a number of rectangles (see Figure 68. ) to hold icons associated to all the
attributes of the MSSPRingProtectionBlock MOC:
the icon for the FailureOfProtocol to be placed outside the node icon next the bottom left and
righthand corner;
The reason for providing each node icon with 6 icons for the local commands comes from the combinations
of active and pending commands that are allowed to coexist at each node.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
126 / 268
ConfigurationState
working fibers
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
127 / 268
intemediate
unknown
end
standby
idle
no icon
GREEN
(not supported)
GREEN
null
tailHeadRing
(interruption Ring)
tailHeadSpan
(interruption Span)
protUnav
(EXT) thRingProtUnav
no icon
RED
tailHeadExrcRing
RED
RED
RED
thExRingProtUnav
BLUE
BLUE
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
128 / 268
tailHeadRing
null
tailHeadSpan
protUnav
thRingProtUnav
no icon
RED
tailHeadExrcRing
RED
RED
RED
thExRingProtUnav
BLUE
BLUE
null
defaultKBytes
improperCode
nodeIdMismatch
RED
RED
RED
inconsistentCode
no icon
RED
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
129 / 268
null
exercise
wtr ring
no icon
YELLOW
RED
CIAN
wtr span
exercise
null
no icon
YELLOW
CIAN
RED
wtr span
exercise
null
no icon
YELLOW
CIAN
RED
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
130 / 268
null
exercise
no icon
YELLOW
CIAN
RED
exercise
null
no icon
YELLOW
RED
CIAN
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
131 / 268
null
exercise
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
no icon
YELLOW
RED
CIAN
null
no icon
null
no icon
LPS (Lockout Protection Span), SFP (Signal Fail Protection), LOWR (Lockout Working Ring),
LOWS (Lockout Working Span); LOWR, LOWS LPS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
132 / 268
EXER (Exercise)
EXCEPTIONS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
133 / 268
7.2.10 Scenarios
First execute the repair of the main span. HP traffic reverts to the main span while LP traffic still is
lost.
1)
b)
Click on the alarm icon displayed on the main span. The alarm detail window is presented, giving
the information needed to repair the span.
First execute the repair of the spare span, so moving to the Span switch scenario.The LP traffic not
overlapping HP traffic is restored.
1)
Click on the alarm icon displayed on the spare span. The alarm detail window is presented,
giving the information needed to repair the span.
The scenario after the repair of the affected spans is described at paragraph 7.2.10.2.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
134 / 268
This paragraph describes various ring scenarios , as shown in the graphical interface.
Alarm icon
Node Condition=intermediate
(not directly affected by the fault)
Node Condition=End
Figure 81. Bidirectional Signal Fail / Ring
7.2.10.2 Bidirectional Signal Fail / Ring cleared .WTR
DESCRIPTION
The bidirectional Signal Fail / Ring on AB span is cleared as a consequence of a repair action. The last
node detecting the signal failure clear starts the WTR ( wait to restore time )
SERVED REQUESTS DISPLAY
Bidirectional Signal Fail / Ring on AB span (indicated by RING INTERRUPTION (tailHeadRing) icons
on AB span) is still displayed.
The east ring active condition icon reports WTRrunning.
OPERATION
All nodes dropping/inserting HP traffic that was affected by the failure still recover it on protection channels
away from the failure.
All LPtraffic paths whose channels are needed to recover HP traffic are still preempted.
Node A (the last detecting the signal failure clear) is running
REPAIR ACTION
The WTR timer may be forced to expiration by RM via Clear WTR command. ( not implemented in this
version )
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
135 / 268
WTR
The scenario after the repair of one of the two faults is described at paragraph 7.2.10.1.
It is suggested the repair of the main span first.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
136 / 268
Alarm icon
Node Condition=Idle
All LPtraffic paths whose channels are needed to recover HP traffic are preempted.
REPAIR ACTION
This command is used in the Add/Remove Node procedures.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
137 / 268
B
Forced Switch Ring East
HP traffic that is traversing both the involved spans is recovered on protection channels away from those
spans.
HP traffic that is traversing one of the involved spans is not recovered.
All LP paths whose channels are needed to recover HP traffic are preempted.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
138 / 268
REPAIR ACTION
After the completion of the local maintenance condition of node B, enter the Release Forced Switch / Ring
on nodes A and C.
C
Forced Switch Ring West
Figure 85. Double Forced Switch / Ring to different nodes, node isolated
7.2.10.6 Double signal Fail / ring, node isolated
DESCRIPTION
Bidirectional Signal Fail / Ring on AB span.
Bidirectional Signal Fail / Ring on BC span.
SERVED REQUESTS DISPLAY
Bidirectional Signal Fail / Ring on AB span (indicated by tailHeadRing icons facing both the AB span).
Bidirectional Signal Fail / Ring on BC span (indicated by tailHeadRing icons facing both the BC span).
OPERATION
Node B is isolated, as the two Force Ring commands partition the ring into two segment, [B] alone and
[C, D, A].
HP traffic that is traversing both the involved spans is recovered on protection channels away from those
spans.
HP traffic that is traversing one of the involved spans is not recovered.
All LP paths whose channels are needed to recover HP traffic are preempted.
REPAIR ACTION
a)
ED
Execute the repair of the main span. HP traffic reverts to the main span while LP traffic still is lost.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
139 / 268
Click on the alarm icon displayed on the main span. The alarm detail window is presented, giving
the information needed to repair the span.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
1)
After the completion of AB main span local maintenance the Release Switch Span West can be entered.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
140 / 268
Span Switch
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
141 / 268
Figure 88. Signal Fail / Ring pending, Forced Switch / Ring pending
7.2.10.9 Double Fault/ Ring pending
DESCRIPTION
Bidirectional Signal Fail on Protection on BA span.
Bidirectional Signal Fail / Ring on DE span.
It is a double fault service affecting. The fault between A and B nodes ( SFP ) has priority greater than
the fault between C and D nodes ( SFR)
SERVED REQUESTS DISPLAY
Bidirectional Signal Fail on Protection (indicated by protection unavailable icons facing the AB span)
OPERATION
Bidirectional Signal Fail / Ring is pending (it is lower priority than the Signal Fail /Span), affected traffic
is not recovered, all LPtraffic remains.
Bidirectional Signal Fail on Protection prevents the use of the protection channels on the AB span.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
142 / 268
ED
01
B
C
D
Protection Unavailable
SC.4:MAINTENANCE
3AL 61348 AA AA
268
143 / 268
DESCRIPTION
A Span Switch Request: Exercise East is issued on node B.
SERVED REQUESTS DISPLAY
East Protocol Role=TailHeadExrcSpan on B node
West Protocol Role=TailHeadExrcSpan on C node
OPERATION
The Exercise command does not affect the traffic carried by the NPE ring
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
144 / 268
The Exercise command does not affect the traffic carried by the NPE ring.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
145 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
146 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Activate the Network Consistency Agent. ( Set Run Level=3 from Monitor application )
b)
Global
PDHPort NAP
SDHPort MStp
at HO/LO level
The option Global causes the execution of all the remaining checks from 2 ) thru 4 ).
The reporting of the operations is performed using multiple messages in order to display the current state
of the ongoing operations (number of not aligned objects, etc...) Otherwise from the Browser the
misaligned objects (tps) can be displayed by selecting the NE and issuing Display: Related items: All
Misaligned Objects.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
147 / 268
The Consistency Download activity verifies the misalignments between EML and NML and alignes EML
data to RM data.
a)
b)
c)
Global
PDHPort NAP
SDHPort MStp
at HO/LO level
Performance Monitoring (Only for Download)
The option Global causes the execution of all the remaining checks 2 ) thru 4 ).
The reporting of the operations is performed using multiple messages in order to display the current state
of the ongoing operations (number of not aligned objects, etc... Otherwise from the Browser the
misaligned objects (tps) can be displayed by selecting the NE and issuing Display: Related items: All
Misaligned Objects.
d)
e)
Execute checks on an eventual EMLNE misalignment. From browser point to the Node icon and
issue Display: Related items: Alarmed Objects, to verify the presence of a Configuration Mismatch
alarm
f)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
148 / 268
MISALIGNMENT INDICATIONS
The following indications of misalignment are perceived by the operator:
DISABLED
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
149 / 268
1)
2)
From the NE list select the misaligned NE and issue Consistency Audit: Global
The consistency report does not include any indication of misalignment, then the misalignment is localized between 1353NM and Network Element.
In addition, the errors are located at NE level, because are traffic affecting.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
150 / 268
From 1353NM map window select the NE and issue: Operations:Supervision: Stop....
2)
At this point the NE is no longer supervised. Execute NE: Supervision: Align down
3)
4)
5)
6)
From the 1354RM map the user can verify that the disalignment ceased
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
151 / 268
From 1353NM select the involved NE and issue Supervision: MIB: Compare
b)
c)
From the Compare dialog box NE1 is misaligned with respect to 1353NM.
d)
ED
7)
8)
From the NE list select the misaligned NE and issue Consistency Audit: Global. The example
which follows reports an example of audit report on connections ( at Lo / Ho )
9)
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
152 / 268
a)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
153 / 268
c)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
154 / 268
Q3 )
The operator is able to specify for TSDIM NEs the download disabled / enabled mode (download enabled
mode is the default condition)
When a NE is in download disabled mode, all changes are buffered in the RM MIB, being not sent
to NE.
Objects in the RM MIB that, as a consequence of the download disable mode, are not aligned with the NE,
are marked with the value of the consistency status attribute (not aligned).
When the download disabled mode is removed and the NE is reachable, RM data are downloaded to NEs.
If the download disabled mode is removed and the NE is not reachable, the operation is rejected.
If problems are detected during the download, the NE is put in isolation mode.
During the downloading activity on a given NE, all concurrent operations requested by RM operator and
involving the same NE are rejected.
8.4.2 Ne isolation detection and recovery (
Q3 )
RM is able to detect not reachable NEs as a consequence both of problems in the EML, in the DCN or
in the NE.
When a NE is in download enabled mode and is not reachable, RM behavior is similar to the one
described for the download disable mode.
Elementary alarms are correlated to the impacted transport entity allowing a better identification of the
transport entity impacted by the isolation problem.
The isolation is detected as a consequence of a failure of an operation addressed to the NE.
The recovery from the isolation is detected by means of a slow polling performed by RM on the isolated
NE.
When an isolated NE is detected as reachable, the download is automatically started.
During downloading activity, the same considerations made for download disable to download enable
transition are applicable.
The OS isolation alarm received by NM and the NM isolation alarm detected by mean of a slow polling
performed by RM are reported as alarms at the RM user interface.
8.4.3 Consistency download management (
Q3 )
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
155 / 268
Mark :
differencies are marked. These differencies will be taken into account and downloaded during the
operations of enabling the download and isolation recovery.
Notify:
differences are marked and wil be not taken into account during the operations of enabling
download or isolation recovery.
The consistency audit is available on the NE, only if the NE is not isolated and the 1354RM is in Download
Disable mode.
8.4.4.1 Consistency audit on objects
Objects impacted by the consistency audit are RM elementary objects like ports, single TPs, subnetwork
connections, ...
8.4.4.2 Download disabled to enabled transition
All current operations on the NE must be completed before serving the transition.
8.4.4.3 Startup / Restart scenario
RM elementary objects are taken into account by layers in a server to client order: physical ports, NAPs,
MSTPs, HOCTPs, HO connections, HOTTPs, LOCTPs, LO connections.
8.4.4.4 Ne reachable to unreachable transition
All the current operations on the NE must be completed considering the NE unreachable even if the state
changes again before the end of the current operations.
8.4.4.5 Download enabled to disabled transistion
All the current operations on the NE must be completed before serving the transition. For these operations
the NE has to be considered as still in download enabled.
8.4.4.5.1 Reporting
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
156 / 268
The operation is available when the NE is not isolated and in download enabled mode. If the
communication is lost during the download, the operator is informed at user interface and the NE is left
in the download enabled mode; when the communication is resumed no automatic restart of the
consistency download is performed.
An object can be not consistent due to the misalignment of one or more attributes. For each attribute the
following information are presented :
object class
user label
attribute: attribute of the object that causes the not consistency
error type: reason of the inconsistency
date
The user label field contains the user label of the object with the following exceptions:
The user can choose, using two different commands, to display a global or a restricted list of the objects.
The global list comprises:
ne
port (sdh)
msCtpCap
msProtBlock4f
ctpho
port (pdh)
nap
au4RTM
cap
ctplo
connInTopol
pmTp
The allAttributes value is used when it is not possible to determinate the attribute that caused the
inconsistency.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
157 / 268
The following table gives an overall mapping of the values of consistency status and consistency activity.
Consistency
Status
Semantic
Normal
RM MIB = NE MIB.
Not aligned
NE not reachable
NE in download disable mode
NE in mark audit
Failed to align
The operator can click on the Consistency Status icon, thus displaying the report
identifying the RM failed operation, i.e. the not aligned attributes and the causes of
themisalignment
Config Mismatch
Notify Audit
Aligning
alignment in progress
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
158 / 268
On the 1354RM a node is misaligned. ( From the map or from attibute NENOTEMLALIGNED on the
NE list)
SEQUENCE
a)
b)
c)
Select NE: Search all related objects: (Not Aligned) Misaligned Objects.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
159 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
160 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
9 MAINTENANCE TRACING
Path Trace
Tandem Connection
a)
ED
To configure the Section Trace Identifier, the user has to point to the involved physical connection
and issue the menu Configuration: Trace Identifier: Set/Modify/Read. See Figure 103.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
161 / 268
b)
ED
The section trace identifier wizard is displayed. See Figure 104.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
162 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
c)
ED
In this step the user can select either Set/Modify or Read the Section Trace Identifier. Select Set /
Modify. The Section Trace Identifier wizard: Step 2 is displayed. See Figure 105. herebelow.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
163 / 268
Enabling/disabling of the Trace Identifier mismatch detection. It specifies if the detection of the Trace
Identifier mismatch is enabled or disabled
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
164 / 268
Expected Trace Identifier value may be different from Sent Trace Identifier if regenerators are
present along the physical connection.
N.B.
d)
ED
To prevent traffic loss the user has to perform the configuration operations in the following sequence:
1)
Disable the Trace Identifier mismatch detection by setting to FALSE the Expected Trace Identifier Enabling
2)
3)
Configure the Sent value of the other port to the desired value
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
165 / 268
5)
Open again the Section Trace Identifier wizard on the same physical connection and Enable
the Trace Identifier mismatch detection of the previously disabled port by setting to TRUE the
Expected Trace Identifier Enabling
SEQUENCE
a)
To read the Section Trace Identifier, the user has to point to the involved physical connection and
issue the menu Configuration: Trace Identifier: Set/Modify/Read. See Figure 103.
b)
c)
In this step the user can select either Set/Modify or Read the Section Trace Identifier. Select Read.
The Section Trace Identifier wizard: Step 2 is displayed.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
166 / 268
e)
4)
SCOPE
The mechanism of trace identifier ( byte J1 of the VC4 / VC3 or byte J2 in the VC12 ) is used to control
the continuity of the trail / path.
a)
ED
From the Trail Routing display point to the trail icon and issue Configuration: Trace Identifier. The
window of Figure 108. is presented.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
167 / 268
b)
ED
Click on Next button, thus passing to Trace Identifier definition, as per Figure 109.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
168 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
c)
ED
Enter the desired values for Sent Trace Identifier ( max 15 characters ) and click on Finish button to
confirm.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
169 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
170 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
DEFINITION
The trace identifier mechanism is used to control the continuity of a path/trail.
The end point of the transport entity (i.e. path/HOtrail) can be configured to send in the ongoing/egressing
direction a socalled trace identifier. The trace identifier is put into the byte J1 for 140Mb and 34Mb or
J2 for 2Mb.
OPERATION
The trace identifier sent at the end points in the two directions (one for unidirectional paths) can be
compared with the expected value programmed by the OS on end and intermediate points in the ingressing/egressing direction. If a mismatch is found as a consequent action the client layer (e.g. PDH) , will
receive AIS.
When a mismatch of the identifier is found a trace identifier mismatch alarm can also be generated according to the severity defined in the ASAP.
The trace identifier can be monitored also in the intermediate points of the transport entity in the ingressing
and/or egressing direction. Also in this case the received Trace Identifier can be read. If the expected value
is programmed, an alarm can be generated.
The functionality is not managed for QB3* NEs.
9.3.1 Send Trace Identifier Definition/Change
CONDITIONS
Trace Identifier setup is allowed on a defined, allocated, implemented path.
SEQUENCE
The Send Trace Identifier can be defined/changed only for an already created path/HOtrail.
SEQUENCE
a)
ED
From the path list open the path popup menu and select Path: Configuration: Trace Identifier. See
below figure.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
171 / 268
b)
ED
The Trace Identifier wizard is displayed. See below figure.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
172 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
c)
ED
Click on Next button. The Trace Identifier wizard displays step 2 dialog box, ( see below figure ), asking the operator to enter the sent Trace Identifier for Source and sink TP
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
173 / 268
SEQUENCE
The user, on the path/HOtrail routing display. selects a single CTP/NAP where the TIM ( Trace Identifier
Mismatch ) alarm is present. Choosing the Read received Trace Identifier , the user will see, after the
NE response, the Received and the Expected Trace Identifier.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
174 / 268
DEFINITION
The Tandem connection is a mechanism defined in SDH and OTN that makes use of:
Tandem Connection Termination points (TCT) on NAPs and/or CTPs
Tandem Connection Monitoring points (TCM) on intermediate CTPs of the Tandem Connection
The Tandem connection allows:
The collection of performance data (15 minutes unidir. and 24 hours unidir. and bidir. ) on end points
(TCT) and on intermediate points (TCM) of the TC.
The handling of protections inside the TC not affected from external faults (SNCP/S)
FUNCTIONAL DESCRIPTION
A tandem connection represents the part of a path/HO trail that requires monitoring independently from
the monitoring of the complete path/HO trail.
Tandem connections may be directly monitored at one end by writing and reading a portion of the original
trails overhead.
Tandem connections cannot be overlapped in SDH while 6 levels of TCM are defined for the OTN in G.709.
PROCEDURES
In the following the Tandem Connection management procedures are described.
9.4.1 Tandem Connection Create
SCOPE
The scope of this procedure is to define a Tandem Connection; starting from a path/trail, the user can select
a single TP (NAP/CAP or CTP) and specify:
The type: TCM (for CTPs) or TCT (for CTPs or NAPs/CAPs)
The level (always 0 for SDH)
The direction:
Ingressing or Egressing for TCM
Including Matrix or Excluding Matrix for TCT. In particular, NAP s and CAP s can only support
Including Matrix TCT
The enabling or disabling of the consequent action (i.e. the enabling or not of AIS insertion in case of TC
problems).
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
175 / 268
The definition is possible only when the path/HO trail is at least allocated and it is lost when the path is
deallocated.
OPERATION
The performed checks are related to unidirectional paths only and are the following:
An Ingressing TCM cannot be instantiated below a CTP with sink role in the crossconnection
An Egressing TCM cannot be instantiated below a CTP with source role in the crossconnection
Following the definition of at least one TCT or TCM, on the using path/trail, an attribute specifies that a
manual TCM have been enabled.
Where possible, restrictions at NE level, should be taken into account during this definition phase.
Possible restrictions to be detected in this phase are related to:
NE type and version.
The support in the same TP, of TCT with more than one direction (e.g. it is not possible to have two TCTs,
before and after matrix on the same AU4 for starting and ending two different tandem connections in the
same TP).
On SDH it is not possible to instantiate a TCM and a TCT on the same TP, on OTN it will be possible at
different levels
TCT and TCM are managed as new classes contained in NAPs, CAPs and CTPs.
Once created TCT and TCM have a configuration state set to defined.
The system automatically sets the ASAP OF TCT/TCM according to the following rules:
For a unidirectional path, the ASAP of a created TCT is set depending on both the role of the related CTP
in the connection and the TCT direction (Including Matrix, Excluding Matrix), i.e. is set according to the
following table
Source CTP
Sink CTP
Including Matrix
Ferf&Ais disabled
Excluding Matrix
Ferf&Ais disabled
(*) All disabled in order to not detect the Unequipped alarm in the not used sink direction.
For a bidirectional path:
The ASAP of a created TCT is set Ferf&Ais disabled
The ASAP of a created Ingressing TCM instantiated below a boundary CTP is set None disabled
The ASAP of a created Egressing TCM instantiated below a boundary CTP is set Ferf&Ais disabled
The ASAP of a created TCM instantiated below a not boundary CTP is set None enabled. This because
the functionality to instantiate a TCM below a specific not boundary CTP has to be used for performance
monitoring purpose and not for fault localization (in this case another function will be provided to the user
to activate on all the CTPs internal to the TC the monitoring function).
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
176 / 268
CONDITION
The user can ask for the automatic definition of TC for a path or a HO trail.
The command is only accepted if the path or HO trail is
Partially terminated and there is only one boundary CTP
Fully not terminated and there is only two boundary CTPs.
The system automatically creates the TCT for the NAP and for the boundary CTP(s).
SEQUENCE
a)
ED
To open the popup menu, point to the path icon from the browser window or select the path from
the path list and press the right mouse button.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
177 / 268
b)
ED
Select Configuration: Tandem Connection. The Tandem Connection Management wizard opens.
See Figure 114. herebelow.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
178 / 268
The possible actions you can select from the radio buttons box are:
ED
Creation
Implementation
Deimplementation
Removal
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
179 / 268
Select option Creation and Creation modality. You can select between AUTOMATIC and MANUAL.
If you select AUTOMATIC the system creates TCTs on NAP/s and boundary CTP/s.
If you select MANUAL, you will select the termination points
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
c)
Tandem Connection createstep 2 allows to select manually the TPs. By clicking on the selection
button, the selection list is presented, as per Figure 116. herebelow. The upper selection button allows to select the point/s on which TCT /s is/are to be defined. The lower selection button allows to
select the point/s on which TCM/s is/are to be defined.
e)
Select the termination point and click on Apply. The icon of the selected termination point is displayed
ROUTE DISPLAY ICON
SELECTION BUTTONS
TP SELECTION LIST
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
180 / 268
The direction:
Ingressing or Egressing for TCM
Including Matrix or Excluding Matrix for TCT. In particular, NAP s and CAP s can only support
Including Matrix TCT
The enabling or disabling of the consequent action (i.e. the enabling or not of AIS insertion in case of TC
problems).
The operation is accepted either when the TCT is defined or implemented.
In case of TCT implemented, the operation (Enabling consequent action) may affect the traffic.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
181 / 268
If the consequent action is not enabled, the far end counters are not managed both for TCM and TCT.
Click on Finish button to complete the Tandem Connection definition.
Point to the path icon and select path routing display. Notice that a graphical flag is drawn in correspondence
of
the
path
icon.
See
below
figure.
In addition, dedicated flags are shown for TCT and TCM .
On each TP where at least one TCM or TCT has been at least defined, a flag is set to indicate this condition.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
182 / 268
g)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
183 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
184 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
On a given TCT or TCM, it is possible to visualize all the attributes (e.g. consistency status, direction, level
etc.). Select the TP and issue Show/Set Attributes.
In addition, in the NAPs view, a NAP involved in a Tandem Connection is marked by a dedicated icon.
See below figure.
Once created in the NE, the TCT or the TCM takes the configuration state equal to implemented.
If, at creation time, the NE provides a KO specifying that the TCT/TCM service is not supported, the
TCT/TCM consistency state is set failed to align with error type feature not supported. The user will
manually deimplement and remove TCT/TCM .
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
185 / 268
The user can manually implement all the defined TCTs and TCMs through a manual command to be
issued at path/trail level. The Path/HO trail must be implemented; if not, the command is refused.
Please refer to the above Manual Implementation of TCT and TCM for each TCT/TCM implementation
activity inside the system.
9.4.4 TCT/TCM deImplement
9.4.4.1 TCT/TCM manual deimplementation
The user can manually deimplement TCT and TCM through a manual command to be issued on single
TCTs and TCMs. The single TCT or TCM must be implemented: if not, the command is refused.
Once removed in the NE, the TCT and the TCM takes the configuration state equal to defined.
If the consistency state of the TCT/TCM was feature not supported, no removal is performed towards
the NE.
This operation requires also an interaction at TCT/TCM level with the management of Performance
Monitoring (see SDH/PM section)
9.4.4.2 TCT/TCM global manual deimplementation
The user can manually deimplement all the TCTs and TCMs through a manual command issued at
path/trail level. Path/HO trail must be implemented: if not, the command is refused.
SEQUENCE
a)
b)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
186 / 268
The TCT/TCM to be removed must be in the defined state. If the removal is performed in download
disable mode, the information of misalignment with respect to the NE will be reported on the related TP
If, under a given CTP or NAP, all the TCTs/TCMs are removed, the flag indicating the TC point is also reset.
All the flags on TPs and path/HO trail are updated in a consistent way.
NOTE
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
187 / 268
When a path/HO trail (or a portion of it) is deallocated, the defined TCTs and TCMs are automatically
removed.
ED
01
All the flags on TPs and path/HO trail are updated in a consistent way.
SC.4:MAINTENANCE
3AL 61348 AA AA
268
188 / 268
DEFINITION
The user can ask to enable or disable the monitoring function on the intermediate points of a path/HO trail.
By default when a path/HO trail is implemented, the monitoring function on intermediate points is disabled.
Enabling the monitoring function on intermediate points means:
The instantiation of the POM (Path Overhead monitoring function) on intermediate CTPs (both egressing
and ingressing according to the real availability in the NE and the path directionality)
The enabling of all alarms on the POM.
The enabling of all alarms on the intermediate CTPs (LOP, AIS, etc.).
When the monitoring function on intermediate points is disabled, alarms and Overhead Monitoring
capability is only enabled on Naps and on boundary CTPs.
This functionality is targeted to perform the needed troubleshooting on a not working or not properly
working path/HO trail.
The enabling of this functionality is intended only as a transitory state.
The user should limit the use of this functionality in order to not overload the system.
The user can only ask to enable this functionality when the path is totally or partially implemented (not
commissioned).
The system enables the monitoring function only on intermediate CTPs belonging to QB3 NEs. QB3*
NEs are not taken into account.
If the path/HO trail has the Trace identifier enabled, the expected trace identifier is set also on intermediate
points according to the type of the path.
The alarms received on POM functions and on CTPs are NOT propagated to the paths and are only used
to give information to the user. The main graphical view to be used for troubleshooting is the path/HO trail
route display.
The enabling status of this functionality is represented by a global attribute of the path/trail. To be noted
that the value enabled is only referred to the NEs supporting the functionality and it has in general the
meaning of where possible.
When a path is deimplemented the monitoring function on intermediate points is disabled first.
The enabling of this functionality is performed regardless to the state of the QB3 SDH alarm enabling
status of the belonging path/HO trail.
The interworking between Trace identifier management, alarm enabling/disabling on paths/HO trails,
monitoring function on intermediate points, is giving from the following table
Nap and boundary
CTPs
Trace identifier
Enabling of alarms
ED
01
CTPs in
SNCPN
SC.4:MAINTENANCE
3AL 61348 AA AA
268
189 / 268
How to enable POM on a path, by pointing at the path icon and issuing the following command:
Path: Configuration: POM on Ctps: Enabling
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
190 / 268
ED
Trace Identifier read on a certain CTP, by issuing the command Trace Identifier: Read.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
191 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
192 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
No Loop
Figure which follows shows the Manage Loop popup menu available on NAP.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
193 / 268
In this case, as shown in the following figure, on the port corresponding to the first NAP a line loop is executed. AIS signal is sent toward the network, detected by the far end NAP and sent back.
SHOW/SET
ATTRIBUTES
AIS
LOOPBACK
ACTIVE
AIS
The NAP loopback status can be shown via Show/set Attributes of the involved NAP. see below figure.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
194 / 268
The NAP loopback status can be shown via Show/set Attributes of the involved NAP.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
195 / 268
Set
Remove
Figure which follows shows the Manage Loop popup menu available on CTP. Point to the CTP and issue
Internal Loopback: Set to setup the loop or Internal Loopback: Remove to remove the loop.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
196 / 268
LOOPBACK
LOOPBACK
AIS
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
197 / 268
CT Access Granted
CT Access Required
CT Access Denied
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
198 / 268
10 PROTECTION MANAGEMENT
10.1 SNCP path layer switch management
The SNCP switch management commands can be applied to SNCP paths or to Bridge & Switch
connections in topology
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
199 / 268
SEQUENCE
a)
From the browser window, e.g. from the Routing display, point with the mouse at the path icon and
open the Manage SNCP popup menu. It is possible to obtain this menu by selecting the path icon
and selecting the Actions:Manage SNCP pulldown menu. The Manage SNCP menu allows to
further select between:
Synchronize. This command retrieves the actual switch status of the B & S connections from
EML.
Release. This command clears the previously issued lockout/forced/manual command. This
command is available for all types of Network Element.
Lockout. This command either locks( forces ) the path/switch to the main route if a Set
Revertive command has been previously entered or locks the path/switch to the actual position
if a Set not Revertive command has been previously entered.
Force Main . This command forces the path on the main route. The path will remain on the main
route even in case of failure. This condition can be modified only by means of the Release
command.This command is available for all types of Network Element.
Force Spare . This command forces the path on the spare route. The path will remain on the
spare route even in case of failure. This condition can be modified only by means of the Release
command. This command is available for all types of Network Element.
Manual Main . This command switches the path to the main route. The switch is rejected in case
of failure and if a previously issued Force/Lockout command is active. The Force/Lockout
condition can be cancelled by means of the Release command.
Manual Spare . This command switches the path to the spare route. The switch is rejected in
case of failure and if a previously issued Force/Lockout command is active. The Force/Lockout
condition can be cancelled by means of the Release command.
Set Revertive. This command causes the path to revert to the main route after the repair of the
involved objects. The Wait to restore time parameter is managed at Equipment layer. This
command is available for all types of Add and Drop Multiplexers; it is not applicable to 1641SX
cross connect.
Set not Revertive. ( default ) The path does not revert to the main route after the repair of the
involved objects. This command is available for all types of Add and Drop Multiplexers; it is not
applicable to 1641SX cross connect.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
200 / 268
Events which manage the switch position have a priority mark; in particular Forced SNCP commands have
priority greater than failure events, while failure events have priority greater than Manual SNCP
commands.
C service. It means that the switch ( only for D & C ) is turned to the service position
The last operation executed on the switch can assume the values:
The Revertive operation mode icon is present if the switch has been set to Revertive.
b)
ED
After the execution of a Manage SNCP command a report is forwarded to the operator.
See Figure 135.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
201 / 268
N.B.
ED
01
202 / 268
N.B.
For a SNCP trail the same commands apply. Notice that The trail can be terminated with an
SNCP connection only in case of 1661SMC equipment with Enhanced connectivity (able to
create an SNCP connection with grooming). Otherwise the trail must utilize an unprotected
physical connection and create the SNCP connection in another NE.
SPARE
LOLCs
LOCTPs
LOCTPs
MAIN
SPARE
LOCTPs
LOLCs
LOCTPs
MAIN
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
203 / 268
protection
working
BEFORE
AFTER
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
204 / 268
ED
01
BEFORE
BEFORE
protection
working
protection
working
W
E
AFTER
W
E
AFTER
SC.4:MAINTENANCE
3AL 61348 AA AA
268
205 / 268
ED
01
E
BEFORE
W
protection
working
W
3AL 61348 AA AA
268
AFTER
SC.4:MAINTENANCE
206 / 268
The node that detects the failure (Tail End), sends a Bridge Request to the node that is adjacent
along the direction where the failure is present (that becomes the Head End): this Bridge
Request is sent on both the long and the short path.
2)
The intermediate nodes substitute all of the connections pertaining the low priority traffic with
bypasses among the two aggregates.
3)
When the Head End receives the Bridge Request on the short path, it sends back to the tail end
a Reverse Request on the short path and a Bridge Request on the long path.
4)
When the Head End receives the Bridge Request also on the long path, it performs a ring Bridge
and sends to the Tail End, on both paths, the notification of this new status
5)
When the tail end receives, on the long path, the bridge request from the Head End it performs
a ring bridge and sends the notification of this new status to the head end, using both paths.
6)
When the tail end receives, on the long path, the notification of the execution of the bridge on
the head end, it performs a ring bridge and switch and sends the notification of this new status
to the head end, using both paths.
When the head end is aware of the bridge and switch activated on the tail end, via the report
of the bridge status on the long path, it performs a switch, so that both ends are now in bridge
and switch
7)
When a protection switch is in effect, all of the protection capacity is used to recover the working traffic;
in this situation no low priority connections can be established on the protection capacity and it is required
that, in order to avoid misconnections, all of the tributaries that terminate a lowpriority connection output
an AIS signal (this operation is called squelching).
After the failure has been removed, a similar sequence of operations is performed by the head and tail
end; if the failure was single, the reverse procedure can starts after a specified time interval, called Wait
Time to Restore (WTR).
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
207 / 268
The following diagrams depict the sequence of operations that occur in a sixnodes ring when a single
failure (signal degrade, in this case) occurs on the fiber that carries the traffic from node 2 to node 3.
Figure 142. depicts the initial situation, where a tributary at node 1 is connected with another tributary
at node 4, using the clockwise direction for the path going from node 1 to node 4 . The remaining
capacity, both working and protection, is used to source and terminate unequipped VC between the
adjacent nodes.
Tributary
Tributary
Working Channels
Protection Channels
Figure 142. :Example of six nodes ring
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
208 / 268
Tributary
Working Channels
Protection Channels
Bridge
Tributary
Switch
The squelching technique requires that two different squelching actions are taken on the HVC and on the
LVC. The HVC are squelched only at the switching nodes, i.e. at the nodes that perform bridge and switch,
while the LVC are squelched where they are terminated. Furthermore, a different squelching action is
taken on the HVC according if they are accessed at the LVC level or not; in detail, if the VC4 is composed
of VC12 that are terminated at different nodes, the squelching performed at the switching nodes must be
removed after the final bridge and switch state has been reached: this is necessary in order not to loose
LVCs that would be otherwise unnecessarily squelched.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
209 / 268
When a 2f MSSPRING is interworked with another ring (either SNC/I or MSSPRING), the
interconnection of the two is performed by connecting two pair of nodes per ring with HVC connections,
as shown in the following figure.
Each VC4 that has to cross the ring boundary (only HVC level ring interconnections are considered here)
must be output by two nodes, one of which, the primary service node (PSN) drops it and continues to the
secondary service node (SSN). In the opposite direction, the SSN inserts a copy of the VC4 into the ring
and the PSN selects between the VC4 coming from the SSN and the VC4 that can be locally inserted. The
selection is performed on the basis of the pathAIS.
The protection mechanism works on the hypothesis that the other ring selects one of the two version of
the incoming VC4 and transmits two identical copies of the VC4 towards the PSN and the SSN (this is
guaranteed if the other ring is an MSSPRING or an SNC/I ring).
Note that the PSN and the SSN need not to be adjacent and need not to be the same for all of the VC4
that cross the ring boundary: i.e. each crossing VC4 has two associated nodes that act as PSN and SSN.
It is also possible to connect two rings at more than two points, but this is usually unfeasible with the normal
ring topologies and has not been considered here.
This document does not address the case where the VC4 that crosses the boundary is terminated at its
primary service node.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
210 / 268
2f MSSPRING
Primary
Service
Node
ED
01
Secondary
Service
Node
SNCP or MSSPRING
SC.4:MAINTENANCE
3AL 61348 AA AA
268
211 / 268
First of all, the APS Controller must know whether it shall operate or not, e.g. because the ring is protected
with a different strategy: this information will be called APS Controller enabling and can be considered
as a binary value (enabled or disabled).
APS Controller must be explicitly activated to exchange K1 and K2 bytes with the other N.E.; also this
information can have only two values (activate or inactive). Note that an enabled but inactive APS
Controller is in a well defined state, which corresponds to a particular set of transmitted K1K2 bytes,
default APS bytes; It is required that the default APS code on K1K2 is a pattern of all zeroes
An enabled APS Controller (even when it is inactive) needs to know the node identifier of the N.E.
where it is operating; the node identifier is a number in the range 0 through 15, and is unique within
the ring.
An enabled and active APS controller must be aware of the topology of the ring, i.e. of the sequence
of nodes (ring map) that is encountered when traversing the ring in a specified direction (e.g.
clockwise); the crossed nodes are identified by their node id and may not be more that 15 (the total
number of N.E. in a 2F MSSPRING is 16) neither less than 2.
A final parameter that must be known by the APS Controller is the Wait Time to Restore value; this value
may range from 0 to, at least, 15 minutes (a step of 1 minute is accepted);
10.2.4.1 Squelching tables: definition and size
The HpSq block needs to receive two sets of squelching tables that contain some routing information
that is necessary to properly identifiy where and when inject AIS.
The first set is composed of four tables that will be called, in the following, VC4 squelching tables. There
is a VC4 squelching table for each aggregate input and output of the network element. The structure of
the four tables is identical: for each incoming (or outgoing) High Priority Au4 (i.e. Au4 1..2 for the Stm4
and Au4 1..8 for the Stm16) the table must contain the source and the destination nodes of the transported
VC4; note that, in case of ring interworking, the VC4 can have two source nodes . It is also allowed for a
VC4 to have multiple destination nodes (up to 15 in the worst case). It can be demonstrated that only one
source and one destination node is necessary for the VC4 squelching tables, namely the farthest source
node and the fartherst destination node.
If a VC4 contains LVC that have different source or destination nodes, the VC4 squelching table must
indicate this situation: for this field a binary value is enough.
If a fixed size table is chosen, the size of each row of each VC4 squelching table is 9 bits, where this number
is obtained by adding 4 bits for the source node identifier, 4 bits for the destination node identifier and 1
bit that indicates whether the VC4 is accessed at the LVC level or not. Multiplying the row size and the
number of rows and the number of tables, the final value of
4 x 8 x (4 + 4 + 1)
288 bits
(36 Bytes)
is obtained
The second set of squelching tables contains, for each terminated LVC, the indication of the source node
of the LVC itself. Also in this case an LVC may have two source nodes that musy be indicated in the table,
regardless of which is the primary and which is the secondary). In the worst case (8 VC4 structured as
63 TU12, all with double source) the following total size is obtained:
63 x 8 x (4 + 4)
4032 bits
(504 Bytes)
As said before, the VC4 squelching tables have to be provided to all of the nodes of the ring, while the LVC
tables are required only at the nodes where LVC traffic is terminated.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
212 / 268
The APS Controller blocks need a set of configuration information for properly execute their functions.
In order to explain with the sufficient detail level, an example of squelching table computation is presented.
In the following figure, a 7 node ring is considered, where the node id are represented by capital letters
from A to G. Five connections are supposed to exist, three regarding VC12 and two regarding VC4:
VC12 #1 of VC4 #1 is supposed to be inserted at node A into the VC4 #1. The exit point of this VC12
is node G. Due to the connectivity restrictions, the VC12 will have not changed neither the TU12 nor
the Au4 along the path.
VC12 #2 of VC4 #1 has two sources, due to the ring interworking: node B is the secondary service
node, while node C is the primary. The destination node is F. Vc12 #2 always occupies the TU12 #2
of the VC4 #1 that is transported into the Au4 #1.
VC12 #63 of VC4 #1 has one source node, E, and two destination nodes, namely F and G: i.e. this
is a pointtomultipoint connection. The Vc12 #63 always occupies the Tu12 #63 of a VC4 that
always occupies the Au4 #1.
VC4 #8 has two sources, A and B, respectively the secondary and primary service nodes, and has
two destination nodes, E and F.
WEST
EAST
VC12 #1
VC4 #1
VC12 #2
SSN
PSN
VC12 #63
VC4 #2
VC4 #8
SSN
PSN
The VC4 squelching tables for the nodes represented in the example are listed in the following. Note that
a VC4 containing LVC is terminated each time an LVC is inserted and or dropped, so that the only node
where the VC4 #1 is not terminated is node D.
VC4 squelching table for node A
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
213 / 268
Node A
From To
West Output
LVC
From To
East Input
LVC
From To
East Output
LVC
VC4 #1
From To
LVC
YES
NO
VC4 #2
VC4 #8
VC4 #1
West Output
From To
LVC
From To
East Input
LVC
From To
East Output
LVC
From To
LVC
YES
YES
NO
NO
VC4 #2
VC4 #8
From:
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
214 / 268
West Input
Node C
West Input
VC4 #1
West Output
From To
LVC
From To
East Input
LVC
From To
East Output
LVC
From To
LVC
YES
YES
NO
NO
VC4 #2
VC4 #8
VC4 #1
West Output
From To
LVC
From To
East Input
LVC
From To
East Output
LVC
From To
LVC
YES
YES
NO
NO
VC4 #2
VC4 #8
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
215 / 268
West Input
VC4 #1
West Output
From To
LVC
YES
From To
East Input
LVC
From To
East Output
LVC
VC4 #2
VC4 #8
NO
From To
LVC
YES
NO
NO
West Output
From To
LVC
VC4 #1
VC4 #2
VC4 #8
From To
East Input
LVC
From To
East Output
LVC
From To
LVC
YES
YES
NO
NO
NO
From:
Vc12 #2 of VC4 #1
B, C
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
216 / 268
Node E
Node G
West Input
West Output
From To
LVC
VC4 #1
YES
VC4 #2
NO
From To
East Input
LVC
From To
East Output
LVC
From To
LVC
VC4 #8
From:
Vc12 #1 of VC4 #1
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
217 / 268
An MSSPRING can be created on the map by means of the command Construction: Add Object: Ring:
MSSpring... Checks are performed during validation and activation phase: only 1661SMC and 1664SM
and 1670SM are allowed.
Implementation, deimplementation and removing can only be performed on the complete ring and not
on single connections.
During the implementation, RM creates :
synchronize
release
force east, west
lockout east, west
manual east, west
change Wait To Restore time (5, 300, 600, 900 sec) ( see NO TAG)
Switch position (displayed on main view) : unknown, idle, bridge east or west, bridge & switch east
or west, pass through
Switch cause (displayed on main view) : Failure, Restoration, Operator Request, None, Unknown.
Active Operator Command : Release, Lockout, Force, Manual, None.
Pending Operator Command : Release, Lockout, Force, Manual, None, Synchronize. It is the
command under execution. It is set to none when the answer (OK or KO) is received from the EML.
At the beginning all the switch positions and switch causes are set to unknown, the pending is set to none.
After a parametric time T1, the managing process performs a synchronization for a parametric number
N of switches with the position set to unknown (i.e. not yet synchronized manually or through an event).
After another parametric time T2, the operation is repeated with another set of N unknown switches.
During this automatic synchronization, the pending command of the switches under operation is set to
Synchronize.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
218 / 268
From the browser point with the mouse at the network and open the popup menu. Select item
Search: All related items... ( see Figure 146. )
b)
From the selection box select item NPAs and click on OK button. The NPA drawing window is
displayed.
Switch East
Switch West
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
219 / 268
All the HO SbnConns belonging to HOPaths and HOTrails in MSSPRING topologies include
squelching Information (4 values : West Src / West Dst / East Src / East Dst end Nodes Identifiers).
Squelching Info are also set for the connections between HOTTP and HOCTP.
For broadcast paths, the squelching information related to legs is evaluated run time during the
implementation (when multiple legs and passthrough are merged into a single broadcast connection).
10.3.1.2 Linear MS protection (1+1)
This feature is only applied to ADMs.
The management of the protection is done by the EMLs. On RM side, only the presence of the protection
is displayed to the operator.
In addition to the alarm already foreseen in case of failure on both the fibers involved in the linear MS
protection, a new alarm is emitted at SENIM level also when a failure on a single fiber will occur. This will
warn the operator on the reduced degree of protection.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
220 / 268
A view of all the MS Protection Blocks in a MSSPRing is available in the browser. To display this view,
execute the following procedure:
a)
From the browser point with the mouse at the network and open the popup menu. Select item
Search: All related items...
b)
From the selection box select item NPA and click on OK. The NPA list is displayed.
c)
Point to the 4F NPE RING NPA and click on NPA view button. The NPA view is displayed.
d)
From each protection block it is possible to issue the ring switch and span switch commands.
The effect of the Span Switch and Ring Switch operations is described in Section Technical Annexes, NPE
ring.
The above mentioned commands are mainly used for maintenance purposes. See Section
MAINTENANCE, Chapter 4 Diagnostic of the NPE Ring.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
221 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
222 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
11 PERFORMANCE MONITORING
11.1 Introduction
The aim of the Performance Monitoring at RM side is to allow the user to monitor transport objects, i.e.
the objects path and trail. The monitoring activity is executed on the involved tps.
In order to monitor transport objects, the user creates objects called Measures , which are performance
monitoring work sessions, defined by a set of characteristics according to the Customers needs.
After creating the measure, the user must associate (correlate) to it the transport/s to monitor and the
termination points (TPs). See NO TAGon page NO TAG.
The status of the measure can be:
Stopped. This means that the collection activity is terminated. The collection activity can restart upon
entering the Activate command.
Only one measure can be active at the same time on a PM termination point for a given
granularity value ( 15 , 24 h )
N.B.
For a path terminated to all virtual objects, the relevant tps cannot be automatically correlated.
In the following paragraphs it is given a description of the main procedures relevant to PM.
N.B.
This feature allows the definition of TCA profiles on 24h unidirectional measurements.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
223 / 268
The user is able to correlate a TCA to 24h measurements. For new NEs, the Maintenance measurement
should to be used but, for compatibility, also the QoS measurement is accepted.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
224 / 268
SEQUENCE
a)
From the Browser select the PM domain and open the popup menu. Select the command Create:
Measure. The object creation dialog box is presented.
measure name (userlabel) . The measure name can be modified, by means of the SHOW/Set
Attributes command, only if the measure status is PLANNED.
ED
Qos ( quality of service ). Counter started are: BBE, ES, SES, UASbidi
Maintenance. Counter started are: BBE, ES, SES, UAS near end, UAS far end.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
225 / 268
Transport State
Qos for Tandem Connection. The transport being associated is involved in a tandem connection
and Counter started are: BBE, ES, SES, UASbidi
Maintenance for Tandem Connection. The transport being associated is involved in a tandem
connection and Counter started are: BBE, ES, SES, UAS near end, UAS far end.
start/end time. If you do not specify start/end time, you can subsequently activate manually the
measure by means of the command Measure Start, otherwise the Measure will be started at the Start
Time and stopped at the Stop time.
One pmtp ( NAP/CAP type ) for a bidirectional transport is enough because the NE
provides the information relevant to both ends (NEAR END + FAR END).
If the path is broadcast all sink ends are monitored. (Only real ends are considered.).
Virtual NAPs or CAPs are not automatically monitored; the closest real CTP ( boundary
CTP ) will be monitored.
Monitored layer. You can specify the layer of the objects monitored by the measure:
LO low order
HO high order
LO&HO you monitor transports belonging to all the path layer network ( HO / LO )
granularity. The granularity is the monitoring frequency, i.e. the frequency of historical data counters
grouping. You can select:
TRUE, the counters belonging to granularity periods will be collected, when the measure is
activated
FALSE, the historical data counters will not be collected, even when the measure is activated.
This implies that the goal of the measure is to set Threshold Crossing Alarm profiles on the
termination points only.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
226 / 268
NOT SUPPORTED
period HDs in DB
d)
To verify the successful creation of the measure, check on the Measure Create report window.
e)
You can now navigate from the pmDomain, in order to find the new measure icon.( from the Browser
pmDomain select Search related items : Measures. The Measure List is presented).
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
227 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
228 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
INTRODUCTION
A measure can monitor paths and trails, i.e. transports of type path and transports of type trail. The
transports have to be correlated to the measure.
SEQUENCE
a)
Select the Measure from the list. The Measure must be planned.
b)
Select the menu Actions: Correlate/Merge. You can further select among:
Correlate paths/trails
Correlate reports
Uncorrelate reports
Merge measures
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
229 / 268
Select Correlate: paths/trails. The Object Correlation window is presented. The measure is already
contained in the window . Drag and drop the paths/ trails to correlate to the window drop area.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
c)
e)
To verify that the correlation has been properly entered, navigate the browser in order to find the icon
of the PMtransport which has been just created. From the browser point with the mouse to the
measure icon and issue Display: Related items: PMTransports. The PMTransport icon/s are
displayed in the browser window.
N.B.
ED
The correlation MeasureTransport can be also executed starting from the transport (path /trail)
by using the relevant popup menu.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
230 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
231 / 268
ED
01
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
DRAG
measure list
Figure 156. Correlate measure to path
SC.4:MAINTENANCE
3AL 61348 AA AA
268
232 / 268
INTRODUCTION
For a transport ( path or trail ) to be monitored by a measure, at least one TP termination point ( NAP,
CAP or CTP) of the transport must be monitored by the measure. This means that the measure, when
activated, will collect PM_ DATA relevant to the TPs correlated. To indicate that a measure has to monitor
a certain transport in a certain TP, the involved TP has to be correlated to the measure; the result of the
correlation procedure is that a new object is created: the pmTP. This object is created under the
pmtransport.
LIMITATIONS
In the correlation of a TP to a Measure, the following limitations apply:
A TP can be correlated to a measure ( and so a PMTP can be created under a measure ) only if the
transport the TP belongs to is already correlated to that measure
A TP can be monitored by at most 2 ( two ) activated measures at the same time, and the measures
must have different pmGranularity values.
SEQUENCE
a)
Select from Browser view the ctp / nap / cap to correlate. They must belong to a transport which is
already correlated to at least one Measure.
b)
c)
The tp is correlated to the Measure which is already correlated to the relevant path. By using the
Browser you can verify the tp correlation to the Measure, looking for the newly created pmTP.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
233 / 268
If the transport object the TP belongs to ( e.g. a path ) is correlated to many measures and you
issue the command to correlate the tp to a Measure, the system provides a measure selection
dialog box, in order to select which measures you want to correlate the tp to.
In addition ,from Measure: Search related items: PMtp , the list below is displayed.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
234 / 268
Among PM tp related items you can select the PM tp view. See figure which follows.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
235 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
236 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
If you issue a Show/Set attributes of a PMTP object, you will get the dialog box of Figure 161.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
237 / 268
REQUIRED SIDE. The REQUIRED SIDE is the direction of the signal to monitor. It can be set
by the 1354RM to one of the following values:
sink
source
both
Examples of assignement of the SIDE are given in paragraph 11.5.1 herebelow.
ACTIVE SIDE. It represents the actual direction monitored on equipment for the specified TP.
REQUIRED MODE. It represents the required mode to start the monitoring on the PMTPs.
The Mode (UNI or BIDI) determines the type of UAS counter to be collected by EML (SH/WX)
for a certain tp. The possible values are:
unidirectional, RM will receive the values of two counters: Near End UAS (Unavailable
seconds) and FEUAS (Far End Unavailable Seconds)
bidirectional, RM will receive the values of only one counter BIDUAS which represents
the logical OR function of the Near End UAS (Unavailable seconds) and FEUAS (Far End
Unavailable Seconds) counters.
ACTIVE MODE. It represents the actual mode monitored on equipment for the specified TP.
REQ SIDE and REQ MODE are automatically selected by RM after executing the command
Correlation of the tp to the measure . They are chosen taking into account:
ACTIVE PM. This attribute is set to TRUE if the RM wants to have PM available on that TP, e.g.
when the measures passes from the status planned to the status activated. This attribute is
set to FALSE if the RM does not want to have PM available on that TP, e.g. in case of transport
rerouting.
sink/source REQUIRED TCA. This attribute is the name of the desired Threshold Crossing
Alarm profile on the termination point.
sink/source ACTIVE TCA. This attribute is the name of the actual Threshold Crossing Alarm
profile on the termination point.
N.B.
ED
ACTIVE SIDE/ACTIVE MODE are not meaningful when the measure is planned.
After activating the measure it is possible to show the actual ACTIVE SIDE and the actual
ACTIVE MODE of the tp in the PMtp show/set attributes window. These attributes show the
situation present on the equipments. If the PMTP is not consistent, this means that at least
one difference between Required and Active attributes is present.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
238 / 268
NEB
ctp
ctp
MAIN
sink
B&S
B&S
ctp
source
ctp
ctp
SPARE
sink
Figure 162. Side of the pmctps in a b&s connection ( signal from NEA to NEB )
NEA
NEB
ctp
ctp
MAIN
source
sink
B&S
ctp
SPARE
ctp
source
ctp
Figure 163. Side of the pmctps in a b&s connection ( signal from NEB to NEA )
ctp
ctp
nap
source
nap
source
sink
sink
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
239 / 268
Counter reports Profiles are objects which allow the automatic generation and sending of documents
( Counter Reports) containing all the data collected by the measure in a range of time (T1, T2).
The document name derives from the measure userlabel by adding the character _ ( underscore ) as
prefix and the characters _CO as suffix. As an example, the document name of the counter report
associated to the measure MEASURE1 will be _MEASURE1_CO.
First of all, the counter Report Profile instance has to be created, then it must be correlated to all the
measures that require the generation of documents; only when the measures will be activated, the
document will be periodically generated and sent.
A counter report profile can be associated to more than one measure at the same time.
SEQUENCE
a)
ED
To create a counter report, from the browser, point to the PM domain and issue the command PMdom:
Create: Counter Report. Enter:
type (on file/ printer / mail). The generated reports can be stored on file, printed or sent by Email.
frequency (15/ 1 h / 1 Day / 1 Week / 1 Month / 1 Year). This attribute means that the counter
reports for the activated measures will be generated each quarter of hour / each hour / each
day...
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
240 / 268
INTRODUCTION
Measure granularity
c)
ED
Report window
15m
15m / 1h / 1day
24h
To verify the correlation, point at the measure and issue Display: Related items: counter Reports. See
Figure 166. and Figure 167.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
241 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
242 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
An example of the document that will be generated by a counter report profile is shown in Figure 168.
N.B.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
243 / 268
Threshold report profiles are objects which allow the automatic generation and sending of documents
( Threshold reports).
These documents contain only the values collected by the measure which exceed some user specified
threshold values.
As in the case of the counter report profiles, first you must create the threshold report profile object; then
it can be correlated to each measure you want the threshold reports to be generated for; threshold reports
will be sent only after measure activation.
SEQUENCE
To use this function you can execute the following steps:
a)
type (on file/ printer / mail). The threshold report can be stored on file, printed or sent by Email.
window (15/ 1 h / 1 Day / 1 Week / 1 Month / 1 Year). This attribute means that the reports for the
activated measures will be generated each quarter of hour / each hour / each day...
The threshold values which will determine the contents of the generated documents.
N.B.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
244 / 268
INTRODUCTION
b)
ED
window
15m / 1h / 1day
1 day / 1 week / 1 month / 1 year
You can verify, by using the browser, that the Threshold Report Profile has been created. See
Figure 170.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
245 / 268
Threshold
report
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
246 / 268
SCOPE
The scope is to correlate a measure to a certain report profile.
SEQUENCE
a)
From Measure list select a measure and issue Correlate/Merge:Correlate Report. A dialog box is
presented.
b)
ED
From Browser drag and drop the report profiles ( counter and threshold ) to the Correlation dialog
box drop area and click on button Create.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
247 / 268
c)
ED
To verify the correlation, in the browser, from the measure issue Search: Related Items: Counter
reports/ Threshold Reports.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
248 / 268
the user activates manually the measure. Stopped measures can be only manually reactivated.
Only when activated, the measure realizes the goal it has been created for: data collection from Network
Elements, automatic generation and sending of counters / thresholds reports (if they have been
correlated), generation of threshold crossing alarm ( in case TCA profiles have been correlated to pmTPs
belonging to the measure).
The conditions to activate a measure are:
Select from the browser the measure and issue the Specific: Start / Consistency / Stop : Start
command. The icon of the measure becomes green and the icon of the transport ( path or trail ) is
marked by an indication of the measure granularity.
granularity
After the activation of the measure, if the measure is marked as consistent, this means that the
activation command has been successfully completed for all the correlated points. This means that
the NEs have started the monitoring action and the EMLs will provide the required data.
If the measure is displayed as not consistent, it means that the activation command has failed for
at least one of the tps actually correlated to the measure. It is required to execute a Consistency
activity on the measure.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
249 / 268
Automatically, when the end time of the actually activated measure expires.
When Stopped, the measure will no longer collect data from the Network Elements and will not generate
reports or threshold crossing alarms.
After being stopped, the measure can be either Consistent or Notconsistent
A stopped measure can be manually reactivated.
SEQUENCE
a)
Select from the browser the measure and issue the Specific: Stop command. The icon of the measure
becomes lightblue.
a)
ED
Select from the browser the measure and issue the Actions: Start/Consistency/Stop: Consistency
command.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
250 / 268
INTRODUCTION
INTRODUCTION
A Threshold Crossing Alarm Profile object allows the user to have the automatic generation of alarms for
each counter type, when the counter values run out of a range of values fixed by the user himself.
When the granularity period expires the alarm reset is performed.
SEQUENCE
a)
From the browser, point with the mouse at the PM Domain and issue the command Create: TCA
Profile. Specify the high threshold value, the low threshold value and the severity for the counters
listed in the following. Maximum values are listed herebelow.
Performance Parameter
Maximum Value
(15minute period)
Maximum Value
(24hour period)
BBE, FEBBE
539,100
51,753,600
2,159,100
207,273,600
8,639,100
829,353,600
34,559,100
3,317,673,600
86,400
SES, FESES
810
78,760
PJCHigh, PJCLow
1,800,000
172,800,000
b)
N.B.
ED
At least one threshold value must be specified since default values are not present.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
251 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
252 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
SEQUENCE
a)
Point with the mouse at the PMTP to correlate and issue the popup menu Performance Monitoring:
Correlate to TCA. The following conditions can be met:
1)
The correlation is executed if in the RM exists only one TCA profile with granularity and rate
compatible with the PMTPs to correlate.
2)
If in the RM exists more than one TCA profile with granularity and rate compatible with PMTPs
to correlate, a dialog box is presented. The operator has to select the specific TCA to correlate.
3)
4)
To verify the successful correlation, from the browser point with the mouse to the involved PMTP
and issue the Display: Main Related items: TCA Profile.
N.B.
In the QB3*ADMs all TPs with same rate and granularity must have the same TCA profile, then
if you try to associate to a certain PMTP a TCA profile different from the TCA profile already
assigned to another TP, a dialog box is presented, asking the user either to force or not the TCA
profile on that NE.
The above limitation does not apply to QB3 ( INFO MODEL ) cross connect equipment.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
253 / 268
The merging of more measures (input measures) into another one (target measure) is a complex action
which allows to put together more monitored objects (paths, trails and their termination points) into one
measure.
SEQUENCE
a)
From the measure list select one of the measures to merge and click on button Merge. The Merge
dialog box is displayed. It contains in the upper area the previously selected measure, whose name
will be the name of the merged measure being created. See Figure 176.
b)
ED
Drag to the drop area the measures to merge and select the button Merge measure. The measures
are merged into a new one. The dropped measures are deleted from MIB.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
254 / 268
INTRODUCTION
The detailed explanation of the displaying data function can be found in document PMDS.
The collected PM data can be presented to the user by means of the Displaying PM data option.
a)
ED
Select the measure from the browser and select the functional button Show Performance Monitoring
Data.
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
255 / 268
A pmNE object is automatically created the first time the user executes the correlation of a TP belonging
to a certain NE.
Starting from the PM domain, you can navigate, by means of the Display: Related Items command, to the
Monitored NEs. See figure below.
The Show/Set attributes from this object contains the following attributes:
userlabel
NE type
last collected file15m / last collected file 24h. These attributes are used to keep a history of the file
that has been collected from RM and to ask EML for sending the not yet received files.
working status. This attribute is usually set to normal. It changes to Synchronizing when the attribute
On going activity is in one of the following states:
ED
SC.4:MAINTENANCE
3AL 61348 AA AA
268
256 / 268
In addition, from browser it is possible to display the PM tp view and the PM transport view. See figures
which follow.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
257 / 268
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
258 / 268
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
INTRODUCTION
To Archive Monitoring data means to memorize PM data on a storing support ( tape / file )
Data archived are those relevant to:
measures
PM transport
pmTPs
historical data
The result of the Archive procedure is to obtain a series of magtapes, each one storing data relevant to
a certain period.
The Archive procedure must be executed to avoid memory disk saturation, with the objective of maintain
hystorical data and transfer them to tape.
The Archive procedure is not executed automatically but must be launched by the 1354RM user.
Only archived data can be deleted from disk.
It is strongly recommended to execute Archive and Delete procedures of the PM hystorical data with the
following time periods:
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
259 / 268
a)
From TMNOS view select the RM icon and issue the Actions: SMF: PMDS DB Administration item.
b)
From TMNOS view select the RM icon and issue the Actions: Performance Monitoring menu item.
b)
From TMNOS view select the RM icon and issue the Actions: Performance Monitoring menu item.
b)
SEQUENCE
a)
From TMNOS view select the RM icon and issue the Actions: Performance Monitoring menu item.
b)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
260 / 268
SEQUENCE
INTRODUCTION
The Archive session allows to display previously completed archive to tape operations and programmed
archive operations.
SEQUENCE
Starting from the PM domain, you can navigate, by means of the Display: Related Items command, to the
Archive Session. The list of the Archive sessions is presented. For each item of the list the Show/Set
attributes dialog box contains the following attributes:
user label, automatically built on from date and the granularity (e.g.: an archive performed on
15 min data from the 15/06/1998 will be given the following user label: 15 minutes counters
1998/06/15)
An instance of archive session, concerning the next archive session, is automatically generated at the
end of each archive operation.
11.16.1 Attribute Setting
The only attribute which can be set by the user is the attribute to date, in order to anticipate or postpone
the next archive operation.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
261 / 268
This is the action opposite to the Correlate Transport to planned Measures; by uncorrelating a transport
from a planned Measure the user indicates that the termination points belonging to that transport will not
have to be monitored by the Measure.
SEQUENCE
a)
From the browser point at the transport icon and issue the Performance Monitoring: Remove from
command.
b)
More than one measure is correlated. The system provides the list of the planned measures
which are monitoring the involved transport object.The user selects the measure to uncorrelate
and clicks on the confirmation button.
2)
SEQUENCE
a)
From the browser point at the tp icon and issue the Performance Monitoring: Uncorrelate from Measure popup menu.
b)
ED
1)
More than one measure is correlated. The system provides the list of the planned measures
which are monitoring the involved tp object.The user selects the measure to uncorrelate and
clicks on the confirmation button.
2)
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
262 / 268
INTRODUCTION
INTRODUCTION
The Remove from RM menu item allows to remove the following objects:
pm TP
PM transport
Measure
The object containment tree is shown in Figure 180. , i.e. if you remove an object, all the contained objects
are automatically removed.
N.B.
MEASURE
REPORT
COUNTER/
THRESHOLD
PM TRANSPORT
PMTP
HISTORICAL
DATA
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
263 / 268
This is the action opposite to the Correlate Counter/threshold report to planned Measures, by
uncorrelating a Counter/threshold report profile from a planned Measure.
SEQUENCE
a)
From the browser, point at the measure icon and issue the Performance Monitoring: Uncorrelate
from Measure command. The list of the associated reports is presented.
b)
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
264 / 268
INTRODUCTION
12 LOGGER
The event logger displays the current events and the list of the events which have been stored in the log
file.
The Event Log dialog box is shown in Figure 181.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
265 / 268
Event Type. The operator can select among the following types:
Immediate. The report window will work as a virtual printer ( FIFO ), displaying messages in real
time.
From Log File. The Report will contain data extracted from the historical event log file of HPOV.
Object_Instance. From Browser drag the object(s) whose event log is required and drop into this
area. A wrongly dropped object should be deleted by means of the Delete popup option. The
presence of objects in this area automatically makes not meaningfull the content of the above
described ClassType box.
Users info
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
266 / 268
EVENT LOG
Open, to start a read operation on an ASCII file. This file is selected by the user by means of
a file filter.
Print all to print the Event Log content on the default printer.
Print Selected to print part of the Event Log content on the default printer.
still closed.
An example of event log is shown in Figure 182.
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
267 / 268
A
Alarm Propagation, 29
Alarms, 13
ASAP, 20
M
MAINTENANCE, 51
Measure, 225
MSSPRING request (trigger), 113
MStrail, 59
C
CONSISTENCY, 147
Consistency audit, 147
Consistency download, 148
N
E
NE, 77
Node, 87
NODE CONDITION, 127
NPE Ring, 113
EML, 75
F
fault localization, 51
Forced Switch / Span, 140
Forced Switch Ring, 137
P
Path, 53, 67
Physical Connection, 80
Physical connection, 55
PM, 223
Probable Causes, 13
protocol message, 113
protocol reply, 113
protocol request, 113
H
HOtrail, 56
I
Inhibition chain, 132
Intermediate nodes, 113
L
Lockout , 132
Lockout of Protection channels span, 113
Scenarios, 134
Serving nodes, 113
signal Fail, 139
Subnetwork, 84
END OF DOCUMENT
ED
01
SC.4:MAINTENANCE
3AL 61348 AA AA
268
268 / 268
INDEX
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Purpose of the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5
2 FUNCTIONALITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Introduction to Functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Supported EMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Supported NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
8
8
3 ROUTING ALGORITHM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 Routing Algorithm General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 Point to point paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 Unprotected path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 SNCP Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 D & C Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 Protection in Rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 Broadcast path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Routing inside rings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1 NPA routing attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 Service route in D&C paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3 Interworking scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
9
9
10
11
11
11
12
16
16
4 ALLOCATION OF RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Choice of link connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Choice of link connections in paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1 Choice of link connections in HO trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
21
21
21
5 NE CONSTRAINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
25
25
26
26
01
050207
ED
DATE
CHANGE NOTE
M.RAGNI ITAVE
V.PORRO ITAVE
APPRAISAL AUTHORITY
ORIGINATOR
1354RM REL.7.2
OPERATORS HANDBOOK
ED
01
1 / 80
26
29
32
36
38
39
39
40
41
42
42
43
45
45
45
47
48
49
49
50
51
52
53
53
53
63
63
63
7 RM OBJECTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 OTN WDM model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Integrated approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
69
73
73
8 OBJECT NAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75
77
ED
01
2 / 80
ED
01
7
10
12
12
13
14
15
16
17
17
18
18
19
19
26
29
32
33
34
38
39
40
46
48
49
50
51
52
54
54
55
55
56
56
58
59
59
61
62
67
67
68
69
70
72
3 / 80
ED
01
3AL 61348 AA AA
80
4 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
1 INTRODUCTION
1.1 Purpose of the document
This section describes the main features of the product and provides a general overview of the system
architecture, the managed equipments and the different functionalities provided by the Regional Manager.
ED
Transport Management
Concatenated AU4s
NPE 4Fiber
DB objects
Object names
01
5 / 80
ED
01
3AL 61348 AA AA
80
6 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
2 FUNCTIONALITIES
2.1 Introduction to Functionalities
The 1354RM is a network management system that has been designed to handle SDH regional networks.
The aim of this chapter is to give an overview of the 1354RM. (See Figure 1. ). The 1354RM covers the
1st NML level ( Network Management Layer). Figure 1. shows all the functional layers and the
communication protocols.
VPN
NML
Client
http
RMI
Web
VPN
Server Server
1354NN
M
ISN
Qnn
NML
1354RM
QB3
QB3*
EML
QB3*
QB3
NE
M: MANAGER
A: AGENT
ED
01
7 / 80
1353NM
1353WX
ED
01
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
3AL 61348 AA AA
80
8 / 80
3 ROUTING ALGORITHM
3.1 Routing Algorithm General
The routing algorithm acts during the allocation of path or trail, i.e. performs the operation that allocates
resources (link connections and CTPs) to the given path/trail and defines the cross connections (named
connections in topology)
Paths can be bidirectional pointtopoint, unidirectional pointtopoint and unidirectional broadcast. HO
trails are always bidirectional pointtopoint.
paths and trails can be:
not protected: a single route (main) is defined between the end points
protected SNCP: two routes (main and spare) are defined between the end points, in order to protect the
path against link faults and node faults;
protected D&C SNCP: in addition to main and spare, one or more service route are inserted in the path,
in order to protect it against multiple faults; (available only for point_to_point paths and trails)
protected in rings: the protection (spare) is added only inside rings
The basic algorithm has the objective of finding the minimum cost route between the end points (NAPs,
CAPs ).
The basic algorithm used is a particular customization of the Dijkstra Algorithm.
It occurs when at least one path constraint has been entered by the user
The algorithm proceeds in the following way.
1.First, the lowestcost main route is computed.
2.Then the spare route is computed with as less as possible overlaps with the main route.
ED
01
9 / 80
In this case the algorithm would find the path with the lowest cost main route, not the lowest sum of main
and spare route costs,costs. This is acceptable for a semiautomatic path allocation, since the user has
forced the routing to be not necessarily the best one.
FULLY AUTOMATIC VERSION
The Dijkstra Algorithm has been customized in order to minimize the sum of main and spare route costs,
with the minimum number of overlapped resources.
Add Service between specific end points. The user can specify the connections involved in the service
( without topological restrictions) choosing the direction to protect
ED
01
10 / 80
Notes
A path protected in ring has a protection just for the SNCP rings it crosses .
1354RM manages the possibility to insert a node in more than one ring, as shown in the following two pictures.
ED
01
11 / 80
In these cases, the routing algorithm is not based on minimum cost criteria, but it tries to avoid unnecessary
changes of rings.
3.4.1 NPA routing attributes
Two attributes are defined in NPA object:
ED
01
12 / 80
NPA Usage Cost: it is an extra cost used in the routing algorithm for the usage of the NPA. It ranges from
0 to 100, like the cost of physical connection;
NPA Reduction Cost Factor: the cost of physical connections inside a NPA is reduced by this factor in
the routing algorithm.
If equals 0, it has no effect. If equals 100, the cost becomes 0.
This reduction is introduced in order to compensate the cost for the usage of the ring.
By default, the NPA usage cost is 20 (like the default cost of a physical connection); the default NPA Reduction Cost Factor is 20%. The user is allowed to modify these values. In particular, putting both values to
0 results in a minimum cost routing.
Example: in Figure 3 below, using default values a path between N2 and N5 is routed through N3 and
N4 using only ring 2 (continuous line), even if the minimum cost route, taking into account only the physical
connection costs, bypasses N3 but uses both ring 1 and ring 2 (dashed line).
If equals 100, the NPA Usage Cost becomes 0 in the routing algorithm.
By default, the NPA Main & Spare Factor is 100%.
MSSPring D&C Factor: it is meaningful for SNCP or D&C SNCP paths/trails traversing MSSPrings. It
can be used to encourage, during spare calculation, the usage of D&C inside MSSPrings.
ED
01
13 / 80
As bigger is set the NPA Main & Spare Factor, as more main and spare are attracted to use the same rings,
resulting in a more ordered routing. This can be particularly useful for D&C paths/trails that use SNCP
rings.
Examples:
in Figure 6. below (case A), using default values, the main route of a path between N2 and N6 is routed
through N4 using only ring 1. The spare is routed through N1, N8 and N7 still using only SNCP ring 1 (continuous line), while the routing obtained disabling NPA Main & Spare Factor bypasses N8 but uses SNCP
ring 2 (dashed line), that wasnt used in the main route.
In fact, the cost of the chosen spare route (N2 N1 N8 N7 N6) for RM routing algorithm is 64: 4*16
(cost of four links), without any additional NPA usage cost; while the cost of the other route (N2 N1 N7
N6) for RM routing algorithm is 68: 3*16 (cost of three links) + 20 (access to ring 2).
not in all cases, the NPA Main & Spare Factor avoids the usage of new rings not used in the main route.
In Figure 6. below (case B), using default values, the main route of a path between N2 and N3 is routed
using only ring 2. The spare is routed through N4 (continuous line) using both SNCP ring 1 and ring 2, that
is the same route obtained disabling NPA Main & Spare Factor.
In fact, the cost of the chosen spare route (N2 N4 N3) for RM routing algorithm is 52: 2*16 (cost of two
links), + 20 (access to ring 1); while the cost of the route that uses only ring 2 (dashed line) is 96: 6*16 (cost
of six links), without any additional NPA usage cost.
Figure 6. NPA Main & Spare Factor effects in stacked SNCP rings
As bigger is the MSSPring D&C Factor, as more the routing algorithm should automatically route main
and spare in order to create D&CIC connections compared to other possible routes. When the cost of
the route with D&CIC is too high, other solutions are preferred.
Examples:
ED
01
14 / 80
In Figure 7. below, a MSSpring is crossed by a protected path in such a way that there are a lot of NEs
between primary and secondary nodes. In this case, using default MSSPring D&C Factor, the spare route
of the path is the one represented by the red continuous line. Increasing the value of the MSSPring D&C
Factor, the dashed route can be preferred, resulting in two D&C connections in nodes N1 and N2.
Figure 7. Routing in stacked MSSprings primary and secondary nodes not adjacent
2. In Figure 6 below, primary and secondary nodes in the MSSpring are adjacent. In this case, using
the default value of MSSPring D&C Factor, the spare route of the path is the red continuous line with
D&CIC connection in nodes N1 and N2. Reducing the value of the MSSPring D&C Factor, the dashed
route can be preferred.
ED
01
15 / 80
ED
01
16 / 80
As a result, two classic D&C connections are created in N3 and N5; one dual node D&C is created in N4.
ED
01
17 / 80
Figure 12. Collapsed dual node D&C interworking for 2f MSSpring configuration 1
ED
01
18 / 80
Figure 13. Collapsed dual node D&C interworking for 2f MSSpring configuration 2
In case of stacked MSSPrings, paths ending in different rings can be routed differently, depending on the
number of nodes between the end nodes. Note that SNCP connections, if supported by NEs, can be
created by the routing algorithm also inside MSSprings (Figure below case A).
ED
01
19 / 80
ED
01
3AL 61348 AA AA
80
20 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
4 ALLOCATION OF RESOURCES
Here it is described the algorithm used by RM in order to choose the network resources (link connections)
in the allocation of paths and HO trails.
first the routing algorithm chooses the routing links of the path;
then, for each routing link of the path, it chooses the first link connection(s) free, i.e. the one(s) with
the lowest time slot (e.g. 01/1/1.1), with the following exceptions:
inside a MSSP Ring (both two and four fibers), the time slot interchange is not possible at HO: the
algorithm chooses the first time slot that is free in all the routing links of the ring used by the HO path;
in case of NE constraint (the protected connections in all QB3* ADMs must have the same time slot
at west and east aggregate ports), the algorithm chooses the first time slot that is free in both the routing
links adjacent to that NE.
4.2.1 Choice of link connections in HO trails
The algorithm used for the choice of the link connections in the HO trails is the following.
first the routing algorithm chooses the routing links of the trail;
then, in each ring crossed by the HO trail, the algorithm chooses the first time slot that is free in all
the routing links used by the HO trail.
ED
01
21 / 80
ED
01
3AL 61348 AA AA
80
22 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
5 NE CONSTRAINTS
ED
01
23 / 80
ED
01
3AL 61348 AA AA
80
24 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
Alcatel implementation foresees rings made up by more than 16 nodes (64 maximum).
ED
01
25 / 80
Node 1
LP Traffic
LP Traffic
HP Traffic
Node 3
Node 4
Node 2
HP Traffic
6.2.1.1 node failures (equipment failure, natural accidents, power loss, software bugs, procedural incorrectness).
For each type of failures the adjacent node detects one of the following alarms:
a ) LOS
b ) LOF
ED
01
26 / 80
c)
d)
e)
MSAIS
MSEXBER
SD
Alarms from a) to d) are classified as Signal Failure (SF); alarm e) is classified as Signal Degrade
(SD).
SF alarms have higher priority than SD alarm. SF condition reflects traffic affected by defect, while SD
condition reflects traffic with signal degradations due to bit errors.
In 4F MSSPRing these alarms can be collected from working and protection line separately or the same
time according to failure type.
A fault condition present only on the working link determines a span protection: HP traffic is restored by
switching to the protection channels of the same span.
A fault condition present on both working and protection links determines a ring protection: the HP traffic
travelling the failed span is restored by switching it to the protection channels travelling in the opposite
direction (away from the failure).
There are two types of span and ring protection:
SF reason;
SD reason.
The activated protection mechanism results from the combination of the following conditions:
SF span protection
SD span protection
SF ring protection
working link failed and protection link failed on the same span;
working link failed and protection link degraded on the same span;
working link degraded and protection link failed on the same span.
SD ring protection
working link degraded and protection link degraded on the same span.
In the cases of only protection link failed or only protection link degraded on a span no protection mechanism is activated and LP traffic carried by the span is lost.
Considering a span the failure may be classified as:
unidirectional if the failure affects only one transmission direction (the alarm condition is detected
only on the node interfacing the span);
bidirectional if the failure affects both transmission direction (the alarm condition is detected on both
nodes interfacing the span).
When SF or SD condition disappear, HP traffic is restored on the working channels and the preceding
preempted LP traffic is restored on the protection channels.
WTR time is used to prevent frequent oscillations between protection and working channels due to intermittent fault.
ED
01
27 / 80
When a node determines that a switch is required (detected alarm or command from OS/CT), it originates
the appropriate bridge request via K bytes in both directions: short path and long path.
The destination request are the adjacent nodes.
In case of unidirectional failure, signalling on the short path permits faster switch execution because
across the failed span the node will typically receive the short path bridge request much sooner than the
long path bridge request.
When a not destination node (intermediate node) receives a bridge request, it goes to PassThrough state
transmitting the same received K bytes on the other direction. In this way source and destination nodes
can mantain direct K byte communication on the long path.
In case of bidirectional failure, such as a cable cut, the destination node will have detected the similar failure itself. It then generates a bridge request in the opposite direction around the ring.
bridge;
switch.
In case of SF protection the protocol foresees that on a node these operations may be performed together;
in case of SD protection these operations are always distinct.
ED
01
28 / 80
APS switching sequences follow ITU Rec. G.841 for 4F MS_SPRing protocol for transoceanic application. (Annex A)
Node 1
Node 4
Node 2
Node 3
Tx block
Working channel
Protection channel
Rx block
ED
01
29 / 80
In Transoceanic application the span protection does not involve all channels, but it is performed on a
AU4 basis in order to save those low priority time slots not required for the high priority traffic restore.
This operation requires the acknowledge of the time slots assignment in transmit and receive directions
for high and low priority traffic over the span.
6.2.2.1 Span switching mechanism
The sequences of the protection algorythm are the same used for the terrestrial rings.
A span protection switching evolves according to the following steps:
a)
a node (or both nodes if the failure is bidirectional) detects SF or SD condition only from working
fibre.
It enters in Switching state performing the following actions:
send span bridge request in both directions (SFS code or SDS code);
AIS forcing on all the time slots received from the working failed fibre (only for SF condition);
AIS forcing on the received low priority traffic channels to preempt (dropped or transmitted in
the opposite direction respect the failure).
b)
the other node interfacing the failed span receives a bridge request on the short path from its adjacent
node.
It enters in Switching state performing the following actions:
If the failure is unidirectional
send span bridge request on the long path and a Reverse Request with bridge status on the
short path;
AIS forcing on the received LP traffic channels to preempt (dropped or transmitted in the opposite direction);
Either in unidirectional and bidirectional case
span bridge (the node bridges only the working channels carrried on the failed span).
c)
the node interfacing the failed span, upon reception of the bridge acknowledgement on the short path
from adjacent node, executes:
span switch (the node switches only the protection channels carrying the restored high priority
traffic);
d)
the other node, upon reception of the bridge & switch acknowledgement on the short path from adjacent node, executes:
span switch (the node switches only the protection channels carrying the restored high priority
traffic);
e)
all the other ring intermediate nodes, on the reception of the first long path bridge request received
from one of the node interfacing the failed span, enter in kbyte PassThrough state.
In this state the node only transmits the k bytes received from the opposite side and does not perform
any action on the own working and protection channels.
So all these nodes know the presence of a span switching, even if they are not directly involved.
ED
01
30 / 80
In case of unidirectional failure also the other protection fibre of the same span is used to carry the high
priority traffic on the other direction.
AIS removing on all the time slots received from the working fibre (only for clearing of SF condition);
AIS removing on all the time slots received from the working fibre (only for clearing of SF condition);
b)
AIS removing on all the time slots received from the working fibre (only for clearing of SF condition);
the adjacent node, upon reception of the WTR bridge request on the short path:
sends out Reverse Request on the short path and WTR on the long path.
b)
when WTR interval expires, the node performs the following actions:
drop span switch restoring the high priority traffic received on working channels (AIS on these
flows is nomore present);
c)
the adjacent node, upon reception of the No Request code on the short path, performs the following
actions:
drop span switch restoring the high priority traffic on the other direction;
drop bridge switch (reconnecting on the released protection channels the low priority channels);
d)
the initial failed node, upon reception of the Idle status on the short path, performs:
drop its bridge switch (reconnecting on the released protection channels the low priority channels);
e)
Both nodes, upon reception of the Idle status on the short path, perform:
AIS removing on the preempted low priority channels (both drop and passthrough sides). Now
the low priority traffic is restored.
f)
All the other nodes, upon reception of the Idle code from both sides, return in the Idle state.
ED
01
31 / 80
Nodes belonging to a Transoceanic ring have a different behaviour respect to a nonTransoceanic ring.
The below figure shows an example of ring connection.
HP traffic
LP traffic
Connection under evaluation
it is carried via NE 5632 in HP channels
Figure which follows shows a ring protection switching involved in a nonTransoceanic ring.
ED
01
32 / 80
HP traffic
LP traffic
The connection protection is carried via:
NE 56 on HP channels,
NE 654123 on LP channels,
NE 32 on HP channels.
During a ring switch, the node adjacent the failure bridges the high priority traffic that were entering on the
failed span onto the protection fibre transmitting in the opposite direction (loopback action). This bridged
traffic travels the long way around the ring on the protection fibres to the other node interfacing the failure.
Here it is switched back onto the working channels (loopback action) rebulding in this way the interrupted
path from the source node to the destination node.
In the other direction the high priority traffic is bridged and switched in the same manner.
Intermediate nodes are not involved in switching operations.
ED
01
33 / 80
HP traffic
OCEAN
LP traffic
The connection protection is carried via:
NE 5412 on LP channels
in transoceanic application only the protection channels carrying the working channels affected by
the failure are managed; in nontransoceanic application all span protection channels are managed.
in transoceanic application also intermediate nodes are involved in bridge and switch operations.
After the fault event between Node 6 and Node 3, the LP3 Connection is lost (the AU4 is used to carry
the HP Traffic), the LP1 Connection is lost however for the failure, but instead the LP2 Connection is not
lost.
ED
01
34 / 80
These LP paths are left in the own time slots and no action is done on them.
Then there is no need for a subsequent LP traffic restoration functionality.
Ring switching needs that every node of the ring (the adjacent at the failure and the intermediate ones)
knows if its HP and LP inserted/dropped traffic is affected by the failure. HP and LP traffic maps must be
provisioned on all the ring nodes.
For HP traffic the algorithm individuates if the path is affected by failure and then must be restored on
protection channels; for LP traffic the algorithm individuates if the path must be interrupted to restore the
corresponding HP path.
To operate correctly ring switching and restoring mechanisms need a set of operations (bridge, switch,
AIS forcing) executed on more ring nodes in a synchronized way to avoid temporary misconnection on
HP and LP connections.
6.2.3.4 Ring switching mechanism
Ring switching of a HP path in transoceanic application consists in dynamically building a new path on a
portion of the ring using the corrispondent time slot of the protection channels. This is done without causing
misconnection on the lost LP paths occupying the same channels and on the HP connection itself in reconstruction phase.
The basic mechanism of ring protection involves the ring nodes in two sequencially distinct phases:
first phase: building of HP path on protection channels and preemption of affected LP paths
Ring restoring of a HP path in transoceanic application consists in the reconnection of the provisioned HP
path and rebuilding plus restoring of previous preempted LP paths. This must be done without causing
misconnection on HP path and restored LP paths.
The basic mechanism of ring restoring involves the ring nodes in three sequencially distinct phases:
second phase: deletion of HP path on protection channels and rebuilding of provisioned LP paths
ED
01
35 / 80
first phase: reconnection of HP path on working channels, deletion of HP path on protection channels
and rebuilding of provisioned LP paths
In case 1) the execution of ring switching will determine the restoring of the lost HP connections (the restored HP path on protection channels will cross all the other span failures present of the ring that does
not interrupt the path).
In case 2) the execution of multiple span switchings on the failed spans will determine the restoring of the
lost HP connections.
In case 3) the execution of ring protection will surely determine the restoring of the lost HP connection (the
restored HP path on protection channels will cross the remaining span failures present on the ring that do
not interrupt the path).
Instead the execution of span switchings however does not guarantee that the HP path is reestablished
(provisioned HP path crosses the ring failed span and then it results still interrupted).
If the aim is to restore the maximum number of HP connections on the ring between two protection mechanism the priority should be done to ring switching instead of span switching.
In Transoceanic application in case of contemporary presence of span and ring failures the optimal protection algorythm is:
submit to ring switching the time slots carrying HP paths affected by ring failure
ED
01
36 / 80
The operations belonging to a phase can be tied to a timer whose duration must be sufficient to guarantee
that signalling arrives to all ring nodes.
submit to span switching the remaining time slots not involved in ring switching carrying HP paths
affected by span failures (in case of multiple span failures the involved time slots could be different
on each span according to the occupation of new restored HP path for ring switching).
On a ring involved in ring protection for two or more ring failure, clearing of ring failure determines the
capability to reobtain some other HP traffic: HP paths no more directly affected by the failure; HP paths
affected by the remaining failures for which the restored HP path on protection channels is available.
In case of cleared failure the situation on the ring is:
restored HP paths on protection channels are mantained because the provisioned HP path is still
affected by other failures (with multiple ring failures a restored HP path implies that the provisioned
HP path crosses all present ring failures);
provisioned HP paths no more affected by failures are reconnected without any switching operation
(previously during appearance of ring failure corrispondent provisioned HP path was restored);
some provisioned HP paths still affected by remaining failures are restored on protection channels
(this occurs only for the paths which have restored HP path on protection channels no more interrupted on the ring);
provisioned LP paths no more affected by failures and not preempted for new HP restoring are re
connected without any switching operation (previously during appearance of ring failure all the LP
paths not involved in ring switching were reconstituted).
With one or more ring failures already present in the ring another ring failure causes a partial ring restoring
operation involving the HP paths that cannot more be restored via protection channels on the other way.
With two or more ring failures present in the ring the clearing of a ring failure causes a partial ring switching
operation involving the HP paths for which the restored path on protection channels is no more interrupted.
6.2.4.4 Ring Segmentation
ED
01
37 / 80
A broadcast connection is an unidirectional pointmultipoints link. An unique transmitting source is connected to many receiving destinations.
In the traffic map this connection is represented as a path in which a node is the insertion point and more
nodes are drop points. On some nodes the flow enters from an aggregate side; then exits from the other
aggregate side and from tributary side. The node needs the contemporary provisioning of a time slot in
passthrough and drop connections.
This type of connection can be configured in a Transoceanic ring.
The figure below shows an example of broadcast connection carried by 4F ring on working channels. The
signal is transmitted by node 5 and received by nodes 1,2,3.
The provisioning of the connection is as follows:
node 5 insertion;
node 6 passthrough;
node 1 drop.
HP traffic
LP traffic
Broadcast connection
ED
01
38 / 80
4F Transoceanic MSSPRing ring protection mechanism is used also to restore broadcast paths.
6.3.2 Failure affecting all drop points
If the ring failure occurs on the span connecting source and nearest sink node, the signal does not reach
any drop point.
HP traffic
LP traffic
Broadcast connection
Protected broadcast connection
ED
01
39 / 80
If the ring failure occurs on a span included between two sink nodes, the signal still reaches some drop
points.
HP traffic
LP traffic
Broadcast connection
Protected broadcast connection
ED
01
40 / 80
ED
01
41 / 80
During both span and ring protection mechanisms the node determines the time slots of the LP channels
involved in a particular action.
6.4.1 Ring path restoring algorythm
During ring switching each node of the ring (not only those interfacing the failure) must determine which
are the LP paths to preempt leaving free the protection time slots to reroute the HP paths.
This activity is realized by ring path restoring algorythm.
The following information are required:
node identifier;
ring map;
traffic maps.
The input parameter is the fault localization.
According to the current node position the algorythm is able to determine which are the LP paths to preempt.
Step 1) Construction of the new HP connections on protection channels.
To determine which are the new connections to build over the protection channels as a consequence of
a failure, each node must know the traffic map of the working paths in the overall ring.
First the algorythm individuates the HP connections cancelled in consequence of the failure.
Then it rebuilds the cancelled connections on the protection channels considering that the new paths travel
in the opposite direction.
Step 2) Determination on the local node of the transmitted and received AU4 time slots of the protection
channels to preempt.
Comparing the localization of the occupied time slots of the new connections with the provisioned LP paths
involved in the node (protection path dropped, inserted or passthrouged by the node) the algorythm determines which are the LP channels to cancel.
The following tables reports the provisioned LP connections to preempt and the provisioned LP connections not involved in protection and then that are mantained on the ring.
At the end is reported the final status of the connections on working and protection channels of the ring
after a ring switching.
LP channels to preempt among those provisioned in drop for both directions. The node performs
AIS forcing action on them.
new built HP paths on protection channel time slots in which the node is involved. In correspondence
to the used time slot the node performs the following actions:
ED
01
42 / 80
In case of multiple failures the algorythm starts from the current traffic maps of the HP connections on working and protection channels on the ring (originated by means of previous failure) to determine:
the protection channels to preempt for span switching when is already present a ring failure (they may
be provisioned LP channels or channels already used for ring protection);
the LP paths to restore when there are more ring failure conditions;
some new HP paths to rebuild (and consequent LP paths to preempt) and other LP paths to restore
when one of the ring failure conditions is cleared.
They will be subdivided partly on tributary side for AIS forcing on dropped side and partly on aggregate
side for AIS forcing on passthrough side.
The same time slots are those involved on tributary side and aggregate main opposite side for span switch
operation.
It compares HP and LP connections transmission side to determine:
ED
01
43 / 80
a)
Lockout of protection
Force Span Switch
Force Ring Switch
Manual Span Switch
Manual Ring Switch
Exercise Span
Exercise Ring
Clear Command
Lockout protection
Force Span Switch
Force Ring Switch
Manual Span Switch
Manual Ring Switch
Exercise Span
Exercise Ring
Clear Command
The command Exercise Span exercises span protection of the requested channel without completing the
actual bridge & switch. The command is issued and the responses are checked but no normal traffic is
affected.
The command Exercise Ring exercises ring protection of the requested channel without completing the
actual bridge & switch. The command is issued and the responses are checked but no normal traffic is
affected.
b)
c)
Switch Status: Idle, Span Bridge, Span Switch, Span Bridge and Switch, Ring Bridge, Ring Switch,
Ring Bridge and Switch
d)
Protocol errors: the K1, K2, K3 pattern is not coherent with the status of the Transoceanic MS
SPring State machine.
ED
01
44 / 80
failure on one of the two interconnection links between rings (from P of a ring to S of the other ring);
failure on a link included between primary and secondary node carrying the secondary circuit;
failure on the interconnection link between P and S nodes carrying the secondary circuit.
The second example illustrates the selection of the flows coming from aggregate opposite side in the following conditions:
failure on the interconnection link between P and S nodes carrying the service circuit;
failure on a link included between primary and secondary node carrying the service circuit.
D&C functionality associated with Transoceanic MSSPRing protection mechanism causes a completely
different interaction respect to notTransoceanic application, particularly in consequence of the bridge
and switch operations performed by intermediate nodes.
ED
01
45 / 80
T
P
Service circuit
Secondary circuit
P: Primary node
S: Secondary node
T: Termination node
Service Selector
ED
01
46 / 80
ED
01
47 / 80
Failures affecting D&C path from primary to termination nodes are restored by the Transoceanic MS
SPRing protection mechanism interacting with D&C function.
LP channels carrying secondary circuit may be used to restore HP paths when occurs particular span and
ring failures.
Infact a span failure on a span included between primary and secondary nodes may cause the use of secondary circuit channel to restore corresponding HP channel.
Secondary circuit channels may be preempted to carry restored HP path on protection channels even in
case of ring failure affecting a HP path carried by the same time slot of the secondary circuit LP channel.
The preemption of secondary circuits is signalled to avoid misconnection on D&C protected path.
This is done forcing AIS to the D&C secondary circuit on the primary node before arrival of the flow on
Service Selector.
Figure 24. illustrates the case of a D&C path selecting secondary circuit on LP channel subsequently preempted because of span failure.
Failures are:
HP AU4#i
LP AU4#i
Node P
Node S
HP AU4#i
AIS
LP AU4#i
Node P
Node S
HP channels
LP channels
D&C Selector
ED
01
48 / 80
span failure occurring on the span adjacent primary node on Service Selector side (applicable for
secondary circuit on HP and LP channels)
ring failure on a span included between primary and termination nodes (for secondary circuit on HP
channels)
ring failure on a span included between primary and termination nodes (for secondary circuit on LP
channels).
T
P
Service Selector
Figure 25. D&C protection management: span failure on link adjacent Service Selector
For secondary circuit carried on HP channels , the secondary circuit is selected executing a crossconnection operation because the signal comes from opposite side working line.
For secondary circuit carried on LPchannels, the secondary circuit is selected executing a passthrough
connection operation because the signal comes from opposite side protection line.
ED
01
49 / 80
T
P
Service Selector
Bridge connection
This case is managed only by Transoceanic MSSPRing manager. The D&C path is represented on traffic
map as HP connection having secondary and termination nodes as drop/insert points.
ED
01
50 / 80
6.5.8 Ring failure on span included between primary and termination nodes (HP case)
Figure 27. reports the behaviour of D&C function together with Transoceanic MSSPRing when a failure
occurs on a span or node included between primary and termination node of a D&C path.
T
P
Service Selector
Figure 27. D&C protection management: ring failure on link between P and T nodes (HP case)
According to Transoceanic concept the selected D&C path must be routed in the opposite way on the
corresponding protection channel.
The primary node still performs the Service Selector function, but moved to the other side of the node.
The selection is always between the service circuit coming from tributary side and the secondary circuit
coming from secondary node on aggregate side. The selected flow is transmitted back to the corresponding protection channel toward the secondary node.
Node operation is as follows:
the D&C function, localized on the opposite side determines the circuit
the Transoceanic MSSPRing function performs ring bridge and switch operations of the D&C flow.
Then during the persistence of the failure the node operation is:
when occurs an alarm condition on one of the two available circuits, the D&C function of the opposite
side performs the selection connecting one of the flows to the protection channel used to restore the
HP D&C path.
When the flow coming from aggregate side must be connected, the node must perform a loopback operation from working to protection channel. ( not common in Transoceanic application)
This choice realizes that a flow travels twice the link between P and S nodes (a first time from S to P and
then from P to S) and seems not in accordance with Transoceanic concept. But it is also true that primary
and secondary nodes of a D&C protected path usually are not positioned as nodes adjacent to an oceanic
link.
ED
01
51 / 80
The following figure reports the behaviour of D&C function together Transoceanic MSSPRing when occurs a failure on a span or node included between primary and termination node of a D&C path.
T
P
Service Selector
Bridge connection
Figure 28. D&C protection management: ring failure on link between P and T nodes (LP case)
Differently from secondary circuit on HP channels in this case it is not possible to reroute toward opposite
way D&C path on primary node after selection because the corresponding LP channel is used to transmit
the secondary circuit on the other direction.
D&C selection capability is lost; the unique possibility is to the route secondary circuit to the termination
node crossing other direction of the ring. This is done using the same protection channels and executing
bridge operation on secondary node and switch operation on termination node.
ED
01
52 / 80
6.5.9 Ring failure on span included between primary and termination nodes (LP case)
6.6 Features
The provided features are in accordance with ITUT Recommendation G.841, in particular the following
definitions are used:
request node: a node that generates either a protocol request or protocol reply (other than NR!). The pair
of nodes sending each other protocol request/reply are peer request nodes.
intermediate node: the node that is not a request node. It is always in the passthrough state. If such
a node executes bridge and switch of at least one AU4 it is also a bridge&switch node.
6.6.1 General description of MSSPRING protection scheme
Multiplex Section Shared Protection Ring (MSSPRING) is an SDH trail protection scheme, as it is
described in ITUT Recommendation G.841, section 6.1.
The MSSPRING application described in G.841, sections 6.1 and 7.2 is called Classic MSSPRING
application.
The MSSPRING application described in G.841, sections 6.2 and Annex A is called Transoceanic
MSSPRING application.
6.6.2 MS shared protection rings Transoceanic application
The application is fully compliant with G.841, Annex A.
6.6.2.1 Network objectives
The application is fully compliant with G.841, Annex A, section A.2 .For transoceanic applications of MS
additional network objectives apply:
1)
Switch time. The switch completion time is less than 300 milliseconds, independent of whether
the ring is carrying extra traffic.
2)
Extent of protection: b) The ring restores all traffic possible, even under conditions of multiple
bridge requests of the same priority.
3)
During a failure, preempted extra traffic can be reestablished on the protection channels
not used to restore the normal traffic.
b)
For transoceanic applications, ring maps are used to switch traffic affected by a failure at
intermediate nodes. A mechanism that autoprovisions the data required for these maps,
and maintains its consistency.
c)
If a ring switch exists and a failure of equal priority occurs on another span requiring a ring
switch, then, if the priority of the bridge request is Signal Fail (Ring) or higher, both ring
switches are established resulting in the ring segmenting into two separate segments.
It is assumed that the span switch must be performed on a perAU4 basis. In this way, an unloaded
Normal AU4 will not be bridged & switched, and the corresponding ET AU4 will not be preempted.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figures which follow show examples of Routing in Working and Routing in Protection schemes.
ED
01
53 / 80
P
working channels
protection channels
N
E
F
P
working channels
protection channels
N
ED
01
54 / 80
P
working channels
protection channels
N
E
F
P
working channels
protection channels
N
ED
01
55 / 80
P
working channels
protection channels
N
E
F
= selector
P
working channels
protection channels
N
E
F
= selector
ED
01
56 / 80
the insert node for the given path (see Figure 29. , node A) shall see the outgoing pointtomultipoint
path as being inserted locally and dropped at the farthest drop node (L);
each node dropping the incoming pointtomultipoint path shall see it as being inserted at the insert
node (A) and dropped locally. In other words, the drop&continue connection is seen as a normal drop
connection plus a passthrough connection. Every such node shall also be aware that the drop
connection is part of a pointtomultipoint path.
According to the above rules, any failure between the insert node and the first drop node, not including
the insert node failure (see Figure 35. ), is handled as follows:
Because of the ring signaling, the insert node (A) knows that a ring failure has occurred between D
and E, and bridges the affected path onto the protection channel that travels away from the failure.
Node L realizes that the failure is affecting the pointtomultipoint path it is receiving from A (because
the ring traffic map declares the path as AL, and the failure is in between) and, knowing to be the
farthest drop node for that path, drops the extratraffic according to the usual rules and converts its
drop/West connection of the failed pointtomultipoint path into a drop&continue/East of the
corresponding protection channel in the opposite direction. The drop part is necessary to receive
the good path from A, whereas the continue is necessary to forward that good path to nodes G and
H.
Likewise, node H realizes that the failure is affecting the pointtomultipoint path it is receiving from
A (because the ring traffic map declares the path as AG, and the failure is in between) and, knowing
to be an intermediate drop node for that path, converts its drop&continue/West connection into a
drop&continue/East of the corresponding protection channel in the opposite direction.
Node G realizes that the failure is affecting the pointtomultipoint path it is receiving from A and,
knowing to be the first drop node for that path, converts its drop&continue/West connection into a
drop/East of the corresponding protection channel in the opposite direction.
As a consequence of that failure, this mechanism brings about an alternative path traveling on the
protection channel in the opposite direction and feeding all the drop nodes of the pointtomultipoint path
a good signal as a substitute for the failed one.
A failure between the first drop node and the farthest drop node (see Figure 36. ), both not included,
is handled as follows:
Node A realizes that only the nodes preceding the ring failure (G) are still reachable: for ring
interconnection purposes, this is sufficient to guarantee that a good tributary can still be sent by A
to the other ring, and thus no switching action is required at all.
If the capability of sending to all the drop nodes is to be preserved upon single ring failure, it is
necessary that node A bridges the inserted path onto the protection channel in order to reach the
affected nodes (H and L); moreover, the nodes beyond the failure (H and L) shall behave as in above
case, Node G realizes that the failure is not affecting the pointtomultipoint path it is receiving from
A and does no switching at all.
The original pointtomultipoint path is therefore split into
a pointtomultipoint path on the working channel, from the insert node through the farthest
unaffected drop node (G), and
ED
01
57 / 80
A failure of the farthest drop node (see Figure 37. ) is handled as follows:
Node A does no switching because the node being declared by its ring traffic map as destination of
the pointtomultipoint path it is inserting is faulty.
All the intermediate drop nodes are unaffected by the failure and keep receiving the path from A on
the working channel.
P
working channels
protection channels
N
E
G
ED
01
58 / 80
P
working channels
protection channels
N
E
F
P
working channels
protection channels
N
E
F
ED
01
59 / 80
As the termination node A bridges and switches the path onto the protection channel away from the failure,
the two interconnection nodes behave as follows (drop & continue/working method):
the Primary node loops the path after the selector back onto the protection channel toward the
secondary node.
the Secondary node is not impacted, as it continues transmitting/receiving to/from the Primary node
using the same side.
This is the only event where a loopback is allowed with Transoceanic application. The increase of distance
to travel (all the spans between the Primary and Secondary node are gone through twice, if the secondary
interconnection is selected) is considered negligible. Note that such a loopback does not imply any
potential for misconneciton, as the paths destined to the failed node (in the event of node failure) are not
bridged & switched.
In this way the dualnode interconnection capability is preserved, still allowing the ring selfhealing when
a potential additional fault affects the secondary path (the handoff to the Secondary node).
As for the drop & continue/protection method, the loopback is not applicable as the continue portion is
preempted by the path being bridged & switched by the termination node A onto the protection channel
away from the failure to reach the Primary node. The secondary interconnection is therefore no longer
available.
6.6.2.2.1.2 Failure of the secondary node
The same behavior recommended for Classic MSSPRING applies to both drop & continue/working and
/protection methods:
for a failure of the secondary node, the tributary at the terminating node is unaffected, since it receives
its tributary from the primary node. Because of the ring signaling, the Primary node knows that the
secondary node has failed. The Primary node chooses its tributary from the traffic entering it from the other
ring.
6.6.2.2.1.3 Failure between the interconnection nodes
A failure occurring between the two interconnection nodes, is dealt with in the same way as in the
Secondary node failure case. The secondary interconnection is no longer available.
ED
01
60 / 80
TX
SNCP
ED
01
B
E
C
NPE
RX
SNCP
SNCP
RX
A
B
NPE
C
F
E
D
Equipment=1664SM
SNCP
TX
3AL 61348 AA AA
80
61 / 80
SNCP
ED
01
B
E
C
NPE
TX
RX
SNCP
SNCP
RX
A
B
NPE
C
F
E
D
Equipment=1670SM
SNCP
TX
3AL 61348 AA AA
80
62 / 80
The feature allows the displaying of the MSTrail (main and spare) related to the Physical Connection in
the 4f MSSPRing Protection Block view.
ED
01
63 / 80
ED
01
3AL 61348 AA AA
80
64 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
7 RM OBJECTS
The database contains the object classes which are described in the following.
NtwDomain
The ntwDomain (network domain) is the whole area controlled by the 1354RM.
Ntw (Network)
The network comprises all the interconnected SDH equipment. A network comprises subnetworks.
A network object instance has an associated symbol and a submap. The symbol represents the network
in the root submap, and clicking on it the corresponding submap can be opened.
EmlDomain
An EML domain is maintained by a single EML OS. This object is generated in order to inform the Operator
on the OS a certain NE belongs to.
An EMLdomain contains the NEs managed by the EML OS.
NE
A Network Element is an SDH telecommunication equipment managed by the OS.
A node has an associated symbol and a submap. The symbol is used to represent the node in the submap
describing the topology of the subnetwork or ET where the node is contained. Clicking on the node, the
asociated submap will be opened. This submap contains the uploaded ports.
Physical Connection
A physical connection connects two ports in the network. These two ports belong to different NEs and must
have the same transmission rate.
A physical connection has a symbol, that is used to represent the physical connection in the submap
associated.
Site
The site is the name of the physical location of the object.
Port
The port represents the physical accesses of the SDH equipment.
A port is a physical interface of a node. Two ports with the same interface can be connected by means
of a physical connection.
A port has a graphical symbol, that is used to represent the port in the submap associated to the node.
Path
ED
01
65 / 80
The subnetwork is a partitioning of the NML network. It contains Elementary topologies and
interconnected Nodes.
A subnetwork is a grouping of nodes and ETs.
A subnetwork has a symbol and a submap.
ConnInTopol
The connInTopol (connection in topology) describes a generic connection (subnetwork connection,
network connection) between two or more ends (they can be Naps,Caps or Ctps) to realize a path in any
partitioning level.
A connInTopol between Naps corresponds to a path.
Ntw
sbn2
sbn1
connInTopol
Nap1
Nap2
It represents both the Msctp and the mscap entities related to an SDH physical port at MS layer.
ED
01
66 / 80
Sbn
NE
nap
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
connInTopol
nap
LOPL
tdm
HOPL
connInTopol
MSL
msctpcap
msctpcap
LOlink connection
LO
ctp
ctp
HOtrail
cap
cap
HO
HO link connection
ctp
ctp
ms trail
msctpcap
MS
msctpcap
ED
01
67 / 80
The figure which follows describes the objects involved in the structure.
NE
nap
nap
connInTopol
connInTopol
ctp3rd ord
LOlc(TU3#1)
tdm
LOPL
tdm
140cap1
(VC4)
#1
LOPL
140cap1
(VC4) #1
HOtrail(VC4S1)
connInTopol
connInTopol
ctp16
HOlc ( AU4#16)
HOlc ( AU4#1)
ctp1
HOPL
HOPL
MSL
MSL
ms trail
mstp
mstp
mstp
physConn
mstp
nap
nap
LOlc(TU3#1)
ctp3rd ord
140cap1
(VC4)
#1
140cap1
(VC4) #1
HOtrail(VC4S1)
connInTopol
ctp16
ctp1
connInTopol
HOlc ( AU4#16)
ctp16
HOlc ( AU4#1)
HOlc ( AU4#16)
ctp1
ms trail
mstp
physConn
ctp1
HOlc ( AU4#1)
connInTopol
ms trail
mstp
ctp16
mstp
mstp
physConn
ED
01
68 / 80
NE
OCH ( colored )
OMS
OPSUNI
In particular:
ED
OMS TPs
01
69 / 80
UNI ports ( OGPI ) of WDM NEs ( e.g. back to back with or without transponders )
OCH Link Connections connection ( LCs ) logically interconnecting OCH CTPs at the same
frequency
OCH LC
OCHCTP
OCHCTP
OMS Trail
OMS TP
OMS TP
OTS Phys Conn
OTS Port
OTS Port
Figure 44. WDM model.
OCH trails representing the logical interconnections between OCH TTPs crossing OCH CTPs,
OCH LCs and OCH cross connections
ED
OADMs provide OCH passthrough at the same Lambda (passthrough of the extraband),
called by 1354RM, OCH passthrough crossconnection.
The CLIENT LAYER represents the CBR / TDM service of the WDM network.
The Client path is the representation of this service. In case of SDH the client path is a trail at the
regenerator section layer.
The Client Layer includes:
Client CTPs on transponders, that is TPs on I/O directions like rsCTPs, gdcCTPs, ochgdc
CTPs)
70 / 80
ED
Client paths interconnecting client terminations ( client NAPs ) with a sequence of LCs and
crossconnections.
The OCH ( B / W ) is a technical layer added at RM level to balance the model mainly in case of
SDH interworking. It contains objects with no counterpart in the NE.
01
71 / 80
PATH
.
LOlc(TU3#1)
nap
LOPL
(VC4)
140cap1
(VC4)
#1
HOtrail(VC4S1)
140cap1
connInTopol
connInTopol
ctp16
HOlc ( AU4#16)
HOlc ( AU4#1)
ctp1
HOPL
MSL
ms trail
mstp
mstp
OSPI
OSPI
physConn
rsttp
rsttp
4x2.5
rsctp
clientctp
client lc
clientctp
client lc
client lc
ochtrail
ochtrail
4x2.5
ochttp
ochctp
ochtrail
rsctp
4x2.5
ochtrail
ochttp
ochttp
OCHlc
client lc
OCHlc
OCHlc
ochctp
OCHlc
ochctp
ochctp
omstrail
omstrail
OMSTP
OMSTP
opsphyscon
OPS
opsport
SDH
OSPIclone
otsport
otsport
LT
opsphyscon
OPS
otsphyscon
OTS
otsphyscon
OTS
otsport
OADM
opsport
otsport
SDH
LT
OSPIclone
ED
01
72 / 80
connInTopol
nap
7.3 Functions
1354RM allows:
upload of WDM NEs and ports from 1353SH
placement of WDM NEs into RM topologies
definition of OTS links and single lambda interconnections (OPS) between WDM NEs. OPS links are
needed for coloured or B/W backtoback interconnections
declaration of connectivity between SDH and WDM networks on a single map
the upload of an existing connectivity at OCH and client layer during the implementation of physical connections. The uploaded connectivity first generates raw connections and then OCH trails and in turn client
raw connections and client paths.
The type of WDM connection is OPS for SDHWDM connection, OTS for WDMWDM connection.
ED
01
73 / 80
ED
01
3AL 61348 AA AA
80
74 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
8 OBJECT NAMES
AZ, az, 09, all special characters except: tilde (~), backslash (\), pipe (|), double quote (), TAB
ED
path
EML Domain
Netw Domain
ne
port
physical Conn
routing link
network
subnetwork
et (ring)
node
trail
perf. measure
pmTransport
TCA Profile
pmNE
pmTp
pmCountRep
tcRProfile
pmTranStProfile
pmRatioProfile
pmQpgProfile
aSSAProfile
raw connection
sublink pointer
01
86
32
24
32
88
92
46
24
24
24
32
94
100
100
48
100
100
24
24
24
24
24
32
86
44
75 / 80
ED
01
3AL 61348 AA AA
80
76 / 80
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
AIS
ALS
APS
ASAP
AU
Administrative Unit
AU PJC
BER
CDROM
CCITT
CT
Craft Terminal
DCN
DS
Degraded Signal
ECC
EML
EPS
FAD
FERF
FLS
Gbit/s
GNE
HMI
HOA
HO Matrix
HPA
HPC
HPT
HP
Hewlett Packard
HPOV
ED
01
77 / 80
HPUX
HPVUE
HVC
IEEE
IM
Information Manager
Kbit/s
LAN
LOF
Loss Of Frame
LO Matrix
LOP
Loss Of Pointer
LOS
Loss Of Signal
LOT
Loss Of Tributary
LPA
LPC
LPT
LVC
Mbit/s
MIB
MS
Multiplex Section
MSSPRING
MSP
MST
NAD
NAP
NE
Network Element
NML
NPE
NSAP
OFS
ED
01
HPOVW
78 / 80
OS
Operation System
PDH
PI
Physical Interface
PPI
PTM
RS
Regenerator Section
RST
SA
Section Adaptation
SCSI
SDH
SF
Signal Failure
SPI
STMN
TF
Transmit Fail
TMN
TN
Telecommunications Network
TP
Termination Point
TU
Tributary Unit
TU PJC
USM
VC
Virtual Container
XC
CrossConnect
ED
01
79 / 80
END OF DOCUMENT
ED
01
3AL 61348 AA AA
80
80 / 80
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5
2 WDM TECHNOLOGY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 WDM Layer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 WDM Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 WDM Equipments managed by 1354RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 WDM NE configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Layering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Network construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4 Integrated management map view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1 Circuit provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.5 Raw connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.6 Data service VC4v Management (4xANY board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.7 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.8 PRC module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.9 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.10 B1 based PM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11 Acronims . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.1 Topological Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.2 Physical Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.3 Transport Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.11.4 Reference Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12 WDM Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.1 OTS conn. navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.12.2 OPS conn. navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.13 WDM network create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.14 Raw Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.14.1 Completed raw connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.15 Optical Network Modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.15.1 Adding a transponder on 1640WM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
9
9
11
11
15
16
16
18
19
21
22
22
23
23
24
24
24
24
25
27
27
34
38
47
50
55
55
01
050207
ED
DATE
CHANGE NOTE
M.RAGNI
V.PORRO
APPRAISAL AUTHORITY
ORIGINATOR
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
1 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
2 / 92
ED
01
SC. 6: WDM
9
10
11
12
12
13
13
14
15
16
17
17
27
28
29
30
31
32
33
34
35
36
37
39
40
41
42
43
44
44
45
46
48
50
51
52
53
54
55
56
57
58
59
61
63
64
64
65
66
67
It. 01
3AL 61348 AA AA
92
3 / 92
ED
01
SC. 6: WDM
69
70
71
72
73
74
74
75
76
77
78
79
80
81
82
83
88
89
91
It. 01
3AL 61348 AA AA
92
4 / 92
1 INTRODUCTION
1.1 Introduction
This document aims at introducing the 1354RM WDM working environment, to the users of the system,
and explain the existing 1354RM functionalities
ED
WDM Technology
WDM Navigation
Convert path/trail
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
5 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
6 / 92
2 WDM TECHNOLOGY
The introduction of WDM technology in transport networks is the first step toward Optical Transport Networks (OTN).
The evolution of WDM Network Elements (NE) from line systems with fixed wavelength add/drop capability to more flexible equipments (Optical Add Drop Multiplexers OADMs and Optical Cross Connect
OXC ) will allow the manipulation of optical channels as time slots are currently managed in the TDM networks.
Since the availability of a network management system is a key feature for transport networks, the current
NML OS set of applications (packaged into the 1354RM product) has to face this new technology by
introducing new functionality.
These functionalities are based on preOTN concepts, i.e. without the management of the overhead and
functionalities described in ITUT G.709 Recommendation.
ACHRONYMS
ATM
CAP
CTP
DVB
EML
ESCON
FDDI
FEC
IPC
InterProcess Communication
MIB
NAP
NE
Network Elements
NML
NML
OADM
OCC
OCh
Optical Channel
OCG
OH
OverHead
OMS
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
7 / 92
OPS
OS
Operation System
OSC
OTH
OTM
OTN
OTS
OXC
Optical CrossConnect
RC
Raw Connection
RSOH
SDH
SNCP
SONET
STMn
TDM
TE
TP
TTP
WDM
WLA
WaveLength Adapter
ED
01
OOS
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
8 / 92
The Client path may also represent the transport endservice delivered by an operator, if only the OTN
network is managed by the NML OS or the specific terminating non DWDM NEs are managed by another
NML OS.
The Client path concept is therefore a way to define the generic server provided by the optical transport network. NOTICE THE THE TRUE CLIENT IS THE SDH PATH.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
9 / 92
The WDM hierarchy represents the stages required by a digital client signal that has to be transported at
WDM layer:
The signal must be colored (i.e. has to be transmitted with the wavelength that has been assigned
to its channel) .
This operation is performed by specific boards named transponders or WLA (WaveLength Adapter)
This operation may be not necessary if the signal source is already coloured in the client equipment
through colored interfaces (specific transmission boards).
The colored signal belongs to the Optical Channel (OCh) layer
The Optical Channels that compose the WDM signals are multiplexed into the WDM signal.
The multiplexed signal belongs to the Optical Multiplex Section (OMS) layer
The signal is transported along the optical fiber until it is extracted to upper layers.
The signal interfaced with the optical medium belongs to the Optical Transport Section (OTS) layer
A schematic representation of the layering of a Client path into the OTN network is shown in Figure
Figure 9. on page 15.
When a single Optical Channel (without supervisory channel) is transported along the optical fiber, the
OMS layer is skipped and the OTS layer is named OPS0 (Optical Physical Section 0).
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
10 / 92
When a SDH network is the client of the OTN network, the WDM Client path is the service provided
by the OTN to the SDH network, which will look at it as a physical connection joining the two SDH NEs
at the extremities of the WDM section (see Figure 1).
By extension of this concept, related to monolambda signals, in WDM layer the ports of WLA boards are
identified as OPS ports and the physical connections connecting SDH NE to WDM NE are identified as
OPS physical connections
2.1.2 WDM Equipments managed by 1354RM
1354RM is the Alcatel NML OS. It currently manages the following WDM equipments:
1640WM
1686WM
1696MSPAN
OCP
1660OPS
Line Terminal
The Line Terminal is where the client digital signal access/exit the OTN network and is multiplexed/demultiplexed into the OTS level signal.
WLA boards are not necessary if the input signal is already colored
The In Line Amplifier configuration (also named as In Line Repeater) provides an optical amplification of
type OTS signal without any regeneration of the original signal.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
11 / 92
The OADM configuration offers the possibility of inserting/extracting wavelength from the optical payload.
The number of wavelength added/dropped in OADM NEs is limited (typically 48 wavelengths)
The OADM may host also an amplification section. In this case the NE configuration is defined as OADM
Repeater.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
12 / 92
Backtoback Regenerator
Two NEs may be put in backtoback configuration to offer regeneration capability for the OTS signal in
case of exceeding attenuation of the signal along the optical section.
This configuration allows to compensate the signal attenuation, the chromatic dispersion and to regenerate the signal (2R or 3R).
In addition an unlimited AddDrop capability is granted by this configuration
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
13 / 92
OCP (Optical Channel Protection) offers the opportunity of introducing OSNCP configuration in OTN networks where the WDM NEs dont support this feature (e.g. 1686WM and 1640WM).
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
14 / 92
2.2 Layering
The following figure shows the relationship between the network components and the model
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
15 / 92
Upload from the EML OS the information about NEs and Ports
A set of ADM NEs connected through an OTN network section, supported by WDM NEs.
The representation of this network is:
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
16 / 92
This connection is anyway the only connection seen by the NML OS at SDH network level and RM routing
algorithm will refer it when an SDH path crossing the two SDH NEs will be allocated.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
17 / 92
In case of fully flexible OTN NEs, 1354RM can provide the automatic routing algorithm for path provisioning. Circuit provisioning means the creation of the SERVER OPTICAL PATH, conventionally called Client path, taking into account of the notflexible NEs, including NE internal cabling.
The following sequence depicts a simple example of set up the OTN Network layout and on how Client
path is identified by RM.
1)
RM has no knowledge of the fixed cross connections defined inside WDM NEs.
2)
As soon as a physical connection is created, the TPs at the extremities are added in RM MIB.
The RM retrieves the fixed cross connection in the WDM NE creates an Incomplete Connection.
At this point the infrastructure supporting the client level services is ready.
3)
ED
01
The RM operator creates the first OPS connection between one of the SDH NE at the extremities of the Client Path and the adjacent WDM NE.
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
18 / 92
RM retrieve a second fixed cross connection, creates a second Incomplete Connection and merges it with
the previous one. The connection is still incomplete
4)
At last, an OPS connection is created at the other extremity of the WDM transport link. Also in
this case the objects up to the Client Nap are created into the SDH NE.
RM recognizes that the connection is now complete (ending on two Client NAPs) and transforms it in a
Client Path.
When both ends of the RC are not CTPs, the RC is defined as complete.
If both the ends of a complete RC are of the same type, the RC is automatically promoted to optical path
(if end points are NAPs) or trail (if end points are CAPs).
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
19 / 92
A Client path is terminated by two Client NAPs, contained in the SDH NEs (virtual, in case) accessing the
WDM layer services.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
20 / 92
SDH/SONET STM1 or STM4 (this service can be inserted/extracted only in 4xANY cards)
Data services,
The board allows also to multiplex some combination of different client signals:
3 x (FDDI or FE or DV or ESCON or STM1) + 1 x STM4
2 x (FDDI or FE or DV or ESCON or STM1) + 2 x STM4
2 x (FDDI or FE or DV or ESCON or STM1) + 1 x (FC or GbEth)
1 x (FDDI or FE or DV or ESCON or STM1) + 1 x STM4 +1 x (FC or GbEth)
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
21 / 92
The incoming elementary alarms from the WDM equipments are managed by 1354RM according to the
same approach defined for SDH networks:
Transport alarms are raised for OCH trails, OMS trails, physical connections (OPS and OTS) and Client
paths . Operational state is managed for the transport entities raising alarms and for the link connections
(OCH and Client).
Alarms on OMS Trails and OTS Physical Connections affects the whole transport service at WDM layer.
Alarms affecting OCh Trails and OPS Physical Connections impact a single channel (i.e. one lambda)
of the transport service.
Some counters have been created in the 1330AS counter summary to take in account the new alarms :
Other counters, even if keeping the name used when pure SDH network were managed by 1354RM collect
the alarms related to both the SDH and WDM entities:
EML: it reports all the processing error alarms affecting the EML domain
It has to be pointed out that the alarms raised by SDH NEs impact only the SDH part of the managed network, i.e. even if SDH NEs may appear in WDM network views, their alarms are not processed by the WDM
manager
This is the default customization defined for AS counters at 1354RM installation time: the operators are
allowed to further customize the counters (e.g. so that alarms are reported on a per layer basis).
Citytocity networks are protected via a mechanism based on an automatic endtoend 1+1 path
protection (SNCP) combined with a restoration application anticipating additional failures and identifying
secondary optical SNCP protected paths
The PRC module is in charge to perform such a restoration activity. This activity is performed by forcing
the OPS NEs switch positions (see Figure 9) accordingly to the alarms collected from the network.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
22 / 92
Since the PRC module is not able to get from the supervised OPS NEs all the information required for the
management of the restoration application, an interface is made available by 1354RM reporting a subset
of SDH transport entity alarms (affecting physical connections and MS trails) to the PRC module.
The interface is based on IPC queue mechanism.
The alarms reported by RM are internally processed by a specific module of PRC that triggers the force
switch activities accordingly.
B1 byte: a byte of the RS overhead of SDH signal (RSOH) allocated for both error and PM monitoring.
The basic concepts of PM management in RM (definition of a measure, correlation of TEs and TPs to it,
graphic and report interface) are kept unchanged for WDM.
The TE correlated to a measure will be a Client path.
2.10 B1 based PM
The B1 byte, as part of the RSOH will be accessible only in 3R transponders, where the overhead contents
may be accessed and analyzed.
B1 measurement may be performed for both (sometimes in a mutual exclusive way) the incoming (ingressing) and outgoing (egressing) SDH/SONET signal.
The monitoring of the incoming signal permits to detect errors occurred in the section between the current
DWDM NE and the adjacent SDH/SONET NEs.
The monitoring of the outgoing signal permits to detect errors occurred in the DWDM Domain.
Although this kind of measurement is unidirectional, it could be used as acceptable approximation of the
QoS of unprotected optical path in preOTN context.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
23 / 92
In the following some simplified definitions of the resources managed by 1354RM (formal descriptions of
a lot them are available in G.803, G.805)
2.11.1 Topological Components
Network: It represents the highest level of partitioning managed by 1354RM.
A path that crosses two Networks cannot be managed by 1354RM as a single transport entity (i.e.
it will be represented with two paths)
Subnetwork: It represents the second level of partitioning (i.e. a Network can be composed by more
than one subnetworks)
ET (Elementary Topology): It represents the third level of partitioning (i.e. usually ETs are contained
in subnetworks). The elementary topologies can be linear links, meshed subnetworks, rings)
Physical Connection: It is the logical representation of fibers and coaxial cables, between network
ports
Example:
The physical connection delimited by to network ports, e.g. two OTS physical ports.
2.11.2 Physical Resources
Network port: It represents the physical port where e.g. the fiber is connected.
Example:
A STM16 port of a SDH NE.
An OTS port of a DWDM NE.
Access port: It represents the physical port where the client signal is added/dropped.
Example:
A PDH port of a SDH NE.
The physical port of a Transponder in DWDM NE.
Example:
MSTrail between two STMn ports of two adjacent SDH NEs.
OMSTrail between two OTS ports of two adjacent DWDM NEs.
Path: A path (can be at either HO or LO path layer) is a route established in the SDH/SONET network.
It is delimited by NAPs (Network Access Points).
Example:
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
24 / 92
2.11 Acronims
Link Connection: It is an arc delimited by the two CTPs with the same timeslot and it is supported by
the same server Trail
Example:
An Au4 Link Connection is delimited by two corresponding AU4 CTPs and is supported by a MS
Trail.
An OCh Link Connection is delimited by two corresponding OCH CTPs and is supported by an OMS
Trail
2.11.4 Reference Points
NAP (Network Access Point): It terminates a path; one Network Access Point is associated to one
access port.
Example:
A VC3 NAP (can be called also VC3 TTP) is associated to a 34 Mbit/s port (or a 45 Mbit/s port)
and it terminates VC3 path).
A Client NAP is associated to an RS TTP of a SDH signal and it terminates a Client Path
CAP (Client Access Point): It terminates a HOTrail; one CAP can support Lower Order CTPs.
Example:
A VC4 CAP can support TU12 and/or TU3 CTPs (depending how the payload has been configured) it terminates VC4 HOTrail).
An OCH CAP supports a channel in OTS signal and terminates an OCH Trail
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
25 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
26 / 92
OPS CON
OTS CON
SDH NODE
WDM NODE
Legenda:
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
27 / 92
a)
Click twice on a OTS physical connection. The physical connection list is displayed.
b)
Select the WDM physical connection and click on Physical Connection Structure button. The OTS
Physical connection structure is displayed. See Figure 14. herebelow.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
28 / 92
Figure 13. shows an example of WDM network interworking with SDH network. To navigate from Netview
map:
OPTICAL NODE
OPTICAL NODE
TRAIL WDMOMS
LC WDM
LC WDM
RAW CONNECTION
PATH WDM
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
29 / 92
TRAIL
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
30 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
31 / 92
c)
ED
Selecting the path and clicking on Routing display button, it is possible to display the path routing
view. See below figure.
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
32 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
33 / 92
Figure 13. shows an example of WDM network interworking with SDH network. To navigate from Netview
map:
a)
Click twice on a OPS physical connection. The physical connection list is displayed.
b)
Select the WDM physical connection and click on Physical connection structure button. The OTS
Physical connection structure is displayed. See figure herebelow.
PORT WDM SDH CLIENT
SDH PHYSCON
LC WDM
WDM PHYSCON
PATH WDM
TRAIL WDM OCH
Figure 20. OPS Physical Connection Structure
c)
ED
Figures which follow show the attributes of the WDM port, equipped on the WDM node and of the
WDM port, shadow of the SDH port equipped on the SDH node
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
34 / 92
SEQUENCE
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
35 / 92
d)
ED
Click twice on the SDH Physical Connection icon; the SDH Physical connection structure is displayed.
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
36 / 92
WDM PATH
SDH TRAIL
ED
01
PAYLOAD
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
37 / 92
SEQUENCE
a)
Network Create
b)
c)
d)
Create WDM NE
NOTES
ED
the connection type for Generic Digital Client/WDM interworking is selected when connecting
to a virtual NE which represent Ethernet equipment.
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
38 / 92
WDM network create is similar to the creation of the SDH network. Namely the involved steps are:
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
39 / 92
NOTE. The rate of the SDH to WDM transponder ( STM1 / STM4 / STM16 ) is previously set at
1353NM level.
NOTE
The rate of the SDH to DATA transponder ( STM1 / STM4 / STM16 ) is previously set at
1353NM level.
LIMITATIONS FOR SDH COLOURED INTERFACE
ED
01
Before creating a connection between SDH equipment and 1696 equipment, it is required
to create on NM a (dummy) MCC board tuned to the desired lambda. Then execute a NE
synchronize from RM.
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
40 / 92
e)
Before creating a connection between SDH equipment and 1640 equipment, it is required
to create on NM a (dummy) TRB201 board tuned to the desired lambda. Then execute a
NE synchronize from RM. This operation is not required if the real board is present in the
equipment.
Create Connection. (step1 ) The example which follows details the WDM OTS connection. Start
the Create Connection wizard from the originating Node. Step 1 of the wizard allows to select connection type= WDM and WDM connection type=OTS. See following figure. Click on Next button.
connection type=WDM
Create connection step2 allows to select originating and terminating port to connect.
g)
Create connection step3 contains the icons of the two ports to be connected. Click on Finish button
to confirm the creation. The OTS connection is created.
h)
Implement the OTS physical connections. See Figure 30. on page 44.The optical client paths are
automatically discovered.
N.B.
ED
In case an OTS physical connections does not iclude its OCHtrail, as in the following figure,
where a raw connection is present, it is required to execute the payload setting of the raw connection.
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
41 / 92
RAW CONNECTION
OCHTRAIL
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
42 / 92
RAW CONNECTION
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
43 / 92
SETUP
BUTTON
Click on button SETUP. The raw connection changes into an OCHtrail. At this point it is possible to implement the physical connection. See Figure 30. on page 44.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
44 / 92
i)
ED
Supervision: Network Implement. This causes the creation of the following objects: trail WDMOMS,
LC WDM, raw connection, trail WDMOCH path WDM. See below figure.
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
45 / 92
OPTICAL NODE
OPTICAL NODE
TRAIL WDMOMS
LC WDM
LC WDM
RAW CONNECTION
PATH WDM
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
46 / 92
DEFINITION
The raw connection is a set of connections, structured in pointtopoint or pointtomultipoint arrangement. These connections are link connections ( lc ) and connections in topology ( connInTopol ), belonging
to the same layer.
The raw connection is terminated generically to a CAP, CTP, NAP. The raw connections between two CAPs
( Connection Access Points ) and the raw connections between two NAPs ( Network Access Points ) are
said complete raw connections; in particular the raw connection between two CAPs is a trail, while a
raw connections between two NAPs is a path.
TYPE OF CONNECTION
Within the NE the following types of connections may be present:
Client
semifixed. It can be modified, cannot be removed ( e.g. a passthrough connection ). These are
automatically uploaded and can be modified by means of the Connectivity Tool.
An example of routing display of a raw connection is shown in the figure which follows.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
47 / 92
GENERAL OPERATION
a)
During the implementation phase, the system uploads ( discovers ) the permanent ( fixed ) connections and constructs the raw connections, by taking into account the uploaded connections.
b)
The raw connection userlabel is assigned automatically and makes use also of special characters
( e.g. $ )
c)
Complete raw connections are automatically transformed to trails and paths, if all involved link connections are implemented.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
48 / 92
a)
The deallocate of a path causes the identification of the permanent ( fixed ) connections and the re
construction of the raw connection
CONSTRAINT
The raw connection can be used as constraint ( the only option Use Main is available )
RAW CONNECTION MANAGEMENT
The raw connection can be extended / shortened / splitted / promoted to path or trail / deleted.
By inserting new fixed connections within the NE, new raw connections are obtained.
NOTE 1
The partitioning concept is no longer applicable to raw connection
NOTE 2
It is not possible to implement manually paths/trails derived from raw connections. The user must configure the involved physical connection or configure a related trail in use by the path to obtain the automatic
implementation of the transport object.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
49 / 92
A raw connection completed is a CAP to CAP connection at OCH level or a NAP to NAP connection at
client level.
An example of complete raw connection is shown in the following figure.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
50 / 92
a)
To remove a connection in topology from a complete raw connection, point to the connection in topology and issue Connectivity Management: Remove from Raw Connection
b)
ED
The raw connection is split into two parts. See figure which follows
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
51 / 92
a)
ED
To add a connection in topology to a raw connection, point to the connection in topology and issue
Connectivity Management: Add to Raw Connection. See figure which follows
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
52 / 92
b)
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
53 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
54 / 92
b)
N.B.
In case on a trail has been issued the command Configuration: Payload: No Client, it is
possible to modify the attribute to Client. See following figure.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
55 / 92
c)
ED
Execute the payload configuration of the OTS physical connection. See following figure.
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
56 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
57 / 92
Verify that the connectivity objects ( LC, trail..) have been correctly created. See following figure.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
58 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
59 / 92
The scope of this procedure is to increase the size of the lambdas in the 1696WM optical equipment, i.e.
an optical MUX/DEMUX is added.
CONDITIONS
The 1696WM Network Element is RM assigned and the network is implemented
SEQUENCE
a)
b)
The remaining channels are passed through, i.e. when creating an OADM board, the OCHCTP on the
west side and the corresponding OCHCTP of the same lambda on the east side are passthrough connected. This is called default connectivity.
2.15.5 1696MS OADM connectivity
No default connectivity is provided by 1696WM equipment. Drop/insert and pass/through connections can
be created and removed. This connections can be considered as non flexible.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
60 / 92
SCOPE
During WDM network implementation, OCH LCs are created, according to the following cases:
OCHCTP west/east TYPE
CREATE LC
EQPD
EQPD
YES
EQPD
BUNDLE
YES
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
61 / 92
NOT EQPD
NO
BUNDLE
BUNDLE
YES
BUNDLE
NOT EQPD
NO
NOT EQPD
NOT EQPD
NO
N.B.
ED
NOT EQPD (not equipped) means ochctp present in RM but not in NE due to the hardware
configuration.
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
62 / 92
EQPD
2.17 Display of the correlation between WDM world and SDH world
SEQUENCE
a)
Point to the wdm path icon and issue the Interworking: SDH Connection popup menu. The SDH
physical connection structure is displayed. See Figure 46. herebelow.
Note that the client path icon is marked by a smal raw connection mark. See figure herebelow.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
63 / 92
CLIENT PATH
On the other hand, in the Optical Physical connection view , the client path icon is marked by a raw connection mark.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
64 / 92
SEQUENCE
a)
Point to the wdm raw connection icon and issue the Configuration: Convert in Path/Trail popup
menu item. The SDH physical connection structure is displayed. See figure herebelow.
Convert in path/trail
A report is displayed, to verify if the action has been correctly executed. See below figure.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
65 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
66 / 92
CLIENT PATH
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
67 / 92
2.19.1 Introduction
The Connect/Disconnect tool is provided to the user to manually modify connectivities outside path allocation/deallocation activity context. Note that path allocation/deallocation is not managed due to equipment limitations.
2.19.2 Creating a connection by means of the Connectivity tool
SCOPE
The scope of this procedure is to create a connection within an OADM by means of the connectivity tool.
SEQUENCE
a)
b)
From the Connectivity Tool wizard step 1 select Connect. Click on Next button.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
68 / 92
c)
ED
If you click on Port selection, you will display the port list from which you can select the port to connect.
Click on CTP selection, you will display the CTP list from which you can select the CTP to connect.
Click on Next button.
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
69 / 92
ED
01
PORT SELECTION
SELECTED CTP
CTP SELECTION
PORT LIST
SELECTED PORT
CTP LIST
SC. 6: WDM
3AL 61348 AA AA
92
SELECTED PORT
SELECTED CTP
It. 01
70 / 92
From step 3 wizard you can select the 2nd CTP . Click on 2nd TP to connect selection button and
select the CTP from the list.
e)
Click on Finish button. The connection is created. See the Connection create report on the figure
which follows.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
71 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
72 / 92
SCOPE
The scope of this procedure is to delete a connection within an OADM by means of the connectivity tool.
SEQUENCE
a)
From the map click twice on the OTS link, getting the physical connection list.
b)
Select the WDM physical connection and click on Physical Connection Structure button. The OTS
Physical connection structure is displayed.
c)
Optical paths and OCH trails must be removed to proceed in disconnecting the OTS connection.
Optical paths and OCH trails will become raw connections
d)
ED
Point to optical path (so called client) and issue Configuration: Conf. State Modification: Deimplement. A warning dialog box alerts that the optical path is correlated to an implemented SDH logical
connection (so called physical connection). The optical path will be deimplemented but the SDH logical connection will not be removed. See below figure.
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
73 / 92
f)
ED
Figure wich follows shows the routing display of the raw connection replacing the OCH trail
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
74 / 92
SEQUENCE
a)
ED
Point to the relevant node and issue Configuration: Connectivity tool
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
75 / 92
b)
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
76 / 92
DISCONNECT
Connectivity tool. Step 1 is used to select the action, in this case DISCONNECT. Click on Next to pass to
step 2.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
77 / 92
Connectivity tool. Step 2 allows to execute the following operations: (See Figure 61. )
selection of the Port to disconnect. From the Port list select the port and click on Apply. The selected
port icon is shown in the wizard main window.
selection of the CTP to disconnect. From the CTP list select the CTP and click on Apply. The selected
CTP icon is shown in the wizard main window.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
78 / 92
d)
Connectivity tool Step 3 shows the data previously selected by the user, asking for confirmation.
Click on Finish button to continue deleting the connection.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
79 / 92
The remote information is very useful, because allows to identify the originating and terminating points.
As an example:
If we select CTPx sited in Milan, via the involved far end CTPy sited in Bozen, it is possible to understand
that the choice of CTPx allows to realize a connection BozenMilano
The new Raw connection routing display is shown in Figure 63. The connection in topology within
1696MID is no longer present.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
80 / 92
SCOPE
The scope of this procedure is to modify a connection within an OADM by means of the connectivity tool.
CONDITIONS
This procedure applies to 1640WM and 1686WM equipments.
SEQUENCE
a)
From the Connectivity Tool wizard step 1 select Modify. Click on Next button.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
81 / 92
From step 2 wizard you can select the Port and the CTP. Click on the PORT list button and select
the Port from the list. Click on the CTP list button and select the CTP from the list. Click on Next button.
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
b)
c)
ED
From step 3 wizard you can select the connection type. See below figure. Click on Finish button to
render effective the change.
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
82 / 92
CONNECTION TYPE
The Connect/Disconnect tool supports the user in the selection of TP s involved in the connectivity, keeping into account possible constraints present at NE level (e.g. OADM WDM NE s).The Connect/Disconnect tool can be activated starting from one of the following cases:
1. Stand alone (nothing selected => Network Domain)
2. Topology selected (Network, Subnetwork, Elementary Topology)
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
83 / 92
5. CTP/CAP selected
6. NAP selected
ED
01
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorization from Alcatel.
3. Node selected
4. Port selected
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
84 / 92
2.20 Warnings
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
85 / 92
Upload connectivity feature of 1354RM is very useful for uploading internal physicallinks automatically
without the operator has to do something. For a full functionality of this feature who install/upgrade
1696MS / 1696MSC has to be aware that the cable configuration has to be manually described for each
nes in Cable list available on CT and NM according to the real hardware configuration.If this step is not
done, internal physical link have to be created manually by the 1354RM operator!
Case in which cable list has to be manually updated :
4xAny board connected to an OPC card or to an MCC board. phantom coupled MCC board are used to
visualize a passthrough between two mux/demux (see para 2.20.1.).
2.20.6 1696MS. Upgrading 1696MS to add new lambdas management without loss of trafic
A special feature available on 1696MS allows to equip new lambdas adding other mux/demux board. This
operation can be done without trafic loss if done according to specific upgrade rules (see specific ne documentation).
When management of new lambdas is added to ne and OTS port of this ne are already assigned to
1354RM a global download action is needed in order to see new OchCtp over OTS port, then and a payload configuration of physical link is needed to create transport object involving new equipped OchCtp(s).
When management of new lambdas is added to ne and OTS port of this ne are already assigned to
1354RM a global download action is needed in order to see new OchCtp over OTS port, then and a payload configuration of physical link is needed to create transport object involving new equipped OchCtp(s).
2.20.7 1696MS, 1696MS. Use of SPV_F_1310_1550 and SPV_FC board.
SPV_F_1310_1550 board and SPV_FC board act as a mux/demux from a 1696MSC to a 1696MS: the
first can transport a 1310 (B&W) signal, a 1550 (Colored) signal and a OSC channel; the second can transport an OSC channel and another colored signal.
These board are transparent at 1354RM level. The optical signals multiplexed by SPV_xxx boards are
seen in 1354RM as they are transported by different OPS physical links, while the OSC signal is never
managed in RM.
2.20.8 1696MS, Board MCC1 (SDH) and MCC2 (SDH). PM: change monitoring point from adjacent boundary clientctp to boundary clientctp.
When a clientpath is correlated to a measure, the default pmtps are the adjiacent boundary clientctps.
Network element allows monitoring on boundary clientctp and on adjacent boundary clientctp but not
at the same time.
To change a monitored point from adjacent boundary clientctp to a boundary clientctp a procedure is
available:
from clientpath Action>alarms>Transport>manual disable. This is necessary to remove rsTrailMonitor from adjiacent clientctp
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
86 / 92
2.20.5 1696MS, 1696MSC. Configuration of 1696MS to have 1354RM upload connectivity working well
correlate to measure the boundary ctp and start this point of measure
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
87 / 92
SCOPE
The scope of this procedure is to remove an optical physical connection
SEQUENCE
a)
From the OTS physical connection structure verify if optical paths (so called client) are present.
OPTICAL PATH
Execute the deimplementation of the optical path by selecting the menu Configuration: Configuration
State Modification: Deimplement. A question box asks for confirmation. Enter YES.
c)
Deallocate the optical path by issuing the command Configuration: Configuration State Modification:
Deallocate. The user can refresh manually the PhysCon structure view.
d)
e)
Remove the OTS optical physical connection. The OTS optical physical connection view remain
opened for a while.
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
88 / 92
SCOPE
The scope of this procedure is to insert a new OADM in a topology.
SEQUENCE
a)
Create in the suitable submap the node to be added ( node 96_MID with ref. to Figure 68. herebelow
96UP
96MID
96DOWN
Create the OTS physical connections 96_UP to 96_MID and 96_MID to 96_DOWN and create via
the Connectivity Tool the required passthrough connection within node 96_MID.
The procedure to create the OTS connection is described at para 2.13 on page 38
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
89 / 92
The Trace Identifier mechanism is used to control the continuity of the signal. The management of the
Trace Identifier in a WDM network is possible only if the transported signal is SDH.
The Trace Identifier, on the WDM NEs, can only be monitored (expected value). It can be provisioned (sent
value) only on the SDH NEs.
The Trace Identifier can be set both on the client path and on the related SDH physical connection. The
following has to be taken into account:
It is not possible to set the Trace Identifier on the SDH physical connection if the client path is present
If the Trace Identifier is set on the client path, the values are propagated on SDH ports, client NAPs and
on boundary WDM NEs (client CTPs)
If a client path is created and the Trace Identifier is already set on the SDH port, the value is is propagated
on the client NAP. When the Trace Identifier management command is executed on the client path, the
values of the Trace Identifier present on the NAPs are presented to the user that can confirm or modify
them
When the client path is deimplemented, the Trace Identifier is removed on client NAPs, on boundary
client CTPs and on SDH ports
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
90 / 92
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
91 / 92
END OF DOCUMENT
ED
01
SC. 6: WDM
It. 01
3AL 61348 AA AA
92
92 / 92
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 NETWORK CREATE ON RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 NETWORK CREATE ON NP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 ASSOCIATION MNG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Create NPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 Port management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
11
13
6 NAVIGATION FROM RM TO NP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Enable navigation on NPOSCA from 1354RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Navigation of 1354NP defined on RM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 Definition of the RM to NP correlation for path/trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4 Display of the correlated object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
15
15
16
19
8 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
01
050207
ED
DATE
CHANGE NOTE
M.RAGNI
V.BALCONI
V.PORRO
APPRAISAL AUTHORITY
ORIGINATOR
RM to NP INTERWORKING
ED
01
It. 01
3AL 61348 AA AA
24
1 / 24
FIGURES
Figure 1. Create NPA step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Create NPA step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. RMNP main attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Correlation selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Correlation dialog box for path/trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. WS selection dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. RMAS main view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. BACKBONE NETWORK sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
01
9
10
12
16
16
17
20
21
It. 01
3AL 61348 AA AA
24
2 / 24
1 GENERAL
ED
01
It. 01
3AL 61348 AA AA
24
3 / 24
ED
01
It. 01
3AL 61348 AA AA
24
4 / 24
2 NETWORK CREATE ON RM
The description which follows is the ordered list of procedures described in section OPERATION of the
1354RM operators handbook
a)
b)
c)
d)
e)
f)
Network: Implement
ED
01
It. 01
3AL 61348 AA AA
24
5 / 24
ED
01
It. 01
3AL 61348 AA AA
24
6 / 24
3 NETWORK CREATE ON NP
The description which follows is the ordered list of procedures described in section OPERATION of this
1354NP operators handbook
a)
PLACE: Create
b)
c)
d)
e)
f)
TELINK Create
ED
01
It. 01
3AL 61348 AA AA
24
7 / 24
ED
01
It. 01
3AL 61348 AA AA
24
8 / 24
4 ASSOCIATION MNG
4.1 Create NPA
ON RM
a)
Create NPA type Fast Restoration e.g. from the 2nd level subnetwork map select Actions: Create:
NPA
b)
In the step1 NPA wizard select NPA type=Fast Restoration, enter NPA cost reduction, NPA usage
cost and NPA name (userlabel) and click on Next button.
c)
ED
In the step2 NPA wizard select the internal (internal to the NP network) and interworking physical connections to assign to this NPA.
01
It. 01
3AL 61348 AA AA
24
9 / 24
e)
From the create report dialog box select button Implement and clixk on OK.
For interworking physical connection the following ACD values are setup: ACD=RM for the port controlled
by RM, sharedRM+NP for the boundary port.
For internal physical connection the following ACD values are setup: ACD=NP for both ports.
ED
01
It. 01
3AL 61348 AA AA
24
10 / 24
ON NP
a)
Execute Port: Assign to Network for the NP ports and sharedRM+NP ports
b)
c)
d)
For NP ports execute Port: Modify. Set usage=backbone and assign the port to the relevant TE
LINK.
e)
ED
01
It. 01
3AL 61348 AA AA
24
11 / 24
NP
NP internal
interworking
NPA create
physcon
physcon
NPA impl
on RM
link type=
RM internal
on NP
PORT
PORT
PORT
link type=
link type=
link type=
drop
inni
inni
TTP
usage=
local
drop
TTP
TTP
ACD=RM+NP
RM
usage=
bkb
usage=
bkb
ACD=NP
ACD=NP
ED
01
It. 01
3AL 61348 AA AA
24
12 / 24
ON RM
a)
b)
Set the path constraints if necessary. The NAP can be added as constraint.
c)
d)
ON NP
a)
Create the circuit having as local drop ports the relevant CTPs of the shared ports as taken from the
path routing
b)
NOTES ON NPA
The NPA can be deimplemented if no traffic crosses its physcons
The deimplementation of the NPA removes the port attribute which were setup during the implementation
The user can add a physcon to an NPA
ED
01
It. 01
3AL 61348 AA AA
24
13 / 24
ED
01
It. 01
3AL 61348 AA AA
24
14 / 24
6 NAVIGATION FROM RM TO NP
path/trail. It opens on RM screen the NPOSCA graphical interface displaying the associated circuit
subnetwork connection. It opens on RM screen the NPOSCA graphical interface displaying the related NP circuit
physical connection. It opens on RM screen the NPOSCA graphical interface displaying the related
TElink
b)
c)
The Definition of the correlation between 1354RM and 1354NP is required for the objects path
and trail. For snc and physical connection is set automatically.
SEQUENCE
a)
ED
Point to path/trail to correlate and issue the menu Related objects: Edit. The correlation selection
dialog box is presented.
01
It. 01
3AL 61348 AA AA
24
15 / 24
Select 1353NP and click on OK. The correlation dialog box is displayed. See following figure.
Enter the name of the NPOS circuit to correlate to the path/trail and click on OK. The correlation is
then created.
PATH / TRAIL
a)
Point to the path/trail and issue Search: Related. The WS selection dialog box is presented.
b)
Click on dictionary button. From dictionary selection box select the WS and click on OK.
ED
01
It. 01
3AL 61348 AA AA
24
16 / 24
The WS address is now present in the WS selection dialog box. Click on OK. NPOSCA graphical
interface opens displaying the associated Circuit: Show view.
PHYSICAL CONNECTION
a)
Point to the Physical Connection and issue Show: Details on NP. The WS selection dialog box ( see
above figure) is presented with the relevant WS already selected. Click on OK.
b)
ED
01
It. 01
3AL 61348 AA AA
24
17 / 24
ED
01
It. 01
3AL 61348 AA AA
24
18 / 24
The description of the above probable causes can be found in the 1678MCC documentation.
ED
01
It. 01
3AL 61348 AA AA
24
19 / 24
EXAMPLE
Figure which follows shows the RMAS main view. The BACKBONE NETWORK sublist is selected.
Opening the BACKBONE NETWORK sublist, the NP probable causes sent to RMAS are displayed on
a dedicated column. See following figure.
ED
01
It. 01
3AL 61348 AA AA
24
20 / 24
ED
01
It. 01
3AL 61348 AA AA
24
21 / 24
ED
01
It. 01
3AL 61348 AA AA
24
22 / 24
8 PERFORMANCE MONITORING
Measurements on MSP (Multiplex Section Protection) are managed via 1353NM or 1354NP only.
N.B.
ED
Multiplex Section Protection internal to the backbone network or interworking are defined via
1353NM. 1354RM does not receive any notification.
01
It. 01
3AL 61348 AA AA
24
23 / 24
END OF DOCUMENT
ED
01
It. 01
3AL 61348 AA AA
24
24 / 24
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Document structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
5
5
5
7
7
7
8
10
10
10
10
11
11
11
3 ASON CREATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 ASON network creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.1 Network Protection Architecture Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2 NPA display & Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.3 NPA modify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.4 NPA Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.5 NPA Remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
13
14
20
26
28
29
31
31
31
34
36
36
38
41
01
050207
ED
DATE
CHANGE NOTE
M.RAGNI
V.PORRO
APPRAISAL AUTHORITY
ORIGINATOR
ASONGMRE
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
1 / 89
41
44
44
44
6 ASON CLIENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1 Creation of an ASON client device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Definition of a physical connection with an ASON client device . . . . . . . . . . . . . . . . . . .
51
51
51
7 ASON PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 ASON PATH Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1.1 Interwork ASON2FMSSPRing with automatic squelching calculation . . . . . . . . . . .
7.1.2 Definition phase:defaultRerouting,defaultPriority and protectionType . . . . . . . . . . . . . . .
7.2 Visualization on maps of SNC Current, Nominal & Backup route . . . . . . . . . . . . . . . . .
7.3 Path: Reroute nominal route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4 Modify the userLabel and rerouting attributes of a SNC . . . . . . . . . . . . . . . . . . . . . . . . . . .
53
53
53
54
55
62
66
69
69
69
75
75
75
76
81
10 GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
87
11 ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
2 / 89
ED
01
SC. 8 ASONGMRE
9
15
17
17
19
20
21
21
22
22
23
23
24
24
25
26
27
28
29
31
32
32
33
34
35
35
36
37
37
38
39
40
41
42
43
45
46
46
47
48
49
50
57
58
59
60
61
62
63
63
It. 01
3AL 61348 AA AA
89
3 / 89
ED
01
SC. 8 ASONGMRE
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
81
82
83
83
84
85
It. 01
3AL 61348 AA AA
89
4 / 89
1 INTRODUCTION
1.1 Introduction
This document aims at introducing the ASON GMRE network controlled by RM.
ED
Overview on ASON
ASON CLIENT
ASON PATH
Remove Protection
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
5 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
6 / 89
While the TPs ends of the above subnetwork connection are chosen by RM, the other TPs involved in
the crossconnection inside the shared NE, are moved by GMRE according to its restoration purposes.
I.e., the setup of the single crossconnections inside the NEs belonging to the ASON domain (included
the shared NEs) will be done by GMREs. For all the other operations at path layer (POM, TCT, PM, path
trace): RM is the master for the TPs on the shared ports, while GMRE is the master for the TPs of the ASON
domain.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
7 / 89
Each manager is able to distinguish between ports on which all the normal operations are allowed because
completely assigned to it and ports on which only specific operations can be performed because shared
2.1.2 ASON NPA
ASON domain is managed by RM as ASON NPA
In ASON NPA definition, the user must specify the role of the physical connection as internal or interworking: the involved port on the NE belonging to the ASON NPA is marked as shared inside RM
In case the ASON network has already been setup by the GMRE user (through CLI), the RM user, to build
the network, has to perform the following steps:
provision the Trace Identifier on the SDH ports assigned to GMRE
set the download disabled mode on the involved NEs
For each node of the domain, performs the Configuration/Upload connectivity command. The command (based on J0) automatically creates in the RM DB the physical connections involving the node selected by the user
implement the uploaded physical connections
To create the NPA providing the internal and the interworking physical connections. The port ending
an interworking physical connection on the NE belonging to the NPA is marked as shared port. During
the NPA creation phase only the nodes supporting the GMRE on top can be involved. This presence of
the GMRE is retrieved through the Q3 interface during the Synchronize NE activity and stored in the RM
MIB
implement NPA
set the download enabled mode on the involved NEs. As a consequence, all commands are sent to
GMRE
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
8 / 89
As a consequence: ports dedicated to the interworking between RM and GMRE are marked as shared
.
1664SX
1664SX
RM
port
RM
port
RM physcon
R$
RM
port
RM
port
R$
interworking
interworking
physcon
physcon
J$
shared
port
J$
shared
port
J$
shared
port
1664SX
J$
shared
port
interworking
1674LG
physcon
G$
port
G$
G$
port
port
internal
physcon
port
internal
physcon
G$
G$
port
internal
physcon
G$
port
internal
physcon
1674LG
G$
port
G$
port
internal
physcon
G$
G$
port
physcon
G$
internal
physcon
port
J$ = shared type
G$
G$
port
port
1674LG
internal
internal
physcon
R$=RM port
G$
port
port
1674LG
internal physcon
G$=INNI port
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
9 / 89
When the RM operator setsup a path crossing (or terminating in) the ASON domain, the subnetwork
connection at the ASON NPA level will be created and also the related crossconnection inside the Nodes.
These crossconnection will be marked in such a way that RM will not directly forward the crossconnection implementation to the NE but they will provided to the GMRE with the provisioning of the SPC nominal
route (the provisioning of the single crossconnections to the NE will be in charge of GMRE)
2.1.4 Control Plane Domain Object
The controlPlaneDomain class represents the GMRE, i.e. the Control Plane instance contained in theNetwork Element. Some important attributes are:
reachable: it indicates the Control Plane communication status.
userLabel: it is the user label of the Control Plane
operationalState, alarmStatus, ...
nativeName: it indicates the name inside GMRE
emsFactoryAddress: it indicates the GMRE Factory IOR for addressing the GMRE/Control Plane using
NMI Corba (not visible on the User Interface)
ipAddress: it indicates the IP address of the GMRE (routing IP)
assignSt: it indicates if the Control Plane has been taken in charge by RM or not
consistSt: it indicates the consistency state
2.1.5 SubNetwork Connection
Some important attributes are:
userLabel
sncActiveSt: it specifies if the SubNetwork Connection has been implemented on the Nes by the GMRE
(not visible on the User Interface).
rerouting: it specifies if the rerouting by the Control Plane is allowed or not.
2.1.6 Network Element
The following attributes are added to the ne:
controlPlaneDomId: it is the Identifier of the Control Plane Domain (not visible on the User Interface)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
10 / 89
2.1.7 Port
The consistency is not applied for the crossconnections with configuration state implemented on CP
where CP stands for Control Plane.
The configuration state attribute of the crossconnections belonging to an SPC is set allocated when the
SPC configuration state is set allocated and moved to implemented on CP when the SPC configuration
state is set implemented (i.e. during path implementation activity)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
11 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
12 / 89
3 ASON CREATION
3.1 ASON network creation
The creation of an ASON Network is split in a well defined sequence of actions that are listed in the following of this paragraph.
SEQUENCE
a)
From the EML list select the EML which contains the NE belonging to GMRE control plane and issue
Actions: Synchronize: Synchronize EML
b)
GMRE NEs are listed with attribute Control Plane different from Not Present. The possible values for this
attribute are : Reachable, Not Reachable, ....
The symbol identifying a GMRE NE is also reported on the browser display as shown in the figure below.
NE with GMRE control Planes are discovered . The control plane is not managed yet. The Control plane
status is Not Managed
c)
From browser point to the ASON subnetwork and select Configuration: J0 definition. This configuration is executed automatically by the NEs belonging to the subnetwork.
d)
From browser, pointing to the subnetwork issue Subnetwork: Configuration: Upload Connectivity.
The physical connections are uploaded from GMREs and represented on RM database and interface.
e)
Create the NPA of type=ASON. Figures which follow shows NPA Create step 2, which requires the
specification of the internal and interworking physical connections.
f)
g)
From NPA list point to Ason NPA and issue Configuration: Implement. The communication RM
GMRE is started and, after a few seconds the Control Plane of each NE becomes reachable. On
GMRE systems the objects required for the routing and restoration functions are created.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
13 / 89
a)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
14 / 89
SCOPE
Bundling Rule ( with same risk, alltogether, one to one ) and click on Apply.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
15 / 89
In case of particular unbalanced configurations, if the NPA Usage Cost is not enough to avoid the ring
changing, the user needs to properly set the costs of physical connections
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
16 / 89
By default the NPA Usage Cost cost is set to an RM installation default value but can be modified
by the user. For example if L is the default cost of a physical connection, a meaningful default
value for the NPA Usage Cost can be L/2+1 ( i.e. (L/2+1)*2 )
c)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
17 / 89
NPA highlight shows on the map the nodes connected by physical connections involved in the NPA.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
18 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
19 / 89
SCOPE
NPAs can be retrieved from:
The containing network (list of all the existing NPAs)
The subnetworks (level 1 & 2) containing at least a Node (not a physical connection) involved in a NPA.
The map view of network and subnetworks
A physical connection involved in a NPA. A specific graphical flag shows that a Phys.Conn. belongs to
a NPA. This flag is represented on the payload structure view
The routing display of a path crossing one or more NPAs (LIN MSP is under analysis). See specific information on Routing.
A map of a topology containing at least a Node involved in a NPA (different from linear MSP) visualizes
a flag with the type and the name of the NPA :
The flag placement is in charge of the user (e.g. close to the right Nodes)
From the flag it is possible to retrieve the NPA and its view.
SEQUENCE
a)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
20 / 89
b)
ED
Click twice on ASON NPA row and select NPA view. See following figure.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
21 / 89
e)
ED
Clicking twice on the icons present in ASON NPA view, the following lists are displayed
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
22 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
23 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
24 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
25 / 89
ASON NPA can be modified adding and removing internal or interworking physical links
The command is performed using a tool similar to the creation/modification wizard
ASON NPA can not be modified by splitting / Joining existing internal physical links. This is due to limitation
on the interface between RM and GMRE.
NOTE: Only a defined NPA can be modified.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
26 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
27 / 89
No path must be present in case of Rings with the exception of SNCP Rings.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
28 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
29 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
30 / 89
a)
ED
From the Domain icon select Shared Risk Group: Create/Remove. The SRG Create/Remove wizard
is presented.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
31 / 89
Select Create and click on Next button. The Step 2 dialog box is displayed.
c)
Click on SRG type list and select from the list the desired type. Click on Apply to confirm.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
32 / 89
d)
N.B.
ED
srg probability change can be accomplished via Show/Set attrbute dialog box. see following figure
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
33 / 89
SEQUENCE
a)
From the Domain icon select Shared Risk Group: Create/Remove. The SRG Create/Remove wizard
is presented.
b)
Select Remove and click on Next button. The Step 2 dialog box is displayed.
c)
Click on SRG list and select from the list the SRG to remove. Click on Apply to confirm.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
34 / 89
d)
ED
Click on Finish to confirm.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
35 / 89
From the Domain icon select Shared Risk Group: Correlate/Modify the set of SRGs. The Correlate/
Modify wizard is presented.
b)
Click on Physical Connection list button and select from the list the Physical Connection to correlate.
Click on Apply to confirm.
Figure 27. SRG (Shared Risk Group) Management: Correlate/Modify the set of SRGs
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
36 / 89
d)
Click on SRG list button and from the list select the SRG to correlate. Click on Apply button and the
click on Finish on the main window.
SRG LIST
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
37 / 89
The scope of this procedure is to launch SRG calculation for WDM server
CONDITIONS
The SDH TELink inheritated the SRG values assigned to the WDM physical connections which support
the SDH physical connection. This command resets the actual (previously inherited) value and relaunches
the calculation of the SDH physical connection SRG, based upon the actual WDM SRG structure.
SEQUENCE
a)
From the Domain icon select Shared Risk Group: SDH SRGs calculation . The SDH SRGs calculation wizard is presented.
b)
Click on Physical Connection list button and select from the list the Physical Connection to correlate.
Click on Apply to confirm.
Figure 30. Shared Risk Group: SDH SRGs calculation: Physcon selectrion
c)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
38 / 89
SCOPE
Figure 31. Shared Risk Group: SDH SRGs calculation: SRG selectrion
d)
ED
The step 2 of the dialog box opens. Click on SRG list. The SRG list opens. Select the SRG and click
on Apply button. Click on Next button.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
39 / 89
Figure 32. Shared Risk Group: SDH SRGs calculation: launching the calculation
e)
ED
Click on Finish to complete the operation.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
40 / 89
The Physical Connection: Administrative State menu is constituted by the following items:
Set Unlock. This command forces in service the Physical Connection which was previously Locked.
The SNCs whose nominal path was crossing this Physical Connection and whose current path was
crossing a different route, revert to the nominal route.
Set Shutting down. This command rquests to GMRE the out of service the Physical Connection
with a Makebeforebreak ( soft rerouting ), i.e. GMRE will define a sequence of operations by
which the new route is made before the shutting down route is turned down.
Set Lock. This command forces out of service the Physical Connection
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
41 / 89
Check. This command asks GMRE the Physical Connection status (typically after a Set Shutting
down operation.
The above described commands can be launched also via the Maintenance wizard. See below figures.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
42 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
43 / 89
5.2.1 Introduction
A Traffic Engineer (TE) link is a bundle of transport entities equivalent from the routing point of view. Examples of TE link are:
Bundle of physical connections / MS Trails
Bundle of HO trails
A TELink has associated a cost and a list of Shared Risk Groups (SRGs).
The definition of the TELinks inside RM applies only to ASON network. When the ASON NPA is built, the
related TELinks are automatically created in RM and in the involved GMREs.
5.2.2 TELinks creation
TELinks related to an ASON NPA are automatically created as a consequence of NPA implementation.
TELinks are composed according to the value of the bundlingRule attribute of the NPA. In particular:
oneToOne: for each physical connection a different teLink is created. The linkMetric and the srgList attributes of the created teLink object are set with the corresponding values of the physical connection
withSameRisk: the physical connection with the same linkType, linkProtectionType, cost and srgList are
grouped in the same teLink object. These attributes are set to the corresponding values of the physical
connection
The TELink can also be created as a consequence of the modification of the composition of an existing
TELink.
5.2.2.1 Update TELink
SCOPE
To update the TELink: change the cost and SRG association
SEQUENCE
a)
From NPA view click twice on TELink icon: the TELink list is displayed.
b)
Select the TELink and issue Actions:Modification: Update TELink. The relevant dialog box is displayed.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
44 / 89
a)
ED
From NPA view click twice on TELink icon: the TELink list is displayed.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
45 / 89
b)
ED
Select the TELink and issue Actions:Modification: Move Physical connections. The relevant dialog
box is displayed. See below figure.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
46 / 89
MOVE
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
47 / 89
Select the physical connection and click on MOVE button. The physcon is displayed in the destination
list.
d)
You can also change SRG, by cliccking on SRG list button, selecting the SRG and confirming with
Apply button. See below figure.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
48 / 89
SRG LIST
ERASE SELECTED
ERASE ALL
Figure 41. Move TELink: change SRG
e)
SEQUENCE
a)
From NPA view click twice on TELink icon: the TELink list is displayed.
b)
Select the TELink and issue Actions:Modification: Move Physical connections. The relevant dialog
box is displayed. See below figure.
c)
Click on DESTINATION button. The list of TELinks having same origin and destination of the source
TELink is presented.
d)
Select the TELink where to move the Physcon and click on Apply button. The icon of the selected
TELink is now present in the dialog bo under subarea DESTINATION ( righthand side of the box)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
49 / 89
e)
ED
Click on Finish button to complete the update.
DESTINATION
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
50 / 89
6 ASON CLIENT
A UNI (network) interface is a port that is connected to a UNI (client) port of a corresponding client device
(e.g. a router) providing Switched Connection (SC) services. The port is located on the edge of a GMRE
domain.
The management of an UNI port, implies:
Creation of an ASON client device
Definition of a physical connection with an ASON client device
The physical connection is created and the UNI (network) port is assigned to RM. This port will be assigned
to the GMRE when the NPA to which the physical connection belongs will be implemented.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
51 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
52 / 89
7 ASON PATH
7.1 ASON PATH Create
SCOPE
Create a transport (path/trail) crossing both SDH and ASON networks.
RM provides the information to create the connection between Ingress and Egress GMREs.
In general a transport entity belonging to the ASON domain is called SNC: SubNetwork Connection. SNC
types are:
Switched Connection not created by RM, but by the clients (e.g. routers) of the GMPLS, between
two UNI ports
spcOnCtrlPlane: it indicates that the SNC (fully initiated and terminated into the ASON domain) is
present on the ASON DB but not in the RM DB; i.e. the DBs are not aligned.
SEQUENCE
a)
b)
c)
1)
2)
A SNC is created
RM, via Q3 interface, implements the cross connections belonging only to the Legacy domain
2)
RM provides to the Ingress GMRE the command to implement the SNC and the routing of the
SNC
3)
Each GMRE takes care to create the cross connection of each managed NE belonging to the
SNC routing
4)
GMRE Ingress determines also a backup SNC: in case of failure automatically the Ingress
GMRE switches on the backup SNC taking care of the all operations;
The calculation of the squelching table of the NE(s) belonging both to a 2F MSSPRing and to the ASONdomain is still in charge of RM.
RM calculates the squelching table of the NE containing the aEnd TP (Legacy domain) and of the Ingress
NE (ASON domain).
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
53 / 89
defaultRerouting
defaultPriority
If the path/trail doesnt cross the ASON domain these attributes are not managed.
If the path/trail crosses the ASON domain a SNC is created and these attribute are managed. SNC attributes: rerouting and priority mirror the related attributes of the path/trail which belong to. Setting the protType attribute of the path/trail entities (in definition phase) the homonymous attribute of the SNC (belonging to the selected transport entity) get a value, but in this case it isnt a pure mirroring: the value on the
SNC depends on the result of the routing algorithm.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
54 / 89
Main
Spare
Service
AllRes (defaul value)
The operator can also use another filter put ever on the option menu; this filter selects the route type of
the SNC.
This route filter (applied over two local attributes routeRole and statusOnConnec) allows the operator tochoose among one of the following values:
Network, NEs and links related to the selected path (in the Legacy domain) are shown with
a color in accordance with the resource type. The mapping is:
Main
Blue
Spare
Pink
Service
Green
Route
Resource type
color
Current
Main
Blue
Current
Spare
Pink
Nominal
Main
Light Blue
Nominal
Spare
Light Pink
C+N [current=nominal]
Main
Blue
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
55 / 89
Spare
Pink
C+N [current?nominal]
Main
C+N [current?nominal]
Spare
BackUp
Not Meaningful
White
In case of not protected path colors are those related to the resorceType=Main.
Visualization of additional SPC details through the driven zoomin on GMRE UI
The feature permits to retrieve some additional SPC details getting them by the GMRE UI.
The zoomin on GRME UI is driven, i.e. the user cannot perform any command on the GMRE UI. Selecting, by the RM browser, a SPC and choosing the Show Details on GMRE the following operations are performed:
telnet to the GMRE host (the GMRE is related to the Ingress node);
get/inventory of the additional details (the action is hidden to the user);
GMRE UI action is: show lsp lsp_index lsp_index, where lsp_index is the ID of the selected SPC.
close connection with GMRE UI.
According to the possible scenarios retrieved on GMRE NEs the following combination are foreseen:
connection Status
RouteRole
Active
Nominal
NotActive
Nominal
Active
Backup
Indeterminated
Nominal
If the physical connection is not part of an ASON NPA, the role is always nominal.
APortName/ZPortName: are the end points of the path/trail;
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
56 / 89
C+N [current=nominal]
PayloadPosition.
N.B. in case of SNC protected by SNCP, the output of the inventory with filter=active is both the main andspare legs. ASON domain does not provide the active/noActive information in case of SNCP protection.
EXAMPLE
a)
From the Path list ( see Figure 43. herebelow), select the path and click on highlight button. The highlight map view is displayed. See Figure 44. on page 58
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
57 / 89
b)
ED
By selecting the option route it is possible to display current, nominal and backup route.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
58 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
59 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
60 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
61 / 89
The Add/Remove Protection Tool can be launched by selecting the path and clicking on the relevant
icon. See following figure.
b)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
62 / 89
SCOPE
ACONN
ZCONN
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
63 / 89
Click on ACONN button. The path routing display ( nominal route ) is presented. Select the ACONNection in topology which will be the starting point of the nominal route change. Click on Select button
to confirm. The selected ACONNection in topology icon is then present in in the main box ( lefthand
side of below figure)
e)
Click on ZCONN button. The path routing display ( nominal route ) is presented. Select the ZCONNection in topology which will be the terminating point of the nominal route change. Click on Select
button to confirm. The selected ZCONNection in topology icon is then present in in the main box
(lefthand side of below figure)
f)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
64 / 89
d)
g)
ED
Click on Finish button to launch the operation.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
65 / 89
SCOPE
Modify the userLabel and rerouting attributes of a SNC
CONDITIONS
A path crossing the ASON domain is allocated or implemented
SEQUENCE
a)
From the routing display of the path select an SNC and issue Modify: Attributes popup menu.
b)
ED
You can modify the userLabel and the other rerouting attributes of the selected SNC
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
66 / 89
c)
ED
Verify for implemented path that the modification is propagated to the SNC selecting the Show: Details on GMRE
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
67 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
68 / 89
a)
ED
From the path routing icon select Add/Remove Protection Tool button. The relevant wizard is presented.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
69 / 89
b)
ED
Select option Add and click on Next button.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
70 / 89
A CONNECTION
Z CONNECTION
c)
ED
Click on button Get Routing Display for A connection
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
71 / 89
From the routing display select the A connection (in Topology) and click on Select button.
e)
f)
From the routing display select the Z connection (in Topology) and click on Select button.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
72 / 89
Z CONNECTION
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
73 / 89
g)
ED
ACONN and ZCONN are selected. See Figure 61. Click on Finish button to confirm. The routing
display must be refreshed. See Figure 62.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
74 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
75 / 89
The scope of this procedure is to remove the protection route from an existing path.
SEQUENCE
a)
From the path routing icon select Add/Remove Protection Tool button. The relevant wizard is presented.
b)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
76 / 89
SCOPE
A CONNECTION
Z CONNECTION
c)
ED
Click on button Get Routing Display for A connection
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
77 / 89
From the routing display select the A connection (in Topology) and click on Select button.
e)
f)
From the routing display select the Z connection (in Topology) and click on Select button.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
78 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
79 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
80 / 89
SCOPE
The scope is to execute a connection to the 1678MCC local terminal (CLI) and launch a show operation
on ASON connections.
SEQUENCE
a)
From the map click on the Control Plane icon associated to the involved node, as per Figure 68. herebelow. The CLI terminal is displayed. See Figure 69.
On the CLI terminal it is possible to launch the 1st level help simply by typing question mark ?. The
1st level command options are displayed: ( see Figure 70. )
Script. Allows the execution of a number of CLI commands as defined in the script file
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
81 / 89
Exit
Quit
The complete description of CLI commands/options can be found in 1678MCC CLI documentation.
? 1st level help
Enter Show, followed by the question mark, to launch the 2nd level help on the show command. The
2st level command options are displayed: ( see Figure 71. )
Interface. Returns a list of all or specific type interfaces available at the GMRE withe the high level
attributes.
Label. Label
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
82 / 89
NotificationHistory. Displays the last n event notifications as issued by GMRE ordered in chronological order from newest to oldest.
LSP INDEX
Figure 72. Show LSP: LSP list
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
83 / 89
Enter Show LSP followed by the question mark, to launch the 3rdnd level help on the show command. The 2st level command options are displayed: ( see Figure 73. herebelow )
TNA. Returns a list of all LSPs for which the TNA address is registered in Generalized UNI object.
3rd level help
f)
ED
Enter Show LSPIndex followed by the number taken from the relevant item of the list of above
Figure 72. The LSP report is displayed. See following figure.
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
84 / 89
e)
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
85 / 89
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
86 / 89
10 GLOSSARY
Ingress network node:
the border node at a network at which the connection or path is entering
the network (equivalent to source node).
Egress network node: the border node at a network at which the connection or path is exiting the network (equivalent to destination node).
Source node: usually the node that requests the connection. For SDH network the ingress network node
is equivalent with source node as this node is in charge of SPC restoration actions using Source based
restoration.
Destination node: usually the node terminating the connection requests. For SDH networks the egress
network node is equivalent with destination node as this node is in charge to correlate (merge) restoration
actions.
Bridge node: The node that passes the connection along a different route. In sourcebased restoration
this is usually the source node for full path diverse routing.
Merging node:
The node that merges the restoration path back to the nominal path. For full path diverse restoration this is usually the egress network node.
SNC a subnetwork connection between the ingress and egress network node
Guaranteed SNC relates to the end to end connection across a restoration domain with guaranteed
restoration scheme from ingress to egress port of the domain.
PRC The combination of SNCP and SBR. Initially the connection is setup like an SNCP. Once one leg fails
the failed leg is restored in SBR manner and the SNCP is changed with the selected and new leg. Reversion must be supported to change back to the original SNCP once both legs are available again.
Priority Indicates the priority of the connection within the network. High priority connection can preempt
low priority connection.
Restoration coordinator A logical instance at Path Management Class category that coordinates states
of various upstream and downstream legs and requests for protection and restoration purposes.
Reversion
Provides means to revert to the nominal route once the route becomes available. Reversion can be provided in automatic mode or can be triggered manually by the operator.
SBR
source based restoration scheme from ingress to egress port of the domain
Service a service is defined in an abstract manner (e.g. gold, silver, bronze) and relates to a target connection (call) from client to client. The service is mapped to network protection restoration feature that can
be setup in various ways within the network.
Call A call is defined between two client interfaces that covers one or more connections.
SNCP
a permanent bridge is performed at source and destination point and both nodes performs
switching on transport plane independently. Once switched a notification report is raised at either end. Neither reversion nor restoration must be provided.
SPC
Soft Permanent Connection; initiated by RM via management plane and implemented like an
End to End path for which any protection and restoration scheme can be applied
SC Switched Connection; initiated by a source client via signaling and implemented like an End to End
path for which any protection and restoration scheme can be applied.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
87 / 89
relates to the Network route between source and destination node that is provisioned
Backup path relates to the Network route between source and destination node that is considered the
protecting (rerouted, restoration) path.
Tunnel relates to a dedicated Network path between source and destination node that might be used
for restoration paths.
Makebeforebreak ( soft rerouting ) defines a sequence of operations at restoration time and for
maintenance purposes that a new route is made before the old failed route is turned down.
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
88 / 89
Nominal route
by RM.
11 ABBREVIATIONS
ASON
EFD
LSA
LSP
MPLS
NNI
OSPF
PG
PPRO
PRC
SBR
SC
Switched Connection
SNCP
SPC
SPR
SRLG
SRG
SSF
TCM
TIM
TNA
TSF
UNI
END OF DOCUMENT
ED
01
SC. 8 ASONGMRE
It. 01
3AL 61348 AA AA
89
89 / 89