3 Ne MNGT

1AA 00014 0004 (9007) A4 ALICE 04.
10
All rights reserved. Passing on and copying of this

document, use and communication of its contents
not permitted without written authorization from Alcatel.
1670SM REL. 4.2 C.T. OPERATORS HANDBOOK
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Document scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Target audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
15
15
15
15
15
15
2 GENERAL INTRODUCTION ON VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 EMLUSM view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 Introduction on the EMLUSM menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 Views menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2 Configuration menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3 Diagnosis menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.4 Supervision menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.5 MSSPRing menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.6 Download menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.7 Equipment menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.8 Board menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.9 Port menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.10 EPS menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.11 Transmission menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.12 Synchronization menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.13 External Points menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 Advices on navigation principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
17
19
21
21
23
24
24
24
25
26
26
28
29
31
32
37
3 NE MANAGEMENT SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1 NE management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 NE supervision and login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
39
40
4 NE MANAGEMENT GENERAL CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Access state (allow or inhibit NE Craft access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1 Switching from the OS to the Craft Terminal access state . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.2 Switching from the Craft Terminal access state back to the OS access state . . . . . . . .
41
41
42
42
01
031128
ED
DATE
CHANGE NOTE
E. PARRAVICINI
C. FAVEROL. BIANCHI
L. R. MAURI
APPRAISAL AUTHORITY
ORIGINATOR
1670SM REL. 4.2

C.T. OPERATORS HANDBOOK
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
1 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
43
45
45
45
52
53
54
5 SECURITY MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Set Manager list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Set ACD level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
55
56
6 EXTERNAL INPUT AND OUTPUT POINTS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 Displaying external points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 Expanding or reducing external points list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 External points configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
57
57
59
60
7 DIAGNOSIS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1 Alarms surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 Log Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.1 Upload Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.2 View Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5 Internal Link Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.6 Dataflow Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
63
65
67
68
68
69
71
72
8 COMMUNICATION AND ROUTING MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1 Overview on Communication and Routing Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1 Partitioning into Routing Subdomains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.2 Partitioning into separate Routing Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.3 OSI over IP tunneling on QB3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Communication and routing menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4 OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5 NTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6 LAPD Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8 Reachable Address Prefixes Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.9 Manual ES Adjacencies table Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.10 IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.11 Tunneling Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
73
73
74
75
76
78
80
81
82
85
87
88
89
90
9 EQUIPMENT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
91
9.1 Introduction and navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
91
9.2 Set and change, remove and modify subrack/board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
98
9.2.1 1670SM subrack management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
98
9.2.2 Board management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.3 Board administrative state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
9.3.1 Setting a board in service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
9.3.2 Setting a board out of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
9.3.3 Consulting a Boards Administrative state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
9.4 Cable configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
9.5 Software description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
9.6 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
2 / 448

4.2 NE Time management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 Alarms Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 Procedure to modify an ASAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.2 Alarm Severity Assignment Profile Management (ASAP) . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.3 Allow/Inhibit Alarms Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.4 Alarms resynchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Restart NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.7 Show supporting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
114
10 BOARD VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

10.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
10.2 Board View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
10.2.1 Port Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
10.2.2 Change Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
10.2.3 Show Supporting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
11 PORT VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
11.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
11.2 Port View: elements on the TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
11.3 Port View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
11.4 AU4 Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
11.5 Physical Media options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
11.5.1 Automatic Laser Shutdown management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
11.5.2 Show Optical Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
11.5.3 Single Fiber Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
11.5.4 MS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
11.5.5 Ethernet Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
11.5.6 Ethernet Mapping Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
11.5.7 Control Path Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
11.6 Show Supporting Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
11.7 Navigate to Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
11.8 Navigate to Monitoring View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11.9 Navigate to HOA port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
1AA 00014 0004 (9007) A4 ALICE 04.10
12 EQUIPMENT PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
12.2 Management: consulting and modifying EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
12.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
12.2.2 Note about HCMATRIX EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
12.2.3 EPS management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
12.3 Configuration: revertive and WTR for EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
12.4 Switching EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
12.5 EPS Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
13 MULTIPLEX SECTION PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.1 Architecture types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2 MSP options introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.3 MSP Create . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4 MSP Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.4.1 MSP modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.5 Display of Protection State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.6 MSP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.7 MSP Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.8 MSP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
161
161
162
163
167
168
169
171
173
174
14 TRANSMISSION VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.2 View Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3 View Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.1 View Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.2 Number of TPs Displayed in Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.3.3 Naming TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
179
179
180
180
180
182
182
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
3 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
15 CROSS-CONNECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

15.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
15.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
15.1.2 Multiplex Structures for SDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
15.1.3 Definition of Termination Points (TP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
15.1.4 Mapping Tables: TP Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
15.1.5 Cross-Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
15.1.6 Cross-Connection Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
15.2 Operative Sequence to execute Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
15.2.1 Procedure for high order signal (AU4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
15.2.2 Procedure for AU4 concatenated (AU44c, AU416c, AU464c) . . . . . . . . . . . . . . . . . 228
15.3 Cross-Connections Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
15.3.1 Search Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
15.3.2 Cross-Connection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
15.3.3 Actions available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
15.4 Create/Modify Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
15.4.1 Cross-Connection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
15.4.2 Create a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
15.4.3 Modify a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
15.5 Activate/Deactivate/Delete Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
15.5.1 Activate a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
15.5.2 Deactivate a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
15.5.3 Delete a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
15.6 Split and Join Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
15.6.1 Split a Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
15.6.2 Join Two Cross-Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
15.7 Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
15.8 Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
15.9 Show Cross-Connected TPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
4 / 448

14.3.4 Dynamic View Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

14.4 Transmission view access and menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
14.5 Add TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
14.5.1 TP Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
14.6 TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
14.6.1 High Order TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
14.6.2 J0 Section Trace management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
14.7 TP Threshold Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
14.8 Terminate / Disterminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
14.8.1 Terminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
14.8.2 Disterminate TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
14.9 Monitoring Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
14.9.1 Creation/Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
14.9.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
14.10 Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
14.10.1 Loopback Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
14.10.2 Loopback Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
14.11 Physical Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
14.11.1 Set Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
14.12 Navigation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
14.12.1 Expand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
14.12.2 Hide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
14.12.3 Show Supported Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
14.12.4 Navigate to Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
1AA 00014 0004 (9007) A4 ALICE 04.10

16 OVERHEAD MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.2 OH Connection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.3 Overhead views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.4 OH Cross Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.5 OH TP creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.6 OH TP deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16.7 OH Phone Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
263
263
264
265
266
271
273
274
17 PERFORMANCE MONITORING MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

17.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
17.2 Performance Monitoring on SDH port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
17.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
17.2.2 Supported Performance Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
17.2.3 Far End (FE) and Near End (NE) Performance Counting . . . . . . . . . . . . . . . . . . . . . . . . 278
17.2.4 Bidirectional counting (24 h Bi) for QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
17.2.5 End to End (ee 24h) Performance Counting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
17.2.6 Performance Monitoring on AUPJE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
17.2.7 Tandem Connection Termination (TCT) and Monitoring (TCM) . . . . . . . . . . . . . . . . . . . 280
17.2.8 Performance Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
17.2.9 Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
17.2.10 Performance Monitoring History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
17.2.11 Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
17.3 Performance Monitoring on ETHERNET port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
17.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
17.3.2 Ethernet physical interface counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
17.3.3 Aggregate counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
17.3.4 Flow counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
17.4 Configuration on SDH port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
17.5 Display Current Data on SDH port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
17.6 Display History Data on SDH port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
17.7 PM Threshold Table Selection on SDH port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
17.8 PM Threshold Table Create/Modification/Display on SDH port . . . . . . . . . . . . . . . . . . . . 300
17.8.1 Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
17.8.2 Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
17.8.3 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
17.9 Configuration on ETH port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
17.10 Display current Data on ETH port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
17.11 Display History Data on ETH port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
17.12 PM overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
18 SYNCHRONIZATION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2 Synchronization Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.1 Displaying the Synchronization View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.2 Synchronization View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.3 Timing Source Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.4 Synchronization Protection Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.5 Synchronization Configuration for T0/T4 and T4 squelch criteria . . . . . . . . . . . . . . . . . .
18.2.6 SSU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.7 Remove Timing Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.8 Change T4 <> T5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.9 Set and Remove T0 Equal T4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18.2.10 Transmission of SSM Quality Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
01
313
313
315
315
316
319
322
324
326
327
328
329
330
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
5 / 448
331
19 MSSPRING MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.1 MSSPRING introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.2 MSSPRING connection configuration advices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.2.1 2Fiber MSSPRING connection configuration advices . . . . . . . . . . . . . . . . . . . . . . . . .
19.2.2 4 Fiber NPE MSSPRING connection configuration advices . . . . . . . . . . . . . . . . . . . .
19.3 Operative sequence to configure MSSPRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.3.1 Operative sequence to configure 2Fiber MSSPRING . . . . . . . . . . . . . . . . . . . . . . . . .
19.3.2 Operative sequence to configure 4 Fiber NPE MSSPRING . . . . . . . . . . . . . . . . . . . . .
19.4 MSSPRING Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4.1 MSSPRing Main Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4.2 Squelching table with 2 fiber Terrestrial applications . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4.3 Traffic Map with 4 Fiber Transoceanic application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4.4 Traffic map table description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4.5 Symbolic representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4.6 Ring Normal / ExtraTraffic Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.4.7 Activate, Deactivate and Delete commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5 MSSPRING Protection Status and Commands for NPE Application . . . . . . . . . . . . . .
19.5.1 4F MSSPRing protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.2 External commands (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.3 4F MSSPRing dual protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.4 Protection Status Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.5.5 Protocol Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.6 MSSPRING Protection Status & Commands for 2F Terrestrial Application . . . . . . . .
19.6.1 2F MSSPRing protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.6.2 External commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.6.3 2F MSSPRing dual protection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19.6.4 2F Protection Status Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
333
333
333
333
333
334
334
335
336
337
343
349
355
357
359
366
367
367
369
377
384
402
403
403
405
413
418
20 ATM/IP/ETH CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20.2 Ethernet board TTPs creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20.2.1 Gigabit ETHERNET board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
435
435
435
435
1AA 00014 0004 (9007) A4 ALICE 04.10
21 SOFTWARE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

21.1 Generalities and descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
21.1.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
21.2 Software download operative sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
21.2.1 Software Download upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
21.3 Software Download Manager menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
21.4 Init download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
21.5 SW package Activation and Units information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
21.6 Mib management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
6 / 448

18.2.11 Show Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

LIST OF FIGURES AND TABLES

FIGURES
Figure 1. EMLUSM main view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2. Menu options flow chart 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. NE EMLUSM Main view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7. NE management: setting the access state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8. Consulting and/or setting the local NE time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. NE Time dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Configuring Alarm Severity Assignment Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. ASAPs Management dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. ASAP Edition dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Set ASAP dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. Set SdhNE Alarms Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. Inhibit alarm notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Alarm inhibition action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Allow alarm notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Alarm resynchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Restart NE confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Set Manager list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. Set ACD level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. Opening the external points view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. External points view (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. Expanding or reducing the external points list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Configuring external points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. Configuration external input point dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. Configuration external output point dialogue box (manual) . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Configuration external output point dialogue box (flexible) . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Alarm Surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Alarm Surveillance (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Abnormal condition menu option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. Example of abnormal condition list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. Example of loopback dialog window management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. Log Browsing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Remote Inventory confirmation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. Remote Inventory completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. View Remote Inventory (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. Internal Link Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. Routing subdomain organization example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. OSI over IP tunneling on QB3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41. Comm/Routing options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42. Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43. OS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44. NTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45. LAPD Configuration dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46. Creation LAPD Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47. Confirmation to change LAPD Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48. Ethernet Configuration L2 only parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49. Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 50. RAP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
01
18
33
34
35
36
40
42
43
44
46
46
48
49
51
52
52
53
53
54
55
56
57
58
59
60
60
61
61
63
64
65
65
66
67
68
68
69
71
74
75
77
79
80
81
83
84
84
85
86
87
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
7 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
88
89
90
92
93
94
95
96
97
98
99
100
101
101
102
103
104
106
107
108
109
110
111
111
112
112
113
113
114
115
116
117
118
119
119
122
123
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
8 / 448

Figure 51. MESA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 52. IP Static Routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 53. OSI Over IP Tunneling configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 54. Equipment Overview Rack level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 55. Equipment Overview Subrack level (1670SM_MS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 56. Equipment Overview Subrack level (1670SMAEP) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 57. Equipment Overview Fans Subrack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 58. Equipment Overview Equipment level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 59. Equipment menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 60. 1670SM subrack setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 61. Fans Subrack setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 62. List of different access cards, booster for SR70M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 63. List of access cards for SR70AEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 64. List of modules (drawers) for boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 65. List of different traffic ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 66. L642CF port setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 67. List of link units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 68. Consulting a boards administrative state (example1) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 69. Consulting a boards administrative state (example2) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 70. Cable configuration option selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 71. Cable configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 72. Cable configuration view (after add action) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 73. Software Description dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 74. No Sw indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 75. Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 76. Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 77. Select Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 78. Select Output Format for file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 79. Equipment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 80. Example of a Board View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 81. Examples of a Port identification and alarm synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 82. Board menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 83. After Port Access selection (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 84. Change Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 85. Change Physical Interface confirm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 86. Examples of a Port View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 87. Examples of G.783 Adaptation and Termination TP box . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 88. Port menu options (SDH, PDH and ETH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 89. AU4 concatenate/deconcatenate commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 90. Example of a concatenated AU4 transmission view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 91. Example of a concatenated AU416c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 92. Physical Media menu (SDH port example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 93. Automatic Laser Shutdown Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 94. Automatic Laser Shutdown Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 95. Automatic Laser Shutdown Management (after ALS Function delete) . . . . . . . . . . . . . . .
Figure 96. ALS and Lasercurrent state (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 97. Visualizing a port optical parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 98. Bidirectional Transmission on a single fiber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 99. Single Fiber Configuration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 100. MS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 101. Ethernet Mapping Protocol (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 102. Control Psth Activation (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 103. Board View example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 104. After Navigate to Transmission view selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 105. View of Monitoring Operations (example 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 106. View of Monitoring Operations (example 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 107. Navigate to HOA port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 108. Consulting EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 109. EPS Management dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 110. EPS: board selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 111. EPS: choose protected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 112. EPS functional state from protected active board view . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 113. EPS functional state from protecting active board view . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 114. Configure EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 115. EPS Management dialogue box (HCMATRIX board) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 116. EPS Management dialogue box (P4ES1N board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 117. Switching EPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 118. EPS Switch dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 119. EPS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 120. EPS overview after Search (example with HCMATRIX) . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 121. MSP Create option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 122. MSP Schema Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 123. MSP schema creation Port dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 124. TP Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 125. MSP 1+1 standard protection schema (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 126. MSP N:1 standard protection schema (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 127. MSP Management option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 128. MSP Management view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 129. MSP Protection Status example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 130. MSP Protection Status Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 131. MSP Commands option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 132. MSP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 133. MSP Delete option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 134. MSP Schema Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 135. MSP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 136. MSP overview after Search (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 137. Symbols Used in Transmission View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 138. Transmission View Area (SDH & ETH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 139. Transmission menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 140. TP Search Dialog, Initial State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 141. Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 142. TP Search Dialog with Various TP Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 143. TP Search Dialog with Status Information Displayed . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 144. Symbols in TP Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 145. Board History Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 146. TP Search Dialog with Different Filtering Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 147. Information... Dialog for Search Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 148. Print to Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 149. Print to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 150. Example of Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 151. High Order TP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 152. J1 hexadecimal editor (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 153. J0 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 154. J0 hexadecimal editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 155. Degraded Signal Threshold selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 156. Monitoring Operations options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 157. Monitoring Operations Creation/Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 158. Display of POM and TCM in Port View (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
01
142
143
144
146
146
150
150
151
151
152
152
153
154
154
156
157
163
163
164
165
166
166
167
168
168
170
171
172
173
173
174
175
180
181
184
185
186
186
187
187
188
189
189
190
190
191
192
193
195
195
196
198
199
200
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
9 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
10 / 448

Figure 159. Display of POM ans TCM/TCT in Port View (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Figure 160. Monitor Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Figure 161. Loopback configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Figure 162. Loopback options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 163. Port Loopbacks View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Figure 164. Loopback options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 165. Loopback Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Figure 166. Display of Loopback action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Figure 167. Physical Media options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Figure 168. Set Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Figure 169. Expand options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Figure 170. Hide options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Figure 171. Board View (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 172. Port View example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Figure 173. SDH Multiplex Structure according to ITU-T G.709 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Figure 174. Frame Construction within the Synchronous Digital Hierarchy . . . . . . . . . . . . . . . . . . . . 218
Figure 175. SDH Transport Level Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Figure 176. PDH Transport Level Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Figure 177. Unidirectional Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 178. Bidirectional Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 179. Example of Broadcast Connection with Three Legs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 180. Protected Unidirectional Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figure 181. Bidirectional Connection Input Protected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figure 182. Protected Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Figure 183. Drop and Continue Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Figure 184. Drop and Continue Insert Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 185. Port Crossconnection options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Figure 186. Transmission Crossconnection option menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Figure 187. Configuration Crossconnection options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Figure 188. Cross-Connection Management Dialog (Initial State) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Figure 189. Cross-Connection Management Dialog (After Search) . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Figure 190. Port Crossconnection options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Figure 191. Transmission Crossconnection options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Figure 192. Protection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Figure 193. Cross Connection icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Figure 194. Creation of a Unidirectional, Non-Protected Cross-Connection . . . . . . . . . . . . . . . . . . . . 242
Figure 195. Create a Bidirectional Protected Cross-Connection (example) . . . . . . . . . . . . . . . . . . . . 244
Figure 196. Create Drop&Continue connection (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Figure 197. Search for Cross-Connection (example for output) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Figure 198. Create an Unprotected Broadcast Cross-Connection (example) . . . . . . . . . . . . . . . . . . 248
Figure 199. Create a Protected Broadcast Cross-Connection (example) . . . . . . . . . . . . . . . . . . . . . . 249
Figure 200. Unprotect a Unidirectional Protected Cross-Connection (example) . . . . . . . . . . . . . . . . 251
Figure 201. Protect an Unidirectional Unprotected Connection (example) . . . . . . . . . . . . . . . . . . . . . 252
Figure 202. Split/Join Unprotected Bidirectional Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Figure 203. Split/Join to Protected Bidirectional Cross-Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Figure 204. Protection Actions Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Figure 205. Select Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Figure 206. Select Output Format for file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Figure 207. Transmission Crossconnection options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Figure 208. Show Cross Connected TP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Figure 209. Overhead options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Figure 210. Cross Connection Management for OverHead dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Figure 211. Main CrossConnection for OverHead dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
Figure 212. OH TP creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 213. OH Search TP for creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 214. OH TP deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 215. Phone Parameters dialog window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 216. Far End Performance Monitoring Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 217. Counter directionality: network centric view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 218. Counter subdivision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 219. Ethernet aggregate counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 220. Performance options menu (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 221. PM Configuration Dialog (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 223. Current PM Data Dialog (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 225. PM History Data Dialog (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 226. Configuration Performance Threshold Tables option . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 227. PM Threshold Table selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 228. Display of Performance Monitoring action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 229. Create PM Threshold Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 230. Modify PM Threshold Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 231. Create Ethernet counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 232. Display PM Ethernet current data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 233. Display graphic data (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 234. Display PM Ethernet History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 235. Display Graphic Data (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 236. PM Overview menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 237. PM overviewTp search windows interworking (example) . . . . . . . . . . . . . . . . . . . . . . . .
Figure 238. PM overview window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 239. Internal organization of the SETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 240. Obtaining the Synchronization view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 241. Synchronization View example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 242. Synchronization Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 243. Timing source configuration for crossconnect equipments . . . . . . . . . . . . . . . . . . . . . . .
Figure 244. Synch. source configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 245. Lockout, Force and Manual commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 246. Configuring the T4 SSM algorithm and the squelch criteria . . . . . . . . . . . . . . . . . . . . . . .
Figure 247. Configuring the T0 SSM algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 248. SSU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 249. Synchronization source removing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 250. Synchronization source removing confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 251. Change T4 <> T5 option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 252. Change T4 <> T5 confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 253. T4 equal T0 setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 254. Transmission SSM Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 255. Timing Source Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 256. MSSPRing pull down menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 257. MSSPRing Management dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 258. Creation Schema dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 259. Activated MSSPRing Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 260. Node Id and associated ring node position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 261. Ring map configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 262. WTR dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 263. Example of error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 264. Squelching table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 265. Example of a ring traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 266. Connections of the ring of Figure 265. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED
01
272
273
274
278
283
284
285
287
289
291
293
294
296
297
298
299
301
303
304
306
306
308
308
309
310
311
313
315
316
319
320
321
322
325
325
326
327
327
328
328
329
330
331
336
337
338
339
340
341
342
343
343
344
344
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
11 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
345
345
346
346
347
347
348
348
350
350
351
352
352
353
354
354
355
357
357
357
358
358
359
359
360
360
361
361
362
362
363
363
363
364
364
364
365
365
366
367
368
369
369
370
371
372
373
373
374
375
376
376
378
379
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
12 / 448

Figure 267. Squelching table of Node A, West side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 268. Squelching table of Node A, East side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 269. Squelching table of Node B, West side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 270. Squelching table of Node B, East side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 271. Squelching table of Node C, West side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 272. Squelching table of Node C, East side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 273. Squelching table of Node D, West side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 274. Squelching table of Node D, East side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 275. Insert to East . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 276. Drop East . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 277. Example of West to East Passthrough with its protection . . . . . . . . . . . . . . . . . . . . . . .
Figure 278. PointtoMultipoint path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 279. PointtoMultipoint configuration and relevant protection channel . . . . . . . . . . . . . . . . .
Figure 280. Drop & Continue and Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 281. Example of Last Drop & Continue on West side (protection on East) . . . . . . . . . . . . . .
Figure 282. Drop & Continue P and Last Drop & Continue in Primary and Secondary nodes . .
Figure 283. Traffic table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 284. Drop/Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 285. PassThrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 286. PointtoMultipoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 287. Drop & Continue plus Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 288. Last Drop Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 289. Traffic example in ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 290. Ring normal traffic map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 291. Ring extratraffic map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 292. Ring Normal traffic map: concatenated path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 293. Pointtomultipoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 294. Ring normal traffic map describing a pointtomultipoint unidirectional path . . . . . . . .
Figure 295. 2 NPE rings, bidir, D&C, no prot. in NPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 296. Path of Figure 295. case B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 297. Bidir, D&C, no prot. in NPE, (add/drop node = Primary) . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 298. Traffic map of Figure 297. case A and Figure 295. case A . . . . . . . . . . . . . . . . . . . . . . .
Figure 299. Path of Figure 297. case B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 300. Bidir, D&C, no prot. in NPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 301. Traffic map of case C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 302. Traffic map of Figure 300. case D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 303. Unidir, D&C, no prot. in NPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 304. Traffic map of Figure 303. case B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 305. Confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 306. Protection states and commands Idle status (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 307. Span and Ring Protection (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 308. Lockout commands (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 309. Protection and working channels where the lockout command can be activated (4F)
Figure 310. Tailend / Headend association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 311. Ring protection with a lockout protection span and a ring failure (4F) . . . . . . . . . . . . . .
Figure 312. Lockout command and nonserved failures (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 313. Forced and Manual commands (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 314. Manual and Force Span/Ring command (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 315. Examples of a Force command and a Automatic protection span (4F) . . . . . . . . . .
Figure 316. Automatic protection Bridge/Switch (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 317. Example of confirmation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 318. Clear WTR commands (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 319. Ring network reference scheme for dual Events (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 320. Automatic protection for double ring failures (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1AA 00014 0004 (9007) A4 ALICE 04.10

Figure 321. Protection span and ring failure with a tailend/headend node mode (R, CMs) . . . . . 380
Figure 322. Protection span and ring failure with a tailend/tailend node mode (R, Cs) . . . . . . . . 381
Figure 323. Dual Events Protection table (4F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
Figure 324. Protection Status window with a Manual Ring command . . . . . . . . . . . . . . . . . . . . . . . . . 385
Figure 325. Visualization of the Forced / Manual protection Statuses . . . . . . . . . . . . . . . . . . . . . . . . . 386
Figure 326. Visualization of the Lockout command Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Figure 327. Visualization of Automatic Protection Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Figure 328. Automatic Protection and Alarm Clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Figure 329. Ring network reference scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Figure 330. Automatic protection for double ring failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Figure 331. Regular condition (no request) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Figure 332. Protection Span failure between ADM1 and ADM4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Figure 333. Working Span failure between ADM1 and ADM4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Figure 334. Clearing of Working Span failure between ADM1 and ADM4 . . . . . . . . . . . . . . . . . . . 395
Figure 335. Ring failure between ADM1 and ADM4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Figure 336. Clearing of Ring failure between ADM1 and ADM4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Figure 337. Protection span failure between ADM12 + ring failure between ADM43 . . . . . . . . . . 398
Figure 338. Working span failure between ADM12 + working ring failure between ADM43 . . . . 399
Figure 339. Ring failure between ADM12 + ring failure between ADM34 . . . . . . . . . . . . . . . . . . . . 400
Figure 340. Ring failure between ADM14 and between ADM12 (ADM1=isolation node) . . . . . . 401
Figure 341. Protection states and commands Idle status (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Figure 342. Ring Protection (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Figure 343. Lockout commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
405
Figure 345. Tailend/Headend association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Figure 346. Tailend/Headend protec. with a lockout working and a direction ring failure (2F) . . 407
Figure 347. Ring protection with a lockout and a ring failure (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
Figure 348. Lockout command and nonserved failures (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Figure 349. Forced and Manual commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Figure 350. Manual and Force Ring command (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Figure 351. Ring Protection with Force and Manual commands (2F) . . . . . . . . . . . . . . . . . . . . . . . . . 411
Figure 352. Automatic protection Bridge/Switch (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Figure 353. Example of confirmation dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Figure 354. Clear WTR command (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Figure 355. Ring network reference scheme (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Figure 356. Examples of Double ring failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Figure 357. 2F Automatic protection (tail/head) for double ring failure visualization . . . . . . . . . . . . . 416
Figure 358. Tail / head dual Events Protection table (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Figure 359. Manual command applied at the Reference Point ring network Figure 356. . . . . . . . 419
Figure 360. Visualization of the Forced / Manual protection Statuses (2F) . . . . . . . . . . . . . . . . . . . . . 420
Figure 361. Visualization of the Lockout command Statuses (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Figure 362. Visualization of Automatic Protection Statuses (2F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Figure 363. Protection status with double ring failure (ref. pointSSAN) . . . . . . . . . . . . . . . . . . . . 423
Figure 364. Protection status with double ring failure (ref. pointSSRN) . . . . . . . . . . . . . . . . . . . . 424
Figure 365. Protection status with double ring failure (ref. pointOSAN) . . . . . . . . . . . . . . . . . . . . 425
Figure 366. Protec. status with double ring failure (ref. pointOSAN) recovering to idle . . . . . . 426
Figure 367. Double manual ring command (ref. pointSSAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Figure 368. Double manual ring command (ref. pointOSAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Figure 369. Manual ring and Lockout Protection (ref. pointSSSN) . . . . . . . . . . . . . . . . . . . . . . . . 429
Figure 370. Manual ring and Lockout Protection (ref. pointSSRN) . . . . . . . . . . . . . . . . . . . . . . . . 430
Figure 371. Automatic working ring and Manual Ring (ref. pointOSAN) . . . . . . . . . . . . . . . . . . . . 431
Figure 372. Automatic working ring and Force Ring (ref. pointSSAN) . . . . . . . . . . . . . . . . . . . . . 432
Figure 373. Automatic working ring and Lockout working Ring (ref. pointSSSN) . . . . . . . . . . . . 433
Figure 374. Automatic working ring and Lockout Protection (ref. pointOSRN) . . . . . . . . . . . . . . 434
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
13 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
436
437
437
439
442
442
443
444
445
446
447
TABLES
Table 1. Alarms at Equipment level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2. TP names on 1670SM (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3. TP names on 1670SM (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4. Optional and Mandatory Configurable Parameters for Cross-Connection Creation . . . . . .
Table 5. Modificable Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 6. SES thresholds: number of errored blocks to declare SES . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7. Threshold table entities association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8. Maximum Performance Parameter Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
223
223
240
250
277
299
302
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
14 / 448

Figure 375. Example of Ethernet TPs creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 376. Control Path activation window (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 377. ETHERNET port view example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 378. Software Download general principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 379. Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 380. Download menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 381. SW Downloading dialogue box (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 382. Software download in progress (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 383. Software Package Information dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 384. Detail of units info (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 385. NE MIB management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 INTRODUCTION
1.1 Scope
1.1.1 Document scope
The aim of this document is to help the operator understand, configure and manipulate Network Elements
(NEs) easily, using the Craft Terminal (CT). The different functionalities related to the equipment views,
the menu items and the different actions that can be undertaken from these views are described in detail.
1.1.2 Target audience
This document is intended for the operators whose role is to manage the Network Elements.
The documents that should be read before starting this document are:
1320CT Basic Operators Handbook
The documents of this Handbook that should be read before starting this document are:
Introduction manual
1.2 Terminology
1.2.1 Acronyms and abbreviations
Refer to the Section Introduction manual.
1.2.2 Glossary of terms
1AA 00014 0004 (9007) A4 ALICE 04.10
Refer to the Section Introduction manual.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
15 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
16 / 448

2 GENERAL INTRODUCTION ON VIEWS AND MENUS

In this chapter the organization of the EMLUSM screen, presented after the NE login, is described.
First is introduced the view organization, than the accessible menu options are listed.
At the end some further advices are given for Navigation principles.
In many screens of this handbook the release number is not indicated, while it is instead present
in the real screen displayed to the operator.
This is due to the fact that the same screen is associated to different releases.
Sometimes the release number reported is only for example.
2.1 EMLUSM view organization

The EMLUSM view (see Figure 1. on page 18). It is the first window presented to the operator after the
login.
It contains the following fields, that provide you with information needed to manage the NE:
Severity alarm synthesis

Domain alarm synthesis
Management status control panel
View title
View area
Message/state area
The Menu bar and the View area contained in the same NE view permits to performs all the configuration
and supervision and display the specific selected item.
The view organization is detailed in the 1320CT Basic Operator Handbook to which refer for the
description, except for the following information, that differs according the NE type:

The different alarm domain type in which can be subdivided the NE are: Synchronization (SYNC),
External Point (EXTP), Equipment (EQP), Transmission (TRNS).
1AA 00014 0004 (9007) A4 ALICE 04.10
Information about the alarms and status is given in the Maintenance section of this handbook.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
17 / 448
Severity alarms
synthesis

Menu bar
View title
View area
Message/state
area
Management
states control panel
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 1. EMLUSM main view organization
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
18 / 448
2.2 Introduction on the EMLUSM menu options

The menu bar allows to perform configuration and supervision functions on the Network Element (NE).
This paragraph list all the menu options and then more details on the relevant contained entries.
For each of them the relevant operative function are briefly introduced and the paragraphs where it is
detailed are referred or the introduction to the options of each menu inserted in next paragraphs of this
chapter is recalled.
The flow charts of Figure 2. on page 33, Figure 3. on page 34, Figure 4. on page 35 and Figure 5. on page
36 summarize the menu options.
From Chapter 3 on page 39 details and operative information on the all the views are given. They are not
presented according the menu option sequence but according a functional subdivision.
In the menu bar there are permanent menu items always displayed.
Starting from the left, the menus are:
Permanent Menus
Views
(first column).
See para. 2.2.1 on page 21.
To navigate among the views (Equipment, External Point, Transmission, etc. ).
Configuration
(second column).
To set general configuration of the NE, set TMN and OverHead parameters and to show or
modify some parameters (performance monitoring, crossconnection, MSP, EPS).
Diagnosis
(third column).
To get information about the NE (alarms, performance monitoring, remote inventory).
Supervision
(fourth column).
To set the supervision states (i.e. Craft Terminal enabling).
MSSPRing
(fifth column).
To manage the 2 fiber and 4 fiber MSSPRing protection, setting the relevant configuration.
Download
(sixth column).
To manage the NE software (download, MIB management).
Help
(last column).
1AA 00014 0004 (9007) A4 ALICE 04.10
To activate the help on line.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
19 / 448
Other Menus
Equipment
(seventh column).
See chapter 9 on page 91.
To manage the NE as a whole, setting the boards which compose it.

It manages both the 1670SM Main Shelf and the 1670SM Access Extension Panel.
From the Equipment view the Board view can be accessed.
Board
(seventh column).
To show the physical port available in a specific board. It is the entry point for the Port view.
Transmission
(sixth column).
It permits to show and set the Termination Point of the equipment, thus having an overview of
the complete signal flow of the various port.
The menu permits to define all the Cross Connections and manages the transmission
resources, setting the relevant configuration.
Further access the Performance Monitoring and permits navigation to the Board view.
It also permits to manage the MSP protection setting the relevant configuration.
Port
(sixth column).
To set and show (detailed alarm view) the transmission resources referred to the Port.
It also permits to manage the MSP protection setting the relevant configuration.
EPS
(sixth column).
To manage the EPS protection, setting the relevant configuration.
Synchronization
(sixth column).
To show and modify synchronization parameters.
External Points
(sixth column).
1AA 00014 0004 (9007) A4 ALICE 04.10
To show and modify housekeeping (environmental) alarms.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
20 / 448

Further, in the menu bar there are other menus, presented as an alternative, only when a particular object
or option is selected.

2.2.1 Views menu introduction

This menu permits to navigate among the views and set some parameters, by means of the following
entries:
Views
'Backward:
Go back to the previous view.
'Forward:
Go to the next view.
'Equipment:
Open the Equipment view.

The Equipment menu and theEPS menu are then available on the menu bar.
'External Points:
Open the External Point view. See chapter 6 on page 57.

The External Point menu is then available on the menu bar.
'Transmission:
Open the Transmission view. See chapter 14 on page 179.

The Transmission menu is then available on the menu bar.
'Synchronization:
Open the Synchronization view. See chapter 18 on page 313.

The Synchronization menu is then available on the menu bar.
'Refresh:
The aim of the refresh feature is to avoid a misalignment between the CT and
the managed NE.
This misalignment is due to a loss of notifications coming from the NE.
'Open Object:
Navigate and show the contents of the selected object: the current view change.
It is equivalent to a double click on the selected object in the view area.
'Open in Window: Navigate and show the contents of the selected object.
The current view doesnt change but a new window with a new view is opened.
'Close:
Close the EMLUSM view, without stopping the supervision of the NE.
2.2.2 Configuration menu introduction

This menu permits to set general configuration of the NE and to show or modify some parameters, by
means of the following entries:
Configuration
'Alarm Severities:
Manage the Alarm Severity Assignment Profile.

See para. 4.3.2.1 on page 45.
'Set Alarm severities:
Send the Alarm Severity Assignment Profile to the selected object

1AA 00014 0004 (9007) A4 ALICE 04.10
'Set SdhNe Alarm Severities: Send the Alarm Severity Assignment Profile referred to the
equipment level.
'NE Time:
ED
01
Display and set the NE local time.

See para. 4.2 on page 43.
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
21 / 448
Manage the following parameter of the Performance Monitoring domain.

It opens the relevant menu options:
"Threshold
table: see para. 17.7 on page 297.
'Eps Overview:
Allows to display as well as search for EPS states.

'Set ACD level:
'Cross Connection Management: Manage the connection of the paths.

'Loopback Management:Enter the loopback management.
Used to configure the loopback command for commissioning or
maintenance purposes.
'Comm/Routing:
Enter Communication and Routing management.

Used to define the parameters for NE and OS in the TMN, opening the
following menu options:
"Local
configuration
Configuration
"NTP Server Configuration
"Interfaces Configuration
"OS
"LAPD
Configuration
Configuration
"RAP Configuration
"MESA Configuration
"IP Static Routing Configuration
"OSI Over IP
"Ethernet
"OSI
"IP
Routing Configuration
Configuration
Configuration
"Tunneling
'Overhead:
Handle the operation on the Overhead bytes.

Used to define the parameters in the following menu options:
"OH
Cross Connection
Phone Parameters
"OH TP creation
"OH TP deleting
"OH
'MSP Overview:
It allows to display as well as search for MSP states.

'PM Overview:
It shows both PM and Monitoring Objects. Search operations are allowed

for PM objects, Monitoring objects or both.
1AA 00014 0004 (9007) A4 ALICE 04.10
'ATM/IP/ETH configuration:
Allows to create the TPs for the ATM/IP/ETH connections.

In current release ETH connections are only available.
'Alarm Persistency Configuration: This feature has the aim to avoid transient alarm conditions for
2 Mbit/s. NOT USED for this NE.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
22 / 448

'Performance:
2.2.3 Diagnosis menu introduction

This menu permits to get information about the NE, by means of the following entries:
Diagnosis
'Alarms:
Display the Alarms Surveillance information of the NE.

It opens the following menu options:
"NE
alarms
alarms
"Subtree alarms
"Equipment alarms
"Transmission alarms
"External Points alarms
"Object
'Log Browsing:
Manage the events stored in the NE.

"Alarm
Log
Log
"Software Trace Log
"Event
'View:
Display the remote inventory data, previously stored in the CT by means

the upload remote inventory performed in the Supervision menu.
See para. 7.4.2. on page 69.
"Remote
Inventory
1AA 00014 0004 (9007) A4 ALICE 04.10
'Abnormal Condition list: Display the list of the object class (Loopback, ALS Handler, protection
board) and the name of the boards that are in abnormal condition.
ED
'Internal link monitor:
Display the status of links between SC and ports.

'Dataflow Analyzer:
Not operative in current release.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
23 / 448
2.2.4 Supervision menu introduction

This menu permits to set the supervision states of the NE, by means of the following entries:
Supervision
'Access State:
Manage the supervision access to the NE, with CT or OS.

"OS
"Requested
'Alarms:
Manage the alarms supervision of the NE.

"Resynchronize
"Allow
/ Inhibit Notifs

'Upload Remote Inventory:
Store the Remote Inventory data in the CT.

'Set Manager list:
'Restart NE:
Reset the NE software.

See para. 4.4 on page 54 .
2.2.5 MSSPRing menu introduction

This menu permits to manage the 2 Fiber (2F) and 4 Fiber (4F) MSSPRing protection, setting the relevant
configuration, by means of the following entries:
MSSPRing
'Main dialog for MSSPRing management:
Contains all the commands to set and manage the

MSSPRing.
2.2.6 Download menu introduction

This menu permits to manage the NE software, by means of the following entries:
1AA 00014 0004 (9007) A4 ALICE 04.10
Download
'Init download:
Manage the software download, upgrading the NE.

'Units info:
Show the status of the software package installed in the NE memory banks.
'Mib management: Permits backup of NE software configuration and restore of backupped file.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
24 / 448

2.2.7 Equipment menu introduction

This menu permits to manage the NE as a whole, setting the boards which compose it, by means of the
following entries:
Equipment
'Set:
Add or change the board type (a list is proposed) and add / remove the
1670SM subracks.
'Modify:
Change the board type without previously remove it. It is only possible
between compatible board or modules (ex. it is possible to change from
an Long and Short 1.1 optical module).
'Remove:
Remove the board.

'Set in service:
Insert a lock symbol in the board.

'Set out of service:
Delete the lock symbol in the board, enabling changes.

'Cable Configuration:
Define the exact connection between the units and booster amplifier.
'Reset:
Not operative.
'Software description:
Show information on the software of the board.

'Remote Inventory:
Show the Remote Inventory data inserted in the equipment.

"Subrack
"Board
level
level
1AA 00014 0004 (9007) A4 ALICE 04.10
'Show supporting equipment: Navigate to the upper equipment level.

ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
25 / 448
This menu permits to show the physical port available in a specific board (alarm synthesis and port symbol)
and to access the port view, by means of the following entries:
Board
'Port Access:
Access the Port view.

'Change Physical Interface:
Change the SPI or PPI object into PPI or SPI (and viceversa) on the
bimode port (140 Mbi/s / STM1 switchable).
'Show supporting equipment: Navigate to the upper subrack level.

'ATM/IP/ETH configuration:
Allows to create the TPs for the ATM/IP/ETH connections.

In current release ETH connections are only available and this menu
is only available if an ETH board has been equipped in the subrack.
2.2.9 Port menu introduction

This menu permits to set and show the transmission resources (TP) referred to the Port, by means of the
entries indicated in the following list.
The menu differs according the port type (SDH, PDH, HOA and ETH).
The Port view is reached by means the Equipment menu and Board view to check the detailed alarms
presented, but the available menu permits to configure the port (many setting options listed in the port
menu are common with the Transmission view).
In these views are presented only the TP specific of the port.
It permits navigation to the Transmission view.
Port
'TP configuration:
'TP Threshold Configuration:
Set B2 excessive BER and Signal Degraded parameter.

'AU4 Concatenation:
Only for SDH ports views.

'Cross Connection:
1AA 00014 0004 (9007) A4 ALICE 04.10
Set parameters for the Overhead (Signal Label and Path Trace) on
Synchronous TPs.
Manage the connection of the paths.

"Cross
Connection Management
Cross Connection
"Modify Cross Connection
"Create
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
26 / 448

2.2.8 Board menu introduction

'Monitoring Operations : Set parameters for POM / SUT / TC TPs.

Not available for PDH port. It opens the following menu options:
"Creation
/ Deletion
"Configuration
'Performance:
Set and show Performance Monitoring parameters and data.

For SDH port:
Monitoring
"Display Current Data
"Display History Data
"Configure
For Ethernet port:

Monitoring (not operative in current release)
"Display Current Data (not operative in current release)
"Display Maintenance Counter (not operative in current release)
"Configure
'Loopback:
Enter the loopback management.

maintenance purposes. It opens the following menu options:
"Port
Loopback Configuration
management
"Loopback
'MSP:
Manage the Multiplex Section Protection of the NE.

"MSP
Create
Management
"MSP Commands
"MSP Delete
"MSP
'Physical Media:
Manage the physical setting of the TP of the ports.

For SDH port:
Management
"Show Optical Configuration
"TX Quality Configuration
"Single Fiber Configuration
"LAPD Configuration
"Ms Configuration
"ALS
For Ethernet port:

Laser Management
"ALS Management
"Ethernet Port Configuration
"ATM/IP/ETH Configuration
"Control Path Activation
1AA 00014 0004 (9007) A4 ALICE 04.10
"Remote
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
27 / 448
Navigate to the upper board level.

'Navigate to Transmission View:
Permit to show a complete overview about the signal flow,

opening all TPs.
'Navigate to Monitoring View:
Permit to show a complete overview about the signal flow,

between SC and boards.
'Navigate to HOA port View:
Permit to show the HOA port associated to a selectde TP (for

example, the HOA port associated to an AU4 in a VC4); it is
available on SDH ports only).
2.2.10 EPS menu introduction

This menu permits to manage the EPS protection, setting the relevant configuration, by means of the
following entries:
1AA 00014 0004 (9007) A4 ALICE 04.10
EPS
ED
'Management:
Set EPS protections.

'Configure:
Set revertive / not revertive and WTR parameters.

'Switch:
Manage the EPS operator commands (Force, Manual, Lockout).

01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
28 / 448

'Show Supporting board:

2.2.11 Transmission menu introduction

This menu permits to show and set the Termination Point of the equipment, thus having an overview of
the complete signal flow of the various port.
The menu permits to define all the Cross Connections and manages the transmission resources, setting
the relevant configuration.
Further access the Performance Monitoring and manage Multiplex Section Protections and Loopbacks
functions.
It permits navigation to the Port view.
The menu lists the following entries:
Transmission
'Add TP:
Search and add TP to the transmission view, than presented in the screen.
'Expand:
Display the TPs related to a selected TP.

"Next
Level of Lower TPs

Lower TPs
"Next Level of Upper TPs
"All Upper TPs
"All
'Hide:
Remove the TP from the screen of the Transmission view.

"Lower
TPs
TPs
"Selected TPs
"Upper
1AA 00014 0004 (9007) A4 ALICE 04.10
'TP configuration:
ED
Set parameters for the Signal Label and Path trace.

'TP Frame Mode Configuration:
Not used for this NE.
'TP Threshold configuration:
Set B2 Ex BER and Signal Degrade threshold.

'Terminate TP:
Terminate the AU4CTP paths.

'Disterminate TP:
Disterminate the AU4CTP paths.

'AU4 Concatenation:
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
29 / 448

'Cross Connection:
"Cross
Connection Management
Cross Connections
"Modify Cross Connections
"Port Switch Over
"Show Cross Connected TPs
"Create
'Monitoring Operations : Set parameters for POM / SUT / TC TPs.

Not available for PDH port. It opens the following menu options:
"Creation
/ Deletion
"Configuration
'Performance:

For SDH port:
Monitoring
"Display History Data
"Configure
For Ethernet port:

Monitoring
"Display Maintenace Counter
"Configure
'Structure VC4:
Define the structure of a selected TP. Not used for this NE.
'Loopback:
Enter the loopback management.

maintenance purposes. It opens the following menu options:
"Port
Loopback Configuration
"Loopback management
'Physical Media:
Manage the TP physical setting.

"ALS
Management
Optical Configuration
"TX Quality Configuration
"Single Fiber Configuration
"Extra traffic
"Regeneration Section management
"Line Length Configuration
"Set Domain
"HDSL Configuration (not used for this NE)
"NT Configuration (not used for this NE)
"X21 Configuration (not used for this NE)
1AA 00014 0004 (9007) A4 ALICE 04.10
"Show
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
30 / 448

'MSP:

"MSP
Create
Management
"MSP Commands
"MSP Delete
"NE MSP Synthesis (not operative in current release)
"MSP
'Show Supported Board: Navigate to the board supporting the selected TP.
'Navigate to Port View: Navigate to the port supporting the selected TP.
2.2.12 Synchronization menu introduction
This menu permits to set and show the Synchronization parameters and status, setting the relevant
configuration, by means of the following entries:
Synchronization
'Timing Source Configuration: Set timing source priority and quality for the selected input reference.
'Protection Command:
Manage commands (force, manual, lockout) for the selected timing

reference.
'T0 Configuration:
Enable/disable SSM and WTR on the T0 synchronization source.

'T4 Configuration:
Enable/disable SSM, WTR and Squelch Criteria on the T4

synchronization source.
'SSU Configuration:
Set NE single or with SSU. See para. 18.2.6 on page 326.
'Remove Timing Reference: See para. 18.2.7 on page 327.

'Change T4<>T5:
Change the synchronization physical interface from 2 MHz (T4) to

2 Mbit/s (T5) without traffic and viceversa.
'Set T0 Equal T4:
'Remove T0 Equal T4:
1AA 00014 0004 (9007) A4 ALICE 04.10
'Transmitted SSM Quality Configuration:Set SSM quality transmitted on the selected T1 SDH
timing reference.
'Frame Mode Configuration: Not used for this NE.
'Show Timing Source:
ED
01
Show the port view related to the selected timing reference.

SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
31 / 448
This menu permits to display and set the input/output environmental alarm (housekeeping alarm), by
means of the following entries:
External Points
'Configuration:
Set the input/output environmental alarm.

'Display:
Show the list of the input/output environmental alarm.

"Show
external Input Points

external Output Points
"Show all external Points
1AA 00014 0004 (9007) A4 ALICE 04.10
"Show
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
32 / 448

2.2.13 External Points menu introduction
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
D
Synchronization
OSI Over IP
IP Static Routing
Configuration
MESA Configuration
Tunneling
Configuration
IP Configuration
OSI Routing
Configuration
Interfaces
Configuration
3AL 81947 BA AA
448
Configuration
ATM/IP/ETH
PM Overview
Internal Link
Monitor
Abnormal
Condition List
View Remote
Inventory
Software Trace Log
Event Log
Alarm Log
Log Browsing
Dataflow Analyzer
External Points
alarms
Transmission alarms
Equipment alarms
Subtree alarms
Object alarms
MSP overview
OH TP Deleting
OH TP Creation
Oh Phone
Parameters
OH Cross
Connection
Overhead
Comm/Routing
Loopback
Management
Cross Connection
Management
Set ACD level
EPS overview
Threshold table
Performance
NE Time
NE alarms
Alarms
Diagnosis
Close
Open in Window
Open Object
RAP Configuration
Ethernet
Configuration
LAPD Configuration
NTP Server
Configuration
OS Configuration
Local Configuration
Set SdhNe Alarm

Severities
Set Alarm Severities
Alarm Severities
Configuration
Refresh
External Points
Transmission
A
E
Equipment
Forward
Note: A,B,C,D and E See next figures
Backward
Views

Figure 2. Menu options flow chart 1
SC.3:NE MANAGEMENT
33 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
Alarms
Requested
3AL 81947 BA AA
448
Note: A, See previous figures

F, See next figure
Restart NE
Set Manager list
Upload Remote
Inventory
Mib
Management
Units info
Remote Inventory
Software
description
Reset
Set out of service
Set in service
Remove
Modify
Set
Equipment
ATM/IP/ETH
Configuration
Show supporting
equipment
Change Physical
Interface
Port Access
Board

Cable Configuration
Show supporting
equipment
Board level
Subrack level
Inhibit Notifs
Allow Notifs
Resynchronize
OS
Init download
Download
Main Dialog for

MSSPRing
Management
MSSPRing
Access State
Supervision
SC.3:NE MANAGEMENT
34 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
with ETH board
Configure
Monitoring
Note: F and C, See previous figures
01
TP Thresholds
configuration
TP configuration
ALS Management
3AL 81947 BA AA
448
Navigate to
HOA port View
Navigate to
Monitoring view
Navigate to
Transmission view
NE MSP synthesis
Show supporting
board
LAPD config.
Ms Configuration
MSP Delete
Physical Media:
MSPCommands
commands
MSP
Single Fiber
Configuration
MSP Management
MSP Create
Set Domain
Line Lenght
Configuration
MSP
Loopback
Performance
Configuration
Creation / deletion
Monitoring
Operations
Regeneration
Section manage
Extra traffic
Single Fiber
Configuration
Tx Quality
Configuration
Show Optical
Configuration
Loopback
management
Port Loopback
Configuration
Display History
Data
Display Current
Data
Modify Cross
Connection
Create Cross
Connection
Cross Connection
Management
TX Quality
Configuration
Navigate to
Port View
Show Supported
Boards
MSP
Physical Media:
Loopback
Structure VC4
Performance
Configuration
Creation / Deletion
Monitoring
Operations
Cross Connection
AU4Concatenation
Disterninate TP
Terminate TP
TP Threshold
Configuration
TP configuration
Hide
ALS
Management
with SDH port
Control Path
Activation
ATM/IP/ETH
Configuration
Ethernet Port
Configuration
ALS
Management
Remote Laser
Management
Cross
Connection
Show Optical
Configuration

AU4
Concatenation
Expand
Add TP
Transmission
Port
Loopback
management
Port Loopback
Configuration
Display History
Data
Display Current
Data
Configure
Monitoring
Show Cross
Connected TPs
Port Switch Over
Modify Cross
Connections
Create Cross
Connections
Cross Connection
Management
Selected TPs
Upper TPs
Lower TPs
All Upper TPs
Next Level of
Upper TPs
All Lower TPs
Next Level of
Lower TPs

SC.3:NE MANAGEMENT
35 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Note: B, D and E, See previous figures
ED
01
Switch
Configure
3AL 81947 BA AA
448
Show Timing
Source
Frame Mode
Configuration
Transmitted
SSM Quality
Configuration
Remove
T0 Equal T4
Set T0 Equal T4
Change
T4 <> T5
Remove Timing
Reference
SSU Config.
T4 Configuration
T0 Configuration
Protection
Command
Timing Source
Configuration
Display
Configuration
External Points
Show All
External Points
Show External
Output Points
Show External
Input Points

Synchronization
Management
Eps
SC.3:NE MANAGEMENT
36 / 448

2.3 Advices on navigation principles

Navigation rules are the same for all the NE using the same Craft Terminal Info Model.
This general rules are described in the 1320CT Basic Operator Handbook.
In this paragraphs are instead inserted menu options typical for this NE involved in Navigation and
example of Navigation.
To reach a particular view of the NE there are several ways (navigation is also possible mixing the different
ways):
double click on the selected object;
select the object and use the Open object or Open in Window option of the Views pull down
menu;
use the Menu option tree structure. The Views pull down menu permits to show the following
menus:
Equipment
Transmission
Synchronization
External Points
The menu structure permits to open the same window following several menu paths.
EXAMPLE: to obtain the Create Cross Connection window:
First navigation path:

Open View ' Transmission pull down menu.
Open Transmission ' Cross Connection ' Cross Connection Management pull down
menu.
Select Create option in the presented window.
Second navigation path:

Open Views ' Equipment pull down menu.
Double click on EquipmentRackSubrackBoard.
Select the Board to access the Board view.
Open Board ' Port Access pull down menu.
Open Port ' Cross Connection ' Create Cross Connection pull down menu.
Third navigation path:

Open Configuration ' Cross Connection Management pull down menu.
Select Create option in the presented window.
1AA 00014 0004 (9007) A4 ALICE 04.10
The menu structure also permits to pass from a view menu to another (i.e. from port view toboard view
or to transmission view) thus facilitating the operators activity.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
37 / 448
The first level of the Equipment Overview representation will be displayed directly into the current
window, immediately after the NE login (see Figure 1. on page 18).
The Equipment view enables a fast navigation through all levels of the equipment hierarchy.
Navigation is done from higher to lower levels. The NE hierarchy is generally organized in the following
way:
rack ' subrack ' board ' port ' TP
The navigation through different levels of the NE hierarchy is performed by double clicking on the objects
(see also para. 9.1 on page 91):
the first level shows the rack level of the Equipment view (see Figure 1. on page 18);
by double clicking on the Equipment body, the subrack level of the Equipment view is reached;
further, by double clicking on a board body, the board level of the Equipment view can be
reached;
further, by double clicking on a port body contained in the board, the port level of the Equipment
view can be reached. The port view displays the inner TPs;
it is possible to go back to the upper level of representation by pressing the <ESC> key on the
keyboard; or to go back to the previous view, by selecting the Previous option from the Views
menu.
1AA 00014 0004 (9007) A4 ALICE 04.10
Note: Selecting in the first level of the Equipment view (rack level, Figure 1. on page 18) the Show
supporting equipment option from the Equipment menu, the Equipment level view is presented.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
38 / 448

Views Navigation
3 NE MANAGEMENT SUPERVISION
1AA 00014 0004 (9007) A4 ALICE 04.10

This chapter is dedicated to the NE states and NE access.
3.1 NE management states

The elementary building blocks of any telecommunication network are the Network Elements (NEs).
Operating with the Craft Terminal the NE can present different management states according to the
condition of the connection (supervision, local access, connection state, etc).
Also general Alarm status are presented.
Management states are present at Network Element Synthesis view level and at USMEML view level.
All the information referred to the management states are inserted in the 1320CT Basic Operators
Handbook.
Any disruption in the communication link between the CT and the NE results in an update of the
management states when the CT has detected the communication failure.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
39 / 448
The Network Element Synthesis views enable you to get access to the current NE EMLUSM view
described in this handbook.
The Network Element Synthesis view enable to work on local or remote NE, selecting it and activating
Supervision and Show Equipment options as described in the 1320CT Basic Operators Handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
The EMLUSM Main view is presented as for the following figure.
Figure 6. NE EMLUSM Main view
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
40 / 448

3.2 NE supervision and login

4 NE MANAGEMENT GENERAL CONFIGURATION

In this chapter general configuration referred to the equipment management are described (Craft Terminal
access, NE Time, Alarms configuration, etc.).
4.1 Access state (allow or inhibit NE Craft access)

The NE can be managed by the OS or by the Craft Terminal. To control the competition of the OS and the
CT, a Local Access Control (LAC) is available.
If the LAC is granted that means the CT is allowed to manage the NE. In the view the icon with a key
symbol has a rectangular shape.
If the LAC is access denied that means the OS manages the NE and the CT is not allowed to modify NE
configuration (it can only read). In the view the icon with a key symbol has a circular shape.
If the LAC is requested that means the CT has requested permission from the OS and is waiting for a
replay.
However the OS does continue to provide a certain number of services. These services includes:
Reception and processing of alarms
Performance processing on TPs
Switching back to the OS access state
1AA 00014 0004 (9007) A4 ALICE 04.10
The access state of an NE can be modified from two types of views.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
41 / 448
Select the Supervision pull down menu. Then select the Requested option from the Access State cascading menu as shown in the following figure.
Figure 7. NE management: setting the access state

From the confirmation dialogue box that opens you can confirm or cancel the Craft access operation using
the Yes or No push buttons. the request is up to the OS which accept or refuse it.
If the OS doesnt answer in a predefined time it is assumed that the NE is in the Craft access state and can
be managed from a Craft Terminal.
4.1.2 Switching from the Craft Terminal access state back to the OS access state
Select the Supervision pull down menu. Then select the OS... option from the Access State cascading
menu in Figure 7. on page 42.
From the confirmation dialogue box that opens you can confirm or cancel the OS access operation.
The NE is now managed by the OS.
1AA 00014 0004 (9007) A4 ALICE 04.10
Notes:
ED
The key symbol icon on the management states of the NE view, indicates whether the NE is
managed by a craft terminal or by the OS.
Local Craft Terminal access is denied on recovery phase after a loss of communication of the
NE. When communication is lost with the NE, the OS automatically recovers the communication
and put the state that was set before the loss of communication (therefore the Craft Terminal
access can be denied or granted).
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
42 / 448

4.1.1 Switching from the OS to the Craft Terminal access state
4.2 NE Time management

The NE local time of a selected NE can be visualized and/or realigned on the OS time basis.
In this view the OS indication identifies the Craft Terminal.
The status of the Network Time Protocol can be checked.
Select the NE Time... option from the Configuration pull down menu.
Figure 8. Consulting and/or setting the local NE time

The following dialogue box is opened from which you can get and/or set the local NE time and check the
NTP Status.
The following fields are available (see Figure 9. on page 44 ):
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
NTP Status section (read only) with the following parameters:
NTP protocol
It can be enabled (in the NTP Server Configuration option at para 8.5 on page 81) or disabled
or empty (greyed).
NTP Main and NTP Spare

It displays the status of the Main and Spare NTP: reachable or unreachable.
Time section with the following data:
NE Time and OS Time

It displays (read only) the time of the Network Element and of the OS (Craft Terminal).
Set NE Time With OS Time

It permits to align the NE time with the time of the CT of the NE and of the CT.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
43 / 448
NTP protocol enabled

In this case, NTP Main and NTP Spare will be reachable or unreachable. When both are reachable
the NE uses the Main.
The Set NE Time With OS Time message is not operative and the user cannot set manually the NE
Time.
NTP protocol disabled

In this case, the NTP Main and NTP Spare are empty (greyed); the Set NE Time With OS Time message is operative and the user can set manually the NE Time (i.e. change the NE time with the Time
of the Craft Terminal).
If you do not want to set the NE local time, click on the Close push button to close the dialogue box.
To realign the NE time on the OS time basis click in the Set NE Time With OS Time radio button and either
click on the Apply push button to validate or on the Close push button to cancel and close the dialogue
box. The OS time comes from the PC date configuration which corresponds to the legal GMT time.
1AA 00014 0004 (9007) A4 ALICE 04.10
Note:
When the NTP is not present, the OS system realigns the time of all supervised NEs
periodically and automatically with a configured periodicity. This periodicity is common for all
the NEs.
If you set the NE time, you will force the change, with an immediate effect on the NE. However
it will not have any effect on the periodic and automatic mechanism.
Figure 9. NE Time dialogue box
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
44 / 448

Two different operative conditions can be defined:
4.3 Alarms Configuration

The operations described in this chapter, mainly related to alarm setting, are:
Alarm Severity Assignment Profile management

Allow/Inhibit alarm notification
Alarm resynchronization
4.3.1 Procedure to modify an ASAP

To modify an ASAP:
select the TP (or the board/port/etc...) whose ASAP is to be changed

from the menu click on Configuration > Alarms Severities... option
(see Figure 11. on page 46) select one of the user profiles (#10001 or #10002) and click on
Modify
(see Figure 12. on page 48) click on the Probable Cause Families associated to the alarm
select the relevant alarm in the list of Probable Cause Name
in the Service affecting/nonaffecting fields select the needed severity (critical/major/minor...)
click on OK
(see Figure 11. on page 46) click on Close
select the relevant TP and then Configuration > Set Alarms Severities... option
in the box that appears select the just modified ASAP (evenctually check it by means of Detail)
click on OK
For further details see paragraphs 4.3.2, 4.3.2.1, 4.3.2.2 on next pages.
4.3.2 Alarm Severity Assignment Profile Management (ASAP)
Managed entities yield alarms when they malfunction. This section deals with the configuration of ASAPs.
An ASAP is a list of Alarm probable causes to which Severities Profiles are assigned, predefined or settable by the operator.
Three important notions are:
the Probable Cause of the alarm

the Severity of the alarm
the Alarm Type (communication alarm, equipment alarm)
4.3.2.1 Alarm Severities

This option permits to configure and display the ASAP.
1AA 00014 0004 (9007) A4 ALICE 04.10
Select the Alarms Severities... option from the Configuration pull down menu as shown in the following
figure.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
45 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 10. Configuring Alarm Severity Assignment Profile
The ASAP Management dialogue box is displayed.
Figure 11. ASAPs Management dialogue box
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
46 / 448

The default presented profiles are:
Profile All Alarms. With this profile all the alarms are enabled (only Sfwr Download Failure
is not alarmed).
This ASAP enables the emission of all alarms.
Profile No Remote Alarmsshows the alarm criterion configuration defined for path alarms
(only AIS and RDI and Sfwr Download Failure are not alarmed).
This ASAP enables the emission of all:
Communication Alarms (i.e. the AIS & RDI alarms are not alarmed)
Equipment alarms
Environmental
Error Processing (i.e. Sfwr Download Failure is not alarmed)
Profile Primary alarms. With this profile the AIS, Battery Degraded, Sfwr Download Failure,
SSF and RDI alarms are not alarmed.
This ASAP enables the emission of all:
Communication Alarms (i.e. the AIS, SSF & RDI alarms are not alarmed)
Equipment alarms
Environmental
Error Processing (i.e. Sfwr Download Failure is not alarmed)
Profile No Alarms : (i.e. all alarms disabled).

This ASAP inhibits the emission of any potential alarm.
Profile 10001 can be set by the user.

Each single alarm can be classified with a criterion selected by the operator.
A default standard configuration is set (Battery Degraded, Battery Failure, Communication Subsystem Failure, Path Trace Mismatch are not alarmed).
NOTE: if this profile is not already present in the list, it is necessary to create it, by using the
dialog of Figure 11. on page 46, selecting one existing profile and then clicking on the Clone
button.
You can select an ASAP.

For ASAP 10001 it is then possible to choose Detail, Modify, Clone or Delete buttons.
For ASAP No Alarms , Primary alarms, No Remote Alarms and All Alarms it is only possible to
choose Detail, or Clone buttons.
Clone selection can be used to create new ASAP.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on Detail, Modify, or Clone button, the ASAP edition dialogue box is displayed.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
47 / 448

Figure 12. ASAP Edition dialogue box

The alarm severity assignment profile dialogue box displays a list of probable causes and a list of alarm
severity.
The Probable cause family check buttons allows to filter the probable causes that will appear in the Probable cause name list. NOTE: it is necessary to choose one or more of these filters to have the list.
To find a particular probable cause, enter its name in the Search entry box at the bottom.
ASAPs are already defined in the system with default values for the assigned severities.
You can modify the severity associated with each probable cause. To do this, select the probable cause
whose severity level you wish to modify.
Then click on the option button: Service Affecting (not protected probable cause), and then Non Service
Affecting (protected probable cause) and then Service Independent (dont used, it is not operative). For
each the severity can be chosen from Critical, Major, Minor, Warning, Nonalarmed or Not used.
A Nonalarm probable cause corresponds to no alarm emitted for this probable cause.
When selecting Details the assigned severity are only shown and it isnt possible to modify.
When you have finished configuring ASAP, press the OK button to confirm the settings and close the dialogue box or the Cancel push button to cancel the new settings and close the dialogue box.
1AA 00014 0004 (9007) A4 ALICE 04.10
When Clone an ASAP the created one is identified with next number (10002, ....).
The max number of ASAP is six.
NOTE: The number of severities and the number of probable causes is fixed. The ASAP function only enables the modification of the severities assigned to the probable causes, it does not allow the addition,
removal or modification of these severities and causes.
To take into account a profile modification, it is mandatory to perform a resynchronization of the alarms
(see para. 4.3.4 on page 53). During this resynchronization, the severity of each alarm is updated. Otherwise, the severities are updated only when the modified or new alarms are emitted by the NE.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
48 / 448

4.3.2.2 Set Alarms Severities

This option permits to send (i.e. to provision) the chosen ASAP to the previously selected object (rack,
subrack, board, port, TP).
If the severity profile is to be changed, it must be done by means of the Modify option, as described in
the previous paragraph (see procedure in para. 4.3.1 on page 45).
It permits also to check the currently operative ASAP used by the object.
Select the Set Alarm Severities... option from the Configuration pull down menu as for Figure 10. on
page 46.
Note: the Set Alarm Severities option is accessible only if an object has been selected.
The Set ASAP dialogue box is displayed (Figure 13. ).
The List of ASAPs on the left side lists all available ASAPs (Alarm Severity Assignment Profiles). The
ASAP currently operative on the object is highlighted.
To choose an ASAP select a new one of the presented list.
Clicking on Detail button, or doubleclicking on an ASAP, a dialogue box is displayed, as that in Figure 12.
on page 48, which displays detailed information about this ASAP.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 13. Set ASAP dialogue box
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
49 / 448
Choose Scope
Selected object only

The new ASAP is only applied to the object currently selected in the view.
This is the default if an object is selected in the view.
Network element
The new ASAP is applied to all objects of the NE matching the criteria specified in Choose Classes
and Choose current ASAP.
Since this application process takes some time, its progress is shown in the Section Execution
Monitoring.
This is the default if no object is selected in the view.
Selected object and subordinates

The new ASAP is applied to the selected object and those of its subordinates matching the criteria
specified in Choose Classes and Choose current ASAP.
Since this application process takes some time, its progress is shown in the Section Execution Monitoring.
N.B.
Due to system architecture, AU4 CTPs are no subordinates of MSTTPs. Therefore, if the
AU4 CTP should be included as subordinate, select the related OSTTP (OpS) or ESTTP
(ElS) as main object.
Choose Class(es)
Enabled if one of the scopes Network element or Selected object and subordinates is selected.
All classes
Specific class(es)
Select one or more object classes the new ASAP shall be applied to.
Choose current ASAP

The new ASAP is only applied to objects which are currently assigned to this ASAP.
Execution Monitoring
Continuously shows the number of modified objects during the ASAP application process if one of the
scopes Network element or Selected object and subordinates is chosen.
1AA 00014 0004 (9007) A4 ALICE 04.10
Press Ok to confirm the ASAP assignment and close the dialog. Press Close to close the dialog and discard any changes.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
50 / 448

Within the Apply to section on the right side, the user specifies the objects (TP or equipment) the ASAP
selected in the List of ASAPs (new ASAP) should be applied to:

4.3.2.3 Set SdhNE Alarms Severities

Selecting the Set SdhNE Alarms Severities option from the Configuration pull down menu only the
alarms at Equipment level are managed as reported in the table below.
Table 1. Alarms at Equipment level
1670SM
FF
ABF
SDH NEs managed alarms
BKF
SHD
Note: for details information on SDH NE alarms refer to NE MAINTENANCE section of this handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 14. Set SdhNE Alarms Severities

If an object was selected in a view before opening this dialog, its ASAP is highlighted in the list. Using the
Detail button or doubleclicking on a list item opens the ASAP Edition dialog which displays detailed information on this ASAP.
Press Ok to confirm the ASAP assignment and close the dialog. Press Close to close the dialog and discard any changes.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
51 / 448
4.3.3 Allow/Inhibit Alarms Notifications
a)
To inhibit alarm notification

Select the Supervision pull down menu. You can then select the Inhibit Notifs option from the Alarms
pull down menu as shown in the following figure.
Figure 15. Inhibit alarm notification
From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok
or Cancel push buttons respectively.
To inform the operator that alarms have been inhibited, the labels of the alarm panel are greyed out.
See following figure.
Figure 16. Alarm inhibition action
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE: inhibiting the alarms notification means that they are not forwarded to the CT but alarms are
still generated by the NE.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
52 / 448

The system provides the possibility to allow/inhibit the spontaneous incoming alarm notifications.

b)
To allow alarm notification

Select the Supervision pull down menu. You can then select the Allow Notifs option from the Alarms
pull down menu as shown in the following figure.
Figure 17. Allow alarm notifications

From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok
or Cancel push buttons respectively.
4.3.4 Alarms resynchronization

The system provides the possibility to recover alarms present on the NE and to update the current problem
list of the NE. After this operation CT and NE current alarms are consistent.
To resynchronize the alarms, select the Supervision pull down menu. You can then select the Resynchronize option from the Alarms pull down menu as shown in the following figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 18. Alarm resynchronization

From the confirmation dialogue box that opens you can confirm or cancel the operation using the Ok or
Cancel buttons respectively.
NOTE: This functionality has to be used only if there is any perturbation. Never use this operation during
a correct behavior.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
53 / 448
4.4 Restart NE

The restart operation is a software reset and can be executed in normal traffic conditions.
The restart operation in any case activates the Commit (active) version.
Select the Restart NE option from the Supervision cascading menu.
The following dialogue box is opened.
Figure 19. Restart NE confirmation

Click on the OK button to perform the restart NE.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on the Cancel button to abort the restart NE.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
54 / 448
5 SECURITY MANAGEMENT

In this chapter are inserted setting options referred to the SECurity management.
5.1 Set Manager list

This option is referred to the SECurity management and allows the user to set the Manager list and the
Access Control Domain of the NE.
Select the Set Manager list option from the Supervision pull down menu.
The dialogbox contains the following fields:
Manager list: each connected manager to the NE is highlighted in the list. The user can set a manager clicking on the denomination.
Several manager can be enabled contemporaneously, having in charge the NE.
The Manager List contains the list of managers ( i.e. RM, SY, NPOS , EML) that work on the NE. The
EMLUSM administrator (SH or Craft Terminal) should set the Manager List only to remove a manager in case of emergency (i.e. the Manager misses the NE connection).
NE Domain field allow to select the domain among that displayed in the list, assigning it to the NE.
The different domains could be assigned to different operators.
OK button is used to validate the selection.

Cancel button close the dialog without changes of the data.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 20. Set Manager list
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
55 / 448
5.2 Set ACD level
The ACD manage the concurrence of access among several different managers (i,e. RM and EML).
This only acts on the functions that can be used by different manager.
Select the Set ACD level option from the Configuration pull down menu.
Current ACD level

Show the Access Control Domain level currently set.
The Access Control Domain check level

Permit to set one of three level checks. By the way, this is an operation that should be performed only
during the EMLUSM installation phase:
NE level, the ACD is performed on all the NEs

No Check, the ACD is not managed
The default value is NE level. If it is changed, it is necessary to restart the EMLUSM.

1AA 00014 0004 (9007) A4 ALICE 04.10
Close button close the dialog without changes of the data.
Figure 21. Set ACD level
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
56 / 448

This option allows the user to select the level of the Access Control Domain.

6 EXTERNAL INPUT AND OUTPUT POINTS MANAGEMENT

This chapter describes how to display and set the input/output environmental alarm (housekeeping alarm),
An external input point is an environmental alarm (also called housekeeping alarm). It corresponds to an
external event which is monitored by the NE. Number of relays on the NE are dedicated to check modification of the environment as for example a fire or a flood.
An external output point is used to manage a NE contact (i.e. relay) connected to detector. An external
output point is independent from external input point.
The operations that can be undertaken in this section are:
Displaying external points
Expanding or reducing external points list
Configuring input and output external points
6.1 Displaying external points

Select the External Points option from the Views pull down menu as shown in the following figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 22. Opening the external points view

After selecting this menu option the external points view is displayed into the current window instead of
the current view.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
57 / 448

Figure 23. External points view (example)

The external points view displays a list of all input and output points. The following information is given
for each external point:
1AA 00014 0004 (9007) A4 ALICE 04.10
the external point Type: Input or Output.

the User Label: a userfriendly label associated to the configurable external point (see further the
paragraph External points configuration).
the External State: represents the alarm state. On when the alarm is raised, else Off. If the external point is active (On), a little red flag is represented near the status of the concerned point.
Only for the Output external point there is the following information:
ED
the Output criteria: if configurated, display the alarm event and the board affected associated to
the Output point (see further the paragraph External points configuration).
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
58 / 448

6.2 Expanding or reducing external points list

The external points view displays a complete list of the external points but it can also be restricted to the
input or to the output points.
To see either the input points, the output points or all the external points, select the appropriate option from
the External Points pull down menu as shown in the following figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 24. Expanding or reducing the external points list
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
59 / 448
6.3 External points configuration
user labels configuration

external state; can be set for output points (ON or OFF)
change of associated Probable Cause; only for External Input points (fixed value)
output criteria
To configure an external point, click on the concerned row of Figure 23. on page 58 and then select the
Configuration option from the External Points pull down menu as shown in the following figure.
Figure 25. Configuring external points
1AA 00014 0004 (9007) A4 ALICE 04.10
The following dialogue box is then opened, displaying information about the selected external point (Input
or Output).
Figure 26. Configuration external input point dialogue box
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
60 / 448

The configuration operations available on external points are:
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 27. Configuration external output point dialogue box (manual)
Figure 28. Configuration external output point dialogue box (flexible)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
61 / 448

Opening the dialog the current state of the selected External Point is shown.
[2]
External Input Point Configuration
User Label: this field can be filled by the user with a Label that indicate the associated event
that must be taken under check (for example presences of water or fire in the room where the
Equipment is placed)
External State: this field is set to off and cant be changed by the operator
Probable Cause: this field is set to housekeeping and cant be changed by the operator
External Output Point Configuration
User Label: this field can be filled by the user with a Label that indicate the alarm detected or
the action that must be executed if a specific event occur (for example a Pump activation when
water is present in the room where the equipment is placed)
External State: can be set to on (alarm) or off (non alarm) only if Manual option has been
selected in the Output Criteria field.
Output Criteria can be configured as:
Manual (forced). The output contact is set in a fixed way , not depending on a particular
event.
For example the output contact could be used to Manually activate a pump to drain water
from the room where the equipment is placed ; in this case is also necessary to set the
option On in the field External State.
Flexible. It is possible to define from CT the couple event/CPO#, where the event is chosen between a set of Output Criteria (LOS, RDI and LOF) and specifies the STMN interface which the Output Criteria refers to by clicking on Choose button; subsequently the TP
search dialog box will be opened.
1AA 00014 0004 (9007) A4 ALICE 04.10
When the configuration of the external point is completed, click on the OK push button to validate the
choice and close the dialogue box. The Cancel push button cancels the configuration and closes the dialogue box.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
62 / 448

[1]

7 DIAGNOSIS MANAGEMENT
Alarms are always present on the operators workspace. The different types of alarms, their number and their
severity level, are represented in all Equipment views (NE views, Board views and Port views). An icon representation is used, which change color when the relevant alarm is active. Thus, at all times, you know the number
of alarms and their severity relating to the equipment.
Access to the Alarm Surveillance to show the alarm condition is detailed in the following paragraph.
Than is presented the abnormal condition list (as result of operators command such us loop, laser forced
on etc.).
At the end the Event log access is introduced.
Information about the significance of equipment alarms and status is given in the Maintenance
section of this handbook.
7.1 Alarms surveillance

In this chapter is described the access to the Alarm Surveillance information of the NE.
It is possible to show all the Alarms or filter the alarms report.
Select the Diagnosis pull down menu. You can then select the following option from the Alarms pull down
menu (see the following figure):
1AA 00014 0004 (9007) A4 ALICE 04.10
NE Alarms:
all the NE alarms are listed in the Alarm Surveillance report which is
activated
Object Alarms:
only the alarms of the selected object are listed in the Alarm Surveillance
report
Subtree Alarms:
only the alarms of the selected object and of the relevant subtrees are
listed in the Alarm Surveillance report
Equipment Alarms:
only the alarms of the equipment management are listed in the Alarm
Surveillance report
Transmission Alarms: only the alarms of the transmission management are listed in the Alarm
Surveillance report
External Points Alarms: only the alarms of the input external point management are listed in the
Alarm Surveillance report
Figure 29. Alarm Surveillance
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
63 / 448
This view shows first a synthesis of the NE alarms (Counter Summary) with the sum of all alarms, then
a detailed list of alarms of the selected filter (Alarms Sublist).
Figure 30. Alarm Surveillance (example)

Detailed information for each alarm is supplied.
For example the board in which the alarm is detected, the status of the alarm, the alarm type, the probable
cause.
The information supplied help the operator, typically during troubleshooting operation, presented in next
section of this handbook (Maintenance section, where more details about alarms are given).
1AA 00014 0004 (9007) A4 ALICE 04.10
Detailed description of the AS screen is given in the AS Operators Handbook.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
64 / 448

Selecting any of the previously seen options, the Alarm surveillance report is displayed as for the example
of the following figure.

7.2 Abnormal Condition List

The abnormal condition provides the synthesis of NE not normal conditions listinig the events that
contribute to abnormal condition. Select Diagnosis>Abnormal Condition List (see Figure 31. on page
65). Figure 32. on page 65 is opened.
Figure 31. Abnormal condition menu option
1AA 00014 0004 (9007) A4 ALICE 04.10
r01sr1sl01/port#01P
Figure 32. Example of abnormal condition list
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
65 / 448
Loopback
ALS is disable and the laser is forced on or off
Protection units (in case of EPS, SNCP, MSP) are in lockout or in forced status
Board (or subboard) is placed in a not configured slot

The abnormal condition are the following:
Select an abnormal condition and click on OK to open the relative dialog window.
Figure 33. on page 66 is opened.
r01sr1sl01/port#01P r01sr1sl01/port#01P
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 33. Example of loopback dialog window management

The other abnormal condition types will open the corrisponding management window or will open the
window to navigate towards the management window.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
66 / 448

7.3 Log Browsing

From the Network Element context views, perform the following operations to have access to the Event
Log file:
In the Diagnosis pulldown menu, select the Log Browsing option. The following options are proposed:
Figure 34. Log Browsing options

The proposed option:
Select the Alarm Log option (Log Id # 1 ) to access the Event Log file.
The Configuration and Log Browsing ELB windows open permitting to analyze all alarms stored
in the NE.
Refer to the ELB Operators Handbook.
Select the Event Log option (Log Id # 2 ) to access the Event Log file.
The Configuration and Log Browsing ELB windows open permitting to analyze all events stored
in the NE.
Refer to the ELB Operators Handbook.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Software Trace Log option is reserved to Alcatel personnel only.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
67 / 448
This paragraph describes the access to the remote inventory of this NE.
In the Remote Inventory are stored information of identification, construction data ect.
The options used are:
Upload Remote Inventory: store the Remote Inventory data in the Craft Terminal.
View Remote Inventory: display the remote inventory data, previously stored in the Craft Terminal
by means the upload remote inventory performed in the Supervision menu.
Remote Inventory option of the Equipment menu is instead presented in para. 9.6 on page 112.
7.4.1 Upload Remote Inventory
This command stores the Remote Inventory data in the Craft Terminal.
Select the Upload Remote Inventory option of the Supervision pull down menu.
The following confirmation dialog box is opened.
Figure 35. Remote Inventory confirmation request
1AA 00014 0004 (9007) A4 ALICE 04.10
Clicking on OK after a while an information dialog box is presented.
Figure 36. Remote Inventory completed
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
68 / 448

7.4 Remote Inventory

7.4.2 View Remote Inventory

This command displays the remote inventory previously stored in the Craft Terminal by means the Upload
remote inventory.
Select the View ' Remote Inventory option of the Diagnosis pull down menu.
The Remote inventory data appears as for the following figure.
Figure 37. View Remote Inventory (example)
1AA 00014 0004 (9007) A4 ALICE 04.10
Data is displayed in specific fields:
ED
Company
It indicates the Companys (Alcatels branch) which designs the unit.
Refer to Alcatel for the abbreviations meaning (four characters).
Unit Type
It indicates the units acronym.
Unit Part Number

It indicates Alcatel or Factory products Part No.. The number indicated is that printed on the
labels or on the units front coverplates.
Software Part Number

It indicates the id. of the units resident software.
CLEI Code
It indicates the CLEI code according to Bellecore specs. TRISD325.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
69 / 448
Manufacturing plant
It indicates the Companys manufacturing plant id. within the company, producing the unit.
Refer to Alcatel for the abbreviations meaning (four characters).
Serial Number
It indicates the products serial number as specified by the NR 130 Norm.
Date identifier
It indicates the meaning of the date that follow.
It is a twodigit code supplying the following information:
00
01
02
03
04
date of construction at the time of final testing

production order data
construction date of the unit lot
date product has been forwarded to customer
customer order date
Date (YYMMDD)
The identification of the date depends on the indications stated in the previous field. When only
the year is displayed, the format must be YY
1AA 00014 0004 (9007) A4 ALICE 04.10
If the RUM alarm is present on the A4S1 access board of the Extension Subrack, the Remote Inventory data managed by the A4S1 and relative to the electrical/optical modules
HAVE NOT to be considered.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
70 / 448


7.5 Internal Link Monitor

This function improves, at the user interface level, the diagnostic associated to the hardware failure.
The presence of a failure on RX or TX side for the signal incoming/outgoing from/to the active HCMATRIX
is detected; Internal Link Monitor displays a detailed localization of the link failure: a graphical representation of all NGI link status, for the active and standby HCMATRIX is shown.
Select the Diagnosis ' Internal Link Monitor option.
As shown in Figure 38. on page 71 the first page displays the link status for the main HCMATRIX, the second one concers the spare HCMATRIX.
In detail, each page contains the following functional blocks and graphical objects:
the tab of the page displays the user label of the HCMATRIX board;
the left side of the page displays the block representing the HCMATRIX board;
the right side of the page displays the list of blocks representing the equipped boards; each
block displays a string contained the user label of the associated board;
two arrows are displayed between the HCMATRIX block and each board block; the two arrows
represent the link status in Rx and Tx side:
a red arrow indicates a link failure
a green arrow indicates a working link

the Refresh button allows to perform an explicit refresh of all the displayed information.
In order to indicate all the possible roots of the link failure, all boards that detect the link failure are represented by a red block in the page of the HCMATRIX main:
a port board is represented by a red block if a link problem is detected in the NGI Rx from the
active HCMATRIX;
the HCMATRIX is represented by a red block if a link problem is detected in one of the NGI Tx
from one of the possible port board.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 38. Internal Link Monitor
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
71 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10

7.6 Dataflow Analyzer
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
72 / 448

8 COMMUNICATION AND ROUTING MANAGEMENT

8.1 Overview on Communication and Routing Domain
The purpose of the communication and routing domain is to define configuration parameters concerning
the communication protocols for the local NE, the OS and each other related NE in order to provide a global communication capabilities inside the network.
A brief description of basic concepts and terms involved in the communication and routing domain follows.
During the TMN design process, a network is partitioned into domains; each domain can consist of a
collection of two types of nodes:
Nodes supporting a link state routing protocol ISIS; these nodes will be called adaptive routers; ISIS protocol floods the network with link state information in order to build a complete
consistent picture of the network topology. Use of ISIS routing protocol in a TMN facilitates
installation and operation due to the self learning capabilities of these protocols and automatic
network reconfiguration in case of failure; moreover the use of these standardized routing protocols guarantees interoperability in a multivendor environment.
Nodes not supporting these protocols; these nodes will be called static routers;
Networks partitions consisting of the former type of node will be called adaptive routing domains; networks partitions consisting of the later type of node will be called static routing domains.
Moreover, a node which has to take routing decisions must became Intermediate Systems, all others can
be made End Systems.
For the description of the following paragraphs use is made of Figure 39. on page 74. It is not a network
planning example, it is only used to describe L1 ,L2 , RAP and MESA.
8.1.1 Partitioning into Routing Subdomains
In order to reduce the overhead associated with distributed adaptive routing, it may be useful to divide
an adaptive routing domain into smaller routing subdomains, called areas or level 1 subdomain. A level
1 subdomain should fulfill the following requirements:
a level 1 subdomain should form a connected subnetwork; this subnetwork should have only
a few links to the outside world, compared with the number of internal links;
each node must belong to exactly one level 1 subdomain;
each node which is connected to a foreign level 1 subdomain must become a level 2 intermediate system; level 1 intermediate systems know how to communicate only with IS in the same
area; obviously, there must be at least one level 2 intermediate system per level 1 subdomain;
Level 2 intermediate systems must form a connected network, because level 1 paths cannot
be utilized for level 2 communication. This network will be called level 2 backbone.
1AA 00014 0004 (9007) A4 ALICE 04.10
In the most simple case, all nodes within a level 1 subdomain share the same area address.
In general it is allowed to have multiple synonymous area addresses within a level 1 subdomain, even if
the usage of this feature should be checked with Alcatel engineers.
The synonymous list is used to ease partitioning in the future. There is a basic rule, which must be followed
by two neighboring level 1 intermediate systems within a subdomain: there must be at least one area address in common between their two synonymous list, otherwise they are not able to communicate with
each other.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
73 / 448
In certain situations it may be desirable to partition a given network into separate routing domains, where
no routing information is exchanged between these domains. The major benefits of this partitioning are
reduction of memory, processing and traffic overhead, because there is no exchange of routing information between the domains. Communication between separate routing domains must be achieved through
the use of Reachable Address Prefixes (RAP).
A Reachable Address Prefixes represents static routing information. It can only be associated with a link
of a level 2 intermediate system, whereby this link crosses routing domain boundaries. A Reachable Address Prefixes is handled in the same way as information about a foreign level 1 subdomain within the
own domain. The Reachable Address Prefixes indicates that any packet whose destination network address NSAP matches the prefix may be forwarded via the link with witch the prefix is associated.
For example, consider network which is split into two separate routing domains:
routing domain A resides in a level 1 subdomain with area address a

routing domain B resides in a level 1 subdomain with area address b
In order to enable the communication, the Reachable Address Prefixes in routing domain A must contain
the area address b and the Reachable Address Prefixes in routing domain B must contain the area address a.
On the other hand, within a given level 1 subdomain, there can be some NEs not supporting ISIS nor
ESIS protocol (static routing). In such condition, the communication can be achieved through the use
of Manual End System Adjacencies (MESA).
A prerequisite for the use of manual end system adjacencies is that the area addresses of the connected
nodes must be the same; as a consequence the nodes must belong to the same level 1 subdomain.
Within a pure Alcatel network there is no need to use any kind of static routing. Therefore normally RAP
and MESA shall never be used.
AREA (subdomain) 1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L2
L2
L1 with MESA
L1
L2
AREA (subdomain) 2
L2
L2
L1
= NE not supporting ISIS
1AA 00014 0004 (9007) A4 ALICE 04.10
L1
with RAP
= NE
L2
L1
L1 with MESA
L1
AREA (subdomain) 3
Figure 39. Routing subdomain organization example
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
74 / 448

8.1.2 Partitioning into separate Routing Domains
8.1.3 OSI over IP tunneling on QB3

This feature (not operative in current release) allows the Element Manager to reach the GNEs (and all the
relevant NEs behind them) by using IP networking.
This would permit to use an external DCN based on IP only. Hence, no OSI networking would be required
on the external DCN.
OSI over IP technique is used to meet the target. OSI packets leaving the SH are encapsulated into IP
packets within the SH system itself. Hence, packets leaving the SH are IP packets, containing the original
OSI packet.
Once the packet get the NE through a pure IP network, the GNE has to strip off the IP encapsulation, extracting the OSI packet, and to route the OSI packet as it does today using a pure OSI networking.
Hence, the internal networking of the SDH network (DCCs) is still based on OSI. No IP packets shall flow
inside DCCs, because the GNE receives the IP packet containing the OSI packet, deletes the IP header,
and forwards only the OSI packet on DCCs.
The default OSI lower layers networking can be replaced by IP routing capability at the bottom of the
QB3/QECC communication protocol suite; the choice is software switchable at NE level. The implementation adopts the RFC1006 standard to put the OSI upper layers on top of IP networking.
The application goal is to offer the TCP/IP transport (i.e. Internet compatibility) in alternative to the full ISO/
OSI communication protocols, in the complete DCN network or at least in a consistent portion of it.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 40. depicts the protocol architecture.
Figure 40. OSI over IP tunneling on QB3
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
75 / 448
To access select Comm/Routing option from the Configuration pull down menu as shown in the following figure.
The Communication and Routing menu allows to perform the following operations:
Local Configuration:
definition of the local NE addresses.
OS Configuration:
addressing of the main and spare OS connected to the local NE.
NTP Server Configuration:
addressing of the main and spare NTP servers connected to the

local NE.
Interfaces Configuration subdivided in:
LAPD Configuration:
definition of the LAPD port parameters for each LAPD channel

on the local NE.
Ethernet Configuration: definition of configuration parameters needed to manage a

local NE which provides a LAN ethernet interface.
OSI Routing Configuration subdivided in:
RAP Configuration:
configuration of parameters necessary to the addressing of NE

connected by Reachable Address Prefixes in a domain different
from the one of the local NE.
These information are stored in RAP table.
MESA Configuration:
configuration of parameters necessary to the addressing of non

ISIS NE in the same domain as the one of local NE.
These information are stored in MESA table.
IP Configuration subdivided in:
IP Static Routing Configuration: definition of Host/Network destination address for IP

static routing.
Tunneling Configuration subdivided in:
OSI Over IP:
definition of destination NSAP address and type of IP routing for

OSI over IP tunneling.
1AA 00014 0004 (9007) A4 ALICE 04.10
The options are described in next paragraphs.

All the previously cited operation can be entered choosing the relevant option of the menu, as shown in
Figure 41. on page 77.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
76 / 448

8.2 Communication and routing menu
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 41. Comm/Routing options
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
77 / 448

Select the Configuration pull down menu. Select the Comm/Routing option and then from the cascading
menu the Local Configuration option.
The dialogbox opens (see Figure 42. on page 79) and allows to configure the local address of the NE.
The following fields are present:
a Local Address section contains the following graphical object:
a Presentation Selector (P.Sel) identifies a presentation entity at the location identified by the
NSAP Address. The presented value must not be modified.
a Section Selector (S. Selector) identifies a section entity at the location identified by the NSAP
Address. The presented value must not be modified.
a Transport Selector (T. Sel) identifies a transport entity at the location identified by the NSAP
Address. The presented value must not be modified.
a Network Service Access Point (NSAP) Address identifies a location in the network. The first field
of the NSAP address, AFI, determines the NSAP format.
The AFI field is 2 characters long (2 exadecimal digits) and, depending on the its value, the
length of NSAP address is variable from 16 characters to 40 characters:
the value of AFI 49 identifies the local format of variable length (from 16 characters to 40
characters);
the value of AFI 39 identifies the ISODCC format up to 40 characters long;
the value of AFI 47 identifies the GOSIPV2 format up to 40 characters long.
In all cases the last two fields of the NSAP address are:
System Id: uniquely identifies a NE in an area and is 12 characters long;

It might be the equipment MAC Ethernet address, level 2, inserted in the NE (check the
value in the para. 8.7 on page 85) or it might be selected by the operator;
Network Selector: provides the distinction among users of the network service and is 2
fixed characters long (value is 1d).
In the view, the NSAP is managed as simple strings of characters without any preformatting
because of the variable format:
1AA 00014 0004 (9007) A4 ALICE 04.10
a first string of two characters that identifies the AFI field

a second string of variable length that identifies the remaining NSAP address
Synonymous Area Addresses section allows to have multiple synonymous area addresses within a
level 1 subdomain. The compilation of the two network addresses is optional and if they are inserted,
the last two fields, System Id and Network Selector, of the mandatory address and of the synonymous
addresses must be the same.
System Type section determines whether the local NE acts as a intermediate system level 1 or as
a intermediate system level 2 or as a End System. Note that a level 2 intermediate system performs functions of a level 1 too. End System is not operative.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
78 / 448

8.3 Local Configuration

Ok button is used to perform a configuration change of the data contained in the dialogbox and closes
it; the dialog is visible until the end of the operations and a wait cursor is displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 42. Local Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
79 / 448
menu the OS Configuration option.
The dialogbox opens (see Figure 43. ) and allows to configure the addresses of the Main and Spare OSs
connected to the local NE.
Main OS Address section contains the same graphical object of the Local Address Section in the Local Configuration dialogbox.
Spare OS Address section contains the same graphical object of the Local Address Section in the
Local Configuration dialogbox.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 43. OS Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
80 / 448

8.4 OS Configuration

8.5 NTP Server Configuration

menu the NTP Server Configuration option.
The dialogbox opens (see Figure 44. ) and allows to configure the addresses of the Main and Spare NTP
(Network Protocol synchronization Time) Servers connected to the local NE, used for time distribution in
the network.
Enabling NTP Protocol section allows to enable or disable the NTP Protocol.
Main NTP Server Address section contains the same graphical object of the Local Address Section
in the Local Configuration dialogbox.
Spare NTP Server Address section contains the same graphical object of the Local Address Section
in the Local Configuration dialogbox.
If the NTP server is coincident with the OS (same hardware), the same NSAP address of the OS must be
assigned.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 44. NTP Server Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
81 / 448
Select the Configuration pull down menu. Select the Comm/Routing>Interfaces Configuration option and then from the cascading menu the LAPD Configuration option.
The LAPD Configuration dialog opens (see Figure 45. on page 83, this example has one LAPD Interface
configured).
It contains the following functional block and graphical objects:
a section named LAPD Interfaces List that allows the user:
to display the list of configured LAPD Interfaces using a graphical table;

to change the role of the LAPD Interface selected in the LAPD Interface List;
to delete the LAPD Interface selected in the LAPD Interface List;
to create a new LAPD Interface.
This section contains the following graphical objects:
the number of LAPD interface displayed in the LAPD Interface List;

the LAPD Interface List that lists all the configured LAPD Interfaces; for each LAPD Interfaces,
the table displays:
the user label of the TTP containing the configured LAPD Interface (MS/RS TTP);
the LAPD role that contains one of the following value:
User
Network
Delete button that allows to delete the LAPD Interface selected in the LAPD table;
Change Role button that allows to change the role (User or Network) of the LAPD Interface
selected in the table (after selection the Figure 47. on page 84 is shown to confirm action required);
Create button that allows to create a new LAPD Interface; this button starts a new dialog (see
Figure 46. on page 84) named Create LAPD Interface; it is disabled when the maximum number of LAPD Interface has been configured.
This Create LAPD Interface dialog contains the following functional blocks and graphical
objects:
a section named Search Criteria that allows the user to display only the LAPDs of the selected type
in the LAPD Table; the section contains the following graphical objects:
the field Interface Type that allows to select the type of the LAPDs to be displayed in the LAPD
Table; the field will manage both ADM and WDM DCC type; the value Ignore will allow to display all the LAPD types;
the Search button starts the search of the selected LAPD type; this buttons can be used to refresh the LAPD table too.
1AA 00014 0004 (9007) A4 ALICE 04.10
a Choose button that allows the operator to select the superior TTP of the LAPD Interface
to be created; this button starts the TPSearch dialog; the TPSearch dialog will be configured in order to display in the right tree only the allowed TTP of the LAPD Interface;
a section LAPD Role that allows to configure the role (User or Network) of the LAPD Interface to be created.
This connection is a must to establish connection between two NEs: if one is configured
with User role, the other one connected must be configured with Network role.
The LAPD Interface List will be updated on reception of the Delete/Create/Change DCC CTP notification. If no LAPD Interface are configured in the equipment, the message No LAPD Interface will
be displayed near LAPD Interface counter (that it is at zero).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
82 / 448

8.6 LAPD Configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 45. LAPD Configuration dialog
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
83 / 448

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
Figure 46. Creation LAPD Interface
Figure 47. Confirmation to change LAPD Role
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
84 / 448

8.7 Ethernet Configuration

Select the Configuration pull down menu. Select the Comm/Routing>Interfaces Configuration option and then from the cascading menu the Ethernet Configuration option.
The dialogbox opens (Figure 49. on page 86) and allows to define the parameters needed to manage
a NE which provide a LAN ethernet interface.
The following fields and data are present:
Ethernet Interface field allows to define or remove a Local Area Network Port for the access to the
Data Communication Network.
MAC Address section allows to display the address of the Network Element in the Ethernet LAN;
it is a readonly field.
OSI Section:
L2 only Parameter field indicates if the port shall be used for level 2 traffic only, thus avoiding
transmitting L1 packets. Note that the flag shall be set to No if some other nodes (NEs or OSs)
of the same area of the relevant NE are connected to the Ethernet.
One example is indicated in Figure 48. on page 85.
L1 Default Metric is a not modificable field, Priority field can be set (default value for Ethernet
is 64).
L2 Default Metric is a not modificable field, Priority field can be set (default value for Ethernet
is 64).
IP Section allows to define the node IP Address, IP Mask and the Routing IP Protocol used.
If OSPF or Both options of Routing IP Protocol field are selected, also the Associated OSPF
Area must be set.
Apply button performs a configuration change of the data.

AREA 1
AREA 2
OS
LAN
1AA 00014 0004 (9007) A4 ALICE 04.10
L2
NE
No
L2
NE
No
L2
NE
Yes
AREA 3
Figure 48. Ethernet Configuration L2 only parameter
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
85 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 49. Ethernet Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
86 / 448

8.8 Reachable Address Prefixes Configuration

Select the Configuration pull down menu. Select the Comm/Routing>OSI Routing Configuration option and then from the cascading menu the RAP Configuration option.
The dialogbox opens (see Figure 50. ) and allows to configure the Reachable Address Prefix table.
Each element of the RAP table allows to link a LAPD port or a LAN port of the local NE to a separate domain; the separate domain is selected by the address Prefixes. If the addressed element is the OS, the
LAN port will be used.
The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing
device (upper part of the figure); each page represents a particular element of the RAP table and the respective pointing device displays the element counter.
In detail, each page contains the following data:
Physical Interface field:
if the element is empty, displays the none value and allows to select a LAPD ports or a LAN
port which will be used to reach the addressed area;
if the element isnt empty, displays the selected port and allows to change it.
Area Address Prefix section allows the user to address the separate domain. The Area Address Prefix represents a NSAP address without the fields System Id and Network Selector.
MAC Address section allows to address the element of a domain to be reached the Ethernet LAN;
the field is managed as a simple strings of 12 digit.
1AA 00014 0004 (9007) A4 ALICE 04.10
Apply button is used to perform a configuration change of the data contained in the complete RAP table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Figure 50. RAP Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
87 / 448
Select the Configuration pull down menu. Select the Comm/Routing>OSI Routing Configuration option and then from the cascading menu the MESA Configuration option.
The dialogbox opens (see Figure 51. ) and allows to configure the Manual ES Adjacencies table.
Each element of the MESA table allows to link a LAPD port or a LAN port of the local NE to a End System
element; the ES element must be in the same area as the one of the local NE. If the addressed element
is the OS, the LAN port will be used.
The view simulates a real notebook; it allows the user to select the pages of the notebook using the pointing
device (upper part of the figure); each page represents a particular element of the MESA table and the
respective pointing device displays the element counter.
In detail, each page contains the following data:
Physical Interface field:
if the element is empty, displays the none value and allows to select a LAPD ports or a LAN
port which will be used to reach the End System element;
if the element isnt empty, displays the selected port and allows to change it.
System Id section represents the System Id of the ES element.
MAC Address section allows to address the element in the Ethernet LAN; the field is managed as
a simple strings of 12 digit.
1AA 00014 0004 (9007) A4 ALICE 04.10
Apply button is used to perform a configuration change of the data contained in the complete MESA table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
Figure 51. MESA Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
88 / 448

8.9 Manual ES Adjacencies table Configuration

8.10 IP Configuration
Select the Configuration pull down menu. Select the Comm/Routing Configuration >IP Configuration option and then from the cascading menu the IP Static Routing Configuration option.
The dialogbox opens (see Figure 52. ) and allows to configure the IP Static Routing table.
The following fields and data are present:
[1]
Destination Host IP Address: allows to define the IP address necessary to reach a specific Host.
[2]
Destination Network:
[3]
Default Gateway IP Address: allows to define the address of the next hop gateway.
[4]
CLNP (Connection Less Network Protocol): allows to use a predefine IP over OSI tunnel towards
a gateway.
[5]
IP PointtoPoint Interface Id: allows to use point to point interfaces made available by EC.
it is alternative to Destination Host IP Address; allows to define the

IP Address and IP Mask to reach a network.
NOTE: points from [3] to [5] are alternative.
1AA 00014 0004 (9007) A4 ALICE 04.10
Apply button is used to perform a configuration change of the data contained in the complete IP Static
Routing table and close the view; the view is visible until the end of the operations and a wait cursor is
displayed.
Figure 52. IP Static Routing configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
89 / 448
Select the Configuration pull down menu. Select the Comm/Routing Configuration >Tunneling Configuration option and then from the cascading menu the OSI Over IP option.
The dialogbox opens (see Figure 53. ) and allows to configure the OSI Over IP table, where is necessary
insert a Remote Destination IP Address in the relevant fields.
Apply button is used to perform a configuration change of the data contained in the complete OSI Over
IP table and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 53. OSI Over IP Tunneling configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
90 / 448

8.11 Tunneling Configuration

9 EQUIPMENT MANAGEMENT
9.1 Introduction and navigation
This section deals mainly with the setting and changing of the boards present on the Equipment and
undertaking board protection operations.
Using the menu options, select the Equipment option from the Views pull down menu.
The first level of the Equipment Overview representation will be displayed directly into the current
window.
The Equipment Overview enables a fast navigation through all levels of the equipment hierarchy.
Navigation is done from higher to lower levels.
The NE hierarchy is organized in the following way: rack > subrack > board > port > TP
The navigation through different levels of the NE hierarchy is performed by double clicking on the objects:
the first level shows the rack level of the Equipment view (see Figure 54. on page 92).
in the rack level two subracks are presented (plus two Fans Subrack, named SRFAN and placed
under each of them):
at the top the 1670SM AEP (Access Extension Panel / Shelf), named SR70AEP;
at the bottom the 1670SM MS (Main Shelf), named SR70M.
This NE will be present and then managed only when configured by the operator.
On the contrary a black square will be shown on the same position.
The subrack presence is managed with the Set option as for the boards of the subracks
(see para. 9.2.1 on page 98).
double clicking on it the subrack level of the Equipment view is reached (see Figure 55. on page
93 for SR70M, Figure 56. on page 94 for SR70AEP and Figure 57. on page 95 for SRFAN);
further, by double clicking on a board body, the board level of the Equipment view can be
reached (as described in chapter 10 on page 115);
further, by double clicking on a port body contained in the board, the port level of the Equipment
view can be reached (as described in chapter 11 on page 121); the port view displays the inner
TPs;
it is possible to go back to the upper level of representation by pressing the <ESC> key on the
keyboard; it is also possible to:
go back to the previous view, by selecting the Backward option from the Views menu;
go to the next view, by selecting the Forward option from the Views menu.
NOTE: Selecting in the first level of the Equipment view (rack level, Figure 54. on page 92) the Show
supporting equipment option from the Equipment menu, the Equipment level view of Figure 58. on
page 96 is presented.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following figures are some examples of equipment management.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
91 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 54. Equipment Overview Rack level
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
92 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 55. Equipment Overview Subrack level (1670SM_MS)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
93 / 448

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 56. Equipment Overview Subrack level (1670SMAEP)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
94 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 57. Equipment Overview Fans Subrack
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
95 / 448

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 58. Equipment Overview Equipment level
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
96 / 448

In the Subrack view it is possible use the options offered by the Equipment menu (see Figure 59. ) clicking
on it in the menu bar.
Alarms indications are present at every NE level.
Details about these alarms indications are given in the Maintenance section of this Handbook.
All the options offered by equipment menu are described in the next paragraphs.
Set and change the boards present on the Equipment is the main function.
Board administrative state that decide on the in/out of service of the board is also described.
Figure 59. Equipment menu
Equipment setting operation are defined according the following sequences:
configuration of a new board:
configure the board using the option Set
change of board type:
Set out of service the board

reconfigure the board using the option Set
remove a board:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Set out of service the board

remove the board using the option Remove
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
97 / 448
9.2.1 1670SM subrack management

A 1670SM can be used in conjunction with a 1670SMAEP subrack (1 to 3 subracks).
In this case the 1670SM will report the alarm condition of the 1670SMAEP towards the CT.
To be able to manage the 1670SM equipment execute the following operation:
Click on the 1670SM black square in the rack view. The outline of the NE becomes highlighted. This
indicates that the NE is selected.
Select the Set option of the Equipment pull down menu.
The dialogue box presented in Figure 60. on page 98 and in Figure 61. on page 99 containing 1670SM
subrack selection is displayed, where:
1AA 00014 0004 (9007) A4 ALICE 04.10
SR70M is a 1670SM Main Shelf

SR70AEP is a 1670SM Access Extension Panel (fully equipped)
SR70AEPUE is a 1670SM Access Extension Panel (under equipped)
SRFAN is a Fans Subrack
Figure 60. 1670SM subrack setting
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
98 / 448

9.2 Set and change, remove and modify subrack/board

Figure 61. Fans Subrack setting
Follow the same rules given to set the boards. They are valid also to delete the 1670SMAEP subrack.
1AA 00014 0004 (9007) A4 ALICE 04.10
To manage the 1670SM subracks proceed according the setting indication of the board as for para. 9.2.2
on page 100.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
99 / 448
The boards (access cards and port cards) can be set, changed, modify or removed using the menu options
of the Equipment view.
a)
Setting or changing a board
A new board may be created in either an empty slot or it may replace an existing Out of Service board
(without the lock symbol). In fact, the Set option is available only after selecting an empty slot or an
Outofservice board.
Click on the empty slot in which a board has to be added, or on an existing Out of Service board in
order to change it (see para. 9.3 on page 106 for in /out of service info). The contour becomes
highlighted to show that operations can be done on it.
Select the the Set option of the Equipment pull down menu of Figure 59. on page 97.
The following examples of dialogue box containing a list of the different types of boards and access
cards are displayed (Figure 62. on page 100 for Access Cards, Boosters and Preamplifier for
SR70M, Figure 63. on page 101 for Access Cards for SR70AEP and Figure 65. on page 102 for
Traffic Port cards).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 62. List of different access cards, booster for SR70M
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
100 / 448

9.2.2 Board management
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 63. List of access cards for SR70AEP
Figure 64. List of modules (drawers) for boards
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
101 / 448


Figure 65. List of different traffic ports
NOTES BEFORE BOARD CONFIGURATION
1AA 00014 0004 (9007) A4 ALICE 04.10
For details on the board identified by acronyms and NE physical composition please refer to the Technical
Handbook.
1.
In the 1670SM equipment is also present a bus termination unit (BTERM).

This unit is not configurable by CT, but it is important to check its presence into the subrack,
because its absence or an its fault displays RUM alarm on both HCMATRIX units.
2.
When the P16S1N configuration is required the operator may have to wait for about five
minutes up the unit will be operative; in this phase a GA will being downloaded: hence it is
important not to extract the unit.
3.
Is mandatory to configure the HCLINK spare after the configuration of the relevant HCLINK main.
When is equippped a HCLINK spare is automatically provisioned the MSP protection of the link
between the NEs.
4.
In case of P16OS1 + A12OS1 configuration, the following steps have to be met:

A)
in the subrack always firstly insert the P16OS1 board and then the relative A12OS1 board
because the latter is power fed by P16OS1;
B)
perform the boards configuration operations from the CT for both the boards and the STM1
modules as for all the similar boards.
If the sequence indicated at point A) is not met, fictitions alarms can be cleared by removing and
inserting again the A12OS1 board.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
102 / 448

When is selected a coloured unit (see for example following figure) it is also necessary to set the
Channel Number and the Grid parameters.
These parameters are mandatory for PR64 and L642CF units.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 66. L642CF port setting
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
103 / 448
When is selected a slot in the Link Area of a Main Shelf is shown the Figure 67. on page 104.

These units are reserved for Multishelf Configuration (more NEs).
Figure 67. List of link units
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE: The list of boards displayed during a Set Board operation is restricted to those which the
equipment may accept in the selected slot. Therefore the list will vary depending on which slot has been
selected.
Choose the board type required, by clicking on the corresponding item in the list. The name of the
board is highlighted. Click on the OK button to validate the choice.
The board representation appears on the NE view in the selected slot when the board set is effective.
A lock representation appears over the boards (inservice, see para. 9.3 on page 106).
In the Create/Modify dialogue box, the Cancel button cancels the operation and closes the dialogue
box.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
104 / 448

b)
Removing a board
Click on the board to remove (Out of Service board, as for next para. 9.3 on page 106).
The outline of the slot becomes highlighted. This indicates that the board is selected and that
operations can be done on the slot.
If the slot you are working on is already empty no name appears under the slot.
Select the Remove option of the Equipment pull down menu of Figure 59. on page 97.
From the confirmation dialogue box that opens you can confirm or cancel the Remove Board operation.
Note: it is possible to remove a board only if it is not involved in any type of cross connection (OH bytes
included) or Performance monitoring.
c)
Modifying a board
Note: This procedure can be done to replace an existing board with another of different type. The Modify
option isnt possible with other board types.
Click on the board to replace. The outline of the slot becomes highlighted to show that operation can
be done on it.
Select the Modify option of the Equipment pull down menu of Figure 59. on page 97 .
A dialog box containing a list of different types of board is displayed.
Chose the board type required by clicking on the corresponding item in the list; the name of the
module is highlighted.
Click on OK button to validate the choice.
The board representation appears on the NE view in the slot when the board change is effective. A
padlock representation appears over the board.
9.2.2.1 VOA configuration
1AA 00014 0004 (9007) A4 ALICE 04.10
To configure the VOA parameters (for example to set the attenuation of the variable optical attenuator)
the sequence is following:
ED
configure VOA board selecting from the Equipment menu the option Set as shown in the
example of Figure 62. on page 100, after selecting the correct position of VOA into the Access
Area (see also Technical Handbook);
select the slot where you have configurated VOA board and then select the VOA configuration
option from the Equipment menu;
it will appear a window where it is possible to configure the VOA parameters (the attenuation
step values are between 1 dB to 11 dB on step 0.5 dB);
click OK to confirm or Cancel to close provisioning.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
105 / 448
9.3 Board administrative state
Note:
in the equipment view, a lock representation

service state.
appears over the boards which are in in
9.3.1 Setting a board in service
In the Subrack view, click on the board in order to select it.

Select the Set in service option of the Equipment pull down menu of Figure 59. on page 97.
A lock representation appears over the boards.
9.3.2 Setting a board out of service
In the Subrack view, click on the board in order to select it.

Select the Set out of service option of the Equipment pull down menu of Figure 59. on page 97.
Select the Ok button in the confirmation window which appears.
A lock representation disappears, substituted by the symbol
over the boards.
9.3.3 Consulting a Boards Administrative state

The boards administrative (in service or out of service) state is indicated on the board view as shown
in the following figures.
Administrative
1AA 00014 0004 (9007) A4 ALICE 04.10
State Information
Figure 68. Consulting a boards administrative state (example1)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
106 / 448

The operator decides to set a board in service or out of service, if it is allowed by the NE.
1AA 00014 0004 (9007) A4 ALICE 04.10
Administrative
State Information
Figure 69. Consulting a boards administrative state (example2)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
107 / 448

This option gives to the operator the possibility to describe the way in which the main subrack (1670SM)
is connected to the boosters and/or preamplifiers. In the following paragraphs will be described the way
to activate the cable list configuration view and the meaning of the displayed information.
To manage the connection execute the following operation:
Click on the 1670SM in the rack view. The outline of the NE becomes highlighted. This indicates that
the NE is selected.
Select the Cable configuration option of the Equipment pull down menu.
Next figure shows these selections.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 70. Cable configuration option selection
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
108 / 448

9.4 Cable configuration

After the selection the following figure is displayed.
Figure 71. Cable configuration view

From a logical point of view, the window is divided in 3 parts:
The upper field displays the configurations provisioned.
The lower field (Add/Modify/Delete Element) is divided in 3 parts:
the left part is related to a schematic representation of the optical port that could be equipped
in the 1670SM;
the central part is related to preamplifiers;
the right part is related to boosters.
The bottom is related to the Ok, Cancel, and Help buttons.
Two arrows are placed near Preamplifier and Boosters text. The right arrow (>) is representing the output
fiber, while the left arrow (<) is representing the input fiber.
1AA 00014 0004 (9007) A4 ALICE 04.10
The combo box summarize the following possibilities:
The optical port output fiber could be connected directly to line.
The optical port output fiber could be connected to a booster placed in a slot in the 1670SM subrack;
in this case the box will show a label referred to the Booster type and the physical slot in which the
board is inserted.
Of course it is not possible to have two boxes showing the same slot number.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
109 / 448
Then the operator can choose to connect an aggregate output to a booster and/or to connect an optical
port input to a preamplifier output. Both operations can be performed selecting the appropriate items from
the correspondent box.
Its operator responsibility check that the selected booster/preamplifier is really equipped and correctly
inserted into its slot in the 1670SM subrack. It is also operator responsibility verify that the selected cable
list configuration is coherent with the actual equipped board or with the boards she/he wants to equip.
It is software responsibility to show correct and congruent information in the boxes the operator can
activate.
At the end of the cable list configuration, send it to the NE pushing the Ok button and confirming the
operation to the standard message box that will appear.
After this close the cable list configuration window pushing the Cancel button.
To cancel the cable list configuration, push the Cancel button in the cable list configuration window. In this
case the window will be closed automatically.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 72. Cable configuration view (after add action)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
110 / 448

Every time the operator wants to set up the cable list the most updated information are shown.

9.5 Software description

This function allows the operator to visualize information about the software(s) which is(are) present in the
selected board.
Click on a board in which the software is wanted to known (all the boards except Converter and Switch
unit, which dont contain software). The outline of the slot becomes highlighted. This indicates that
the board is selected and that operations can be done on the slot.
Select the Software description option of the Equipment pull down menu of Figure 59. on page
97.
The following window opens.
Figure 73. Software Description dialogue box

The dialogue box contains as many folder sheets as there are softwares in the selected board.
Click on the Close push button to close the dialogue box.
1AA 00014 0004 (9007) A4 ALICE 04.10
If the selected board does not contain any software, the following information will be displayed:
Figure 74. No Sw indication
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
111 / 448
9.6 Remote Inventory

This command displays the remote inventory data present in the Subrack and Boards.
Select a board and then the Remote Inventory option of the Equipment pull down menu.
Two options are available (see the following figure):
Subrack level: prints or write on a file the remote inventory data of the subrack
Board level: show the remote inventory data of the selected board
Figure 75. Remote Inventory
1AA 00014 0004 (9007) A4 ALICE 04.10
For the Board level a dialog similar to Figure 76. appears.
Figure 76. Remote Inventory
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
112 / 448

The remote inventory data of the Subrack level can be printed on the default printer (see Figure 77. ) or
to a file in postscript or ASCII format (see Figure 78. ).
Figure 77. Select Printer
1AA 00014 0004 (9007) A4 ALICE 04.10
Note: If no printer is installed, there is no error message displayed to indicate this.
Figure 78. Select Output Format for file
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
113 / 448
Click on Show Supporting Equipment menu option of the Equipment menu to navigate to the
equipment that supports the selected board (1670SMMS or 1670SMAEP).
Figure 79. (it is an example) opens.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 79. Equipment Overview
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
114 / 448

9.7 Show supporting equipment

10 BOARD VIEW
10.1 Introduction
The Board View permits to show the physical port available in a specific board and to access the Port
view.
The Board view is reached selecting the Equipment option in the Views pull down menu, then double
clicking on the presented rack/subrack to present the subrack view, as described at chapter 9 on page 91.
Double click on the selected board to show the relevant Board view, presenting the contained ports.
In case of board with multi access SDH another view permits to select the SDH port.
An example of board view with the presented port is in following Figure 80.
Alarms and Status indications referred to the board level are present at the bottom of the view, as indicated
in the example (Administrative State and Board Alarms/Status).
This information are In/Out of service of the board (Administrative State) and board alarms and status
like missing (RUM) or mismatch (RUTM), EPS condition if supported and other indications typical of
each unit (i.e. high laser temperature HLT).
In the Maintenance Section of this Handbook details on this indication are given.
Administrative state
1AA 00014 0004 (9007) A4 ALICE 04.10
Board Alarms/Status
Figure 80. Example of a Board View
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
115 / 448
The port identification is usually internal to the rectangular board (see in Figure 81. some examples of
optical ports and booster).
Figure 81. Examples of a Port identification and alarm synthesis

The following information is available:
type of port (name)

state of port (alarm status synthesis)
symbol of the port
The operator is provided with a representation of the port alarm synthesis on each port.
The messages displayed at the top view provide port denomination.
The messages displayed at the bottom provide information about Board alarms.
A message under the mouse facility provides the name and the port type or the alarms name. A message
appears in the message area in the bottom left corner of the view.
1AA 00014 0004 (9007) A4 ALICE 04.10
By double clicking on a board view, it is also possible open the corresponding port view (see chapter 11
on page 121).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
116 / 448

A port type is described with a board rectangular view and a port identification.

10.2 Board View Menu

Selecting the Board option in the menu bar of Figure 80. on page 115 the complete pull down Board menu
is presented:
Port Access:
Access the Port view. See para.10.2.1 on page 118 .

Note: this option is accessible after the selection of a port contained
in the view.
Change Physical Interface: Change the SPI or PPI object into PPI or SPI (and viceversa) on the
bimode port (140Mbit/s / STM1 switchable).
Show supporting equipment:
ATM/IP/ETH Configuration: It allows to configure the TPs for the ATM/IP/ETH connections.
Note: this is available only if an ETH board has been equipped
in the Subrack.
Navigate to the upper subrack level.

See para.10.2.3 on page 120.
Figure 82. Board menu options
1AA 00014 0004 (9007) A4 ALICE 04.10
These options are described in next paragraphs.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
117 / 448
Click on Port Access menu option of the Board menu to access the Port View (see chapter 11 on page
121).
Navigation to the Port view permits to show a detailed alarm presentation of the port and to set the relevant
configurations as for the example of the following figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
Note: on the ETH port the TPs are not automatically created (except for MAU TP) when the board is
equipped in the subrack but they must be created with the aid of the Configuration >ATM/IP/ETH
Configuration (refer to chapter 20 on page 435).
Figure 83. After Port Access selection (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
118 / 448

10.2.1 Port Access

10.2.2 Change Physical Interface

This command allows to change the type of physical interface in a bimode port (140 Mbit/s / 155 Mbit/s
switchable port) i.e. it changes the SPI or PPI object into PPI or SPI.
Select the symbol of the port in the Board view.
Click on Change Physical Interface menu option of the Board menu (see Figure 84. ).
Figure 84. Change Physical Interface
The following dialog box is opened:
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 85. Change Physical Interface confirm

Click on the OK button to change the physical interface.
Click on the Cancel button to abort the change of the physical interface.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
119 / 448
Click on Show Supporting Equipment menu option of the Board menu to navigate to the subrack that
supports the selected port view (1670SMMS or 1670SMAEP).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
120 / 448

10.2.3 Show Supporting equipment

11 PORT VIEW
11.1 Introduction
This section describes the operations necessary for the consultation, modification and configuration of
each port.
The Port View permits to set and show the transmission resources (i.e. the Termination Point, TP) referred
to the specific Port: it permits to check the detailed alarms presented by each TP of the Port, and the
available menu permits to configure the port (many setting options listed in the port menu are common
with the Transmission view).
In these views are presented only the TP specific of the port.
The menu differs according the port type (SDH, PDH and ETH).
The Port View can be accessed from the Equipment or Transmission Views.
The Port view is reached selecting the Equipment option in the Views pull down menu, then double
clicking on the presented rack/subrack to present the subrack view, as described at chapter 9 on page 91.
Double clicking on the selected board the relevant Board view is available presenting the ports (see
chapter 10 on page 115).
By double clicking on a board view, the corresponding port view is opened (see Figure 86. on page122).
The Port view is also reached selecting the Transmission option in the Views pull down menu.
Then the Add TP option of the Transmission menu permits to select and confirm a TP (see the description
at para. 14.5 on page 185).
On the transmission view which appears select the TP and on the Transmission menu select the
Navigate to a port view option.
The HOA port view can be reached from the Port view, selecting a TP and then Port> Navigate to HOA
port View option.
From the Port view it is possible to Navigate to Transmission view.
The port types contain the following TP:
SDH port: Electrical or Optical SPI TTP, RST TTP, MST TTP, prot TTP (MSP TTP), AU4 CTP,
Trail Monitor (only with enabled POM)
SONET port: Electrical or Optical SPI TTP, RST TTP, MST TTP, prot TTP (MSP), AU3P
PDH port: PPI TTP, En CTP, VCn TTP
ETH port: MAU TTP, VC4XV TTP, VC4PTC TTP
On the port view, the messages displayed at the top view in the form of message boxes provide more
information concerning the type and the alarms of the port.
1AA 00014 0004 (9007) A4 ALICE 04.10
On the other hand the messages displayed at the bottom provide information about MSP protection and
ALS state (if they are supported).
A message under the mouse facility provides the name and the port type. A message appears in the
message area in the bottom left corner of the view.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
121 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SDH
port
ETH
port
Figure 86. Examples of a Port View
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
122 / 448
11.2 Port View: elements on the TP

The symbols of the TPs (see Figure 87. ) have the following meaning:
Alarm Icon Area

The icon boxes represent alarms. The color of the boxes changes according to the alarm severity.
TP Role
The icon boxes represent the function: Adaptation, Termination or Compound Adaptation and
Termination.
Cross-connected state
If the condition of the resource is cross-connected, an icon with a X appears beneath the box.
Performance state
If the condition of the resource is under performance monitoring, an icon with a P appears beneath
the box.
Loop state
If the condition of the resource is under loop, an icon with a L appears beneath the box.
Selected state
An orange frame around the box identifies the TP selection, so port menu refers to the selected TP.
Alarm icon area
G.783 TP Role
(Termination)
TP identifier
Selection indication
Crossconnected state
TP under Performance monitoring
Alarm icon area

G.783 TP Role (Adaptation)
1AA 00014 0004 (9007) A4 ALICE 04.10
G.783 Functional block acronym
Figure 87. Examples of G.783 Adaptation and Termination TP box
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
123 / 448
Selecting the Port option in the menu bar of Figure 86. on page 122 the complete pull down Port menu
is presented (see Figure 88. ).
The menu differs according the port type (SDH, PDH and ETH) and is introduced in the following:
TP configuration:
TP Threshold Configuration: Set B2 excessive BER and Signal Degraded parameter.

AU4 Concatenation:
1AA 00014 0004 (9007) A4 ALICE 04.10
Set parameters for the Signal Label and Path Trace overhead on
Synchronous TPs.
Cross Connection:

Monitoring Operations:
Set parameters for POM/SUT/TC TPs. Not available for PDH port.
See para.14.9 on page 198.
Performance:

Loopback:
Manage the loopback commands for commissioning or maintenance

purposes.
MSP:

See para. 13.4 on page 167
Physical Media:
Manage the physical setting of the TP of the port.

Show Supporting Board:

Navigate to Transmission View: permit to show a complete overview about the signal flow,
opening all TPs.
See para.11.7 on page 141.
Navigate to Monitoring View:
permit to show an overview about the Monitoring Operations

(POM, SUT, TC) all TPs.
Navigate to HOA port View:
permit to display the internal structure of the payload.

ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
124 / 448

11.3 Port View Menu
1AA 00014 0004 (9007) A4 ALICE 04.10

SDH port
PDH port
ETH port
Figure 88. Port menu options (SDH, PDH and ETH)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
125 / 448
Select a STM64 or STM16 or STM4 optical interface to configure as AU4 concatenation structure.
Zoom in to open the board and then the port view menu.
Select the AU4 Concatenation option from the Port menu to open Figure 89. (this is an example).
The STMN stream appears divided into different groups: not all AU4s can be chosen as first AU4 but if
it is selected a STM64 (for example):
only AU4#1, AU4#5, AU4#9, AU4#13, AU4#17 ............ AU4#57, AU4#61 for AU44c
only AU4#1, AU4#17, AU4#33 and AU4#49 for AU416c
only AU4#1 for AU464c
Therefore, for example, for concatenated action of four AU4s in one AU4c these AU4 streams are deleted
and substituted by the new AU4c component.
Select the supported concatenation Number =4 (selection 16 refers to the concatenation of sixteen AU4
in one AU416c, selection 64 refers to the concatenation of sixtyfour AU4 in one AU464c) to visualize
the available group/groups then select the group to concatenate and click on the Concatenate button.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on the Cancel button to exit and come back to the previous window.
Figure 89. AU4 concatenate/deconcatenate commands
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
126 / 448

11.4 AU4 Concatenation

The Concatenate button will be enabled and the Deconcatenate button will be disabled when is selected
a non concatenated AU4, viceversa when is selected a concatenated AU4.
The port view represented in Figure 90. on page 127 shows an STM64 interface with four AU4
concatenated in one AU44c (AU4#29 is the first of four involved). The AU44c appears as a single icon
that has a bigger size than a AU4 blocks. The AU44c streams support the Alarm synthesis,
CrossConnection states and Performance Monitoring information as standard AU4 streams.
In the example is also shown an AU416c concatenation with sixteen AU4 concatenated in one AU416c
(AU4#33 is the first of sixteen involved).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 90. Example of a concatenated AU4 transmission view
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
127 / 448

To deconcatenate an AU44c select again the AU4 Concatenation option in the Port View menu and then
select the AU44c or AU416c to deconcatenate (see Figure 91. ).
Click on the Deconcatenate button to apply the command or on Cancel to exit.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 91. Example of a concatenated AU416c
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
128 / 448

11.5 Physical Media options menu

The Port > Physical Media options permit to set physical configuration of each TP of the port.
The Physical Media options are also accessible from the Transmission menu.
It opens a menu which differs according to the port type:
For SDH port:
ALS Management
Show Optical Configuration
TX Quality Configuration:
Single Fiber Configuration
LAPD Configuration:
MS Configuration
see para. 18.2.10 on page 330

see para. 8.6 on page 82
For Ethernet port:
Remote Laser Management

ALS Management
Ethernet Port Configuration
Ethernet Mapping Protocol
ATM/IP/ETH Configuration:
Control Path Activation
(not operative)
(not operative)
refer to chapter 20 on page 435
These options are described in next paragraphs except the previously referenced.
SDH port
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 92. Physical Media menu (SDH port example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
129 / 448
11.5.1 Automatic Laser Shutdown management
Automatic laser shutdown (ALS) is useful in case of a loss of communication between two NEs due to
optical fiber breakdown. For safety reasons it may be necessary to shutdown the laser to enable the fixing
of the communication link.
The automatic laser shutdown function can only be configured from the optical ports of the equipment.
Select the SPI block (for SDH port) or MAU block (for ETH port) in the port view and then select the Port
pull down menu.
Select the Physical media option and then from the cascading menu the Als Management option.
The Automatic Laser Shutdown State dialogue box opens (Figure 93. on page 130). From this window
it is only possible to create the ALS function (all the ALS commands are greyed).
Select the Apply button and open again the Als Management option to configure the ALS and Restart
parameters.
Figure 94. on page 131 opens.
SDH port
1AA 00014 0004 (9007) A4 ALICE 04.10
ETH port
Figure 93. Automatic Laser Shutdown Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
130 / 448

The aim of this paragraph is to describe the optical port hence the laser sources.

Figure 94. Automatic Laser Shutdown Management

The dialogue box enables the ALS Management and the Restart parameters. The following actions are
available:
a)
Allow Automatic Laser Shutdown

To allow the automatic laser shutdown functionality, select the ALS Enabled option of the ALS
Function option button.
b)
Forcing the Laser to start or stop

When the laser is forced to ON or OFF, it is restarted or stopped and the Automatic Laser Shutdown
is disabled, if it was not already so.
1AA 00014 0004 (9007) A4 ALICE 04.10
c)
ED
1)
Force laser ON
To carry out a laser forced ON, select the Laser Forced ON option of the ALS Function then
click on Apply and then or Close push button to close the dialogue.
2)
Force laser OFF

To carry out a laser forced OFF, select the Laser Forced OFF option of the ALS Function then
click on Apply and then or Close push button to close the dialogue.
Delete : this option deactivates the ALS function, returning to the state shown in Figure 95. on page
132.
From this window it is only possible to create the ALS function (all the ALS commands are greyed).
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
131 / 448

Figure 95. Automatic Laser Shutdown Management (after ALS Function delete)
d)
Enabling or Disabling Automatic / Manual Laser Restart

To enable (disable) an automatic laser restart following an automatic laser shutdown (periodic
restart), select the Enabled (Disabled) option of the ALS Auto Restart. The laser will be ON for 2
secs and OFF for 70 secs, in periodic mode. The same procedure is applicable for the ALS Manual
restart : while the ALS auto Restart is disabled,the manual restart permits to perform a laser restart
for a single time period.
e)
Wait to restart time

The Wait To Restart Time: field indicating the delay period in seconds, occurring before an
automatic laser restart is launched (following an automatic shutdown). The restart time period for
this equipment is fixed to 70 secs.
f)
Als Manual restart (not operative, from Craft Terminal, in current release)
When the Als Manual Restart is Enable it is possible to enter two different commands: Manual or
Test Restart. The manual command immediately activates a single laser restart: this command
overrides the wait to restart time. The test restart is similar to the manual restart but the laser remains
ON for a longer time in order to make a measurement of the received optical power.
1AA 00014 0004 (9007) A4 ALICE 04.10
When all the different parameters have been configured, select the Apply button to confirm the setting
and Close the dialogue box.
Selecting only the Close button allows you to cancel the choices made.
Note that the ALS procedure is activated (if enable) only when the fiber has been interrupted and the ALS
state has not to be confused with the laser state.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
132 / 448

ALS states and Laser state (see example of Figure 96. ), displayed by the functional state message area
of the optical port, are:
ALS states:
Inactive
In test
Active
Undefined
No ALS has been activated (Off)

The laser has been Forced ON/OFF or the laser restart key has been pressed at least
for 12 seconds
The ALS has been activated (On)
TheALS is not present (not created)
Laser state:
On
Off
Forced on
Forced off
all OK or ALS not present (not created)

Laser off (when ALS is created)
ALS forced on by operator command
ALS forced off by operator command
normal condition
after Tx or Rx failure
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 96. ALS and Lasercurrent state (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
133 / 448
This command permits to get detailed information on the optical characteristics of the port that is
visualized.
Firstly select an optical board and the SPI block, then click on Show Optical Configuration option from
the Physical media pull down menu to visualize the parameters of the selected optical port.
Figure 97. shows an example of the parameters of the selected interface.
NOTE: this dialogue box can only be read.
Figure 97. Visualizing a port optical parameters
1AA 00014 0004 (9007) A4 ALICE 04.10
The laser ports are identified by these major characteristics:
STM Level: describes the input/output optical interface types: STM1 / STM4 / STM16 / STM64
The wavelength of the laser source: the units are nanometers (nm = 109 m).
The use of the port (Optical Reach): describes whether the laser port is used for intraoffice
transmissions on long distances (Long Haul 40 km) or for infraoffice transmissions on short
distances (Short Haul 15 km).
For Colored Optical port is added others information: Channel, Grid and FEC.
To close the dialogue box click on the Close button.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
134 / 448

11.5.2 Show Optical Configuration
11.5.3 Single Fiber Configuration

The single fiber configuration can be realized with passive optical couplers (see Figure 98. ).
The optical coupler must not loop the Tx signal onto the local Rx.
For this purpose and in general to avoid a low Tx/Rx decoupling also when the optical line is interrupted,
an identification label has been assigned to the local Tx side; the Rx part in the remote receive side checks
the congruency between the received and the expected labels. If a signal label mismatch is recognized
on the received section, an alarm (AIS and RDI) will be generated.
Example of Figure 98. shows that is accepted the label 1 from Tx1 to Rx2 while is accepted label 2
from Tx2 to Rx1.
Tx1 Label : 1
Tx2 Label : 2
Tx1
Tx2
Single bidir
OPTICAL
PASSIVE
COUPLER
Rx1
OPTICAL
PASSIVE
COUPLER
Rx2
Rx1: accepted label=2
Rx2: accepted label=1
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 98. Bidirectional Transmission on a single fiber
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
135 / 448
Select the Physical media option and then from the cascading menu the Single Fiber Configuration
option.
Figure 99. on page 136 opens. The following fields have to be considered:
Allow Single Fiber: select the transmit mode on the single fiber (enable or disable).
Transmitted Section:
Transmitted Media Byte assigned label to Tx (014)
Transmitted Media Type overhead byte used for the communication:
Media Dependent byte of Regeneration Section

or
S1 byte of Multiplex Section (the part not used for the SSM)
Received Section:
Received label
Expected label (014)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 99. Single Fiber Configuration View
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
136 / 448

Select the RST block.

11.5.4 MS Configuration
The Ms Configuration menu allows the SS bit provisioning for Multiplex Section Object (MSTTP) in
SONET/SDH network interworking.
Select the MSP block.
Click on Ms Configuration menu option of the Port menu.
Figure 100. opens.
This dialog allows to select between SDH or SONET networks. After the selection click on Apply and then
on Close to close the dialog.
Ms Forced AIS is not supported in the current release.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 100. MS Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
137 / 448
11.5.5 Ethernet Port Configuration

11.5.6 Ethernet Mapping Protocol

It is used for Gigabith Ethernet Rate Adaptive board (GBETH) only.
Select a VC TP.
Click on PortEthernet Mapping Protocol option of the Port> Physical Media menu.
Figure 101. opens.
Figure 101. Ethernet Mapping Protocol (example)

This dialog aims to show the actual Ethernet mapping protocol used and allowing the user to change it.
In Figure 101. is depicted an example.
1AA 00014 0004 (9007) A4 ALICE 04.10
The options available for GIGABIT ETHERNET boards are the following:
ED
GFP null extension Header with FCS
GFP null extension Header without FCS
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
138 / 448
11.5.7 Control Path Activation

It is used for Gigabith Ethernet Rate Adaptive board (GBETH) only.

This dialog allows to modify the state of the Ethernet port virtual TPs, created as explained in chapter 20
on page 435.
Select a TP in the Ethernet port view window.
Click on Control Path Activation option of the Port> Physical Media menu.
A new window will be opened (Figure 102. is an example); a similar window is display when a new
concatenated VCX is created in the ATM/IP/ETH configuration window (refer to para. 20.2.1 on page
435).
This dialog aims to show the activation state of the virtual TPs present in the Ethernet Port View and to
change the number of virtualTPs active.
The Active state is reached by choosing the number of Virtual TPs to be active and click on the Apply
button.
Figure 102. Control Psth Activation (example)
1AA 00014 0004 (9007) A4 ALICE 04.10
On the contrary to change in Idle the Active state of a TP decrease the Virtual TPs to be active field and
then and click on the Apply button.
Click on the Refresh button to uptade the changes.
Click on Close button to close the Control Path Activation window.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
139 / 448
11.6 Show Supporting Board
Click on Show Supporting Board menu option of the Port menu to navigate to the board that supports
the selected port view.
Figure 103. (example) opens.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 103. Board View example
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
140 / 448

Select a TP.
11.7 Navigate to Transmission View

Select a TP.
Click on Navigate to Transmission View menu option of the Port menu to navigate to the corresponding
Transmission View that is related to the selected TP.
Navigation to the Transmission view permits to show a complete overview about the signal flow as for the
example of the following figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 104. After Navigate to Transmission view selection
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
141 / 448
11.8 Navigate to Monitoring View
Click on Navigate to Monitoring View menu option of the Port menu to navigate to the corresponding
Monitoring View that is related to the selected TP.
Navigation to the Monitoring view permits to show a complete overview about the Monitoring Operations
(POM, SUT, TC) as for the example of the following figure.
In Figure 105. on page 142 is shown an example of Monitoring View of a TP with POM and TCM both
before and after matrix.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 105. View of Monitoring Operations (example 1)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
142 / 448

Select a TP where are configurated some Monitoring Operations (POM, SUT, TC).

In Figure 106. on page 143 is shown an example of Monitoring View of a TP with POM after and before
matrix and TCT before matrix, and a second TP with TCM after and before matrix.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 106. View of Monitoring Operations (example 2)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
143 / 448
11.9 Navigate to HOA port View

After having selecting a TP (for example AU4), click on Port > Navigate to HOA Port View option.
The HOA port displays the internal structure of the payload, as for the following figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 107. Navigate to HOA port
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
144 / 448

12 EQUIPMENT PROTECTION MANAGEMENT

12.1 Introduction
It is unthinkable to launch a telecommunications system, handling millions of communications, without the
possibility of replacing equipment in a real time way, consequent to equipment failure. Everything must
be done so that the communications can continue smoothly and so that the equipment failure remains
transparent to the users. Protection management deals with this aspect of the EMLUSM.
The protection is performed by switching the board supporting the protected service when this board fails
to a protecting board capable of supporting the same service. This protection is realized according to a
protection scheme.
An equipment protection scheme is composed of the following parameters which can be configured:
Group type: 1+1 or 1+n

the group type specifies if one or more unreliable resources for protection can be assigned to
one or more reliables resources. 1+1 group type means that a working element is protected by
one protecting unit. 1+n group type means that n working elements are protected by only one
protecting unit.
Protection priority
A priority can be assigned to protected units in 1+n protection schemes. This priority can be
1, 2, ... or n, 1 being the highest priority.
Configuration type: revertive or non revertive

In revertive mode, a protected service will be switched back to its protected element when it has
recovered from its failure.
In non revertive mode, the switch to the protecting element is maintained even after a recovery
from failure.
Protection wait to restore time

Used when revertive mode is active, the protection wait to restore time prevents several
protection switches due to an intermittent failure. A protected element must be fault free during
this fixed period of time before a protected service is switched back to it.
Board duplication remains the easiest way to ensure equipment protection in a system.
The actions that can be undertaken are of the following type:
Consult and modify an Equipment Protection Scheme (EPS)

Force Switch EPS
In Board view, the board whose contents is represented is considered as implicitly selected.
1AA 00014 0004 (9007) A4 ALICE 04.10
EPS protection states are displayed by the functional state message area of the boards involved in an
equipment protection scheme.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
145 / 448
12.2.1 Introduction
In order to consult EPS, perform the following operations.
The Port view is reached selecting the Equipment option in the Views pull down menu, then double
clicking on the presented rack/subrack to present the subrack view, as described at chapter 9.1 on page
91.
Select the Equipment option in the Views pull down menu.

Double click on the presented rack/equipment/subrack to present the subrack view.
Select the EPS pull down menu. Then select the Management... option as show in the following
figure.
Figure 108. Consulting EPS

A dialogue box like the following example is opened.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 109. EPS Management dialogue box
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
146 / 448

12.2 Management: consulting and modifying EPS

The EPS Management dialogue box shows the current NE protection schemes in the left side. The
list gives for each protecting board the protected board(s).
The available protection schemes are coherent with the NE type and release.
The right side of the dialogue box allows to modify the EPS configuration.
If no protection scheme have been created the dialogue box fields are empty.
The current release of this NE fix the following protection:
N+1 (with N 15) P4ES1N protection:
board of slot MAIN (protected): P4ES1N, from slot 25 to 39
board of slot SPARE (protecting): P4ES1N, from slot 24 to 38
Note: for P4ES1N more than one protection group N+1 revertive can be created, depending
on the equipment configuration.
The spare board position can be assigned in a flexible way. The only constraint are the following:
the access card corresponding to the protecting board must be an HPROT card
the HPROT card has to be plugged at the left side of the access card group
the main/spare boards have to be adjacent
the protecting board has to be plugged at the left side of the protected group of boards
the protecting/protected group of ports have to be of the same type
N+1 (with N 15) P16S1N protection:
board of slot MAIN (protected): P16S1N, from slot 25 to 39
board of slot SPARE (protecting): P16S1N, from slot 24 to 38
Note: for P16S1N more than one protection group N+1 revertive can be created, depending on
the equipment configuration.
The spare board position can be assigned in a flexible way. The only constraint are the following:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
the access card corresponding to the protecting board must be an HPROT16 card
the HPROT16 card has to be plugged at the left side of the access card group
the main/spare boards have to be adjacent
the protecting board has to be plugged at the left side of the protected group of boards
the protecting/protected group of ports have to be of the same type
1+1 MATRIX protection:
01
board of slot 22, HCMATRIX main (protected)
board of slot 41, HCMATRIX spare (protecting)
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
147 / 448
For each type of failure on the HCMATRIX main board (CRU, Shelf Controller) a switch is performed
to the spare boards.
N.B.
I M P O R T A N T : upon inserting a new HCMATRIX unit or when it is inserted again, wait

approx. 10 minutes (i.e. that the orange LED on the HCMATRIX frontplate lights on and
simultaneously the clock symbol on the unit on the CT has disappeared) and 20 minutes
again to allow the synchronization between the two HCMATRIX units.
The presence of errors in case of a matrix switch is related to the switch of the CRU functionality and
strictly depends on the CRU mode selected at the time of the switch.
CRU locked: in this case the clock generated by the HCMATRIX active and by the
HCMATRIX standby are exactly the same, since locked to the same 2 MHz reference. A
switch event is simply a change of the selection of clock and data on the port boards that are
receiving identical and perfectly aligned data from the active and the standby HCMATRIX.
In this case, when the switch is due to a command, we can guarantee a minimum impact on the
traffic (errors, if any, are generated for less than 50 ms) that is due to the time needed for the
selection of the new clock.
CRU in free running or holdover: in this case the clock generated by the HCMATRIX active
and the HCMATRIX standby are not the same, since each of them is obtained from the local
10 MHz generator.
A switch event is again a change of the selection of clock and data on the port boards, but they
are now receiving different data (generated with different clocks) from the active and the
standby HCMATRIX.
In this case the impact on the traffic is due to two contributions: the time needed for the selection
of the new clock (that is exactly the same as in the previous case) and the time needed to the
port for the realignment of the data.
1AA 00014 0004 (9007) A4 ALICE 04.10
It is important to highlight that the free running and holdover situations are reached only after a
sequence of several failures, i.e. the loss of all of the synchronization sources (up to six may be
configured) of the node.
Furthermore the effect on the traffic is evident only if this situation is combined with a matrix switch.
In other words, the behavior described is a consequence of several multiple failures which affect both
the synchronization sources and the hardware.
The protection mechanisms implemented for the synchronization sources are typical of a node for
the SDH network.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
148 / 448

12.2.2 Note about HCMATRIX EPS

12.2.3 EPS management

The HCMATRIX protection is automatically presented in the left side of the dialog box
when the SPARE HCMATRIX is created in the Set option of the Equipment menu. It is not
created with the EPS menu described in this chapter.
This right side is divided into two parts.
The upper part provides a message field with the name of the Protecting board and a choose button to
display the list of boards available.
The lower part provides a list to display the Protected boards currently in the displayed scheme.
A choose button is provided to display the list of boards which could be added as protected.
A delete button enables user to remove a protected board from a scheme.
a)
Scheme displaying
To display a specific scheme, user selects an item on the left list.

This operation fills the protecting element text field and the protected list with the board user name. If user
clicks where there is no item displayed, the right part is displayed empty.
The Cancel button closes the dialog box.
b)
Scheme creation
To create a new protection scheme, dont click on item in the left list.
In this way the right part is displayed empty and the Choose Protecting button is sensitive.
Press this button to displays a window to choose a board in the Board Selection list (see Figure 110. on
page 150). The board are listed opening the NE > rack > subrack levels.
After that operation, Choose Protecting button becomes insensitive and Choose Protected button
becomes sensitive (see Figure 111. on page 150).
The user can add, always using the same Board Selection list dialogue box presented, as many
protected bitributary boards as wanted (max. 8, N+1).
When the right part of window is correctly filled, the OK button close the dialog box and create the scheme
(the new list is update reopening the EPS Management dialogue box).
The Cancel button cancels the creation and closes the dialog box.
c)
Scheme deletion
To delete an existing protection scheme, the user selects a scheme in the left list. Using the Delete button,
user could delete the scheme.
1AA 00014 0004 (9007) A4 ALICE 04.10
d)
Scheme modification
To modify an existing protection scheme by adding or removing protection units, the user selects a scheme
in the left list. Using Choose button for protected elements, user could add protected boards.
By selecting a protected board and using the Delete Protected button, user could remove protected
elements from scheme. When the right part of window is correctly filled, the OK button close the dialog
box and modify the scheme .
The Cancel button cancel the modification closes the dialog box.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
149 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 110. EPS: board selection
Figure 111. EPS: choose protected
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
150 / 448

The EPS functional state of a board selected in the board view is displayed at the bottom of the view as
shown in the following figures.
Protection role
Protection status
Switch Type
Figure 112. EPS functional state from protected active board view
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 113. EPS functional state from protecting active board view
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
151 / 448
12.3 Configuration: revertive and WTR for EPS
In order to configure, perform the following operations:
Select a Protected or Protecting board in the Equipment view.
Select the EPS pull down menu. Then select the Configure option as show in the following figure.
Figure 114. Configure EPS
1AA 00014 0004 (9007) A4 ALICE 04.10
The following dialogue box is opened (see two examples shown in Figure 115. on page 152 and in
Figure 116. on page 153).
Figure 115. EPS Management dialogue box (HCMATRIX board)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
152 / 448

This functionality configure Revertive and Wait Time to Restore in a protection scheme.

Figure 116. EPS Management dialogue box (P4ES1N board)

The dialog box provides configuration for elements such as :
the name of the protecting element as a label

the Equipment Type of the protecting element as a label
a list displaying the protected elements owned by the scheme
the Revertive Mode flag as an option menu. The available values are revertive and non revertive
the Wait to Restore time value (steps of 30 seconds, from 60 to 600). Only for N+1 EPS
Notes: in the current release the Wait Time to Restore is fixed to 5 minutes.
For this NE:
1 + 1 HCMATRIX is Not Revertive only
N +1 4xSTM1 Electrical port (P4ES1N) protection is Revertive
N +1 16xSTM1 Electrical port (P16S1N) protection is Revertive
1AA 00014 0004 (9007) A4 ALICE 04.10
When the configuration of the equipment protection scheme is completed confirm closing the dialog box
by clicking on the OK button. The Cancel button cancels the configuration and closes the dialog box.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
153 / 448
12.4 Switching EPS
The forced switch will fail if the other board is already forced switched or if the protecting board has a failure
condition.
In order to switch an EPS, perform the following operations:
Select a transmission board in the Equipment view.
Select the EPS pull down menu. Then select the Switch option as show in the following figure.
Figure 117. Switching EPS

The following dialogue box is opened (HCMATRIX board in the example):
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 118. EPS Switch dialogue box
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
154 / 448

This functionality enables to force a protecting board to work even if there is not failure.
1AA 00014 0004 (9007) A4 ALICE 04.10

This dialogue box displays in its left part the EPS of the selected board.
From this dialogue box the operator can configure, in the current release, only the Manual to by clicking
on the relevant radio button.
The Switch to command perform the manual switch, active only if the other board is not alarmed.
Clicking on the OK button will initiate the switch and close the dialogue box. The Cancel button cancels
the operation and closes the dialogue box.
A T T E N T I O N : before sending a matrix EPS command verify that the standby

HCMATRIX has been inserted at least 20 minutes before (see note at para.
12.2.2 on page 148).
N.B.
ED
01
If RUM alarm is displayed on both HCMATRIX (before and/or after switching) it is

also necessary verify the BTERM unit presence in the subrack (BTERM without
faults).
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
155 / 448
12.5 EPS Overview

EPS Overview allows to display as well as search for EPS states.

Selecting the EPS Overview option from the Configuration pull down menu Figure 119. opens.
Figure 119. EPS overview

To Search the EPS groups two different ways of filtering are supported; a filtering for all protection units
located on a dedicated Board Type as well as a filtering for protection units carrying a specific Status.
The search criteria can be chosen with the help of a combo box:
1AA 00014 0004 (9007) A4 ALICE 04.10
Board Type: allows to filter for the EPS protected boards; the following filters values should be
offered (examples):
ED
Ignore
HCMATRIX
P4ES1N
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
156 / 448

Status: allows to filter for all possible EPS protection states;the following filters values should be
offered (examples):
Ignore
Normal
DNR
AutoFail
AutoWTR
Manual
Force
Lockout
After the filter selection click on Search button to start; the field below the Search button will be updated
(see Figure 120. ).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 120. EPS overview after Search (example with HCMATRIX)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
157 / 448
Protection Group
(example protection GroupId, 10)
Board Id
(example r01sr1/board#9 )
Board Role:
Ped
Ping
(Protected)
(Protecting)
B Status (board status):

Each protection unit is presented with the following information:
A
S
F
(Active)
(StandBy)
(Faulty)
Protection Status: defines the current state of the protection unit as follow
Normal
DNR
AutoFail
AutoWTR
Manual
Force
Lockout
(Do Not Revert)

(Autoswitch Equipment Fail)
(Autoswitch Wait Time to Restore)
(Manual switch)
(Force switch)
The colors used for each row have the following meaning:
Green (OK):
for protected protection units active
Red (Critical):
for protected protection units in fail condition, protection unit in lockout or active
on autoswitch or commands
Orange (Major):
for protected units in standby after a command and protecting protection unit
in standby for autoswitch or commands
Cyan (Indicative):
for protecting protection unit active and no fail condition present in the schema
(Do Not Revert State)
At the bottom of the EPS Overview windows are available five button that allows to navigate through the
EPS management views and subrack view, board view.
In this way the operator has a quick link towards the views showing the correlation between the alarms
and the protection states.
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE: Before to click on one of the five buttons select a row.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
158 / 448
The buttons available are:

Open Subrack View:

opens the Subrack view showing the protection states with icons on the
boards.
The possible protection states and the relevant symbols are explained in
the following:
Symbol
EPS protection status

No Request
Do not Revert
Lockout
Auto Switch (WTR, Fail)
Manual
Forced
Open Board View:
opens the board view showing the alarm and the board administrative
states. See the relevant description.
Open Commands:
opens the EPS Switch dialog box. See the relevant description.
EPS Management:
opens the EPS Management dialog box. See the relevant description.
EPS Parameters:
opens the EPS Configuration dialog box. See the relevant description.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on Close button to exit from the EPS Overview window.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
159 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
160 / 448

13 MULTIPLEX SECTION PROTECTION MANAGEMENT

13.1 Architecture types
The Multiplex Section Protection is the connection between two NEs protected by a cable and port
duplication. At the source the signal is duplicated and sent to the sink via two independent cables. When
occurs a multiplex section failure, the system switches to the other cable and port.
The MS Linear Trail Protection can be applied to any NE where it is possible to configure a linear APS
(single ended/dual ended) line protection. For this NE is applicable the APS 1+1 Proprietary, the APS
1+1 Standard and the APS 1 :1 Standard dual ended.
The APS 1 +1 (not revertive) feature permits a 1+1 protection in a linear link, where a path signal is
protected by another dedicated path carrying the same signal. The protection can be set both in single
(unidirectional) and in dual (bidirectional) ended mode.
In single ended mode (unidirectional) the protection is accomplished by switching only the signal affected
by the failure.
In dual ended mode (bidirectional) the protection is accomplished by switching both the affected and the
unaffected signals.
Architecture 1+1 Standard
Described in ITUT Rec. G783/G841. The refence switching criteria are SF and SD. It provides a
k1/k2 communication protocol thus this protection can be single or dual ended.
Architecture 1+1 Proprietary (not used)
The refence switching criteria are SF and SD. No k1/k2 communication protocol is provided thus
this protection can be only single ended.
Architecture 1+1 Optimized (not used)
Architecture 1 : 1 Standard
Described in ITUT Rec. G783/G841 as architecture 1 : N ( when N=1 ). The reference switching
criteria are SF and SD. It provides revertive mode managed by k1/k2 protocol and thus this
protection can be single or dual ended. The spare interface can be used to transport low priority
traffic .
The WTR time is used with revertive mode.
1AA 00014 0004 (9007) A4 ALICE 04.10
Signal Degrade (SD) software setting enables the MSP protection mechanisms when a SD is recognized
on the working port. The SD threshold reference value depend on the NE selected threshold on the MS
termination point. This threshold value is configured as explained in the para. 14.7 on page 196.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
161 / 448
13.2 MSP options introduction
Select Equipment from the Views menu.
Double click on rack/subrack.
Double click on the SDH optical board to configure to open the port icon.
Double click on the port icon to open the port view.
Select the MSP block in the port view and then choose the MSP options by clicking on Port > MSP
menu; the possible choice are:
MSP Create
MSP Management see para. 13.4 on page 167
MSP Commands
MSP Delete
1AA 00014 0004 (9007) A4 ALICE 04.10
All these previous options can also be accessed from the Transmission > MSP menu.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
162 / 448

All the MSP options are available starting from the Port View following the step explained below:

13.3 MSP Create

Select the MSP Create option from the Port > MSP menu (see Figure 121. on page 163) to open the
MSP Schema Creation (see Figure 122. on page 163).
Figure 121. MSP Create option
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 122. MSP Schema Creation
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
163 / 448
Are supported in this release two MSP Protection Schemas:

MSP 1+1 standard

MSP N:1 standard
Select one and then click on Add Port button in the Ports field to create a MSP schema.
Following steps are necessary:
choose Port
select a Port Role (protected or protecting)
define Channel Id (mandatory for MSP N:1)
define SDH Priority (type of traffic, High or Low)
Figure 123. MSP schema creation Port dialog
Select the Choose Port button to define the Protected Port and Protecting Port units.
Click on RackSubrack and select the Board (Protected / Protecting) on the Equipment window (left
side).
The termination Points list (right side) is available.
1AA 00014 0004 (9007) A4 ALICE 04.10
On this right side select the OpS TP of the chosen board and then click on the OK button. It is possible
to select the board through the Board History button selecting the board list menu.
The Filter Section is divided into different fields. It permits to visualize a reduced TP Class. If used, OpS
class must be selected. The complete TP research description is reported in the Transmission View para.
14.5.1.2 on page 188.
Click on the OK button and repeat the operation for both Protected Port and Protecting Port. If it has
been selected a Protected/Protecting port configured in a previously MSP schema protection an error
message of access denied will be appear on the screen.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
164 / 448

Figure 124. TP Search
In the dialogue of Figure 122. on page 163 also configure the MSP protection schema with the chosen
Protection Schema and enter the related Schema Parameters according the following rules:
1+1 Standard can be dualended or singleended, Not Revertive

N+1 Standard can be dualended or singleended, Revertive
Decide if enable the MSP protection mechanisms when a Signal Degrade is recognized.
At the end click on the OK button to confirm the MSP protection schema configuration. An error message
will be appear if the selected schema is not supported by the NE.
1AA 00014 0004 (9007) A4 ALICE 04.10
In Figure 125. on page 166 and Figure 126. on page 166 are shown two examples of MSP schema
creation.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
165 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 125. MSP 1+1 standard protection schema (example)
Figure 126. MSP N:1 standard protection schema (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
166 / 448

13.4 MSP Management

Select the MSP Management option from the Port > MSP menu (see Figure 127. on page 167) to open
the MSP Schema Configuration (see Figure 128. on page 168).
Figure 127. MSP Management option

The MSP Schema Configuration dialog shows the current state of the MSP schema, settings and state
(protected or protecting) of the current SDH-n port.
This dialog allows to set the configuration parameters for the designated multiplex section:
Protection Schema reported in the previous paragraph 13.1 on page 161
Dual Ended / Single Ended protection switch and directionality
Revertive/Non Revertive mode (always not revertive in current release)
Protected Port: the location of the board hosting the protected port is displayed (see Ports field)
Protecting Port: the location of the board hosting the protecting port is displayed (see Ports field)
The WTR Time (Wait To Restore) is the delay time for switching protection and protecting port after
recovery from failure / defect. In current release this Time is fixed to 300 seconds.
1AA 00014 0004 (9007) A4 ALICE 04.10
Configure the MSP protection Schema with the chosen protection schema and enter the related schema
parameters. At the end click on the OK button to configure the MSP protection schema. An error message
will be appear if the selected schema is not supported by the NE.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
167 / 448
The same MSP Management option can be used to modify the schema parameters of an active MSP
configuration.
Before changing a single ended (unidirectional) schema into a dual ended (bidirectional), all active
switches must be cleared (manual switch, lockout,...). If the operator wants to change the protection
schema architecture or the ports involved in the MSP schema, the current schema must be removed and
recreated.
Figure 128. MSP Management view
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 129. MSP Protection Status example

Figure 129. on page 168 represents a forced command. The forced indication is both reported on the
protected and protecting units. The Active status indication shows where the forced command is applied.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
168 / 448

13.4.1 MSP modification

13.5 Display of Protection State

The MSP protection state of a port is displayed at the bottom of the Port view. Some examples are reported
in Figure 130. on page 170.
The following states are always displayed:
Port Status Active (red color) or Standby (orange color). The active protection status is referred
to a protected/protecting port (where the traffic is transported): when a failure is detected, the
protecting port is ready to save the traffic (and becomes active). The standby protection status is
referred to a protecting/protected port that is ready to save the traffic.
MSP Protection Role Protected (green color) or Protecting (ochre color). The protection role
depends on the selected port type (Protected / Protecting).
MSP Group Status, MSP Own Unit and MSP Related Unit (green color) Displayed if an automatic
switch is requested. Own Unit stands for the currently displayed unit in the port view, Related Unit
stands for the related unit of the same protection group. The status indications are:
NR: (abbreviation of No Request); normal, idle condition, the traffic is on the main port
DNR:(abbreviation of Do Not Revert); the SF or SD have been recovered but the traffic is
switched on the spare port
PF: a protection failure has been detected on the port
RF: a release command has been failed
FOP: a failure of protocol has been detected
complete: = the bridge/switch actions are completed
pending: = the bridge/switch actions are pending
The complete and pending indications precede the following statuses:
AS: automatic protection switching enabled
MS: a manual local protection command has been activated
FS: a forced local protection command has been activated
LO: a lockout local protection command has been activated
SF/SD: Signal Failure or Signal Degraded has been detected
WTR: wait time to restore status
MSP Request Source (green color) indicates where the operator commands (force/manual/lockout)
have been performed. Only present when a command is operative.
Local: switch due to near end SD/SF or local user switch command
Remote: switch due to received K1/K2 bytes.
A remote switch cannot be released locally, but can be overwritten by a switch with higher
priority.
MSP Protocol Status

This parameter indicates the current APS Protocol status.
The following values are possible:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
OK
Failure (in case of FOP)
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
169 / 448

MSP statuses displayed in a normal conditions
MSP statuses displayed after an automatic protection switching
MSP statuses displayed after a forced command
Figure 130. MSP Protection Status Examples
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 130. represents a MSP configuration with a normal condition, with an automatic protection
switching and with a forced command. In any situation are represented the statuses displayed on both
protected/protecting Port views. The Active status indication, with a forced command on the protecting
group, shows where the forced command is applied.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
170 / 448

13.6 MSP Commands

Select the MSP Commands option from the Port > MSP menu (see Figure 131. on page 171) to open
the MSP Commands window (see Figure 132. on page 172).
Figure 131. MSP Commands option

Protecting Port : the location of the board hosting the protecting port is displayed.
Protected Port : the location of the board hosting the protected port is displayed.
The Lockout of protection command denies working channel access to the protection section by issuing
a Lockout of protection request (on the Protection Status of MSP Management).
It is possible to Lockout the Protecting Port or Lockout the Protected Port; to remove the lockout
commands select Release Ping (for the protecting) and Release Ped (for the protected).
In MSP 1+1 the Lockout of protection command is available, but the Lockout of protected command
is not available. In MSP N:1 both commands are available.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Force to command switches the working channel (Protected port) to the protection section
(Protecting port), unless an equal or higher priority switch command is in effect or SF condition exits on
the protection section, by issuing a Forced switch request for that port (on the Protection Status of MSP
Management). It is also possible to switch back to the working channel using again the Force to
Protected port command.
For 1+1 nonrevertive system, forced switch no working channel transfers the working channel back from
protection to working section, unless an equal or higher priority request is in effect. Since forced switch
has higher priority than SF or SD on working section, this command will be carried out regardless of the
working section condition.
The Manual to command switches the working channel (Protected port) to the protection section
(Protecting port), unless a failure condition exits on the protection section or an equal or higher priority
switch command is in effect, by issuing a Manual switch request for that port (on the Protection Status
of MSP Management). It is also possible to switch back to the working channel using again the Manual
to Protected port command.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
171 / 448
The Clear WTR command cancel the delay time for switching protection and protecting port after recovery
from failure/defect. It is not operative in current release.
The Exercise command issues an exercise request for protection channel and checks responses on MSP
bytes, unless the protection channel is in use. This check controls the k1/k2 communication protocol
functionality to be sure that the protocol is right also on the protection section.
Not Operative in current release.
The Release command clears all previously switching commands.
Figure 132. MSP Commands
The priority levels for the MSP commands are (from the higher to the lower one): Lockout, Force to,
Autoswitch (SF&SD), Manual to.
1AA 00014 0004 (9007) A4 ALICE 04.10
Refer to G.841 ITUT Rec. about MSP commands and autoswitch protection criteria and priority.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
172 / 448

For 1+1 nonrevertive system, manual switch no working channel transfers the working channel back from
protection to working section, unless an equal or higher priority request is in effect. Since manual switch
has lower priority than SF or SD on working section, this command will be carried out only if the working
section is not in SF or SD condition.

13.7 MSP Delete

Select the MSP Delete option from the Port > MSP menu (see Figure 133. on page 173) to open the
MSP Schema Deletion (see Figure 134. on page 173).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 133. MSP Delete option
Figure 134. MSP Schema Deletion

Click on OK button to delete the selected MSP Schema Configuration.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
173 / 448
13.8 MSP overview

MSP Overview allows to display as well as search for MSP states.

Selecting the MSP Overview option from the Configuration pull down menu Figure 135. opens.
Figure 135. MSP overview

To Search the MSP groups two different ways of filtering are supported; a filtering for all protection units
located on a dedicated Board Type as well as a filtering for protection units carrying a specific Status.
The search criteria can be chosen with the help of a combo box:
1AA 00014 0004 (9007) A4 ALICE 04.10
Board Type: allows to filter for the MSP protected boards; the following filters values should be
offered (examples):
ED
Ignore
P4ES1N
P4S1N
P4E4N
P4S4N
S41N
L41N
L42N
P16S1N
S161N, S161ND
L161N, L161ND
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
174 / 448

L162N, L162ND
S642
L642
L642CF
Status: allows to filter for all possible EPS protection states;the following filters values should be
offered (examples):
Ignore
NR (Normal)
DNR
AutoSF
AutoSD
AutoWTR
Manual
Force
Lockout
APS Invalid (Fail)
Bad channel (Fail)
1AA 00014 0004 (9007) A4 ALICE 04.10
After the filter selection click on Search button to start; the field below the Search button will be updated
(see Figure 120. ).
Figure 136. MSP overview after Search (Example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
175 / 448
Protection Group
(example protection GroupId, 160)
Port Id
(example r01sr1sl10/port#01OpS )
Role:
Ped
Ping
Protected
Protecting
Status (board status):

Each protection unit is presented with the following information:
A
S
F
ET
(Active)
(StandBy)
(Faulty)
Extra Traffic (Not operative)
Protection Status: defines the current state of the protection unit as follow
NR
DNR
AutoSF
AutoSD
AutoWTR
Manual
Force
Lockout
APS Invalid
Bad channel
(Normal)
(Do Not Revert)
(AutoSwitch Signal Fail)
(AutoSwitch Signal Degrade)
(AutoSwitch Wait Time To Restore)
(Manual Switch)
(Protection fail condition APS Iinvalid)

(Protection fail condition Channel Mismatch)
The colors used for each row have the following meaning:
Green (OK):
for protected protection units active
Red (Critical):
for protected protection units in fail condition, protection unit in lockout or active
on autoswitch or commands
Orange (Major):
for protected units in standby after a command and protecting protection unit
in standby for autoswitch or commands
Cyan (Indicative):
for protecting protection unit active and no fail condition present in the schema
(Do Not Revert State)
At the bottom of the MSP Overview windows are available five button that allows to navigate through the
MSP management views and to open the Port View.
By clicking on Open Port Viewt the operator has a quick link towards the view showing the correlation
between the alarms and the protection states.
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE: before to click on one of the five buttons select a row.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
176 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10

The buttons available are:
Open Port view:
opens the port view showing the correlation between the alarm and the MSP
protection states.
MSP Create:
opens the MSP Create dialog box. See the relevant description.
MSP Delete:
opens the MSP Delete dialog box. See the relevant description.
MSP Management: opens the MSP Management dialog box. See the relevant description.
MSP Commands: opens the MSP Commands dialog box. See the relevant description.
Click on Close button to exit from the EPS Overview window.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
177 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
178 / 448

14 TRANSMISSION VIEW
14.1 Overview
This section describes the operations necessary for the consultation, modification and configuration of
TPs, providing a representation of the entire signal flow.
The generic Transmission View, described in this chapter, offers the possibility of displaying a single TP
or a set of all kinds of TPs (or collected functionality which is represented by one/several TPs).
To display the termination points in the Transmission View, either select specific TPs from a TP search
dialog or access the view directly from another view, e.g. by navigating from the Port View.
The Transmission View provides the following features:
Brief overview regarding transmission resources.
An overview concerning all TPs belonging to a port can be called in by activating the function
to expand the selected TP. TP names are listed in an additional information area if the mouse
pointer is positioned over it. The following states are indicated:
1AA 00014 0004 (9007) A4 ALICE 04.10
the alarm state is indicated by the alarm synthesis icon

the cross-connection state is indicated by a cross
whether a TP can be structured is indicated by a circle
whether a TP is under Performance Monitoring indicated by a blue P letter
whether a TP is involved in a loop action, it is indicated by a backfolded arrow
An overview concerning signal flow can be requested by a user action. The user can select
a TP and apply the action Show Cross-connected TPs. The result is that the objects related
to the TP are displayed and lines indicate the connections. Expanding and hiding TPs that are
related to the currently selected TP enables all related TPs to be added to the view, thus
providing a representation of the entire signal flow.
Display of single or multiple termination points.
Search for and select a termination point in a TP search dialog and display it in the Transmission
View.
Pop-up the Transmission View from the board view. All TPs/compound TPs associated with the
physical port are displayed (i.e. TPs down to AU-4).
Provide the functionality to create/show cross-connections.
Provide the functionality to create/show Multiplex Section Protection.
Provide the functionality to create/show Loopback commands.
Provide the possibility of configuring a selected TP. This functionality is accessed by calling the
configuration dialogs of the common Transmission/Port Views category.
Provide the possibility of showing a detailed view of a TP with alarms, navigating to the Port view.
Provide the possibility of showing and setting Performance Monitoring parameters and data.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
179 / 448
14.2 View Elements


The Transmission View uses the symbols illustrated in Figure 137.

!

Figure 137. Symbols Used in Transmission View
14.3 View Layout

The Transmission View is a main view. It provides views of specific areas, which display the transmission
resources, and the specific Transmission View pulldown menu which provides the Transmission View
operations.
1AA 00014 0004 (9007) A4 ALICE 04.10
14.3.1 View Description

Figure 138. illustrates the Transmission View area. TPs that are received from the network element are
displayed in the Transmission View with the respective TP and connection symbols described in
Figure 137. on page 180. The number of TPs presented initially depends on whether the Transmission
View is popped up from a board view, whether a TP has been selected in another view or whether it is called
without a selected TP.
When the Transmission view is reached selecting the Transmission option in the Views pull down menu
in its initial state contains no objects.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
180 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10

SDH
port
ETH
port
Figure 138. Transmission View Area (SDH & ETH)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
181 / 448
It is possible both to expand a VC-4, thus displaying all underlying TPs, and to hide TPs which are of no
interest. The objects initially displayed depend on the situation/definition.
14.3.3 Naming TPs
The following rules are applied in order to identify the TPs displayed:
the root node contains the full user label
all child nodes contain a short label indicating the position inside the tree.
14.3.4 Dynamic View Behavior

The following section describes the view states and provides a short description of events that affect the
view.
14.3.4.1 Initial state of the view
In its initial state, the Transmission View contains no objects. Objects can be searched for and displayed
using the Add TP dialog.
14.3.4.2 Working state of the view
In its working state, the Transmission View already contains objects. If the operator searches for and
displays a TP using the TP Search dialog, the view is first initialized again and then the TP is displayed.
The same applies in the case of navigation from another view to the Transmission View the Transmission
View is always initialized and the corresponding objects are then displayed in it.
14.3.4.3 Navigation to Transmission View from other views
If the Transmission View is popped up from the Port View, only the selected TP is displayed.
14.3.4.4 Alarm notification
Alarms concerning the TPs displayed are indicated graphically by the alarm synthesis icons of the TP
objects. The TP objects are updated accordingly.
14.3.4.5 Object deletion
1AA 00014 0004 (9007) A4 ALICE 04.10
All kinds of object deletion events related to TPs displayed are indicated by the TP objects. The graphical
objects are removed accordingly from the Transmission View.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
182 / 448

14.3.2 Number of TPs Displayed in Transmission View
1AA 00014 0004 (9007) A4 ALICE 04.10

14.4 Transmission view access and menu

The Transmission view can be reached selecting the Transmission option in the Views pull down menu.
In this case, in its initial state, the Transmission View contains no objects.
In the case of navigation from another view (example the Port view) to the Transmission View, the
Transmission View is always initialized and the corresponding objects are then displayed in it (see for
example Figure 138. on page 181).
Selecting the Transmission option in the menu bar of Figure 138. on page 181.
The complete pull down Transmission menu is presented (see Figure 139. on page 184).
The following menu items are available:
Add TP:
Select the TP to show on the Transmission view.

Expand:
Display TPs that are related to the selected TP.

Hide :
Hide TPs that are related to the selected TP or the selected TP.
TP Configuration:
Set parameters for the Overhead on Synchronous TPs.

TP Threshold Configuration:Set B2 ExBER and Degraded Signal parameters.

Terminate TP:
Terminate a path on a AU4CTP.

Disterminate TP:
Disterminate a path on a AU4CTP.

AU4 Concatenation:
Manage the concatenation of AU4.

Cross-Connection:

Monitoring Operations:
Create, configure and delete POM/SUT/TC TPs.

Performance:

Structure VC4 :
Provides the possibility of structuring and destructuring selected TP.

NOT USED in this NE.
Loopback:
Manage the loopback commands, for commissioning or

maintenance purposes. See para. 14.10 on page 203.
Physical Media:
Manage the physical TP setting.

ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
183 / 448
MSP :

Only for SDH port. See para. 13.4 on page 167.
In this paragraph is not described the MSP>NE MSP synthesis
option of the Transmission menu because not used in this NE.
Show Supported Board:

Navigate to Port View:
Permit to show the detailed alarm of the TP.

These options are described in next paragraphs except the previously referenced.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 139. Transmission menu options
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
184 / 448


14.5 Add TP
Select the Transmission > Add TP option.
This menu item opens the TP Search dialog (see Figure 140. ). The TP Search dialog enables the user
to search for and add a TP to the Transmission View (e.g. search for all TPs on a board with PM enabled).
14.5.1 TP Search
14.5.1.1 Default Mode
In this mode, the dialog displays the structure of the equipment tree. After double-clicking, e.g. on a port,
the contents of the port appear on the right-hand side of the dialog (TP list). To keep the number of items
displayed small, they are displayed in a hierarchical order.
Double-click again to recall the next level (see Figure 142. on page 186).
Figure 140. TP Search Dialog, Initial State
1AA 00014 0004 (9007) A4 ALICE 04.10
After double-clicking on an object, an Information window appears (see Figure 141. on page 186). The
message text corresponds to the object selected.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
185 / 448
The search can be stopped with Cancel.
1AA 00014 0004 (9007) A4 ALICE 04.10
It is possible to select several individual TPs from the TP list by clicking on them while holding down the
Ctrl key on the keyboard. To select a block of TPs, click on the first TP and then click on the last TP in the
block while holding down the Shift key on the keyboard. But only the first TP selected in the list will be
shown in the Transmission View.
Figure 142. TP Search Dialog with Various TP Selections
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
186 / 448

Figure 141. Information Window

After clicking on Show CC State, a more detailed TP list is displayed (see Figure 143. ) containing TP
cross connection status information.
Figure 143. TP Search Dialog with Status Information Displayed

The symbols in the TP list have the following significance:
"

#

"
Figure 144. Symbols in TP Search
1AA 00014 0004 (9007) A4 ALICE 04.10
The background color of the symbols represents the status of the TP:
ED
grey = inactive
green = active
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
187 / 448

An easy way to recall to previously displayed boards is to use Board History. Select the relevant board
from the list.
Figure 145. Board History Check List

14.5.1.2 Search Mode
1AA 00014 0004 (9007) A4 ALICE 04.10
Use Search Mode together with the filtering options provided below the TP list (see Figure 146. ). The
following options are available:
Class:
Ignore, EIS STM1 Electrical, OpS (SDH optical), PPI (140 Mbit/s), MS, RS, AU4, VC4, VC4+AU4,
GMAU.
Assign State:
Ignore, NML, EML
Perf Monitoring (Performance Monitoring condition):

Ignore, enabled
Connection State (Current connectivity status):

Ignore, not connected, connected
Alarm State (Path Trace):

Ignore, critical, major, minor, warning, not alarmed
TTI expect: not used
TTI receive: not used
TTI transmit: not used
Location:
Permits
to
insert
the
location
r<rack#>sr<subrack#>sl<slot#><port#>
ED
of
the
TP
in
the
following
format:
Name: not supported
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
188 / 448

Figure 146. TP Search Dialog with Different Filtering Options

After activating the search process with the Search button, the following dialog box appears. The search
can be interrupted by clicking on Cancel.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 147. Information... Dialog for Search Process

Note: When searching for PM-enabled TPs on NE, Rack or Subrack, the time for the request can
be very high. It is recommended to search for PM-enabled TPs at the board level (a board is selected
for the search) with filter.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
189 / 448
The following buttons are available in all modes (see Figure 146. on page 189):
It closes the dialog and opens the Transmission View containing the selected TP, as for the
example of Figure 138. on page 181.
Close
It closes the dialog without updating the Transmission View.
Print
This command is used to generate and print a list of TPs according to the current filter selection
(refer to Figure 150. on page 191 for an example of a printout).
The command opens the following dialog:
Figure 148. Print to Printer

Select the desired printer from the list box and click on Ok to start the print job or abort with
Cancel.
The dialog changes after clicking on File:
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 149. Print to File

Enter the name of the output file in the input field or select a file name from the File Select dialog
by clicking on Select file. Select if the output format should be Postscript or ASCII.
The output file is generated after clicking on Ok. Use Cancel to stop the process.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
190 / 448

Ok
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 150. Example of Printout
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
191 / 448

14.6 TP Configuration
TP Configuration can also be accessed from the Port view menu.

14.6.1 High Order TP Configuration
Depending on the TP selected, a dialog appears for the configuration of the main parameters of the
following objects:
VC-4 TTP (140 Mbit/s PDH)

AU-4 CTP (STM1 SDH)
VC4XV TTP (ETH)
The main parameters are:
C2 Signal Label: Automatic (decided by the NE) or Equipped not specific
J1 Path Trace
1AA 00014 0004 (9007) A4 ALICE 04.10
The fields of the following figure appears:
Figure 151. High Order TP Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
192 / 448

Select the Transmission > TP Configuration option.
14.6.1.1 J1 Path Trace

If the Path Trace is 16 bytes long, the first byte is a CRC7 checksum calculated by NE.
If the Path Trace is shorter than 16 bytes, it is filled with zero bytes (0 hexadecimal).
Received fields is read only.
With the relevant button the operator can set the Expected field as:
TTI Enable
TTI Disable
TTI Repeated
The Transmitted field can be set with TTI Enable or TTI Repeated byte
Empty TTI button permits to send an all zeroes path trace.
To replace modified with the default, enter the default manually.
Click on Hex button, Figure 152. will be opened displaying in hexadecimal code the same value repored
in Trasmitted and Received field.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 152. J1 hexadecimal editor (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
193 / 448
Received and Expected fields are read only.

They can display the following number, according the G.707 recommendations for the C2 Signal Label:
0:
1:
2:
3:
4:
18:
19:
20:
21:
Unequipped
Equipped non-specific
TUG structure
Locked TU-n
Asynchronous 34/45MByte
Asynchronous 140MByte
ATM
MAN, DQDB
FDDI
In the Transmitted field it is possible to select the values:
Automatic: the C2 Signal Label value is automatically selected by the NE according the VC
structure;
Equipped not specific (it corresponds to number 1).
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
194 / 448

14.6.1.2 C2 Signal Label
14.6.2 J0 Section Trace management

Select RST block and then select Port> TP Configuration.

The fields of the following figure appears:
Figure 153. J0 Configuration

This function is implemented in order to manage the J0 Trace configuration.
This dialog shows the current values for received, expected and transmitted trail trace and it allows the
operator to change only the values of expected and transmitted trail trace.
The received trail trace is readonly.
Expected and Transmitted fields are editable by the operator.
With the relevant button it is possible to enable or disable TTI Monitoring.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on Hex button, Figure 154. will be opened displaying in hexadecimal code the same value repored
in Trasmitted and Received field.
Figure 154. J0 hexadecimal editor
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
195 / 448
This menu allows the operator to set the alarm thresholds for MST and VCi layer.
Select the MST or the VCi block.
Select the Transmission > TP Threshold Configuration option.
Figure 155. will be opened.
The user can select one of the two different Defect distribution:
Poisson distribution enable configuration of the Excessive Bit Error Ratio (ExBER on MST,
VCi) threshold and of the Signal Degrade (SD on MST, VCi) threshold of the TPs related
counted primitives.
Bursty distribution enable configuration of the maximum number of errored frames and the
total amount of bad block per frame.
ExBER Threshold : 103 to 105
Enable Consequent Actions : fixed to enabled
Signal Degrade Threshold : 105 to 109
Bursty Parameters Threshold : 1 or 10 or 100 or 1000
Bursty Parameters Consecutive Bad Seconds : 2 to 10
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 155. Degraded Signal Threshold selection
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
196 / 448

14.7 TP Threshold Configuration

14.8 Terminate / Disterminate TP

Select the Transmission > Terminate TP or Disterminate TP option.
Only one command in the menu is available, depending on whether a TP is terminated or not.
14.8.1 Terminate TP
Use this action to terminate a path. It can be performed on a AU-4 CTP.
A cross-connection between the selected AU-4 CTP (= aTP) and a modifiable VC-4 TTP (= bTP) is
created. Three TUG-3 and TU-3 are created if the modifiable VC-4 TTP was not already structured.
A cross appears in the icon of the terminated TP:
If the TP is already cross-connected a error message appears.

14.8.2 Disterminate TP
1AA 00014 0004 (9007) A4 ALICE 04.10
Use this action to disterminate a path. It can be performed on a AU-4 CTP. The related cross-connection
is deleted.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
197 / 448
14.9 Monitoring Operations

Select the Transmission > Monitoring Operations option as for the following figure.
Creation/Delation and Configuration options are present.
Figure 156. Monitoring Operations options menu

Monitoring Operations can also be accessed from the Port view menu.
The commands of this menu item are for the management of the POM, SUT, TCT e TCM functions (Path
Overhead Monitoring, Supervised Unequipped Termination and Tandem Connection
Termination/Monitoring; SUT functions is not operative in current release).
1AA 00014 0004 (9007) A4 ALICE 04.10
This command is available selecting the following object:
AU4 CTP (High order POM before and after matrix; TCM before and after matrix)
AU44c CTP (High order POM before and after matrix; TCM before and after matrix)
VC4 (TCT after matrix)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
198 / 448

14.9.1 Creation/Deletion
This dialog allows multiple object creation/deletion.
The dialog shown in the following Figure 157. opens:
Figure 157. Monitoring Operations Creation/Deletion

The Path Overhead Monitoring has the following configurable parameters:
Before Matrix
After Matrix
The Supervisory Unequipped Termination, NOT OPERATIVE in current release, has the following
parameters:
Sink (before matrix)

Sink (after matrix)
Source
Bidirectional
The Tandem Connection has the following configurable parameters:
1AA 00014 0004 (9007) A4 ALICE 04.10
Tandem Connections Monitoring (TCM):
TCM Before Matrix
TCM After Matrix

Tandem Connection Termination (TCT):
TCT Bidirectional Before Matrix
TCT Bidirectional After Matrix
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
199 / 448
When select and apply the Path Overhead Monitoring, the changes will be displayed in the Port View in
the following manner:
Figure 158. Display of POM and TCM in Port View (example)

When select and apply the Tandem Connection Monitoring / Tandem Connection Termination, the
changes will be displayed in the Port View in the following manner:
Figure 159. Display of POM ans TCM/TCT in Port View (example)
1AA 00014 0004 (9007) A4 ALICE 04.10
Also refer to para. 11.8 on page 142, about navigation to Monitoring View.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
200 / 448

Press Ok to apply the parameters or Close to close the dialog and discard the not with Ok applied
changes.

14.9.2 Configuration
Depending on the parameters selected in the Monitoring Operations Creation/Deletion dialog, not all
sections of the dialog are available.
NOTE: It is possible to open the POM and TCT/TCM Configuration dialog for a CTP even if neither
PathOverheadMonitor nor Tandem Connection was created before (SUT isnt available in this
release). No changes can be made in this case and the values displayed can be ignored.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 160. Monitor Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
201 / 448
Are available these following configurable parameters (see Figure 160. on page 201):

TTI Definition
The TTI (Trail Trace Identifier) has a maximum length of 16 characters.
The following TTI Definitions are available:
TTI Expected
TTI Received without the display
TTI Sent
The following TTI Types are available:
TTI Enabled
TTI Disabled
TTI Continuous
Error Distribution
Poisson or Bursty error distribution are managed.
TCM/TCT ConsActions
It is needed to support explicit consequent action activation (AIS insertion) for TCT sink and
bidirectional.
Thresholds
Set the thresholds of the following parameters:
Signal Degrade
Poisson mode only: from 105 to 109.
Excessive Error
Poisson mode only: fixed to 103 also if presented a selection from 103 to 105.
Bursty Degrade
Select a value between 1 and 8000 errors/sec for the Bursty Degrade threshold.
Bursty Consecutive
Select a value between 2 and 10 sec for the Bursty Degrade Consecutive.
Alarm Timing
Raising and Clearing Timing are not supported by OMSN.
Unequipped Trail
1AA 00014 0004 (9007) A4 ALICE 04.10
Not available.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
202 / 448

14.10 Loopback
The commands of this menu item are for the management of the loopback commands, for commissioning
or maintenance purposes.
14.10.1 Loopback Configuration
The loopbacks can be applied at line (external to equipment) level or at internal equipment level.
The loopback commands are used to separate the communication network into independent part checking
the line/equipment functionality during the network installation or maintenance operation.
The loopback architecture provides four configurations (see Figure 161. ):
Line Loopback And Continue

Line Loopback And AIS
Internal Loopback And Continue
Internal Loopback and AIS
Initial
Destination
Line
Internal
Destination
Line
Line Loop And Continue
Line Loop And AIS
Destination
AIS
Initial
Internal
Line
Initial
Internal loop And Continue
1AA 00014 0004 (9007) A4 ALICE 04.10
Initial
AIS
Line
Destination
Internal loop And AIS
Figure 161. Loopback configurations
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
203 / 448
Select a TP that supports the Loopback Configuration.
SDH board:
The loopback configuration can be done only on SDH ports with the acronym ending
with a N or a D letter (i.e. P4S1N, S41N, L41N, L42N, L162ND, etc.)
Line loopback performed on:
EIS for electrical STM1 SPI
OpS for optical STM1, STM4, STM16, STM64 SPI
Internal loopback performed on:
MsT TTP for STM1, STM4, STM16, STM64 ports
Select the Transmission > Loopback > Port Loopback Configuration option as for the following
figure.
Port Loopback Configuration can also be accessed from the Port view menu.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 162. Loopback options menu
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
204 / 448

Loopbacks act on the following TPs:

Figure 163. opens.
Figure 163. Port Loopbacks View
1AA 00014 0004 (9007) A4 ALICE 04.10
Choose the TP clicking on the Choose TP button.

Select the TP where to apply the loopback command. For the TP selection procedure, follow the TP
research description reported in para. 14.5.1 on page 185.
For this NE the Timed Loopbacks field is not managed and thus Start/Stop loopbacks time is not editable.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
205 / 448
To manage the loopback configuration select the Transmission > Loopback > Loopback
Management option as for the following figure.
Figure 164. Loopback options menu

Loopback Management can also be accessed from the Port view menu and from the Configuration
menu.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 165. on page 207 opens.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
206 / 448

14.10.2 Loopback Management

Figure 165. Loopback Management
1AA 00014 0004 (9007) A4 ALICE 04.10
The configured loopback are listed into the current loopbacks table. This table can be managed by the
Search criteria, Delete and Create commands.
Search Criteria (not operative): to configure the filter select the Loop and Continue type (Yes= Loop
And Continue, No= Loop And AIS) then select the Directionality Internal or Line and edit the Initial
TP Id (write: rack, subrack, board, port# and the TP type: EIS (SPI/PPI Electrical), OpS (SPI/PPI
Optical), MST and so on. For Initial TP has to be intended the outgoing signal while for Destination
TP the incoming signal. Enable the filter through the Toggle Filter Enable/Disable button. Click
on the Search button to start the configured loopback research into the current loopback table.
The Delete command permits to delete a loopback listed in the Current loopbacks Table: select a
loopback in the list and click on the Delete button.
The Create command permits to create a new loopback configuration: clicking on Create the
previous figure (Figure 163. on page 205) opens. Follow the previously paragraph indications to
create a new loopback configuration.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
207 / 448

The activated loopbacks are signalled in the Port view and in the Transmission view as for the following
figure:
TRANSMISSION VIEW
Active Loopback
PORT VIEW
Active Loopback
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 166. Display of Loopback action
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
208 / 448
14.11 Physical Media

Select the Transmission > Physical Media option as for the following figure.
Figure 167. Physical Media options menu

The Physical Media options permit to set physical configuration of each TP.
1AA 00014 0004 (9007) A4 ALICE 04.10
It opens a menu in which the various options will be available according the TPs type (for the option
common with the Port view reference is made to the relevant paragraph):
ED
01
ALS Management
Show Optical Configuration
TX Quality Configuration
Single Fiber Configuration
Extra traffic
Regeneration Section management
Line Length Configuration
Set Domain
HDSL Configuration
NT Configuration
X21 Configuration

Not operative.
Not operative.
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
209 / 448
This option is referred to the SECurity management and allows the user to set the Manager list and the
Access Control Domain of the selected TP.
Select the block: EIS for Electrical SDH port, OpS for Optical SDH port, P (PPI) for PDH port.
Select the Set Domain option from the Physical Media cascade menu to present the following view:
NML Assignement: each connected manager to the TP is highlighted in the list. The user can set
a manager clicking on the denomination.
Several manager can be enabled contemporaneously, having in charge the TP.
The Manager List contains the list of managers ( i.e. RM, SY, NPOS , EML) that work on the NE. The
EMLUSM administrator (SH or Craft Terminal) should set the Manager List only to remove a
manager in case of emergency (i.e. the Manager misses the NE connection).
Resource domain field allow to select the domain among that displayed in the list, assigning it to
the TP.
The different domains could be assigned to different operators.

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 168. Set Domain
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
210 / 448

14.11.1 Set Domain

14.12 Navigation Commands

14.12.1 Expand
Select the Transmission > Expand option as for the following figure.
Figure 169. Expand options menu
1AA 00014 0004 (9007) A4 ALICE 04.10
This menu item provides the possibility of displaying TPs that are related to the selected TP.
These may be TPs that are contained by the TP or TPs which belong to the physical port that is actually
connected to the TP.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
211 / 448
14.12.2 Hide

Select the Transmission > Hide option as for the following figure.
Figure 170. Hide options menu
1AA 00014 0004 (9007) A4 ALICE 04.10
This menu item provides the possibility of hiding all upper/lower TPs of a selected TP and the deletion of
a selected TP.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
212 / 448

14.12.3 Show Supported Board

Select the Transmission > Show Supported Board option.
This menu provides the possibility of navigating directly to the board that supports the TP.
The Board View appears (see following figure):
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 171. Board View (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
213 / 448
Select the Transmission > Navigate to Port View option.

This menu provides the possibility of navigating to the corresponding Port View related to the selected
TP in order to access a detailed overview of alarms quickly.
The Port View appears (see following figure):
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 172. Port View example
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
214 / 448

14.12.4 Navigate to Port View
1AA 00014 0004 (9007) A4 ALICE 04.10

15 CROSS-CONNECTION MANAGEMENT
15.1 Introduction
15.1.1 Overview
The purpose of this domain is to manage the connection of the high and low level path.
The following chapters provide the user with information concerning operations on cross-connections:
Para. 15.1.2 on page 216 Multiplex Structures for SDH

gives an overview on the SDH technology.
Para. 15.1.3 on page 219 Definition of Termination Points

gives an overview about the termination points implemented on the NE.
Para. 15.1.5 on page 224Cross-Connection Types

provides information concerning cross-connection types supported by the NE.
Para. 15.1.6 on page 225 Cross-Connection Protection

provides information concerning cross-connection protection supported by the NE.
Para. 15.2 on page 228 Operative sequence to execute Cross-Connections

lists the steps of the procedure to realize cross-connection.
Para. 15.3 on page 229 Cross-Connections Management

details the contents of the main cross-connections view.
Para. 15.4 on page 236 Create/Modify Cross-Connections

describes the creation and modification of cross-connections.
Para. 15.5 on page 253 Activate/Deactivate/Delete Cross-Connections

describes the activation, deactivation and deletion of cross-connections.
Activation and deactivation not supported in current release.
Para. 15.6 on page 254 Split and Join Cross-Connections

describes how to split or join bidirectional cross-connections.
Para. 15.7 on page 257 Protection Switching

deals with switching actions (force, manual, lockout protection) on cross-connections.
Para. 15.8 on page 259 Print

deals with printing out list entries on printers or into files.
Para. 15.9 on page 260 Show Cross-Connected TPs

describes the possibility of showing connections between two or more TPs of different different
hierarchies, e.g. connection between au4 and vc4.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
215 / 448
By introducing the Synchronous Digital Hierarchy (SDH), a standardized optical interface and a standard
management structure of transmission has been created. The Synchronous Digital Hierarchy (SDH)
signal structure contains an extended overhead as well as a fixed pointer controlled assignment of the user
signal elements, thus improving the possibilities of the network management.
Signals of the Synchronous and Plesiochronous Digital Hierarchy (PDH) are packed by synchronous
multiplexers into Virtual Containers (VC). The STM-1 signal structure is achieved by using the multiplex
structure complying with ITU-T and ETSI, (see Figure 173. on page 217). Each of the user channels
(2 Mbit/s, 34 Mbit/s, 45 Mbit/s and 140 Mbit/s) is packed into a container synchronous to the STM-1 frame
according to a predefined structure.
1AA 00014 0004 (9007) A4 ALICE 04.10
To adjust the plesiochronous signals to the synchronous network clock, certain filling algorithms are
available. Fix fill bits are inserted into synchronous signals. A byte column (9 Byte) as Path Overhead
(POH) is added to the Container (C) generated. Path Overhead and Container together form the Virtual
Container (VC). With the pointer pointing to the start of the VC, in respect of the STM-1 frame, an
Administrative Unit (AU) or if several Containers of a group are to be combined a Tributary Unit (TU)
is generated. Several TUs form a Tributary Unit Group (TUG) and TUGs again can be combined into a
VC. The AU of the signal, together with the Section Overhead (SOH), finally make up the STM-1 frame.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
216 / 448

15.1.2 Multiplex Structures for SDH
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 173. SDH Multiplex Structure according to ITU-T G.709
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
217 / 448
C11
VC11
VC12
C12
2 Mbit/s
(1,5 Mbit/s)
VC2
C2
6 Mbit/s
VC3
C3
C4
(45 Mbit/s)
34 Mbit/s
140 Mbit/s
TU11
TU12
TU2
TU3
x3
x1
x1
x4
TUG2
x7
TUG3
x7
VC3
x3
VC4
C
VC
TU
TUG
AU
x1
x3
STM1
xN
not implemented
Pointer -Processing
: Container
: Virtual Container
: Tributary Unit
: Tributary Unit Group
: Administrative Unit
Legenda:
AU3
AU4

STMN
The STM-1 frame consists of:

a Section Overhead (SOH)
an AU Pointer area
a payload area

270 Columns (Bytes)

9
270
1
Section Overhead
SOH
3
4
9 rows
AU Pointer
Payload
Section Overhead
SOH
9
Figure 174. Frame Construction within the Synchronous Digital Hierarchy

The STM-1 frame has a basic bit rate of 155.520 Mbit/s. A single user channel is packed into a Virtual
Container. These Virtual Containers are of different size and may be nested or packed differently.
Virtual Containers for the European bit rates:
the STM-1 frame contains a VC-4

a VC-4 may contain one C-4 or three TUG-3
each TUG-3 may contain one VC-3 or seven TUG-2
each TUG-2 contains three VC-12 or one VC-2
1AA 00014 0004 (9007) A4 ALICE 04.10
An STM-1 user signal can be constructed of:
either 1 x VC-4
or 3 x VC-3
or 2 x VC-3 + 7 x VC-2
or 2 x VC-3 + 21 x VC-12
or 1 x VC-3 + 14 x VC-2
or 1 x VC-3 + 7 x VC-2 + 21 x VC-12
or 21 x VC-2
or 14 x VC-2 + 21 x VC-12
or 7 x VC-2 + 42 x VC-12
or 63 x VC-12
STM-N signals are constructed by integer multiples of the basic signal STM-1 of 155.520 Mbit/s. For
example an STM-16 signal of 2.488.320 Mbit/s is generated by combining sixteen STM-1 signals byte
interleaved.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
218 / 448
15.1.3 Definition of Termination Points (TP)

When ports are depicted on the user interface, the following abbreviations are used.
This section concerns the multiplex structure (see Figure 173. on page 217) as well as on the information
model of object-oriented programming which was used when forming the user interface. As a rule, a
Termination Point (TP) is the starting and terminating point of a transmission segment. A distinction is
made between the following types of TPs:
CTP (Connection Termination Point)

The CTP represents the termination of a connection. The transmission signal is terminated, i.e.,
the received signal is monitored and the error signaling evaluated, while own-code signaling is
inserted in the transmitted signal.
TTP (Trail Termination Point)

The TTP represents the termination of a transmission segment. The signal is monitored and passed
on after modification in one form or another.
Both TP types exist on the SDH level and the PDH level.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
CTPs on SDH level

On SDH level (see Figure 175. on page 221) a distinction is made between the following CTPs:
AU-4 (Connection Termination Point)

The AU-4 CTP represents both the creation and termination of an STM-1 connection. The
High-order Connection Supervision (HCS) function is included.
TU-x (Connection Termination Point), i.e. TU-12 CTP, TU-2 CTP, TU-3 CTP.
The TU-x CTP represents both the creation and termination of a VC-x connection. The
Low-order Connection Supervision (LCS) function is included.
CTPs on PDH level

On PDH level (see Figure 176. on page 222), a distinction is made between the following CTPs:
E4 (Connection Termination Point)

The E4-CTP represents the nonintrusive monitoring of incoming 140 Mbit/s PPI.
S4 (Connection Termination Point)

The S4-CTP represents the nonintrusive monitoring of outgoing 140 Mbit/s PPI .





The E1-CTP represents the nonintrusive monitoring of incoming 2 Mbit/s PPI. The
Mon.(Monitoring) label indicates that is possible to enable the CRC4 control signal.

The S1-CTP represents the nonintrusive monitoring of outgoing 2 Mbit/s PPI . The
Mon.(Monitoring) label indicates that is possible to enable the CRC4 control signal.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
219 / 448
TTPs on SDH level
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
ES (Electrical Section TTP)

An ESTTP displays the physical characteristics of a port with electrical access (level and code
monitoring and conversion).
OS (Optical Section TTP)

An OSTTP displays the physical characteristics of a port with optical access (level and code
monitoring and conversion).
RST (Regenerator Section TTP)

An RSTTP displays the creation and/or termination of an RSOH (Regenerator Section
Overhead), i.e., rows 1 to 3 of the first 9xN columns of an STM-N frame.
MST (Multiplexer Section TTP)

An MSTTP displays the creation and/or termination of an MSOH (Multiplexer Section
Overhead), i.e., rows 5 to 9 of the first 9xN columns of an STM-N frame.
VC-4 (Trail Termination Point)

A VC-4 TTP represents both the creation and termination of a VC-4 path.
TTPs on PDH level

On PDH level (see Figure 176. on page 222) a distinction is made between the following TTPs:
PPI (Trail Termination Point)

On the PDH side, an PPITTP corresponds to the ESTTP of the synchronous side. Depending
on the type, it can either display the characteristics of a 140 Mbit/s, a 45MBit/s, a 34 Mbit/s or
a 2 Mbit/s port.
E4 (Trail Termination Point)

The E4-TTP represents the creation and/or termination of a 140 Mbit/s connection.

The E3-TTP represents the creation and/or termination of a 34 Mbit/s connection.

The E2-TTP represents the creation and/or termination of an 8 Mbit/s connection.



MSP definition
Transmit side, the MSNP (AU4CTP) input enters two different MSNP/MSN (unProtected CTP)
sources and then the MSNTTP working and protection sources (to insert the K1K2 bytes) are sent
to the own SPI interfaces. Receive side, the working and protection MSN/MSNP outputs (AU4CTP)
enter in the switching selector. The MSNPTTP terminates the selected signal and checks the SSF
and the MSP protocol failure.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
220 / 448

On SDH level (see Figure 175. on page 221) a distinction is made between the following TTPs:

$%&
'
,

()
()
()
)
(*
(*
(*
(*
(*
(*
(*
*
+*
+*
+*
NOT USED
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 175. SDH Transport Level Diagram
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
221 / 448
.,#%
+-,%
$
$
$)*
*,%
),%
$)+
$)

$)
$+
)
)
$*
$*
$+
+*

+*
$+
+*
"

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 176. PDH Transport Level Diagram
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
222 / 448

!

15.1.4 Mapping Tables: TP Names

The TP names on the 1670SM reflect the software model the user interface is based on. Therefore they
differ from the TP names given in the ITU-T recommendations.
The following tables list the TP names mapping conventions in the Transmission View.
Table 2. TP names on 1670SM (1)

1AA 00014 0004 (9007) A4 ALICE 04.10
Table 3. TP names on 1670SM (2)

ED
01

!
!

SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
223 / 448
The NE supports unidirectional, bidirectional and broadcast connections unprotected as well as protected.
By means the cross connection selections it is possible to configure the SNCP protection.
In addition it permits Drop and Continue connections.
15.1.5.1 Unidirectional Connection
Information is transmitted exclusively from the input port to the output port (point-to-point); there is no
routing in reverse direction.
input TP
output TP
Figure 177. Unidirectional Connection

15.1.5.2 Bidirectional Connection
Information is transmitted between input port and output port in both directions (point-to-point).
input TP
output TP
Figure 178. Bidirectional Connection
15.1.5.3 Broadcast Connection (Multi-leg / Multipoint)

In contrast to a cross-connection between just two points (point-to-point), one source and one sink, a
broadcast connection consist of one source and several sinks, different legs that share the same source
TP.
In the example below, information is broadcast from one input to outputs A, B and C on three legs.
output A
input TP
leg 1
leg 2
leg 3
output B
output C
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 179. Example of Broadcast Connection with Three Legs
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
224 / 448

15.1.5 Cross-Connection Types

A warning box indicates when the resources available for broadcast connections are exhausted.
Note: Non-intrusive Monitoring
Adding a protection leg to a unidirectional cross-connection offers the ability to perform
non-intrusive monitoring on this cross-connection. No errors are introduced to the original
cross-connection with applying or removing the protection leg.
15.1.6 Cross-Connection Protection
15.1.6.1 Protected Unidirectional Connection
A unidirectional connection is routed from Input A to the Output (primary route). In the case of a failure,
the system automatically switches to the protection path from protection Input B to the Output. This second
connection is permanently kept in hot standby operation (see Figure 180. ).
input A
prot.
input B
output TP
in case of
failure
Figure 180. Protected Unidirectional Connection

15.1.6.2 Protected Bidirectional Connection
A bidirectional connection is routed from Input A to the Output C (primary route). Input A (input protected
see Figure 181. ) can be protected:
in case of
failure
Figure 181. Bidirectional Connection Input Protected
1AA 00014 0004 (9007) A4 ALICE 04.10
Note: By means of this connection are created links with SNCP protection.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
225 / 448
The protected broadcast is realized as a set of independent, protected, unidirectional connections using
the same pair of input termination points, as illustrated in Figure 182. Each protection can be forced,
locked out or switched independently. Therefore, if a failure occurs at a certain input, it is possible that only
some of the protections of the protected broadcast actually switch to the protection input.

/
#
#

Figure 182. Protected Broadcast

Figure 182. shows a broadcast connection from input A to outputs A, B and C. Leg 2 and 3 are protected
via input B, whereas leg 1 is not protected.
15.1.6.4 Drop and Continue Connection
A Drop and Continue connection is a composed by (see Figure 183. ):
a unidirectional broadcast connection routed from Input A to the Output C and to Output B
a unidirectional connection from Input protecting B to Output C
a unidirectional connection from Output C to Input A
Output C is protected; when receive from Input main the connection is defined normal, when receive
from Input Protecting main the connection is defined inverse.
All the connections are created in a single step of configuration.
Input
Prot. input
Output
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 183. Drop and Continue Normal
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
226 / 448

15.1.6.3 Protected Broadcast Connection
15.1.6.5 Drop and Continue Insert Connection

An example of Drop and Continue Insert Connection is presented in Figure 184.

The connections are created in a double step of configuration: two cross connection will be presented,
composed in the following way:
First connection:
a unidirectional broadcast connection routed from Input A to Output B and C
Second connection:
a protected unidirectional connection routed from Input C to Output A, with protecting Input B
Input
Prot. input
Output
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 184. Drop and Continue Insert Connection
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
227 / 448
This paragraphs list the complete procedure to realize cross-connection moving among the various
menus.
15.2.1 Procedure for high order signal (AU4)
Select Transmission option from the View menu.
Select Transmission Cross Connection Cross Connection Management.
Click on Create in the Cross Connection Management windows; a new window called Main Cross
Connection is opened.
Select the correct value in the fields Type and Protection
Click on Choose relative to the Input field; a new window called TP search is opened.
On the Equipment field select the Board, in the Termination Points field select AU4
Click on OK; the TP search window is closed.
In the Main Cross Connection window repeat the same on the Output field and on the Prot. Input
field for protected connections.
Click on OK in the Main Cross Connection window to terminate the creation and subsequently
click on Cancel to go to the Cross Connection Management window.
Click on Search in the Cross Connection Management window to see the new crossconnection
created.
15.2.2 Procedure for AU4 concatenated (AU44c, AU416c, AU464c)

Note: Before to create an AU4 concatenated crossconnection is necessary to define that the AU4s on
a STM4 or STM16 or STM64 board are concatenated as explained in para. 11.4 on page 126.
Select Transmission option from the Views menu.
Select Transmission Cross Connection Cross Connection Management.
Click on Create in the Cross Connection Management window; a new window called Main Cross
Connection is opened.
Select the correct value in the fields Type and Protection
Click on Choose relative to the Input field; a new window called TP search is opened.
1AA 00014 0004 (9007) A4 ALICE 04.10
On the Equipment field select the Board, in the Termination Points field select the
concatenated AU44c (syntax example: r01sr1sl25/port#01#01AU4P4c )
Click on OK; the TP search window is closed.
In the Main Cross Connection window repeat the same on the Output field and on the Prot. Input
field for protected connections.
Click on OK in the Main Cross Connection window to terminate the creation and subsequently
click on Cancel to go to the Cross Connection Management window.
Click on Search in the Cross Connection Management window to see the new crossconnection
created.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
228 / 448

15.2 Operative Sequence to execute Cross-Connections

15.3 Cross-Connections Management

A list of cross-connections can be displayed in the Cross-Connection Management dialog (see
The dialog can be accessed via the Transmission or Port view or via Configuration menu as shown in
the following figures.
Transmission view is presented with the Views Transmission pull down menu.
Port view is presented with the Views Equipment pull down menu, then clicking on the presented
objects with the sequence rack > subrack > board > port.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 185. Port Crossconnection options menu
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
229 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 186. Transmission Crossconnection option menu
Figure 187. Configuration Crossconnection options menu
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
230 / 448

The Cross-Connection Management dialog is initially empty (see Figure 188. on page 232).
A list of the cross-connections is displayed in the Cross-Connection Management dialog after selecting
the Search command.
There are two possibilities of displaying a list of cross-connections:
do not enter any search criteria and press the Search button to display a list of all existing
cross-connections;
enter Search Criteria (one or more) and then press the Search button to display a selection of
cross-connections. Set Ignore for attributes not to be used as filtering criteria.
Use button Cancel Search to cancel an active search request or close the dialog.
15.3.1 Search Criteria

The following Search Criteria are available on the top side of the Cross Connection Management view
(Figure 188. on page 232).
Name (not supported in current release)

Number of the crossconnection (automatically assigned).
ACD (not supported in current release)

Enter the Access Control Domain of the relevant cross-connections: E= connection made with
1353SH, M= connection made with 1354RM, empty= connection made with CT.
This filter option can only be used, if at least one ACD is defined on the NE and one or more
cross-connections are assigned to this ACD(s).
Type
Select the connection type:
Unidirectional
Bidirectional
Multipoint
Drop&Continue
Protection
Select protection functionality:
1AA 00014 0004 (9007) A4 ALICE 04.10
Protected
Not protected
TP Class
Select one of the TP types involved in the requested cross-connection.
State
Select the connection state:
ED
Activated
Deactivated (not operative, the connection state is always Activated)
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
231 / 448
Prot. State
Select the protection state (automatic and operators commands)
Forced to Input
Forced to Protecting
Manual Switch to Input
Manual Switch to Protecting
Auto. Switch to Input
Auto. Switch to Protecting
Lockout
Normal I
Normal P
TP ID Prefix
Enter the TP type and physical location of the port, or only the physical location at least down to board
level, according to the following format:rack
r<rack#>sr<subrack#>sl<slot#>/port#<port#>-TP (see Figure 189. on page 234)
1AA 00014 0004 (9007) A4 ALICE 04.10
The # within brackets identifies a number.
Figure 188. Cross-Connection Management Dialog (Initial State)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
232 / 448


15.3.2 Cross-Connection List

After a successful search, a read only list of cross-connections matching the search criteria appears
(see Figure 189. on page 234). The number of matching cross-connections is displayed in the upper left
corner of the list. The list contains information concerning the following parameters for each
cross-connection:
Prot. State
detailed switching information in the format:
<protection state> <traffic ind> (<location>:<signal state><switch status>,
[<location>:<signal state><switch status>])
<protection state>
Normal, Auto, Lockout, Forced or Manual
<traffic ind>
indicates the location of current traffic:
P (Protecting input) or I (Input)
<location>
indicates the location of the errored signal:
P (Protecting input) or I (Input)
<signal state>
indicates the signal state: SD (Signal Degrade) or SF (Signal Failure)
<switch status>
status of the switch:
c (completed) or p (pending)
Example:
Auto I (P:SD-c)
There has been an Automatic switch from the protecting input to the Input where the traffic is
currently located. The reason for the automatic switch was Signal Degrade in the Protecting input.
The switch was completed.
State
connection state indicating whether cross-connection is A(ctivated) or D(eactivated)
Dir.
Direction-related connection type:
uni(directional), bi(directional) or mp (multipoint)
Input
signal source; contains the TP type and physical location of the port according to the format

Protecting Input
protecting source (for protected cross-connections only); contains the TP type and physical location
of the port according to the format
1AA 00014 0004 (9007) A4 ALICE 04.10

ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
233 / 448
Output
signal destination
for point-to-point cross-connections, the TP ID of the destination is specified according to the format
r<rack#>s<subr.#>b<board#>/port#<port#>-TP ; for
multi-leg cross-connections, the
string multipleLegs appears instead.
At the bottom of the dialog is a range of buttons to start actions on the listed cross-connections. Before
starting any action apart from creation or printing, mark at least one cross-connection.
To mark several cross-connections (multi-select) that are listed in succession, select the first
cross-connection of a block with a mouse click and the last one with a mouse click while pressing the
<Shift> key.
Or, mark a number of individual cross-connections by clicking the mouse button while pressing the
<Control> key.
Deselect cross-connections by clicking on the respective row while simultaneously pressing the <Control>
key. To deselect a number of cross-connections at a time, press the <Shift> key and hold it down while
moving the mouse pointer to the last entry.
1AA 00014 0004 (9007) A4 ALICE 04.10
All actions that may affect traffic must be confirmed. A confirmation dialog pops up in this case and the
user has to confirm the requested action.
Figure 189. Cross-Connection Management Dialog (After Search)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
234 / 448

15.3.3 Actions available

The following actions are available on the bottom side of the Cross Connection Management view:
Create a crossconnection (see para. 15.4 on page 236)

The Main Cross-Connection dialog (see Figure 195. on page 244) is opened.
Modify a Cross-Connection (see para. 15.4 on page 236)

Available if just one cross-connection is selected from the list. The Main Cross-Connection dialog
(see Figure 195. on page 244) is opened.
Activate a Cross-Connection (see para. 15.5 on page 253)

Available if at least one cross-connection is selected from the list. Not operative in current release.
Deactivate a Cross-Connection (see para. 15.5 on page 253)

Available if at least one cross-connection is selected from the list. Not operative in current release.
Delete a Cross-Connection (see para. 15.5 on page 253)

Available if at least one cross-connection is selected from the list.
Split a Cross-Connection (see para. 15.6.1 on page 256)

Available if at least one bidirectional cross connection is selected from the list.
Join two Cross-Connections (see para. 15.6.2 on page 256)

Available if two cross connections are selected. Not operative in current release.
Protection Switching (see para. 15.7 on page 257)

Available if exactly one protected cross-connection is selected from the list. The Protection Actions
dialog is opened.
Print (see para. 15.8 on page 259)

Prints the filtered list of cross-connections.
1AA 00014 0004 (9007) A4 ALICE 04.10
The dialog has to be closed explicitly.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
235 / 448
Creation and modification of cross-connections are performed in the Main Cross-Connection dialog. The
dialog can be accessed via the Transmission or Port view as for the following menus example or by using
the Create or Modify buttons (para. 15.3.3 on page 235) in the Cross-Connection Management dialog
(see Figure 188. on page 232).
The dialog box of Figure 195. on page 244 is presented (Main Cross Connection view).
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 190. Port Crossconnection options menu
Figure 191. Transmission Crossconnection options menu
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
236 / 448

15.4 Create/Modify Cross-Connections
1AA 00014 0004 (9007) A4 ALICE 04.10

To prevent operation faults, the system is designed according to the following guidelines:
All operations that may affect traffic must be confirmed. The subsystem provides a confirmation
dialog box before the operation can be executed.
If the window displays an existing cross-connection, the OK button is insensitive when this
cross-connection is assigned to NML or it is not assigned to the user profile.
If the window is used to create a new cross-connection, the system verifies that the relevant TPs can
be used (not assigned to NML and assigned to the user profile) after the OK button is pressed. If a
specified TP is not permitted, the corresponding message box appears.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
237 / 448
15.4.1 Cross-Connection Parameters
A cross-connection is defined through a set of parameters which depend on the connection and protection
type. Only those parameters which are permitted within the current context can be accessed. All others
are disabled (faded gray).
To create a cross-connection, one or more of those parameters must be defined according to the
cross-connection type. Table 4. on page 240 gives an overview about the optional and mandatory input
parameters for the various cross-connection types. Activate the relevant entry boxes first of all by clicking
on them with the mouse.
Configurable Parameters
Type
Select the connection type:
Unidirectional
Bidirectional
Drop&Continue
D&C Topology
Select the direction for Drop&Continue:
Normal
Inverse
Protection
Define protection state:
Protected
Not Protected
Prot. Criteria (only available for protected connections)

Clicking on the Prot. Criteria button, Figure 192. on page 239 for the Protection Criteria dialog is
opened, where the user can display and configure the SNCP type Protection. No protection criteria
for automatic protection switching can be configured.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following SNCP type are available:
ED
SNCPI : Inherently monitored SubNetwork Connection Protection
SNCPN : Nonintrusively monitored SubNetwork Connection Protection
SNCPS : Sublayer SubNetwork Connection Protection (not operative in current release)
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
238 / 448

The Main Cross Connection view of Figure 195. on page 244 permits to create the cross connections.

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 192. Protection Criteria
Revertive (available only for protected connections)

Select whether protection is to be revertive or not.
In Revertive mode, a protected service is switched back to its initial, protected element when the fault
has been eliminated.
When Revertive mode is active, the Wait To Restore protection period prevents several protection
switches being initiated as a result of an intermittent failure. The protected element must be error-free
during this defined period of time before a protected service is switched back to it.
The Wait To Restore time period is fixed to 5 minutes.
In Non-revertive mode, switchover to the protecting element is maintained even after the fault has
been eliminated.
HOT (available only for protected connections)

To enter the Hold Off Time expressed in ms with a range from 0 to 10.000.
HOT is the time between declaration of Signal Degrade or Signal Fail, and the initialization of the
protection switching algorithm.
Input
To enter the input TP, click the relevant Choose button and select the TP in the TP Search dialog
(see Figure 142. on page 186). Otherwise, select the input field and enter the name of the TP directly.
Prot. Input
To enter the protecting TP, click the relevant Choose button and select the TP in the TP Search
dialog. Otherwise, select the input field and enter the name of the TP directly.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
239 / 448
Output
It is possible to enter one or more output TPs.
To enter one output TP, click the relevant Choose button and select the TP in the TP Search dialog.
Otherwise, select the input field and enter the name of the TP directly.
To enter more than one output TP and create a broadcast connection, proceed as described
previously and press button Add Leg afterwards. The previously chosen TP is then moved to the
list box located below. Click the Choose button and select the next TP in the TP Search dialog.
Otherwise, select the input field and enter the name of the TP directly. Repeat this procedure for each
destination TP. A list of all the selected output TPs is displayed in the list box located below it.
To delete a leg from the list, select the TP in the list box and click on the Delete Leg button.
Note: Non-intrusive Monitoring
Adding a protection leg to a unidirectional cross-connection offers the ability to perform
non-intrusive monitoring on this cross-connection. No errors are introduced to the original
cross-connection with applying or removing the protection leg.
Table 4. Optional and Mandatory Configurable Parameters for Cross-Connection Creation

12

%

%3

" !
4&

'33
!

!
&

5

" "
5

5

" !

" "
5

3

Non-configurable Parameters
CC Topology
1AA 00014 0004 (9007) A4 ALICE 04.10
The topology of the cross-connection is indicated via two icons. The left-hand icon displays the
current topology and the right one displays a view of the topology following confirmation of the current
modifications.
In addition, the color of an icon indicates the connection state of the cross-connection:
green > active
brown > inactive
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
240 / 448


The icon is set according to the entries made in Type and Protection (see examples in the following
figure):
TPs not cross-connected
Unidirectional, not protected
Bidirectional, not protected
Unidirectional, protected
Bidirectional, protected
Broadcast, not protected
Broadcast with one protected leg
Drop & Continue normal
Drop & Continue inverse
Loopback connection:
unidirectional, same input and output TP
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 193. Cross Connection icons
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
241 / 448
current state:
TPs are not connected

Example:
state after creation:

unidirectional, non-protected cross-connection
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 194. Creation of a Unidirectional, Non-Protected Cross-Connection
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
242 / 448

15.4.2 Create a Cross-Connection

This chapter lists the steps the user has to take to create a cross-connection using the Main Cross
Connection view of Figure 195. on page 244 and Figure 196. on page 245.
For a detailed description of the single parameters, refer to the previous para. 15.4.1 on page 238.
For information on cross-connection types, refer to para. 15.1.5 on page 224.
Note:
After creation of a cross-connection, the cross-connection list in the Cross Connection

Management dialog is not automatically updated. Use button Search in this dialog to update
the list.
Create a Point-to-Point Cross-Connection (uni- or bidirectional)

1)
Select the cross-connection Type.
2)
Select the Protection state.
3)
Select or type in the Input TP.

To enter the TP, click the Choose button and select the TP in the Search for Cross Connection
Input dialog (see Figure 197. on page 247), or select the input field and enter the name of the
TP directly.
The Search for Cross Connection Input dialog offers the possibility to list TPs according to
different filter criteria. E.g. to obtain a list of all not connected AU-4 TPs of a rack, first select the
rack in the right list box, then select the filter criteria ConnectionState not connected and
Class AU-4 and click on button Search. The matching TPs are listed in the right listbox. Select
the input TPs in the list and confirm with Ok.
For a more detailed description on the Search for Cross Connection dialog see para. 14.5.1
on page 185.
4)
Select or type in the Output TP as described in Step 3 ).
The following steps only apply to protected cross-connections:

5)
Select or type in the Protecting Input (Prot. Input) TP as described in Step 3 ).
6)
Configure the Revertive mode.
7)
Configure the Protection Criteria (Prot. Criteria)
8)
Configure the HOT (Hold Off TIme)
1AA 00014 0004 (9007) A4 ALICE 04.10
Press the button Ok to confirm the creation.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
243 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 195. Create a Bidirectional Protected Cross-Connection (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
244 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 196. Create Drop&Continue connection (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
245 / 448

1)
Select the cross-connection Type unidirectional
2)
Select the Protection state.
3)
Select or type in the Input TP.

To enter the TP, click the Choose button and select the TP in the Search for Cross Connection
Input dialog (see Figure 197. ), or select the input field and enter the name of the TP directly.
The Search for Cross Connection Input dialog offers the possibility to list TPs according to
different filter criteria. E.g. to obtain a list of all not connected AU-4 TPs of a rack, first select the
rack in the right list box, then select the filter criteria ConnectionState not connected and
Class AU-4 and click on button Search. The matching TPs are listed in the right listbox. Select
the input TPs in the list and confirm with Ok.
For a more detailed description on the Search for Cross Connection dialog see para. 14.5.1
on page 185.
4)
Select or type in the Output TPs as described in Step 3 ).
Press the button Add Leg in the Main Cross Connection dialog (Figure 195. on page 244) and all
output TPs are displayed in the list box under the output field.
To delete a leg from the list, select the TP in the list box and click on the Delete Leg button.
The following steps only apply to protected broadcast connections:
5)
Select or type in the Protecting Input TP. Note that each single protected leg of the broadcast
has to be assigned to the same protecting input.
Proceed as described in Step 3 ). Afterwards, select the protected output TP in the output list box
and click button Protect Leg. The leg is then marked as protected in the list box. Repeat this
procedure for each protected output TP (only one protected leg is supported in current release).
To unprotect a leg from the list, select the protected TP in the list box and click on the Unprotect Leg
button.
Examples are in Figure 198. on page 248 and Figure 199. on page 249.
6)
Configure the Revertive mode.
7)
Configure the Protection Criteria (Prot. Criteria)
8)
Configure the HOT (Hold Off TIme)
1AA 00014 0004 (9007) A4 ALICE 04.10
Press the button Ok to confirm creation.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
246 / 448

Create a Broadcast Connection
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 197. Search for Cross-Connection (example for output)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
247 / 448

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 198. Create an Unprotected Broadcast Cross-Connection (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
248 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 199. Create a Protected Broadcast Cross-Connection (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
249 / 448

When modifying a cross-connection, note that some of the transformations involved may affect traffic
(because the system may have to destroy and re-create the cross-connection to perform the necessary
transformation). As mentioned at the beginning of this chapter, the user is required to confirm operations
affecting traffic, i.e. a confirmation window warns the user.
Within the Main Cross Connection dialog, modification of a cross-connection is restricted to the
protection state and the parameters required by the protection.
Refer to Table 5. on page 250 for an overview of the accessible parameter when the protection state has
been changed from not protected to protected and vice versa. For a description of the parameters,
please refer to the previous para. 15.4.1 on page 238.
To modify a cross connection select one from the connection list of Figure 189. on page 234. and then click
on the Modify button.
Note:
After modification of a cross-connection, the cross-connection list in the Cross Connection

Management dialog is not automatically updated. Use button Search in this dialog to update
the list.
Table 5. Modificable Parameters

12

4&
'33
!

!
&
1AA 00014 0004 (9007) A4 ALICE 04.10

5
ED

%
3

5

5
5
5
5
5
5

%
3

5

5

5

01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
250 / 448

15.4.3 Modify a Cross-Connection
The following few facts should be taken into consideration when modifying connections.
1AA 00014 0004 (9007) A4 ALICE 04.10

From Unprotect to protected cross-connection

When a protected cross-connection is being unprotected (protection changed to not protected), the
dialog displays the additional option button Unprotected.
It offers the choice of whether to keep the protected input TP (Input) or the protecting input TP (Prot.
Input) as the only signal source of the new unprotected cross-connection. Ensure that the active TP
is selected (i.e. check the protection state in the Cross-Connection Management dialog).
An example is in the following Figure 200.
In addition, a question box appears, asking the user to confirm the unprotect action.
Figure 200. Unprotect a Unidirectional Protected Cross-Connection (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
251 / 448
When an unprotected cross-connection is being protected, the Prot. Input field is available to select
the protection input connection to insert.
An example is in the following Figure 201.
1AA 00014 0004 (9007) A4 ALICE 04.10
Protection principle are given in para. 15.1.6 on page 225.
Figure 201. Protect an Unidirectional Unprotected Connection (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
252 / 448

From Protect to unprotected cross-connection

15.5 Activate/Deactivate/Delete Cross-Connections

15.5.1 Activate a Cross-Connection
Not supported in current release.
The Cross Connection Management dialog provides the possibility of displaying a selection of existing
cross-connections (see Chapter 15.3 on page 229). The connection state (Act = A or D) is indicated in this
connection list.
To activate a cross-connection, select one from the connection list (see Figure 189. on page 234) and then
click on the Activate button to initiate the process. A confirmation box appears in which to confirm the state
change request. The connection in the list is automatically updated to indicate the new connection state
(Act = A).
If the set of cross-connections selected from the list includes both activated and deactivated
cross-connections, clicking the Activate button only initiates actions on the deactivated
cross-connections which were selected.
15.5.2 Deactivate a Cross-Connection
Not supported in current release.
After creation, a cross-connection is automatically in an active state. To deactivate a cross-connection,
select one from the connection list (see Figure 189. ) and then click on the Deactivate button to initiate
the process. A confirmation box appears in which to confirm the state change request. The connection
in the list is automatically updated to indicate the new connection state (Act = D).
If the set of cross-connections selected from the list includes both activated and deactivated
cross-connections, clicking the Deactivate button only initiates actions on the activated
cross-connections which were selected.
15.5.3 Delete a Cross-Connection
Only deactivated cross-connections should be deleted. However, deletion of active cross-connections is
possible.
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE: the Delete crossconnection action is not possible in the case that is still
existing any operation/connection/termination on the underlying supported signals, such as:
Performance Monitoring on lower or higher TPs
POM / HPOM operations
Lower order Connections
Higher order Connections
Lower/Higher order Path Terminations
Loopbacks
LAN/LAPD (and any comm/routing channel)
Auxiliary channels
Thus the deletion of every active operation/connection/termination is necessary, in the same order as
above listed, before the deletion of a crossconnection.
To delete a cross-connection, select the corresponding connection from the list and click on the Delete
button. To prevent operation errors, the user must confirm the deletion request.
The deleted cross-connection automatically disappears from the connection list when the operation is
successful.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
253 / 448
15.6.1 Split a Cross-Connection

Precondition
Only bidirectional cross-connections can be split.
Split
Select one or more bidirectional cross connections from the list in the Cross Connection Management
dialog and press Split. The cross-connections are split without further confirmation from the user.
The original cross connection(s) disappear from the list in the Cross Connection Management dialog
after a successful action. The user has to press Search to see the new cross connections.
Depending on the protection state of the original cross-connection, the split action has the following effect:
a)
Unprotected Cross-Connection
An unprotected bidirectional cross-connection is split into two unidirectional cross-connections with
the input TP in one of them being the output in the other and vice versa (see Figure 202. ).
The new cross connection has the same name and activation status as the old bidirectional one.
6
7
+8

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 202. Split/Join Unprotected Bidirectional Cross-Connection
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
254 / 448

15.6 Split and Join Cross-Connections

b)
Protected Cross-Connection
Splitting a protected connection results in one protected unidirectional cross-connection and one
broadcast with two legs. The input of the original cross-connection is one of the legs in the broadcast.
The other leg in the broadcast is the protecting input. The input of the broadcast is the output of the
original protected cross-connection.
6
7
*8

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 203. Split/Join to Protected Bidirectional Cross-Connection
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
255 / 448
15.6.2 Join Two Cross-Connections
Two cross-connections can be joined if they match the following characteristics:
The connections are either

1)
both unprotected, unidirectional and the input is the output of the other one, or
2)
one of them is protected and unidirectional, and the other one a broadcast with two legs.
Restriction: the input of the broadcast connection has to be the output of the protected
connection and the legs of the broadcast match the input and the protection input of the
unidirectional connection, also refer to Chapter Split a Cross-Connection, effect b).
Both cross-connections have the same connection state (activated or deactivated).
Both cross-connections have the operational state enabled, i.e. they are listed in black color in the
Cross Connection Management dialog.
Join
Select exactly two cross connections in the Cross Connection Management dialog and press the Join
button. The cross-connections are joined without further confirmation from the user.
The original cross connection(s) disappear from the list in the Cross Connection Management dialog
after a successful action. Press Search to see the new cross-connections in the list.
The result is either a bidirectional (case 1, see Figure 202. ) or a protected bidirectional (case 2, see
Figure 203. ) cross-connection.
1AA 00014 0004 (9007) A4 ALICE 04.10
If the original cross-connections have different names, the new name is a concatenation of the names of
both of them.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
256 / 448

Precondition

15.7 Protection Switching

The Protection Actions dialog is displayed after clicking on the Protection button in the Cross
Connection Management dialog (see Figure 189. on page 234).
Users can only switch protection on cross-connections belonging to them and not assigned to the NML.
A second condition is that protection is enabled for the cross-connection concerned (protection parameter
is set to protected).
The three protection actions Force, Lock Out and Manual Switch belong to different levels, whereby
Lock has the highest priority and Manual Switch the lowest.
Note that a protection state can only be changed within the same or from a higher priority level, e.g. Force
To Protecting can be reverted with Release but not with Manual Switch To Input.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 204. Protection Actions Dialog
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
257 / 448
Force to Input
The cross-connection is switched to the protected input regardless of signal quality. Automatic
protection is disabled.
Force to Protecting (Input)

The cross-connection is switched to the protecting input regardless of signal quality. Automatic
protection is disabled.
Release Force
Forced switching is disabled and automatic protection switching re-enabled.
Manual Switch to Input (not operative in current release)

The user can switch over to the protected input manually. Switching over is not executed if the signal
quality on the protected path is worse than on the protecting path.
Manual Switch to Protecting Input (not operative in current release)

The user can switch over to the protecting input manually. Switching over is not executed if the signal
quality on the protecting path is worse than on the protected path.
Release Manual Switch (not operative in current release)

A manual switch is disabled and automatic protection switching re-enabled.
Lock Out to Invoke

The connection path is locked for protection switching, i.e. neither forced nor manual switching can
be performed.
Release Lock Out

The protection lock is disabled.
Note: All the operations listed are context-dependent and are enabled or disabled (grayed) accordingly.
After completion of protection switching, the list entry in the Cross Connection Management dialog is
updated automatically.
1AA 00014 0004 (9007) A4 ALICE 04.10
After clicking on an action button and completing the action initiated, the dialog disappears automatically.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
258 / 448

The dialog window enables the user to perform protection- related operations on protected
cross-connections. These are:

15.8 Print
This option is used to print the currently filtered cross-connection list and the related filter settings on the
default printer ( Figure 205. ) or to a file in postscript or ASCII format ( Figure 206. ).
Figure 205. Select Printer
1AA 00014 0004 (9007) A4 ALICE 04.10
Note: If no printer is installed, there is no error message displayed to indicate this.
Figure 206. Select Output Format for file
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
259 / 448
An overview of signal flow can be requested by means of a user action. The user can select a TP and
initiate the action Show Cross Connected TPs from the Transmission view.
Figure 207. Transmission Crossconnection options menu

The result is that all other TPs connected to the currently selected TP are displayed (see the example of
Figure 208. on page 261). A line indicates the connection .
1AA 00014 0004 (9007) A4 ALICE 04.10
This functionality should only be applied selectively (either for a single TP or selected group of TPs).
Expanding and hiding TPs that are associated with the currently selected TP enables all the related TPs
to be added to the view so that the complete signal flow can be illustrated.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
260 / 448

15.9 Show Cross-Connected TPs
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 208. Show Cross Connected TP
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
261 / 448

1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
262 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10

16 OVERHEAD MANAGEMENT
16.1 Introduction
The purpose of this set of dialogs is to handle the operations on the Overhead (OH) bytes of the NE.
The possible operations are:
Overhead crossconnection
Crossconnection between 2 or more OH bytes
Termination of an OH byte onto an auxiliary port or vocal channel
Total Passthrough of the MSOH bytes for some cards
Definition of the Phone Parameters
There is a TP associated to every OH byte and to every auxiliary port, so TP could be used instead of OH
bytes or auxiliary port, depending on the context.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
263 / 448
16.2 OH Connection overview

Here are described the possible OH connections.

For OH Phone Parameters directly refer to para. 16.7 on page 274.
OH Crossconnection
The operator has to be able to crossconnect two or more OH bytes on two different boards.
The possible crossconnection types is:
unprotected bidirectional point to point
The steps an operator has to do in order to perform the crossconnection are the following:
create the OH TPs involved in the operation

create the OH crossconnection:
select type of crossconnection
select first OH TP involved in the operation
select second OH TP involved in the operation
After having deleted an OH crossconnection, the involved TPs have to be deleted.
OH Termination
The operator has to be able to terminate one OH byte onto an auxiliary port or vocal channel.
The steps an operator has to do in order to perform the OH bytes termination are the following:
create the OH TP involved in the operation

create the OH byte termination:
select the created OH TP
select the auxiliary port/vocal channel TP involved in the operation
After having deleted an OH byte termination, the involved TP have to be deleted.
Total MSOH Passthrough
For STM ports it make sense to allow the operator to perform a total passthrough of the MSOH bytes.
A total MSOH passthrough connection (connection between msPassThroughCTP points) is setup only
if no single MSOH passthrough connection are set and if no single msoh crossconnection are set. If a
total MSOH passthrough connection is set, a single MSOH passthrough connection or a single MSOH
crossconnection cannot be set.
The steps an operator has to do in order to perform the total MSOH passthrough are the following:
create the msPassThroughCTP points involved in the operation

create the total MSOH passthrough:
select the first msPassThroughCTP point involved in the operation
select the second msPassThroughCTP point involved in the operation
1AA 00014 0004 (9007) A4 ALICE 04.10
After having deleted a total MSOH passthrough, the involved msPassThroughCTP points have to be
deleted.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
264 / 448
16.3 Overhead views

The Overhead Views allows to perform the previously presented operations.

To access select Overhead option from the Configuration pull down menu; the following options are
presented in the cascading menu, as shown in the following figure:
OH Cross Connection See para. 16.4 on page 266
OH Phone Parameters See para. 16.7 on page 274
OH TP creation
OH TP deleting
Figure 209. Overhead options
1AA 00014 0004 (9007) A4 ALICE 04.10
The options are described in next paragraphs.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
265 / 448
Select the Configuration pull down menu. Select the Overhead option and then from the cascading menu
the OH Cross Connection option.
The Cross-Connection Management for OverHead dialog opens (see Figure 210. ) and allows to start
the configuration.
Figure 210. Cross Connection Management for OverHead dialog
1AA 00014 0004 (9007) A4 ALICE 04.10
It is the similar to dialog used for the crossconnection of the TP for paths, then the same
description and functions are valid.
Next configuration steps use the Main Cross-Connection for OverHead (see Figure 211. on page 267)
dialog and the TP Search dialog (see Figure 142. on page 186), also in this case already described for
path management.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
266 / 448

16.4 OH Cross Connection

Figure 211. Main CrossConnection for OverHead dialog

For all details, navigation and sequences on these views refer to chapter 15 on page 215.
There is one big difference between the OH TPs and the other kinds of TPs: the OH TPs have to be:
created ONLY BEFORE a crossconnection/termination operation involving them has been

performed;
deleted AFTER a crossconnection/termination deleting involving them has been confirmed.
The current implementation of the TP Search Dialog (TPSD) works only with created TPs.
In the following a description of the main functions and commands is given, also to list the Supported and
Not Supported operation.
16.4.1 Cross-Connection Management for OverHead dialog
See Figure 210. on page 266.
Supported operations
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Search cross connections/terminations according to one or more of the following filtering

attributes: name, type, class or one of the TPs involved. The operator can set the filtering
criteria, can start the search and select one or more crossconnections/terminations among
those presented in a readonly list as a result of the search operation. For each cross
connection/termination matching the filtering criteria, the following information is shown: type
and the names of the involved TPs; for multileg crossconnections a generic string, such as
multileg, is presented instead.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
267 / 448
Delete the selected crossconnection/termination

go to the Main Cross Connection for OverHead dialog and modify the existing
crossconnection/termination
Note: this dialog disappears only when the user explicitly clicks on the close button.
Delete operations can be performed on several crossconnections/termination at the same time.
Modify operations can be performed only on single crossconnections/terminations.
The OH crossconnections are automatically active at the moment of their creation.
The operation buttons availability follows some rules:
The Delete and Print buttons are enabled only if at least one item is selected from the list.
A special dialog will ask the user for a confirmation.
The modify button is enabled if one (and only one) item is selected. It brings up the Main
crossconnection dialog.
The create button is always enabled. It brings up the Main crossconnection Dialog.
When some operation may affect the existing traffic, the operator is warned about that, and a confirmation
dialog must be answered to carry on/cancel the operation. The choices for this dialog are: yes/no for
single items, yes to all/cancel for multiple items.
Not Supported operation
When used for OH purposes, the Cross-Connection Management dialog doesnt support the following
functionalities:
Protect cross connections/terminations: all the OH crossconnections/terminations are

unprotected;
Activate/Deactivate crossconnections/terminations: all the OH crossconn/terminations are

automatically active since their creation;
Split cross connection/termination;
Modify Cross Connection Termination.
16.4.1.1 Main Cross-Connection for Overhead dialog

See Figure 211. on page 267.
According to the philosophy of offering only meaningful operations to the user, and being the OH
crossconnection operations a subset of those applying to the general cross connections (e.g.:protections
are not allowed), some fields of this dialog are disabled.
1AA 00014 0004 (9007) A4 ALICE 04.10
By clicking on the proper portions of the dialog and on the proper buttons, the operator can perform the
operations hereafter listed:
selection of the crossconnection type
selection of the first TP involved in the crossconnection
selection of the second TP involved in the crossconnection
In order to do that the operator can either type in the involved TPs ID or use the TP Search dialog.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
268 / 448

After choosing one or more crossconnections/terminations, this dialog allows to:
Supported operations

When creating a new cross connection, some or all of the following operations are available,
depending on the NE type characteristics:
Choose one input TP
Choose one output TP

It is possible to directly type in the TP name or to click on the Choose button to select a
TP from the TP Search dialog box.
When modifying an existing cross connection, the same operations are available. Some
changes, may be trafficaffecting, as they may imply a temporary cross connections
destruction. In these cases a proper dialog box forces the user to confirm the operation. In the
proper part of the dialog, an icon shows the icon of the selected existing cross connection. For
OH handling, these icons cannot be used to change the topology.
16.4.1.2 TP Search dialog

The TP Search dialog (see Figure 142. on page 186) currently offers:
navigation rack/subrack/board/port
a list of TPs to choose from
When used in the OH domain, this dialog is a subcase of the most generic TP Search.
1AA 00014 0004 (9007) A4 ALICE 04.10
The operator can choose among a list of:
ED
all the possible OH TPs belonging to a specified class: no board selected and MS, RS or VC
class selected;
all the possible OH TPs belonging to a specified board/port: board/port selected and no TP class
selected;
all the possible OH TPs belonging to a specified board/port and class: board/port selected and
MS, RS or VC class selected;
all the OH TPs already connected (also accordingly to the connection type);
all the OH TPs not yet connected;
a combination of the above options.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
269 / 448
the auxiliary and vocal channels TPs are in the SERVICE board of slot 20
The auxiliary channels are:
2 x G.703 2 Mbit/s; in the screen are indicated as:
r01sr1sl11/port#01P
Expanding
this
TP,
31
referred
TPs
are
presented
r01sr1sl11/port#02#11e0CTP to r01sr1sl11/port#02#131e0CTP
from
r01sr1sl11/port#03P
r01sr1sl11/port#04P
r01sr1sl11/port#05P
r01sr1sl11/port#06P
4 x V.11; in the screen are indicated as:
r01sr1sl11/port#01#01v11TTP
4 x V.24; in the screen are indicated as:
1 x phonic interface (voice channel); in the screen are indicated as:
1AA 00014 0004 (9007) A4 ALICE 04.10
from
4 x G.703 64Kbit/s; in the screen are indicated as:
r01sr1sl11/port#01P
Expanding
this
TP,
31
referred
TPs
are
presented
r01sr1sl11/port#01#11e0CTP to r01sr1sl11/port#01#131e0CTP
r01sr1sl11/port#01#01q23TTP
Expanding this TP, four referred TPs are presented:
These TPs permit to connect the voice channel toward four directions.
The other boards used to terminate or crossconnect the OH bytes are the STMn boards.
The OH TP are present in MS, RS and VC4 TP Class.
In these TPs the indication ......#0011 to 0099 (MS or RS) are referred to the coordinates of the
Section OverHead bytes on the SDH frame (1,1 to 9,9).
The voice channel are identified by the ow indication, the FU is for Future Use, the NU is for
National Use, UC is for User Channel and Pass is for Passthrough channel.
The examples of the figure in this OH connection chapter can be helpful to the operator.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
270 / 448

In this Network Element to connect the auxiliary / vocal channels and the Overhead bytes the
following operative indication must be observed:

16.5 OH TP creation
the OH TP creation option.
The OH TP creation dialog opens (see Figure 212. ) and allows to create the OH TP to cross connect.
In detail, the dialogbox contains the following graphical object:
a Choose button is used to display a list of OH Tps to be created. The Choose button
starts the TP Search (see Figure 213. on page 272) with predefined filtering; the TP
Search dialog allows the operator to visualize only not created OH Tps.
To visualize the OH TP in the TP Search view double click on the MS, RS or VC4 Tp.
OH Tp field displays the label of the selected OH Tp to be created.
Apply button is used to perform a create request of the tp displayed in the OH Tp field. After having
performed the create request, the OH Tp field is set to empty.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 212. OH TP creation
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
271 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 213. OH Search TP for creation
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
272 / 448

16.6 OH TP deleting
the OH TP deleting option.
The OH TP deleting dialog opens (see Figure 214. ) and allows to delete the OH TP no more involved
in an OH crossconnection.
In detail, the dialogbox contains the following graphical object:
a Choose button is used to display a list of OH Tps to be deleted. The Choose button starts
the TP Search with predefined filtering; this TP Search dialog allows the operator to visualize
only created and not crossconnected OH Tps.
OH Tp field displays the label of the selected OH Tp to be deleted.
Apply button is used to perform a delete request of the tp displayed in the OH Tp field. After having
performed the delete request, the OH Tp field is set to empty.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 214. OH TP deleting
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
273 / 448
The OH phone parameters option permits to configure the telephone number and to manage the
parameter phonic extension.
the OH Phone Parameters option.
Figure 215. opens.
Figure 215. Phone Parameters dialog window

In the window are presented:
The interface field (at the top) where can be selected the phonic interfaces to be configured.
It identifies a TP indicated as q23TTP, referred to the physical voice connection on the SERVICE
unit in slot 20.
The phone number field, to set the telephone number for operator call on the phonic interface.
The phonic extension field, where enable or disable the extension of the selected phonic interface.
If enabled the phonic signal is extended towards the external on the access panel of the NE.
Apply button performs the configuration change of the modified phone parameters of the selected phonic
interface without close the dialog.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
274 / 448

16.7 OH Phone Parameters

17 PERFORMANCE MONITORING MANAGEMENT

17.1 Introduction
The Performance Monitoring domain on the NE covers the monitoring of counter values for trail
termination points and connection termination points.
Examples of these counters on the SDH port are Errored Seconds (ES) and Severely Errored Seconds
(SES).
The Performance Monitoring domain counts these errors during specified granularity periods (15 min,
24h) and stores the values in history data logs.
For the purpose of quality supervision, the values of the error counters can be compared to user-defined
threshold levels. If a counter value has crossed a threshold level, a notification (Threshold Crossing Alarm)
is issued.
The principle performance management functions are:
Configuration of the counting interval for each performance measurement point.
Collection of the performance data.
Configuration of the quality thresholds that generate alarms and log records when predefined values
are exceeded.
1AA 00014 0004 (9007) A4 ALICE 04.10
On the ETHERNET port a set of performance counters are foreseen for QoS and maintenance purpose.
By selecting the GMAU TP and subsequently the Transmission > Performance menu, the following
options are available:
Configure Performance Monitoring
Display Current Data
Display Maintenance Counter
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
275 / 448
17.2.1 Overview
Performance Monitoring functionalities are described in the following paragraphs in addition to general
information concerning performance monitoring on the NE:
Para. 17.4 on page 287 Configuration deals with the configuration of performance monitoring.
Para. 17.5 on page 291 Display Current Data deals with displaying current performance data.
Para. 17.6 on page 294 Display History Data deals with displaying history performance data.
Para. 17.7 on page 297 PM Threshold Table Selection deals with the selection of threshold tables.
Para. 17.8 on page 300 PM Threshold Table Modification/Display deals with the modification of
threshold tables and permits ro display the same.
17.2.2 Supported Performance Counters

The NE uses performance counters to count transmission errors.
A set of performance counters is provided according to the Termination Point (TP), where performance
measurement occurs.
The user can start performance monitoring on one or more subsets of counters for each TP; it is not
possible to start individual performance counters.
Near end performance monitoring events are:
Background Block Error (BBE): A BBE counter measures the number of errored blocks which do
not occur as part of an SES.
Errored Second (ES): A one second period with one or more errored blocks or with a defect.
Severely Errored Second (SES): A one second period which contains 30% of errored blocks for
STM64 / STM16 ( 25% for STM4 and 15% for STM1), or at least one defect Severely
Disturbed Period (SDP). An SES is also counted as an ES (see Table 6. on page 277).
Near End Unavailable Second (NEUAS): An Unavailable Second is a second which is part of the
Unavailable Time.
1AA 00014 0004 (9007) A4 ALICE 04.10
The corresponding Far End (FE) performance monitoring events are:
Far End Background Block Error (FEBBE): A far end errored block which does not occur as part
of an FESES.
Far End Errored Second (FEES): Identifies, at a terminal, a one second period with one or more
errored blocks or with a defect which were received by the Far End Terminal.
Far End Severely Errored Second (FESES): Identifies, at a terminal, a one second period which
contains 30% of errored blocks for STM64 / STM16 ( 25% for STM4 and 15% for STM1),
or at least one defect Severely Disturbed Period (SDP) which was received/detected by the Far End
Terminal. An FESES is counted as an FEES (see Table 6. on page 277).
Far End Unavailable Second (FEUAS): An Unavailable Second is a second which is part of the
Unavailable Time at the far end.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
276 / 448

17.2 Performance Monitoring on SDH port
The Termination Point (TP) type determines which performance monitoring events can be counted:

SDH TPs
Both near end and far end counters are supported in receive direction of the signal for all SDH path
layers and for the multiplex section layer. For the regenerator section, no far end information is
transmitted and, therefore, only near end counting is supported.
PDH TPs
Only near end counters are supported in receive direction for all PDH path layers.
Further definitions:
Errored Block (EB): A block in which one or more bits associated with the block are erroneous.
Remote Error Indicator (REI) [formerly Far End Block Error (FEBE)]: Identifies, at a terminal, the
count of errored blocks that were received by the far end terminal.
Remote Defect Indicator (RDI) [formerly Far End Receive Failure (FERF)]: indicates to a terminal
that the far end terminal has detected an incoming failure.
Unavailable Time (UAT): A period of unavailable time begins at the onset of 10 consecutive SES
events. These 10 seconds are considered to be part of unavailable time. A new period of available
time begins at the onset of 10 consecutive non-SES events.
Pointer Justification Event (PJE): A PJE is an inversion of I or D bits of the pointer, together with
an increment or decrement of the pointer value to signify a frequency justification.
Out of Frame Second (OFS): An OFS is defined as a second in which one or more out of frame
events have occurred. This event is identified by the A1/A2 byte of the SDH Frame.
The counting of OFS is only supported for the regenerator section termination. Please note that this
counter is deprecated by ETSI and will be removed from international standards.
Table 6. SES thresholds: number of errored blocks to declare SES
1AA 00014 0004 (9007) A4 ALICE 04.10
Near End
ED
STM1
STM4
STM16
STM64
MS
15%
25%
30%
30%
RS
30%
30%
30%
30%
CTP (VC4)
30%
Far End
STM1
STM4
STM16
STM64
MS
15%
25%
30%
30%
CTP
30%
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
277 / 448
Far end performance monitoring parameters are derived from Remote Defect Indicators (RDI) and
Remote Error Indicators (REI) (refer to following figure).
Node B
Node A
Source
Sink
transmission
signal
significant bits
significant bits
far end
defect
RDI insertion
Sink
near end
defect
near end
counter
far end
counter
far end
defect
significant bits
near end
defect
far end
counter
near end
counter
RDI insertion
Source
significant bits
transmission
signal
Figure 216. Far End Performance Monitoring Principles
At Node A, the near end information represents the performance of the unidirectional section/path
from B to A, while the far end information represents the performance of the unidirectional
section/path from A to B.
At Node B, the near end information represents the performance of the unidirectional section/path
from A to B, while the far end information represents the performance of the unidirectional
section/path from B to A.
Near end performance data at Node A and far end performance data at Node B correspond as long as
neither direction is disturbed, and vice versa.
1AA 00014 0004 (9007) A4 ALICE 04.10
In compliance with ETSI and ITU-T standards, far end errors cannot be counted in the case of near end
failures.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
278 / 448

17.2.3 Far End (FE) and Near End (NE) Performance Counting

17.2.4 Bidirectional counting (24 h Bi) for QoS

As specified in G.826, G.784 and ETSI 300417, the bidirectional PM collection for Quality of Service has
been supported by combining the information on each direction of transport to assess a single
unavailability state: the bidirectional path is in the unavailable state if either one or both directions are in
the unavailable state.
PM data are collected by a single UAS plus two sets of three event counters (BBE, ES, SES) for NEPM
and FEPM respectively. When the path transports unidirectional payload just the four counters for the
NEPM are activated (BBE, ES, SES and UAS).
Data collection is performed only on 24 hours registers and the NE maintains a buffer of two registers: the
24hours current registers and the historical one.
17.2.5 End to End (ee 24h) Performance Counting

VCn trails can be monitored in intermediate node through the activation of performance monitoring
process on Monitoring function.
As the trails are often responsible of the endtoend customer service, the end toend monitoring can be
requested to provide monitoring for Quality of Service purposes and, in addition, for network Maintenance
applications.
End to end monitoring is achieved by activation of Performance monitoring on the two direction of path
and using farend primitives. This process is bidirectional.
The bidirectional process needs the presence on the two Monitoring functions in the two directions in one
NE and among the two monitoring function a 24 hour collection can be activated with the collection of
incFE_BBE, incFEES, IncFESES, UAS, eFEBBE, eFEes, eFESES.
17.2.6 Performance Monitoring on AUPJE

AU PJE (Administrative unit point justification event) is an optional parameters request in G.784.
For AU PJE counters, the positive and negative PJE shall be counted separately on one selectable AU
within an STMN signal, after the AU has been resynchronized to the local clock. Refer to G.783.
The number of positive and negative outgoing PJE per second are collected in 15 minutes and 24 H
counters. A history of 16 x 15minutes counters and 2x 24H are stored in the NE for each AU selected.
1AA 00014 0004 (9007) A4 ALICE 04.10
No Threshold crossing mechanism is supported on AUPJE counters.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
279 / 448
TCM allows monitoring within the operator domain. The quality within the operators own domain can be
proven regardless of the received quality of the signal at the entry point of the network. At the input point
the reference value is set to zero by using the TCM feature.
Tandem Connection Monitoring is applicable to VC4nc (n=1, 4, 16, ...), VC4, VC3 and VC12 layers.
TCM provides:
Incoming error count (IEC)

TC_REI to indicate errored blocks within the TC to the far end
OEI to indicate errored blocks of the egressing VCn
TC_API as access point identifier complying with generic 16byte string format
TC_RDI indicating to the far end that defects have been detected within the TC at the near end TC
sink
17.2.8 Performance Data Collection

Near end and far end performance monitoring events are counted over fixed monitoring periods of 15
minutes and 24 hours.
The 24-hour monitoring periods start at 00 : 00 (UTC) and the 15-minute monitoring periods start at
xx : 00, xx : 15, xx : 30 and xx : 45.
Performance monitoring can be enabled and disabled at any time during a monitoring period. An entity
of all near end or far end performance monitoring events is always counted, it is not possible to start
individual performance counters (e.g. SES only). BBE, ES and SES counting is stopped during
Unavailable Time.
Event Counting
The performance events (e.g. SES) are counted in a counter per event. These counters are called the
current registers. At the end of the monitoring period, the contents of the current registers are transferred
to the first of the recent registers, together with a time stamp to identify the period (including the day). Time
stamping is performed using UTC (as for all alarms). After that, the current register is reset. It is also
possible to reset an individual current register manually.
Suspect Flag
A suspect interval flag is set as an indication that the data of the corresponding register may be either
incomplete or invalid.
Zero Suppression
Zero suppression is a basic mechanism to remove irrelevant PM information and to reduce the amount
of PM reports in the system. A PM report is suppressed and hence no history record is created by the entity
which is responsible for PM reporting when all of the following conditions are true for the monitoring period:
1AA 00014 0004 (9007) A4 ALICE 04.10
an interval is error-free (all PM counter values are zero)

PM was enabled during the entire monitoring interval (the elapsed time equals its nominal value, i.e.
900 for 15 min. and 86400 for 24 h)
PM was running properly (the suspect interval flag is not set)
By default, zero suppression is active for all PM enabled TPs. The number of suppressed intervals is
indicated.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
280 / 448

17.2.7 Tandem Connection Termination (TCT) and Monitoring (TCM)

17.2.9 Data Collection

Note: PM data is not counted on boards that were plugged out at the moment of enabling data
collection (see PM Configuration dialog). Nevertheless, PM data is counted on boards that were
plugged in at the moment of enabling data collection, but were plugged out and back in some time
during data collection.
Performance Monitoring can be started at any time.
As soon as Performance Monitoring is started on the Craft Terminal, current PM data is collected on the
I/O boards, incrementing the performance counters each time an error is detected.
The performance data counted is evaluated every quarter of an hour or every 24 hours and stored there
in a history record.
When the user disables the monitoring of a TP within the first 10 minutes of a 15-minute period, it is
possible that have still not been received the PM data of the previous monitoring interval.
Since PM data is not stored after monitoring is disabled, the PM data of the previous interval is lost in this
case.
If equipment or line protection switching occurs during a counting interval, the NE does not provide
complete performance measurement for the protected TPs.
Only the period between the last switch and the end of the counting window is counted.
The interval is marked for suspect data and the elapsed time indicates the length of the measured period.
17.2.10 Performance Monitoring History
Performance Monitoring history data is necessary to assess the recent performance of transmission
systems. Such information can be used to sectionalize faults and to locate the source of intermittent errors.
History data, in the form of performance monitoring event counts, is stored in registers in the NE. All the
history registers are time stamped.
In compliance with ETSI and ITU-T standards, the history registers operate as follows.
The history data is contained in a stack of registers. There are sixteen 15-minute period registers and one
24-hour period registers per monitored event. These registers are called the recent registers. At the end
of each monitoring period, the contents of the current registers are moved to the first of the recent registers.
When all recent registers are full, the oldest information is discarded.
17.2.11 Thresholds
For quality supervision purposes, the recorded errors through the performance counters can be compared
to threshold levels. If a counter value has crossed a threshold level, a Threshold Crossing Alarm (TCA)
is transmitted to the alarm manager.
The threshold values are defined in threshold tables together with a severity and a flag indicating whether
crossing this value should be notified by an alarm and logged or only stored in the current problem list.
The user can modify and delete such tables.
1AA 00014 0004 (9007) A4 ALICE 04.10
Different thresholds can be assigned for near end and far end and for granularity of 15 minutes and 24
hours.
The TCA only reports the value of the counter which has crossed the threshold, it does not provide a
complete set of all counters. Therefore, the user has to explicitly retrieve all current performance data after
receiving the alarm. The user can retrieve this information from the Current Performance Management
Data Dialog.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
281 / 448
For 24hour monitoring periods, one threshold value is defined: if the event count reaches or
exceeds the threshold value during the monitoring period, a TCA is generated. To clear a TCA, the
alarm must be manually acknowledged by the user.
For 15minute monitoring periods, two threshold values (set, reset) are defined:
a TCA is generated during the monitoring period when the event count reaches or exceeds the set
threshold value the first time. This TCA is automatically cleared by the system at the end of the
following monitoring period in which the event count is less than or equal to the reset threshold value
and there was neither an unavailable nor a suspect period during this monitoring period
The following limitations apply for explicit clearance:
The value of the low threshold is fixed to 0 (only a single threshold is provided by a threshold table).
An SES threshold crossing is cleared at the end of the interval if no unavailability was detected and
SES had not reached the low threshold (low threshold equal to 0).
Even in case of a suspect interval the TCA is cleared if no unavailability was detected and the low
threshold had not been reached.
1AA 00014 0004 (9007) A4 ALICE 04.10
Additionally an explicit clearance of TCAs for all granularity periods is executed if one of the following
events occurs during the current interval:
deletion of the current data instance (TP)
resetting of counters (only for 24 h)
increased thresholds (higher than current value of counters) (only for 24 h).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
282 / 448

The system behavior concerning the clearance of 15 min. and 24 h TCAs differs:
17.3 Performance Monitoring on ETHERNET port

Performance Monitoring on Ethernet port are described in the following paragraphs:
Para. 17.9 on page 304 Configuration deals with the configuration of performance monitoring.
Para. 17.10 on page 305 Display Current Data deals with displaying current performance data.
Para. 17.11 on page 307 Display History Data deals with displaying history performance data.
An Ethernet link can be defined between two Gigabit Ethernet interfaces (for this NE).
At the terminations of Ethernet link, it is possible to monitor the Ethernet frames and to collect information
about the Ethernet traffic by means of some counters.
Definitions of incoming and outgoing counter direction
Incoming (network centric view): it refers to the direction starting from Ethernet domain toward
SDH domain (see Figure 217. ). The traffic arrives to the board from an Ethernet link and goes
out from an SDH link.
Outgoing (network centric view): it refers to the direction starting from SDH domain toward
Ethernet domain (see Figure 217. ). The traffic arrives to the board from an SDH link and goes
out from an Ethernet link.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 217. Counter directionality: network centric view
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
283 / 448
Ethernet counters can be distinguished from different points of view as depicted in Figure 218. on page
284.
They can be:
physical interface counters

aggregate counters
flow counters
At physical interface level, the working status of transceiver is controlled.

At aggregate level, all Ethernet traffics passing through the same port can be viewed as an aggregate.
At flow level, each single flow is managed.
Besides this classification, some counters can be of Quality of Service, others only of maintenance.
Figure 218. Counter subdivision
17.3.2 Ethernet physical interface counters
1AA 00014 0004 (9007) A4 ALICE 04.10
Ethernet physical interface counters are used to test Ethernet interface working state.
They are:
Symbol Error : for an interface operating at 100 Mb/s, the number of times there was as invalid data
symbol when a valid carrier was present. For an interface operating in fullduplex mode at 1000 Mb/s,
the number of times the receiving media is nonidle carrier event for a period of time equal or greater
than minFrameSize, and during which there was at least one occurrence of an event that causes the
PHY to indicate Data reception error on the GMII. The count represented by an instance of this object
is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier
event. This count does not increment if a collision is present.
Media Available Exits : number of times that ifMauMediaAvailable for this MAU instance leaves the
state available. Discontinuities in the value of this counter can occur at reinitialization of the
management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
Jabber State : number of times that mauJabberState for this MAU instance enters the state jabbering.
This counter will always indicate zero for MAUs of type dot1MauTypeAUI and those of speeds above
10 Mb/s. Discontinuities in the value of this counter can occur at reinitialization of the management
system, and at other times as indicated by the value ifCounterDiscontinuityTime.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
284 / 448

17.3.1 Overview

False Carrier : number of false carrier events during IDLE in 100BASEX and 1000BASEX links.
For all other MAU types, this counter will always indicate zero. This counter does not increment at
the symbol rate. It can increment after a valid carrier completion at a maximum rate of once per 100
ms for 100BASEX and once per 10s for 1000BASEX until the next CarrierEvent. Discontinuities
in the value of this counter can occur at reinitialization of the management system, and at other times
as indicated by the value of ifCounterDiscontinuityTime.
They are only maintenance counters.

17.3.3 Aggregate counter
Aggregate counters count frames that pass through the same port. Single flows are hidden inside the
aggregate.
Aggregate counters are (refer to Figure 219. on page 285):
TRCO (Total Received Correct Octets): total number of octets of Ethernet frames received correctly
by the Virtual Ethernet Interface, including Ethernet header characters.
TRCF (Total Received Correct Frames): total number of Ethernet frames received correctly by the
Virtual Ethernet Interface.
TRSEF (Total Received Service Errored frames): it is the sum of three contributions.
TTO (Total Transmitted Octets): total number of octets of Ethernet frames transmitted out by the
Virtual Ethernet Interface, including Ethernet header characters.
TTF (Total Transmitted Frames): total number of Ethernet frames transmitted out by the Virtual
Ethernet Interface.
TDF (Total Discarded Frames): total number of Ethernet frames which were chosen to be discarded
due to buffer congestion.
They are Quality of Service counters.
TTO incoming
TTF incoming
TRCO outgoing
TRCF outgoing
TTO outgoing
TTF outgoing
TRCO incoming
TRCF incoming
TRSEF incoming
Node A
SDH VCn
pipe
TRSEF outgoing
Node B
Transmitted
frames
Received
frames
ISA Eth/GbE port
ISA Eth/GbE port
1AA 00014 0004 (9007) A4 ALICE 04.10
TDF incoming
TDF outgoing
OMSN
OMSN
Incoming direction
Outgoing direction
Eth > SDH
SDH >Eth
Figure 219. Ethernet aggregate counter
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
285 / 448
Flow frames can be coloured Red Green or Yellow depending if flow is in compliance or not with SLA
parameters.
So flow counters definitions take in consideration frames colours.
1AA 00014 0004 (9007) A4 ALICE 04.10
Counters definitions are:
TRCO_G (Total Received Correct Green Octets): total number of octets of green Ethernet frames
received correctly, including Ethernet header characters.
TRCF_G (Total Received Correct Green Frames): total number of green Ethernet frames received
correctly.
TRCO_Y (Total Received Correct Yellow Octets): total number of octets of yellow Ethernet frames
TRCF_Y (Total Received Correct Yellow Frames): total number of yellow Ethernet frames received
correctly.
TRCO_R (Total Received Correct Red Octets): total number of octets of red Ethernet frames
TRCF_R (Total Received Correct Red Frames): total number of red Ethernet frames received
correctly.
TDF_G (Total Discarded Green Frames): total number of green Ethernet frames which were chosen
to be discarded due to buffer congestion.
TDF_Y (Total Discarded Yellow Frames): total number of yellow Ethernet frames which were chosen
to be discarded due to buffer congestion.
TTO_G (Total Transmitted Green Octets): total number of octets of green Ethernet frames
transmitted out, including Ethernet header characters.
TTF_G (Total Transmitted Green Frames): total number of green Ethernet frames transmitted out.
TTO_Y (Total Transmitted Yellow Octets): total number of octets of yellow Ethernet frames
transmitted out, including Ethernet header characters.
TTF_Y (Total Transmitted Yellow Frames): total number of yellow Ethernet frames transmitted out.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
286 / 448

17.3.4 Flow counter
17.4 Configuration on SDH port

Use menu item Add TP to display a special TP in the Transmission menu (see para. 14.5 on page 185).
Select the TP and open the PM Configuration dialog (see Figure 221. on page 289) by clicking on the
menu item Performance>Configure Performance Monitoring from Transmission pull down menu.
Figure 220. Performance options menu (1)

This PM Configuration dialog serves as the main interface to all PM services. Every
configuration of all monitoring intervals is defined using this dialog.
It is possible to access the same PM Configuration dialog selecting a TP in the Port view and opening
the same Performance > Configure Performance Monitoring option in the Port pull down menu (see
chapter 11 on page 121).
1AA 00014 0004 (9007) A4 ALICE 04.10
Note: to configure PM for AU4 CTPs and TUx CTPs, Path Overhead Monitoring (POM) or
Supervised Unequipped Termination (SUT, not supported) or Tandem Connection (TCT, TCM) must
be created first (see description in para. 14.9 on page 198).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
287 / 448
The selected TP is indicated in the first box at the top of the screen: TP Identifier.
In case of AU4 CTP and TUx CTPs, the PM Configuration dialog also contains a cascading menu that
allows to configured the POM/SUT/TC options as follow (see Figure 221. on page 289):
PathOverhMon After Matrix

PathOverhMon Before Matrix
TP (Performance is made on AUPJE)
TCM After Matrix
TCM Before Matrix
When more than one of the above options is chosen, a Question dialog box is displayed; click on Cancel
to continue or OK to interrupt any action.
Note: As long as the PM Configuration dialog is open, a modified POM/SUT/TC configuration is not
automatically recognized and displayed. This may lead to rejections or confirmations of forbidden
PM configuration. Therefore make sure to reopen the PM Configuration dialog each time the
POM/SUT/TC configuration is changed.
Each page label presents a range of parameters for one near end or far end granularity period (15 min.
or 24 h) which together form a dataset. To select a special page label, click on the top part of the label:
NE15m, near end 15 minutes page

NE24h, near end 24 hours page
FE15m, far end 15 minutes page
FE24h, far end 24 hours page
24hBi, near and far end 24 hours page bidirectional (UAS is the sum of far end and near end)
ee 24h, end to end 24 hours page (enable only on HPOM)
1AA 00014 0004 (9007) A4 ALICE 04.10
Each dataset has to be configured independently. For AU4 CTP and TUx CTP the highest criteria is
POM and SUT.
I.e. select the POM/SUT/TC option first and then configure the different associated datasets. Confirm the
configuration with Apply before you continue with a different POM/SUT/TC option.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
288 / 448

The PM Configuration dialog is designed as a notebook consisting of a text field, to identify the selected
TP, and page labels.

Figure 221. PM Configuration Dialog (example)
Activate any item within the page label by selecting the respective radio button.
Mode
1AA 00014 0004 (9007) A4 ALICE 04.10
Data Collection
Select this button to activate performance monitoring. Disabling Data Collection leads to
clearance of the current and all history data of this entity.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
289 / 448
If this item is selected, history data collection is performed in the selected entity for the
corresponding TP.
Note that on disabling this mode item, no history data is available. Nevertheless, datasets
collected prior to deactivation are not cleared and are displayed after re-enabling the item, as
long as the number of displayed datasets does not exceed 16 for 15 min. granularity and one
for 24 hours granularity.
Lock Data Collection (not supported)

If Lock is selected, PM remains enabled but data collection is stopped. All history performance
data remain available. All current values are set to zero.
EML OS Monitoring (only accessible from SH)

Not available for Craft Terminal.
Notifications
UAT (only available for 24 h granularity)

For 24h granularity, UAT (UnAvailable Time) notifications are created if enabled. This
notification results in an UAT alarm in the Alarm Surveillance.
Note: This parameter can only be selected during creation and cannot be subsequently modified.
Suppress Additional Threshold

Disabled: the alarm is generated every time the value exceed the upper threshold (value up).
Enabled: after a first alarm generation, the alarm is generated again when the value exceed the
upper threshold (value up) after the lower threshold (value down) has been exceeded.
Threshold Table
Attach a threshold table to the selected TP. Only assign threshold tables that match the granularity
period of the datasets (i.e. a 15 min. threshold table must not be assigned to a 24 h dataset).
Otherwise the Transmission view is blocked and only released by closing and reopening the PM
Configuration window and the Transmission view.
Click on button Attach... to open the PM Threshold Table Select dialog (see Figure 227. on page
298) and configure the threshold table (see para. 17.7 on page 297).
Select button Remove to disassociate the threshold table from the entity.
Note: A threshold table can only be attached if Data Collection is enabled.
Set Alarm Severity UAT
ASAP Id
This field shows the label of the ASAP pointer assigned to the UAT alarm.
1AA 00014 0004 (9007) A4 ALICE 04.10
Set ASAP
Allows to set a new ASAP pointer for the UAT alarm. The Set ASAP button opens the window
displayed in Figure 13. on page 49.
Confirm the configuration with the button Apply before closing the dialog. Otherwise the configuration is
lost.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
290 / 448

Create History Data
17.5 Display Current Data on SDH port

Use menu item Add TP to display a special TP in the Transmission view (see para. 14.5 on page 185).
Select the TP and open the Current PM Data dialog (see Figure 223. on page 293) by clicking on the
menu item Performance>Display Current Data from Transmission pull down menu.

This Current PM Data dialog serves to show the results and status of the Performance
Monitoring counters.
It is possible to access the same Current PM Data dialog selecting a TP in the Port view and opening
the same Performance > Display Current Data option in the Port pull down menu (see chapter 11 on
page 121).
The Current PM Data dialog is designed as a notebook consisting of a text field, to identify the selected
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
291 / 448

TCM After Matrix
TCM Before Matrix
Each page label presents a range of parameters for one near end and far end granularity period (15min.,
24h, 24h bidirectional) which together form a dataset. To select a special page label, click on the top part
of the label:
15 min, near end and far end 15 minutes page

24 h, near end and far end 24 hours page
24hBi, far end 24 hours page bidirectional (UAS is the sum of far end and near end)
All datasets available which are related to the selected TP and recorded in the current monitoring interval
are displayed in this dialog.
The following items are indicated for each entity:
Administrative State
Indicates whether the PM collection is locked for the local user or not.
Operational State
Indicates whether PM is enabled or disabled.
Suspect Data
Indicates if collection errors occurred during the collection period.
Threshold Table
Indicates which threshold table is assigned to the entity.
Current Problem List

Indicates current UAT (Unavailable) and TCA (ThresholdCrossed) alarms.
Note:The entry Unavailable ThresholdCrossed indicates, that both alarms are active. Since the text field
is too small to display the full text at a time, use the cursor to scroll the text field in this case.
Elapsed Time
Indicates the time which has elapsed since the monitoring interval was started. This information tells
the user whether the data collection covers the whole period.
At the bottom the PM results are listed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Reset button is used to restart the counting period. Two buttons are present for nearend and farend
periods.
Press the Refresh button to update the window contents and display the latest data.
Using the Print button, PM data can be saved to a file or printed on paper.
Note: if no printer is installed, there is no error message displayed to indicate this.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
292 / 448

In case of AU4 CTP and TUx CTPs, the Current PM Data dialog also contains a cascading menu that
allows to choose the POM/SUT/TC options to display as follow (see Figure 223. on page 293):
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 223. Current PM Data Dialog (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
293 / 448

17.6 Display History Data on SDH port
Select the TP and open the PM History Data dialog (see Figure 225. on page 296) by clicking on the menu
item Performance>Display History Data from Transmission pull down menu.

This PM History Data dialog serves to show stored Performance Monitoring counting.
It is possible to access the same PM History Data dialog selecting a TP in the Port view and opening
the same Performance > Display History Data option in the Port pull down menu (see chapter 11 on
page 121).
The PM History Data dialog is designed as a notebook consisting of a text field, to identify the selected
1AA 00014 0004 (9007) A4 ALICE 04.10
In case of AU4 CTP and TUx CTPs, the PM History Data dialog also contains a cascading menu that
allows to choose the POM/SUT/TC options (see Figure 225. on page 296) to display as follow:
ED

TCM After Matrix
TCM Before Matrix
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
294 / 448

Use menu item Add TP to display a special TP in the Transmission view (see para. 14.5 on page 185).

Each page label presents a range of parameters for one near end and far end granularity period. To select
a special page label, click on the top part of the label.
All available datasets (entities), which are related to the selected TP, are displayed in the table:
15 min, near end and far end 15 minutes page

24 h, near end and far end 24 hours page
24h Bi, near end and far end 24 hours page bidirectional (UAS is the sum of far end and near
end)
The PM data is displayed containing information concerning:
Interval End Time

in the format dd.mm.yyyy hh:mm:ss.
The number of recorded events concerning an entity is divided into near end and far end data
Elapsed Time
indicating whether the data collection was complete
susp
indicating suspect data where collection errors occured during the collection period.
In case of 15 min. entities, a maximum of 16 datasets can be displayed simultaneously for each counter,
the 24h entities display a maximum of one dataset. These figures cannot be changed by the user.
If the limit of 16 datasets for 15 min. granularity and one datasets for 24 h granularity is reached, the oldest
set in the list is cleared when the next data set arrives.
Press the Refresh button to update the window contents and display the latest data.
Using the Print button, PM data can be saved to a file or printed on paper.
Note: if no printer is installed, there is no error message displayed to indicate this.
1AA 00014 0004 (9007) A4 ALICE 04.10
I M P O R T A N T : after a reset action or EQUICO unit extraction, the relevant data of PM history
on the CT will be lost; this means that the history data is not lost on the SH if it has already been
uploaded from the NE.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
295 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 225. PM History Data Dialog (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
296 / 448

17.7 PM Threshold Table Selection on SDH port

The PM Threshold Table Select dialog (see Figure 227. on page 298) pops up if the Attach button is
clicked in the PM Configuration dialog (see Figure 221. on page 289).
In addition, this dialog can be accessed using the Configuration pull down menu as shown in following
figure:
Figure 226. Configuration Performance Threshold Tables option

Note: Do not open several dialogs at the same time using both possibilities. Since those dialogs are not
synchronized, they could display different contents.
The dialog presents a list of existing threshold tables.
The tables are individually indicated with a number.
Each table is dedicated to a specific entities, as reported in Table 7. on page 299. Each table can be
modified according the operator selections.
The Filtering Criterias are not operative.
1AA 00014 0004 (9007) A4 ALICE 04.10
The user can perform the following actions:
Create / Modify / Display a threshold table.
Delete an existing threshold table.

Mark the table in the list and click on the Delete button.
Note that a threshold table cannot be deleted if it is attached a PM entity. An error message informs
the user of this situation.
Attach the selected threshold table to a TP entity. It is only available entering from the PM
Configuration dialog (see Figure 221. on page 289).
The user has to close the dialog explicitly by clicking on the button Close.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
297 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 227. PM Threshold Table selection
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
298 / 448
Table 7. Threshold table entities association

N.
layer
TPs ASSOCIATED
granularity
STM16
RS
15 minutes
STM16
RS
24 hours
STM4
RS
15 minutes
STM4
RS
24 hours
STM1
RS
15 minutes
STM1
RS
24 hours
STM16
MS NE / FE
15 minutes
STM16
MS NE / FE
24 hours
STM4
MS NE / FE
15 minutes
10
STM4
MS NE / FE
24 hours
11
STM1
MS NE / FE
15 minutes
12
STM1
MS NE / FE
24 hours
13
VC4
Path Termination NE / FE
15 minutes
14
VC4
Path Termination NE / FE
24 hours
After the activation of a PM on a TP, it will be signalled in the Port view and in the Transmission view as
for the following figure:
PORT VIEW
Active PM
TRANSMISSION VIEW
1AA 00014 0004 (9007) A4 ALICE 04.10
Active PM
Figure 228. Display of Performance Monitoring action
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
299 / 448
17.8.1 Creation
The PM Threshold Table Create dialog (see Figure 229. on page 301) pops up when the Create button
is clicked in the PM Threshold Table Selection dialog (see Figure 227. on page 298).
Carry out the following steps to create a threshold table:
1)
Enter the table name in input field Name.

Leading and successing blanks are ignored. Leaving the input field blank or entering only blanks
is not allowed and rejected.
2)
Select a Granularity of 15 min. or 24 h for the entity.
3)
Enter the set (Value Up) and the reset (Value Down) threshold values. Note that the reset value
if supported, will be available with 15 min. monitoring periods.
Table 8. on page 302 shows the allowed maximum performance parameter values.
The respective value is automatically reset to the maximum if a larger figure is entered.
4)
Select the alarm Severity for each PM attribute in case a threshold is crossed.
5)
Disable Send notification if no notification message should be sent in the case of a crossed
threshold.
6)
Confirm the entries with Apply to create the threshold table. A number of threshold tables can
be created from the same window.
1AA 00014 0004 (9007) A4 ALICE 04.10
Explicitly close the window with button Close.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
300 / 448

17.8 PM Threshold Table Create/Modification/Display on SDH port
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 229. Create PM Threshold Table
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
301 / 448

The PM Threshold Table Modify dialog (see Figure 230. on page 303) pops up if a threshold table is
selected in the PM Threshold Table Selection dialog (see Figure 227. on page 298) and the Modify
button is clicked.
Carry out the following steps to modify a threshold table:
1)
Modify the upper threshold value (Value Up) and the lower value (Value Down)
Table 8. on page 302 shows the allowed maximum performance parameter values.
2)
Modify the alarm Severity for each PM attribute in case a threshold is crossed.
3)
Disable Send notification if no notification message should be sent in the case of a crossed
threshold.
Note that the Name (really number) of a threshold table can be changed.
4)
Confirm the modifications with Apply.
5)
To modify more than one threshold table, do not close the dialog, but select the next threshold
table in the PM Threshold Table Selection dialog and press the Modify button
(see Figure 227. on page 298).
Explicitly close the dialog with button Close.

17.8.3 Display
The PM Threshold Table Display dialog (similar to Figure 230. on page 303) pops up if a threshold table
is selected in the PM Threshold Table Selection dialog (see Figure 227. on page 298) and the Display
button is clicked.
Refer to the previous paragraphs for a description of the attribute values and types.
Table 8. Maximum Performance Parameter Values
Performance Parameter
BBE, FEBBE
1AA 00014 0004 (9007) A4 ALICE 04.10
Max. Value
for 24-h period
539,100
51,753,600
BBE, FEBBE on STM-1 boards
2,159,100
207,273,600
8,639,100
829,353,600
34,559,100
3,317,673,600
138,239,100
13,270,953,600
OFS, ES, UAS, FEES,
900
86,400
SES, FESES
810
78,760
1,800,000
172,800,000
PJC high, PJC low
ED
Max. Value
for 15-min. period
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
302 / 448

17.8.2 Modification
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 230. Modify PM Threshold Table
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
303 / 448

17.9 Configuration on ETH port
Select the TP (Gmau) and open the PM Configuration dialog (see Figure 221. on page 289) by clicking
on the menu item Transmission >Performance >Configure Performance Monitoring (refer to
The Create Ethernet Counter window is opened (refer to Figure 231. on page 304)
Figure 231. Create Ethernet counter
1AA 00014 0004 (9007) A4 ALICE 04.10
In that dialog the operator will be allowed to create/delete the currentData by checking/unchecking the
corresponding checkbox for the incoming and outgoing direction.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
304 / 448

Use menu item Add TP to display a special TP in the Transmission menu (see para.14.5 on page 185).
17.10 Display current Data on ETH port

Use menu item Add TP to display a special TP in the Transmission view (see para.14.5 on page 185).
Select the TP and open the Current PM Data dialog (see Figure 232. on page 306) by clicking on the
menu item Display Current Data (refer to Figure 222. on page 291).
This Current PM Data allows the operator to send a request in order to retrieve the maintenance
counters.
The layout of the dialog maintenance counters is depicted in Figure 232. on page 306.
At startup the dialog displays an empty table; the dialog allows to choose the polling time and how many
times the action will be done; the default values for those entries are 0 for polling time and 1 for number
of retries, with that default configuration if the the Start polling button allows to perform the configured
request. If the number of retries is bigger than 1, several actions are performed on the NE.
During the polling interval the label of the button Start polling will be changed to Stop polling, and for
every response arrived a row is added to the table. Every time the operator push the Start polling button
new lines will be added to the lines already present in the table.
1AA 00014 0004 (9007) A4 ALICE 04.10
If the table contains two or more row, the button Display Graph. will be enabled.
That button allow to visualize the counter values in a graphical view.
An example of this visualization is showed in Figure 233. on page 306.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
305 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 232. Display PM Ethernet current data
Figure 233. Display graphic data (1)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
306 / 448
17.11 Display History Data on ETH port

Use menu item Add TP to display a special TP in the Transmission view (see para.14.5 on page 185).
Select the TP (Gmau) and open the PM History Data dialog (see Figure 225. on page 296) by clicking
on the menu item Display History Data (refer to Figure 224. on page 294).
The menu item Display History Data will be opened (refer to Figure 234. on page 308):
In case of one hour history data, the showed values are the hourly historic data collected by NE.
If the NE has collected only one history data, the dialog shows directly counter values.
If the NE has collected more than one history data, the displayed counter values are calculated as
a difference from the older available history data value.
The older one will be added in the first line with the label and for each cell a tooltip will show the
history value received.
In case of 24 hour history data, the showed values concern the single 24 historic data collected by
NE and the dialog displays directly counter values.
In the bottom of the dialog, the description of the showed counters value is displayed.
The layout of the dialog Display History Data is depicted in Figure 234. on page 308; this dialog shows
the numeric value for each counter calculated as described before.
1AA 00014 0004 (9007) A4 ALICE 04.10
The button Display Graph. allows the operator to visualize the values of a single counter (selecting a
column) in a graphical view.
An example of that is showed in Figure 235. on page 308.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
307 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 234. Display PM Ethernet History Data
Figure 235. Display Graphic Data (2)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
308 / 448

17.12 PM overview
This menu provide a NE global view for PM and Monitoring operations helps the operator to list these
resources.
Select the PM Overview option from the Configuration menu (see following Figure 236. ).
The PM Overview dialog will be opened (refer to Figure 238. on page 311).
Figure 236. PM Overview menu

PM/Monitoring Overview (PMO) dialog is able to show both PM and Monitoring objects.
Search operation are allowed for PM objects, monitoring object or both.
Search operations are divided in two phases:
[1]
The operator chooses a list of interesting TP using TP search; at the end fo this search operation then
operator moves such a list of TPs into PMO dialog. These TPs define a list of search roots for
Monitoring and PM.
[2]
The operator configure the filtering criteria in PMO and starts PM/Monitoring search oeprations using
the Show button in PMO.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 237. on page 310 represents the interworking between these two dialogs.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
309 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 237. PM overviewTp search windows interworking (example)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
310 / 448

Figure 238. PM overview window
1AA 00014 0004 (9007) A4 ALICE 04.10
The button area contains the following buttons (refer to Figure 238. on page 311):
ED
ADD TP : it starts the search operations using the TP Search dialog; only TP references are
moved by TP search into PMO dialog; this is a precondition to start PM/Monitoring search
operations, using TP selected by TP search as search roots.
Show : it starts the search for PM/Monitoring objects in the MIB according to the filtering criteria.
Reset Filter : it resets all filtering settings to default conditions.
Preferences : it starts the user preferences dialog; it is greyed out in USM not supporting this
feature.
Config PM : it starts the dialog for Current Data create/delete.
Config Mon : it starts the dialog for monitoring object create/delete.
Current Data : it starts the dialog for PM counter visualization.
History Data : it starts the dialog for PM counter visualization.
Print : it starts a request to print the tree content.
Delete : it starts a request to remove the selected objects (monitoring and/or).
Delete All : it destroys the TP list and make empty the TreeGadget.
Port View : it starts the Port View. PMO dialog is not closed after Port View or Port details dialog
opening.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
311 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
312 / 448

18 SYNCHRONIZATION MANAGEMENT
18.1 Introduction
All SDH NEs require timing in order to generate the necessary synchronization and frame phase reference
information. The timing can be provided by a source external to the NE or an internal timing generator.
The derived timing shall be used for all signals and interfaces in the NE that are related to the SDH frame
structure.
Follows a brief description of the heart of the NE clock known as the Synchronization Equipment Timing
Source (SETS).
It can be divided into 2 parts:
OSC: the internal oscillator

SETG: the Synchronization Equipment Timing Generator
The SETG is responsible for the generation of the external timing source for the Frame structure and the
clock, whilst the internal oscillator is useful only in the abnormal functioning Freerunning mode that will
be explained later.
The simplified figure that follows represents the internal organization of the SETS.
Squelch
A
Selector
A
Selector
C
T4/T5
Squelch
B
T1
T3/T6
Selector
B
SETG
T0
OSC
SETS
S15
Figure 239. Internal organization of the SETS

The internal sources (inputs) are:
1AA 00014 0004 (9007) A4 ALICE 04.10
T1: Reference obtained from incoming STMN signals

T3/T6: Reference obtained from an external incoming 2048 kHz (T3) or 2048 kbit/s (T6) signal
OSC: the internal oscillator
The number of timing reference inputs depends on the configuration of the NE.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
313 / 448
T0: is the reference output signal for the clock and signal frames
T4: is the 2 MHz reference output for the external equipment synchronization
T5: is the 2 Mbit/s reference output for the external equipment synchronization
Other reference points:
Y: is used for communication of Synchronization Status Message (SSM) between SETS and MST
functional blocks;
S15: is used to provide notifications and loss of incoming timing reference reporting to the
Synchronous Equipment Management Function (SEMF).
Selector A provides the capability to select timing reference from available T1 inputs, either automatically
based on the priority and quality level of the candidate sources (SSM algorithm), or manual as a result of
commands issued from the managing system.
Selector B is capable of selecting timing reference from T1 or T3/T6 inputs, according to the SSM
algorithm. The capability for manual selection of the timing source is also provided.
Selector C is only operated in manual mode, to switch between SETG output signal (T0) and a T1 timing
reference.
The squelch functions A and B mute the relevant timing references in the presence of failure condition,
or SSM threshold violation.
The choice of the timing reference is done in two ways:
Automatically
Following a particular algorithm based on the quality and the priority of the incoming timing signals.
The automatic selection is based either on the priority of the incoming timing source (Priority
algorithm) or on the priority and the quality level of the incoming sources (SSM algorithm).
Manually
Following an order from the Operator.
NOTE: The priority level is determined by the Operator for each candidate timing source. It is static
information. On the other hand, the quality of the source is dynamic information, dependant of the quality
of the reference clock generating the timing.
In an SDH signal frame, the quality of the timing source is located in the Section Overhead.
The SETG has 3 modes of operation:
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Locked mode
The SETG output is fully controlled by the external timing references (T1 and T3/T6).
HoldOver mode
The external timing reference is malfunctioning. The SETG during normal functioning stores
regularly the value of the external timing reference. In this case the SETG output is controlled by this
memorized value.
Free running mode
This is not a normal operating mode. The external timing reference and the memorized timing
reference are malfunctioning. In this case the SETG output is controlled by the internal clock source.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
314 / 448

The external sources (outputs) are:
18.2 Synchronization Management

The operations that can be done on the synchronization sources are the following:
Timing Source Configuration

Protection Commands
T0 Configuration
T4 Configuration
SSU Configuration
Remove Timing Reference
Change T4 <> T5
Set T0 Equal T4
Remove T0 Equal T4
Transmitted SSM Quality Configuration
Show Timing Source
Before any other operation the synchronization view has to be displayed.

18.2.1 Displaying the Synchronization View
Using menu options, select the Synchronization option from the Views pull down menu as shown in the
following figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 240. Obtaining the Synchronization view

Selecting this menu option the synchronization representation will be displayed directly into the current
window instead of the current view. All the operations that can be done on the synchronization sources
are performed from this synchronization view.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
315 / 448
The Synchronization view shows the external timing reference sources and the T0, T4/T5 generation.
The selection is based on the SSM algorithm or on the priority of the incoming timing sources. Activating
the SSM algorithm implies that the selection of the source is before done on the quality criteria and then
on the priority criteria for sources at the same quality level.
After selecting the Synchronization option from the Views menu the Synchronization View is visualized in
following Figure 241.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 241. Synchronization View example
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
316 / 448

18.2.2 Synchronization View
Synchronization View Description

The synchronization view provides two list of allowable timing references:
one for T0 timing output; T0 list is always present

one for T4 or T5 timing output; T0 list is always present
T0 list contains:
a timing reference associated to the Internal Oscillator timing source; it is always present
and it cannot be removed or redefined;
6 max timing reference for candidate inputs belonging to the allowable timing reference
T1 or T3/T6, that can be configured by the operator;
T4 or T5 list contains:
6 timing reference for candidate inputs belonging to the allowable timing reference T1, that
can be configured by the operator.
The T0 and T4/T5 lists are used for the management of reference timing source protection; a 1:N
protection like mechanism is used for the selection of the timing source from T0 (T4/T5) list of the allowable
timing references.
The protection system chooses the timing reference to generate the output T0 (T4/T5) either
automatically, basing on the priority and quality level of the candidate sources according a selection
algorithm or manually under control of the managing system.
View elements description
Here after, the basic component contained in the synchronization view are described:
Timing reference
Each allowable timing reference is represented by the graphical object displayed in the view;
the timing reference graphical object displays (with the exception of Internal Oscillator timing
reference) the following information (if the timing source has been declared by the user):
the name of the selected timing source;

the status of the synchronization source (lockout, manual switch, force switch, automatic
switch, no request, fail);
the label of the quality level of the timing input source;
the priority of the timing input source;
two small boxes representing the SSF (Los) and DRIFT alarms detected on the timing
source:
DRIFT means that the Frequency Offset between the external signal source and the
internal clock is high then the maximum tolerance value;
SSF (Server Signal Failure) means a loss of signal on the relevant timing reference.
In case of alarm indication the operator can select Show Timing Source (Figure 255. on
page 331) to visualize the alarm detail.
1AA 00014 0004 (9007) A4 ALICE 04.10
In the timing reference graphical object associated to the Internal Oscillator the following
information are displayed:
ED
01
the name of the timing source: Internal Oscillator;

a small box representing the LOS alarm; the small box will be lighted up when all the
selected timing source are lost, indicating the Holdover or Free Running operation mode;
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
317 / 448
a label field representing the abnormal clock operation modes; one of the following strings
can be displayed in the label field:
Holdover, displayed when the clock operates in Holdover mode;
Free Running, displayed when the clock operates in Free Running mode;
empty string is displayed when the clock operates in Lock.

a label 0 representing the priority of the Internal Oscillator.
Selectors
Small ellipse are used to represent respectively:
the selector A
the selector B
the selector C
Squelch Status
Boxes contained a label field are used to represent the squelch statuses T0/T4 and T4; the box
displays the configured quality level threshold and it is lighted up when the output timing signal
is inhibited.
Output Signal
An arrow and a label field are used to represent respectively:
the output signal T0

the output signal T4/T5
Line Type
The following different line type are used to link the output signals and the respective allowable
timing reference:
a solid line between an output signal and an allowable timing reference means that timing
reference is currently used to generate that signal;
a dashed line between an output signal and an allowable timing reference means that
timing reference is not currently in use as timing source but will act in the protecting role.
In the same way, a solid line between T0 signal and T4/T5 signal box is drawn when T0 signal
is used to generate T4/T5.
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
318 / 448


18.2.3 Timing Source Configuration

This functionality allows to configure the input synchronization sources and configure or modify the timing
source priority and quality.
Figure 242. Synchronization Menu

The menu options are greyed according to the current state of the dialogue box that the user can open.
Firstly select a synchronization source reference block and after the Synchronization menu to open the
Synchronization option list (see Figure 242. ).
Then select the Timing Source Configuration option from the cascading menu, as shown in the above
figure.
1AA 00014 0004 (9007) A4 ALICE 04.10
The following dialogue box is opened (see Figure 243. on page 320).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
319 / 448

Figure 243. Timing source configuration for crossconnect equipments

The Timing source configuration dialogue box displays the extracted quality of the selected timing source.
It permits to configure the following timing source information:
Quality level
Priority level
Extracted Quality is the actual Rx quality retrieved from the signal received from the line.
Select an empty synch. source reference and click on Timing Source Configuration and then on the Input
Source Choice.
Figure 244. on page 321 shows the opened windows.
Following the TP Search procedure described in para. 14.5.1 on page 185 (rack, subrack, board, port)
enter the physical board termination point (TP) value; these TP are: EIS for electrical SDH port, OpS for
optical SDH port.
This operation can be repeated for all the available empty synch. sources both for T0 clock and for T4
clock.
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE: when selecting as source synchronization a reference T1 obtained from incoming STM1
signal from optical/electrical modules housed in the Access Extension Panel, is necessary:
select T1 from the first eight STM1 signal (inside 1st group of P16S1N unit) incoming
on the first two A4S1 access card of that group;
select only on first three sync. source boxes shown on window.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
320 / 448

Figure 244. Synch. source configuration

Click on the Input Quality Configuration: the option button opens the option menu to select the desired
quality level.
Timing source may have, in increasing order, five quality levels: G.811, G.812T, G.812L, G.813, Q. Dont
use (where the highest quality level is G.811).
If Input Quality Configuration is set to a value other than Extracted, Rx quality is forced to this value.
Click on the Priority: the option button opens the option menu to select the desired priority level.
The internal oscillator timing source will have the lowest priority (priority=0) and its priority can not be
changed. The other timing sources will have a priority of 1 to n.
Priority of 1 is the highest priority. Levels 6,...2 are intermediate levels between level 0 and 1, in increasing
order of priority (i.e. 0 6 5 4 3 2 1).
When the configuration of the timing source is completed, click on the OK button to validate the choice
and close the dialogue box. The Cancel button cancels the configuration and closes the dialogue box.
1AA 00014 0004 (9007) A4 ALICE 04.10
Positioning the mouse on the synch. source box Port# test, the corresponding physical interface
denomination (racksubrackboardport) is written on the window bottom left.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
321 / 448
Select the timing reference from the synchronization view. As in Figure 242. on page 319, select the
Synchronization pull down menu. You can then select the Protection Commands to open Figure 245.
Menu options are greyed according to the current state of the selected timing source.
Figure 245. Lockout, Force and Manual commands

a)
Invoke/Release Lockout: Locking or unlocking a timing source enables or disables the timing
source from being considered as a possible timing source for T0 or T4/T5.
b)
Invoke/Release Force and Manual Selection of Timing Source
General selection.
A timing source can be selected manually or automatically. Furthermore, the selection of a particular
incoming timing source (except the internal oscillator) may be forced.
This selection is independent of the priority or quality of the timing source. If the timing source is lockout
or unavailable, this operation is impossible. A timing source is considered to be available if it is not lockout
and has not a failure condition or Priority level of 0.
The forced switch mode is terminated by releasing or inhibiting the force selected timing source.
The manual selection option is only possible if the quality and priority of the selected timing source are
sufficient. Otherwise the automatic selection algorithm overrules the manual selection.
1AA 00014 0004 (9007) A4 ALICE 04.10
If the previously manual selected timing source becomes unavailable the automatic selection is activated.
The Status indication describes the current synch. status (No Request, Automatic Switch, Failure, ...)
Note: The internal oscillator cannot be forced or manually selected.
From the dialogue box that opens, you can confirm or cancel the operation.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
322 / 448

18.2.4 Synchronization Protection Commands
Manual selection.
1AA 00014 0004 (9007) A4 ALICE 04.10

Manual selection is not operative in the current release.
To perform or release a T0 or T4/T5 lockout, forced or manual selection, the following operations have to
be done:
Select the T0 or T4/T5 source.
Click on the Synchronization menu.
Select the Protection Commands option then invoke/Release the Lockout, Forced or manual
Selection option.
Click on Apply in the displayed confirmation box.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
323 / 448
Select the available T0 or T4 synchronization sources and then the T0 Configuration or T4

Configuration command. This command permits to select/deselect the SSM algorithm, to set the wait
time to restore and to enable the revertive procedure if all these features are available.
In this NE revertive mode is hardware set, with fixed WTR.
In Revertive mode the internal selector A/B (Figure 239. on page 313) changes every time to the best
reference clock with the highest quality; on the same quality level basis the reference clock Source with
the best priority will be selected. The changing mechanism of the reference inputs is controlled by the wait
time to restore: this time sets a delay before to change the input source.
Selecting the T0 Configuration or T4 Configuration set the SSM algorithm and the Wait To Restore Time
in the dialog box upper part of Figure 246. on page 325 and Figure 247. on page 325.
Click on the SSM Algorithm to select/deselect it.
Wait To Restore Time button field and Revertive option are disabled.
Selecting T4 Configuration it is possible to set the T0/T4 and T1/T4 squelch criteria in the dialog box of
Figure 246. on page 325.
This functionality allows to configure the external timing reference (T4) squelch criteria. The squelch
function mutes the relevant timing references in the presence of a failure condition.
Squelch may be forced by the Operator or according to squelch criteria which consists in a choice of quality
level.
Different squelch criteria may be applied:
when T0 is selected to generate T4 (squelch B in Figure 239. on page 313): T0 may be

squelched if all the allowable timing references of Selector B have Quality Level lower than the
programmable threshold;
when T1 is selected to generate T4 (squelch A in Figure 239. on page 313): T1 may be
squelched if T1 Quality Level is lower than the programmable threshold or if it becomes
unavailable.
The T0/T4 and T1/T4 squelch fields enables you to configure the quality level of the T0 or T4 timing
source, opening the relevant option menu.
When the configuration of T0/T4 Configuration is completed, click on the OK button to validate the choice
and close the dialogue box.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Cancel button cancels the configuration and closes the dialogue box.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
324 / 448

18.2.5 Synchronization Configuration for T0/T4 and T4 squelch criteria
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 246. Configuring the T4 SSM algorithm and the squelch criteria
Figure 247. Configuring the T0 SSM algorithm
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
325 / 448

The SSU configuration command allows either to configure the single NE or the NE with SSU.
In the last case the SSU quality has to be defined.
At first click on SSU block (see Figure 241. on page 316) and then select SSU Configuration from the
Synchronization menu.
It will present the following Figure 248.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 248. SSU Configuration
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
326 / 448

18.2.6 SSU Configuration

18.2.7 Remove Timing Reference

Select the synch. source to remove and click on the Remove Timing Reference option as shown in
following Figure 249.
Figure 249. Synchronization source removing
1AA 00014 0004 (9007) A4 ALICE 04.10
To remove the selected source click on OK button of the confirmation message (see following
Figure 250. ).
Figure 250. Synchronization source removing confirmation
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
327 / 448
This menu allows the change of the synchronization physical interface from 2 MHz (T4) to 2 Mbit/s (T5)
and viceversa.
This menu is enable only if the SERVICE board is present in the subrack.
Select Change T4 <> T5 from the Synchronization menu as shown in the following Figure 251. :
Figure 251. Change T4 <> T5 option
1AA 00014 0004 (9007) A4 ALICE 04.10
A confirmation message appears (see the following Figure 252. ):
Figure 252. Change T4 <> T5 confirmation message

Click on ok to confirm. The new window will display T5 instead of T4.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
328 / 448

18.2.8 Change T4 <> T5

18.2.9 Set and Remove T0 Equal T4

To connect T0 internal synch. select a synch. source and click on Set T0 Equal T4 menu option.
The connection between T0/T4 will pass from a shaped to a continue line as in the example of Figure 253.
Figure 253. T4 equal T0 setting
1AA 00014 0004 (9007) A4 ALICE 04.10
To separate T4 from T0 click on the Remove T0 Equal T4 menu option.

The T0/T4 connection will become shaped while the connection between T1/T4 will pass from a shaped
to a continue line.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
329 / 448
Select the T1 SDH Reference Source block in the Synchronization View (Figure 241. on page 316) hence
the Transmission SSM Quality Configuration is enabled. This selection allows, with the Inserted option,
to transmit the system internal T0 clock quality towards the external SDH interface.
It is also possible to transmit different quality level selecting a different value.
Click on Transmitted SSM Quality Configuration option in the Synchronization menu.
Figure 254. opens.
Figure 254. Transmission SSM Quality

This Transmission SSM Quality window can be also opened from any SDH boards.
1AA 00014 0004 (9007) A4 ALICE 04.10
Select the Equipment option of the Views menu, then access the Board view> Port view> Physical
Media> SDH Tx Quality Configuration; it is also possible to open the window selecting the
Transmission option of the Views menu, then access the Physical Media> SDH Tx Quality
Configuration option.
In both cases select the MST block.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
330 / 448

18.2.10 Transmission of SSM Quality Configuration

18.2.11 Show Timing Source

Selecting any T1 Reference Source block in the Synchronization View (Figure 241. on page 316) hence
the Show Timing Source is enabled. This selection allows to analyze the input source considering its
payload structure and the related alarms (Port view is presented).
Click on Show Timing Source option of the Synchronization menu.
Figure 255. opens.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 255. Timing Source Example
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
331 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
332 / 448

19 MSSPRING MANAGEMENT
19.1 MSSPRING introduction
Different MSSPRING protections architectures are provide: 2Fiber (Terrestrial) and 4Fiber NPE
(Transoceanic). See ITUT Rec. G.841 and relevant Annex A.
The description of the MSSPRING protections is inserted in the Technical Handbook.
19.2 MSSPRING connection configuration advices

In the following paragraphs 2Fiber and NPE advices are reported, to follow before to implement the
MSSPRing protection: there are some limitations concerning the aggregate types or the AU4s
crossconnections to be considered.
19.2.1 2Fiber MSSPRING connection configuration advices
The following suggestions must be considered in the MSSPRING connection configuration:
SNCP, 4 Fiber MS SPRING and Aggregate MSP protection connections cannot be installed in
a 2 Fiber MSSPRING network. This leads to an unprotected connections installation.
AU4s from #9 to #16 dont have to be used for connections nor considered in any parameter
of Squelching table provisioning. Only AU4s from #1 to #8 must be used and configured for
path installation.
AU4 permutation (change of AU4 allocation) is not allowed. The AU4 allocated to passthrough
in HVC connections must be the same through the node.
AU4 crossconnection Aggregate side, i.e. paths received from the Aggregate line and
loopedback to the (same) Aggregate line are not allowed.
Follow the Squelching Table Configuration in order to define the Squelching Table HO for
East and for West aggregates describing, for each connection installed, as Source Node, the
Node Identifier of the node generating the considered AU4 and as Destination Node, the
Node Identifier of the node terminating the AU4.
19.2.2 4 Fiber NPE MSSPRING connection configuration advices
1AA 00014 0004 (9007) A4 ALICE 04.10
The following suggestions must be considered in the NPE (4 Fiber MSSPRING transoceanic) connection
configuration:
ED
SNCP, 2 Fiber MS SPRING and Aggregate MSP protection connections cannot be installed in
a 4 Fiber MSSPRING network. This leads to an unprotected connections installation.
In this version this is valid also for 1:1 Optical Tributary MSP.
AU4 permutation (change of AU4 allocation) is not allowed in Traffic Map Configuration (WT
/ PT Channels). The AU4 allocated to passthrough in HVC connections, must be the same
through the node.
AU4 crossconnection Aggregate side, i.e. paths received from Aggregate line and
loopedback to the (same) Aggregate line are not allowed.
Follow the indication of Traffic Map Configuration in order to define the traffic map for
Working and Protection AU4. In this way it is possible to define, in every node, the path of each
AU4 through the ring.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
333 / 448
In the following paragraphs 2Fiber and 4Fiber NPE operative sequence to follow during configuration
are inserted.
19.3.1 Operative sequence to configure 2Fiber MSSPRING
Next paragraphs list the operative sequence according the type of procedure to obtain.
Activation procedure
a)
Create an MSSPRING schema with WTR, Node Identifier, Ring map and the related Squelching
Table for each node of the ring, in the desired order. WTR Ring must be the same in all the nodes.
b)
In the Main dialog for MSSPRing management select ACTIVATE in each node of the ring, in the
desired order.
Consider that, in this step, Default K byte West or East detection by View Protection Status
Parameter (under MSSPRing label > Protocol exception), will occur on those Ports connected
to the nodes not provisioned yet with the MSSPRing protection created (active).
c)
Verify in the View Protection Status Parameter screen, at the end of the provisioning update, that all
the nodes of the ring are in MSSPRing active and No request state.
Deactivation procedure
a)
In the Main dialog for MSSPRing management select DEACTIVATE in each node of the ring.
Parameter (under MSSPRing label > Protocol exception), will occur on those Ports of the
activated nodes connected to the nodes just deactivated.
b)
In the Main dialog for MSSPRing management select DELETE in each node of the ring.
Removing a node
a)
In the Manage ring Map view select the node and click on theRemove Node button.
b)
Modify the table in the Configure Squelch Table view according the new Ring Map.
c)
Opening the View Protection Status Parameter screen, send Force Ring command to both NEs
adjacent to the node to be removed.
d)
Physically remove the node.
e)
Connect the fibers and send the Release command of the relevant Force Ring to both NEs
adjacent to the removed node.
Adding a node
a)
In the Manage ring Map view insert the node in the selected position. Next nodes are automatically
shifted.
Modify the table in the Configure Squelch Table view according the new Ring Map.
adjacent to the node to be added.
Physically add the node and configure with 2Fiber MSSPRING activated with the right
configuration (Ring Map, Squelching table, WTR, Node Identifier).
Connect the fibers and send the Release command of the relevant Force Ringto both NEs
adjacent to the added node.
1AA 00014 0004 (9007) A4 ALICE 04.10
b)
c)
d)
e)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
334 / 448

19.3 Operative sequence to configure MSSPRING
19.3.2 Operative sequence to configure 4 Fiber NPE MSSPRING
1AA 00014 0004 (9007) A4 ALICE 04.10

Next paragraphs list the operative sequence according the type of procedure to obtain.
Activation procedure
a)
Create an MSSPRING schema with WTR, Node Identifier, Ring map and the related Traffic Map
for each node of the ring, in the desired order.
WTR Ring must be the same in all the nodes.
b)
In the Main dialog for MSSPRing management select ACTIVATE in each node of the ring, in the
desired order.
Consider that, in this step, Default K byte west or East detection by View Protection Status
Parameter (under MSSPRing label > Protocol exception), will occur on those Ports connected
to the nodes not provisioned yet with the MSSPRing protection created (active).
c)
Verify in the View Protection Status Parameter screen, at the end of the provisioning update, that all
the nodes of the ring are in MSSPRing active and No request state.
Deactivation procedure
a)
In the Main dialog for MSSPRing management select DEACTIVATE in each node of the ring.
Parameter (under MSSPRing label > Protocol exception), will occur on those Ports of the
activated nodes connected to the nodes just deactivated.
b)
In the Main dialog for MSSPRing management select DELETE in each node of the ring.
Removing a node
a)
In the Manage ring Map view select the node and click on theRemove Node button.
b)
Modify the table in the Configure Ring Traffic Map view according the new Ring Map.
c)
adjacent to the node to be removed.
d)
Physically remove the node.
e)
adjacent to the removed node.
Adding a node
a)
In the Manage ring Map view insert the node in the selected position. Next nodes are automatically
shifted.
b)
Modify the table in the Configure Ring Traffic Map view according the new Ring Map.
c)
adjacent to the node to be added.
d)
Physically add the node and configure with 4Fiber NPE activated with the right configuration (Ring
Map, Traffic Map, WTR, Node Identifier).
e)
adjacent to the added node.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
335 / 448
The NE supports the MSSPRING protection as Terrestrial and Transoceanic application with a 2Fiber
or a 4Fiber architecture.
The available tables permit to visualize for the same NE the architecture 1 x 2Fiber and 1 x 4Fiber
Transoceanic (NPE protection).
For the Transoceanic application a max. of 64 nodes are available and a max. of 16 for the Terrestrial
2Fiber application.
Figure 256. shows the MSSPRing pull down menu.
Figure 256. MSSPRing pull down menu

The Main Dialog for MSSPRing management option contains all the commands to configure and
manage the MSSPRing.
1AA 00014 0004 (9007) A4 ALICE 04.10
In any dialog box is present the Cancel or Close buttons. When the user clicks on these buttons the dialog
box will close without starting any operation.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
336 / 448

19.4 MSSPRING Configuration

19.4.1 MSSPRing Main Configuration

Select the MSSPRing pull down menu. Then select the Main Dialog for MSSPRing management
option from the pull down menu.
The following dialogue box is displayed (see Figure 257. ) when no protection have been previously
configured.
Figure 257. MSSPRing Management dialogue box

The only command available is Create. The name of Schema Selection is not editable but is fixed to No
Schema.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on Create to start the MSSPRing configuration. Figure 258. opens.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
337 / 448

Figure 258. Creation Schema dialog box

The user can select the MSSPRing Application and the Architecture types supported by the Network
Element.
Terrestrial MSSPRing Application is a 2 Fiber architecture.
Transoceanic MS_SPRING is a 4 Fiber architecture.
The Port Selection depends on the Architecture type: if the architecture is a 2F MSSPRing, the working
and protection port on each side is the same and the Protecting West and East fields are disabled
(greyed).
If the architecture is a 4F MSSPRing, the working and protection ports on each side are different.
The label r(xx)sr(y)sl(zz)port#(hh) where r=rack, sr=subrack, sl=slot give the position of the physical port.
In the same board it is generally possible to have different port numbers. Only one port number (port#01)
is available in the 1670SM.
Actually for 1670SM the working and protection aggregate boards have a fixed location in the
subrack and the Choose Port buttons is not used.
1AA 00014 0004 (9007) A4 ALICE 04.10
The OK button will start the selected operation. The cursor is displayed busy up to receiving a reply. Then
the dialog window will be closed. Figure 259. opens and all commands are now available.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
338 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 259. Activated MSSPRing Management
Click on Ring Map to configure the network node connection. Figure 260. opens.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
339 / 448


Figure 260. Node Id and associated ring node position

The Ring Map sets the connection sequence of the nodes within the ring. The matrix represents up to 64
nodes for transoceanic application and up to 16 nodes for terrestrial application.
Select Current NodeId (it means the NE where the operator is acting) in the box and enable ( n ) Change
NodeId button (Id means Node Identifier).
Select Available NodeId in the pull down list (0 to 63 for transoceanic application, 0 to 15 for terrestrial
application) releasing the left mouse button or pushing the stepper arrows and enter keys to select the
NodeId value.
This will be displayed in the Available NodeId box then click on Add Node button.
Clicking on the Add Node button the selected Ring position will shift one step on the right starting from
1 position and in the NodeId field the Available NodeId value is inserted. In the same time the Available
NodeId will be updated to a new value.
1AA 00014 0004 (9007) A4 ALICE 04.10
The default association for a four node ring related to the fourth node (NodeId=3; Ring Position=4) is
depicted in Figure 261.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
340 / 448

Figure 261. Ring map configuration

Repeat the procedure for all nodes of the ring selecting the different NEs and edit the different Current
NodeId value.
To remove a node, select the node and click on Remove Node button. The following Ring Position of the
nodes on the right decreases by one and the erased NodeId is inserted into Available NodeId , so it can
be assigned to other nodes.
The OK button will start the selected operation, displaying the busy cursor up to receiving the reply to the
actions. Then the dialog window will be closed.
1AA 00014 0004 (9007) A4 ALICE 04.10
Click on the WTR Time button. Figure 262. opens.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
341 / 448

Figure 262. WTR dialog box

Click on the push mouse button on the up/down Seconds arrows to select the required delay for the
relevant WTR. The step value is 60 sec.
The range value accepted is from 60 sec. to 900 sec.
Click on OK to apply the WTR Configuration.
WTR Time Span is used only for 4 fiber architecture; it is disabled (greyed) for 2 fiber architecture.
1AA 00014 0004 (9007) A4 ALICE 04.10
The same WTR Time Ring must be set on each Node of the ring.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
342 / 448

19.4.2 Squelching table with 2 fiber Terrestrial applications

With a 2 fiber Terrestrial application can be selected the Squelching Table while with a 4 fiber
Transoceanic application can be selected the Ring Traffic (see Figure 259. on page 339).
If the operator tries to select a different table a error message is visualized. Figure 263. shows the error
message visualized when is selected the Ring Traffic with a Terrestrial application.
Figure 263. Example of error message

Click on Squelching Table of Figure 259. on page 339 to configure the AU4 (AU4#1 to AU4#8 for 2F
Architecture) connection between the different nodes. Figure 264. opens. The same opens clicking on
Configure Squelch Table of the MSSPRing pull down menu of Figure 256. on page 336.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 264. Squelching table

When the window is opened for the first time the squelching table is N/A (not available) because the NE
has never been configured. Point the mouse on the matrix position and click on the right mouse button
to open the node list menu. Select the node identification number (0 to 15) from the available list using
the slider or the stepper arrows on the right scroll region.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
343 / 448
19.4.2.1 Squelching table example

Figure 265. is an example of ring traffic.

Figure 266. rapresent in a table the connections of the ring example.
Figure 267. to Figure 274. show how to configure the relative squelching table.
AU4#3
AU4#1
AU4#2
West
East
West
East
B
AU4#1
AU4#2
AU4#3
AU4#2
AU4#3
AU4#3
East
West
East
AU4#1
West
Figure 265. Example of a ring traffic

The squelching table is applicable only for HOVC signals.
AU
Number
1
2
3
west
A
Node
B
east
C
VC
VC
VC
4
5
1AA 00014 0004 (9007) A4 ALICE 04.10
6
Figure 266. Connections of the ring of Figure 265.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
344 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10

Node A:
Figure 267. Squelching table of Node A, West side
Node A:
Figure 268. Squelching table of Node A, East side
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
345 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10

Node B:
Figure 269. Squelching table of Node B, West side
Node B:
Figure 270. Squelching table of Node B, East side
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
346 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10

Node C:
Figure 271. Squelching table of Node C, West side
Node C:
Figure 272. Squelching table of Node C, East side
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
347 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10

Node D:
Figure 273. Squelching table of Node D, West side
Node D:
Figure 274. Squelching table of Node D, East side
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
348 / 448

19.4.3 Traffic Map with 4 Fiber Transoceanic application

After having set the Schema Configuration, the WTR Time and the Ring Map for the transoceanic
application, the user has to configure the traffic maps. That means to describe each path implemented
on the ring, in terms of crossconnections make up that path inside each node.
19.4.3.1 General information on Connection Configuration
Here are briefly described some parameters indicated in the configuration tables:
The main connection types are:
Drop/Insert
Terminated connections between Tributaries and Aggregates (Trib. to Agg.)
PassThrough
Connection between Aggregate West and Aggregate East (or vice versa) through the matrix
Pointto Multipoint, FirstPointtoMultipoint, LastPointtoMultipoint

Signal broadcasting from one aggregate/tributary to other Aggregates/Tributaries.
Drop and Continue P (Protection Channels)

Drop, insert through the switching service (SS) and bidirectional passthrough between the
aggregates through the Continue function (Used in Primary node for dualnode ring
interconnection).
Last Drop Continue

Same as Drop/Insert, but used in Secondary node for dualnode ring interconnection.
Continue
Bidirectional passthrough. It can be applied to AU4 #k protection channels to realize the Drop
and Continue P function. Continue is only associated to the Drop and Continue function.
No Connection
Concatenated
It means: same Crossconnections as the one of the first AU4 of the AU44c concatenation
signal. It is not a crossconnection type but a different AU4 configuration: each AU4 is
connected to the following increasing the total bandwidth (N x AU4) capacity (see Figure 292. ).
Mixed configurations of previous connections
All the previous connections are possible on:
AU4
1AA 00014 0004 (9007) A4 ALICE 04.10
can be referred to Aggregate STM 16
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
349 / 448
For each type of main connection is listed the available mode.
Insert to West (or East)

The selected AU is transmitted from the tributary to only one Aggregate in the
corresponding West (or East) side. This crossconnection may be part of one
unidirectional path, or of one direction of a bidirectional path.
WEST
AGGREGATES
EAST
Rx
Tx
Tx
Rx
TRIBUTARY
Tx
Rx
Figure 275. Insert to East
Drop West (or East) (see Figure 276. )

The selected AU is received from only one Aggregate.
AGGREGATES
WEST
EAST
Rx
Tx
Rx
Tx
TRIBUTARY
Tx
Rx
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 276. Drop East
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
350 / 448

Drop/Insert (see Figure 275. )
Passthrough (see Figure 277. )

With regard to passthrough traffic, if the path is bidirectional, the same AU must be used
for both directions, i.e., West to East, East to West).
The passthrough can be distinguished in West to East or East to West by the direction
arrow, or bidirectional selecting both modes in the same AU.
WEST
Rx
AGGREGATES
EAST
Tx
PASS THROUGH
WEST TO EAST
Tx
Rx PASS THROUGH
EAST TO WEST
BIDIRECTIONAL
Rx
WEST 1
EAST 1
AGGREGATES
Tx
Tx
Rx
UNIDIRECTIONALS
WEST 2
EAST 2
Rx
Tx
PASS THROUGH
WEST TO EAST
Tx
Rx
PASS THROUGH
EAST TO WEST
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 277. Example of West to East Passthrough with its protection
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
351 / 448
The allowed selection is the broadcast of the incoming signal towards the tributary and the
opposite aggregate
The PointtoMultipoint path broadcasts the incoming signal to different nodes according
to the following rules:
in the first drop node

PointtoMultipoint;
in the last drop node the same traffic is named Last PointtoMultipoint;
in any intermediate drop node this traffic is named PointtoMultipoint.
the
crossconnection
traffic
is
named
First
This convention allows to minimize the switching protection only for not reachable nodes.
Tributaries
Source
node
Intermediate
drop node
First drop
node
Last
drop node
Figure 278. PointtoMultipoint path
West
East
Working i
Working i
Tx
Matrix
Rx
AGGREGATES:
i= working, k=i+16 = protection
Tributary
Protection k
Protection k
Tx
Rx
1AA 00014 0004 (9007) A4 ALICE 04.10
Matrix
Figure 279. PointtoMultipoint configuration and relevant protection channel
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
352 / 448

PointtoMultipoint, FirstPointtoMultipoint, LastPointtoMultipoint
Drop and Continue P

The Drop&Continue architecture is applied for dual node ring interconnection.

Interworking between the transoceanic MSSPRing and another ring shall be achieved
using two nodes (named Primary and Secondary nodes). The crossconnection on the
first node (the Primary node) is performed by the Drop and continue and the Continue
functions. The current configuration is name Drop & Continue P then is only used the
protection channels. The Secondary node, that may not be adjacent, is the protection of
the Primary node and utilizes the Last Drop Continue connection.
East
AGGREGATES i and k=i+16

Working i
Working i
Tx
Rx
Matrix
Tx
Rx
ss
Protection k
Protection k
Rx
Tx
Tx
Rx
TRIBUTARY
Rx
Tx
Continue
Drop and Continue
Protection k
Figure 280. Drop & Continue and Continue
1AA 00014 0004 (9007) A4 ALICE 04.10
Drop and Continue is associated to the Continue function. Figure 280. depicts the whole
functionality. The current crossconnection provides the Drop and Continue P (Protection)
while the Continue Working i is not supported. This configuration is always bidirectional.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
353 / 448
The second ring interconnection of the Secondary node is named Last Drop & Continue.
The Secondary node is the protection node. Actually Drop and Continue configuration
uses only the protection channels (k=i+16). Thus the Last Drop and Continue has to
utilize the protection channels.
East
West
AGGREGATES i and k=i+16
Working i
Working i
Tx
Rx
Tx
Rx
Protection k
Protection k
Rx
Tx
Tx
Rx
Tx
Rx
TRIBUTARY
Tx
Rx
Figure 281. Example of Last Drop & Continue on West side (protection on East)
Figure 282. resume the Drop & Continue P and Last Drop & Continue in the Primary
and Secondary nodes:
West
Working i
Working i
Tx
Rx
Tx
East
West
East
Working i
Rx
Working i
Tx
Rx
Tx
Rx
ss
Protection k
Protection k
Rx
Tx
Tx
Protection k
Rx
Tx
Rx
Tx
Protection k
Rx
Tx
Rx
1AA 00014 0004 (9007) A4 ALICE 04.10
TRIBUTARY
Tx
Rx
Figure 282. Drop & Continue P and Last Drop & Continue in Primary and Secondary nodes
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
354 / 448

Last Drop & Continue

19.4.4 Traffic map table description

The application lists to the operator a twosection matrix: one for working traffic (WTXC Map) the other
for the protection traffic (PTXCMap). Each section manages 64 x 2 columns with N x 2 rows; every two
column correspond to West and East side of a node (maximum node number=64) while N depends on
the STMN level (for 1670SM, N=16).
Click on Traffic Map of Figure 259. on page 339. Figure 283. opens.
Figure 283. Traffic table
1AA 00014 0004 (9007) A4 ALICE 04.10
Select the radio button related to the crossconnect (XC) type at the bottom of the window and then point
the mouse to a matrix position corresponding to a row/column crossing and push the left mouse button.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
355 / 448
PT for PassTrough
D for Drop
I for Insert
PTM for PointtoMultipoint
FPTM for First PointtoMultipoint
LPTM for Last PointtoMultipoint
C for Continue
D&CW for Drop & Continue Working (not supported)
LDC for Last Drop Continue
CNC for Concatenated
D&CP for Drop & Continue Protection
NC for No Connection

The possible traffic indications are:
For each node and any AU4# select the right XC(crossconnect) option.
In this way it is possible to configure the type of connection of each AU4 in all the 64 nodes of the ring.
Note that the node indications (first row) of the traffic map tables are referred to the node identification
and not to the physical position of the ring map.
The meaning of the abbreviation is explained at the window bottom.
The symbol
indicates the West Tx side or the East Rx side.
1AA 00014 0004 (9007) A4 ALICE 04.10
The symbol indicates the West Rx side or the East Tx side.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
356 / 448
19.4.5 Symbolic representation

Remember that i=working, k= protection.

Drop=D, Insert= I (see Figure 284. ).
AU4 #i
West
D
I
East
I
D
West
D
Bidir.
D/I West
Bidir.
D/I East
East
I
West
East
Unidir.
D West
Unidir.
I East
Unidir.
I West
Unidir.
D East
Figure 284. Drop/Insert

Pass Through = PTPT (see Figure 285. )
AU4 #i
West East
PT PT
West East
PT PT
PT PT
unidirectional West to East
West East
PT
bidirectional
PT
unidirectional East to West
Figure 285. PassThrough

FirstPointtoMultipoint=FPTMFPTM,
LastPointtoMultipoint=LPTM
AU4 #i
PointtoMultipoint=PTMPTM,
West East
FTPM FTPM
first node
West East
PTM PTM
intermediate node
West
LPTM
last node
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 286. PointtoMultipoint
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
357 / 448
Continue=C (protection AU4#k=i+16) and Drop and Continue P=D&CP (working AU4=i)
AU4 #i
West
C
C
AU4 #k

West
D&CP
D&CP
East
D&CP
D&CP
East
C
C
Drop & Continue
Continue West
Drop & Continue

Continue East
Figure 287. Drop & Continue plus Continue

Last Drop Continue=LDC
East
LDC
LDC
AU4 #k
West
LDC
LDC
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 288. Last Drop Continue
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
358 / 448

19.4.6 Ring Normal / ExtraTraffic Examples

The ring Normal/ExtraTraffic maps may be drawn up by giving the description of each installed path in
terms of the whole set of crossconnections set up inside each node traversed to the path itself.
AU4 #i (working channel) i=1 to 16

AU4 #k (protection channel) k=i+16
A
F
C
D
Figure 289. Traffic example in ring

For example (see Figure 289. ), the Normal bidirectional paths installed between A and D and between
D and F on the working AU4 #i are described by the ring normal traffic map as depicted below:
A
B
C
D
E
F
West East West East West East West East West East West East
I
PT PT
PT PT
D
I
PT PT
D
D
PT PT
PT PT
I
D
PT PT
I
AU4 #i
path
(working channel)
path
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 290. Ring normal traffic map
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
359 / 448
AU4 #i
A
B
West East West East
I
D
D
I
(protection channel)
path
Figure 291. Ring extratraffic map

A contiguous concatenated path (AU44c) may be represented (see Figure 289. ) by fully describing it
only in the first row (i.e., the one with the smaller channel number), and merely padding the next three ones
with a special marker to show that they are concatenated to the first and thus share the same
characteristics (see figure below).
AU4 #i
AU4
#i+1
A
B
C
D
E
F
West East West East West East West East West East West East
I
PT PT
PT PT
D
D
PT PT
PT PT
I
CNC CNC CNC CNC CNC CNC
AU4
#i+2

AU4
#i+3

1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 292. Ring Normal traffic map: concatenated path
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
360 / 448

Likewise, the ExtraTraffic bidirectional path set up between A and B on the protection AU4 #k are
described by the ring extratraffic map as depicted below:

The ring traffic map (Figure 294. ) represents the pointtomultipoint path of Figure 293. depicted
below:
E
M
Figure 293. Pointtomultipoint
AU4 #1
A
B
West East West East
I
PT PT
G
West East
FPTM FPTM
H
West East
PTM PTM
L
West East
LPTM
M
West
(working channel)
Figure 294. Ring normal traffic map describing a pointtomultipoint unidirectional path
1AA 00014 0004 (9007) A4 ALICE 04.10
(node L knows that its drop connection is the farthest of a pointtomultipoint path because its preceding
nodes East outgoing path on the same time slot is a pointmultipoint crossconnection).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
361 / 448
The ring figures show the working channels with blue lines, the protection channels with red lines. The
white pipes depict the working channels while the grey pipes the protection ones.
B
NPE
NPE
F
NPE
NPE
F
Figure 295. 2 NPE rings, bidir, D&C, no prot. in NPE
B
West East
C
West
D
East
I
D
AU4 #i
West
East
(working
channel)
D&CP
D&CP
D
West
1AA 00014 0004 (9007) A4 ALICE 04.10
AU4 #k
E
F
West East West East
East
C
C
E
F
West East West East
(protection
LDC
channel)
LDC
Figure 296. Path of Figure 295. case B
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
362 / 448

19.4.6.1 Dual ring interconnection examples

B
NPE
NPE
F
E
E
W
E
NPE
NPE
F
Figure 297. Bidir, D&C, no prot. in NPE, (add/drop node = Primary)
AU4 #i
AU4 #k
A
B
East
West East West
PT PT
D&CP
PT PT
D&CP
A
West East
PT PT
PT PT
B
West
East
West
C
East
C
C
West
LDC
LDC
East
E
F
West East West East
I
(working
D channel)
E
F
West East West East
(protection
channel)
Figure 298. Traffic map of Figure 297. case A and Figure 295. case A
A
West East
B
West
1AA 00014 0004 (9007) A4 ALICE 04.10
AU4 #k
D
East
West
East
C
C
E
F
West East West East
LDC
(protection
LDC
channel)
Figure 299. Path of Figure 297. case B
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
363 / 448
W
E
NPE
NPE
F
NPE
NPE
F

W
Figure 300. Bidir, D&C, no prot. in NPE
AU4 #i
AU4 #k
(working
A
B
C
D
E
F
West East West East West East West East West East West
East channel)
I
D&CP
D
D&CP
PT
PT
PT
PT
PT
PT
PT
PT
PT
PT
PT
PT
C
C
LDC
LDC
(protection
channel)
Figure 301. Traffic map of case C
1AA 00014 0004 (9007) A4 ALICE 04.10
AU4 #i
AU4 #k
(working
A
B
C
D
E
F
West
East West East West East West East West East West East channel)
D&CP
I
D
D&CP
C
C
PT
PT
PT
PT
(protection
channel)
LDC
LDC
Figure 302. Traffic map of Figure 300. case D
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
364 / 448

NPE
F
Figure 303. Unidir, D&C, no prot. in NPE
A
B
C
D
E
West East West East West East West East West East
AU4 #i
1AA 00014 0004 (9007) A4 ALICE 04.10
AU4 #k
PT
PT D&CP
F
West East
D&CP
LDC
LDC
PT
PT
(working
channel)
(protection
channel)
Figure 304. Traffic map of Figure 303. case B
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
365 / 448
The Main Activities commands (see Figure 257. on page 337) manage the MSSPRing configuration. The
MSSPRing status can be Enable, Active, Disable and Inactive.
After having configured the protection schema by means of the Create button, the status becomes
Enable .
The Activate button selection set in service the MSSPRing protection mechanism on the selected
schema configuration.
To change from Active to Enable click on the Deactivate button. This command starts the request to
deactivate the MSSPRing protection mechanism.
When the selected protection schema is Enable the Delete button starts the request to remove it. The
delete action is started after confirming the window message (see Figure 305. ).
Figure 305. Confirmation message
1AA 00014 0004 (9007) A4 ALICE 04.10
During the activation procedure on different ADMs some of these can be in Active status, others in Inactive
status. The statuses, the protocol request and the protocol protection errors are described in next chapters
describing theMSSPRing Protection Status and Commands.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
366 / 448

19.4.7 Activate, Deactivate and Delete commands

19.5 MSSPRING Protection Status and Commands for NPE Application

19.5.1 4F MSSPRing protection commands
If a protection schema is Active it is possible to select one of the above commands.
Click on MSSPRing >Main Dialog for MSSPRing management pull down menu and select Prot.
Commands. Figure 306. opens.
Figure 306. Protection states and commands Idle status (4F)

The working/protection span state boxes are available only for the 4Fiber MSSPRing architecture.
1AA 00014 0004 (9007) A4 ALICE 04.10
The ring and span protections are depicted on Figure 307. on page 368.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
367 / 448
w
w
p
p
w
w
E
p
p
Span Protection:
the working channels are
substituted by the protection
channels
E
p
p
w
w
w
w
p
p
Ring Protection:
the working channels are substituted
by the ring protection channels p
( B on East side )
( A on West side )
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 307. Span and Ring Protection (4F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
368 / 448
19.5.2 External commands (4F)

The external protection commands are: Lockout, Force, Manual, WTR.

The lockout commands disable the MSSPRing management.
The lockout section presents six lockout commands (see Figure 308. ). Each lockout command is
applicable on different points where the lockout actions has to be performed (see Figure 309. ).
Figure 308. Lockout commands (4F)
w
w
p
p
Protection Span West Working Span West
1AA 00014 0004 (9007) A4 ALICE 04.10
p
p
Working Ring West
p
p
Protection Span East Working Span East
w
w
w
w
w
w
p
p
Working Ring East
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
369 / 448
Hereinafter these events are named Events and the single event Event.
The Events will be served if some actions (B/S=bridges and switches) are executed and the network
has been updated.
The Events will be signalled if the K1/K2 protocol communicates to the network nodes what has
happened.
The ring traffic can be completely restored when there are also two or more span failures. A single ring
failure is completely restored but not two ring failures or a ring and a span failure. When are present
multiple ring failures the automatic B/S protection will try to maintain on all the possible connections.
The K1/K2 communication protocol MSSPRing is generated from the two nodes adjacent to Event via
the protection communication channels. A node is defined tail end when it firstly receives the Event,
the second node is defined headend when it receives back the protocol answer. Figure 310. shows the
association of tailend / tailend or headend / tailend.
Some network protection mechanisms are accepted or rejected depending on the end type (tail/head)
(lockout command,...).
X
p
Tailend
w
w
p
p
Tailend/Headend
Tailend
Figure 310. Tailend / Headend association
1AA 00014 0004 (9007) A4 ALICE 04.10
If the node is tailend, the lockout working ring/span commands disable the protection MSSPRing
mechanisms, while if the node is headend, it serves the request node protection. With the lockout
protection span command and a ring failure, the ring protection is served if this ring failure occurred along
the same span; the ring protection is disabled if this ring failure has occurred in another ring section.
Instead of a span protection a ring protection is attempted with a working span failure and a lockout
protection span (see Figure 311. on page 371).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
370 / 448

The protection events can be equipment/signal failure, signal degrade or external command or a
combination of them.

Lockout protection
span
failure
w
w
p
p
A
E
B
E
ring protection
Lockout protection
span
failure
w
w
p
p
A
E
W
E
C
W
no ring protection
Lockout protection
span
failure
w
w
p
p
A
W
E
W
B
E
1AA 00014 0004 (9007) A4 ALICE 04.10
ring protection
Figure 311. Ring protection with a lockout protection span and a ring failure (4F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
371 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Combinations
of nonserved
failures:
01
W
B
5
3 together 4
3 together 6
A Node
A Node
1 together 2
1 together 5
Ring E
Ring W
w
w
p
2
A Node
Span W
w
w
p
A Node
Span E
signal degrade
detected in 4
ring protection on
the opposite side
if the ring failure
occurs between
AB or BC nodes
A Node
Span E

signal degrade
detected in 2
ring protection on
the opposite side
if the ring failure
occurs between
AC or CB nodes
A Node
Span W
Lockout Working Lockout Working Lockout Working Lockout Working Lockout Protection Lockout Protection
Figure 312. shows a ring with three nodes and the actions performed by the lockout commands. This
command disables the acknowledgment of the signal failure/degrade on the aggregate ports.
Figure 312. Lockout command and nonserved failures (4F)
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
372 / 448

The Force command (see Figure 313. ) executes a forced protection. The Force Span command
substitutes the working channels onto the relevant protection channels between two adjacent nodes on
the same direction (respectively East side and West side or vice versa). The Force Ring command
substitutes the working channels with the protection channels between two adjacent nodes on the
opposite direction (see Figure 314. ).
Figure 313. Forced and Manual commands (4F)
A1
w
w
w
w
p
p
Span West
p
p
p
p
B1
p
p
W. channels are substituted by P.channels

on the same side for both adjacent nodes
A1
p
p
w
w
Span East
w
w
B1
p
p
W. channels are substituted by P.channels

on the opposite side for both adjacent nodes
Ring West
Ring East
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 314. Manual and Force Span/Ring command (4F)

The Manual command is similar to Force command but it is at a lower priority level with respect to
automatic MSSPRing. The general priority scale that can be applied to solve antithetical situations
starting from the lowest priority level is: manual ring manual span automatic working ring automatic
working span force ring force span automatic protection span lockout
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
373 / 448
Force Ring
w
w
failure
w
w
p
p
w w
p p
Force Ring
w
w
p
p
failure
w
w
E
w w
1AA 00014 0004 (9007) A4 ALICE 04.10
p p
Figure 315. Examples of a Force command and a Automatic protection span (4F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
374 / 448

When a force ring command is applied a next working span failure is not able to modify the forced
configuration applied. That is because force ring command has a higher priority respect to the Automatic
working span protection. But if the failure is detected on the protection channels the Force ring command
is not served because, in this case, the span protection priority is higher than the Force priority (see
Figure 315. ). Vice versa the Manual protection is exceeded by the Automatic protection.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 316. Automatic protection Bridge/Switch (4F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
375 / 448
B/S actions
12 channels are
sobstituted by 56 channels
A node
w
p
p
w
3
4
6
5
8
7
1
2
87 channels are
sobstituted by 43 channels
A node
w
p
p
12 channels are
sobstituted by 34
A node
The working channels 12

(W) or 78 (E) remain active
A node
Signal fail/degrade Signal fail/degrade Signal fail/degrade Signal fail/degrade

Ring W
Ring E
Span Working W Span Protection W/E

From each command exists its own Release button to cancel the previously selected command and come
back to normal MSSPRing protection.
Figure 317. Example of confirmation dialog box

Clicking on the WTR command Figure 318. opens. If the WTR box, in the Local Condition, becomes red
a waiting time has been activated after repairing the ring/span failure. The waiting time, set in the
configuration menu, can be cleared selecting the appropriate clear command. A confirmation dialog box
opens and, if the operator clicks OK, the WTR box turns off and the protection status window is updated.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 318. Clear WTR commands (4F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
376 / 448

Each command starts when the proper button is selected. A dialog box (see Figure 317. ) has to be
confirmed before the command is performed.
19.5.3 4F MSSPRing dual protection commands

In general dual contemporary Events can be:
two external commands
an external command and a ring/span failure
two contemporary ring/span failures
Dual Events can appear on the same side W/W or E/E (SS= same side) or on the opposite side W/E
or E/W (OS= opposite site) of the ring network. In the SS or OS the Events can appear on the same node
(SN) or on the different nodes (DN), the different node can be an adjacent node (AN) or a remote node
(RN). Figure 319. depicts a clockwise ring network. The network propagation K1K2 protocol signals are
according to the following legend:
C
= served the column element
= served the row element
= served both row and column elements
Cs
= signalled (not served) the column element
Rs
= signalled (not served) the row element
Bs
= signalled (not served) both row and column elements
B(ring) or Ring = the row and column elements combine to serve the ring protection
RMs /CMs= the row/column element cannot be neither served nor signalled (this is only for
Automatic working ring); only the Protection span is served.
1AA 00014 0004 (9007) A4 ALICE 04.10
when a command (Manual switch, Force switch) is neither served nor signalled that is erased (it
is not pending at the node).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
377 / 448

Reference point
clockwise
OS SN
SS SN
1
E
SS RN
4
OS RN
OS AN
2
W
w
w
p
p
SS RN
E
w
w
p
p
SS AN
OS RN
Figure 319. Ring network reference scheme for dual Events (4F)
1AA 00014 0004 (9007) A4 ALICE 04.10
The automatic protection for dual ring failures is represented in Figure 320. on page 379.
Consider the network reference scheme of Figure 319.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
378 / 448

Reference
point
Span
Other
points
SN
SS AN
Ring
RN
Working
RN
SN
SS AN
RN
Span
Automatic
SN
OS AN
SN
OS AN
RN
Protection
Span
Automatic
SN
SS AN
RN
SN
OS AN
RN
Working
Protection
C
R,CMs
R,Cs
R,CMs
C
R,Cs
Ring
B
B
B
Ring
B
Prot. Span
B
B
B
Prot. Span
B
Ring
Span
ROW
Ring
Node B isolated
R,Cs
B
R,Cs
Node A isolated
R,Cs
Ring
Ring
Node B isolated
R,Cs
Ring
B
C,Rs
B
C,Rs
B
C,Rs
Work. Span
Ring
B
C,Rs
Ring
Ring
B
C,RMs
B
C,Rs
B
C,RMs
Ring
Ring
B
C,Rs
A
COLUMN
Figure 320. Automatic protection for double ring failures (4F)

Ring, Work. Span (Working Span) and Prot. Span (Protection Span): the two failures combine to a single
failure and a single protection.
Figure 320. reports the failures network indications R, CMs and C, RMs in case of a tailend/headend
node mode. Hence the protection span indication will be served (see Figure 321. on page 380) instead
of having signaled the ring failure indication (see Figure 322. on page 381).
1AA 00014 0004 (9007) A4 ALICE 04.10
The indications reported in the Figure 320. are in fact related to a tailend/headend adjacent node mode.
The same modality is applied on the table of Figure 323. on page 383.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
379 / 448

Protection
span failure
ring failure
w
w
p
p
A
E
C
E
Protection
span failure
w
w
p
p
A
W
E
E
W
C
W
ring failure
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 321. Protection span and ring failure with a tailend/headend node mode (R, CMs)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
380 / 448
Protection
span failure

ring failure
w
w
p
p
A
E
C
E
Protection
span failure
w
w
p
p
A
W
E
E
W
C
W
ring failure
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 322. Protection span and ring failure with a tailend/tailend node mode (R, Cs)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
381 / 448
The first row at the top of the protection table (see Figure 323. on page 383) shows the Events at the
reference point. For each of them the associated Event is listed on the first column at the left of the table.
The first dual Event is a manual ring command on the reference point associated to a manual ring
on the same node at the same side, that is the same command repeated two times: no double command.
A manual ring on the reference point and a manual ring SSAN break the ring into two isolated sections,
no possible action only signalled Events: Bs. The same happens when is considered a manual ring
SSRN or OSRN. A manual ring on the reference point and on OSSN are antithetical: Bs. A manual
ring on the reference point and on OSAN dont break the ring into two separated sections (A node is
connected to B through D and C nodes) : B.
Manual span has a higher priority with respect to manual ring thus the result is: C. The C, Rs indication
means that the column is served while the row is only signalled.
Force ring has a higher priority with respect to manual ring, thus the result is: C.
Manual (force) ring and lockout ring SSSN are antithetical: the lockout ring command doesnt consider
the k1/k2 protocol while the manual ring makes use of it (bridge and switch) to change the signal
transmission (same reason is for manual (force) span and lockout span SSSN). In this case lockout ring
has a higher priority with respect to manual (force) ring and the result is: C. When manual (force) and
lockout commands are activated on separated points they coexist and are both served: B.
Manual (force) ring and lockout protection span follow the following role: both are served if related to
SSSN or OSAN. Otherwise the manual ring is disabled.
Manual span (second column) has a higher priority with respect to manual ring and the result is: R. Two
manual span commands on different points are accepted and served: B. A manual span and a Force ring
are antithetical, they break the ring into different sections. Force ring is priority respect to manual span:
C. Manual span and force span coexist if they dont point to the same span. Manual span and force span
SSSN or OSAN point to the same span and the result is: C.
Manual (force) span and lockout working ring/span coexist if they dont point to the same channels (lockout
working span SSSN) and are served: B. Lockout working span has a higher priority with respect to
manual span thus for lockout working span SSSN the result is: C. Manual (force) span and lockout
protection is the same as manual span and force span.
Automatic working ring and manual ring/span cannot be supported together, the automatic working ring
has a higher priority with respect to any manual command and the result is: R.
Similar consideration can be repeated for the other table results. The automatic protection span and
lockout protection span columns give the same results.
1AA 00014 0004 (9007) A4 ALICE 04.10
Automatic working ring and force span OSSN: this situation is similar to the one described in
Figure 321. on page 380. The network node failures are considered for automatic working ring column
unidirectional failures (tailend headend adjacent node mode). The ring failure cannot be signalled
because the communication protocol k1/k2 is busy to send the force command, it is only possible to serve
the protection span. The result is: C.RMs.
Force ring command and force span SSSN / OSAN point to the same signal and the final result is force
span: C. The others results can be easily deduced from the previously cited examples.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
382 / 448

The same reference schema is applied to describe dual generic Events where is considered both the
ring/span failure and the external command.
Reference
point
Other
points
Ring
SS
RN
SN
AN
Ring
SS SN
AN
RN
RN
SS SN
AN
Span
Force
OS SN
AN
RN
OS SN
AN
RN
Ring
Lockout Working
SN
AN
RN
SN
AN
RN
SN
SS AN
RN
Span
SN
AN
OS RN
Lockout Protection
Span
SS SN
1AA 00014 0004 (9007) A4 ALICE 04.10
R
R
R,Cs
R
R
B
R
R,Cs
R
B
Bs
C
C
C,Rs
C
C
C,Rs
R,Cs
R,Cs
R
B
B
B
R
B
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
B
B
B
C
B
Bs
Bs
B
RN
OS
Span
RN
SS SN
AN
SS
Span
Bs
RN
OS
Ring
AN
SN
AN
RN
SN
OS AN
RN
Automatic
C,Rs
C
C
C,Rs
B
B
B
B
B
B
R
R,Cs
R
B
Force
Lockout
Working
Protection
SN
AN
Span
Manual
OS
Manual
Ring
R
R
R
R
R
R
R
R
R
R
R
R
C
Bs
Bs
Bs
C
Bs
Cs
C,Rs
R,Cs
R
B
B
B
R
B
C,Rs
C,RMs
Bs
C,Rs
Working
Protection
Span
Ring
Span
R
R
R,Cs
R
R
R
R
R
R
R
R,Cs
R
R
R
R
R
R,Cs
R
B
B
B
R
B
R,Cs
R
B
B
B
R
B
C
C
C
C
C
C
C
B
B
B
C
B
R
R
R
R
B
B
B
B
B
C
C
C,Rs
C
C
C,Rs
Span
B
R
R,Cs
R
B
R,Cs
R
B
B
B
R
B
B
R
R,Cs
R
B
R
R
R,Cs
R
R
R,Cs
R,Cs
R
B
B
B
R
B
B
B
B
B
B
Ring
R
B
B
B
B
B
B
B
B
B
B
B
B
B
R
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
C
B
B
B
B
B
B
B
B
B
B
B
C
B
B
B
C
B
B
B
B
B
B
B
C
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
C
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
C
C,Rs
C
B
B
B
B
B
B
B
B
C,RMs
C,Rs
C,RMs
B
C
C,Rs
C
B
B
B
C
B
B
B
B
C,Rs
C
B
C,Rs
B(ring)
B
B
B
B(ring)
B
B(ring)
B
B
B
B(ring)
B
C
B
C,Rs
Span
B
B
B
B
R
B
B
B
B
B
B
B
R
B
B
B
B
B
C
B
Figure 323. Dual Events Protection table (4F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
383 / 448
19.5.4 Protection Status Visualization
1 Lockout Switching
2 Forced Switching
3 Automatic Switching (MSMSPRing protection for equipment/signal failure)
4 Manual Switching
5 Idle (regular operation without MSSPRing protection)
These protection states are represented with the following color state boxes:
Green: Active State, No Request condition
Red: Inactive State and any external or protection executed command (that has been served)
Yellow: ordered but not executed command (that has only been signalled= pending status)
Greyed: not available state box
Automatic switching and external commands are revertive: then when the Events have been cleared the
MSSPRing configuration comes back to its idle status.
The state boxes visualize the Node Condition Request as a consequence of the equipment/signal failure
or the external commands detected on the corresponding side (Event). The state boxes dont describe
the protection actions provided on the NEs.
The served Events (B/S=bridges and switches are executed and the network has been updated) are
completed B/S actions visualized as red box indications
The signalled Events (the K1/K2 protocol communicates to the network nodes what has happened) are
pending B/S visualized as yellow box indications.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 324. on page 385 visualizes the protection status with a served West manual ring command.
The protection status window is divided in different status fields: Schema description and status, Local
Conditions, Node Conditions and Protocol Exceptions. The first describes the network configuration and
application type and its status, the second gives the local external commands indications, the third the
Events results on the nodes and the fourth checks the k1/k2 ring protocol. The window is divided into
three parts: West, middle and East. On the West there are all the box indications corresponding to the
West protections and commands. In the middle WTRRing refers to West and East sides, No Request
corresponding to Idle Status, and Intermediate Node denotes that the protections and commands dont
concern the node involved. Thus the Manual Ring command visualizes Manual Ring on the local node
and Request Node Ring in the Local Conditions. The red color means that the command has been
served. A regular protocol Exceptions is represented with white boxes, a protocol alarm is signalled with
red boxes.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
384 / 448

The protection states network ring indications are:

Figure 324. Protection Status window with a Manual Ring command
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 325. on page 386 reports the Protection Status for external Force and Manual Commands in
a 3node ring (A, B, C), Figure 326. on page 387 shows the lockout statuses and Figure 327. on page
388 the automatic protection statuses.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
385 / 448
Node Conditions
Local Conditions
Request
Node
Ring
W
Force/
Manual
Ring
W
Request
Node
Ring
E
Intermediate
Node
Force/Manual
Ring W
Request
Node
Ring
E
Force/
Manual
Ring
E
w
w
p
p
3AL 81947 BA AA
448
w
w
p
p
Request
Node
Span
W
Force/
Manual
Span
W
Request
Node
Span
E
Force/Manual
Span W
A
B
C
Request
Node
Span
E
Force/
Manual
Span
E
Request
Node
Span
W
Force/Manual
Span E
A
B
C

Request
Node
Ring
W
Force/Manual
Ring E
Node
Reference
node: A
Intermediate
01
Intermediate
Node
ED
Intermediate
Node
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 325. Visualization of the Forced / Manual protection Statuses
SC.3:NE MANAGEMENT
386 / 448
01
Node Conditions
Local Conditions
Reference
node: A
Lockout
Ring W
Lockout Working
Ring W
Lockout
Span W
w
w
p
p
w
w
p
p
Lockout
Prot W
Lockout
Prot E
Lockout Working Lockout Protection Lockout Protection

Span W
Span W
Span E
A
B
C
A
B
C
A
B
C

Intermediate
Node
ED
Intermediate
Node
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 326. Visualization of the Lockout command Statuses
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
387 / 448
Node Conditions
Request
Ring
W
Request
Ring
E
Intermediate
Node
Request
Ring
E
w
w
p
p
w
w
p
p
Request Request
Span
Span
W
E
Turn off Turn off

No
No
Request Request

Request
Ring
W
Reference Signal fail/degrade Signal fail/degrade Signal fail/degrade Signal fail/degrade

Ring W
Ring E
Span Working W Span Protection W
node: A
A
B
C
A
B
C
A
B
C
A
B
C
Intermediate
Node
01
Intermediate
Node
ED
Intermediate
Node
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 327. Visualization of Automatic Protection Statuses
The automatic protection and alarm clearing is visualized on Figure 328. on page 389. The considered
network failures create on the adjacent nodes a tailend/headend node connection. The alarm clearing
can be executed firstly repairing the working link and after the protection one or vice versa.
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
388 / 448
Automatic Protection

Protection
Span Failure
Alarm Clearing
Turns
No
Requeston
adjacent
nodes + I
comes back
to the Idle status
Working
Ring Failure
Alarm Clearing
A
A + WTRring
After WTR time
it comes back to
the Idle status
Working
Span Failure
Alarm Clearing
B
B + WTR S
After WTR time
it comes back to
the Idle status
Figure 328. Automatic Protection and Alarm Clearing

Legenda of Figure 328. :
A = Request Node Ring (adjacent nodes) + I (remote nodes)
B = Request Node Span (adjacent nodes) + I (remote nodes)
WTR = Wait Time to Restore
I = Intermediate Node: a remote node that does not serve a Request Node Ring/Span
Idle = No Request and Active green indications only
A + WTRRing = If working span link is restored before the protection the status becomes Idle
without waiting the WTR time.
Considering the network of Figure 329. on page 390 and the reference point the West side of 4_ADM1
node (adjacent node is 4_ADM4), some network protection statuses of Figure 328. are hereinafter
reported.
Figure 331. on page 392 shows the starting regular condition (no request).
1AA 00014 0004 (9007) A4 ALICE 04.10
The span protection failure turns off the No Request indications to the adjacent nodes (Figure 332. on
page 393). Multiple span protection failures are always served and visualized as the couple of adjacent
nodes ADM1 ADM4 of Figure 332. on page 393.
The span working failure between ADM1 and ADM4 serves the Request Span protection on the adjacent
nodes (see Figure 333. on page 394). When the working span failure is cleared the WTRS (span) box
indication turns on (see Figure 334. on page 395): the previous automatic protection is frozen for the WTR
time. The operator can clear the WTR selecting WTR menu and the Clear WTR command. A protection
span failure and a working span failure on the same ADM side are equivalent to a ring failure and hence
served.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
389 / 448

Reference point
4_ADM1
W
4_ADM2
4_ADM4
W
w
w
p
p
4_ADM3
E
w
w
p
p
Figure 329. Ring network reference scheme

For dual ring failures it has be considered the previously table (here reported for a better comprehension
in Figure 330. on page 391).
1AA 00014 0004 (9007) A4 ALICE 04.10
When there are a protection span failure and a ring failure on remote node (RN), the ring failure cannot
be served but only signalled (see Figure 337. on page 398). With a working span failure and a ring failure
the working span protection has a higher priority with respect to the ring protection and only the working
span is served (see Figure 338. on page 399). Multiple ring failures are served (see Figure 339. on page
400) but the isolation nodes can be only signalled (see Figure 340. on page 401).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
390 / 448
Reference
point
Span
Other
points

SN
RN
SN
OS AN
RN
SN
SS AN
Span
Automatic
Working
Ring
SS AN
RN
SN
OS AN
RN
Protection
Span
Automatic
SN
SS AN
RN
SN
OS AN
RN
Working
Protection
C
R,CMs
R,Cs
R,CMs
C
R,Cs
Ring
B
B
B
Ring
B
Prot. Span
B
B
B
Prot. Span
B
Ring
Span
Ring
R,Cs
R,Cs
R,Cs
Ring
R,Cs
Node B isolated
B
Node A isolated
Ring
Node B isolated
Ring
B
C,Rs
B
C,Rs
B
C,Rs
Work. Span
Ring
B
C,Rs
Ring
Ring
B
C,RMs
B
C,Rs
B
C,RMs
Ring
Ring
B
C,Rs
Figure 330. Automatic protection for double ring failures

The visualized boxes on the Protection Status and Command window will be:
B, C, R : Request Node Ring/Span on the adjacent nodes and Intermediate Node on the remote nodes
visualized as red boxes
Ring, Work. Span (Working Span) and Prot. Span (Protection Span); the two failures combine to a single
failure and a single protection.
Prot. Span : turns off No Request on the adjacent nodes and Intermediate Node on the remote nodes.
The last ones visualized as red boxes (see Figure 332. on page 393).
Work. Span : Request Node Span on the adjacent nodes and Intermediate Node on the remote nodes
visualized as red boxes (see Figure 333. on page 394).
Ring : Request Node Ring on the adjacent nodes and Intermediate Node on the remote nodes
1AA 00014 0004 (9007) A4 ALICE 04.10
Node A (B) isolated : the isolated node is visualized with two yellow Request Node Ring East and West
box indications, both the adjacent nodes with a red Request Node Ring box indication, the remote nodes
with the red Intermediate Node indication (see Figure 340. on page 401).
Bs, Cs, Rs : Request Node Ring/Span on the adjacent nodes visualized as yellow boxes. The yellow
boxes are not visualized where is served Ring/Span protection.
R,CMs : turns off No Request on three adjacent nodes and Intermediate Node on the remote nodes.
The last ones visualized as red boxes.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
391 / 448
In case of protection span failure + ring failure SSRN the Protection span is only served: C,Rs (see
Working ring + working span OSSN: C,Rs (see Figure 338. on page 399).
Protection span + working ring SSAN: R,CMs. It corresponds to visualize the protection span between
ADM1ADM2, protection span between ADM2ADM3 and Intermediate node on ADM4.
1AA 00014 0004 (9007) A4 ALICE 04.10
The same considerations can be applied for the visualization of dual generic Events of Figure 323. on
page 383.
Figure 331. Regular condition (no request)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
392 / 448

Working ring +working ring SSRN are both served: Request Node Ring on the adjacent nodes

Figure 332. Protection Span failure between ADM1 and ADM4

The box color is white unless otherwise specified:
Active : green
1AA 00014 0004 (9007) A4 ALICE 04.10
Intermediate Node ADM2ADM3 : red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
393 / 448

Figure 333. Working Span failure between ADM1 and ADM4

Active : green
1AA 00014 0004 (9007) A4 ALICE 04.10
Request Node Span ADM4ADM1 : red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
394 / 448

Figure 334. Clearing of Working Span failure between ADM1 and ADM4
The WTR S West box lights on red after having inserted the signal incoming on the ADM1 (working link).
If was first restored the signal incoming on the ADM4 (working link) the ADM1WTRS East would be
lighted on.
Active : green
1AA 00014 0004 (9007) A4 ALICE 04.10

Request Node Span ADM4ADM1 : red
ADM1 WTRS West : red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
395 / 448

Figure 335. Ring failure between ADM1 and ADM4

Active : green
1AA 00014 0004 (9007) A4 ALICE 04.10
Request Node Ring ADM4ADM1 : red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
396 / 448

Figure 336. Clearing of Ring failure between ADM1 and ADM4

The WTR Ring box lights on red after having inserted the signal incoming on the ADM1 (working link).
If was first restored the signal incoming on the ADM4 (working link) the ADM1WTRRing would be lighted
on.
Active : green
1AA 00014 0004 (9007) A4 ALICE 04.10

ADM1 WTRRing : red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
397 / 448

Figure 337. Protection span failure between ADM12 + ring failure between ADM43
Active : green
1AA 00014 0004 (9007) A4 ALICE 04.10
Request Node Ring ADM4 West ADM3 East : yellow
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
398 / 448

Figure 338. Working span failure between ADM12 + working ring failure between ADM43
The yellow box indications would be visualized on both the adjacent nodes as the red box indications.
Unlikely the reduced number of protocol messages doesnt allow to visualize on the same node Request
node Span/Ring yellow and red box (ADM1 of Figure 338. ): the yellow indication is not visualized on the
node where the Protection is served.
1AA 00014 0004 (9007) A4 ALICE 04.10
Active : green
Intermediate Node ADM4ADM3, Request Node Span ADM2ADM1 : red
Request Node Ring ADM4 West, ADM3 East : yellow
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
399 / 448

Figure 339. Ring failure between ADM12 + ring failure between ADM34
Active : green
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
400 / 448

Figure 340. Ring failure between ADM14 and between ADM12 (ADM1=isolation node)
Active : green
Request Node Ring ADM4, Request Node Ring ADM2: red, on the side towards failure (in this case
ADM1)
1AA 00014 0004 (9007) A4 ALICE 04.10
Request Node Ring West and East ADM1 : yellow
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
401 / 448
19.5.5 Protocol Exceptions
Wrong APS Code: the communication K1/K2 code works improperly. That is unexpected protocol signal
is received on the multiplex section protection links.
Node ID mismatch: the connection nodes dont match the right identification sequence.
1AA 00014 0004 (9007) A4 ALICE 04.10
default K bytes: there is a wrong equipment/configuration provisioning and it is not possible to aim the
required MSSPRing protection.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
402 / 448

The protocol error indications are three.

19.6 MSSPRING Protection Status & Commands for 2F Terrestrial Application
19.6.1 2F MSSPRing protection commands

If a protection schema is Active it is possible to select one of the above commands.
Clicking on the Prot. Commands button in the MSSPRing >Main Dialog for MSSPRing management
(see Figure 259. on page 339), Figure 341. is opened.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 341. Protection states and commands Idle status (2F)

The working/protection span state boxes are not available (greyed) for the 2F MSSPRing architecture.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
403 / 448
w/p
A
w/p
w/p

In the MSPRing 2 Fiber configuration, the 18 working channels are inserted into the 916 protection
channels in the opposite side of the failure event as shown in Figure 342.
B
w/p
Ring Protection:
the working channels (AU4 1 to 8) are substituted
by the ring protection channels p (AU4 9 to 16)
( B on East side )
( A on West side )
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 342. Ring Protection (2F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
404 / 448

19.6.2 External commands (2F)

The external protection commands are: Lockout, Force, Exercise (not operative in current release),
Manual, WTR.
The lockout commands disable the MSSPRing management.
The lockout section presents six lockout commands, four operative (Figure 343. ). Each lockout command
is applicable on different points where the lockout actions has to be performed (Figure 344. ) and any
Lockout command is associated to a Release command to come back to the previous status.
Term Span identifies the section interested by the command, it doesnt assume the Span meaning of the
four fiber protection.
Figure 343. Lockout commands (2F)
West
w
p
p
w
East
w
p
p
w
1AA 00014 0004 (9007) A4 ALICE 04.10
w= working (AU4 1 to 8)
p=protection (AU4 9 to 16)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
405 / 448
The Events will be served if some actions (B/S=bridges and switches) are executed and the network
has been updated.
The Events will be signalled if the K1/K2 protocol communicates to the network nodes what has
happened, without execute actions.
A single ring failure is completely restored but not two ring failures. When are present multiple ring failures
the automatic B/S protection will try to maintain on all the possible connections.
The K1/K2 communication protocol MSSPRing is generated from the two nodes adjacent to Event via
the protection communication channels. A node is defined tail end when it firstly receives the Event,
the second node is defined headend when it receives back the protocol answer. Figure 345. shows the
association of tailend / tailend or headend / tailend.
Some network protection mechanisms are accepted or rejected depending on the end type (tail/head)
(lockout command,...).
w/p
w/p
w/p
w/p
Tailend
Tailend/Headend
Tailend
Figure 345. Tailend/Headend association

If the node is tailend, the lockout working ring command disable the protection MSSPRing
mechanisms, while if the node is headend, it serves the request node protection (protection not
disable). See Figure 346. on page 407.
1AA 00014 0004 (9007) A4 ALICE 04.10
With the lockout protecting span command and a ring failure, the ring protection is served if this ring failure
occurred along the same section; the ring protection is disabled if the ring failure has occurred in
another ring section.
On the contrary, with the lockout working ring command failure and a ring failure along a different section,
the ring protection is served (protection not disable). See Figure 347. on page 408
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
406 / 448

The protection events can be equipment/signal failure, signal degrade or external command or a
combination of them.
Lockout working
w/p

w/p
head
E
W
failure
W
tail
ring protection
Lockout working
A
failure
w/p
tail
W
w/p
E
W
head
no ring protection
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 346. Tailend/Headend protec. with a lockout working and a direction ring failure (2F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
407 / 448
W
no ring protection
Lockout working
Lockout working
failure
W
E
ring protection
Lockout working
failure
w/p
w/p
E
ring protection
w/p
W
E
w/p
w/p
w/p
E
failure
failure
w/p
Lockout protecting Span

Lockout protecting Span
w/p
E
E
no ring protection
Lockout working
failure
w/p
w/p
W
A
E
C
W
1AA 00014 0004 (9007) A4 ALICE 04.10
ring protection
Figure 347. Ring protection with a lockout and a ring failure (2F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
408 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
Combinations
of nonserved
failures and
external commands
01
W
E
3
B
w/p
w/p
A Node
A Node
Ring E
Lockout Working
Ring W
Lockout Working
E
2
w/p
w/p
ring protection on
the opposite side
if the ring failure
occurs between
AC or CB nodes
A Node
Ring W
Lockout Protection
ring protection on
the opposite side
if the ring failure
occurs between
AB or BC nodes
A Node
Ring E
Lockout Protection

Figure 348. shows a ring with three nodes and the actions performed by the lockout commands. This
command disables the acknowledgment of the signal failure/degrade on the receiving ports.
Figure 348. Lockout command and nonserved failures (2F)
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
409 / 448
Figure 349. Forced and Manual commands (2F)
Manual/force Ring East
A
W
w18
Manual/force Ring West
A1
E
W/P
p916
w18
W/P
p916
B1
w18
w18
p916
p916
w18
w18
p916
p916
W/P
w18
p916
w18
p916
W. 18 channels are substituted by P. 916 channels

on the opposite side for both adjacent nodes
Figure 350. Manual and Force Ring command (2F)
1AA 00014 0004 (9007) A4 ALICE 04.10
The Manual command is similar to Force command but it is at a lower priority level with respect to
automatic MSSPRing. The general priority scale that can be applied to solve antithetical situations
starting from the lowest priority level is: manual ring automatic working ring force ring lockout Working
Ring lockout Protecting Span.
When a force ring command is applied a next working failure is not able to modify the forced configuration
applied. That is because force ring command has a higher priority respect to the Automatic working
protection. In this condition the ring can be split according the location of command and event. Vice versa
the Manual protection is exceeded by the Automatic protection. Figure 351. on page 411 visualizes the
ring protection with a Force/Manual command and a signal failure. FSR is for Force Switching Request,
SFR is for Signal Failure Request.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
410 / 448

The Force command (Figure 349. ) executes a forced protection. The Force Ring command substitutes
the working channels (AU4 1 to 8) with the opposite direction protection channels (AU4 9 to 16) between
two adjacent nodes (Figure 350. ).
The Force Span command is not operative in 2 fiber MSSPring.
Force Ring East

failure

w/p
w/p
E
W
E
C
ring protection for FSR
Force Ring East
failure
A node is isolated
w/p
w/p
W
A
E
C
E
Manual Ring East

ring protection for SFR and FSR
failure
w/p
w/p
E
B
E
ring protection for SFR

Manual Ring East
failure
w/p
w/p
W
A
E
1AA 00014 0004 (9007) A4 ALICE 04.10
W
ring protection for SFR
Figure 351. Ring Protection with Force and Manual commands (2F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
411 / 448
Signal fail/degrade Signal fail/degrade

Ring W
Ring E
12 w. channels are
sobstituted by 34 p.
channels
B/S actions
w/p
34 w. channels are
sobstituted by 12 p.
channels
w/p
A
w/p

A node
A node
w/p
Figure 352. Automatic protection Bridge/Switch (2F)

Each command starts when the proper button is selected. A dialog box (Figure 353. ) has to be confirmed
before the command is performed.
From each command exists its own Release button to cancel the previously selected command and come
back to normal MSSPRing protection.
Figure 353. Example of confirmation dialog box
1AA 00014 0004 (9007) A4 ALICE 04.10
Clicking on the WTR command (of Figure 259. on page 339) next figure opens. If the WTR box, in the Local
Condition field of Figure 341. on page 403, becomes red a waiting time has been activated after repairing
the ring failure. The waiting time, set in the configuration menu, can be cleared selecting the Clear WTR
Ring command. A confirmation dialog box opens and, if the operator clicks OK, the WTR box turns off
and the protection status window is updated.
Figure 354. Clear WTR command (2F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
412 / 448
19.6.3 2F MSSPRing dual protection commands

In general dual contemporary Events can be:
two external commands
an external command and a ring failure
two contemporary ring failures
Dual Events can appear on the same side W/W (West/West) or E/E (East/East) (SS= same side) or on
the opposite side W/E or E/W (OS= opposite site) of the ring network. In the SS or OS the Events can
appear on the same node (SN) or on the different nodes (DN), the different node can be an adjacent node
(AN) or a remote node (RN). Figure 355. on page 414 depicts a clockwise ring network. The network
propagation K1K2 protocol signals are according to the following legend:
C
= served the column element
= served the row element
= served both row and column elements
Cs
= signalled (not served) the column element
Rs
= signalled (not served) the row element
Bs
= signalled (not served) both row and column element
1AA 00014 0004 (9007) A4 ALICE 04.10
when a command (Manual switch, Force switch) is neither served nor signalled, it is erased ( it is
not pending at the node).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
413 / 448

Reference point
clockwise
OS SN
SS SN
1
E
SS RN
4
OS RN
OS AN
2
W
w/p
E
w/p
SS AN
3
w/p
SS RN
w/p
OS RN
Figure 355. Ring network reference scheme (2F)

Figure 355. visualizes the ring reference scheme: the adjacent node (AN) is the node connected to the
reference point.
1AA 00014 0004 (9007) A4 ALICE 04.10
The automatic protection for dual ring failures is represented in Figure 357. on page 416.
Consider the network reference scheme of Figure 356. on page 415 with a tailend/headend alarm
propagation. In this figure are depicted the node switches for any reported double events.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
414 / 448
failure
w/p
1
E
w/p
E
W
E
SSAN
failure
failure
w/p
1
W
w/p
E
SSRN
3
failure
failure
w/p
1
failure
4
E
W
w/p
E
W
E
OSSN
failure
w/p
E
W
w/p
failure
W
E
OSAN
failure
w/p
E
W
w/p
W
E
OSRN
1AA 00014 0004 (9007) A4 ALICE 04.10
failure
Figure 356. Examples of Double ring failure
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
415 / 448
Reference
point
Automatic Protection Ring
Other
points
Automatic Protection Ring
SN
SS
OS
AN
Node 2 : isolated = Bs
Node 13 in switching for SF alarm =B
Node 4=intermediate
RN
Nodes 1,2,3,4 in switching for SF alarm =B
SN
Node 1: isolated=Bs
Nodes 2,4 in switching for SF alarm=B
Node 3= intermediate
AN
Node 1,2 in switching for alarm=B

Nodes 3,4 = intermediate
RN
Node 2: isolated=Bs
Node 1,3 in switching for SF alarm=B
Node 4 = intermediate
Figure 357. 2F Automatic protection (tail/head) for double ring failure visualization
The same reference Figure 355. on page 414 and Figure 356. on page 415 schemas are applied to
describe dual generic Events where both ring failures and external commands are considered.
The first row at the top of the protection table (Figure 358. on page 417) shows the Events at the
reference point. For each of them the associated Event is listed on the first column at the left of the table.
Two manual ring commands can be only signalled: Bs (Manual SSSN and OSAN commands give the
same ring protection switching and then both can be served).
Two Lockout commands are both always served: B.
Force command has priority with respect to the Manual one.
Automatic protection has priority with respect to the Manual command.
Force Ring and Automatic Protection (or two Force ring commands) are always served if they are not
applied on the SSSN. In this last case has to be considered the priority level. The behavior is that seen
for two automatic protection switching (Figure 356. on page 415).
Lockout working SSSN has priority with respect to Manual, Automatic protection and Force commands.
In the other cases, both commands are served (B).
Lockout protection SSSN / OSAN and Manual or Automatic or Force command are both served
because the switching SSSN / OSAN channels are not managed by the lockout protection: B.
1AA 00014 0004 (9007) A4 ALICE 04.10
Lockout protection SSAN / OSSN overrides the Manual or Automatic or Force command because the
lockout protection controls the switching channels of the same Node.
Lockout protection SSRN / OSRN and manual or automatic or force command: the lockout protection
prevents the working 18 channels from being inserted into the protecting 916 ones. The lockout
protection is served, because it has a higher priority, the ring protection will be only signalled (pending).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
416 / 448
Reference
point
Other
points
Automatic
Manual
Ring
Ring
Manual
OS AN
SN
RN
Force
Ring
SN
SS
AN
RN
SN
OS
AN
RN
Lockout Protecting
Lockout Working
SN
SS
AN
RN
SN
OS
AN
RN
SN
SS
AN
RN
SN
OS
AN
RN
Ring
Force
Ring
Lockout
Protection
Working
R
R
R
R
B
R
R
B
R
R
R
R
R
R
RCs
R
B
B
B
B
B
B
B
B
B
C
B
B
B
B
B
B
C
RCs
B
R
RCs
C
C
C
C
B
B
B
B
B
B
C
R
C
B
B
B
B
B
C
B
B
B
B
B
B
C
CRs
C
B
CRs
CRs
C
B
CRs
CRs
C
B
CRs
SN
SS AN
RN
Working
Bs
Bs
Bs
B
Bs
C
C
C
R
B
B
B
B
B
R
B
RCs
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 358. Tail / head dual Events Protection table (2F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
417 / 448
19.6.4 2F Protection Status Visualization
1 Lockout Switching
2 Forced Switching
3 Automatic Switching (MSMSPRing protection for equipment/signal failure)
4 Manual Switching
5 Idle (regular operation without MSSPRing protection)
These protection states are represented with the following color state boxes:
Green: Active State, No Request condition
Red: Inactive State and any external or protection executed command (that has been served)
Yellow: ordered but not executed command (that has only been signalled= pending status)
Greyed: not available state box.
Automatic switching and external commands are revertive: then when the Events have been cleared,
the MSSPRing configuration comes back to its idle status.
The state boxes visualize the Node Condition Request as a consequence of the equipment/signal failure
or the external commands detected on the corresponding side (Event). The state boxes dont describe
the protection actions provided on the NEs.
The served Events (B/S=bridges and switches are executed and the network has been updated) are
completed B/S actions visualized as red box indications
The signalled Events (the K1/K2 protocol communicates to the network nodes what has happened) are
pending B/S visualized as yellow box indications.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 359. on page 419 shows the protection status with a served East manual ring command. Any
protection status window is divided in different status fields: Schema description and status, Local
Conditions, Node Conditions and Protocol Exceptions. The first one describes the network configuration
and application type and its status, the second gives the local external commands indications, the third
the Events results on the nodes and the fourth one checks the k1/k2 ring protocol. The window is divided
into three parts: West, Middle and East. On the West there are all the box indications corresponding to
the West protections and commands. In the middle WTRRing refers to West and East sides, No
Request corresponding to Idle Status, and Intermediate Node denotes that the protections and
commands dont concern the node involved. The Manual Ring command visualizes Manual Ring on the
local node and Request Node Ring in the both Local Conditions adjacent East ADM1West ADM2
nodes, while the 3 and 4 nodes are Intermediate Node. The red color means that the command has been
served. A regular protocol Exceptions is represented with white boxes, a protocol alarm is signalled with
red boxes. The Prot. Unavailable indications are activated when a lockout protection command is applied
in a network node.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
418 / 448

The protection statuses ring network are:
ADM1:
ADM3:
ADM2:

ADM4:
Figure 359. Manual command applied at the Reference Point ring network Figure 356.
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 360. on page 420 reports the Protection Status for external Force and Manual commands in
a 3 node ring (A, B, C). Figure 361. on page 421 shows the lockout statuses and Figure 362. on page
422 the automatic protection statuses.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
419 / 448
Force/
Manual
Ring
W
Force/
Request
Node
Ring
E
w/p
Request
Node
Ring
E
w/p
A
w/p
w/p
Request
Node
Ring
W
Node
Request
Node
Ring
W
Manual
Ring
E
1AA 00014 0004 (9007) A4 ALICE 04.10
Node
Node Conditions
Force/Manual
Ring E
Intermediate
Local Conditions

Force/Manual
Ring W
Intermediate
Reference
node: A
Figure 360. Visualization of the Forced / Manual protection Statuses (2F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
420 / 448
Lockout
Ring W
Lockout
Ring E
w/p
w/p
A
w/p
Lockout
Prot W
Node
Conditions
1AA 00014 0004 (9007) A4 ALICE 04.10
w/p
Lockout
Prot E
Prot. Unavailable
Intermediate
Node
Prot. Unavailable
Intermediate
Node
Lockout Working Lockout Protecting Lockout Protecting

Ring E
Span W
Span E
Prot. Unavailable
Local
Conditions
Lockout Working
Ring W
Prot. Unavailable

Reference
node: A
Figure 361. Visualization of the Lockout command Statuses (2F)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
421 / 448
w/p
Request
Ring
E
w/p
A
w/p

Request
Ring
E
w/p
Request
Ring
W
Node
Request
Ring
W
Node
Intermediate
Node Conditions
Signal fail/degrade
Ring E
Intermediate
Signal fail/degrade
Ring W
Reference
node: A
Figure 362. Visualization of Automatic Protection Statuses (2F)
1AA 00014 0004 (9007) A4 ALICE 04.10
The WTR status is visualized on the side where the link has been repaired. The considered network
failures are related to a tailend/headend node connection. The WTR Clear command can be executed
by the user without waiting the WTR setting time.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
422 / 448
19.6.4.1 Double ring failure

The double ring failure visualization of Figure 356. on page 415 are here following reported.
ADM1:
ADM3:
ADM2:

ADM4:
Figure 363. Protection status with double ring failure (ref. pointSSAN)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 363. reports the protection status with double ring failure (reference pointSSAN. The node 2
isolated, the nodes 23 in switching and the node 4 Intermediate. The box color is white unless otherwise
specified:
Active: green
Request Node Ring West ADM3East ADM1: red (served)
Request Node Ring West ADM2East ADM2: yellow (pending)
Intermediate Node ADM4: red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
423 / 448
ADM1:
ADM3:
ADM2:

ADM4:
Figure 364. Protection status with double ring failure (ref. pointSSRN)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 364. reports the protection status with double ring failure (reference pointSSRN). The nodes
1, 2, 3, 4 are being switched for signal failure alarm and both the two signal failures are served. The box
color is white unless otherwise specified:
Active: green
Request Node Ring East ADM3East ADM1: red (switching for SF)
Request Node Ring East ADM4East ADM2: red (switching of the opposite nodes)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
424 / 448
ADM1:
ADM3:
ADM2:

ADM4:
Figure 365. Protection status with double ring failure (ref. pointOSAN)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 365. reports the protection status with double ring failure (reference pointOSAN). The nodes
1, 2 are being switched for signal failure alarm and both signal failures are served: B. The box color is white
unless otherwise specified:
Active: green
Request Node Ring West ADM2East ADM1: red (switching for SF)
Intermediate Node ADM3ADM4: red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
425 / 448
ADM1:
ADM3:
ADM2:

ADM4:
Figure 366. Protec. status with double ring failure (ref. pointOSAN) recovering to idle
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 366. reports the previous protection status with double ring failure (reference pointOSAN)
while the ring protection comes back to its idle status. The WTR (Wait To Restore) Ring on ADM1 node
becomes red to signal that the SF disappears at the reference point. The box color is white unless
otherwise specified:
Active: green
WTR Ring : red (to signal the SF recovering)
Request Node Ring West ADM2East ADM1: red
Intermediate Node ADM3ADM4: red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
426 / 448
19.6.4.2 Double external command or an external command and a ring failure

Some more significative double events of Figure 358. on page 417 are here following reported.
ADM1:
ADM3:
ADM2:

ADM4:
Figure 367. Double manual ring command (ref. pointSSAN)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 367. reports the protection status with double manual command (reference pointSSAN). Both
the commands can be only pending. The Request ring to 1,2,3 nodes becomes pending while the 4 node
is Intermediate node. The box color is white unless otherwise specified:
Active: green
Request Node Ring
Request Node Ring
Request Node Ring
Intermediate Node
ED
01
East ADM1 West ADM2: yellow (pending) for Manual Ring East ADM1
East ADM2 West ADM3: yellow (pending) for Manual Ring East ADM2
West ADM1 East ADM3: yellow (pending) for switching of the opposite nodes
ADM4: red
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
427 / 448
ADM1:
ADM3:
ADM2:

ADM4:
Figure 368. Double manual ring command (ref. pointOSAN)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 368. reports the protection status with double manual command (reference pointOSAN). Both
the commands can be served. The Request Manual ring to ADM1 (East) and to ADM2 opposite side
(West) collapses in the same manual command. Both the manual commands are served. The box color
is white unless otherwise specified:
Active: green
Request Node Ring East ADM1 West ADM2: red (served)
Intermediate Node ADM3, ADM4: red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
428 / 448
ADM1:
ADM3:
ADM2:

ADM4:
Figure 369. Manual ring and Lockout Protection (ref. pointSSSN)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 369. reports the protection status with a manual command and a lockout protection (reference
pointSSSN). Both the manual and the lockout commands are visualized to the same ADM1 node
(East). Both the commands are served because the bridge/switch points are different. The box color is
white unless otherwise specified:
Active: green
Request Node Ring East ADM1 West ADM2: red (served)
Intermediate Node ADM3, ADM4: red
Manual Ring and Lockout Prot. commands East ADM1: red
Prot. Unavailable East ADM1 : red
N.B.
The Prot. Unavailable is not propagated on West ADM2 node because on West ADM2 the
protection switching has been executed.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
429 / 448
ADM1:
ADM3:
ADM2:

ADM4:
Figure 370. Manual ring and Lockout Protection (ref. pointSSRN)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 370. reports the protection status with a manual command and a lockout protection (reference
pointSSRN). The manual command is pending while the lockout command is served. The box color
Active: green
Manual Ring command East ADM1: yellow
Request Node Ring East ADM1 West ADM2 : yellow (pending)
Request Node Ring West ADM1 East ADM2 : yellow (pending) for switching of the opposite nodes
Lockout Prot. command: East ADM3 : red
Prot. Unavailable East ADM3 and West ADM4: red (served)
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
430 / 448
ADM1:
ADM3:
ADM2:

ADM4:
Figure 371. Automatic working ring and Manual Ring (ref. pointOSAN)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 371. reports the protection status with a ring failure and a manual ring command (reference
pointOSAN). The automatic protection has a higher priority with respect to the manual command and
then it has been served. The box color is white unless otherwise specified:
Active: green
Request Node Ring East ADM1 West ADM2 : red (served)
Intermediate Node ADM3 ADM4 : red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
431 / 448
ADM1:
ADM3:
ADM2:

ADM4:
Figure 372. Automatic working ring and Force Ring (ref. pointSSAN)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 372. reports the protection status with a ring failure and a force ring command (reference
pointSSAN). The ADM2 is isolated and the force command is pending. The box color is white unless
otherwise specified:
Active: green
Request Node Ring East ADM1: red (served) the West ADM1 switching is applied for SF
Request Node Ring West ADM3: red (served) the East ADM3 switching is applied for the force command
Request Node Ring West ADM2, East ADM2: yellow (pending) the ADM2 is isolated
Intermediate Node ADM4 : red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
432 / 448
ADM1:
ADM3:
ADM2:

ADM4:
Figure 373. Automatic working ring and Lockout working Ring (ref. pointSSSN)
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 373. reports the protection status with a ring failure and a lockout working command (reference
pointSSSN). The Lockout command has a higher priority with respect to the automatic protection
switching and then only the lockout command has been served. The box color is white unless otherwise
specified:
Active: green
Lockout Ring command East ADM1: red
Request Node Ring East ADM1 West ADM2 : red (served)
Intermediate Node ADM3 ADM4 : red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
433 / 448
ADM1:
ADM3:
ADM2:

ADM4:
Figure 374. Automatic working ring and Lockout Protection (ref. pointOSRN)
1AA 00014 0004 (9007) A4 ALICE 04.10
The lockout protection has a higher priority with respect to the automatic ring protection. The box color
Active: green
Lockout Prot. command West ADM3: red
Prot. Unavailable West ADM3 East ADM2 : red (lockout protection is served)
Request Node Ring East ADM1 West ADM2 : yellow (automatic protection is pending)
Intermediate Node ADM4 : red
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
434 / 448

20 ATM/IP/ETH CONFIGURATION
20.1 Introduction
This chapter describes the operations necessary for the ATM/IP/Ethernet boards creation in the
Equipment view and the ATM/IP/Ethernet TTPs creation; as a matter of fact ATM/IP/Ethernet boards does
not crate TTPs when they are configurated.
For this NE and in current release only Gigabit Ethernet boards are available.
The ATM/IP/Ethernet board creation is performed (following the same rules of all the other SDH/PDH ports
as explained in para. 9.2 on page 98) when a CT user sets an ATM/IP/Ethernet board.
For the TTPs creation refer to para. 20.2 on page 435 where all the operation are explained.
The operational sequence to follow to manage ATM/IP/Ethernet crossconnection is:
1)
ATM/IP/Ethernet board declaration (Equipment Set);
2)
ATM/IP/Ethernet board TTPs creation (VC4XV, VC44c TTP, VC4 TTP);
3)
TTPs crossconnection (refer to para. 15.3 on page 229).
20.2 Ethernet board TTPs creation

20.2.1 Gigabit ETHERNET board
In current release two architectures are possible to provide Gigabit Ethernet ports:
[1]
GIGABIT board (GETHMB) standalone.

With this architecture can be configurated up to 4 TPs (VC4XV type).
The same rule above described are applicable to 1660SM when the GIGABIT board (GETHMB)
is equipped in normal slot (i.e. slot with a throughput of 622 Mbit/s).
It is possible to reach a max. concatenation level equal to 7 per port; of course this means that there
is only one VC4XV with concatenation level =1 available for another port and no resources for the
last two ports present on the board.
For more details read the Gigabit Ethernet description reported in the Technical Handbook.
[2]
GIGABIT board (GETHMB) + GBIT Access (GETHAG).

With this architecture can be configurated up to 4 TPs (VC4XV type) on the GETHAG access card
and up to 4 TPs (VC4XV TTP type) on the GETHMB main board taking into account that the
maximum throughput for the couple must not exceed 1.2 Gbit/s; the concatenation level per port
can be from 1 to 7.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Gigabit Ethernet TPs creation follows these rules.

Select ATM/IP/ETH Configuration option from the Configuration menu to open the ATM/IP/Ethernet
ports Configuration (see Figure 375. on page 436).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
435 / 448

initial empty fields
with defined TPs
Figure 375. Example of Ethernet TPs creation

The ATM/IP/Ethernet ports Configuration window is filled with notebook pages (initially blank).
The user can create a new port, delete an existing one and change port associations (that means
modify the STM1 number and STM1 Time Slot on ATM/IP/Ethernet ports already created) via the three
buttons contained in the notebook page.
When the user want to create a new TPs he can select an empty row, then in the Selected Item sections,
he can fill the field Signal choosing among the available options and push theCreate button.
Note: in case of concatenated VC TP creation, before to push on Create button it is also necessary to
choose the Concatenation Level value; after creation command new fields and a new button appear.
The STM1 Number and the STM1 Time Slot are automatically assigned.
If the user want to change the port attribute association he can select a filled row, then in the Selected
Item section he can change the fields STM1 number and STM1 Time Slot and than push the Time
Slot Sw. button.
The Ctrl Path Act. button allows to change the state of the concatenated virtual VCs that could be Idle
or active.
Click on Ctrl Path Act. button a new window will be opened (see Figure 376. on page 437); for details about
the meaning of the field refer to para. 11.5.7 on page 139.
1AA 00014 0004 (9007) A4 ALICE 04.10
To delete a port the user can select a row and push Delete button.
To close the dialog box click on the Close push button.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
436 / 448

Figure 376. Control Path activation window (example)
1AA 00014 0004 (9007) A4 ALICE 04.10
It is possible to see the VCs created on the ETHERNET board as above explained by selecting the relevant
row in the ATM/IP/Ethernet configuration window and then click on the Navigate button; Figure 377.
on page 437 shows an example.
Figure 377. ETHERNET port view example
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
437 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
438 / 448

21 SOFTWARE MANAGEMENT
21.1 Generalities and descriptions
The Craft Terminal provides a set of functions which allow software packages manipulation within NEs.
The downloading operation consists in the establishment of session between the NE and a software
server for the purpose of file transfer.
Actions can then be performed on the NE software version as update and activation operation, or roll back
to the previous software version operation. In this way the NE can follow the product evolution with in
service equipment.
The same function is used during maintenance phase, to update spare boards for substitution after
troubleshooting.
The operations that can be undertaken in this section are:
display Software Download Information

initiate / Abort Software Package Download
manage Software Packages within NEs, activating the downloaded Software Package or coming
back to the previous condition
A backup/restore can be also done on the MIB of the NE. Indeed the MIB can be saved to or restored
from the mass storage of the Craft Terminal.
The software download general principle is represented in the following figure.
Software Management
OPERATOR
MANAGER
Download
Control
Event
Report
AGENT
NE
Software Downloading
OPERATOR
Transfer
Request
SERVER
CLIENT
Binary & Data

Files
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 378. Software Download general principle
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
439 / 448
21.1.1 Naming Conventions
Software Package: Software Package stands for a piece of software which can be executed by an
NE of a particular type. It consists in one or more Software Units and a Descriptor File. A software
package is identified by its name, release, version and edition.
On the NE (i.e. once downloaded) a software package can be:
the active version: the software package currently running on the NE

a standby version: a software package which is neither the active version nor the boot version
Software Unit: A Software Unit is a part of a software package which can be either executable code
or a data segment of a particular board within an NE. A software unit is also identified by its name,
release, version and edition.
Descriptor File: A Descriptor File contains information about the software package it belongs to and
lists the composing software units. Each software package must have a descriptor file otherwise it
would not be possible to interpret the content of the package.
Software Management Function: The Software management function offers information about all
current software packages present in an NE. Indicators enable software management (running
package, activated package, etc...).
The following software version states are available:
Commit (active) version: the software version currently running on the NE.
Standby version: is a software version which has been downloaded on the NE but which is
not in the active state.
Two main functions are involved in the software downloading:
Software Download Manager function

Software Download Server function
The Software Download Manager function takes the downloading and management requests of the
operator and sends them to the NE. Thus, this function enables a download process to be initiated and
monitored by the operator. It manages the NE software releases and initiates software download
operations.
1AA 00014 0004 (9007) A4 ALICE 04.10
The Software Download Server is only responsible for fulfilling the requests received from NEs and
performing software package file transfer operations to the NE.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
440 / 448

The naming conventions used for Download Management are the following:
21.2 Software download operative sequence

Two main different operative condition are defined for this Equipment:
First installation of a 1670SM.

The NE is received without the relevant software install. The software download must be done
as described in the SIBDL section of this Handbook.
Updating a 1670SM with an already installed software.

Follow the operative indications of para. 21.2.1 on page 441.
21.2.1 Software Download upgrade

In order to update the following procedure is to be done as explained in the next steps:
a)
Install on the PC the NE Software Package present in the CDROM (refer to 1320CT Basic
Operators Handbook for details).
b)
Open a session on CT application (startup of the application, start supervision and NE login).
c)
Check the present status of the software on a selected NE.
1AA 00014 0004 (9007) A4 ALICE 04.10
Download should not be performed in presence of unstable alarms

d)
Open the Download menu as for para. 21.3 on page 442.
e)
Select the new software package in the server and triggers the download process, as presented at
para. 21.4 on page 443. A message will indicate the completed download.
f)
Activate the package as presented at para. 21.5 on page 445.
g)
Check that the activated package is in the Commit status.
h)
If problems are found with the new activated package, activate the previous software package
(revertback operation) to come back to the previous condition and then try to repeat the procedure.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
441 / 448
21.3 Software Download Manager menu

All the software download operations are carried out from the software download manager.
Figure 379. Equipment view
To display the software download manager menu from the main view, select the NE on which you want to
perform download operations (see Figure 379. ) then select the Download pull down menu.
The following menu is displayed:
1AA 00014 0004 (9007) A4 ALICE 04.10
Figure 380. Download menu
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
442 / 448

21.4 Init download

You can request the NE to start / abort a software download operation. After selecting the desired NE you
must choose an available software package and then start the download process. All these operations
can be performed from the SW downloading dialogue box.
Select the Init download option from the Download pull down menu.
The Software download initiate dialogue box is opened (see for example the following figure):
Figure 381. SW Downloading dialogue box (example)

The following fields are available to search a specific package:
Server filter: to enter the server name selected

Package filter: to enter the package name selected
To use the filter and display the selection, push on Apply filter(s) button. The SW packages existing on
the Craft Terminal are displayed.
1AA 00014 0004 (9007) A4 ALICE 04.10
In the next field the list of the packages is displayed:
Server: name of the server

Package: name of the package
Version: version number of package
Click on Forced push button to set the forced download attribute: then all software units of the Descriptor
file have to be downloaded. Otherwise only the units with different software version will be loaded.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
443 / 448
Click on the OK button to start the download. From the confirmation dialogue box that opens, you can
confirm or cancel the download. If you confirm the operation, the SW Downloading dialogue box then
disappears and the Software download in Progress dialogue box is displayed (see Figure 382. ) from
which you can if necessary abort the software download.
You can monitor the download progress by means of the Software in Progress dialogue box which also
enables you to possibly abort the current download.
Figure 382. Software download in progress (example)
1AA 00014 0004 (9007) A4 ALICE 04.10
The Software download in Progress dialogue box displays the name and type of the NE and the SW
package name, the total of bytes, the current percentage and the current file which is being downloaded.
Click on the Abort button to abort the complete download transaction. From the confirmation dialogue
box that opens you can confirm or cancel the abort.
Click on the Close button to close the SWDL Work in Progress dialogue box at the end of the software
download.
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
444 / 448

If you dont want to execute the download, click on the Cancel push button of the Software download
initiate dialogue box to close it.

21.5 SW package Activation and Units information

This item permits to activate the downloaded software package and to get information about the software
of the various units of the equipment.
The operator is able to get information about the software package of the NE at any moment, even if no
download operations have been performed previously.
For this, select the Units info option from the Download pull down menu.
The following dialogue box is opened.
Figure 383. Software Package Information dialogue box

The SW Information dialogue box displays the name and type of the NE, and the respective package name
and status of the committed and (if existing) the uncommitted software.
You can select one software package by clicking on the name.
1AA 00014 0004 (9007) A4 ALICE 04.10
NOTE:
ED
before activating new SW Package verify that both HCMATRIX units have been locked
(Lock State) at least 20 minutes before.
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
445 / 448
Software package: name, release, version, edition of the package

Operational state: enabled or disabled
Activation date: date and hour of the last activation
Vendor: the supplier of the product
Current state\Action: commit or standby and with the option button; none/Force/Activate/Delete
current state = standby means the package is not active on the NE
current state = commit means the package is active on the NE
action = (none) means no action to do
action = activate serves to activate the selected SW package
action = force (item not operative)
Select the Activate option of the CurrentState\Action field, to activate the Software package.
The Sw units Det. button allows to give more information about a selected software package.
Clicking on it, the following window is displayed:
Figure 384. Detail of units info (example)
1AA 00014 0004 (9007) A4 ALICE 04.10
Clicking on [] symbol behind each software package all details disappear.

In Figure 383. on page 445 when you click on the:
ED
OK button you close dialogue box

Cancel button you close the SW Information dialogue box
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
446 / 448

The following fields are displayed:

21.6 Mib management

This function allows to make a backup and/or a restore of the Mib (MIB is a data base pertaining the
configuration of the equipment).
Select the Mib management option from the Download pull down menu. The following window is displayed:
Figure 385. NE MIB management

The following fields are displayed:
Available backups on local server: gives the list of the backups available on the Craft Terminal.
Backup name: to enter the new backup name.
Three push buttons allow to choose the action with click on:
Backup: performs the backup on the CT of the Mib present on the NE.
Restore: this function allows the managing system to restore the NE configuration database of the
managed system. Only one restore operation can be performed at the same time on a given NE.
Delete: this action allows to delete a backup of the NE database. The NE is not involved in this action.
The only effect is to delete the selected backup version stored in a specific directory of the FT server.
To activate an already restored MIB you click on Activate button. Only at this point it becomes operative
on the NE, with an automatic restart of the NE software.
1AA 00014 0004 (9007) A4 ALICE 04.10
To exit of the NE MIB management window, you click on Close button.

To save or load the MIB to/from an external disk follow the indication of the 1320CT Basic Operators
Handbook using the menu options of the Network Element Synthesis (NES).
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
447 / 448
1AA 00014 0004 (9007) A4 ALICE 04.10
END OF DOCUMENT
ED
01
SC.3:NE MANAGEMENT
3AL 81947 BA AA
448
448 / 448

3 Ne MNGT

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

3 Ne MNGT

Transféré par

Droits d'auteur :

Formats disponibles

1AA 00014 0004 (9007) A4 ALICE 04.

All rights reserved. Passing on and copying of this

1670SM REL. 4.2 C.T. OPERATORS HANDBOOK

2 GENERAL INTRODUCTION ON VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 NE MANAGEMENT GENERAL CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1670SM REL. 4.2

1AA 00014 0004 (9007) A4 ALICE 04.10

6 EXTERNAL INPUT AND OUTPUT POINTS MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 COMMUNICATION AND ROUTING MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All rights reserved. Passing on and copying of this

4.2 NE Time management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All rights reserved. Passing on and copying of this

9.7 Show supporting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10 BOARD VIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

1AA 00014 0004 (9007) A4 ALICE 04.10

12 EQUIPMENT PROTECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

1AA 00014 0004 (9007) A4 ALICE 04.10

15 CROSS-CONNECTION MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

All rights reserved. Passing on and copying of this

14.3.4 Dynamic View Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

17 PERFORMANCE MONITORING MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

1AA 00014 0004 (9007) A4 ALICE 04.10

21 SOFTWARE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

All rights reserved. Passing on and copying of this

18.2.11 Show Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

LIST OF FIGURES AND TABLES

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Figure 51. MESA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Figure 105. View of Monitoring Operations (example 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Figure 213. OH Search TP for creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Figure 267. Squelching table of Node A, West side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

Figure 375. Example of Ethernet TPs creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

All rights reserved. Passing on and copying of this

1320CT Basic Operators Handbook

1AA 00014 0004 (9007) A4 ALICE 04.10

Refer to the Section Introduction manual.

1AA 00014 0004 (9007) A4 ALICE 04.10

All rights reserved. Passing on and copying of this

2 GENERAL INTRODUCTION ON VIEWS AND MENUS

2.1 EMLUSM view organization

Severity alarm synthesis

Domain alarm synthesis

1AA 00014 0004 (9007) A4 ALICE 04.10

Domain alarm synthesis

All rights reserved. Passing on and copying of this

1AA 00014 0004 (9007) A4 ALICE 04.10