ISA_ES1_ES4 CT Operator’s Handbook
224
3AL 89871 AAAA Ed.01 ISA–ES1/ES4 CT Operator’s Handbook Alcatel ES1/ES4 Ethernet Switching System ISA ES1/ES4 ISA–ES1/ES4 Rel.1.1
Transcript of ISA_ES1_ES4 CT Operator’s Handbook
3AL 89871 AAAA Ed.01
ISA–ES1/ES4 CT Operator’s Handbook
AlcatelES1/ES4Ethernet Switching System
ISA ES1/ES4
ISA–ES1/ES4 Rel.1.1
3AL 89871 AAAA Ed.01
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
1
01
/3AL 89871 AAAA AA
218
218
ISA–ES1ES4 REL 1.1 CT OPERATOR’S HDBK
TABLE OF CONTENTS
LIST OF FIGURES AND TABLES 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HANDBOOK GUIDE 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 General information 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Handbook applicability 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Purpose of the handbook 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4 Handbook Structure 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5 Handbook Configuration Check 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.1 List of the editions and of modified parts 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5.2 Notes on Ed. 01A 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5.3 Notes on Ed. 01 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 PRODUCT-RELEASE HANDBOOKS 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 SAFETY NORMS AND LABELS 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 First aid for electric shock 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Norms and labels 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Products, product-releases, versions and Customer Documentation 21. . . . . . . . . . . . . . 4.2 Handbook supply to Customers 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Aims of standard Customer Documentation 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4 Handbook Updating 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1 Changes introduced in the same product-release (same handbook P/N) 22. . . . . . . . . . . . 4.4.2 Supplying updated handbooks to Customers 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.3 Changes due to a new product-release 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 Customer documentation supplied on CD–ROM 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.1 Contents, creation and production of a CD–ROM 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.2 Use of the CD–ROM 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.3 CD–ROM identification 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.4 CD–ROM updating 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 ACRONYMS AND DEFINITIONS 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Acronyms 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR
01A 040625 G. PARLADORI ITAVE A. GRADIA ITAVE
01 040831 G. PARLADORI ITAVE A. GRADIA ITAVE
ISA–ES1ES4 REL. 1.1 CT OPERATOR’S HDBK
D.E. MARAZZA
D.E. MARAZZA
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
2
01
/3AL 89871 AAAA AA
218
218
5.2 Definitions 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INTRODUCTION 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 INTRODUCTION 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Scope 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Reading rules 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 System Generalities 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Ethernet Technique 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2 Virtual Concatenation and LCAS 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.3 Management software 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.4 Ethernet over SDH Management 53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 ES–CT main functionalities 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1 Supervision 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.2 Configuration 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.3 Diagnosis 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.4 MIB Management 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.5 Transmission 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.6 Connection 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.7 Performance Monitoring 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 SOFTWARE PRODUCT AND LICENSE DELIVERED TO THE CUSTOMER 57. . . . . . . . . . . . . . . 2.1 Software product and licenses description 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Software products, licenses and part numbers 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SOFTWARE INSTALLATION 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 ES SOFTWARE INSTALLATION 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Scope of the procedure 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Start–up of the Personal Computer 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Host Computer Configuration 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1 Verification of IP address assignment for the host computer 62. . . . . . . . . . . . . . . . . . . . . . 3.4 Summary procedure for ES software installation 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 ES–CT Installation procedure 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6 NE–ES package installation procedure 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7 Software Uninstallation procedure 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7.1 ES–CT Uninstallation 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8 NE–ES software downloading 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9 Start–Up of the ES Craft Terminal management software 95. . . . . . . . . . . . . . . . . . . . . . . . . .
MANAGEMENT 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 CRAFT TERMINAL FOR ES MANAGEMENT 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Introduction 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Summary procedure for ES Management 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Main view 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1 Resources TREE area (A1) 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4 List of the menus options 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1 “Views” menu introduction 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.2 Configuration menu introduction 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.3 Diagnosis menu introduction 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.4 Supervision menu introduction 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.5 Mib–Management menu introduction 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.6 Transmission menu introduction 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.7 Connection menu introduction 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
3
01
/3AL 89871 AAAA AA
218
218
4.4.8 Performance menu introduction 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.9 Help menu introduction 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 Supervision management 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.1 Access state (allow or inhibit ES–Craft access) 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.2 Set Manager list 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.3 Restart ISA (Not operative) 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6 Generic and common functions 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.1 Configuration –> Options 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.2 DIALOG WINDOWS PRESENTATION: “FullWindow” and “TabbedWindow” 118. . . . . . . . . 4.6.3 Views –> Search 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.4 Views –> Print 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7 Diagnosis and Alarms Configuration 122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.1 Configuration –> Alarms Severity (ASAP management) 123. . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.2 Set Alarms Severities 126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.3 Allow/Inhibit Alarms Notifications 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.4 Alarms re–synchronization 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.5 Alarms Surveillance (Diagnosis –> Alarms option) 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.6 Event Log Browser (Diagnosis –> Log Retrieval) 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.7 Diagnosis –> Navigation to EML–USM 133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.8 MIB Management 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.1 Backup/Restore DB 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.2 Compare two Backup Files (not operative) 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.9 Transmission 135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.1 Ethernet Ports denomination and numbering 135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.2 Configuration –> Traffic Descriptor –> ETS Traffic Descriptor 136. . . . . . . . . . . . . . . . . . . . . 4.9.3 Transmission: ISA : Configure ISA 141. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.4 Transmission: ISA : ISA Properties 142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.5 ISA: application table in the Transmission context 143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.6 Transmission: Ethernet Port : Configure (LOCAL) Ethernet Port 144. . . . . . . . . . . . . . . . . . . 4.9.7 Transmission: Ethernet Port : (LOCAL) Ethernet Port Properties 149. . . . . . . . . . . . . . . . . . . 4.9.8 Transmission: Ethernet Port : Configure (REMOTE) Ethernet Port 150. . . . . . . . . . . . . . . . . 4.9.9 Transmission: Ethernet Port : (REMOTE) Ethernet Port Properties 157. . . . . . . . . . . . . . . . . 4.9.10 Transmission: Ethernet Port : Substitute Server Layer 158. . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.11 Transmission: Ethernet Port : Substitute Port Type 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.12 Transmission: Ethernet Port : Create ETS InFlow 160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.13 Transmission: Ethernet Port : Create ETS InFlow/ColorProfile (not yet available) 161. . . 4.9.14 Transmission: Ethernet Port : Create ETS OutFlow 163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.15 Create ETS OutFlow / VlanManagement (not available in current release) 164. . . . . . . . . 4.9.16 Transmission: ETS InFlow : Modify ETS InFlow 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.17 Transmission: ETS InFlow : ETS InFlow Properties 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.18 Transmission: ETS OutFlow : Modify ETS OutFlow 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.19 Transmission: ETS OutFlow : ETS OutFlow Properties 165. . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.20 Transmission: ETS InFlow : Delete ETS InFlow 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.21 Transmission: ETS OutFlow : Delete ETS OutFlow 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.22 Transmission: ETS InFlow : Create Eth2ETS Classifier 167. . . . . . . . . . . . . . . . . . . . . . . . . 4.9.23 Transmission: Classifier : Modify Classifier 168. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.24 Transmission: Classifier : Classifier Properties 168. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.25 Transmission: Classifier : Delete Classifier 168. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.26 Transmission: Bridge : Configure (R)STP Bridge 169. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.27 Transmission: Bridge : (R)STP Bridge Properties 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.28 Transmission: Bridge Port : Configure (R)STP Bridge Port 172. . . . . . . . . . . . . . . . . . . . . . . 4.9.29 Transmission: Bridge Port: (R)STP Bridge Port Properties 173. . . . . . . . . . . . . . . . . . . . . . . 4.9.30 Transmission: (R)STP Port : Configure (R)STP Port 174. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9.31 Transmission: (R)STP Port: (R)STP Port Properties 176. . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
4
01
/3AL 89871 AAAA AA
218
218
4.10 Connection 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10.1 Ethernet Port: application table in the Connection context 178. . . . . . . . . . . . . . . . . . . . . . . 4.10.2 Connection: Ethernet Port : Create Ets XC One Step 179. . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10.3 Connection: ETS InFlow : Create Ets XC 181. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10.4 Connection: ETS InFlow : Modify Ets XC 183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10.5 Connection: ETS InFlow : Ets XC Properties 183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10.6 Connection: ETS InFlow : Delete Ets XC 184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10.7 Connection: ETS OutFlow : Create Ets XC (not operative) 185. . . . . . . . . . . . . . . . . . . . . . . 4.10.8 Connection: ETS OutFlow : Modify Ets XC (not operative) 185. . . . . . . . . . . . . . . . . . . . . . . 4.10.9 Connection: ETS OutFlow : Ets XC Properties 185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10.10 Connection: ETS OutFlow : Delete Ets XC 185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10.11 Connection: (R)STP Switch Management (not operative) 185. . . . . . . . . . . . . . . . . . . . . . . 4.10.12 Ethernet SWITCH: Setting the FDB ageing time 186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.11 Performance 187. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11.1 Performance: Ethernet Port : Configure Eth. Aggr. 187. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11.2 Performance: Ethernet Port : Eth Aggr. Properties 188. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11.3 Performance: ETS InFlow : Configure InFlow (not operative) 190. . . . . . . . . . . . . . . . . . . . . 4.11.4 Performance: ETS InFlow: InFlow Properties (not operative) 191. . . . . . . . . . . . . . . . . . . . . 4.11.5 Performance: ETS OutFlow: Configure OutFlow (not operative) 193. . . . . . . . . . . . . . . . . . 4.11.6 Performance: ETS OutFlow: OutFlow Properties (not operative) 194. . . . . . . . . . . . . . . . . . 4.11.7 PM Data Results (HISTORY and MAINTENANCE) 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MAINTENANCE 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 MAINTENANCE 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Introduction 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 General trouble–shooting flow–chart for ISA–ES boards 203. . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Alarms, states and commands on ISA–ES board front cover 205. . . . . . . . . . . . . . . . . . . . . . 5.4 Troubleshooting by means of the ES Craft Terminal 206. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Alarms/states organization in the main view 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 Alarms synthesis indications 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3 Alarms indications in the Resources TREE area (A1) 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.4 Alarms indications in the resource properties 212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.5 Alarms relevant to ES–Boards observable on SDH–CT 213. . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.6 Alarms Surveillance (AS) 214. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.5 ISA–ES Units replacement 218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6 SOFTWARE UPGRADING/DOWNGRADING 218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
5
01
/3AL 89871 AAAA AA
218
218
LIST OF FIGURES AND TABLES
FIGURESFigure 1. ISA–ES subsystem, protocol stacking 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2. Bridge representation example and relevant FDB table 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3. ES System into SDH network, example 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4. VLAN Classification–Identification–Aggregation (example) 40. . . . . . . . . . . . . . . . . . . . . . . . . Figure 5. Stacked VLAN management (example) 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 6. Engineered Point–to–Point Ethernet over SDH link Example 42. . . . . . . . . . . . . . . . . . . . . . . Figure 7. Spanning Tree example 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 8. Some examples of Bridges and Ports roles in RSTP network 44. . . . . . . . . . . . . . . . . . . . . . . Figure 9. Ethernet MAC 802.3 frame format 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 10. Ethernet “Tagged” MAC 802.3 frame format 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 11. Ethernet “Stacked VLAN” frame format 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 12. TCI Field format (802.1Q VLAN Tag) 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 13. GFP Framing (from G.7041/Y.1303) 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 14. Ethernet encapsulation into GFP frame (from G.7041/Y.1303) 48. . . . . . . . . . . . . . . . . . . . . Figure 15. Ethernet/LAPS encapsulation (ITU–T X.86) 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 16. Ethernet over SDH Framing 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 17. Virtual Concatenation (example) 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 18. Protocol stack for ATM/MPLS/Ethernet over SDH management 53. . . . . . . . . . . . . . . . . . . . Figure 19. Example of management of an SDH network with SDH and ES traffic 54. . . . . . . . . . . . . . Figure 20. OSI and IP addressing example 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 21. Initial presentation intermediate screen 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 22. Selecting installation procedure (1st step) 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 23. Craft Terminal master setup, list of detected Components on the media 66. . . . . . . . . . . . . Figure 24. Selecting CraftTerminal components (1st step) 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 25. Software License agreement 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 26. Existing previous ES–CT version uninstall 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 27. Uninstall confirmation 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 28. Uninstall previous ES–CT version successfully completed 70. . . . . . . . . . . . . . . . . . . . . . . . Figure 29. Choose destination folder for ES–CT installation 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 30. Setup type 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 31. Program Folder denomination 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 32. Start copying files and current settings summary 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 33. Setup in progress, temporary windows sequence presentation 75. . . . . . . . . . . . . . . . . . . . . Figure 34. Successive installation, temporary windows presentation 76. . . . . . . . . . . . . . . . . . . . . . . . . Figure 35. Installation procedure menu window (2nd step) 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 36. Craft Terminal master setup, list of detected Components on the media 77. . . . . . . . . . . . . Figure 37. Selecting SNMPCT component 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 38. Existing different SNMPCT release to be uninstalled 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 39. Existing previous similar release to be maintained: “REPAIRE” 80. . . . . . . . . . . . . . . . . . . . Figure 40. SNMP CT Add On setup 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 41. SNMPCT setup in progress temporary window 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 42. Maintenance Finished 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 43. SNMPCT installation completed 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 44. Selecting installation procedure (end step) 85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 45. Descriptor files administration 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 46. Software Package Administration–ES service specific 87. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 47. File–Browser for Software Package installation 87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 48. Software Package Administration – create Enhanced OMSN 88. . . . . . . . . . . . . . . . . . . . . . Figure 49. Software Package Administration – add ES service 89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 50. Add/Remove Programs icon selection 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
6
01
/3AL 89871 AAAA AA
218
218
Figure 51. Add/Remove Programs view 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 52. Delete confirmation (example) 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 53. Delete completed (example) 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 54. Download Initiate (example) 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 55. NE Software package activation (example) 94. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 56. 1320CT software start–up 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 57. NES view example 96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 58. Logon view 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 59. Main view 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 60. TREE area example 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 61. Spontaneous information message example 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 62. Set Manager list 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 63. Configuration –> Options 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 64. Configuration –> Options – Program (“Full Window Mode” example) 118. . . . . . . . . . . . . . . Figure 65. Configuration –> Options – Program (“Tabbed Window Mode” example) 118. . . . . . . . . . . . Figure 66. Views –> Search 120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 67. Views –> Print 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 68. ASAP Management dialogue box. 123. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 69. ASAP: severities profile example 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 70. ASAP: Set Alarm Severities (example) 127. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 71. Alarms Surveillance (“ISA Alarms” example) 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 72. Log Retrieval: Event (Filter example) 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 73. Log Retrieval: Event (Report example) 131. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 74. Log Retrieval: Alarm (Filter example) 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 75. Log Retrieval: Alarm (Report example) 133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 76. MIBmanagement –> Backup/Restore DB 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 77. Configuration: ETS Traffic Descriptor (example) 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 78. Create an ETS Traffic Descriptor (example) 137. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 79. Configure ISA 141. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 80. ISA Properties 142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 81. ISA–ES node: transmission application table 143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 82. Configure (local) Ethernet Port 146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 83. List of Protocol Profile 147. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 84. Create Protocol Profile 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 85. (Local) Ethernet Port Properties 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 86. Configure (remote) Ethernet Port (GFP) 153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 87. Configure (remote) Ethernet Port (LAPS) 154. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 88. Rate Limiting Combination (VC4 case) 156. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 89. Virtual Concatenation Granularity manager (VC12 case) 156. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 90. Inconsistency error on Port Configuration 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 91. (Remote) Ethernet Port Properties 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 92. Substitute Server Layer (from GFP to LAPS) 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 93. Substitute Server Layer (from LAPS to GFP) 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 94. Substitute Port Type (from ETS to ETB) 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 95. Substitute Port Type (from ETB to ETS) 159. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 96. Create ETS InFlow 161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 97. List of Color Profile (not available in current release) 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 98. Create Color Profile (not available in current release) 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 99. Create ETS OutFlow 163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 100. Create VLAN Management (not available in current release) 164. . . . . . . . . . . . . . . . . . . . . Figure 101. Delete ETS InFlow 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 102. Create Eth2ETS Classifier 167. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 103. Configure (R)STP Bridge 169. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 104. STP Instances 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
7
01
/3AL 89871 AAAA AA
218
218
Figure 105. (R)STP Bridge Properties 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 106. Configure (R)STP Bridge Port 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 107. (R)STP Bridge Port Properties 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 108. Configure (R)STP Port 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 109. (R)STP Port Properties 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 110. Ethernet Port: Connection application table 178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 111. Create Ets XC “OneStep” 180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 112. Error message on “Create Ets XC OneStep” 180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 113. Create Ets XC 182. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 114. Ets XC Properties 183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 115. Delete Ets XC 184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 116. Ethernet SWITCH: Connection application table 186. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 117. Ethernet Port Configure Monitoring (example) 187. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 118. Ethernet Port Monitoring Properties (example) 188. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 119. InFlow Configure Monitoring (example) 190. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 120. InFlow Monitoring Properties (example) 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 121. OutFlow Configure Monitoring (example) 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 122. OutFlow Monitoring Properties (example) 194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 123. PM data results in tabular mode (example) 197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 124. General Flow–chart for ISA–ES board troubleshooting 204. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 125. Alarms/statuses organization in the main–view 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 126. TREE area example 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 127. Example of EthernetPort Properties alarms 212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 128. Example of alarms reported in the “resource information area A3” 213. . . . . . . . . . . . . . . . Figure 129. AlarmsSurveill.–“Counter Summary” window(“ISA Alarms” example) 214. . . . . . . . . . . . . . Figure 130. AlarmsSurveill.–“Alarm Sublist” window (“ISA Alarms” example) 215. . . . . . . . . . . . . . . . . .
TABLESTable 1. Handbook configuration check 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2. Handbooks common to all Alcatel NetworkElements supporting ES functionality 15. . . . . . . Table 3. Handbooks common to all the Alcatel Network Elements using 1320CT platform 15. . . . . . . Table 4. Handbooks related to the specific Network Element 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5. Documentation on CD–ROM 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6. Ethernet layer stack over SDH 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7. Software product part number 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8. Software licenses part numbers 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 9. Alarms & Severities association in predefined ASAPs 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 10. TrafficDescriptor, PolicingMode and ColorProfile for INFLOW resource 138. . . . . . . . . . . . . . Table 11. Prioritization for OUTFLOW resource with “Stacked–VLAN management” 139. . . . . . . . . . . . Table 12. Alarms colors and Severity association 208. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 13. Colors of the Management States when in “ab–normal” condition (alarmed) 209. . . . . . . . . . Table 14. Severity Alarms Synthesis indications 209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 15. Domain Alarm Synthesis indication 209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 16. Management States Control Panel. 209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 17. Alarms Surveillance information general description 216. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 18. “Probable Cause” of alarms and relevant maintenance actions 217. . . . . . . . . . . . . . . . . . . . .
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
8
01
/3AL 89871 AAAA AA
218
218
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
9
01
/3AL 89871 AAAA AA
218
218
HANDBOOK GUIDE
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
10
01
/3AL 89871 AAAA AA
218
218
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
11
01
/3AL 89871 AAAA AA
218
218
1 HANDBOOK STRUCTURE AND CONFIGURATION CHECK
1.1 General information
WARNING
ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims theimplied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liablefor errors contained herein or for damages, whether direct, indirect, consequential, incidental, orspecial, in connection with the furnishing, performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for informationpurposes only and are subject to change without notice. They do not represent any obligation on thepart of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied,reproduced or disclosed to a third party without written consent.
1.2 Handbook applicability
PRODUCT ANV P/N FACTORY P/N
ES1 – ES4 ––– –––
PRODUCT RELEASE VERSION (N.B.) ANV P/N FACTORY P/N
ES1/ES4 1.1 – ––– –––
This handbook is not applied to a specific Network Element product-release.
It is a common handbook for several equipments of different product-releases using ES1 and ES4products.
The use of this handbook is indicated in the list of the ”Handbooks related to the specific softwareapplication”, in the Technical and Operator’s Handbooks of the Network Element.
Being the document dedicated to a set of equipments, screens are inserted as ”example” and can beextracted from any of the referred equipments.
N.B. See NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS on page 22.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
12
01
/3AL 89871 AAAA AA
218
218
1.3 Purpose of the handbook
This handbook describes the operations concerning commissioning and operation that the operators mustcarry out as indicated by the software application(s) referred to in this handbook (see para. 1.2 on page11).
This handbook must be used together with the associated Technical and Operator’s Handbooks and doesnot replicate information contained into them.In particular, all cautions relevant to safety, rules for EMC and ESD, as well as warnings regardingoperations that may cause damages to the equipment, are not duplicated here, but must be retrieved fromthe Technical Handbook.
When using this handbook it is assumed that the Operators know:
• the structure (hardware composition) and all the possible operating modes of the equipment(product-release) this handbook refers to.
• how to use a PC and the Windows ambient applications.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
13
01
/3AL 89871 AAAA AA
218
218
1.4 Handbook Structure
This handbook has been edited according to the suggestions given by the ”Code of Practice” for InstructionHandbooks issued by the European Broadcasting Union (EBU RACC. R29/82).
This handbook is divided into the following main topics as described in the table of contents:
HANDBOOK GUIDE: It contains general information about structure and use of thehandbook, and safety norms on using the equipments.
INTRODUCTION: It contains the ISA–ES system generalities.
SOFTWARE PRODUCT: It contains the software packages list, the software licenses list,and their relevant part–numbers.
SOFTWARE INSTALLATION: It reports the procedures to install the ISA–ES software.
MANAGEMENT: It describes all the views presented by the ES–CraftTerminal,including all the information needed to set the various ISA–ESparameters and configurations.
MAINTENANCE: It contains all the details for periodic checks, faults locations,repair procedures, and restore to normal operations.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
14
01
/3AL 89871 AAAA AA
218
218
1.5 Handbook Configuration Check
1.5.1 List of the editions and of modified parts
Legend
n = new part p =proposal partm = modified part d =deleted part
Table 1. Handbook configuration check
EDITION 01A 01 02 03 04 05
INTRODUCTION
1. INTRODUCTION n m
2. SOFTWARE PRODUCT n m
SOFTWARE INSTALLATION
3. ES SOFTWARE INSTALLATION n m
MANAGEMENT
4. MANAGEMENT n m
MAINTENANCE
5. MAINTENANCE n m
Note: the sections relevant to HANDBOOK GUIDE are not subjected to configuration check.
1.5.2 Notes on Ed. 01A
Ed.01A, created in June 2004, is a provisional issue of this handbook.
1.5.3 Notes on Ed. 01
Ed.01, created in August 2004, is the first validated and officially released issue of this handbook.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
15
01
/3AL 89871 AAAA AA
218
218
2 PRODUCT-RELEASE HANDBOOKS
The list of handbooks given here below is valid on the issue date of this Handbook andcan be changed without any obligation for ALCATEL to update it in this Handbook.
Some of the handbooks listed here below may not be available on the issue date of thisHandbook.
The standard Customer Documentation in the English language for the equipment whoseproduct-release-version is stated in para.1.2 on page 11 consists of the following handbooks:
Table 2. Handbooks common to all Alcatel NetworkElements supporting ES functionality
REF HANDBOOK ANV Part No.FACTORY
Part No.
THIS
HDBK
[1]
ISA–ES1/ES4 Rel.1.1Operator’s Handbook
3AL 89871 AAAA –.–.–
[1]Providing general information and operational procedures common to all AlcatelNetwork Elements performing ES1 and ES4 functions.
Table 3. Handbooks common to all the Alcatel Network Elements using 1320CT platform
N.B. 1320CT and Q3CT–P are equivalent terms
REF HANDBOOK ANV Part No.FACTORY
Part No.
THIS
HDBK
[2]
1320CT 3.xBasic Operator’s Handbook
3AL 79551 AAAA 957.140.042 N
[2]It provides general information and operational procedures common to all 1320CT(Craft terminal) of Alcatel InfoModel Network Elements.
[3]
1330AS Rel. 6.5Operator’s Handbook
3AL 88876 AAAA –.–.–
[3]It provides detailed information and operational procedures regarding the AlarmSurveillance software embedded in the 1320CT software package.
ELB Rel. 2.x Operator’s Handbook 3AL 88877 AAAA –.–.–
[4]Providing detailed information and operational procedures regarding the EventLog Browser software embedded in the 1320CT software package.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
16
01
/3AL 89871 AAAA AA
218
218
Table 4. Handbooks related to the specific Network Element
HANDBOOK ANV Part No.FACTORYPart No.
THISHDBK
Technical Handbook NB NB
Provides information regarding Equipment description, Installation, Turn–On, Test andoperations, Maintenance and Hardware setting documentation.
OMSN CT Operator’s Handbook NB NB
Provides NE screens and operational procedures for the SDH management.
N.B. This Handbook is always supplied with Technical Handbook and CT Operator’s Handbookdedicated to the specific Network Element. Each manual has its own Part number.
Table 5. Documentation on CD–ROM
See para.4.5 on page 23.
REF CD–ROM TITLE ANV Part No. FACTORY Part No.
[5]
DCP ES1/ES4 1.1 CD–ROM–DOC EN 3AL 89874 AAAA –.–.–
[5]It contains, in electronic format, the following handbooks: REF. [1]
DCP–1320CT 3.x CD–ROM–DOC EN 3AL 79552 AAAA 417.100.032
[6]It contains, in electronic format, the following handbooks: REF. [2] to [4].Envisaged after the release of all handbooks
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
17
01
/3AL 89871 AAAA AA
218
218
3 SAFETY NORMS AND LABELS
3.1 First aid for electric shock
Do not touch the patient with bare hands until the circuit has been opened.
Open the circuit by switching off the line switches. If that is not possible, protect yourself with drymaterial and free the patient from the conductor.
ARTIFICIAL RESPIRATION
It is important to start mouth to mouth resuscitation at once and seek doctor help immediately.
TREATMENT OF BURNS
This treatment should be used after the patient has regained consciousness. It can also be employed whilethe artificial respiration is being applied (in this case there should be at least two persons present).
WARNING:
• Do not attempt to remove his clothing from the burnt parts;
• Apply dry gauze on the burns;
• Do not apply ointments or other oily substances.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
18
01
/3AL 89871 AAAA AA
218
218
Mouth to mouth resuscitation method
1
2
3
4
5
6
Lay the patient supine with his arms parallel with the body, if the patient is layingon an inclined plane, make sure that his stomach is slightly lower than his chest.Open the patient’s mouth and check that there are no extraneous bodies in hismouth (dentures, chewing–gum etc.),
Kneel beside the patient level with his head. Puta hand under the patient’s head and one underhis neck (see fig.) Lift the patient’s head and letit recline backwards as far as possible
Shift the hand from the patient’s neck to is chin:place your thumb between his chin and hismouth, the index along his jawbone, and keep theother fingers closed together (see fig.). Whileperforming these operations take a good supplyof oxygen by taking deep breaths with yourmouth open.
With your thumb between the patient’s chin andmouth keep his lips together and blow into hisnasal cavities (see fig.)
While performing these operations observe if thepatient’s chest rises (see fig.) If not it is possiblethat his nose is blocked: in that case open thepatient’s mouth as much as possible by pressingon his chin with your hand, place your lips aroundhis mouth and blow into his oral cavity. Observeif the patient’s chest heaves. This secondmethod can be used instead of the first evenwhen the patient’s nose is kept closed bypressing the nostrils together using the hand youwere holding his head with. The patient’s headmust be kept sloping backwards as much aspossible.
Start with ten rapid expirations, hence continue at a rate of twelve/fifteenexpirations per minute. Go on like this until the patient has regainedconsciousness, or until a doctor has ascertained his death.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
19
01
/3AL 89871 AAAA AA
218
218
3.2 Norms and labels
Refer to the Technical Handbook associated to ALCATEL’s designed and manufactured equipmentto obtain the following information:
– COMPLIANCE WITH EUROPEAN NORMS.
– SAFETY RULES
• General rules
• Harmful optical signals
• Risk of explosion
• Moving mechanical parts
• Heat–radiating Mechanical Parts
– ELECTROMAGNETIC COMPATIBILITY
– ELECTROSTATIC DISCHARGERS (ESD)
– EQUIPMENT LABELS
Identical or similar information on Personal Computer, Work–Station etc., other than ALCATEL’s, loadedwith software applicatives described in this Handbook, is supplied in the Constructor’s technicaldocumentation.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
20
01
/3AL 89871 AAAA AA
218
218
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
21
01
/3AL 89871 AAAA AA
218
218
4 GENERAL ON ALCATEL CUSTOMER DOCUMENTATION
4.1 Products, product-releases, versions and Customer Documentation
A ”product” is defined by the network hierarchical level where it can be inserted and by the whole ofperformance and services for which it is meant.A ”product” evolves through successive ”product-releases” which are the real products marketed fortheir delivery at a certain ”product-release” availability date.
So, a ”product–release” defines a set of hardware components and a software package which, as a whole,identify the possible network applications and the equipment performance which the specific”product-release” has been designed, engineered and marketed for.
In some cases a ”product-release” has further development steps, named ”versions”, that are born toimprove or add some performance (mainly software) with respect to the previous version, or for bug fixingpurposes.
A ”product-release” has its own standard Customer Documentation, composed by one or morehandbooks.
A new ”version” of a ”product-release” may or may not produce a change in the status of the CustomerDocumentation set, as described in para.4.4 on page 22.
4.2 Handbook supply to Customers
Handbooks are not automatically delivered together with the equipment they refer to.The number of handbooks per type to be supplied must be decided at contract level.
4.3 Aims of standard Customer Documentation
Standard Customer Documentation, referred to hereafter, must be always meant as plant-independent.Plant-dependent documentation, if envisaged by the contract, is subjected to commercial criteria as faras contents, formats and supply conditions are concerned (plant-dependent documentation is notdescribed here).
Standard hardware and software documentation is meant to give the Customer personnel the possibilityand the information necessary for installing, commissioning, operating and maintaining the equipmentaccording to Alcatel–Telecom Laboratory design choices.In particular the contents of the handbooks associated to the software applications focus on theexplanation of the man-machine interface and of the operating procedures allowed by it.
Consequently, no supply to the Customers of design documentation (like software source programs,programming tools, etc.) is envisaged.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
22
01
/3AL 89871 AAAA AA
218
218
4.4 Handbook Updating
The handbooks associated to the ”product–release” are listed in para.2 on page 15.Each handbook is identified by:– the name of the ”product-release” (and ”version” when the handbook is applicable to the versions
starting from it, but not to the previous ones),– the handbook name,– the handbook P/N,– the handbook edition (usually first edition=01),– the handbook issue date. The date on the handbook does not refer to the date of print but to the date
on which the handbook source file has been completed and released for the production.
4.4.1 Changes introduced in the same product-release (same handbook P/N)
The edition and date of issue might change on future handbook versions for the following reasons:
– only the date changes (pointed out in the Table of Contents) when modifications are made to theeditorial system not changing the technical contents of the handbook.
– the edition, hence the date, is changed because modifications made concern technical contents. Inthis case:• the table in para. 1.5 on page 14 indicates the section(s) edition change;• in affected chapters of each section, revision bars on the left of the page indicate modifications
in text and drawings (this is done after the first officially released and validated version).
Changes concerning the technical contents of the handbook cause the edition number increase (e.g. fromEd.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition ofa version character (e.g. from Ed.02 to Ed.02A).
NOTES FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operator’s Handbooks) are notmodified unless the new software ”version” distributed to Customers implies man–machineinterface changes or in case of slight modifications not affecting the understanding of theexplained procedures.Moreover, should the screen prints included in the handbook contain the product-release’s”version” marking, they are not replaced in the handbooks related to a subsequent version, ifthe screen contents are unchanged.
4.4.2 Supplying updated handbooks to Customers
Supplying updated handbooks to Customers who have already received previous issues is submitted tocommercial criteria.By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue(supplying errata–corrige sheets is not envisaged).
4.4.3 Changes due to a new product-releaseA new product-release changes the handbook P/N and the edition starts from 01. In this case the modifiedparts of the handbook are not listed.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
23
01
/3AL 89871 AAAA AA
218
218
4.5 Customer documentation supplied on CD–ROM
In the following ’CD–ROM’ means ’Customer Documentation on CD–ROM’
4.5.1 Contents, creation and production of a CD–ROM
In most cases, a CD–ROM contains the documentation of one product–release(–version) and for a certainlanguage.In some other cases, the same CD–ROM can contain the documentation of differentproduct–release(–version)s for a certain language.
As a general rule:
– CD–ROMs for Network Management products do not contain:
• the Installation Guides
• the documentation of system optional features that Customers could not buy from Alcateltogether with the main applicative SW.
– CD–ROMs for Network Elements products do not contain the documentation of system optionalfeatures (e.g. System Installation Handbooks related to racks that Customers could not buy fromAlcatel together with the main equipment).
A CD–ROM is obtained collecting various handbooks and documents in .pdf format. Bookmarks andhyperlinks make the navigation easier. No additional information is added to each handbook, so that thedocumentation present in the CD–ROMs is exactly the same the Customer would receive on paper.
The files processed in this way are added to files/images for managing purpose and a master CD–ROMis recorded.
Suitable checks are made in order to have a virus–free product.
After a complete functional check, the CD–ROM image is electronically transferred to the archive of theProduction Department, so that the CD–ROM can be produced and delivered to Customers.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
24
01
/3AL 89871 AAAA AA
218
218
4.5.2 Use of the CD–ROMThe CD–ROM can be used both in PC and Unix WS environments.
The CD–ROM starts automatically with autorun and hyperlinks from the opened “Index” document permitto visualize the .pdf handbooksOther hyperlinks permit to get, from the Technical handbooks, the specific .pdf setting documents.
In order to open the .pdf documents Adobe Acrobat Reader Version 4.0 (minimum) must have beeninstalled on the platform.The CD–ROM doesn’t contain the Adobe Acrobat Reader program. The Customer is in charge of gettingand installing it.ReadMe info is present on the CD–ROM to this purpose.
4.5.3 CD–ROM identificationEach CD–ROM is identified:
1 ) by the following external identifiers, that are printed both on the booklet and the CD–ROM uppersurface:– the name of the ”product–release(s)” (and ”version” when the CD–ROM is applicable to
the versions starting from it, but not to the previous ones),– a writing indicating the language(s),– the CD–ROM P/N (Factory P/N 417.xxx.xxx x and ANV P/N),– the CD–ROM edition (usually first edition=01)
2 ) and, internally, by the list of the source handbooks and documents (P/Ns and editions) by whosecollection and processing the CD–ROM itself has been created.
4.5.4 CD–ROM updating
The list of source handbook/document P/Ns–editions indicated in previous para. 4.5.3 point (2 ), inassociation with the CD–ROM’s own P/N–edition, is also loaded in the Alcatel–Information–System as astructured list.Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive system,a check in the Alcatel–Information–System is made, indicating the list of CD–ROMs that must be updatedto include the new editions of these handbooks/documents.This causes the planning and creation of a new edition of the CD–ROM.Updating of CD–ROMs always follows, with a certain delay, the updating of the single handbookscomposing the collection.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
25
01
/3AL 89871 AAAA AA
218
218
5 ACRONYMS AND DEFINITIONS
5.1 Acronyms
ACD: Access Control Domain
ADM: Add and Drop Multiplexer
AIS: Alarm Indication Signal
ALMAP: Alcatel Management Platform
ARP: Address Resolution Protocol
AS: Alarm Surveillance
ASAP: Alarm Severity Assignment Profile
ATM: Asynchronous Transfer Mode
AUI: Attachment Unit Interface
BE: Best Effort
BGP: Border Gateway Protocol
BM: Bandwidth Manager
BW: BandWidth
CAC: Connection Admission Control
CCITT: Telegraph and Telephone International Consultative Committee
CD: Current Data
CD–ROM: Compact Disc Read Only Memory
CE: Customer Edge (device)
C&I: Classification and Identification
CFI: Canonical Field Identifier
CIR: Committed Information Rate
CoS: Class of Service
CR–LDP: Constraint based Routing Label Distribution Protocol
CRC: Cyclic Redundancy Check
CT: Craft Terminal
DCCM: Data Communication Channels Multiplex
DCCR: Data Communication Channels Regeneration
DCN: Data Communications Network
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
26
01
/3AL 89871 AAAA AA
218
218
DHCP: Dynamic Host Configuration Protocol
DiffServ: Differentiated Service
DS: Differentiated Service
DSC: Different Speed Connection
DTL: Designed Transit List
EC: Equipment Controller
ECC: Embedded Communication Channels
EFCI: Explicit Forwarding Congestion Indication
EML: Element Management Layer
EMLIM: Element Management Layer Information Manager
ENE: External Network Element
EOS: Ethernet Over SDH
EPD: Early Packets Discarding
EPS: Equipment Protection Switching
ES: Ethernet Switch
ESI: End System Identifier
E or ETH: Ethernet
ETB: Ethernet Bridge
ETP: External Termination Point
ETS: Ethernet Transparent Service (or Ethernet Transport Service)
EXP: MPLS Experimental field
FAD: Functional Access Domain
FCS: Frame Check–Sum
FDB: Filtering Data Base
FE: Fast Ethernet
FEC: Forwarding Equivalence Class
FTN: FEC to NHLFE
Gbit/s: Gigabits per second
GE or GbE: Gigabit Ethernet
GFC: Generic Flow Control
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
27
01
/3AL 89871 AAAA AA
218
218
GFP: Generic Framing Procedure
GNE: Gateway Network Element
GOSIP: Government Open System Interconnection Profile
GUI: Graphical User Interface
HD: History Data
HDLC: High Level Data Link Control
HMI: Human Machine Interface
HOL: Head Of Line
I/F: Interface
ICI: Inter Carrier Interface
ICMP: Internet Control Message Protocol
IGMP: Internet Group Management Protocol
ID: Identifier
IEEE: Institute of Electrical and Electronics Engineers
IGP: Interior Gateway Protocol
IM: Information Manager
IP: Internet Protocol
IPCP: IP Control Protocol
ISA: Integrated Service Adapter (or: IP, SDH and ATM)
ISDN: Integrated Services Digital Network
ISO: International Standard Organization
ITU–T: International Telecommunication Union – Telecommunication sector
JRE: Java Runtime Environment
Kbit/s: Kilobits per second
L3: Layer 3
LAN: Local Area Network
LAPS: Link Access Procedure over SDH
LCP: Link Control Protocol
LCAS: Link Capacity Adjustment Scheme
LDP: Label Distribution Protocol
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
28
01
/3AL 89871 AAAA AA
218
218
LER: Label Edge Router
LSP: Label Switched Path
LSR: Label Switch Router
LVC: Lower Order Virtual Container
MAC: Medium Access Control
MAU: Medium Access Unit
Mbit/s: Megabits per seconds
MIB: Management Information Base
MPLS: Multi Protocol Label Switching
MRU: Maximum Receive Unit
MTU: Maximum Transmit Unit
MS: Multiplex Section
MSN: Multi Service Node
NAD: Network Access Domain
NAP: Network Access Point
NAT: Network Address Translation
NCP: Network Control Protocol
NE: Network Element
NES: Network Element Synthesis
NHLFE: Next Hop Label Forwarding Entry
NIM: Non Intrusive Monitoring
NML: Network Management Layer
NSAP: Network Service Access Point
OAM: Operation, Administration and Maintenance
OID: Object Identifier
OMP: OSPF Optimized Multi Path
OMSN: Optical Multi Service Node
OS: Operations System
OSI: Open System Interconnection
OSPF: Open Shortest Path First
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
29
01
/3AL 89871 AAAA AA
218
218
P2P: Point To Point
P2MP: Point To Multi–Point
para: paragraph
PC: Personal Computer
PDH: Plesiochronous Digital Hierarchy
PI: Physical Interface
PIR: Peak Information Rate
PLM: PayLoad Mismatch
PM: Performance Monitoring
PMV: Performance Monitoring View
POS: Packet Over Sonet/SDH
PPP: Point–to–Point Protocol
PR_EA (or PREA): Packet Ring, Edge Aggregator
PSTN: Public Switched Telephone Network
QoS: Quality of Service
RA: Received Aggregate
RAM: Random Access Memory
RAS: Remote Access Service
RCC: Routing Control Channel
RDI: Remote Defect Indication
RFC: Request For Comment
RIP: Routing Information Protocol
RSVP: Resource Reservation Protocol
RSVP–TE: Resource Reservation Protocol – Traffic Engineering
RSTP: Rapid Spanning Tree Protocol
Rx: Receive direction
SC: Shelf Controller
SCSI: Small Computer Serial Interface
SDH: Synchronous Digital Hierarchy
SEC: SECurity
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
30
01
/3AL 89871 AAAA AA
218
218
SL: Signal Label
SLA: Service Level Agreement
SNMP: Simple Network Management Protocol
SP: Service Provider
STP: Spanning Tree Protocol
SVLAN: Stacked Virtual LAN
SW: Software
TA: Transmitted Aggregate
TBD: To Be Defined
TCA: Threshold Crossing Alarm
TCI: Tag Control Information
TCP/IP: Transmission Control Protocol / Internet Protocol
TD: Traffic Descriptor
TLS: Transparent LAN Service
TMN: Telecommunications Management Network
TN: Telecommunications Network
TP: Termination Point
TPD: Tail Packets Discarding
TP_T: Transmission Path Termination
TP/VP_A: Transmission Path/Virtual Path Adaptation
TSF: Trail Signal Fail
TTL: Time To Live
Tx: Transmit direction
UDP: User Datagram Protocol
USM: User Services Manager
VC: Virtual Container
VID: Virtual LAN Identifier
VLAN: Virtual Local Area Network
VoIP: Voice over IP
VPN: Virtual Private Network
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
31
01
/3AL 89871 AAAA AA
218
218
VR: Virtual Router
WC–WFQ: Work–Conservative WFQ
WFQ: Weighed Fair Queuing
WNC–WFQ: Work–Non–Conservative WFQ
W–RED: Weighed – Random Early Discarding
XC: Cross–Connection
5.2 Definitions
The following definitions are taken by IETF:RFC 3031: ”Mpls Architecture”Draft–ietf–mpls–lsr–mib–08Draft–ietf–mpls–ftn–mib–04RFC MIB IP
Ethernet Transparent Service (ETS): a provider service that emulates the functionality of a traditional Local Area Network.
Ethernet Flow: 4–uple <MAC Source Address, MAC Destination Address, 802.1p Priority bits,VLAN tag > representing an Ethernet connection between remote MAC address. Ethernet traffic is tagged with 802.1p VLAN and is classified with 8 Ethernet priority values.
Flow: set of Ethernet flows transmitted between two remote customer’s sites with the same QoS.
Aggregate: a set of flows passing through the same Virtual Ethernet Interface.
Forwarding Equivalence Class (FEC): a group of IP packets, which are forwarded in the samemanner (e.g. over the same path, with the same forwarding treatment).
Label: a short fixed length physically contiguous identifier, which is used to identify a FEC, usually of local significance.
Label Stack: an ordered set of labels.
Label Switched Path (LSP): the path through one or more LSRs at one level of the hierarchy followed by a packet, in a particular FEC.
MPLS Node: a node wich is running MPLS. An MPLS node will be aware of MPLS control protocols, will operate one or more L3 routing protocols, and will be capable of forwarding packets on labels. An MPLS node may optionally be also capable of forwarding native L3 packets.
Label Switching Router (LSR): an MPLS node, which is capable of forwarding native L3 packets.
Label Edge Router (LER): an MPLS node that connects an MPLS domain with a node, which is outside of the domain, either because it does not run MPLS, and/or because it is in a different domain.
InSegment: It represents an incoming segment in a LSR.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
32
01
/3AL 89871 AAAA AA
218
218
OutSegment: It represents an outgoing segment from a LSR.
XC: It represents a cross–connection, which is used to associate in and out segments toghether,in order to form a cross–connection.
Next Hop Label Forwarding Entry (NHLFE): It is used when forwarding a labeled packet. Itcontains the following information:
The packet’s next hopThe operation to perform on the packet’s label stack; this is one of the following operations:
Replace the label at the top of the label stack with a specified new label.Pop the label stack.Replace the label at the top of the label stack with a specified new label, and then push one or more specified new labels onto the label stack.
It may also contain:The data link encapsulation to use when transmitting the packet.The way to encode the label stack when transmitting the packet.Any other information needed in order to properly dispose of the packet.
FEC to NHLFE (FTN): It maps each FEC to a set of NHLFEs. It defines a rule to compare against incoming packets and an action to be taken on matching packets.
Jabber: a condition wherein a station transmits for a period of time longer than the maximum permissible packet length, usually due to a fault condition.
Jabber Function: a mechanism for controlling abnormally long transmission.
Link: the transmission path between any two interfaces of generic cabling (from ISO/IEC 11801)
Promiscuous Mode: if active the MAC forwards to upper layers all the received packets. It canbe active only on certain type of media.
Tx: Indicates the Transmission direction.
Rx: Indicates the Receiving direction.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
33
01
/3AL 89871 AAAA AA
218
218
INTRODUCTION
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
34
01
/3AL 89871 AAAA AA
218
218
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
35
01
/3AL 89871 AAAA AA
218
218
1 INTRODUCTION
1.1 Scope
This chapter describes the main features of the graphical interface for the ISA–ES Operator and providesa general overview of the system architecture.
1.2 Reading rules
All the manuals describe menus, but not necessarily all the options of these menus. When a menu optionis not detailed in a manual, the information is given in another manual.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
36
01
/3AL 89871 AAAA AA
218
218
1.3 System Generalities
1.3.1 Ethernet Technique
The Ethernet (also called MAC 802.3) technique, operating at level 2 of the ISO–OSI protocol stack, isused to transport data packets originated by the network layer (level 3). It is based over the concept of“multiaccess channel”; i.e. a single channel is shared among many users that are connected on the samecommunication medium. The MAC (Medium Access Control) functions provide to manage the access tothe physical channel and the related possible access conflicts that can arise. The channnel used toconnect many users is called LAN (Local Area Network).The data packets are encapsulated into the MAC frame (illustrated in Figure 9. page 45), and then are sentinto the Ethernet physical layer (level1), after conversion using the Manchester encoding procedure.
Alcatel ISA–ES (Integrated Services Adapter–Ethernet Switching) is a system operating at layer 2 bymeans of the MAC protocol. It acts as an Ethernet Switch (or bridge), used to connect different LAN’sbetween them. The LAN’s may be local or remote, where remote LAN’s are linked using the existing SDHphysical backbone, by means of the POS (Packets Over SDH/SONET) procedure.
For more information about Ethernet/MAC refer to IEEE 802.3 standard.
3 NETWORK any network “packetized” data service
2 DATA LINK ETHERNET
1 PHYSICAL SDH
Table 6. Ethernet layer stack over SDH
The Alcatel ES system can manage packets data streams transported over “local” Ethernet FE or GbE(Fast Ethernet, Gigabit Ethernet) and “remotized” ethernet over GFP/SDH or LAPS/SDH; the GbE portis available only on ES4 and ES16 boards.
Three types of ES boards are foreseen: ES1 (with an SDH equivalent capacity of 1 VC4, 8 FastEthernetLocal ports and 8 Remote ports), ES4 (SDH equivalent capacity of 4 VC4, 8 FastEthernet Local ports, 1GigaEthernet Local port, and 16 Remote ports), ES16 (SDH equivalent capacity of 16 VC4, 14FastEthernet Local ports, 4 GigaEthernet Local port, and 64 Remote ports; local ports are located onindependent access modules). The three boards are differentiated also by other features that will beexplained, in this handbook, as they come across the configuration of the single features.ES16 board is not available in current release.
The bridge function may be carried out by means of the “MAC autolearning” procedure (802.1D Rec.) orby means of manual “engineered” point–to–point connections.The Ethernet Bridge representation is schematically illustrated in Figure 2. page 38; the insertion of theES Bridge into the SDH network is illustrated in Figure 3. page 39.
ES system can act also as a “Virtual Bridge” (802.1Q Rec.) or as a “Provider Bridge” (802.1ad/D1.3 Rec.)managing the VLAN (user tag) and S–VLAN (provider tag) fields of the MAC frame (also called“VLAN–tagged MAC frames”); in this way it can further support the SLA with differentiated CoS, and theaggregation of many users over a single virtual circuit. Some generic examples about VLAN and S–VLANutilization are reported in Figure 4. page 40. and Figure 5. page 41. For more details about VLAN/LLCrefer to IEEE 802.1Q standard.
Furthermore it accomplishes the functions requested by the Spanning Tree Proptocol (STP, RSTP,VLAN–STP, MSTP), in order to prevent “infinite loops” due to redundantly connected bridges; see STPexample in Figure 7. page 43. STP functions are compliant to 802.1d, 802.1w, 802.1s Rec.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
37
01
/3AL 89871 AAAA AA
218
218
The various Ethernet frames formats are illustrated in Figure 9. up to Figure 11. ; the other framesformats are reported in the related OMSN (1640fox/1650sm/1660sm) Technical Handbooks, and in thestandard recommendations.The ISA–ES system and protocol stacking is illustrated in the figure below (Figure 1. ).The Ethernet/GFP framing is illustrated in Figure 13. and Figure 14. The Ethernet/LAPS framing is illustrated in Figure 15. An example of Point–to–Point cross–connected Ethernet link is illustrated in Figure 6. page 42
EthernetSwitchFE,GE
EthernetoverSDH
FE or GEMAC
any
1
2
3
Ethernetlocal
GFP or LAPS
MAC
any
2
3
SDH1
GFP
VLAN and/or SVLAN
processing
(or Bridge)
or
LAPSSDH
(remote Ethernet)
CIA
CIA = Classification, Identification, Aggregation
MAC
any
2
3
VLAN
S–VLAN
MAC
any
2
3
VLAN
S–VLAN
CIA function can be enabled/disabled by the operator
NOTE: VLAN and SVLAN functions are not supported in current release
Figure 1. ISA–ES subsystem, protocol stacking
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
38
01
/3AL 89871 AAAA AA
218
218
MAC–C10
C10
B1
1
2
3
4
5
6
C15
C23
C28
L1
L2
L3
C26
C24
L4
L5
L6
NOTES:
1, 2, 3, 4, 5, 6 : ports of the bridge
L1, L2, L3, L4, L5, L6: LANs
Cn : Computer with its own MAC address
BRIDGE
Computer Address Port
MAC–C15
1
3
MAC–C23
MAC–C24
5
6
MAC–C26
MAC–C28
5
4
FDB table
(Filtering Data Base table)
Bridge operations examples:
C15 to C26 ––> FORWARD to port5
C26 to C23 ––> DISCARD
C10 to C21 ––> LEARNING
C21 to C28 ––> LEARNING (adding C21 on FDB)
C21
Cn : new inserted computer
A “MAC Bridge” takes into account the MAC addresses.A “Virtual Bridge” takes into account the MAC addresses and the VLAN identifiers (user tag).A “Provider Bridge” takes into account the MAC addresses and the S–VLAN identifiers (provider tag).The “Provider Bridge” can work in mixed mode, taking into account the VLAN and the S–VLAN identifiers.In any configuration, the Bridge works in promiscuous mode.
NOTE: “Virtual Bridge” and “Provider Bridge” options are not supported in current release
Figure 2. Bridge representation example and relevant FDB table
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
39
01
/3AL 89871 AAAA AA
218
218
B1
ISA–ES
SDH NETWORK B2
ISA–ES
B3 ISA–ES
B4 ISA–ES
LocalEthernet
Ports
Ethernet Over SDH
(POS)
Figure 3. ES System into SDH network, example
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
40
01
/3AL 89871 AAAA AA
218
218
ETS InFlow
VLAN#25
VLAN#150L–ETH
Port
C
C
Classifier
LAN1
ETS InFlowVLAN#200
C
L–ETHPort
LAN2ETS InFlow
VLAN#500–700
C
Pri3
Pri5
Pri7
Pri3
ETS XC
ETS OutFlow
ETS OutFlow
ETS OutFlow
R–ETHPort
POSSDH
NOTES:L–ETH = local ethernet; R–ETH = remote ethernet;C = classifier; Pri = priority; XC = Cross–ConnectionClassifiers, InFlows and OutFlows are internal resourcesThe VLAN’s on LAN1 and LAN2 are aggregated on the same SDH resourceA frame with VLAN tag that is not defined on Classifiers is discarded
NOTE: this feature is for future release: VLAN functions are not supported in current release
Figure 4. VLAN Classification–Identification–Aggregation (example)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
41
01
/3AL 89871 AAAA AA
218
218
InFlowfrom LAN1
XC
R–ETHPort
SDH
OutFlow
OutFlow
OutFlow
InFlowfrom LAN2
InFlowfrom LAN3
PUSHSVLAN
PUSHSVLAN
PUSHSVLAN
XC
R–ETHPort
InFlow
InFlow
InFlow
POPSVLAN
POPSVLAN
POPSVLAN
S–VLAN management, example1: Provider Network
InFlowfrom LAN1
XC
L–ETHPort
LAN4
OutFlow
OutFlow
OutFlow
InFlowfrom LAN2
InFlowfrom LAN3
PUSHSVLAN
PUSHSVLAN
PUSHSVLAN
XC
L–ETHPort
InFlow
InFlow
InFlow
POPSVLAN
POPSVLAN
POPSVLAN
S–VLAN management, example2: Provider LAN
NOTE: this feature is for future release: S–VLAN functions are not supported in current release
Figure 5. Stacked VLAN management (example)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
42
01
/3AL 89871 AAAA AA
218
218
PU
SH
S–V
LAN
PO
PS
–VLA
N
InF
low
Cla
ssifi
er
(VID
)(P
riorit
y)
ET
S X
C
Eth
erne
tD
ata
Out
Flo
w
(TD
)
SD
H N
etw
ork
SD
H X
CS
DH
XC
ET
S X
C
Out
Flo
wIn
Flo
w
Eth
erne
tD
ata
(TD
)
(Rat
e)(R
ate)
R–E
TH
Por
t(R
ate)
R–E
TH
Por
tL–
ET
H P
ort
(Rat
e)
Poi
nt–t
o–P
oint
Eth
erne
t Lin
k E
xam
ple
Term
inat
ing
Poi
ntTr
ansp
ort
Net
wor
kO
rigin
atin
gP
oint
L–E
TH
Por
t PO
PS
–VLA
NP
US
HS
–VLA
N
Eng
inee
red
VLA
N
NOTE: VLAN and S–VLAN functions are not supported in current release
Figure 6. Engineered Point–to–Point Ethernet over SDH link Example
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
43
01
/3AL 89871 AAAA AA
218
218
A
C
DH
B
FG
E
PHYSICAL TOPOLOGY (Example)
A
C
DH
B
FG
E
ACTIVE SPANNING TREE TOPOLOGY (Example)
Root Bridge
Active (forwarding) Port
Inactive (discarding) Port
Active link
Inactive link
Secondary Bridge
Active (forwarding) PortActive link
NOTES:– The active STP topology is dynamic, therefore it will change on occurrence of certain events/failures– The RootBridge is the bridge having the identifier with lowest numerical value (and with higher prioritty)– The Secondary Bridge will substitute the Root Bridge, on failure of this latter– The STP procedure is managed by means of control frames BPDU (Bridge Protocol Data Unit)– The Inactive Ports can be configured to accept control frames
Figure 7. Spanning Tree example
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
44
01
/3AL 89871 AAAA AA
218
218
A
C
DH
B
FG
E
BRIDGE and PORT ROLES (example)
Root Bridge
DesignatedPort for LAN L6
L6
L1
DesignatedBridge for L6
RootPort for Bridge A
AlternatePort for Bridge A
L2
I
DesignatedPortfor path H – I
BackupPortfor path H – I
L3
L7
L8
L4
L5
L9
L10
L11
L13
L14
L15
L16
DesignatedPortfor L4
: inactive (discarding) Port (Alternate or Backup role)
DesignatedBridge
for L4, L5, L7
NOTES:– A, B,... : bridges– L1, L2, ... : LAN’s– The parameters indicated will be detailed hereinafter in this handbook, where they will be used
Figure 8. Some examples of Bridges and Ports roles in RSTP network
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
45
01
/3AL 89871 AAAA AA
218
218
+––––––––––+––––+–––––––––––––+–––––––––––––+–––––+ | Preamble | FS | Dest. Addr. | Source Addr.| L/T | |(7 bytes) |(1) | (6) | (6) | (2) | +––––––––––+––––+–––––––––––––+–––––––––––––+–––––+ +––––––––––––––––––––––––+–––––––––+–––––+ | Data | Pad | FCS | | (0 to 1500) | (0–46) | (4) | +––––––––––––––––––––––––+–––––––––+–––––+ FS=start of frame delimiter; L/T=Length–of–data–field / Type ; FCS= frame checksum
Figure 9. Ethernet MAC 802.3 frame format
+–––––+––––+––––+––––+–––––+––––+–––––+ | PRE | FS | DA | SA | 1Q | TCI| L/T | |(7B) |(1) | (6)| (6)| (2) | (2)| (2) | +–––––+––––+––––+––––+–––––+––––+–––––+ +––––––––––––––––––––––––+–––––––––+–––––+ | Data | Pad | FCS | | (0 to 1500) | (0–46) | (4) | +––––––––––––––––––––––––+–––––––––+–––––+ PRE: preamble; FS: Frame Start; DA: Destination Addr.; SA: Source Addr.1Q: “ProtocolType” 802.1Q field (a constant fixed value= hex“0x8100”)TCI : Tag Control Information = (3bits: user priority 802.1p)+(1bit: CFI)+(12bits: VLAN identifier 802.1q);
[CFI: Canonical Field Id.]L/T: MAC client Length/Type
Figure 10. Ethernet “Tagged” MAC 802.3 frame format
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
46
01
/3AL 89871 AAAA AA
218
218
+–––––+––––+––––+––––+–––––+––––+–––––+––––+––––+ | PRE | FS | DA | SA | 1QP |TCIP| 1Q | TCI|L/T | |(7B) |(1) | (6)| (6)| (2) | (2)| (2) | (2)| (2)| +–––––+––––+––––+––––+–––––+––––+–––––+––––+––––+ +––––––––––––––––––––––––+–––––––––+–––––+ | Data | Pad | FCS | | (0 to 1500) | (0–46) | (4) | +––––––––––––––––––––––––+–––––––––+–––––+ PRE: preamble; FS: Frame Start; DA: Destination Addr.; SA: Source Addr.1Q: “ProtocolType” 802.1Q field (a constant fixed value= hex“0x8100”)TCI : “Tag Control Information” = (3bits: user priority 802.1p)+(1bit: CFI)+(12bits: VLAN identifier 802.1q);
[CFI: Canonical Field Id.]L/T: MAC client Length/Type1QP: 2byte “provider–ProtocolType” , similar to the 1Q identifier, settable by the Service ProviderTCIP: 2byte “provider–TagControl Information” , similar to the TCI bytes
(3bits:provider–priority)+(1bit:CFI)+(12bits:provider–VLAN id.),settable by the Service Provider
Figure 11. Ethernet “Stacked VLAN” frame format
0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 +––+––+––+––+––+––+––+––+––+––+––+––+––+––+––+––+ | UP | C| VID | +––+––+––+––+––+––+––+––+––+––+––+––+––+––+––+––+
UP: User Priority (3 bits)C: CFI, Canonical Field Identifier (1 bit)VID: VLAN Identifier (12 bits)
Figure 12. TCI Field format (802.1Q VLAN Tag)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
47
01
/3AL 89871 AAAA AA
218
218
4
12345
.
.
.
n
1 2 3 4 5 6 7 8
4–65535
Fields constituting a GFP client frame
GFP Frame size and transmission order
Payload area
Bit transmission order
Octet
Bit
Core header
Octettransmission
order
Optionalpayload FCS
(CRC–32)
Clientpayload
informationfield
Payloadheaders
(4–64 bytes)
cHEC(CRC–16)
16–bit Payloadlength indicator
Coreheader
Payloadarea
GFP
GFP
GFP
GFP
(Ethernet Frame)
2 bytes
2 bytes
X = 4 to 64 bytes
4 bytes
N= 0 to 65535–X bytes
Figure 13. GFP Framing (from G.7041/Y.1303)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
48
01
/3AL 89871 AAAA AA
218
218
PLIcHEC
tHEC
2222
0–60
7
1
6
6
2
4
Type
Octets
Bits
Octets
GFP
Preamble
Length/Type
MAC client data
Pad
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Frame Check Sequence (FCS)
Start of frame delimiter
Destination Address (DA)
Source Address (SA)
GFP Extension Header
Payload
Ethernet MAC FrameGFP Frame
Figure 14. Ethernet encapsulation into GFP frame (from G.7041/Y.1303)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
49
01
/3AL 89871 AAAA AA
218
218
Destination Address
Start of Frame Delimiter
Preamble7
Source Address
Client Data
Length/Type
Pad
4 FCS
1
6
6
2
46 to 1500
Destination Address
2nd byte of SAPI (0x01)
1st byte of SAPI (0xFE)
Source Address
Client Data
Length/Type
Pad
FCS of MAC
FCS of LAPS
Flag (0x7E)
Address (0x04)
Control (0x03)
Flag (0x7E)
nr. of bytes
1
Ethernet frame
nr. of bytes
1
1
1
1
1
4Ethernet frame
LAPS frame
Figure 15. Ethernet/LAPS encapsulation (ITU–T X.86)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
50
01
/3AL 89871 AAAA AA
218
218
PRE FS DA SA DFL Ethernet Payload FCS
DA SA DFL Ethernet Payload FCS
Ethernet Packet
Ethernet PacketHeader
POH SDH payload
POS frame
VC4 or VC3 or VC12 frame
Ethernet
GFP
SDH
FCSorLAPS
(E, FE, GbE)
Figure 16. Ethernet over SDH Framing
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
51
01
/3AL 89871 AAAA AA
218
218
1.3.2 Virtual Concatenation and LCAS
The ISA–ES system supports (at the SDH side) Virtual Concatenation and LCAS features.
The Virtual Concatenation consists in the fact that frames not fitting into a single SDH–container aretransported over more individual containers, indicated with the symbol VCn–Xv (e.g. VC12–3v indicatesthe virtual concatenation of 3 VC12).The original frame is parelleled “TimeSlot–by–TimeSlot” and loaded over different payloads.The individual containers can follow different paths in the network, with different delays, and they needto be reassembled at the end points, taking into account the different path delays.This feature is compliant to ITU–T G.707 rec.A schematic example is illustrated in the figure below (example with concatenation granularity=3).
The LCAS feature (Link Capacity Adjustement Scheme) permits the operator to “hitless” modify thebandwidth capacity of a virtual concatenated link, in order to meet the bandwidth needs of the service (byadding or removing virtual containers in all the involved nodes of the network). It can also temporarilyremove failed links of the group, in automatic and hitless mode. In case of failure or addition of links, thetraffic is automatically redistributed over the working links. Reference: ITU–T G.7042 rec.
SDH network
”big” Ethernet frame
a1 a2 a3 a4 a5 a6
b1 b2 b3 b4 b5 b6
a7 a8 a9 a10 a11 a12
b7 b8 b9 b10 b11 b12
a1 a4 a7 a10
b1 b4 b7 b10
a2 a5 a8 a11
b2 b5 b8 b11
a3 a6 a9 a12
b3 b6 b9 b12
VC number 2, path delay 2
VC number 3, path delay 3
VC number 1, path delay 1
a1 a2 a3 a4 a5 a6
b1 b2 b3 b4 b5 b6
a7 a8 a9 a10 a11 a12
b7 b8 b9 b10 b11 b12
time slot 1 2 3 4 5 6 7 8 9 10 11 12
Byte
Figure 17. Virtual Concatenation (example)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
52
01
/3AL 89871 AAAA AA
218
218
1.3.3 Management software
The transportation of Ethernet frames is achieved by integrating the necessary hardware and softwarefunctions into the SDH Network Elements.
The software related to the Ethernet Switch (ES) management provides a human interface permitting theOperator to manage the relevant functions. The human interface can be integrated on a PersonalComputer representing the ES Craft Terminal (ES–CT), or on a Work Station representing the ESOperations System (ES–OS).ES–CT is installed on a Common Platform CT, and ES–OS is installed on a Common Platform OS.
The Alcatel–NE’s management is based on a software platform, common to all the transport equipments,resulting on the NES operator interface (Network Elements Synthesis); the description of the NESinterface and some generic procedures, common to all the Alcatel–NE’s, are reported on 1320CTOperator Handbook; the hardware configuration, features and functionalities of Alcatel Network Elementssupporting ES services are described in the relevant Technical Handbooks; the SDH traffic managementby means of the SDH–CT is described in the relevant OMSN–CT Operator Handbooks.The list of the related HANDBOOKS is reported in paragraph 2, page 15.
The ES management by means of the OS is described in the relevant TMN Operations System Operator’sHandbooks.
The aim of this handbook is to illustrate the operational procedures to access and to handle theEthernet traffic by means of the ES–Craft Terminal (ES–CT).
The ES–CT permits to manage the functions and the parameters relevant to the ES service, such as:– signals rate, bandwidth, interface type, traffic contract, cross–connections, manual and automatic
switching, alarms, performance monitorings, etc.
The ES traffic and network management signalling inside the existing SDH network is accomplished bymeans of a dedicated communication protocol, as indicated in para.1.3.4, page 53.
The provided CT software needs a WINDOWS computer operating environment. The operator’s interfaceis organized in a WINDOWS system. A skill on these tools is required on behalf of the user.For the personal computer characteristics see para 4.5.2, page 24.
The CT Common Platform (i.e. 1320CT) software package has to be already installed, before installingthe ES–CT.
The software product is distributed by Alcatel in a CD–ROM.This CD–ROM contains:
• Software products for management by means of the craft terminal• Software product for updating the NE (download)
The software products used for management permits the dialogue between the Craft terminal and theNE, to realize the functions of the applications as configuration, alarms management, etc.
The software product used for updating the NE must be installed on the PC and then downloaded on theNE, thus following product evolution. The download of the NE is done in the SDH–CT environment,therefore the relevant download operations are reported in the specific OMSN–Operator Handbook (seeTable 4. on page 16).
The list with the part numbers of the software product relevant to ES service is reported in para. 2, page57.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
53
01
/3AL 89871 AAAA AA
218
218
1.3.4 Ethernet over SDH Management
The management of SDH equipments is organized as required by the 7–layers ISO/OSI protocol stack,while the Ethernet, MPLS and ATM equipments (ISA) are usually managed by means of SNMP (SimpleNetwork Management Protocol), that is an application of the 5–layers TCP/IP reference model.
By carrying the Ethernet traffic over the SDH network structures there is the need to manage together andcontemporarily SDH and Ethernet equipments; this function is accomplished by means of theencapsulation of SNMP messages inside the OSI layers (“IP over OSI tunneling”). In this way the Ethernetmanagement information is transported over the existing SDH networks.
The various protocols relations are illustrated in Figure 18. on page 53.
An example of Ethernet/MPLS/SDH network management is shown in Figure 19. page 54.In this example, the OS enters the network management messaging over an Ethernet link (IEEE–802.3protocol) of a Gateway NE (GNE); here the messagges are transported over the optical Qecc links bymeans of the LAPD protocol; at the remote managed nodes, the messages are acknowledged asbelonging to:
• OSI reference model, for SDH management• TCP/IP (SNMP) reference model, for Ethernet, ATM and MPLS management.
Application
Presentation
Session
Transport (TP4)
Network(CLNP)
LAPD
Qecc/F
802.3
QB3
IP
UDP
SNMP
Lay1
Lay2
Lay3
Lay4
Lay5
Lay6
Lay7
43
12
ISO/OSI protocols
TMN protocols(F/Qecc)
TMN protocols(QB3)
Internetprotocols
1): OSI stack for SDH management (F/Qecc Interface)
2): IP over CLNP tunneling for ISA Management (F/Qecc Interface)
3): OSI stack for SDH management (QB3/Qecc Interface)
4): IP over CLNP tunneling for ISA management (GNE entry from OS, IEEE–802.3)
Figure 18. Protocol stack for ATM/MPLS/Ethernet over SDH management
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
54
01
/3AL 89871 AAAA AA
218
218
SDH (OSI) & ES (SNMP)TMN
SDH+ESNE
SDH NE
Gateway NE
OS
SDH+ESNE
SDH NE
SDH+ESNE
FCT
FCT
QB3
QECC
QECC
QECC
QECC
QECC
QECC
F
F
F
LAPD
OSI
SNMP
802.3
LAPDOSILAPD
OSI SNMP
LAPD
OSI
SNMP
LAPD OSILAPD
(GNE)
SDH–CT
ES–CT&
SDH–CT
SDH–OS
ES–OS&
TP4
Appl.
Sess.
Pres.
CLNP
MAC
Eth–qb3
SDH (OSI)
SNMP
IP
UDP
Tunnel
TP4
Appl.
Sess.
Pres.
CLNP
rs232–F
SDH (OSI)
SNMP
IP
UDP
LAPD
TP4
Appl.
Sess.
Pres.
CLNP
LAPD
SDH–qcc
SDH (OSI)
SNMP
IP
UDP
QB3 F QECC
Protocol stack at different interfaces:
Tunnel Tunnel
ES (SNMP) ES (SNMP) ES (SNMP)
NOTE:The tunnel IP over CLNP is initiated inside the Manager (CT or OS) and terminated at the destinationNE, in order to carry SNMP management messages into the SDH network.The SNMP messages are tunneled in the NE’s where the message is not to be opened
Figure 19. Example of management of an SDH network with SDH and ES traffic
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
55
01
/3AL 89871 AAAA AA
218
218
NOTE: in order to transfer the management information, the involved entities need an OSI address (forthe ISO/OSI information messages) and an IP address (for the SNMP information messages). Inparticular:
1 ) the CT (personal computer, local manager or craft terminal) needs to be associated to an OSIaddress and to an IP address. The OSI address is assigned by means of the Alcatel LowerLayers Manager (AAL) application; the IP address assignment is done in the WINDOWSenvironment by means of the “Network” application of the “ControlPanel”. Refer to the 1320CTBasic Handbook for these operations.
2 ) the EC (Equipment Controller board of the NE) needs to be associated to an OSI address andto an IP address. The OSI address and IP address are assigned by means of the SDH–CTapplication (“Configuration:Comm/Routing:...” options). Refer to the OMSN Operator’sHandbook for these operations.
3 ) the ISA board needs to be associated to an IP address. The IP address is assigned by meansof the SDH–CT application (“Configuration:Comm/Routing:...” options). Refer to the OMSNOperator’s Handbook for these operations.
An illustrative example is reported in next Figure 20.
CTF EC
ISA#1
ISA#n
LAPD
Qecc
(Local Manager)
OSI address
IP address
(to other NE’s, or Gateway, or Remote Manager)
+
IP address
IP address
Managed NE (adjacent)
OSI address
IP address+
SNMP
Figure 20. OSI and IP addressing example
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
56
01
/3AL 89871 AAAA AA
218
218
1.4 ES–CT main functionalities
In this chapter, the main functionalities of the ES Craft Terminal are described, referred to the main dialogviews and menu options as they are displayed on the Operator monitor. The functionalities constitute theheading of each of the paragraphs below.
1.4.1 Supervision
It permits to manage the access to the ES functions from the various levels of management.
1.4.2 Configuration
It permits to manage the configuration of the following functions:Alarms Severities Assignment Profiles (ASAP)Threshold data table setting for Performance monitoringTraffic contract descriptor setting.
1.4.3 Diagnosis
It permits to open the Alarms Surveillance (AS) application.
1.4.4 MIB Management
It permits to save/load the MIB (data base) of the ES functionality configurations.
1.4.5 Transmission
It permits to manage the functions related to the Transmission domain:creation, configuration, modification and deletion of the ES rersources (ES–Node,Ethernet–Ports, in/outFlows, Classifiers, etc.).
1.4.6 Connection
It permits to manage the functions related to the Connection domain:creation, configuration, modification and deletion of the links, cross–connections on ISA–ES.
1.4.7 Performance Monitoring
It permits to manage the functions related to the Performance domain:configuration, modification and deletion of data collections related to the PerformanceMonitoring (PM) on the ES resources.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
57
01
/3AL 89871 AAAA AA
218
218
2 SOFTWARE PRODUCT AND LICENSE DELIVERED TO THE CUSTOMER
2.1 Software product and licenses description
The software products are distributed by Alcatel in a CD–ROM.
This CD–ROM contains:
• Software packages for ES management by means of the craft terminal
• Software packages to be downloaded into the NE (by means of the download function)
The software package used for management permits the dialogue between the ES–CT and the NE, toconfigure all the ES functions.
The software package used for updating the NE must be installed on the PC and then downloaded onthe NE, thus following product evolution. The download on the NE is done in the SDH–CT environment,therefore the relevant download operations are reported in the specific–NE Operator Handbook.
Alcatel, typically, offers several software licenses for the software product;they are referred both to the Network Element software features and to the Craft Terminal softwarefeatures.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
58
01
/3AL 89871 AAAA AA
218
218
2.1.1 Software products, licenses and part numbers
The Software Product is identified by a denomination and one or more part numbers, as listed on thefollowing table.
Table 7. Software product part number
Denomination ANV Part NumberFactory
Part NumberN.B.
SWP–ES1 R.1.1 (CD–ROM) 3AL 98164 AA –.–.– 1
SWP–ES4 R.1.1 (CD–ROM) 3AL 89807 AA –.–.– 2
N.B. 1 to manage the ES1 board
2 to manage the ES4 board
In order to use the above software product, one or more software licenses may be requested.
Every Software license is identified by a denomination and a part number, listed in the following table.
Table 8. Software licenses part numbers
Name ANV Part NumberFactory
Part NumberN.B.
SWL–RCT ES1/ES4 SERIES R.1.1 3AL 89820 AA –.–.– 1
SWL–ES R.1.1 SVLAN/ISA POINT 3AL 89816 AA –.–.– 2
N.B. 1 for the ES–CraftTerminal (specific to the release)
2 for the SVLAN functionality (not yet available, available only in a future next step)each ES point needs one of these “ISA POINT” licenses:one ES board includes 2 points, then it needs 2 “ISA POINT” licenses
NOTE: this product includes software developed bythe Apache Software Foundation (http://www.apache.org).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
59
01
/3AL 89871 AAAA AA
218
218
SOFTWARE INSTALLATION
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
60
01
/3AL 89871 AAAA AA
218
218
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
61
01
/3AL 89871 AAAA AA
218
218
3 ES SOFTWARE INSTALLATION
NOTE: the figures included in this chapter are only examples, in order to explain the installationprocedures. In the real installation, some version/edition/release numbers inside the windows may bedifferent, but the procedure is the same.
3.1 Scope of the procedure
This procedure describes how to install the software required by the ES–CraftTerminal and how tode–install it, if necessary.
3.2 Start–up of the Personal Computer
The PC is started by means of the relevant switch.NOTE: Administrator privileges for WINDOWS environment are needed, to install and de–install theES–CT software package.NOTE: the Alcatel CraftTerminal Common Platform (i.e. 1320CT) software package already installed isneeded, before starting the installattion of the ES–CT software package.
At this point the Windows application starts automatically and the operator will see the Windows desktop.
3.3 Host Computer Configuration
The configuration of the Personal Computer hosting the ES Craft Terminal is the same as the configurationfor Alcatel CraftTerminal Common Platform (i.e. 1320CT). See the 1320CT Basic Handbook for detailsabout this issue.NOTE1: the IP address assignment to the host computer (PC) is necessary, before using the ES–CT;the procedure to assign this IP address is reported into the 1320CT–BasicHandbook; the steps to verifythat the IP address to the PC has been assigned are recalled in the following paragraph.NOTE2: if, for any reason, the IP address is changed, the following customization WINDOWS commandis necessary: “Start–>Programs–>Alcatel–>SNMPCT–K–ADDON–>SNMP–AddOn Customization”.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
62
01
/3AL 89871 AAAA AA
218
218
3.3.1 Verification of IP address assignment for the host computer
Note: the following procedure is here described only for WINDOWS–NT environment, but forWINDOWS–XP or others it is similar; please refer to 1320CT BasicHandbook for details.
a ) Verify that the “LLman Lower Layers” adapter is installed:
1 ) In WINDOWS environment: “Start>Setting>ControlPanel”;2 ) in the ControlPanel view, start the “Network” application3 ) in the Network view, open the “Adapters” folder4 ) in the Adapters folder, verify that the item “LLman NIC LowerLayerAdapter” is listed
b ) Verify that the IP address to the PC is assigned:
1 ) In WINDOWS environment: “Start>Setting>ControlPanel”;2 ) in the ControlPanel view, start the “Network” application3 ) in the Network view, open the “Protocols” folder4 ) in the Protocols folder, select the item “TCP/IP Protocol” and then click on the key “Properties”5 ) in the opened “properties” window, in the “Adapters” pull–down menu, select the item “LLman
NIC LowerLayerAdapter”6 ) in the IP address fields, verify if the IP–address and related mask are already assigned
If any of the above features is not verified, refer to 1320CT BasicHandbook for the AlcatelLowerLayermanager installation, and for the IP address assignment.
3.4 Summary procedure for ES software installation
The following steps have to be done, mainly, for ES software installation:
a ) Installation of 1320CT and SDH–CT packages, see 1320CT Basic Handbbok (see also note below).b ) Installation of SDH–NE software package into the PC, see 1320CT Basic Handbbok.c ) Download of SDH–NE software into the NE, see the specific OMSN Operator’s Handbook.d ) Installation of ES–CT, see para. 3.5, page 63.e ) Installation of ES–NE software package into the PC, see para. 3.6, page 86.f ) Download of ES–NE software into the NE, see para.3.8, page 93.g ) Activation of the ES–NE software into the NE, see para.3.8, page 93.
NOTE1: in case of migration from a release to another one, the presence of the previous release ofSDH–USM software package (see 1320CT Operator Handbook) is necessary, in order to download thenew software release, otherwise the equipment–SW and the CT–SW are not aligned and the equipmentcannot be supervised anymore. Hence the operator is recommended to keep the previous release ofthe SDH–USM, until the actual SW–package will be downloaded into the equipment.
NOTE2: in case of migration to a new release containing a new “ADD–ON” (ServiceSpecific packet suchas the ES–swp), from an old release containing another service packet (for instance an ATM–swp), thedownload of the software into the NE must be done in two steps:
first step downloading the new SDH packet associated with the known service packet (e.g.:enhanced OMSN with ATM, see also para. 3.6, page 86)second step downloading the new SDH packet associated with the new service packet (e.g.:enhanced OMSN with ES).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
63
01
/3AL 89871 AAAA AA
218
218
NOTE3: in case of UPGRADE from an OLD release to a NEW release that is not consecutive, thedownload of the software into the NE must be done in two steps:
first step: the release of the software into the NE and the release of the CT must be aligned (i.e., ifthe CT is in current release, it must be downgraded, thus installing the CT aligned to the NE softwareresident into the NE); in these conditions the new SW_package can be downloaded and activated,using the old CT.second step: instal the new CT release and access the NE.If the DataService board (ES) was not present in the old release, then download the new SDH packetassociated with the new service packet (e.g.: enhanced OMSN with ES).
3.5 ES–CT Installation procedure
The software of the ES Craft Terminal is contained in a Compact Disk (CD–ROM), supplied by Alcatel.The part number of this product is reported in para. 2.1.1, page 58.As an alternative it can be received from an Internet distribution Alcatel–Service site, managed by Alcatel;in this latter case the installation can be slightly different from this following procedure.NOTE: Every CraftTerminal application (NES, ES–CT, EML–USM, etc.) must be closed, before startingthe installation.
In order to guarantee the correct operations, all the Craft Terminal (SDH and ES) softwarepackages must be installed in the same PC disk partition.
NOTE: this product includes software developed bythe Apache Software Foundation (http://www.apache.org)
The sequence of the installation procedure will be different, according to software and selectionconditions:
• first installation, without ES–CT software previously installed in the PC
• installation with ES–CT software of previous or same version already installed in the PC.
This differences will be explained hereinafter.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
64
01
/3AL 89871 AAAA AA
218
218
To install the ES–CT software execute the following operations:
1 ) Insert the CD–ROM disk into the CD–ROM drive (example E:).
2 ) The installation program automatically starts and after an intermediate screen (Figure 21. ), thewindow of Figure 22. will appear:
Figure 21. Initial presentation intermediate screen
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
65
01
/3AL 89871 AAAA AA
218
218
Figure 22. Selecting installation procedure (1st step)
NOTE: the Back button permits to go back to the previous window; the Cancel button permitsto abort the present window: these functions are the same in all the screens where they arepresent.
3 ) (Figure 22. ) The above view permits to select the following options:
– Installation of the ES–CT software product: “CT Products installation”.
– The “CT Products de–installation” option is not operative.The unistallation of the application has to be done in the Windows–NT environment, seeinstructions at para. 3.7, page 90.
– “Quit”, to exit the installation procedure.
In this phase select the first option (CT Products installation).
Then click on Next button, to access the next dialog box (Figure 23. ).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
66
01
/3AL 89871 AAAA AA
218
218
Figure 23. Craft Terminal master setup, list of detected Components on the media
4 ) (Figure 23. ) The screen lists the installed Software Components detected.
Click OK to have the next dialog box:
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
67
01
/3AL 89871 AAAA AA
218
218
Figure 24. Selecting CraftTerminal components (1st step)
5 ) (Figure 24. ) This view permits to select the software components to be installed. They are:
– JRE ... (Java Runtime Environment, to support java software procedures)– Alcatel–Lower–Layer V... (to manage the interfaces communication between the
computer and the NetworkElement)– COMMON_FASTETH REL... (supporting ES management functionality)– CT–K rel... (to support the 1320CT CraftTerminal Common Platform)– SNMPCT–K–ADD–ON v... (Add–on software to manage the SNMP communication)
NOTE: the procedures to install the components JRE, Alcatel–Lower–Layer and CT–K arethe same as described in the 1320CT Basic Handbook, therefore they are not described in thismanual; please refer to the 1320CT Basic Handbook for their installation.
NOTE: the installation can be done by selecting more than one or all the components together,in this window, or selecting only one of them at a time.NOTE: the procedure can be slightly diferent, if all the components are selected, since somewindows figures will be added or skipped.
Click on Clear All button, then click on the square corrispondent to COMMON_FASTETHcomponent to mark it with a check, and then click on Next to have the following window:
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
68
01
/3AL 89871 AAAA AA
218
218
Figure 25. Software License agreement
6 ) (Figure 25. ) This view presents the terms of the license for the usage of the ES–CT.
Press the Yes button for acceptance, then the procedure can continue toward two directions:
– if another ES–CT component is already existing in the host computer, then the procedurewill ask if it has to be uninstalled; in this case the following Figure 26. will be displayed
– otherwise the Figure 29. will be shown (go to page 71).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
69
01
/3AL 89871 AAAA AA
218
218
If an already existing ES–CT software has been detected, then the following figure will bedisplayed:
Figure 26. Existing previous ES–CT version uninstall
7 ) (Figure 26. ) Click on ”Install this Delivery version and De–install the previous one” option,to mark it.
Then click on Next button to continue on the following:
Figure 27. Uninstall confirmation
8 ) (Figure 27. ) Click on Yes button to continue:
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
70
01
/3AL 89871 AAAA AA
218
218
Figure 28. Uninstall previous ES–CT version successfully completed
9 ) (Figure 28. ) This window informs that the de–installation of the previous ES–CT software hasbeen successfully completed.
Clicking on Ok button, the procedure will return the following Figure 29.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
71
01
/3AL 89871 AAAA AA
218
218
Figure 29. Choose destination folder for ES–CT installation
10 ) (Figure 29. ) The procedure proposes the default directory (C:\...) for the installation.
The Browse button can be used to change directory: in this case a file manager box will beopened to choose a new folder.When finished, select Next button.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
72
01
/3AL 89871 AAAA AA
218
218
Figure 30. Setup type
11 ) (Figure 30. ) It proposes the setup type, that is only the Typical one.Click on Next button.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
73
01
/3AL 89871 AAAA AA
218
218
Figure 31. Program Folder denomination
12 ) (Figure 31. ) It suggests the default program–icon name and permits to change it, if necessary.Click on Next button.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
74
01
/3AL 89871 AAAA AA
218
218
Figure 32. Start copying files and current settings summary
13 ) (Figure 32. ) It displays the current settings for the installation.If any displayed setting is not correct, click on Back option for a review, otherwise:click on Next button to start the files copying.Then, a series of automatic windows presentation will be displayed, showing the setup inprogress; see an example in next figure:
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
75
01
/3AL 89871 AAAA AA
218
218
Figure 33. Setup in progress, temporary windows sequence presentation
14 ) (Figure 33. ) The ES–CT installation procedure starts and, after intermediate automaticscreens, it will continue toward two directions:
– If more than one component installation at a time has been chosen in Figure 24. page 67,then the following Figure 34. will be displayed (go to page 76).
– otherwise, if only one component installation at a time has been chosen in Figure 24. page67, then the Figure 35. will be displayed (go to page 77).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
76
01
/3AL 89871 AAAA AA
218
218
Figure 34. Successive installation, temporary windows presentation
15 ) (Figure 34. ) The sequence of successive components installation procedure continues and,after intermediate automatic screens, the procedure will continue as detailed in the point (19 ),page 78.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
77
01
/3AL 89871 AAAA AA
218
218
Figure 35. Installation procedure menu window (2nd step)
16 ) (Figure 35. ) To install the “SNMPCT–K–ADD–ON” component click on “CT productsinstallation” and then on “Next” to access the following view (Figure 36. page 77 ).
Figure 36. Craft Terminal master setup, list of detected Components on the media
17 ) (Figure 36. ) The screen lists the installed Software Components detected.
Click OK to present next dialog box:
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
78
01
/3AL 89871 AAAA AA
218
218
Figure 37. Selecting SNMPCT component
18 ) (Figure 37. ) This view permits to select the software components to be installed.
To install the SNMPCT Manager: click on Clear All button, then click on the squarecorrispondent to SNMPCT–K–ADD–ON component to mark it with a check, and then click onNext.
19 ) At this point the procedure can continue toward the following directions:
– If no previous SNMPCT–K–ADD–ON component is installed in the host computer, thenthe procedure will continue presenting the following figures: Figure 40. pg81, thenFigure 41. pg82, then Figure 43. pg84, and then Figure 44. pg85.
– If another SNMPCT–K–ADD–ON component is already existing in the host computer,then two possible cases will be possible:
a)Different release : in this case the procedure will ask if it has to be uninstalled,displaying Figure 38. pg79, then Figure 40. pg81, and so on, skipping Figure 42.
b)Equal or similar release : in this case (maintenance) the procedure will continuedisplaying Figure 39. pg80, then Figure 40. pg81, and so on.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
79
01
/3AL 89871 AAAA AA
218
218
If another different release of SNMPCT software has been detected, then the following figurewill be displayed:
Figure 38. Existing different SNMPCT release to be uninstalled
20 ) (Figure 38. ) This view permits to uninstall the different software components.
To uninstall the SNMPCT component: select the Remove it... item, and then click on Next.
The procedure will continue on Figure 40.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
80
01
/3AL 89871 AAAA AA
218
218
If another equal or similar release of SNMPCT software has been detected, then the followingfigure will be displayed:
Figure 39. Existing previous similar release to be maintained: “REPAIRE”
21 ) (Figure 39. ) Select the “Repair” item, to maintain the software release.
Then click on Next button to continue to the following:
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
81
01
/3AL 89871 AAAA AA
218
218
Figure 40. SNMP CT Add On setup
22 ) (Figure 40. ) This window permits to choose between CT–K (new CT version) or the Q3CT–P(old CT version) where the SNMP–AddOn packets are to be inserted.
Click on CT–K... to select the new CT version.
Then, clicking on Next button, the procedure will display the following Figure 41.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
82
01
/3AL 89871 AAAA AA
218
218
Figure 41. SNMPCT setup in progress temporary window
23 ) (Figure 41. ) This is a temporary window showing the setup progress.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
83
01
/3AL 89871 AAAA AA
218
218
Maintenance case (skipped in case of first installation):
Figure 42. Maintenance Finished
24 ) (Figure 42. ) This window informs that maintenance is completed.
Click on Finisk to continue.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
84
01
/3AL 89871 AAAA AA
218
218
Figure 43. SNMPCT installation completed
25 ) (Figure 43. ) This window informs that the installation of the SNMPCT software has beencompleted.
Press the OK button, then the following figure will be shown:
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
85
01
/3AL 89871 AAAA AA
218
218
Figure 44. Selecting installation procedure (end step)
26 ) (Figure 44. ) The above view permits to select the installation procedures options.
In this final phase select the last option (QUIT), then click on Next button to end and to leavethe installation application.
NOTE1 : After finished the installation, a “Restart” of the personal computer is necessary(“Start”–>“ShutDown” –>“Restart the computer”).
NOTE2 : After the restart of the personal computer, the following window operation is necessary:“Start”–>“Programs” –>“Alcatel” –>“SNMPCT–K–ADDON” –>“SNMP–AddOn Customization”.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
86
01
/3AL 89871 AAAA AA
218
218
3.6 NE–ES package installation procedure
After the installation of the craft–terminal packages, the installation of the NE–ES package (i.e. the filedescriptor for the ES part, to be downloaded inside the NE in a subsequent step) is needed. Execute thefollowing operations:
Start the NES (“Network Element Synthesis”) view as described in para. 3.9 page 95, then the followingwindow will be displayed:
Figure 45. Descriptor files administration
1 ) (Figure 45. ) In this window, select the menu options: Supervision > Files Administration > SWP Administrator.
The “Software Package Administration” window will be opened:
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
87
01
/3AL 89871 AAAA AA
218
218
Figure 46. Software Package Administration–ES service specific
2 ) (Figure 46. ) This window contains three folders: SDH, SERV.SPEC. and OMSN;select the “SERV.SPEC.” (Service Specific) folder, then click on Install button.
A file–manager box will be opened (see Figure 47. ).In this file–browser box, select the CD–ROM driver (e.g. E:\, see note below) and the filenamepath: Ect\Swdw\ESx\(version)\ESx.dsc (i.e. the ES descriptor file); then click on Open button;at this point the installation will start.
NOTE: if not already in, insert the ES software CD–ROM into the PC driver, the installation setupis started automatically; stop the setup clicking on Cancel button and then confirm with ExitSetup.
Figure 47. File–Browser for Software Package installation
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
88
01
/3AL 89871 AAAA AA
218
218
Figure 48. Software Package Administration – create Enhanced OMSN
3 ) (Figure 48. ) In this window click on the “SDH/WDM” folder, then select the specific equipmentwith the desidered version to be associated with the ES part.NOTE: if the appropriate SDH/WDM Package is not already installed, it must be done asdescribed for the ES “Service–Specific” package, in the previous step (2 ) page 87; (for moredetails see 1320CT Handbook).
Click on Create OMSN button, to create a new software package: SDH+ES, whose name willbe the same of the equipment, with the “E” suffix (“Enhanced”).NOTE: if the Create OMSN button is “greyed” (i.e. not available), it means that the relevantOMSN is already existing: in this case go to the next step.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
89
01
/3AL 89871 AAAA AA
218
218
Figure 49. Software Package Administration – add ES service
4 ) (Figure 49. ) In this window click on the “OMSN” folder. In the “Created OMSN Packages” field,select the specific “Enhanced” OMSN, as created in the previous point.
Select the ES version (in the “Compatible Add–Ons” field) and click on Add button.
NOTE1: if the Add button is “greyed” (i.e. not available), it means that the relevant add–onservice is already installed.
NOTE2: in case of migration to a new release containing a new “ADD–ON” (ServiceSpecificpacket such as the ES–swp), from an old release containing another service packet (forinstance an ATM–swp), the download of the software into the NE must be done in two steps:
first step downloading the new SDH packet associated with the known service packet(e.g.: enhanced OMSN with ATM)second step downloading the new SDH packet associated with the new service packet(e.g.: enhanced OMSN with ES).
After the aforesaid operations, the software package SDH+ES is installed in the host computerand can be downloaded into the NE, in a subsequent step, from the EML–USM environment(see para.3.8, page 93.).
5 ) (Figure 49. ) At the end of the operation, exit this application by means of the “Close” button.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
90
01
/3AL 89871 AAAA AA
218
218
3.7 Software Uninstallation procedure
3.7.1 ES–CT Uninstallation
To de–install the software in WINDOWS environment, execute the following operations:
1 ) Open the Windows–Control Panel (Start –> Settings –> ControlPanel) and select theAdd/Remove Programs icon, as for the following figure.
Figure 50. Add/Remove Programs icon selection
2 ) (Figure 50. ) Click twice on the Add/Remove Programs icon to open it; then the next windowwill appear:
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
91
01
/3AL 89871 AAAA AA
218
218
Figure 51. Add/Remove Programs view
3 ) (Figure 51. ) Select, in the Install/Uninstall tab of this window, the application “FASTETHUSM”(or “ALCATEL SNMPCT...”, or other CT components) and click on the Add/Remove button.A confirmation message is presented:
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
92
01
/3AL 89871 AAAA AA
218
218
Figure 52. Delete confirmation (example)
4 ) (Figure 52. ) After confirmation with Yes button, next figure (example) appears, indicating thedeleting process:
Figure 53. Delete completed (example)
(Figure 53. ) At the end of the deleting process click OK.
The uninstallation of the SNMPCT component can be done in a similar way, by selecting the“Alcatel CT Kernel (SNMP Add–On v...)” row in Figure 51. page 91. The de–installationprocedure for other CraftTerminal components is the same too.
Then it is possible to de–install other Alcatel Craft Terminal software components or close theControlPanel window, exiting the procedure.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
93
01
/3AL 89871 AAAA AA
218
218
3.8 NE–ES software downloading
The download is the operation that permits to transfer a software package from the computer (server) tothe specific equipment (client). The “download” generalities and details are reported in the operatorhandbook relevant to the specific equipment. The download is to be done in the EML–USM context (i.e.SDH–CT); to start the sdh–ct select (in the NES view) the OMSN hosting the ES board and then the option“Supervision” –> “Show Equipment” (see also para. 3.9 page 95).
To download the ES–NE software, execute the following operations:
1 ) In the EML–USM view, select the menu options: Dowload > Init Download... to activate thefollowing window:
Figure 54. Download Initiate (example)
2 ) (Figure 54. ) In this box, select the software package containing the ES service, i.e. that one withthe “E” suffix (in this example 1640FXE).
Press the Ok button to start, a box showing the progress of the downloading process will be thendisplayed; when the download will finish with the message “Software download completed”,Close that box.
(Figure 54. ) Click on Cancel to close this box, after download completed.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
94
01
/3AL 89871 AAAA AA
218
218
3 ) In the EML–USM view, select the menu options: Dowload > Units Info... to have the followingwindow:
Figure 55. NE Software package activation (example)
4 ) (Figure 55. ) Select the appropriate equipment–version tab of this window. Select the Activateoption of the “CurrentState\Action” pull–down field, and then the Ok button, to activate theselected Software package.Press the Ok button on the further displayed confirmation box.
The SW Units Det. button opens another box giving some information about the selecteddownloaded package.
(Figure 55. ) Click on Cancel button to close this box.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
95
01
/3AL 89871 AAAA AA
218
218
3.9 Start–Up of the ES Craft Terminal management software
In order to activate the ALCATEL product , perform the following sequence :
Start > Alcatel 1320CT
as shown in next figure:
Figure 56. 1320CT software start–up
Then, the NES (Network Elements Synthesis) window will be displayed (see next figure).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
96
01
/3AL 89871 AAAA AA
218
218
Figure 57. NES view example
In the NES window, select the specific host equipment in the map folder, and then the following menuoptions: Supervision > Start Supervision, then, by means of the pop–up menu: “Realign ISA BoardPopulation”.
When the realignment phase is finished, select the ES equipment and then the following menu options:1) Supervision > Start Supervision, 2) Supervision > Show Equipment. Then, the ES–USM view willbe displayed.
The ES–CT application can be also activated from the SDH–CT view, by selecting the ES board and thenthe following menu option: Equipment > ISA Navigate (anyway this is possible only after the“realignment” and the “start supervision” operations from NES view).
NOTE: before using the ES–CT, the downloading of the ES software into the NE, and the assignmentof the IP addresses to the host computer, to the Controller board and to the ES Board (from sdh–ct:“Configuration”>”Comm/Routing”>”IPConfiguration”>”ISABoardIPAddress”) are necessary. See para 3.8page 93 for details about download procedure, the OMSN–Operator Handbook for the board IP addresssetting, and the 1320CT BasicHandbook for the PC IP address setting.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
97
01
/3AL 89871 AAAA AA
218
218
MANAGEMENT
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
98
01
/3AL 89871 AAAA AA
218
218
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
99
01
/3AL 89871 AAAA AA
218
218
4 CRAFT TERMINAL FOR ES MANAGEMENT
4.1 Introduction
This application (here named “ES–CT”) permits to manage the ES boards provisioned for the OMSNequipments.
NOTE1: before using the ES–CT, the assignment of some IP addresses is necessary:a) to the CT (personal computer). See the 1320CT–BasicOperatorHandbook for details about IP ad-dress setting for the host computer.b) to the EC (controller) board (from sdh–ct: “Configuration”>“Comm/Routing”>“IPConfigura-tion”>”IPAddressOfPointToPointInterface”). See the OMSN–Operator Handbook for details about IPaddress setting for EC board.c) to the ES board (from sdh–ct: “Configuration”>”Comm/Routing”>”IPConfiguration”>”ISABoardIP-Address”). See the OMSN–Operator Handbook for details about IP address setting for ES board.
NOTE2: if, for any reason, the IP address is changed, the following customization WINDOWS commandis necessary: “Start–>Programs–>Alcatel–>SNMPCT–K–ADDON–>SNMP–AddOn Customization”.
It has to be used in conjunction with the 1320CT platform, because it is an option of this latter; the activationof “ES–CT” starts from the “Network Element Synthesis” view, by doing the following operations:select the NE hosting the ES board; then, with the pop–up menu: “Realign ISA Board Population”; thenselect the displayed ES–NE and with the pop–up menu: “Start Supervision”.After having done these latter operations, the entering into ES–CT can be done:
a)from the NES view, by selecting the ES object and then the pop–up menu option “ShowEquipment”b) from the SDH–CT view, by selecting the ES board and then the menu option “Equipment –> ISA Navigate”.
After the activation, the following temporary screen is displayed:
Figure 58. Logon view
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
100
01
/3AL 89871 AAAA AA
218
218
4.2 Summary procedure for ES Management
The following actions have to be done, mainly, for ES traffic management (the order of sequence is manda-tory, for a correct working):
a ) IP address assignment for the CraftTerminal, the EC board and the ES boardb ) definition of SDH virtual ports and containers to be used for ES signals and relevant ports associa-
tions (via the menu “Configuration”: “ISA Port Configuration”, on SDH–CT)c ) cross–connection of virtual SDH containers transporting Ethernet packets (on SDH–CT)d ) traffic contract definition (on ES–CT)e ) Ethernet and GFP (or LAPS) ports interface definition (on ES–CT)f ) InFlow/OutFlows creation (on ES–CT)g ) Classifiers definition (on ES–CT)h ) Configuration of Performance Monitoring points.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
101
01
/3AL 89871 AAAA AA
218
218
4.3 Main view
After the temporary logon view, the shown screen is similar to the following Figure 59. on page 102, wherea generic view is reported in order to explain the meaning of its main components.The following fields and areas are generally displayed:
• title : window frame containing name of Craft Terminal and release and equipment labels.
• menu bar : bar containing the applications pull–down menus: Views, Configuration, Diagno-sis, Supervision, Mib_Management, Transmission/Connection/Performance (alternative:the desired menu application can be activated either from the “Views” options, or from the ap-plication tabs), Help (see para. 4.4, page 106).
• tool bar : providing some fast buttons (from left to right): “go to the previous view”; “go to thenext view”; “refresh tree”, “properties of selected resource”; “delete the selected resource”;“print the selected resource”; “help about the clicked item”. (Note: in the “Performance” and“Connection” applications, some further buttons are displayed (fast keys), in order to switchamong different modalities of the function).
• curr.Appl. : current selected application.
• Appl.tabs (Application tabs): containing the tabs to enter the main ES applications: Transmis-sion, Connection, Performance. By clicking on these tabs, the corresponding alternativemenu is displayed in the menu–bar, and the displayed areas are changed, according to the se-lected application.
• message row : it displays an help/information message about the current action or the objecton which the mouse is transiting over.
• Severity Alarms Synthesis : a series of boxes reporting the alarms and their current counting,subdiveded according to the assigned severity: CRItical, MAJor, MINor, WarNinG, INDetermi-nate; the detailed description is reported in the chapter 5 (“Maintenance”).
• Domain Alarms Synthesis : a box reporting the alarms counting relevant to the TransmissionDomain; the detailed description is reported in the chapter 5 (“Maintenance”).
• Management States Control Panel : a series of boxes displaying the states of the manage-ment control: SUPervised, local access (key), COM (CT–communication port connected), OS(1353SH presence), Manager (upper level NM–manager presence); the detailed descriptionis reported in chapter 5 (“Maintenance”), see also para. 4.5, page 114.
• A1 (Resources Tree Area): this area displays the available resources by means of a tree struc-ture; when an item is indicated by a “+” sign it means that the resource contains more lower re-sources and can be expanded, if indicated by “–” it means the resource is already expanded,if no sign is present it means that the resource is a leaf. An item of the tree can be selected byclicking on the left mouse button; a pop–up menu, containing the actions that can be done onthe selected item, is generated by clicking on the right mouse button. See details in para. 4.3.1.
• A2 (Application Table Area): this area lists, in tabular form, the object contained in the selectedresource (selected in the tree). A row of the table can be selected by clicking on the left mousebutton; a pop–up menu, containing the actions that can be done on the selected item, is gener-ated by clicking on the right mouse button.
• A3 (Resource Information Area): this area displays, only for information purpose, the detailsabout the selected resource, after selecting it in the above area A2; the displayed informationdepends on the application that is being used.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
102
01
/3AL 89871 AAAA AA
218
218
• Pop–up menus : some menus pop up in the areas A1 or A2, after selecting a resource andclicking on the right button of the mouse; the pop–up menus yield directly the possible options,for that particular selected resource, that are related to the current selected application.The pop–up menus appearing in the tree–area (A1) are also called “contextual pop–upmenu”. The items contained in the “contextual pop–up menus” are the same as those containedin the specific menus of the menu–bar. The pop–up menu can also be activated after selectinga resource in the application–table–area A2.
title
rowmessage
menu bar
A1
tool bar
Severity AlarmsSynthesis
Domain AlarmsSynthesis
Manag. StatesControl Panel
A2
A3
curr.Appl.Appl. tabs
Contextualpop–upmenu
Figure 59. Main view
The whole window and also the “A1”, “A2” and “A3” areas can be stretched, by means of the mouse arrow.Further, a self–explaining message appears under the mouse cursor, when it is passed over an active field;this message reports the status–information, when the mouse is passed over the resources listed in the“Tree” area (see para. 4.3.1.4, page 105).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
103
01
/3AL 89871 AAAA AA
218
218
4.3.1 Resources TREE area (A1)
ISA–Switch
Ethernet port
expanded branch
not expanded branch
leaf
Figure 60. TREE area example
The Tree is composed of: a “root” (the ISA ES Node), “branchs” and “leaves”. A branch contains one ormore leaves and is expandable, to see the leaves. It is preceded by a little square containing a “+” signor a “–” sign; the “+” means that the branch is contracted and can be expanded, the “–” means that thebranch is already expanded and can be contracted. A leaf is not preceded by any sign and means thatcannot be expanded.
All the ports are visualized automatically by the system in the tree; if not yet defined, they are greyed.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
104
01
/3AL 89871 AAAA AA
218
218
4.3.1.1 RESOURCES VISUALIZATION IN THE TREE AREA:
“ES Node” (with active alarms):
The colored circle before the switch is a visual indication of the alarms synthesis, see below for details.
“ETHERNET port” (Local (or Remote), in–service (up), with active alarms) :
The colored ball before the port is a visual indication of the alarms synthesis, see below for details.
“IN–FLOW” Point :
“OUT–FLOW” Point :
The presence of a little upper cross (“X”) means that the point is connected.
“CLASSIFIER” POINT”
The presence of a little upper cross (“X”) means that the point is connected.
“Bridge” :
“ETB Port” (also called “(R)STPBridgePort”):
“RSTP Port” :
NOTES:
ES Node: representing the ISA–ES virtual nodeLOCAL ETHERNET PORT: representing the local ethernet accessREMOTE ETHERNET PORT: representing the remote ethernet access (ethernet over sdh)IN–FLOW: internal resource used into a “Local” or “Remote” ethernet port, in order to define and charac-terize an incoming ethernet data flowOUT–FLOW: internal resource used into a “Local” or “Remote” ethernet port, in order to define and charac-terize an outgoing ethernet data flowEth2ETS CLASSIFIER: representing the Classifier Point (identification), to classify the ethernet data flow;it defines the priority and the Vlan number of the flow; it can define also a range of Vlan links into an ethernetflow, if they are directed towards the same wayBridge: representing the logical bridge point to group the “Bridging” resources that have to work in “auto-learning” modality. NOTE: the name of this resourse is changed to SWITCH, in the Connection context.ETB Port (also called “(R)STPBridgePort”): representing the Ethernet Port that has been configured towork in “autolearning” modalityRSTP Port: representing the logical Port that contains the parameters to define the STP/RSTP bridgemodality
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
105
01
/3AL 89871 AAAA AA
218
218
4.3.1.2 VISUALIZATION OF RESOURCES CONDITIONS IN THE TREE AREA:
Colors of the displayed resource:• colored (yellow, or blue, green, etc.) = available and in–service (active)• light grey = available but not–in–service• dark grey = out–of–context (not manageable in current application)
A little upper cross (above the resource symbol) means that the resource is a connection point.A little lower black point (under the resource symbol) means that the resource contains active PM (Perfor-mance Monitoring) points. NOTE: the black point is displayed only in the “Performance” domain.
4.3.1.3 ALARMS VISUALIZATION IN THE TREE AREA:
Alarms summary : (at level of ES Node)
The Alarms summary is visualized only at the ES Node level, reporting the colors of the maximum alarmseverities, detected in the current ES Node (inner circle) and in the contained resources (outer rings). Ifthe inner circle is not colored, it means that the alarms are in the contained resources and not in the parentone.
Alarms synthesis (only at the ports level):
The Alarms synthesis is visualized at all the ports, reporting all the alarm severity colors (in form of concen-tric rings), detected in the current resource (inner circle) and in the contained resources (outer rings). Ifthe inner circle is not colored, it means that the alarms are in the contained resources and not in the parentone.The colors of the alarms are detailed in section 5 (“Maintenance”).
4.3.1.4 SPONTANEOUS INFORMATION ABOUT RESOURCES IN THE TREE AREA:
A self–explaining message appears under the mouse cursor, when it is passed over an active field; thismessage reports the status–information, when the mouse is passed over the resources listed in the “Tree”area (see Figure 61. page 105); more information is given by pressing the F12 key on the keyboard.This spot gives information about: Traffic Label, Traffic Contract, Connection Type, Alarms, etc.
Figure 61. Spontaneous information message example
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
106
01
/3AL 89871 AAAA AA
218
218
4.4 List of the menus options
The menu bar contains all the options for the configuration and supervision of the ISA–ES Elements.
These paragraphs list all the menus options. Their usages and functions are described in other paragraphsthat are referenced; here a brief description is given for someone of them.
NOTE: some option of the menus can be sometime deactivated (greyed), if its function is not congruentwith the currently selected item or application, or when it is not yet operative.
The menu bar contains “permanent menus” (always displayed) and other “specific menus”, alternative be-tween them, displayed only when a particular application is selected in the “Application tabs”, or when theyare selected in the “Views” items. Starting from left, the menus are:
– Permanent Menus
• Views (first column). See options in para.4.4.1 on page 107.
• Configuration (second column). See options in para.4.4.2 on page 108.
• Diagnosis (third column). See options in para.4.4.3 on page 109.
• Supervision (fourth column). See options in para.4.4.4 on page 109.
• MIB–Management (fifth column). See options in para. 4.4.5 on page 109.
• Help (last column: it activates the help system).See options in para. 4.4.9 onpage 113.
– Specific alternative Menus
• Transmission (sixth column) See options in para.4.4.6 on page 110.
• Connection (sixth column). See options in para. 4.4.7 on page 112.
• Performance (sixth column). See options in para. 4.4.8 on page 113.
– Pop–up Menus
NOTE: The menu items contained in the “contextual” pop–up menus are the same as those containedin the specific menus of the menu–bar; e.g.: the contextual pop–up item “Configure Ethernet Port” of theTransmission application can be also activated by selecting, in succession: “Transmission” in the applica-tions tabs, then a Local (or Remote) Ethernet port in the “Tree area”, then, in the menu–bar, “Transmission”–> “Ethernet Port Management” –>”Configure Ethernet Port” ; therefore for their details please refer to thedescription given for the equivalent menu–bar options.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
107
01
/3AL 89871 AAAA AA
218
218
4.4.1 “Views” menu introduction
It contains the following entries:
– Backward: To go to the backward view.
– Forward: To go to the forward view.
– Transmission: to enter the Transmission application. See options in para. 4.4.6 on page 110.It yields the “Transmission” menu in the sixth column of the menu bar.
– Connection: to enter the Connection application. See options in para 4.4.7 on page 112.It yields the “Connection” menu in the sixth column of the menu bar.
– Performance: to enter the Performance application. See options in para 4.4.8 on page 113.It yields the “Performance” menu in the sixth column of the menu bar.
– Arrange Windows: not yet operative
– Refresh: It refreshes the graphical views.It contains the following sub–options:• Refresh Tree: It refreshes the resources TREE.
– Open Object: not yet operative
– Open In Window...: not yet operative
– Search...: It activates a general search windowfrom wich a specific (or a group of) resource can be searched. (See para. 4.6.3,page 119).
– Filter...: not yet operative
– Print: It causes the printing of details for the selected resource list shown in the“Application Table” area. (See para. 4.6.4, page 121).
– Close...: not yet operative
– Exit: To close the ES–CT session.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
108
01
/3AL 89871 AAAA AA
218
218
4.4.2 Configuration menu introduction
It contains the following entries:
– Alarms Severities: To manage the Alarms Severity Assignment Profile (ASAP).See para. 4.7.1 on page 123.
– Set Alarms Severities: To associate an ASAP to a resource.See para. 4.7.2 on page 126.
– Set ACD level: not yet operative
– Traffic Descriptor: To manage the parameters defining the traffic.It contains the following sub–options:
• ETS Traffic Descriptor: to manage the Ethernet traffic parameters. Seepara. 4.9.2 on page 136.
– Link CreationWizard: (not yet operative).To start a wizard program for helping during the Links configurations. Thisprocedure recalls, in the right order, the necessary dialogue windows toconfigure the links parameters.
– Connection Wizard: (not yet operative). To start a wizard program for helping during theConnections configurations. This procedure recalls, in the right order, thenecessary dialogue windows to configure the cross–connections.
– Options: To set some options relevant to the CT graphic interfaceand to the applications (default values, measurement units, etc.).See para. 4.6.1 on page 116.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
109
01
/3AL 89871 AAAA AA
218
218
4.4.3 Diagnosis menu introduction
It contains the following entries:
– Alarms: To enter the “Alarms Surveillance” (AS) application.See para 4.7.5. page129. It contains the following sub–options:
• ISA Alarms: for the “Surveillance” of alarms relevant to the ES board.• Object Alarms: for the “Surveillance” of alarms relevant to the selected ob-
ject.• Transmission Alarms: for the “Surveillance” of alarms relevant to the
Transmission domain.
– Log Retrieval: To manage the Event Log Browser (ELB).See para. 4.7.6 on page 130. It contains the following sub–options:
• Event: to “browse” the logs relevant to the ES events.• Alarm: to “browse” the logs relevant to the ES alarms.
– Navigation: It contains the following sub–options:• EMLUSM: To navigate to the parent EML–USM layer (OMSN equipment).
See para. 4.7.7 on page 133.
4.4.4 Supervision menu introduction
It contains the following entries:
– Access State: To manage the supervision access states. See para. 4.5.1 page 114.It contains the following sub–options:
• OS: to switch the access from CT to the OS• Requested: to request the access for the local CT
– Alarms: To manage the alarms relevant to the supervision state.It contains the following sub–options:
• Re–synchronize: See para. 4.7.4 on page 128.• Allow Notification: See para. 4.7.3 on page 128.• Inhibit Notification: See para. 4.7.3 on page 128.
– Set Manager List: To manage the accesses to the local node from the various types ofmanagers that are available. See para.4.5.2 on page 115.
– Restart ISA: To restart the equipment software. See para. 4.5.3, page 115.Not operative in current release.
4.4.5 Mib–Management menu introduction
It contains the following entries:
– Backup/Restore DB: To manage the backup and restore of the MIB (configuration data–base).See para.4.8.1 on page 134.
– Compare two Backup Files: Not operative in current release.See para.4.8.2 on page 134.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
110
01
/3AL 89871 AAAA AA
218
218
4.4.6 Transmission menu introduction
It contains the following entries:
– ISA Management: To manage the transmission parameters for the ISA–ES unit.It contains the following sub–options:
• Configure ISA: See para.4.9.3 on page 141.• ISA Properties: See para. 4.9.4 on page 142.
– Bridge Management: To manage the transmission parameters for the Bridge functions.It contains the following sub–options:
• Configure (R)STP Bridge: See para.4.9.26 on page 169.• (R)STP Bridge Properties: See para. 4.9.27 on page 171.
– Ethernet Port Management: To manage the transmission parameters foran Ethernet port (Local or Remote). It contains the following sub–options:
• Configure Ethernet Port: Local port: See para. 4.9.6 on page 144.Remote port: See para. 4.9.7 on page 149
• Ethernet Port Properties: Local port: See para. 4.9.8, page 150.Remote port: See para. 4.9.9 on page 157.
• Substitute Server Layer: See para. 4.9.10 on page 158.ETH on GFPETH on LAPS
• Substitute Port Type: See para. 4.9.11 on page 159.Ethernet(ETS) –> Bridge(ETB)Bridge(ETB) –> Ethernet(ETS)
• Create ETS InFlow: See para. 4.9.12 on page 160.• Create ETS OutFlow: See para. 4.9.14 on page 163.• Create Ip Port: not operative.
– Ip Port Management: (not yet operative).
– Rsvp Port Management: (not yet operative).
– Sender Management: (not yet operative).
– ETS InFlow Management: To manage the transmission parameters for an InFlow point.It contains the following sub–options:
• Create Eth2ETS Classifier: See para. 4.9.22 on page 167.• Modify ETS InFlow: See para. 4.9.16 on page 165.• Delete ETS InFlow: See para. 4.9.20 on page 166.• ETS InFlow Properties: See para. 4.9.17 on page 165.
– ETS OutFlow Management: To manage the transmission parameters for an OutFlow point.It contains the following sub–options:
• Modify ETS OutFlow: See para. 4.9.18 on page 165.• Delete ETS OutFlow: See para. 4.9.21 on page 166.• ETS OutFlow Properties: See para. 4.9.19 on page 165.
– Classifier Management: To manage the transmission parameters for an ETS–Classifier point.It contains the following sub–options:
• Modify Classifier: See para. 4.9.23 on page 168.• Delete Classifier: See para. 4.9.25 on page 168.• Classifier Properties: See para. 4.9.24 on page 168.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
111
01
/3AL 89871 AAAA AA
218
218
– Bridge Port Management: To manage transmission parameters for an ETB Port.It contains the following sub–options:
• Configure (R)STP Bridge Port: See para. 4.9.28 on page 172• (R)STP Bridge Port Properties: See para. 4.9.29 on page 173.
– (R)STP Port Management: To manage the transmission parameters for an xSTP Port.It contains the following sub–options:
• Configure (R)STP Port: See para. 4.9.30 on page 174• (R)STP Port Properties: See para. 4.9.31 on page 176.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
112
01
/3AL 89871 AAAA AA
218
218
4.4.7 Connection menu introduction
It contains the following entries:
– (R)STP Switch Management: (not operative)To manage the connection parameters for an (R)STPSwitch. See para.4.10.11 on page 185.
It contains the following sub–options:• –––
– Ethernet Port Management: To manage the connection parameters for an Ethernet port.It contains the following sub–options:
• Create Ets XC One Step: See para.4.10.2 on page 179.
– ETS InFlow Management: To manage the connection parameters for an InFlow point.It contains the following sub–options:
• Create Ets XC: See para. 4.10.3 on page 181• Modify Ets XC: See para. 4.10.4 on page 183• Delete Ets XC: See para. 4.10.6 on page 184• Ets XC Properties: See para. 4.10.5 on page 183
– ETS OutFlow Management: To manage the connection parameters for an OutFlow point.It contains the following sub–options:
• Create Ets XC: See para. 4.10.7 on page 185; (not operative)• Modify Ets XC: See para. 4.10.8 on page 185; (not operative)• Delete Ets XC: See para. 4.10.10 on page 185• Ets XC Properties: See para. 4.10.9 on page 185
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
113
01
/3AL 89871 AAAA AA
218
218
4.4.8 Performance menu introduction
It contains the following entries:
– Ethernet Port Management:To manage the Performance Monitoring (PM) parameters for an Ethernetport. It contains the following sub–options:
• Configure Eth Aggr: See para. 4.11.1 on page 187• Eth Aggr Properties: See para. 4.11.2 on page 188.
– ETS InFlow Management: (not operative) To manage the Performance Monitoring (PM) parametersfor an InFlow point. It contains the following sub–options:
• Configure InFlow: (not operative) See para. 4.11.3 on page 190• InFlow Properties: (not operative) See para. 4.11.4 on page 191.
– ETS OutFlow Management: (not operative) To manage PerformanceMonitoring (PM) parametersfor an OutFlow point. It contains the following sub–options:
• Configure OutFlow: (not operative) See para. 4.11.5 on page 193• OutFlow Properties: (not operative) See para. 4.11.6 on page 194.
4.4.9 Help menu introduction
It contains the following entries:
– On Context: To activate a contextual help.
– Glossary: To display the glossary of the terms used.
– Spontaneous: To activate a spontaneous help, giving explanations aboutthe objects pointed by the mouse cursor.
– About : To display information about the ES–CT software.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
114
01
/3AL 89871 AAAA AA
218
218
4.5 Supervision management
In this paragraph and relevant sub–paragraphs general configuration referred to the equipment supervi-sion are described (ES–CraftTerminal access, local and upper management list, etc.).
4.5.1 Access state (allow or inhibit ES–Craft access)
The ES–NE can be managed by the OS (Operations System) or by the ES–CT. To control the competitionof the OS and the CT, a Local Access Control (LAC) is available.a) If the LAC is “granted” that means the CT is allowed to manage the NE. The icon with a key symbolhas a rectangular shape and its border is green.
b) If the NE is “isolated“ the icon with a key symbol has a rectangular shape and its border is blue.c) If the LAC is ”access denied” that means the OS manages the NE and the CT is not allowed to modifyNE configuration (it can only “read”).The icon with a key symbol has a circular shape.
If the LAC is ”requested” that means the CT has requested permission from the OS and is waiting for areplay.However the OS does continue to provide a certain number of services. These services include: Receptionand processing of alarms, Performance processing, Switching back to the OS access state.
The access state of an NE can be modified as follows:
1) Switching from the OS to the ES Craft Terminal access state
Select the Supervision pull down menu. Then select the Requested option from the Access Statecascading menu.
From the confirmation dialogue box that opens you can confirm or cancel the ”Craft access” operationusing the Yes or No push buttons. the request is up to the OS, which accepts or refuses it.If the OS doesn’t answer in a predefined time it is assumed that the NE is in the Craft access stateand can be managed from an ES–CT.
2) Switching from the ES–CT access state back to the OS access state
Select the Supervision pull down menu. Then select the OS option from the Supervision –> Ac-cess State cascading menu.From the confirmation dialogue box that opens you can confirm or cancel the ”OS access” operation.The NE is now managed by the OS.
N.B. The key symbol icon on the management states of the NE view indicates whether the NE is man-aged by a craft terminal or by the OS.
N.B. Local Craft Terminal access is denied on recovery phases after a loss of communication of theNE. When communication is lost with the NE, the OS automatically recovers the communicationand puts the state that was set before the loss of communication (therefore the Craft Terminalaccess can be denied or granted).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
115
01
/3AL 89871 AAAA AA
218
218
4.5.2 Set Manager list
This option allows the user to set the Manager list, i.e. to define the list and the priorities of the entities thatthe ES–CT can access and manage.
Select the Set Manager list option from the Supervision pull down menu.
The dialog–box contains the following field:
– Current Value : to define the current Operator as BM (Bandwidth Manager) or EML (Element Mana-gement Layer) .According to the user profile, the list can be read or read/write. If the user is not allowed, the “CurrentValue” cannot be edited.
OK button is used to validate the selection.
Cancel button closes the dialog without changes of the data.
Help button provides some useful information about the dialog.
Figure 62. Set Manager list
4.5.3 Restart ISA (Not operative)
The restart operation is a software restart.
Select the Restart ISA option from the Supervision cascading menu.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
116
01
/3AL 89871 AAAA AA
218
218
4.6 Generic and common functions
This paragraph and relevant sub–paragraphs describe the generic menu items, common to all the applica-tions:
– Configuration –> Options– Views –> Search– Views –> Print
4.6.1 Configuration –> Options
This function is accessible by selecting, in the menu bar: Configuration –> OptionsAn example of the displayed dialog window is reported in Figure 63. page 117.
These options permit to set some general parameters relevant to the initial default settlement, graphic in-terface, etc. A set of tabbed windows is displayed, where each of them is shown by clicking on the relevanttab (”Default Values”, “Format”, “Program”, “Measurement Units”):
– Default Values, i.e. the initial values that the system will automatically assign to some parameters:• Traffic Descriptor Name: default TD name• ASAP Name: default ASAP name
– Format, i.e. the format for some parameters:• Decimal : DotSeparator (“.”) or CommaSeparator (“,”) numerical notation• Date/Time : Long or Short
– Program, i.e. some parameters relevant to the graphical interface:• Language : the options are: “English (UK)”, or “English (US)”, or “Italian”• Tabular/Graphical Area : it is relevant to the ApplicationArea; the options are: “TabularMode”,
or “GraphicalMode”; the “GraphicalMode” (not operative) is applicable only in Performance Mo-nitoring (PM)
• Secondary Window Layout: it is relevant to the displayed dialog windows; possible options:“Full window Mode” (the dialogs are presented on only one window) or “Tabbed Window Mode”(the dialogs are presented on more windows, accessible by relative tabs), see para. 4.6.2, page118.
• Views Layout : the only option is “Tabbed Mode”
– Measurement Units :• Time : possible options: “MicroSec” or “MilliSec”• Size : possible options: “Cell” or “Octet”• BitRate : possible options: “CellPerSec” or “Kbps” or “Mbps”
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
117
01
/3AL 89871 AAAA AA
218
218
Figure 63. Configuration –> Options
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
118
01
/3AL 89871 AAAA AA
218
218
4.6.2 DIALOG WINDOWS PRESENTATION: “FullWindow” and “TabbedWindow”
This function is accessible by selecting, in the menu bar: Configuration –> Options and then clicking on“Program” tab, “SecondaryWindowLayout” field.
It is relevant to the displayed dialog windows; possible options: “Full window Mode” (the dialogs are pre-sented on only one window) or “Tabbed Window Mode” (the dialogs are presented on more windows, ac-cessible by relative tabs). They report the same fields, but represented in two different manners; see ex-amples on Figure 64. and Figure 65.
Figure 64. Configuration –> Options – Program (“Full Window Mode” example)
Figure 65. Configuration –> Options – Program (“Tabbed Window Mode” example)
NOTE: All the dialogue windows described in this handbook are reported in “FullWindow” mode, the infor-mation fields reported in the “TabbedWindow” mode are the same.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
119
01
/3AL 89871 AAAA AA
218
218
4.6.3 Views –> Search
This function is accessible by selecting, in the menu bar: Views –> SearchAn example of the displayed dialog window is reported in Figure 66. page 120.
This same dialog is also always recalled by the other applications, when a specific resource has to besearched and associated to the calling application.
This function permits to search a resource (or a group of). A set of tabbed windows is displayed, whereeach of them is shown by clicking on the relevant tab :ETS Inflow, ETS Inflow, ETS XC, Ethernet Port.
The searching can be extended over all the existing resources of that type or restricted to some particularconditions of that resource (e.g. connected/notconnected, in a range, etc.) by entering other parametersrelevant to the resource to be searched; i.e. the searching can be done also without defining any specificparameter, in this case it will find all the resources related to the tab window.The possible parameters for the searching criteria are listed below:
– ETS OutFlow :• Status : up / down• XC Status : CrossConnected / NotCrossConnected• Server Type : Ethernet• Port Range : from... to...
– ETS InFlow :• Status : up / down• XC Status : CrossConnected / NotCrossConnected• Service Type : Ethernet• Port Range : from... to...
– ETS Xc :• not operative
– Ethernet Port :• Status : up / down
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
120
01
/3AL 89871 AAAA AA
218
218
Figure 66. Views –> Search
At the bottom of the window there are the following buttons:
– Create : to create a new search criterion.
– Delete : to delete the selected search criteria.
– Search : to start the searching: at the end of the operation, the search results are tabled in the win-dow.
– Apply : this key is used when the search has been called by an application, to browse a resource;by pressing this key the selected resource will be passed to the relevant application.
– Close : to close the Search window.
– Print : to print the results of the searching. It shows the dialog described in 4.6.4, page 121.
– Help : to get helps about this function.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
121
01
/3AL 89871 AAAA AA
218
218
4.6.4 Views –> Print
This function is accessible by selecting, in the menu bar: Views –> PrintAn example of the displayed dialog window is reported in Figure 67. page 121.
This function permits to print the details concerning the list of resources shown in the “Application area”of the main view.The printing can be addressed to a Printer or to a File.In case of “File”, the user can browse the desired file by clicking on the key “Choose File”; the “OutputFormat” of the file can be chosen among “Pdf”, “Html”, “Postscript”, or “Ascii” types.
This same dialog is also always recalled by the other applications, when the properties details associatedto a resource have to be printed.
Press on “Ok” to print, on “Preview” to preview, or on “Cancel” to leave the dialog without printing.
Figure 67. Views –> Print
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
122
01
/3AL 89871 AAAA AA
218
218
4.7 Diagnosis and Alarms Configuration
Alarms indications are always present on the operator’s workspace. The different types of alarms, their numberand their severity level are represented in the various views and areas of the ES–CT (Severity and DomainAlarms Synthesis, Tree–Area, Information–Area, Alarms Surveillance application, etc. ). The alarms are repre-sented by symbols, or icons, or texts (depending on the context ), which change color when the relevant alarmis active. Thus, at any time, the user can know the number of alarms and their severity.
This paragraph and relevant sub–paragraphs describe some operations mainly related to the associationsof the alarms with an appropriate severity for faults diagnosis, and the activation of “Alarms Surveillance”.The faults and alarms details and description as well as their relevant maintenance are reported in thechapter 5 (“Maintenance”).The following functions are related:
– Alarms Severity Assignment Profile (ASAP) management,– Alarms re–synchronize,– Allow/Inhibit alarms notification,– Restart ISA,– Alarms Surveillance: ISA alarms– Alarms Surveillance: Object alarms– Alarms Surveillance: Transmission alarms
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
123
01
/3AL 89871 AAAA AA
218
218
4.7.1 Configuration –> Alarms Severity (ASAP management)
Managed entities yield alarms when they have some malfunctions. This paragraph deals with the configu-ration of ASAPs. An ASAP is a list of Alarm probable causes to which Severities Profiles are assigned,predefined or settable by the operator.This option permits to configure (create, modify, etc.) the ASAPs.
This same dialog is also always recalled by the other applications, when the association of an ASAP toa selected alarm or resource is needed.
Select the Alarms Severities option from the Configuration pull down menu.
The ASAP Management dialogue box is displayed, as follows:
Figure 68. ASAP Management dialogue box.
The default presented profiles are:• “no alarm”: all the alarms are disabled (“cleared”), i.e. they are not displayed by the ES–CT.• “path alarms”: all the alarms are enabled and set to “major” severity.• “all alarms”: all the alarms are enabled and set to “minor” severity.
The predefined profiles of these default ASAPs are listed in Table 9. page 125.
By clicking on any of the keys: Details or Create or Modify, a window as that of Figure 69. page 124 isdisplayed (example).
At the bottom of the window (Figure 68. ) there are the following other buttons:– Delete : to delete the selected ASAP.– Cancel : to close the window.– Print : to print the list of ASAPs.– Help : to get helps about this function.– Ok : this button is not active, because it can be used only to set the Alarm Severity to a resource, when
this dialog is recalled by the relevant resource configuration.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
124
01
/3AL 89871 AAAA AA
218
218
Figure 69. ASAP: severities profile example
CREATING AN ASAP:
As soon as the previous window (Figure 68. ) is presented, only the Create button is available, therefore,by clicking on this key the window of Figure 69. is displayed and the user can create a new ASAP.For this purpose follow the following steps:
– ASAP Identifier : fill this field with a name– Probable Causes Families : the category of alarms can be chosen among:
• Communication or Error Processing or Equipment or Quality Of Servicethe choosing of these families is not operative, in current release.
– Probable Cause Name :a list of alarms names belonging to the above selected family;the relevant severity associated to a selected alarm of the list is shown inthe adjacent field “Severity”; the other two fields indicate if it is “No ServiceAffecting” or “Service Indipendent” (these latter two fields are not opera-tive).
• Severity :this field contains a pull–down list of the possible severities to be associated to theselecte alarm, they are: “cleared”, “major”, “warning”, “minor”, “critical”, “indeterminate”; themeaning of these alarms severities is described in chapter 5 (“Maintenance”).
At the bottom of the window there are the following buttons:– Ok : to confirm the creation of this new asap.– Cancel : to close the window without doing any operation.– Print : to print a detail list of this ASAP.– Help : to get helps about this function.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
125
01
/3AL 89871 AAAA AA
218
218
GETTING DETAILS ON ASAPs:
After selecting a profile in the window of Figure 68. and clicking on the Details key, details about it aregiven on the displayed “ASAP Severity” window, the same as Figure 69. In this case the user can just check the associated severities, by clicking on the alarms name in the listProbable Cause Name and reading the associated severity in the Severity field; at the end click on Can-cel button to leave the dialogue.
MODIFYING AN ASAP:
After selecting a profile in the window of Figure 68. and clicking on the Modify key, the user can modifyit, on the displayed “ASAP Severity” window (Figure 69. ).In this case the user can change the associated severities, by clicking on the alarms name in the list Prob-able Cause Name and then choosing the appropriate severity in the pull–down list of the Severity field;at the end click on the Ok button to confirm the modifications.
SETTING AN ASAP TO A RESOURCE:
The ASAP association to a resource is carried out from the option “Configuration... (a resource)”, in the“Transmission” context; e.g.: for an Ethernet–port, select the Transmission application, then select therelevant Ethernet–port, then, in the pop–up menu, select the “Configure Ethernet Port” option; in the pre-sented window, in the “Configuration” sector there is the field “ASAP Name”, where the desired asap canbe configured: clicking on the [...] button, the window of Figure 68. page 123 will be recalled, then selectthe desired ASAP and click on “Ok” button.
ALARMS & SEVERITIES ASSOCIATION IN PREDEFINED ASAPs:
Table 9. Alarms & Severities association in predefined ASAPs
ALARM name ASAP_ID:“no alarm”
ASAP_ID:“path alarms”
ASAP_ID:“all alarms”
LOS (Loss Of Signal) cleared major minor
LOF (Loss Of Frame) cleared major minor
TSF (Trail Signal Fail) cleared major minor
PLM (PayLoad Mismatch) cleared major minor
GTM (GFP Type Mismatch) cleared major minor
SCD (Sdh Concatenation Degrade) cleared major minor
NOTE: “cleared” means that the alarm is not displayed by the ES–CT. The meaning of the other alarmsseverities is described in chapter 5 (“Maintenance”).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
126
01
/3AL 89871 AAAA AA
218
218
4.7.2 Set Alarms Severities
This option permits to send (i.e. to provision) a chosen ASAP to a selected EthernetPort, or to all the Ether-netPorts of the ES node.
Select the Set Alarm Severities option from the Configuration pull down menu.
The ASAP Enhanced dialogue box is displayed, as for the window shown in Figure 70. page 127.The ASAP currently operative on the selected object (only if EthernetPort) is highlighted, permitting tocheck the currently used ASAP.
To set an ASAP, fill fields and areas as follows:
• List of ASAPs sector:the list reports all the existing ASAP’s. One of them can be highlighted, if an EthernetPorthas been selected.Select one of the listed ASAP’s to be provisionedDetail: it gives details about the selected ASAP, with the same procedure as seen in para4.7.1, page 123.
• Apply to sector:(active only if an ASAP has been selected in the List of Asap’s)Choose Scope items:
Selected Object Only : it is active only if an EthernetPort has been selected. Ifmarked it means that the selected ASAP will be sent only to the selected object.ISA Switch : if marked it means that the selected ASAP will be sent to all the objects(EthernetPorts) of the node.Selected Object and Subordin... : not operative.
Choose Class(es) items:All Classes : not operativeSpecific Class(es) : it is marked by the system, if the above “ISA Switch” item ismarked, otherwise it is not active. It means that the selected ASAP will be set on allthe objects classes listed in the field below (EthernetPorts).Choose Current Asap : it applies a filter to provision only the objects that are associ-ated with the ASAP here indicated (path alarms/all alarms/ignore).
• Execution Monitoring sector:(it reports the progress counting of the resources as they are provisioned)Object Processed counter: total number of objects processedObject Ok counter: number of objects successfully processedObject Nok counter: number of objects where the Asap could not be changed.
At the bottom of the window there are the following other buttons:– Ok : to provision the selected ASAP and close the window– Apply : to provision the selected ASAP without closing the window– Cancel : to close the window without doing any operation– Help : to get helps about this function.
– NOTE : the ASAP association to a resource can be carried individually out also from the option “Config-ure (a resource)”, in the “Transmission” context; e.g.: for an Ethernet–port, select the Transmission ap-plication, then select the relevant Ethernet–port, then, in the pop–up menu, select the “Configure EthernetPort” option; in the presented window, in the “Configuration” sector there is the field “ASAP Name”, wherethe desired asap can be configured (e.g. see para 4.9.6 page 144 “Configure Ethernet–port”).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
127
01
/3AL 89871 AAAA AA
218
218
Figure 70. ASAP: Set Alarm Severities (example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
128
01
/3AL 89871 AAAA AA
218
218
4.7.3 Allow/Inhibit Alarms Notifications
The system provides the possibility to allow/inhibit the spontaneous incoming alarms notifications on theES–CT.
i ) To inhibit alarm notification,Select the Supervision pull down menu and then select the Inhibit Notification option from theAlarms cascading menu.From the confirmation dialogue box that opens you can confirm or cancel the operation using the Okor Cancel push buttons respectively.To inform the operator that alarms have been inhibited, the labels of the alarm panel are greyed out,as shown below:
N.B. Inhibiting the alarms notification means that they are not forwarded to the ES–CT, butalarms are still generated by the NE.
j ) To allow alarm notificationSelect the Supervision pull down menu and then select the Allow Notification option from theAlarms cascading menu; note: this option will be available only after the above described “InhibitNotification”.From the confirmation dialogue box that opens you can confirm or cancel the operation using the Okor Cancel push buttons respectively; after this operation, the alarms will be displayed and notifiedagain by the ES–CT.
4.7.4 Alarms re–synchronization
The system provides the possibility to recover alarms present on the ES–NE and to update the currentproblem list (Alarms Surveillance) of the NE. After this operation, the ES–NE and the ES–CT currentalarms list (Alarms Surveillance) will be consistent.
To re–synchronize the alarms, select the Supervision pull down menu and then select the Resynchronizeoption from the Alarms cascading menu.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
129
01
/3AL 89871 AAAA AA
218
218
4.7.5 Alarms Surveillance (Diagnosis –> Alarms option)
This paragraph illustrates the access to the “Alarms Surveillance” application of the ES–CT.
NOTE: detailed information about the significance of alarms and statuses is given in section 5(“Maintenance”) of this handbook.
Select the Diagnosis pull down menu and then the Alarms cascading menu; the following options are of-fered:
– ISA Alarms: all the ES alarms are listed in the Alarms Surveillance reportwhich is activated.
– Object Alarms: only the alarms relevant to the selected object are listedin the Alarms Surveillance report.
– Transmission Alarms: only the alarms relevant to the Transmission context are listedin the Alarms Surveillance report.
Selecting any of the previously seen options, the Alarms Surveillance (AS) report is displayed as for theexample of the following figure (this example is relative to “ISA Alarms” option).
This view shows first a synthesis of the ES–NE alarms (“Counter Summary” window) with the sum of allalarms, then a detailed list of alarms of the selected filter (Alarms Sublist).
Figure 71. Alarms Surveillance (“ISA Alarms” example)
Detailed information for each alarm is supplied in the “Alarm Sublist” window.For example: the resource where the alarm is detected, the status, the type, the probable cause of therelevant alarm, etc.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
130
01
/3AL 89871 AAAA AA
218
218
The listing of all the Alarms or the filtering of a class of them is also possible.
The information supplied helps the operator, typically during troubleshooting operation, presented in nextsection of this handbook (chapter 5 “Maintenance”), where more details about alarms are given).
Detailed description about this application is given in the “AS Operator’s Handbook”.
4.7.6 Event Log Browser (Diagnosis –> Log Retrieval)
This paragraph illustrates the access to the “Event Log Browser” (ELB) application of the ES–CT.
NOTE1: more information about the significance of alarms and statuses is given in section 5(“Maintenance”) of this handbook.
NOTE2: detailed description about the Log application is given in the “ELB Operator’s Handbook”.
Select the Diagnosis pull down menu and then the Log Retrieval cascading menu; the following optionsare offered:
– Event: all the events related to the selected ES Unit are listed in thelog report that will be activated.
– Alarm: all the alarms related to the selected ES Unit are listed in thelog report that will be activated.
Selecting one of the previously seen options, the Event Log Browser (ELB) starts. First of all it displaysa “Filter” dialog windows, where the user can choose the object and the time period to be applied to thelog report. After completing the filter dialog, the ELB displays the desired report, where detailed informationfor each Event or Alarm is supplied.
This information helps the operator typically during troubleshooting operation, presented in next sectionof this handbook (chapter 5 “Maintenance”), where more details about alarms are given.
– Event: in this case the filter dialog presents an “Event Type” and an “Event Time” pane, in order tochoose the filter parameters (see Figure 72. page 130).
Figure 72. Log Retrieval: Event (Filter example)
– Click on Filter key and the Event report is then displayed as for Figure 73. page 131.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
131
01
/3AL 89871 AAAA AA
218
218
Figure 73. Log Retrieval: Event (Report example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
132
01
/3AL 89871 AAAA AA
218
218
– Alarm: in this case the filter dialog presents an “Event Type”, an “Event Time”, a “Perceived Severity”and a “Probable Cause” pane, in order to choose the filter parameters (see Figure 74. page 132).
Figure 74. Log Retrieval: Alarm (Filter example)
– Click on “Filter” key and the Event report is then displayed as for Figure 75. page 133.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
133
01
/3AL 89871 AAAA AA
218
218
Figure 75. Log Retrieval: Alarm (Report example)
4.7.7 Diagnosis –> Navigation to EML–USM
This function allows to navigate to the SDH context of the NE, i.e. to the SDH–CraftTerminal.
Select, in the menu–bar, the Diagnosis item and then the Navigation –> EMLUSM option.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
134
01
/3AL 89871 AAAA AA
218
218
4.8 MIB Management
This paragraph and relevant sub–paragraphs describe some operations related to the MIB management;MIB: Management Information Base, i.e. it is the data–base of the ES–NE configuration.
4.8.1 Backup/Restore DB
This function is accessible by selecting, in the menu bar: MIB–Management –> Backup/Restore DBAn example of the displayed dialog window is reported in Figure 67. page 121.
This function permits to save (backup) the ES–NE configuration and/or to restore it.
The backup (save) can be done writing a name for the current configuration in the field “Backup name”and then clicking on the “BackUp” key.
The restore can be done selecting a name in the field “Available Backup Files” and then clicking on the“Restore” key.The restoration function will take some time to finish and during this interval the ES–NE will not respondto the ES–CT.
Figure 76. MIBmanagement –> Backup/Restore DB
At the bottom of the window there are the following other buttons:– Delete : to delete the selected backup file.– Close : to close the window without doing any operation.– Help : to get helps about this function.
4.8.2 Compare two Backup Files (not operative)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
135
01
/3AL 89871 AAAA AA
218
218
4.9 Transmission
The transmission application permits to manage all the parameters related to the transmission context.It can be entered by selecting, in the menu–bar: “Views” –> “Transmission”, or by clicking on its relevanttab of the main view.
NOTE: All the dialogue windows described in this handbook are reported in “FullWindow” mode, the infor-mation fields reported in the “TabbedWindow” mode are the same (see para.4.6.2, page 118).
4.9.1 Ethernet Ports denomination and numbering
NOTE: the RemoteEthernetPorts are to be configured at the sdh side, before their usage, associatingthem with sdh containers; the choice of the sdh containers should be done according to the rate of the totalforecast data traffic; (SDH–CT option: “Configuration”–> “ISA Port Configuration”); see OMSN Operator’sHandbook for details about SDH configuration and connection.
The correspondence of Ports denomination between ES side and SDH side is the following: ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––| | ES–CT context | SdhCT context | ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––|LocalEthernetPorts: | ETHLocPort#n | Port Number=n ||RemoteEthernetPorts: | ETHRemPort#10n | Port Number=n | ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––( note: 10n stands for 1000+n )
ES1 board: the 8 LocalEthernetPorts are numbered 9,10, ... to 16; they are directly accessible at the8 apposite connectors on the frontpanel of the board; the numbering order is from the down to thetop side of the board.
ES4 board: the 8 LocalEthernetPorts are numbered 19,20, ... to 26; they are directly accessible atthe 8 apposite connectors on the frontpanel of the board; the numbering order is from the down tothe top side of the board. The GigaBit LocalEthernetPort is numbered 27, it is directly accessible atthe apposite connector on the frontpanel of the board.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
136
01
/3AL 89871 AAAA AA
218
218
4.9.2 Configuration –> Traffic Descriptor –> ETS Traffic Descriptor
This option is obtained by selecting, in the menu–bar: “Configuration” –> “Traffic Descriptor” –> “ETS Traffic Descriptor”.An example of the displayed dialog window is reported in Figure 77. page 136.
The function of this option is to show the existing traffic descriptions related to the ETS traffic, or to createa new one, to display (or print) the details about a selected one, and also to delete one of them.
This same dialog is also always recalled by the other Transmission applications, when the association ofa Traffic Descriptor (TD) to the relevant resource is needed.
Figure 77. Configuration: ETS Traffic Descriptor (example)
The parameters listed in Figure 77. page 136 are:• Traffic Descriptor: name of the traffic descriptor; Traffic Type: Traffic codification, according
to international standard conventions (details are given in next para.4.9.2.1).• CIR: Committed Information Rate; PIR: Peak Information Rate; CBS: Committed Burst Size;
PBS: Peak Burst Size. These latter parameters are explained in para 4.9.2.1.The keys presented at the bottom of Figure 77. page 136 are:
• Create (see para 4.9.2.1), Details (see para 4.9.2.4), Modify (see para 4.9.2.5): to create a newTraffic Descriptor, or to get details about or to modify a Traffic Descriptor
• Delete : to delete the selected Traffic Descriptor• Close : to close the window• Print : to print details about the selected Traffic Descriptor• Help : to get helps about this function.
NOTE: when this dialog is recalled by a resource configuration, it displays the additional keys “Apply” (toassociate the selected TrafficDescriptor to the resource), and “Cancel” (to exit without TD association).
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
137
01
/3AL 89871 AAAA AA
218
218
4.9.2.1 Creating a new ETS Traffic Descriptor
After clicking on “Create” key (Figure 77. page 136), the following dialogue is popped–up (example):
Figure 78. Create an ETS Traffic Descriptor (example)
Referring to Figure 78. , page 137, fill fields and areas as follows:• Traffic descriptor Name: insert a traffic descriptor name;• Traffic Type: identification of the traffic, in terms of international standard codifications; possible
options:
a ) Best Effort Serviceb ) Guaranteed Service (not available in current release)
According to the Traffic Type, the following QoS parameters will be displayed in the dialog ofFigure 78. , page 137:• CIR : Committed Information Rate; range= 0 to PIR (expressed in Kb/sec). It is the normal me-
dium rate of the data flow (Effective Bandwidth). It is settable only if the traffic (b ) has been se-lected.
• PIR : Peak Information Rate; range= 64 to physical–line–rate (expressed in Kb/sec). It is themaximum rate up to which the source can transmit for a short time period. In the case of (b )traffic, this parameter is automatically set equal to CIR by the system.
• CBS : Committed Burst Size (committed number of bytes for which the source may transmit thePIR); range= 0 to 16384 bytes (see note below); it is settable only if the traffic (b ) has beenselected.
• PBS : Peak Burst Size (maximum number of bytes for which the source may transmit the PIR);range= 1 to illimited bytes (see note below). In the case of (b ) traffic, this parameter is automati-cally set equal to CBS by the system. A value greater than 1000 is advisable.
NOTE: in this release the traffic parameters are fixed to:Best Effort; CIR=0, PIR=1000 (kb/s), CBS=0, PBS=2000 bytes
To confirm the inserted values click on Ok button.NOTE: for more details see also para. 4.9.2.2 (page 138) and 4.9.2.3 (page 139).
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
138
01
/3AL 89871 AAAA AA
218
218
4.9.2.2 Stacked–VLAN, Policing Mode and Color Profile (not available in current release)
NOTE: These parameters (not yet available) are assigned by means of the options “Create ETS Inflow”and “Create ETS Outflow”
The Traffic in the network may be policed or not, prioritized or not, depending on the network conditionsand the parameters of the traffic.The prioritization of an Ethernet data flow can be indicated on the 3 “user–priority” bits (802.1p) of the“Tagged–Ethernet” frame and also on the 3 “provider–priority” bits of the “Stacked–Vlan” frame; (seeframes formats in para. 1.3.1, page 36). Therefore 8 levels of user–priority exist: pri0 ... to pri7, where pri0is the minimum and pri7 the maximum; other 8 levels for provider–priority are possible, if the “Stacked–VLAN” mode is enabled.In the MPLS network, three levels of priority are contemplated: green, yellow and red, whose code is indi-cated on the 3 EXP bits of the MPLS frame; where green means the maximum priority and red the minimum(green packets are always passed first, yellows may be passed or blocked, reds are always blocked).In function of the traffic contract and of the policing mode, the priority of a data flow into the MPLS networkis assigned by the MPLS traffic scheduler of the system.In case that the policing is in “color–aware” mode, the MPLS–prioritization granularity is made deeper, tak-ing into account the single VLAN–priorities, that can have assigned to any of them a green or yellow orred color.
The following Table 10. and Table 11. contain the relationships among Stacked–VLAN, TrafficDescriptor,PolicingMode and ColorProfile.
Traffic Descriptor Policing Mode Color Profile (1) MPLS Colouring (2)
BEST EFFORT “disabled” only “Unbound” YELLOW
“color–blind” YELLOW or RED
GUARANTEED “disabled” only “Unbound” GREEN
“color–blind” GREEN or RED
REGULATED “disabled” “Unbound” GREEN
“Bound” (3) GREEN or YELLOW
“color–blind” “Unbound” GREEN or YELLOW or RED
“color–aware” “Bound” (3) as assigned by the“ColorProfile”
Table 10. TrafficDescriptor, PolicingMode and ColorProfile for INFLOW resource
Notes on Table 10. See “Create ETS Inflow”, para 4.9.12, page 160Green: max MPLS priority, Red: min priority(1): “Unbound” means that “NoProfile” is associated to the ColorProfile field, or the “Unbind” key has beenclicked; “Bound” means that a ColorProfile has been assigned(2): in cases different from “color–aware”, the colouring is performed by the scheduler, depending on thetraffic condition(3): in this case the “Priority” value of the associated Classifier must be different from “untagged”or “don’t care”
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
139
01
/3AL 89871 AAAA AA
218
218
Stacked–VLAN Management Priority Mode VLAN Provider–Prioritization
“Unbound” (1) – no provider–prioritization
“Bound” (1) “color blind” the packets are passed withoutany information about MPLS–colours
“color aware” green packets are assigned tothe priority as defined into the“StackPriority” fieldyellow packets are assigned tothe priority as defined into the“StackPriorityYellow” field
Table 11. Prioritization for OUTFLOW resource with “Stacked–VLAN management”
Notes on Table 11. See “Create ETS Outflow”, para 4.9.14, page 163(1): “Unbound” means that “0” value is associated to the “VlanManagement” field, or the “Unbind” key hasbeen clicked; “Bound” means that a VLAN–management profile has been assigned to this Outflow: in thiscase the StackedVLAN “shim” header is “pushed” into the ethernet frame
4.9.2.3 Traffic Bandwidth Limiting
NOTE: This parameter is assigned by means of the option “Configure (remote) EthernetPort”
The total traffic rate into Remote EthernetPorts can be controlled by the CAC function (Connection Admis-sion Control), if activated. For instance the limit can be fixed to 10 or 100 Mb/s, depending on the type ofethernet interface used at the end points. Infact, usually, the SDH available bandwidth can be greater thanthe standard ethernet interfaces, thus, this rate–limiting function avoids the configuration of a total com-mitted traffic greater than the ethernet physical rates.
The rate limiting function takes into account the sum of the CIR parameters of all the data flows afferentto a port, or, in the cases where the CIR is not defined, a single afferent flow’s PIR must not exceed thelimit.
See para. 4.9.8.1 page 155 (“Configure (remote) EthernetPort” : “Bandwidth Matching”) for details.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
140
01
/3AL 89871 AAAA AA
218
218
4.9.2.4 Getting details about ETS Traffic Descriptor
After selecting a Traffic Descriptor and clicking on “Details” key (Figure 77. page 136), a dialogue windowsimilar to Figure 78. , page 137 is popped–up.
The displayed dialog is read–only and gives the actual values of the parameters for the selected TrafficDescriptor. The meaning of the displayed parameters is described in the previous paragraph 4.9.2.1.
4.9.2.5 Modifying an ETS Traffic Descriptor
After selecting a Traffic Descriptor and clicking on “Modify” key (Figure 77. page 136), a dialogue as thatin Figure 78. , page 137 is popped–up.
The displayed dialog permits to change only the name, in the field “Traffic Descriptor Name”.
4.9.2.6 Associating an ETS Traffic Descriptor to a resource
The TrafficDescriptor association to a resource is carried out from the options “Configure or Modify... (aresource)”, in the “Transmission” context; e.g.: for an InFlow Point, select the Transmission application,then select the relevant InFlow Point, then, in the pop–up menu, select the “Modify InFlow” option; in thepresented window there is the field “Traffic Descriptor”, where the desired TD can be configured: clickingon the [...] button, the window of Figure 77. page 136 will be recalled, then select the desired TD and clickon “Apply” button.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
141
01
/3AL 89871 AAAA AA
218
218
4.9.3 Transmission: ISA : Configure ISA
This option is obtained, after selecting the ISA–ES node, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “ISA Management” –> “Configure ISA”.An example of the displayed dialog window is reported in Figure 79. page 141.
The function of this option is to manage the transmission parameters of the selected ISA–ES node.
To configure the ISA–ES node, fill fields and areas as follows:
• System Info sector:System Location: indicating where the MplsPrea is placed (read only field)Up Time: incremental time since the node was started up (read only field)Mgmt IP Address: indicating the assigned IP address (read only field)Software Version: it is relevant to the SW downloaded into the NE (read only field)
• MIB Default Value sector:Asap Severity: this field associates, among those reported in the pull–down menu, a se-verity to the alarm on violating the default values.
Figure 79. Configure ISA
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
142
01
/3AL 89871 AAAA AA
218
218
4.9.4 Transmission: ISA : ISA Properties
This option is obtained, after selecting the ISA–ES node, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “ISA Management” –> “ISA Properties”.An example of the displayed window is reported in Figure 80. page 142.
The function of this option is to show the transmission parameters set for the selected ISA–ES node.All the reported information fields are read–only, and are the same as those explained ones for “ConfigureISA”, para. 4.9.3 page 141.
Figure 80. ISA Properties
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
143
01
/3AL 89871 AAAA AA
218
218
4.9.5 ISA: application table in the Transmission context
An example of Application Table associated to the ISA–ES node is illustrated in Figure 81. page 143.It is displayed in the area A2, after selecting the ISA–ES node in the resource–tree.It reports, in tabular form, the resources of the selected ISA–ES node.The table contains two folders: “Local Ethernet Ports”, “Remote Ethernet Ports” .“Local Ethernet Ports” lists the main parameters related to this topic:“Alarms Synthesis”, “Name”, “Total Bandwidth (indicated by the supporting pipe)”, “Oper. Status”, “Admin-istration Status”.“Remote Ethernet Ports” lists the main parameters related to this topic:“Alarms Synthesis”, “Name”, “Total Bandwidth (indicated by the supporting pipe)”, “Oper. Status”, “Physi-cal Type”, “Administration Status”.
The properties of a resource of the table are displayed in the information area (A3), after selecting a rowof the table.A pop–up menu, related to the selected resource, can be activated, after selecting an item of the table andpressing the right button of the mouse.The listed parameters, the displayed properties and the options of the pop–up menu are described in thesuccessive paragraphs.
Figure 81. ISA–ES node: transmission application table
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
144
01
/3AL 89871 AAAA AA
218
218
4.9.6 Transmission: Ethernet Port : Configure (LOCAL) Ethernet Port
This option is obtained, after selecting a LOCAL EthernetPort, by means of the contextual pop–up menu,or by selecting in the menu–bar: “Transmission” –> “Ethernet Port Management” –> “Configure Ethernet Port”.An example of the displayed window (in TabbedWindow mode) is reported in Figure 82. page 146.
The function of this option is to manage the transmission parameters of the selected local EthernetPort.
To configure a local EthernetPort, fill fields and areas as follows:
• Configuration sector:Name: indicating the name assigned by the system to the Port (read only field)Type: indicating the type of port (read only field, fixed to “ethernetCsmacd”)Underlying Layer: associated layer (read only field, in this case fixed to “mau”)Last Change: the value of SystemTime when the port entered its current operational stateMTU: Maximum Transmit Unit; size of the largest packet which can be sent/received onthe interface, specified in octets (read only field, fixed to “1600”)Connector: (true/false) indicating if the interface has a physical connector (read only field)MAC Address: indicating the assigned MAC address (read only field, set by the system)Discard Errored Frames: indicating whether errored frames are to be discarded (readonly field, set by the system= “true”)Client Type: indicating the transported layer (read only field, set by the system= “ets”)Admin. Status: Administration status, possible pull–down options:
up : to set the port in–servicedown : to set the port out–of–service
Oper. Status: operational status, (read only field, set by the system) possible options:up : the port is availabledown : the port is unavailable
Bandwidth: max band capacity offered by the associated underlying physical channel(read only field, set by the system); possible pull–down options:10BaseT : 10 Mb/s100BaseT : 100 Mb/s1000Base : 1Gb/s
Alias: friendly name for the interface as specified by the userLink Up Down Trap: indicating whether linkUp / linkDown traps (notification upon thechanging of the node operational state from up to down and vice versa) should be gener-ated for this interface; possible options: enabled / disabled .Promiscuous Mode: indicating whether this interface has to inspect
the packets’ MAC addresses; possible options:enabled : the MAC packets are accepted regardless of their MAC addressesdisabled (not available) : the MAC packets addresses are inspected beforetheir acceptance
Encaps. Method: method of MAC packets encapsulation inside the underlying physicallayer; possible options:
ethernetV2 : default mode, set by the systemIEEE8023 : not yet operative
Asap Name: name of alarms profile to be associated to the current Port:
the key permits to choose and associate an asap to this resource, recallingthe dialogue described in para. 4.7.1 page 123
the key gives the asap properties currently associated to this resource
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
145
01
/3AL 89871 AAAA AA
218
218
Protocol Profile: (not available) name of the 2–bytes provider VLAN–protocol–tag to be“pushed” into the ethernet frame of data flows afferent to the current Port:
the key permits to choose and associate a provider protocol–tag to thisresource, recalling the dialogue described in para. 4.9.6.1 page 147
the key gives the Prot.–tag properties currently associated to this resource
• Alarms sector:this group reports the alarms relevant to the EthernetPort; their color is green if not–alarmed, if alarmed their color will be congruent with the severity assigned in the associat-ed ASAP; the alarms colors are described in section 5 (“Maintenance”).
• MAU sector:MAU Identifier: assigned by the system (read only field, fixed to “1”)MAU Jack Id: assigned by the system; identifier of the MAU connector that is associatedto the ”MAU Id”; (possible values are: 1, 2, 3, 4) for each MAUType: symbolic name of the mau interfaceStatus: mau current status (read only field), possible pull–down options:
operational / shutdownMedia Available: (read only field); medium availability; options: “available”/“not avail-able”/“other”Default Pause: (read only field); pause signal that can be inserted into the negotiation sig-nalling; possible options: “disable”/“symmetric”/“asymmetric”Jabber State: (read only field); state of the jabber process (checking about abnormal datatransmissions longer than the max permissible packet length)Default Type: possible pull–down options:
10BaseTFD :100BaseTXFD :
Type List: list of available interfaces typesAuto Neg. Support: indicating (true/false) if the auto–negotiation is supportedJack Type List: (read only field) list of available connectors types
• Auto Negotiation sub–sector:Admin. Status: Administration status, possible pull–down options:
enabled : auto–neg. enablingdisabled : auto–neg. disabling
Remote Signalling: notification about the detection of auto–neg. remote signallingProcess Status : current status of the auto–negotiation processRestart : (possible buttons: “Apply/Refresh”), to apply or refresh the ethernet link re–ne-gotiationLocal Capability Options: containing two fields: “Available”, “Current”; set of capabilitiesadvertised by the local auto–negotiation entityRemote Capability Options: containing the field: “Available”; set of capabilities receivedfrom the remote auto–negotiation entity (read only field)
After setting all the desired parameters, click on the “Ok” key to send the chosen parameters to the Ether-netPort.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
146
01
/3AL 89871 AAAA AA
218
218
Figure 82. Configure (local) Ethernet Port
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
147
01
/3AL 89871 AAAA AA
218
218
4.9.6.1 Create Protocol Profile (not available in current release)
This option is obtained, in the “Configure Ethernet Port” window (Figure 82. page 146), after clicking on
the key of the “ProtocolProfile” item.An example of the displayed window is reported in Figure 83. page 147.
The function of this option is to manage the ProtocolProfiles to be associated to the Ethernet Ports re-sources. The ProtocolProfile defines the provider protocol–tag to be inserted into the 2–bytes field of theStacked–VLAN shim header.It reports the list of the existing ProtocolProfiles, with relevant value in hex code.Furthermore it contains:the “Create” button, permitting to create a new ProtocolProfile as explained below;the “Details” button, permitting to see the properties of an existing ProtocolProfile;the “Modify” button, permitting to change the name of an existing ProtocolProfile;the “Delete” button, permitting to delete an existing ProtocolProfile;the “Apply” button, permitting “to bind” the selected ProtocolProfile to the related port;the “Cancel” button, permitting to close the window without associating a ProtocolProfile;the “Print” button, permitting to print the properties of a selected ProtocolProfile;the “Help” button, permitting to have information about this current function.
Figure 83. List of Protocol Profile
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
148
01
/3AL 89871 AAAA AA
218
218
To create a ProtocolProfile, click on “Create” key (Figure 83. page 147) and then the dialog box indi-cated in fig Figure 84. page 148 will be displayed; fill fields and areas as follows:
• Protocol Profile Name: type a mnemonic name
• Value (HEX): type an hexadecimal value for the provider protocol–tag that will be inserted intothe 2–bytes field of the Stacked–VLAN shim header; the value identifies the network providerand has to be 2–bytes long in hexadecimal notation; the third non–included byte is forced bydefault to “0x”.
click on the “Ok” button, to close and save the new ProtocolProfile;click on the “Cancel” button, to close the dialog without saving the new ProtocolProfile;click on the “Help” button, to get information about this window.
Figure 84. Create Protocol Profile
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
149
01
/3AL 89871 AAAA AA
218
218
4.9.7 Transmission: Ethernet Port : (LOCAL) Ethernet Port Properties
This option is obtained, after selecting a Local EthernetPort, by means of the contextual pop–up menu,or by selecting in the menu–bar: “Transmission” –> “EthernetPort Management” –> “EthernePort Properties”.An example of the displayed window is reported in Figure 85. page 149.
The function of this option is to show the transmission parameters set for the selected local Ethernet port.All the reported information fields are read–only, and are the same as those explained ones for “ConfigureEthernetPort”, para. 4.9.6, page 144.
Figure 85. (Local) Ethernet Port Properties
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
150
01
/3AL 89871 AAAA AA
218
218
4.9.8 Transmission: Ethernet Port : Configure (REMOTE) Ethernet Port
This option is obtained, after selecting a REMOTE EthernetPort, by means of the contextual pop–upmenu, or by selecting in the menu–bar: “Transmission” –> “Ethernet Port Management” –> “Configure Ethernet Port”.An example of the displayed window is reported in Figure 86. page 153 (GFP) and Figure 87. page 154(LAPS). NOTE: the switch between GFP and LAPS framing type is done by means of “Substitute ServerLayer”, see para. 4.9.10, page 158.
The function of this option is to manage the transmission parameters of the selected remote EthernetPort.NOTE: before doing this operation, the user should have done, on SdhCT application, the configurationof this same port, defining its SDH specific container. See also the note in para. 4.9.8.2, page 157.
To configure a remote EthernetPort, fill fields and areas as follows:
• Configuration sector:Name: indicating the name assigned by the system to the Port (read only field)Type: indicating the type of port (read only field, fixed to “ethernetCsmacd”)Last Change: the value of SystemTime when the port entered its current operational stateMTU: Maximum Transmit Unit; size of the largest packet which can be sent/received onthe interface, specified in octets (read only field, fixed to “1600”)Connector: (true/false) indicating if the interface has a physical connector (read only field)MAC Address: address of the selected ethernet port (logical address set by the system)Alias: friendly name for the interface, it can be specified by the userDiscard Errored Frames: indicating whether errored frames are to be discarded –––(read only field, set by the system= “true”)Client Type: indicating the transported layer (read only field, set by the system= “ets”)Admin. Status: Administration status, possible pull–down options:
up : to set the port in–servicedown : to set the port out–of–service
Oper. Status: operational status, (read only field, set by the system) possible options:up : the port is availabledown : the port is unavailable
Link Up Down Trap: indicating whether linkUp / linkDown traps (notification upon thechanging of the node operational state from up to down and vice versa) should be gener-ated for this interface; possible options: enabled / disabled .Promiscuous Mode: indicating whether this interface has to inspect
the packets’ MAC addresses; possible options:enabled : the MAC packets are accepted regardless of their MAC addressesdisabled (not available): the MAC packets addresses are inspected beforetheir acceptance
Encaps. Method: method of MAC packets encapsulation inside the underlying physicallayer; possible options:
ethernetV2 : default mode, set by the systemIEEE8023 : not yet operative
Asap Name: name of alarms profile to be associated to the current Port:
the key permits to choose and associate an asap to this resource, recallingthe dialogue described in para. 4.7.1 page 123
the key gives the asap properties currently associated to this resource
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
151
01
/3AL 89871 AAAA AA
218
218
Protocol Profile: (not available) name of the 2–bytes provider VLAN–protocol–tag to be“pushed” into the ethernet frame of data flows afferent to the current Port:
the key permits to choose and associate a provider protocol–tag to thisresource, recalling the dialogue described in para. 4.9.6.1 page 147
the key gives the Prot.–tag properties currently associated to this resourceTP/GFP SDH Configuration sub–sector:
this group permits to configure the matching between the SDH container and the ethernet-bandwidth used by the current port, performing, if activated, a rate limiting control bymeans of the CAC (Connection Admission Control); see also para. 4.9.8.1 page 155 andpara. 4.9.2.3 page 139.
Concatenation Type Set: available only if “UnderlyingLayer”=“vconc”; if marked itpermits to choose, in the “Bandwidth” field, the possible bandwidths that can be usedin virtual–concatenation modeRate Limiting Set: available only if “UnderlyingLayer”=“sdh”; if marked it permits tochoose, in the “Bandwidth” field, the possible bandwidths that can be used in Rate–Limiting modeUnderlying Layer: possible pull–down options:
vconc : (virtual concatenation); to permit the setting of the “virtual–concatena-tion granularity” modesdh : to permit the setting of the “Rate–Limiting” mode
Bandwidth [bps]: available bandwidth (band–limit) that can be used by the data flows af-ferent to the current Port:
the key permits to choose and associate a band–limit value to this re-source, recalling the dialogue described in para. 4.9.8.1 page 155
the key gives the band–limit properties currently associated to this re-source
Current SDH Speed: actual configured sdh rate (not operative)Vc Type: actual configured sdh VC type.
• Alarms sector:this group reports the alarms relevant to the EthernetPort; their color is green if not–alarmed, if alarmed their color will be congruent with the severity assigned in the associat-ed ASAP; the alarms colors are described in section 5 (“Maintenance”).
• GFP sector, displayed only if the port is GFP type (Figure 86. page 153):Enable FCS: (not operative); insertion or removal of GFP–FCS (Frame Check Sequence)field into the optional field pFCS of the GFP frame.Send Control: assignment of SignalLabel code (SL inserted into GFP frame); possiblepull–down options: “automatic”/“forced” (automatic means the tx SL shall be automaticallycalculated; forced means the tx SL will be always forced to the “equipped–non–specific”code).TxSL / RxSL / ExpSL: Signal Label management (Tx=transmitted, Rx=received, Exp=ex-pected).
• LAPS sector, displayed only if the port is LAPS type (Figure 87. page 154):Flag Ins.: insertion of Flag byte in the LAPS frame; possible pull–down options:“single”/“two” (single means consecutive frames; two means non–consecutive frames).Send Control: assignment of SignalLabel code (SL inserted into LAPS frame); possiblepull–down options: “automatic”/“forced” (automatic means the tx SL shall be automaticallycalculated; forced means the tx SL will be always forced to the “equipped–non–specific”code).
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
152
01
/3AL 89871 AAAA AA
218
218
TxSL / RxSL / ExpSL: Signal Label management (Tx=transmitted, Rx=received, Exp=ex-pected).
After setting all the desired parameters, click on the “Ok” key to send the chosen parameters to the Ether-netPort.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
153
01
/3AL 89871 AAAA AA
218
218
Figure 86. Configure (remote) Ethernet Port (GFP)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
154
01
/3AL 89871 AAAA AA
218
218
Figure 87. Configure (remote) Ethernet Port (LAPS)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
155
01
/3AL 89871 AAAA AA
218
218
4.9.8.1 Bandwidth matching
This option is obtained, in the “Configure (remote) Ethernet Port” window (Figure 86. page 153), after
clicking on the key of the “Bandwidth” item.NOTE: before doing this operation, the user should have done, on SdhCT application (with “IsaPortConfi-guration” option), the configuration of this same port, defining its SDH specific container. See also the notein para. 4.9.8.2, page 157.The user is recommended to configure the Ethernet–bandwidth and the SDH–containers in a congruentmode.
The total traffic rate into Remote EthernetPorts can be controlled by the CAC function (Connection Admis-sion Control), if activated. For instance the limit can be fixed to 10 or 100 Mb/s, depending on the type ofethernet interface used at the end points. Infact, usually, the SDH available container capacity can begreater than the band of standard ethernet interfaces, thus, this rate–limiting function avoids the configura-tion of a total committed traffic greater than the physical transport rates.In case of VirtualConcatenation mode, the function permits to set and to limit the bandwidth equivalent toa multiple of the number of sdh–VC’s that are used.The rate limiting function takes into account the sum of the CIR parameters of all the data flows afferentto a port, or, in the cases where the CIR is not defined (BestEffort traffic), a single afferent flow’s PIR mustnot exceed that limit.The displayed window is different, depending on the parameter “UnderlyingLayer”.If “UnderlyingLayer” =“sdh”, then a window as in Figure 88. page 156 will be displayed.If “UnderlyingLayer” =“vconc”, then a window as in Figure 89. page 156 will be displayed.
Rate Limiting case (Figure 88. page 156).
The function of this option is to manage the Rate Limiting to be associated to the current remote EthernetPort. It lists the possible sdh–VC rates that can be used, depending on the VC type that has been config-ured at the SDH side (by means of the SdhCT), for the current port. It is available only if the chosen sdh–VCis not concatenated.It reports the list of the possible rates, with relevant payload capacity:
if SdhVC = VC4, the possibilities are: 149,760,000; 100,000,000; 10,000,000if SdhVC = VC3, the possibilities are: 48,384,000; 10,000,000if SdhVC = VC12, the possibilities are: 2,176,000
Furthermore it contains:the “Ok” button, permitting “to bind” the selected RateLimiting to the related port;the “Cancel” button, permitting to close the window without associating a RateLimiting;the “Help” button, permitting to have information about this current function.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
156
01
/3AL 89871 AAAA AA
218
218
Figure 88. Rate Limiting Combination (VC4 case)
Virtual Concatenation Granularity case (Figure 89. page 156).
The function of this option is to manage the VirtualConcatenationGranularity to be associated to the cur-rent remote Ethernet Port. It permits to set and to limit the bandwidth equivalent to a multiple of the numberof VC’s that are configured at the sdh side. The congruency between SDH side (container) and ISA–ESside (bandwidth) is recommended.
It contains the following areas and fields:Vconc Granularity: permitting to set the number (n) of concatenated packets, depending onthe type of concatenated VC chosen at the SDH side:
if SdhVC = VC12, then n_max=50if SdhVC = VC3, then n_max=2
VCi: Total Vconc Bandwidth:(VCi=VC12 or VC3); indicating the total concatenated bandwidthSDH Bandwidth: indicating the actual, configured and active SDH bandwidth.
Furthermore it contains:the “Ok” button, permitting “to bind” the selected Vconc to the related port;the “Cancel” button, permitting to close the window without associating a Vconc;the “Help” button, permitting to have information about this current function.
Figure 89. Virtual Concatenation Granularity manager (VC12 case)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
157
01
/3AL 89871 AAAA AA
218
218
4.9.8.2 Inconsistency error on Port configuration
NOTE: In case that the selected port has not been configured on SdhCT side, or if the Port actual parame-ters are not congruent with the Sdh side, the IsaEs–CT will return a window informing that there is an incon-sistency between SDH and port configurations; see figure below:
Figure 90. Inconsistency error on Port Configuration
4.9.9 Transmission: Ethernet Port : (REMOTE) Ethernet Port Properties
This option is obtained, after selecting a Remote EthernetPort, by means of the contextual pop–up menu,or by selecting in the menu–bar: “Transmission” –> “EthernetPort Management” –> “EthernePort Properties”.An example of the displayed window is reported in Figure 91. page 157.
The function of this option is to show the transmission parameters set for the selected remote Ethernetport.All the reported information fields are read–only, and are the same as those explained ones for “ConfigureEthernetPort”, para. 4.9.8, page 150.
Figure 91. (Remote) Ethernet Port Properties
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
158
01
/3AL 89871 AAAA AA
218
218
4.9.10 Transmission: Ethernet Port : Substitute Server Layer
This option is obtained, after selecting a remote Ethernet Port, by means of the contextual pop–up menu,or by selecting in the menu–bar: “Transmission” –> “Ethernet Port Management” –> “Substitute Server Layer”.It contains two sub–options:
ETH on GFP : active only if the current framing type is LAPS over SDH, to change from LAPS to GFPETH on LAPS : active only if the current framing type is GFP over SDH, to change from GFP to LAPS.
An example of the displayed window is reported in Figure 92. page 158 and Figure 93. page 158.
This option permits to switch the server layer where the ethernet frames are encapsulated, between GFPover SDH and LAPS over SDH.
Figure 92. Substitute Server Layer (from GFP to LAPS)
Figure 93. Substitute Server Layer (from LAPS to GFP)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
159
01
/3AL 89871 AAAA AA
218
218
4.9.11 Transmission: Ethernet Port : Substitute Port Type
This option is obtained, after selecting an Ethernet Port, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “Ethernet Port Management” –> “Substitute Port Type”.It contains two sub–options:
Ethernet(ETS) –> Bridge(ETB) : active only if the current port type is ETS (i.e. the afferent trafficswitching is manually engineered), to change from ETS to ETB
In this case, after this operation, a new ETB port resource will be displayed beneath the Bridgesymbol in the ResourceTree area. Note: it will be displayed only after a “Refresh Tree” opera-tion.
Bridge(ETB) –> Ethernet(ETS) : active only if the current port type is ETB (i.e. the afferent trafficis automatically switched by means of “Mac Autolearning” procedure), to change from ETB to ETS
After this operation, the ETB port resource beneath the Bridge symbol will be cancelled. Note:it will be cancelled only after a “Refresh Tree” operation.
An example of the displayed window is reported in Figure 94. page 159 and Figure 95. page 159.
This option permits to switch the ethernet port resource, between “engineered” ETS and “bridged” ETB.
Figure 94. Substitute Port Type (from ETS to ETB)
Figure 95. Substitute Port Type (from ETB to ETS)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
160
01
/3AL 89871 AAAA AA
218
218
4.9.12 Transmission: Ethernet Port : Create ETS InFlow
This option is obtained, after selecting a remote (or local) ETS EthernetPort, by means of the contextualpop–up menu, or by selecting in the menu–bar: “Transmission” –> “Ethernet Port Management” –> “Create ETS InFlow”.NOTE: the option is available only if the selected ethernet port is ETS type (and not ETB), with “AdminSta-tus” = “up”.An example of the displayed window is reported in Figure 96. page 161.
The function of this option is to create an InFlow resource into the selected ETS ethernet Port.To create an InFlow object, fill fields and areas as follows:
• ETS InFlow: indexed name assigned by the system to the resource (read only)note : the index is incremental over all the existing inflows of all the ports
• User Label: optional name assigned by the user to describe this resource• Service Type: upper layer service type (read only field): Ethernet• Flow Type: possible options:
unicastNoAutolearning : for unicast linkmulticastOptionA : (not available in current release) for multicast link
• Traffic Descriptor indicating the name of the associated traffic descriptor (TD):
the key permits to choose and associate a traffic descriptor to the data flow, recallingthe dialogue described in para. 4.9.2 page 136.
the key gives the properties of the traffic descriptor currently associated.NOTE: the bandwidth associated to this resource must be congruent with the CIR/PIR val-ues indicated in the contract, with the band indicated in the mother–port, and also with thesdh rate capability of the logical port associated by means of the SDH–CraftTerminal ap-plication (see para. 4.9.2 page 136).
• Status: notification about the actual status of the resource;possible pull–down options (read only):up : the resource is in–service ; down : the resource is out–of–service
• Service Id: (set by the system); indicating the suffix number of the mother–port• Policing Mode: to set the policing on the ETS traffic; possible pull–down options:
disabled: the policing is not performedcolor–blind: (not yet available) the policing is based on the associated TDcolor–aware: (not yet available) the policing is based on the associated TD and on thepriority colours of the associated “ColorProfile” explained below
• VLANPop: (not yet available) possible values: “disabled” or “enabled”; if enabled it pops out the“provider Stacked–VLAN” shim fields of the ethernet frame. Note: if this is “enabled”, the “priori-ty” field of the relevant Classifier must be different from “untagged” or “don’t care”
• Color Profile: (not yet available) indicating the name of the association between the user–prior-ities and the MPLS traffic colours; Note: if a ColorProfile is associated, the “priority” field of therelevant Classifier must be different from “untagged” or “don’t care”
the key permits to choose and associate a color profile, recalling the dialogue de-scribed in para. 4.9.13 page 161
the key gives the properties of the color profile currently associatedthe “Unbind” key permits to untie the data flow from the color profile
NOTE1: more information about the traffic description, Policing, ColorProfile is reported in para. 4.9.2.2page 138.
NOTE2: under the same mother Eth.Port, all the inflows in “color–aware” mode must have the same“ColorProfile”; i.e. only one ColorProfile per EthPort is supported.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
161
01
/3AL 89871 AAAA AA
218
218
After setting all the desired parameters, click on the “Ok” key to create this new InFlow point, that will beshown in the tree–area, attached to the selected ethernet port.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
Figure 96. Create ETS InFlow
4.9.13 Transmission: Ethernet Port : Create ETS InFlow/ColorProfile (not yet available)
This option is obtained, in the “Create ETS Inflow” window (Figure 96. page 161), after clicking on the key of the “ColorProfile” item.An example of the displayed window is reported in Figure 97. page 162.
The function of this option is to manage the traffic ColorProfiles to be associated to the Inflow resources.It reports the list of the existing ColorProfiles, with relevant name and colour associated to the relevantpriority.Furthermore it contains:the “Create” button, permitting to create a new ColorProfile as explained below;the “Details” button, permitting to see the properties of an existing ColorProfile;the “Modify” button, permitting to change the properties of an existing ColorProfile;the “Delete” button, permitting to delete an existing ColorProfile;the “Apply” button, permitting “to bind” the selected ColorProfile to the related Inflow;the “Cancel” button, permitting to close the window without associating a ColorProfile;the “Print” button, permitting to print the properties of a selected ColorProfile;the “Help” button, permitting to have information about this current function.
NOTE: more information about the traffic description, Policing, ColorProfile is reported in para. 4.9.2.2page 138.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
162
01
/3AL 89871 AAAA AA
218
218
Figure 97. List of Color Profile (not available in current release)
To create a ColorProfile, click on “Create” key (Figure 97. page 162) and then the dialog box indicatedin fig Figure 98. page 162 will be displayed; fill fields and areas as follows:
• Color Profile Name: type a mnemonic name
• Priority0 ... to Priority7: choose, by means of the pull–down menu, the desired colour (green,or yellow, or red) to be associated to the relevant priority.
click on the “Ok” button, to close and save the new ColorProfile;click on the “Cancel” button, to close the dialog without saving the new ColorProfile;click on the “Help” button, to get information about this window.
Figure 98. Create Color Profile (not available in current release)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
163
01
/3AL 89871 AAAA AA
218
218
4.9.14 Transmission: Ethernet Port : Create ETS OutFlow
This option is obtained, after selecting a remote (or local) ETS EthernetPort, by means of the contextualpop–up menu, or by selecting in the menu–bar: “Transmission” –> “Ethernet Port Management” –> “Create ETS OutFlow”.NOTE: the option is available only if the selected ethernet port is ETS type (and not ETB), with “AdminSta-tus” = “up”.An example of the displayed window is reported in Figure 99. page 163.
The function of this option is to create an OutFlow resource into the selected ETS EthernetPort.
To create an OutFlow object, fill fields and areas as follows:
• ETS OutFlow Name: indexed name assigned by the system to the resource (read only field)note : the index is incremental over all the existing outflows of all the ports
• User Label: optional name assigned by the user to describe this resource• Server Type: server layer type (read only): Ethernet• Status: notification about the actual status of the resource; possible pull–down options:
up : the resource is in–servicedown : the resource is out–of–service
• Server Id: (set by the system); indicating the suffix number of the mother–port• VLAN Management: (not yet available) automatic incremental index identifying the Stacked-
VLAN–management profile; value “0” means that the SVLAN–management is disabled (“Un-bound”): in this case the StackedVLAN shim header is not “pushed” into the ethernet frame
the key permits to choose and associate a VLAN–management profile, recalling thedialogue described in para. 4.9.15 page 164
the key gives the properties of the VLAN–management profile currently associatedthe “Unbind” key permits to untie the data flow from the VLAN–management profile.
NOTE1: more information about the traffic description, ColorProfile and Stacked–VLAN is reported inpara. 4.9.2.2 page 138.
NOTE2: in case of Multicast (not yet available), all the multi–casted outflows must have the same VLAN–Management parameters.
After setting all the desired parameters, click on the “Ok” key to create this new OutFlow point, that willbe shown in the tree–area, attached to the selected ethernet port.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
Figure 99. Create ETS OutFlow
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
164
01
/3AL 89871 AAAA AA
218
218
4.9.15 Create ETS OutFlow / VlanManagement (not available in current release)
This option is obtained, in the “Create ETS Outflow” window (Figure 99. page 163), after clicking on the
key of the “VLAN Management” item.An example of the displayed window is reported in Figure 100. page 164.
The function of this option is to manage the “Stacked–VLAN” parameters to be associated to the outflowresources. It pushes, if activated, the Stacked–Vlan provider–ShimHeader to the ethernet frame.To create a VLAN–Management profile, fill fields and areas as follows:
• VLAN index: indexed value assigned by the system to this profile (read only)• VLAN value: Stacked–Vlan identifier to which associate these parameters• Priority Mode: possible options:
colorBlind : the packets are forwarded without taking into account the MPLS colours infor-mationcolorAware : the packets are forwarded as follows:
“green” packets are assigned to the priority level selected into the “Stack–Priority” field“yellow” packets are assigned to the priority level selected into the “Stack–Priority Yellow” field
• Stack Priority: priority level to be assigned to the “green” packets; possible options:pri000 to pri111 (min. priority= “pri000”, max = pri111)
• Stack Priority Yellow: priority level to be assigned to the “yellow” packets• Stack Status: possible options:
up : to activate this Stacked VLAN management profiledown : to deactivate this Stacked VLAN management profile
NOTE: more information about the traffic description, ColorProfile and Stacked–VLAN is reported in para.4.9.2.2 page 138.
After setting the desired parameters, click on the “Ok” key to create this new VLAN–Management profile.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
Figure 100. Create VLAN Management (not available in current release)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
165
01
/3AL 89871 AAAA AA
218
218
4.9.16 Transmission: ETS InFlow : Modify ETS InFlow
This option is obtained, after selecting an InFlow object, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “ETS InFlow Management” –> “Modify ETS InFlow”.
The function of this option is to modify the transmission parameters set for the selected InFlow point.All the reported information fields are the same as those explained ones for “Create InFlow”, para. 4.9.12,page 160.
4.9.17 Transmission: ETS InFlow : ETS InFlow Properties
This option is obtained, after selecting an InFlow object, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “ETS InFlow Management” –> “ETS InFlow Properties”.
The function of this option is to show the transmission parameters set for the selected InFlow point.All the reported information fields are read–only, and the same as those explained ones for “Create In-Flow”, para. 4.9.12, page 160.
4.9.18 Transmission: ETS OutFlow : Modify ETS OutFlow
This option is obtained, after selecting an OutFlow object, by means of the contextual pop–up menu, orby selecting in the menu–bar: “Transmission” –> “ETS OutFlow Management” –> “Modify ETS OutFlow”.
The function of this option is to modify the transmission parameters set for the selected OutFlow point.All the reported information fields are the same as those explained ones for “Create ETS OutFlow”, para.4.9.14, page 163.
4.9.19 Transmission: ETS OutFlow : ETS OutFlow Properties
This option is obtained, after selecting an OutFlow object, by means of the contextual pop–up menu, orby selecting in the menu–bar: “Transmission” –> “ETS OutFlow Management” –> “ETS OutFlow Properties”.
The function of this option is to show the transmission parameters set for the selected OutFlow point.All the reported information fields are read–only, and the same as those explained ones for “Create Out-Flow”, para. 4.9.14, page 163.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
166
01
/3AL 89871 AAAA AA
218
218
4.9.20 Transmission: ETS InFlow : Delete ETS InFlow
This option is obtained, after selecting an InFlow object, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “ETS InFlow Management” –> “Delete ETS InFlow”.Note: this option is not available and the resource will not be deleted if containing any inner resource (Clas-sifier), or if it is cross–connected, or also if it contains PM points.An example of the displayed window is reported in Figure 101. page 166.
This option permits to delete the selected InFlow point.
Figure 101. Delete ETS InFlow
4.9.21 Transmission: ETS OutFlow : Delete ETS OutFlow
This option is obtained, after selecting an OutFlow object, by means of the contextual pop–up menu, orby selecting in the menu–bar: “Transmission” –> “ETS OutFlow Management” –> “Delete ETS OutFlow”.Note: this option is not available and the resource will not be deleted if containing any inner resource, orif it is cross–connected, or also if it contains PM points.The displayed window is similar to that reported in Figure 101. page 166.
This option permits to delete the selected OutFlow point.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
167
01
/3AL 89871 AAAA AA
218
218
4.9.22 Transmission: ETS InFlow : Create Eth2ETS Classifier
This option is obtained, after selecting an InFlow object, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “ETS InFlow Management” –> “Create Eth2ETS Classifier”.An example of the displayed window is reported in Figure 102. page 167.NOTE: VLAN functions are not supported in current release.
The function of this option is to create a Classifier of the ethernet traffic into the selected InFlow; everyInFlow resource needs one or more classifiers. More classifiers can be created into the same InFlow, butheading to different VLAN ranges. It classifies the ethernet traffic to be transported over the ETS.To create an Eth2ETS Classifier, fill fields and areas as follows:
• ETS InFlow: indicating the name assigned by the system to the resource (read only field)• Classifier Index: incremental index assigned by the system to the resource (read only field)• VLan: (not operative) VLAN identifier number, in decimal format; range 0 to 4096 (2^12)• Priority: (not operative, set by the system to “don’t Care” ); to define the ETS priority level; pos-
sible pull–down options:pri000 , pri010 , don’tCare , pri111 , pri110 , pri001 , pri101 , pri100 , untagged(min. priority= “pri000”, max = pri111)Note: in cases that the related InFlow has been set with “VLAN–Pop”=“enabled” or “Color-Profile”=“bound”, then this value must be different from “don’tCare” or “untagged” .
• Status: possible pull–down options:up : to set the resource in–servicedown : to set the resource out–of–service
• Max VLan: (not operative) max VLan number on which the data flow can be linked; value ’0’means only one Vlan linked (the one indicated in the “VLan” field); a value greater than “VLan”field defines the Vlan range, in decimal format (e.g.: “VLan”=33 and “Max VLan”=50 defines thevlan range from 33 to 50).
• Max Priority: (not operative) max priority associable to this classifier, in binary format; value’0’ means only one priority, a value greater than the value set in “Priority” field defines the priorityrange.
NOTE: the VLAN identifiers defined here must be different from those ones defined in other classifiers ofthe same ethernet port, otherwise the classifier cannot be created.
After setting all the desired parameters, click on the “Ok” key to create this new Classifier point, that willbe shown in the tree–area, attached to the selected InFlow object.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
Figure 102. Create Eth2ETS Classifier
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
168
01
/3AL 89871 AAAA AA
218
218
4.9.23 Transmission: Classifier : Modify Classifier
This option is obtained, after selecting a Classifier object, by means of the contextual pop–up menu, orby selecting in the menu–bar: “Transmission” –> “Classifier Management” –> “Modify Classifier”.
The function of this option is to modify the transmission parameters set for the selected Classifier point.All the reported information fields are the same as those explained ones for “Create Eth2ETS Classifier”,para. 4.9.22, page 167.
4.9.24 Transmission: Classifier : Classifier Properties
This option is obtained, after selecting a Classifier object, by means of the contextual pop–up menu, orby selecting in the menu–bar: “Transmission” –> “Classifier Management” –> “Classifier Properties”.
The function of this option is to show the transmission parameters set for the selected Classifier point.All the reported information fields are read–only, and the same as those explained ones for “CreateEth2ETS Classifier”, para. 4.9.22, page 167.
4.9.25 Transmission: Classifier : Delete Classifier
This option is obtained, after selecting a Classifier object, by means of the contextual pop–up menu, orby selecting in the menu–bar: “Transmission” –> “Classifier Management” –> “Delete Classifier”.The displayed window is similar to that reported in Figure 101. page 166.
This option permits to delete the selected Classifier point.Note: the resource will not be deleted if containing any inner resource, or if it is cross–connected, or alsoif it contains PM points.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
169
01
/3AL 89871 AAAA AA
218
218
4.9.26 Transmission: Bridge : Configure (R)STP Bridge
This option is obtained, after selecting the Bridge node, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “Bridge Management” –> “Configure (R)STP Bridge”.An example of the displayed dialog window is reported in Figure 103. page 169.
The function of this option is to manage the (R)STP parameters of the selected Bridge node.
To configure the STP Bridge resource, fill fields and areas as follows:
• General Bridge Management sector:Bridge Type: possible pull–down options:
“bridge 802.1d” (set by the system); for MAC bridge functionsProtocol Type: possible pull–down options:
“STP” : for simple Spanning Tree Protocol functions“RSTP” : for Rapid Spanning Tree Protocol functions“TRANSPARENT” : to disable STP functions on the root bridge
STP Instance: this item permits to set the parameters of the STP functions for this node:
the key permits to set and associate a set of STP parameters, recallingthe dialogue described in para. 4.9.26.1 page 170
the key displays the STP instances currently associated to this bridge
Figure 103. Configure (R)STP Bridge
After setting the desired parameters, click on the “Ok” key to confirm.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
170
01
/3AL 89871 AAAA AA
218
218
4.9.26.1 STP Bridge Instances Configuration
This function is activated in the “Configure (R)STP Bridge” window (Figure 103. page 169), after clicking
on the key of the “STP Instances” item.An example of the displayed window is reported in Figure 104. page 171.
The function of this option is to manage the “STP Bridge Instances” to be associated to this nodeTo set the STP instances, fill fields and areas as follows:
• Address: Bridge identifier of this selected bridge, as specified in IEEE802.1D, composed of 8octets, of which the first 4 bits represent a priority parameter, the next 12 bits are consideredas local system ID, the remaining 6 octets represent the bridge address, similarly to a MAC ad-dress (read only, set by the system)
• Designated Root: (read only) representing the Bridge Identifier of the Bridge assumed to bethe RootBridge. If there are two or more Bridges with the same Root Path Cost, then the Bridgewith the best priority (least numerical value) is selected as the Designated Bridge.
• Priority: 16–bit decimal value, but only the most significant 4 bits are settable.The possible options are 16 values, settable by means of the associated incrementing/decrementing keys. (best priority = least numerical value).
• Root Path Cost: (read only) representing the cost of the path to the RootBridge as seen fromthis bridge for this spanning tree instance. When this Bridge is the RootBridge this parameterhas the value zero. Otherwise, it is equal to the sum of the values of the Designated Cost andPath Cost parameters held for the Root Port.
• Root Port: (read only) the port number of the port which offers the lowest cost path from thisbridge to the root bridge for this spanning tree instance. I.e., that Port for which the sum of thevalues of the Designated Cost and Path Cost parameters held for the Port is the lowest.
• Hold Time: (read only, only for STP, fixed to one second); interval length during which no morethan one Configuration Bridge PDUs shall be transmitted by this node.
• Time Since Change: time (in hundredths of second) since the last time a topology change wasdetected by this spanning tree instance.
• Topology Changes: (read only) total number of topology changes detected by this spanningtree instance since the management entity was last restarted or initialized.
• Hello Time: (read only: actual value that this instance is currently using); amount of time be-tween the transmission of Configuration bridge PDUs by this instance on any port when it is theRootBridge of the spanning tree or trying to become so, in units of hundredths of a second;(range=1 to 10 sec).
• Max Age: (read only: actual value that this instance is currently using); maximum age of Span-ning Tree Protocol information learned from the network on any port before it is discarded, inunits of hundredths of a second; (range=6 to 40 sec).
• Fwd Delay: (read only: actual value that this instance is currently using); this value, measuredin units of hundredths of a second, controls how fast a port changes its spanning state whenmoving towards the Forwarding state. The value determines how long the port stays in eachof the Listening and Learning states, which precede the Forwarding state. This value is alsoused, when a topology change has been detected and is underway, to age all dynamic entriesin the filtering Database. (Range=4 to 30 sec)
• Next Best Root Cost: (only for RSTP); cost of the path to the root through the next best rootport as seen from this bridge for this spanning tree instance.
• Next Best Root Port: (only for RSTP); port number of the next port which offers the lowest costpath from this bridge to the root bridge for this spanning tree instance. This port will become rootport if the actual root port goes down.
• TxHoldCount: (only for RSTP); used by the Port Transmit state machine to limit the maximumtransmission rate.
• Bridge Convergence Sensibility sector:
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
171
01
/3AL 89871 AAAA AA
218
218
the values considered in this sector are used by all bridges (for STP convergence sensibil-ity) when this bridge is acting as the RootBridge.Hello Time / Max Age / Fwd Delay: their meaning is explained above.
After setting the desired parameters, click on the “Ok” key to confirm these STP Instances set.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
Figure 104. STP Instances
4.9.27 Transmission: Bridge : (R)STP Bridge Properties
This option is obtained, after selecting the Bridge node, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “Bridge Management” –> “(R)STP Bridge Properties”.An example of the displayed window is reported in Figure 105. page 171.
The function of this option is to show the transmission parameters set for the selected Bridge node.All the reported information fields are read–only, and are the same as those explained ones for “Configure(R)STP Bridge”, para. 4.9.26 page 169.
Figure 105. (R)STP Bridge Properties
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
172
01
/3AL 89871 AAAA AA
218
218
4.9.28 Transmission: Bridge Port : Configure (R)STP Bridge Port
This option is obtained, after selecting a Bridge port (i.e. ETBport), by means of the contextual pop–upmenu, or by selecting in the menu–bar: “Transmission” –> “Bridge Port Management” –> “Configure (R)STP Bridge Port”.An example of the displayed dialog window is reported in Figure 106. page 172.
The function of this option is to manage the transmission parameters of the selected (R)STP Bridge port.
To configure the Bridge (ETB)port, fill fields and areas as follows:
• Bridge Port Configuration sector:Bridge Port Name: settable “alias” name for this portBridge Port State: (read only); current state of this port, informing about the action thisport takes on reception of a frame. Possible values:
disabled : the port is disabled by failure or by the administrative control. A Port in thisstate does not participate in frame relay or STP operations.dataframediscarding : data frames received in this port should be discarded, butthe control frame (such as BPDU)should be passed. The information of data frameand control frame is not learned.learning : data frames and control frames (such as BPDU) can be learned, but cannot be forwarded to other Bridge Ports.forwarding: data frames and control frames can be learned and forwarded
VLAN Identifier: set by the system, VLAN functions are not yet available.
After setting the desired parameters, click on the “Ok” key to confirm.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
Figure 106. Configure (R)STP Bridge Port
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
173
01
/3AL 89871 AAAA AA
218
218
4.9.29 Transmission: Bridge Port: (R)STP Bridge Port Properties
This option is obtained, after selecting an (R)STP Bridge port (ETBport), by means of the contextual pop–up menu, or by selecting in the menu–bar: “Transmission” –> “Bridge Management” –> “(R)STP Bridge Port Properties”.An example of the displayed window is reported in Figure 107. page 173.
The function of this option is to show the transmission parameters set for the selected Bridge ETBPort.All the reported information fields are read–only, and are the same as those explained ones for “Configure(R)STP Bridge Port”, para. 4.9.28 page 172.
Figure 107. (R)STP Bridge Port Properties
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
174
01
/3AL 89871 AAAA AA
218
218
4.9.30 Transmission: (R)STP Port : Configure (R)STP Port
This option is obtained, after selecting an (R)STP port, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “(R)STP Port Management” –> “Configure (R)STP Port”.An example of the displayed dialog window is reported in Figure 108. page 175.
The function of this option is to manage the transmission parameters of the selected RSTP port.
To configure the RSTP port, fill fields and areas as follows:
• Ethernet Port Configuration sector:Port Number: (read only); assigned by the system according to the mother portForce Port State: (read only); indicating the forced current state; possible values:
Dynamic : the port is managed by the Spanning Tree Protocol.Disabled : used to disable the port. In this state, all frames received will be discarded,further the Port does not participate in the operations of the STP or MAC learning pro-cesses.Blocked : the frames received by this port will be discarded, thus forcing it out of theactive topology, for preventing frame duplication arising through multiple paths.Forwarding : the port is participating in the frames relay, STP algorithm computationand MAC learning procedures, thus it is included in the active topology.
VLAN Management: VLAN functions are not yet available.
• R_STP Port Configuration sector:Port State: (read only); indicating the current port state regard the STP process; possiblevalues are as detailed in the sector above (item “ForcePortState”).Port Priority : 8–bit decimal value, but only the most significant 4 bits are settable. Thepossible options are 16 values, settable by means of the associated incrementing/decre-menting keys. (best priority = least numerical value).Port Role : (read only); the following values are available (see 802.1D):
root : the port offers the lowest cost path from this bridge to the root bridge. It is tobe part of the active topology connecting the Bridge to the Root Bridge.designated : the port is connecting a LAN, through the current Bridge, to the Root-Bridgealternate : Alternate Port if the Bridge is not the Designated Bridge for the attachedLAN. It offers an alternate path (after failure) in the direction of the Root Bridge to thatprovided by the Bridge Root Port.backup : Backup Port if the Bridge is the Designated Bridge for the attached LAN.Backup Port acts as a backup (after failure) for the path provided by a DesignatedPort in the direction of the leaves of the Spanning Tree. Backup Ports exist only wherethere are two or more connections from a given Bridge to a given LAN.disabled : the Port has no role within the operation of Spanning Tree.master : –––
Port Path Cost : contribution of this port to the path cost of paths towards the spanningtree root that include this port. 802.1D recommends that the default value of this parameterbe in inverse proportion to the speed of the attached LAN.Forward Transition : number of times this port has transitioned from Learning state to theForwarding state.Port Designed Cost : path cost of the Designated Port of the segment connected to thisport. This value is compared to the Root Path Cost field in received bridge PDUs.Port Designed Pt Number : number of the designated port, in decimal formatPort Designed Pt Priority : priority of the designated port, in decimal format
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
175
01
/3AL 89871 AAAA AA
218
218
Port Designed Root : unique Bridge Identifier of the Bridge recorded as the RootBridgein the Configuration BPDUs transmitted by the Designated Bridge for the segment to whichthe port is attached.Port Designed Bridge : Identifier of the bridge that this port considers to be the Desig-nated Bridge for this port’s segment.Port Admin Conn Type : connection type of the “administrative port”, to identify point–to–point link or shared media link. The following values are available (only for RSTP) :
autopointtopoint : the administrative port is automatically connectededgeport : the administrative port is a “target” port, situated at the edge of the STPnetwork, it can be connected to other adjacent networkspointtopoint : the administrative port is manually connectednopointtopoint : the administrative port has no connection
Port Oper Admin Conn Type : (only for RSTP); notification about current operational con-nection type of the administrative port.
After setting the desired parameters, click on the “Ok” key to confirm.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
Figure 108. Configure (R)STP Port
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
176
01
/3AL 89871 AAAA AA
218
218
4.9.31 Transmission: (R)STP Port: (R)STP Port Properties
This option is obtained, after selecting an (R)STP port, by means of the contextual pop–up menu, or byselecting in the menu–bar: “Transmission” –> “(R)STP Port Management” –> “(R)STP Port Properties”.An example of the displayed window is reported in Figure 109. page 176.
The function of this option is to show the transmission parameters set for the selected (R)STP port.All the reported information fields are read–only, and are the same as those explained ones for “Configure(R)STP Port”, para. 4.9.30 page 174.
Figure 109. (R)STP Port Properties
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
177
01
/3AL 89871 AAAA AA
218
218
4.10 Connection
The Connection application permits to manage all the parameters related to the Connection context.It can be entered by selecting, in the menu–bar: “Views” –> “Connection”, or by clicking on its relevanttab of the main view.
NOTE: All the dialogue windows described in this handbook are reported in “FullWindow” mode, the infor-mation fields reported in the “TabbedWindow” mode are the same (see para.4.6.2, page 118).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
178
01
/3AL 89871 AAAA AA
218
218
4.10.1 Ethernet Port: application table in the Connection context
An example of Application Table associated to the EthernetPort is illustrated in Figure 110. page 178.It is displayed in the area A2, after selecting the EthernetPort in the resource–tree.It reports, in tabular form, the main parameters related to the existing connections into the selected Port:“ETS InFlow”, “Status”, “ETS OutFlow”.NOTE1: the Connection view displays in the tool–bar a further fast–key, for quick recalling the EthernetPortoption “Create XC One Step”.NOTE2: in the Connection view the “Bridge” resource displayed into the TREE area is named “Switch”.
The properties of a connection of the table are displayed in the information area (A3), after selecting a rowof the table.A pop–up menu, related to the selected resource, can be activated, after selecting an item of the table andpressing the right button of the mouse.The listed parameters, the displayed properties, and the options of the pop–up menu are described in thesuccessive paragraphs.
”XC” FastKey
Figure 110. Ethernet Port: Connection application table
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
179
01
/3AL 89871 AAAA AA
218
218
4.10.2 Connection: Ethernet Port : Create Ets XC One Step
This option is obtained, after selecting an (ETS) Ethernet Port, by means of the contextual pop–up menu,or by selecting in the menu–bar: “Connection” –> “Ethernet Port Management” –> “Create Ets XC One Step”.NOTE1: this option is not available if the Port is ETB type.NOTE2: this option can also be quickly recalled by the further fast–key added into the tool bar.An example of the displayed window is reported in Figure 111. page 180.
The function of this option is to create a “One–Step” cross–connection, i.e. the first connection point of anETS EthernetPort in a fast way, starting from the parent ethernet port. It can be done for ports not yet con-taining cross–connected resources (InFlow or OutFlow). The Ingress and Egress connection points canalso be contained in the same port. If the InFlow/OutFlow resources are not yet existing, they will be auto-matically created by this option. This operation will not be possible if the selected ethernet port containsalready connected resources: in this case an error message will be displayed (see Figure 112. page 180).
To create a “OneStep” connection, fill fields and areas as follows:Port Eth. Ingress: name of the selected EthernetPort, fixed to “ingress” by the system.Port Eth. Egress: name of the “egress” EthernetPort
this item can be manually typed, or it can be browsed by means of the key,that recalls the “Search” dialogue described in para. 4.6.3 page 119.
Traffic Section: Traffic Descriptor : to indicate the name of the associated traffic descrip-tor (TD);
the key permits to choose and associate a traffic descriptor to the data flow, re-calling the dialogue described in para. 4.9.2 page 136.NOTE: this item will not be editable, if the InFlow resource has already been createdbefore.
Inflow Section: User Label : to indicate the user label (optional) of the inflow to be con-nected;
NOTE: this item will not be editable, if the InFlow resource has already been createdbefore.
Outflow Section: User Label : to indicate the user label (optional) of the outflow to be con-nected;
NOTE: this item will not be editable, if the OutFlow resource has already been createdbefore.
History area: reporting the operations executed by the program on doing the current con-nection.
After setting all the desired parameters, click on the “Apply” key to set up the cross connection.The window will be closed without doing any operation by clicking on “Cancel” key.Once the program executed the requested operations, click on “Finish” key to close the dialog window.The “Help” key gives helps about this function.
NOTE: the RemoteEthernetPorts are to be configured and connected also at the sdh side; see OMSN Op-erator’s Handbook for details about SDH configuration and connection.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
180
01
/3AL 89871 AAAA AA
218
218
Figure 111. Create Ets XC “OneStep”
Figure 112. Error message on “Create Ets XC OneStep”
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
181
01
/3AL 89871 AAAA AA
218
218
4.10.3 Connection: ETS InFlow : Create Ets XC
This option is obtained, after selecting an unconnected InFlow point, by means of the contextual pop–upmenu, or by selecting in the menu–bar: “Connection” –> “ETS InFlow Management” –> “Create Ets XC”.An example of the displayed window is reported in Figure 113. page 182.
The function of this option is to create a unidirectional cross–connection between an InFlow and an Out-Flow.Note: the multicast cross–connection is not yet operative.
To create an ETS connection, fill fields and areas as follows:ETS InFlow: indicating the point from which the connection starts (read only field: fixedby the system to the selected InFlow)ETS OutFlow: to choose the OutFlow point where the connection has to be closed; thesyntax of this name has to be in the form: “OutFlow#index”;
the key permits to choose an OutFlow point (that must be already existing),recalling the “Search” dialogue described in para. 4.6.3 page 119. The user canset, on the “OutFlow” tab of this dialogue, some search criteria (such as “XcSta-tus”, etc.), to facilitate the search, otherwise the search will be widened on allthe existing OutFlow points; the search is carried out by clicking on the “Search”key, after which the desired “leg” is set by selecting an item in the search resultand then clicking on the “Apply” key of the same search window.
Add Leg key: it adds the chosen item typed in the “OutFlow” field into the adjacent listDel Leg key: it deletes a “leg” selected in the adjacent listXC Topology: see belowStatus: possible pull–down options:
up : to set the connection in–service (set by the system)down : to set the connection out–of–service (not operative).
XC Topology sub–area:this area contains two figures, the first of which represents the current state ofthe connection, while the second one its future state, after these under way op-erations. The meaning of these figures are the following:
Not cross connected points Unidirectional, multicastcross connected points
Unidirectional, unicastcross connected points
(not operative)
NOTE–A: the RemoteEthernetPorts are to be configured and connected also at the sdh side; see OMSNOperator’s Handbook for details about SDH configuration and connection.See also NOTE1 and NOTE2 and NOTE3 at the end of this paragraph.
After setting all the desired parameters, click on the “Ok” key to set up the cross connection.The window will be closed without doing any operation by clicking on “Cancel” key.The “Help” key gives helps about this function.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
182
01
/3AL 89871 AAAA AA
218
218
Future XCtopology
Current XCtopology
Figure 113. Create Ets XC
NOTE1: CREATING A UNIDIRECTIONAL UNICAST (Point–To–Point) CROSS–CONNECTION
To create this type of connection, simply write (or choose, by means of the [...] key) the OutFlow point inthe relevant“OutFlow” field, then click on “Add Leg” and then on “Ok”.The involved resources will then be marked, on the TREE area, with an “x”, to indicate their cross–connec-tion status.Please note also that the Rate and the Traffic Descriptor associated to the two involved resources mustbe coherent, otherwise the XC will not be created (see para 4.9.2 page 136).
NOTE2: CREATING A UNIDIRECTIONAL MULTICAST (Point–To–MultiPoint) CROSS–CONNEC-TION (not operative)
To create this type of connection, write (or choose, by means of the [...] key) the OutFlow point in the rele-vant“OutFlow” field and click on “Add Leg”, then write (or choose) and add the successive legs in the sameway; at the end click on “Ok”.Note–a: the involved InFlow must have the parameter “FlowType” set to “MulticastOptionA” (see para4.9.12 page 160).Note–b: the involved OutFlows must belong to different ports (only one leg per Ethernet port)The involved resources will then be marked, on the TREE area, with an “x”, to indicate their cross–connec-tion status.Please note also that the Rate and the Traffic Descriptor associated to the involved resources must becoherent, otherwise the XC will not be created (see para 4.9.2 page 136).
NOTE3: CREATING A BIDIRECTIONAL UNICAST (Point–To–Point) CROSS–CONNECTION
To create this type of connection, simply create two Unidirectional connections (as described in NOTE1)in the opposite directions.Please note also that the Rate and the Traffic Descriptor associated to the involved resources must becoherent, otherwise the XC will not be created (see para 4.9.2 page 136).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
183
01
/3AL 89871 AAAA AA
218
218
4.10.4 Connection: ETS InFlow : Modify Ets XC
This option is obtained, after selecting a connected InFlow, by means of the contextual pop–up menu, orby selecting in the menu–bar: “Connection” –> “ETS InFlow Management” –> “Modify Ets XC”.
The function of this option is to modify the parameters (such as “Add Leg” or “Del Leg”) of the selectedconnected InFlow point.All the reported information fields and operations are the same as those explained ones for “Create EtsXC”, para. 4.10.3, page 181.
4.10.5 Connection: ETS InFlow : Ets XC Properties
This option is obtained, after selecting a connected InFlow, by means of the contextual pop–up menu, orby selecting in the menu–bar: “Connection” –> “ETS InFlow Management” –> “Ets XC Properties”.An example of the displayed window is reported in Figure 114. page 183.
The function of this option is to show the parameters set for the selected cross–connection.All the reported information fields are read–only, and the same as those explained ones for “Create EtsXC”, para. 4.10.3, page 181. Further this properties window reports also the location (i.e. the parent re-source) of the resources involved (InFlow, OutFlow), thus facilitating the individuation of their position.
Figure 114. Ets XC Properties
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
184
01
/3AL 89871 AAAA AA
218
218
4.10.6 Connection: ETS InFlow : Delete Ets XC
This option is obtained, after selecting a connected InFlow point, by means of the contextual pop–upmenu, or by selecting in the menu–bar: “Connection” –> “ETS InFlow Management” –> “Delete Ets XC”.An example of the displayed window is reported in Figure 115. page 184.
This option permits to delete a selected ETS cross connection.The XC will be deleted, in all its connected points, after clicking on the “Yes” key.
Figure 115. Delete Ets XC
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
185
01
/3AL 89871 AAAA AA
218
218
4.10.7 Connection: ETS OutFlow : Create Ets XC (not operative)
4.10.8 Connection: ETS OutFlow : Modify Ets XC (not operative)
4.10.9 Connection: ETS OutFlow : Ets XC Properties
This option is obtained, after selecting a connected OutFlow, by means of the contextual pop–up menu,or by selecting in the menu–bar: “Connection” –> “ETS OutFlow Management” –> “Ets XC Properties”.
The function of this option is to show the parameters set for the selected cross–connection.All the reported information fields are read–only, and the same as those explained ones for InFlow“Ets XCProperties”, para. 4.10.5, page 183.
4.10.10 Connection: ETS OutFlow : Delete Ets XC
This option is obtained, after selecting a connected OutFlow point, by means of the contextual pop–upmenu, or by selecting in the menu–bar: “Connection” –> “ETS OutFlow Management” –> “Delete Ets XC”.The displayed window is similar to that reported in Figure 115. page 184.
This option permits to delete the selected cross–connection.The XC will be deleted, in all its connected points, after clicking on the “Yes” key.
4.10.11 Connection: (R)STP Switch Management (not operative)
This option is not yet operative.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
186
01
/3AL 89871 AAAA AA
218
218
4.10.12 Ethernet SWITCH: Setting the FDB ageing time
An example of Application Table associated to the EthernetSWITCH is illustrated in Figure 116. page 186.It is displayed in the area A2, after selecting the EthernetSwitch in the resource–tree.
The panel displayed in the detail information area (A3), when the Switch resource has been selected inthe TREE area, permits to set the “Ageing Time” of the information collected into the FDB table of thisswitch. After this time, an item of the FDB (Filtering Data Base) table that reached this age is removed.Measurement unit in seconds. Range: 10 s to 1000000 s (recommended value 300s), granularity 1 s.To set this parameter, type a value in the “Ageing Time” field and then click on the “Set Ageing Time”key.The “Delete Row” and “Print” keys are not yet operative.
Figure 116. Ethernet SWITCH: Connection application table
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
187
01
/3AL 89871 AAAA AA
218
218
4.11 Performance
The Performance application permits to manage all the parameters related to the performance context.It can be entered by selecting, in the menu–bar: “Views” –> “Performance”, or by clicking on its relevanttab of the main view.
NOTE: All the dialogue windows described in this handbook are reported in “FullWindow” mode, the infor-mation fields reported in the “TabbedWindow” mode are the same (see para. 4.6.2, page 118).
4.11.1 Performance: Ethernet Port : Configure Eth. Aggr.
This option is obtained, after selecting an active Ethernet Port (local or remote), by means of the contextualpop–up menu, or by selecting in the menu–bar: “Performance” –> “Ethernet Port Management” –> “Configure Eth Aggr”.An example of the displayed dialog window is reported in Figure 117. page 187.
The function of this option is to manage the Performance Monitoring (PM) parameters of the selectedEthernetPort (local or remote), activating the data collection.
To configure the PM function for an Ethernet Port, fill fields and areas as follows:• Incoming sector (these parameters are relative to the monitoring of the port incoming side):
Eth Inc Name: name of the selected EthernetPort incoming side (read only field)Data Collection: mark this box, in order to start the monitoring.Else, clear this box, in order to stop the monitoring, in this way removing also the PM point.
• Outgoing sector (these parameters are relative to the monitoring of the port outgoing side):Eth Out Name: name of the selected EthernetPort outgoing side (read only field)Data Collection: mark this box, in order to start the monitoring.Else, clear this box, in order to stop the monitoring, in this way removing also the PM point.
Figure 117. Ethernet Port Configure Monitoring (example)
Click on “Ok” key to confirm the chosen values. The “Cancel” key aborts the dialog. The “Help” key givesdetailed information about this window.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
188
01
/3AL 89871 AAAA AA
218
218
4.11.2 Performance: Ethernet Port : Eth Aggr. Properties
This option is obtained, after selecting a monitored Ethernet Port, by means of the contextual pop–upmenu, or by selecting in the menu–bar: “Performance” –> “Ethernet Port Management” –> “Eth Aggr Properties”.An example of the displayed dialog window is reported in Figure 118. page 188.
The function of this option is to show the Performance Monitoring (PM) parameters and the currently col-lected values for the selected Ethernet–Port. All the reported information fields are read–only.
It contains the following information fields:• Incoming/Outgoing – Configuration sectors:
these parameters are the current EthPort monitoring configuration parameters; theirmeanings are described in para. 4.11.1 page 187.
• Incoming – Information sector:these fields indicate the current PM collected valuesTRCF: number of Total Received Correct ethernet FramesTRCO: number of Total Received Correct ethernet OctetsStart Time: indicating the time when the performance monitoring was started
• Outgoing – Information sector:these fields indicate the current PM collected valuesTTF: number of Total Transmitted ethernet FramesTTO: number of Total Transmitted ethernet OctetsStart Time: indicating the time when the performance monitoring was started
The “Reset” key causes the resetting of the reported values (not operative).The “Refresh” key causes the updating of the reported values.The “Close” key closes the window. The “Print” key causes the printing of the reported values. The “Help”key gives detailed information about this window.
Figure 118. Ethernet Port Monitoring Properties (example)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
189
01
/3AL 89871 AAAA AA
218
218
PM Data Results (HISTORY and Maintenance)The history and maintenance monitoring data results are reported in the main view, in the Application–Table–Area (A2), after having selected the EthernetPort in the tree–area (see example reported in para.4.11.7 page 196).
The HISTORY and Maintenance PM data for the EthPort, reported into the application table area (A2),are detailed in para. 4.11.7.1 page 198.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
190
01
/3AL 89871 AAAA AA
218
218
4.11.3 Performance: ETS InFlow : Configure InFlow (not operative)
This option is obtained, after selecting a connected InFlow, by means of the contextual pop–up menu, orby selecting in the menu–bar: “Performance” –> “ETS InFlow Management” –> “Configure ETS InFlow”.NOTE: the selected InFlow has to be already cross–connected, otherwise the PM menu is not active.An example of the displayed dialog window is reported in Figure 119. page 190.
The function of this option is to manage the Performance Monitoring (PM) parameters of the selected In-Flow resource: activating the data collection, etc.
To configure the PM function for an InFlow, fill fields and areas as follows:• InFlow Cd – Configuration sector :
InFlow Name: indicating the name of the selected ETS InFlow (read only field)Data Collection: mark this box, in order to start the monitoring.Else, clear this box, in order to stop the monitoring, in this way removing also the PM point.
Figure 119. InFlow Configure Monitoring (example)
Click on “Ok” key to confirm the chosen values. The “Cancel” key aborts the dialog. The “Help” key givesdetailed information about this window.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
191
01
/3AL 89871 AAAA AA
218
218
4.11.4 Performance: ETS InFlow: InFlow Properties (not operative)
This option is obtained, after selecting a monitored InFlow, by means of the contextual pop–up menu, orby selecting in the menu–bar: “Performance” –> “ETS InFlow Management” –> “ETS InFlow Properties”.NOTE: the selected InFlow has to be already cross–connected, and with PM configured, otherwise thisPM menu is not active.An example of the displayed dialog window is reported in Figure 120. page 191.
The function of this option is to show the Performance Monitoring (PM) parameters and the currently col-lected values for the selected InFlow. All the reported information fields are read–only.
It contains the following information fields:• InFlow Cd – Configuration sector:
these parameters are relative to the current monitoring configuration parameters; theirmeanings are described in para. 4.11.3 page 190.
• InFlow Cd – Information sector:these fields indicate the current PM collected values (Cd= CurrentData)TRCFg: number of Total Received Correct ethernet Frames, green colouredTRCOg: number of Total Received Correct ethernet Octets, green colouredStart Time: indicating the time when the performance monitoring was started
The “Reset” key causes the resetting of the reported values (not operative).The “Refresh” key causes the updating of the reported values.The “Close” key closes the window. The “Print” key causes the printing of the reported values. The “Help”key gives detailed information about this window.
Figure 120. InFlow Monitoring Properties (example)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
192
01
/3AL 89871 AAAA AA
218
218
PM Data Results (HISTORY and Maintenance)The history and maintenance monitoring data results are reported in the main view, in the Application–Table–Area (A2), after having selected the ETS InFlow in the tree–area (see example reported in para.4.11.7 page 196).
The HISTORY and Maintenance PM data for the ETS InFlow, reported into the application table area (A2),are detailed in para. 4.11.7.2 page 199.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
193
01
/3AL 89871 AAAA AA
218
218
4.11.5 Performance: ETS OutFlow: Configure OutFlow (not operative)
This option is obtained, after selecting a connected OutFlow, by means of the contextual pop–up menu,or by selecting in the menu–bar: “Performance” –> “ETS OutFlow Management” –> “Configure ETS OutFlow”. NOTE: the selected OutFlow has to be already cross–connected, otherwise the PM menu is not active.An example of the displayed dialog window is reported in Figure 121. page 193.
The function of this option is to manage the Performance Monitoring (PM) parameters of the selected Out-Flow resource: activating the data collection, etc.
To configure the PM function for an OutFlow, fill fields and areas as follows:• OutFlow Cd – Configuration sector :
OutFlow Name: indicating the name of the selected ETS OutFlow (read only field)Data Collection: mark this box, in order to start the monitoringElse, clear this box, in order to stop the monitoring, in this way removing also the PM point.
Figure 121. OutFlow Configure Monitoring (example)
Click on “Ok” key to confirm the chosen values. The “Cancel” key aborts the dialog. The “Help” key givesdetailed information about this window.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
194
01
/3AL 89871 AAAA AA
218
218
4.11.6 Performance: ETS OutFlow: OutFlow Properties (not operative)
This option is obtained, after selecting a monitored OutFlow, by means of the contextual pop–up menu,or by selecting in the menu–bar: “Performance” –> “ETS OutFlow Management” –> “ETS OutFlow Properties”.NOTE: the selected OutFlow has to be already cross–connected, and with a configured PM, otherwisethis PM menu is not active.An example of the displayed dialog window is reported in Figure 122. page 194.
The function of this option is to show the Performance Monitoring (PM) parameters and the currently col-lected values for the selected OutFlow. All the reported information fields are read–only.
It contains the following information fields:• OutFlow Cd – Configuration sector:
these parameters are relative to the current monitoring configuration parameters; theirmeanings are described in para. 4.11.5 page 193.
• InFlow Cd – Information sector:these fields indicate the current PM collected values (Cd= CurrentData)TTFg: number of Total Transmitted ethernet Frames, green colouredTTOg:number of Total Transmitted ethernet Octets, green colouredStart Time: indicating the time when the performance monitoring was started
The “Reset” key causes the resetting of the reported values (not operative).The “Refresh” key causes the updating of the reported values.The “Close” key closes the window. The “Print” key causes the printing of the reported values. The “Help”key gives detailed information about this window.
Figure 122. OutFlow Monitoring Properties (example)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
195
01
/3AL 89871 AAAA AA
218
218
PM Data Results (HISTORY and Maintenance)The history and maintenance monitoring data results are reported in the main view, in the Application–Table–Area (A2), after having selected the ETS OutFlow in the tree–area (see example reported in para.4.11.7 page 196).
The HISTORY and Maintenance PM data for the ETS OutFlow, reported into the application table area(A2), are detailed in para. 4.11.7.3 page 200.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
196
01
/3AL 89871 AAAA AA
218
218
4.11.7 PM Data Results (HISTORY and MAINTENANCE)
The history and maintenance monitoring data results are reported in the main view, in the Application–Table–Area (A2), after having selected the relevant resource in the tree–area; as examples seeFigure 123. page 197.Note: in the “Performance” application, one further fast key is displayed in the tool–bar: “PM:Refresh”,in order to refresh the displayed values. When in “Graphical Format” (not operative), three further fastbuttons are displayed in the tool–bar: “GraphicalPM: save an image of the graph”, “GraphicalPM: switchbetween decimal and exponential format” and “GraphicalPM: switch between Histogram and Bar repre-sentation”.
The application table area (A2) contains different types of folders:HD 1h : it means History Data for 1 hour period, reported values are the difference between currentand previous monitoring period; when the mouse is passed on a value, it pops–up the correspondingabsolute value (accumulated since the starting time). This table reports the measured parametersin the last 4 intervals.HD 24h : it means History Data for 24 hour period, reported values are absolute values (accumulatedsince the starting time). This table reports the measured parameters only in the last interval.Maintenance : it reports some monitoring data useful for maintenance operations, such as (exam-ples): total afferent correct frames, errored frames (TRSEF), discarded frames (TDF), frames color-ation, etc. Reported values are absolute values. Different monitoring parameters are reported for dif-ferent resources (see the following sub–paragraphs).
Note: the Maintenance folder presents also, in the “Resource Information Area” (A3), adialog pane in which the user can carry out a sampling in real time of the PM data (polling),by choosing the “Polling Time” and the number of samples (“N. Retries” ), and pressingthen on the “Start Polling” key. After finishing the collection of the requested number ofsamples, the polling is automatically stopped, if not yet stopped by the user. Reported val-ues are the difference between current and previous monitoring period; when the mouseis passed on a value, it pops–up the corresponding absolute value.
The History Data can be displayed either in tabular and in graphical format.The choice between tabular and graphical format (not operative) is done by means of the “Configura-tion”–> “Options”, “Program” folder, at the “Tabular/GraphicalArea” item, as described in para. 4.6.1, page116.
When in “Graphical Format” (not operative), the choice between decimal and exponential represen-tation or between histogram and bar representation is done by means of the relevant “fast PM keys”presented in the tool–bar.An image of the graph (in histogram or bar representation), not operative, can be captured by means ofthe relevant “GraphicalPM: save an image of the graph” fast PM key presented in the tool–bar.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
197
01
/3AL 89871 AAAA AA
218
218
TABULAR format (example)The view reports (see example in Figure 123. ), in tabular form, the same PM parameters that are de-scribed in para. 4.11.7.1 page 198 for the “EthPort” , or para. 4.11.7.2 page 199 for the “InFlow”, or para.4.11.7.3 page 200 for the “OutFlow”; (this example is referred to the “EthPort ”).
PM fast key
A2
A3
Figure 123. PM data results in tabular mode (example)
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
198
01
/3AL 89871 AAAA AA
218
218
4.11.7.1 Ethernet Port PM data tables (History and Maintenance)
The application table area (A2) contains, for EthernetPort resources, the following PM data folders:HD1h Inc., HD1h Out, HD24h Inc., HD24h Out, Maintenance Inc., Maintenance Out; the Localports contain also a folder relevant to the physical interface: Interface Maintenance.HD 1h Inc. /(Out): it reports the results of the HISTORY collected monitoring data relevant to the 1hour period, for the Incoming /(Outgoing) side of the portHD 24h Inc. /(Out) : it reports the results of the HISTORY collected monitoring data relevant to the24 hours period, for the Incoming /(Outgoing) side of the portMaintenance Inc. /(Out) : it reports the results of the Maintenance monitoring data, for the Incomingside /(Outgoing) of the portInterface Maintenance: (only for Local ports), it reports the results of the Maintenance monitoringdata relevant to the local physical interface.• HD1h Inc. folder:
TRCF: number of Total Received Correct FramesTRCO: number of Total Received Correct ethernet OctetsStart Time: indicating the time when the performance monitoring was startedSuspect Interval Flag: if this value is “true” it means the measurement data is unreliable,if “false” it means the data is reliable.
• HD1h Out. folder:TTF: number of Total Transmitted ethernet FramesTTO: number of Total Transmitted ethernet OctetsStart Time: as above explainedSuspect Interval Flag: as above explained.
• HD24h Inc. folder:it contains the same PM parameters as the above explained “HD1h Inc.”, but for a 24 hinterval.
• HD24h Out. folder:it contains the same PM parameters as the above explained “HD1h Out.”, but for a 24 hinterval.
• Maintenance Inc. folder:TRCF: as above explainedTRCO: as above explainedTRSEF: number of Total Received Service Errored FramesRetrieving Time: time of the last PM data refreshThe Maintenance folder presents also, in the “Resource Information Area” (A3), a dialogpane in which the user can carry out a sampling in real time of the PM data (polling); formore details see para. 4.11.7 page 196.
• Maintenance Out. folder:TTF: as above explainedTTO: as above explainedRetrieving Time: time of the last PM data refreshdialog pane for PM data sampling (polling): as above explained
• Interface Maintenance folder (only in LocalPorts):Symbol Error: number of invalid data symbols (due to line code error) received by the portwhen a valid carrier signal is present; (for 1000Mb/s i/f it is incremented only once perframe, if one or more errors occurred); it is not incremented under a collision eventMedia Available Exits: number of times the physical medium is not present (LOS event)Jabber State Enters: number of times the physical interface enters in jabber state; i.e.when Ethernet frames are longer than the MTU; (only for 10Mb/s i/f)False Carrier: number of times an invalid carrier signal is received, during IDLE state;(only for 100 or 1000Mb/s interfaces)Retrieving Time: time of the last PM data refreshDialog pane for PM data sampling (polling): as above explained
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
199
01
/3AL 89871 AAAA AA
218
218
4.11.7.2 ETS InFlow PM data tables – History and Maintenance (not operative)
The application table area (A2) contains, for InFlow resources, the following PM data folders:
HD 1h : it reports the results of the HISTORY collected monitoring data relevant to the 1 hour period.HD 24h : it reports the results of the HISTORY collected monitoring data relevant to the 24 hoursperiod.QoS Maintenance : it reports the results of the Maintenance monitoring data, for the QoS monitoring,with the indications about colorations of the afferent traffic and of the discarded frames.
• HD1h folder:TRCFg: number of Total Received Correct Frames, green colouredTRCOg: number of Total Received Correct ethernet Octets, green colouredStart Time: indicating the time when the performance monitoring was startedSuspect Interval Flag: if this value is “true” it means the measurement data is unreliable,if “false” it means the data is reliable.
• HD24h folder:it contains the same PM parameters as the above explained “HD1h”, but for a 24 h interval.
• QoS Maintenance folder:TRCOg: as above explainedTRCFg: as above explainedTRCOy: number of Total Received Correct ethernet Octets, yellow colouredTRCFy: number of Total Received Correct Frames, yellow colouredTRCOr: number of Total Received Correct ethernet Octets, red colouredTRCFr: number of Total Received Correct Frames, red colouredRetrieving Time: time of the last PM data refreshThe Maintenance folder presents also, in the “Resource Information Area” (A3), a dialogpane in which the user can carry out a sampling in real time of the PM data (polling); formore details see para. 4.11.7 page 196.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
200
01
/3AL 89871 AAAA AA
218
218
4.11.7.3 ETS OutFlow PM data tables – History and Maintenance (not operative)
The application table area (A2) contains, for OutFlow resources, the following PM data folders:
HD 1h : it reports the results of the HISTORY collected monitoring data relevant to the 1 hour period.HD 24h : it reports the results of the HISTORY collected monitoring data relevant to the 24 hoursperiod.QoS Maintenance : it reports the results of the Maintenance monitoring data, for the QoS monitoring,with the indications about colorations of the afferent traffic and of the discarded frames.
• HD1h folder:TTFg: number of Total Transmitted ethernet Frames, green colouredTTOg: number of Total Transmitted ethernet Octets, green colouredStart Time: indicating the time when the performance monitoring was startedSuspect Interval Flag: if this value is “true” it means the measurement data is unreliable,if “false” it means the data is reliable.
• HD24h folder:it contains the same PM parameters as the above explained “HD1h”, but for a 24 h interval.
• QoS Maintenance folder:TTOg: as above explainedTTFg: as above explainedTDFg: number of Total Discarded ethernet Frames due to congestion, green colouredTTOy: number of Total Transmitted ethernet Octets, yellow colouredTTFy: number of Total Transmitted ethernet Frames, yellow colouredTDFy: number of Total Discarded ethernet Frames due to congestion, yellow colouredRetrieving Time: time of the last PM data refreshThe Maintenance folder presents also, in the “Resource Information Area” (A3), a dialogpane in which the user can carry out a sampling in real time of the PM data (polling); formore details see para. 4.11.7 page 196.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
201
01
/3AL 89871 AAAA AA
218
218
MAINTENANCE
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
202
01
/3AL 89871 AAAA AA
218
218
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
203
01
/3AL 89871 AAAA AA
218
218
5 MAINTENANCE
5.1 Introduction
The Maintenance general metodology is reported on the equipment–specific Operator Handbooks;please refer to them for: equipment troubleshooting and relevant interventions.
Only the maintenance issues relevant to hardware and software relative to ISA–ES board are hereinafterreported.
5.2 General trouble–shooting flow–chart for ISA–ES boards
In case of faults/defects/failures please follow the general troubleshooting procedure illustrated by thefollowing flow–chart.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
204
01
/3AL 89871 AAAA AA
218
218
START
AN ALARMIS PRESENT
OBSERVE THE LEDS ON THE FRONT COVER
IS THE
ISA–ES BOARD
BICOLOR LED RED?
NO
THROUGH PUSH–BUTTON
ON ISA–ES BOARD
DOESTHE ALARM
CONDITIONPERSIST ?
NO TRANSITORY
FAILURE
IS FAULTY, REPLACE IT ACCORDING
TO THE DESCRIBED PROCEDURE
CONNECT THE PC TO THEEQUIPMENT AND, ACCORDING TOTHE TYPE OF DETECTED ALARM,
PROCEED AS STATED IN
YES
YES
(see para 5.5 on page 218)
OF THE ISA–ES BOARD
PARA 5.4 ON PA GE 206
RESTART THE UNIT
THE ISA–ES BOARD
(see para 5.3 on page 205)
END END
Figure 124. General Flow–chart for ISA–ES board troubleshooting
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
205
01
/3AL 89871 AAAA AA
218
218
5.3 Alarms, states and commands on ISA–ES board front cover
The state of the ISA–ES unit is indicated by a bicolor LED, placed in the lower side of the ISA–ES boardfront cover:
• when red, it indicates internal failure• when green, it indicates in service unit
In order to give some commands, there is one RESTART push–button on the front of the ISA–ES unit:• restart push–button, to restart the unit’s software•
The positions of the LEDs and command push–buttons on the ISA–ES front coverplate are shown on theequipment–specific Technical Handbook.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
206
01
/3AL 89871 AAAA AA
218
218
5.4 Troubleshooting by means of the ES Craft Terminal
The information about the alarms will be mainly obtained by means of the craft terminal through theAlarms Surveillance (AS) data, the alarms/status indications presented in the main view, and in the“properties windows”, depending on the level of the resource under observation.
The troubleshoot procedure by means of the the ES–CT consists of the following steps:
a ) observing the active alarms on the Severity Alarms Synthesis, Domain Alarms Synthesis andManagement States Control Panel, see Figure 125. page 207: they resume all the active alarmson the ES–Node. Table 14. , Table 15. and Table 16. on page 209 and up describe the meaning ofthese alarms/statuses and the relevant maintenance actions. See the following para.5.4.1 and 5.4.2.
b ) observing the alarms reported in the tree–area A1; this structure immediately helps to localize thealarmed resource, since the alarm condition is directly indicated near every resource symbol. Themeaning of these alarms is described in para 5.4.3, page 211.
c ) the properties view (in the “Transmission” context) of each selected resource contains the “Alarms”sector that gives information about the presence of alarms in the resource under observation. Seeexample in para 5.4.4, page 212. The information about alarms can also be observed in theresource–information–area A3 (reporting the same information as the property–view).
d ) in case of alarm presence, open the Alarms Surveillance application to troubleshoot. Thisapplication gives the details of the detected alarms and helps for their localization. See para 5.4.6on page 214.
e ) the synthesys of some alarms relevant to the ISA–ES boards is also reported on the views presentedin SDH–CT (RUM, RUTM, RUP, ICP, VM, etc...): the details about these alarms and furthermaintenance interventions are reported in the equipment–specific Operator Handbooks.
In case of unit replacement, follow the indications reported in para. 5.5 on page 218.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
207
01
/3AL 89871 AAAA AA
218
218
5.4.1 Alarms/states organization in the main view
title
rowmessage
menu bar
A1
tool bar
Severity AlarmsSynthesis
Domain AlarmsSynthesis
Manag. StatesControl Panel
A2
A3
curr.Appl.Appl. tabs
Resource AlarmsIndications
Figure 125. Alarms/statuses organization in the main–view
The critical (CRI) or major (MAJ) alarms indicate severe alarms that could have impact on thecurrent traffic (interruption or degrade), thus requiring a rapid intervention to restore theregular working condition of the equipment.
A message, activated by the mouse facility when passing over an alarm or status icon, provides the alarmor status complete denomination: a text appears in the “message–row” at the bottom left corner of the view.
The area A3 reports alarms indications too, related to the resource that has been selected in the A2 area.
The tree–structure A1 immediately helps to localize the alarmed resource, since the alarm condition isdirectly indicated near every resource symbol.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
208
01
/3AL 89871 AAAA AA
218
218
5.4.2 Alarms synthesis indications
Referring to Figure 125. page 207, the icons CRI, MAJ, MIN, WNG, IND are part of the Severity AlarmsSynthesis area, they are described in Table 14. on page 209; they report the actual number of alarmsgrouped for different severities, and the relevant color as assigned by the ASAP.If not alarmed, every alarm icon is green and rectangular shaped.If alarmed, every alarm icon is ASAP–coloured and circular shaped.
The icon TRNS is part of the Domain Alarms Synthesis area, described inTable 15. on page 209. itreports the actual number of alarms pertaining to the transmission domain. Its color corresponds to thehighest severity among the set of the active alarms for this domain, according to the rules in Table 12.
The alarms SUP, LAC (”key”), COM, OS, MGR are part of the Management States Control Panel,presented in Table 16. on page 209.
All these indications (except for SUP, LAC, COM, OS, MGR) are the summaries of particular types ofalarms detected by the equipment, further they report the total counting of alarms per group; the specificcause of alarm is to be found as indicated in this and in the following paragraphs.
NOTE: the customization of the ASAP’s (Alarms Severity Assignment Profile) can change the colors andthe assignment of each alarm to the various groups of alarms; the ASAP configuration is reported in para.4.7.1, page 123.
Table 12. reports the association between the colors of the Alarms and their Severity.Table 13. reports the colors of the Management States Control Panel when not in “normal” condition.
Example of alarmed representation: (coloured and with internal circular shape)
Example of non–alarmed representation: (green and with internal rectangular shape)
Table 12. Alarms colors and Severity association
Alarm Color Severity
RED CRITICAL (CRI)
ORANGE MAJOR (MAJ)
YELLOW MINOR (MIN)
PALE BLUE WARNING (WNG)
WHITE INDETERMINATE (IND)
GREEN NO ALARM
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
209
01
/3AL 89871 AAAA AA
218
218
Table 13. Colors of the Management States when in “ab–normal” condition (alarmed)
State State Color
SUP: not supervised BROWN
“key” (LOCAL ACCESS STATE) : denied CYAN
COM: NE unreachable RED
OS: NE managed by the OS CYAN
MGR: managed by RM CYAN
Table 14. Severity Alarms Synthesis indications
Mnemonic Alarm/Status Description Maintenance
CRI Critical alarms
Synthesis of alarms that need immediate trouble-shooting (typical: NE isolation). NB1.
Open the AS application: see detailed indications inpara. 5.4.6 on page 214.
MAJ Major (Urgent) alarmsSynthesis of alarms that need immediate trouble-shooting. NB1. Open the AS application: see detailedMAJ Major (Urgent) alarms shooting. NB1. Open the AS application: see detailedindications in para. 5.4.6 on page 214.
MIN Minor (Not urgent) alarms
Synthesis of alarms for which a delayed troubleshoot-ing can be defined. NB1.
Open the AS application: see detailed indications inpara. 5.4.6 on page 214.
WNG Warning alarms
Synthesis of alarms due to failure of other NE in thenetwork. NB1.
Open the AS application: see detailed indications inpara. 5.4.6 on page 214.
IND Indeterminate alarms
Synthesis of alarms not associated to the previousseverities. Not operative.
Open the AS application: see detailed indications inpara. 5.4.6 on page 214.
Table 15. Domain Alarm Synthesis indication
Mnemonic Alarm/Status Description Maintenance
TRNS Transmission alarmsSynthesis of alarms of the Transmission domain.
(Indicated as “Communications” Events in the AS ap-plication, see para. 5.4.6 on page 214)
Table 16. Management States Control Panel.
Mnemonic Alarm/Status Description Maintenance
SUP Supervision stateIndicates whether or not the NE is under supervision.
Used in the OS.
Local Access stateIndicates whether the Craft Terminal has the OS per-mission to manage the NE (granted: rectangularshape) or not (denied: circular shape).
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
210
01
/3AL 89871 AAAA AA
218
218
Mnemonic MaintenanceAlarm/Status Description
COM Operative System IsolationIdentifies the operational state of the connection be-tween NE and Craft Terminal: “disabled” (NE: Un-reachable), or“Enabled” (NE: Reachable).
OS NE managed by the OS The NE is being managed by the OS.
MGR Upper Management assignment Indicates that the NE is supervised by an Upper Man-ager (BM or RM, etc.).
NB1: Alarms Severity Assignment Profile (ASAP) can modify the assignment of each alarm root tothe various synthesis.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
211
01
/3AL 89871 AAAA AA
218
218
5.4.3 Alarms indications in the Resources TREE area (A1)
alarmed resource
not alarmed resource
Figure 126. TREE area example
ALARMS VISUALIZATION :
Alarms summary : (at level of ISA–ES node)
The Alarms summary is visualized only at the ES node level, reporting the colors of the maximum alarmseverities, detected in the current atm switch (inner circle) and in the contained resources (outer rings).If the inner circle is not colored, it means that the alarms are in the contained resources and not in theparent one.
Alarms synthesis (only at the ports level):
The Alarms synthesis is visualized at all the ports, reporting all the alarm severity colors (in form ofconcentric rings), detected in the current resource (inner circle) and in the contained resources (outerrings). If the inner circle is not colored, it means that the alarms are in the contained resources and notin the parent one.
No alarm :
The colors of the alarms indicate the associated severity as specified in Table 12. page 208.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
212
01
/3AL 89871 AAAA AA
218
218
5.4.4 Alarms indications in the resource properties
The properties view of each selected resource contains the “Alarms” sector that gives information aboutthe presence of alarms in the resource under observation.
Figure 127. page 212 is an example of property view.It is obtained by means of the menu path: Transmission –> Ethernet Port Management –> Ethernet PortProperties.The alarms properties are found also for the other ISA–ES resources where the alarms are foreseen.
The conditions of alarms relevant to a selected resource (selected in the list of the A2 area) can also beobserved in the resource–information–area A3 (reporting the same information as the property–view); seeexample in Figure 128. page 213.
The non–alarmed condition of an alarm is represented by a green color icon and a “–” sign in the box.The alarmed condition is represented by a color and an “X” sign in the box (the color of the relevant alarmis assigned by the ASAP: see Table 12. page 208):
Not alarmed condition :
Alarmed condition :
The alarms that can be found in the property–view are listed and described in Table 18. page 217, wherethe relevant maintenance actions are reported too.
Alarms indications
Figure 127. Example of EthernetPort Properties alarms
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
213
01
/3AL 89871 AAAA AA
218
218
Resource AlarmsIndications
Figure 128. Example of alarms reported in the “resource information area A3”
5.4.5 Alarms relevant to ES–Boards observable on SDH–CT
The synthesys of some other alarms relevant to the ISA–ES boards are reported on the views presentedin SDH–CT: RUM (unit–missing), RUTM (unit–mismatch), RUP (unit–problems), ICP(communications–problems), VM (version–mismatch), etc. The details about these alarms and furthermaintenance interventions are reported in the equipment–specific OMSN Operator Handbook.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
214
01
/3AL 89871 AAAA AA
218
218
5.4.6 Alarms Surveillance (AS)
In case of presence of alarms, observed as seen in the previous paragraphs, open the AlarmsSurveillance (AS) application to troubleshoot. For this purpose select, in the menu–bar, the Diagnosispull down menu and then the Alarms cascading menu; the following options are offered:
– ISA Alarms: all the ES–node alarms are listed in the AlarmsSurveillance report that is activated.
– Object Alarms: only the alarms relevant to the selected object are listedin the Alarms Surveillance report.
– Transmission Alarms: only the alarms relevant to the Transmission context are listedin the Alarms Surveillance report.
Selecting one of these latter options, the Alarms Surveillance (AS) report is displayed as for the examplein the following figures (this example is relative to “ISA Alarms” option).
This application shows a synthesis of the ES–NE alarms (“Counter Summary” window, see Figure 129. )with the sum of all alarms, and then a detailed list of alarms belonging to a group selected in the previouswindow (see Alarms Sublist in Figure 130. ).
Figure 129. AlarmsSurveill.–“Counter Summary” window(“ISA Alarms” example)
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
215
01
/3AL 89871 AAAA AA
218
218
Figure 130. AlarmsSurveill.–“Alarm Sublist” window (“ISA Alarms” example)
Detailed information for each alarm is supplied in the “Alarm Sublist” window. For example: the resourcewhere the alarm is detected, its status, type, probable cause of the relevant alarm, etc.The colors of the alarms indicate the associated severity as specified in Table 12. page 208.
The listing of all the Alarms or the filtering of a class of them is also possible. The filtering is achieved bydouble clicking on a row of alarm, in the “Counter Summary” little window (Figure 129. ); e.g. the alarmsrelative to the ISA–ES side are displayed, in the “Alarm Sublist” window, by double clicking on the last rowof the “Counter Summary” window.
The alarms scenario is indicated by the colors of the alarms and by the information displayed in the table.For instance, referring to Figure 130. , if an alarm is still active, the whole row has the same color of itsrelevant “Perceived Severity”; else, if it has been cleared, the color of the row is green (except the“Perceived Severity”). The same information is reported in the “Clearing Status” column.
A more detailed description of the “Alarms Surveillance” (AS) application is given in the “AS Operator’sHandbook”.
The main information obtained by means of the AS application is shortly described in the followingTable 17. on page 216 and Table 18. on page 217.The maintenance action must take into account the equipment or board or resource where the alarm isdetected.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
216
01
/3AL 89871 AAAA AA
218
218
Table 17. Alarms Surveillance information general description
TITLE DESCRIPTION
– Perceived SeverityThe severity assigned to the alarm is indicated, with the relevant color,i.e.: MAJOR, MINOR, WARNING....
– Event date and time Indicates year, month, day and hour of the alarm.
– Friendly NameIdentifies the rack, subrack, board, port, and TP in which the alarm is detected,e.g.: / r01sr1sl01/#port01–E1S
– Event TypeIndicates the family type of the alarm as subdivided in the ASAP list, i.e.: COM-MUNICATIONS, etc.
– Probable CauseThe fault/problem is indicated, i.e.: loss of signal, transmitter degraded, re-placeable unit missing,resource isolation, ...
– Reservation StatusIndicates if the alarm is reserved (RSV) or not (NRSV) according to securitymanagement.
– Clearing statusIndicates if the alarm condition is terminated (CLR) or is still active (NCLR).If cleared it has a green background,
– Acknowledge statusIndicates if the alarm has been acknowledged (ACK), with the “Attend” buttonon the COMPACT ADM unit, or not ( NACK).
– Correlated notification flag
Not used
– Repetition counter Not used
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
217
01
/3AL 89871 AAAA AA
218
218
Table 18. “Probable Cause” of alarms and relevant maintenance actions
PROBABLE CAUSE
NAME AND/OR ACRONYMOF DISPLAYED ALARM
MAINTENANCE
LOS (Loss Of Signal)Problems on receive path or on remote transmitter.
Check the ISA–ES continuity connections on RX path and remotetransmitter.
LOF (Loss Of Frame)Problems on receive path or on remote transmitter.
Check the RX path (ports, cross–connections, etc.) and remotetransmitter.
TSF (Trail Signal Fail)Problems on receive line.
Check the integrity of RX line and relevant connessions.
GTM (GFP Type Mismarchl)Problems on remote i/f. The GFP frame is not congruent with theexpected one.
Check the remote Ethernet port configuration.
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
218
01
/3AL 89871 AAAA AA
218
218
5.5 ISA–ES Units replacement
NOTE: this procedure is applicable either for ES1 or ES4 board.
In case that the ISA–ES unit is faulty, replace it by doing the following operations:
a ) remove the faulty unit from the equipment
b ) insert a new unit into the same slot of the equipment.
The start–up of the new unit can take some minutes.
5.6 SOFTWARE UPGRADING/DOWNGRADING
The migration of the ISA–ES software from a version to another can be requested in maintenance casesas:
a ) software product evolution
b ) roll back of the software product to older or previous versions.
In these cases, a sofware package installation (see para 3.6, page 86 ) and a download operation (seepara 3.8, page 93) are necessary.
NOTE: in case of migration from a release to another one, the presence of the previous release ofSDH–USM software package (see 1320CT Operator Handbook) is necessary, in order to download thenew software release, otherwise the equipment–SW and the CT–SW are not aligned and the equipmentcannot be supervised anymore. Hence the operator is recommended to keep the previous release ofthe SDH–USM, until the actual SW–package will be downloaded into the equipment.
NOTE2: in case of migration to a new release containing a new “ADD–ON” (ServiceSpecific packet suchas the ES–swp), from an old release containing another service packet (for instance an ATM–swp), thedownload of the software into the NE must be done in two steps:
first step downloading the new SDH packet associated with the known service packet (e.g.:enhanced OMSN with ATM, see also para. 3.6, page 86)second step downloading the new SDH packet associated with the new service packet (e.g.:enhanced OMSN with ES).
NOTE3: in case of UPGRADE from an OLD release to a NEW release that is not consecutive, thedownload of the software into the NE must be done in two steps:
first step: the release of the software into the NE and the release of the CT must be aligned (i.e., ifthe CT is in current release, it must be downgraded, thus installing the CT aligned to the NE softwareresident into the NE); in these conditions the new SW_package can be downloaded and activated,using the old CT.second step: instal the new CT release and access the NE.If the DataService board (ES) was not present in the old release, then download the new SDH packetassociated with the new service packet (e.g.: enhanced OMSN with ES).
END OF DOCUMENT
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
Y 1
01
RELEASED
/3AL 89871 AAAA TQZZA
4
4
LABELS AND ASSEMBLY INSTRUCTIONSTARGHETTE E INFORMAZIONI PER IL CENTRO STAMPA
QUESTA PAGINA NON VA INSERITA NEL MANUALETHIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
COD.MANUALE HDBK P/N: 3AL 89871 AAAA Ed.01
ISA–ES1/ES4 Rel.1.1
ES1/ES4 CT OPERATOR’S HANDBOOK
ORIGINALE INTERLEAF: FILE ARCHIVIAZIONE: cod ANV (PD1-PD2)
– No PAGINE TOTALI PER ARCHIVIAZIONE: 220+4=224– DIMENSIONE BINDER SORGENTE (du –ks): 62.652 kBytes
INFORMAZIONI PER IL CENTRO STAMPA - ASSEMBLY INSTRUCTIONS
– STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING
– COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE:HANDBOOK COMPOSITION AND ASSEMBLY:
No pagine(facciate)
numeratenumbered(facciate)
No pages da from a to
TARGHETTE - LABELS
3AL 89871 AAAA Ed.01
frontespiziofront
2 1/2 2/2
3AL 89871 AAAA Ed.01manualemanual
218 1/218 218/218
TOTALE PAGINE A4 (FACCIATE) TOTAL A4 PAGES: 220
TOTALE FOGLI A4 TOTAL A4 SHEETS: 110
WARNING FOR A-UNITS OTHER THAN A-ITALY
• Labels are done according to A-Italy binder format.• Source file ALICE 6.10
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
Y 2
01
RELEASED
/3AL 89871 AAAA TQZZA
4
4
QUESTA PAGINA NON VA INSERITA NEL MANUALETHIS PAGE MUST NOT BE INCLUDED IN THE HANDBOOK
FCGSite
Originators
VIMERCATE
:
Domain
ES1/ES4 REL.1.1
Division
Rubric
CT OPERATOR’S HANDBOOK
TypeDistribution Codes Internal External
::::
ONDSDHISA–ES1/ES4ISA–ES1/ES4 REL.1.1 CT OPERATOR’S HDBK
:
A. GRADIA
Approvals
NameApp.
App.Name
D. E. MARAZZA
G. PARLADORI C. FAVERO
INFORMAZIONI EDITORIALI
– ORIGINALE SU FILE: ALICE 6.10• sistemazione ’figlist’
3AL 89871 AAAA Ed.013AL 89871 AAAA Ed.01
ISA–ES1/ES4 Rel.1.1
Ethernet Switching System
ES1/ES4 CT OPERATOR’S HANDBOOK
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
Y 3
01
RELEASED
/3AL 89871 AAAA TQZZA
4
4
ISA–ES1/ES4 Rel.1.1
Ethernet Switching System
ES1/ES4 CT OPERATOR’S HANDBOOK
3AL 89871 AAAA Ed.01
VOL.1/1
ISA–ES1/ES4 Rel.1.1
Ethernet Switching System
ES1/ES4 CT OPERATOR’S HANDBOOK
3AL 89871 AAAA Ed.01
VOL.1/1
ISA–ES1/ES4 Rel.1.1
Ethernet Switching System
3AL 89871 AAAA Ed.01 ES1/ES4 CT OPERATOR’S HANDBOOK VOL.1/1
ISA–ES1/ES4 Rel.1.1
Ethernet Switching System 3AL 89871 AAAA Ed.01 ES1/ES4 CT OPERATOR’S HANDBOOK VOL.1/1
ISA–ES1/ES4 Rel.1.1
Ethernet Switching System
3AL 89871 AAAA Ed.01 ES1/ES4 CT OPERATOR’S HANDBOOK VOL.1/1
All
right
s re
serv
ed. P
assi
ng o
n an
d co
pyin
g of
this
docu
men
t, us
e an
d co
mm
unic
atio
n of
its
cont
ents
not p
erm
itted
with
out w
ritte
n au
thor
izat
ion
from
Alc
atel
.
ED
1AA
000
14 0
004
(900
7) A
4 –
ALI
CE
04.
10
Y 4
01
RELEASED
/3AL 89871 AAAA TQZZA
4
4
END OF DOCUMENT
