9500MPR R. 3.1 Node Configuration Operation and Maintetance

9500MPR (Microwave Packet Radio) (ETSI) R 3.
1 Node Configuration O&M -

Page 1
All Rights Reserved Alcatel-Lucent 2011
9500 MPR
9500 MPR (Microwave Packet Radio)
(ETSI) R 3.1 Node Configuration
Operation and Maintenance
STUDENT GUIDE
TWT63043-R 3.1-SG1-SEN- I1.0 Issue 1.00
All rights reserved Alcatel-Lucent 2011
Passing on and copying of this document, use and communication of its contents
not permitted without written authorization from Alcatel-Lucent
9500MPR (Microwave Packet Radio) (ETSI) R 3.1 Node Configuration O&M -
Page 2
9500MPR (Microwave Packet Radio) (ETSI) R 3.1 Node Configuration O&M
9500 MPR
2
Empty page
Switch to notes view!
This page is left blank intentionally
Page 3
9500 MPR
3
Terms of Use and Legal Notices
1. Safety Warning
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to wear
conductive jewelry while working on the products. Always observe all safety precautions and do not work on the equipment
alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (Marks) are the property of their respective holders, including Alcatel-Lucent.
Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning the Mark. The
absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to change
without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other
use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and must
include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used,
copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and
is expressly prohibited from modifying the information or creating derivative works without the express written consent of
Alcatel-Lucent.
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including lost
profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not Alcatel-Lucent has
been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an endorsement, nor
a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The information
contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some cases, due to
contractual limitations, certain compromises have been made and therefore some features are not entirely accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment and
its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. Alcatel-Lucent
disclaims any warranties in connection with the products as used and described in the courses or the related documentation,
whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties, including warranties of
merchantability, non-infringement and fitness for a particular purpose, or arising from a course of dealing, usage or trade
practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are governed by
the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal Notices, or the application
thereof to any person or circumstances, is held invalid for any reason, unenforceable including, but not limited to, the warranty
disclaimers and liability limitations, then such provision shall be deemed superseded by a valid, enforceable provision that
matches, as closely as possible, the original provision, and the other provisions of these Terms of Use and Legal Notices shall
remain in full force and effect.
Page 4
9500 MPR
4
Blank Page
Page 5
9500 MPR
5
Course Outline
About This Course
Course outline
Technical support
Course objectives
1. Topic/Section is Positioned Here
Xxx
Xxx
Xxx
1. NE Operation
Module 1. 3JK Operator Interface MPR Node
Module 2. 3JK Initial Configuration MPR Node
Module 3. 3JK Performance Monitoring MPR Node
2. Maintenance
Module 1. 3JK Fault Management
Module 2. 3JK Software Download
Page 6
9500 MPR
6
Course Outline [cont.]
Page 7
9500 MPR
7
Course Objectives
Welcome to 9500MPR (Microwave Packet Radio) (ETSI) R3.1 Node Configuration
O&M
Upon completion of this course, you should be able to:
Configure as a Node and manage the 9500MPR R3.1
Page 8
9500 MPR
8
Course Objectives [cont.]
Page 9
9500 MPR
9
About this Student Guide
Conventions used in this guide
Where you can get further information
If you want further information you can refer to the following:
Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful or
interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical Practices
where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment damage or
personal injury.
Page 10
9500 MPR
10
About this Student Guide [cont.]
Page 11
9500 MPR
11
Self-assessment of Objectives
At the end of each section you will be asked to fill this questionnaire
Please, return this sheet to the trainer at the end of the training
Contract number :
Course title :
Client (Company, Center) :
Language : Dates from : to :
Number of trainees : Location :
Surname, First name :
Did you meet the following objectives ?
Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Instructional objectives
Yes (or
globally
yes)
No (or
globally
no)
Comments
1 To be able to:
Describe the basic concepts of
9500MPR

2 To be able to:
Describe the main functionalities
of the 9500MPR

3 To be able to:
Describe the management system of
the 9500MPR

4 To be able to :
Describe the functionality of each unit
of the MSS

5 To be able to:
Describe the functionality of the ODUs

6 To be able to:
understand all the menus available
with the LCT

7 To be able to:
Configure a NE starting from scratch

8 To be able to:
Activate and evaluate the performance
monitoring application

9 To be able to:
Performa the troubleshooting of the
9500MPR

10 To be able to:
Perform the SW download of the 9500MPR

Page 12
9500 MPR
12
Self-assessment of Objectives [cont.]
Instructional objectives
Yes (or
Globally
yes)
No (or
globally
no)
Comments

Thank you for your answers to this questionnaire
Other comments
Section 1 Module 1 Page 1

All Rights Reserved 2011, Alcatel-Lucent
3JK Edition 2.0
Do not delete this graphic elements in here:
Module 1
Operator Interface MPR Node
3JK Edition 2.0
Section 1
NE Operation
3JK Edition 2.0
9500 MPR 9500MPR (Microwave Packet Radio) (ETSI) R 3.1 Node Configuration O&M
NE Operation Operator Interface MPR Node
1 1 2
Blank Page
Updated to rel 3.1 ALU University 2011-08-25 02
First edition External Consultant 2007-07-30 01
Remarks Author Date Edition
Document History
3JK Edition 2.0
1 1 3
Objectives
Objectives: to be able to
understand all the menus available with the LCT.
3JK Edition 2.0
1 1 4
Objectives [cont.]
3JK Edition 2.0
1 1 5
Table of Contents
Page
1 WebEML start 11
1.1 WebEML start 12
2 WebEML Main View 15
2.1 WebEML Main view 16
2.2 Main Tool Bar Area 19
2.3 Severity Alarm Panel 21
2.4 Domain Alarm Synthesis Panel 22
2.5 Management State Control Panel 23
2.6 Selection Criteria 24
2.7 Button Policy 25
Blank Page 26
3 Menu Configuration 27
3.1 Menu Configuration 28
3.2 Menu NE Time 29
3.3 Menu Network Configuration 30
3.3.1 Local Configuration 31
3.3.2 NTP Configuration 32
3.3.3 IP Static Routing Configuration 33
3.3.4 OSPF Area Configuration 35
3.3.5 Routing Information 37
3.4 Menu Alarm Severities 38
3.5 Menu System Settings 42
3.6 Menu Cross Connections 45
3.6.1 LAG/RING area 46
3.6.1.1 LAG 47
3.6.1.2 Ring 48
3.6.2 Connectors 49
3.6.3 Graphical Area 52
3.6.4 Buttons 53
3.6.5 Segregated port view 54
3.6.6 How to segregate slots or ports 55
3.6.7 How to create a cross-connection 57
3.6.8 Creation Dialogs 59
3.6.9 Information Dialogs 60
3.6.10 TDM Cross-Connections 61
3.6.10.1 PDH to Radio/MPT-ACC 62
3.6.10.2 Radio to Radio 64
3.6.10.3 Radio/MPT-ACC to Ethernet 66
3.6.10.4 PDH to Ethernet 69
3.6.11 Cross-Connections with TDM2Eth Profile 71
3.6.12 How to modify a TDM cross-connection 74
3.6.12.1 PDH to Radio/MPT-ACC 75
3.6.12.3 Radio/MPT-ACC to Ethernet 77
3.6.12.4 PDH to Ethernet 78
3.6.13 SDH Cross-Connections with SDHACC 79
3.6.13.1 SDH to Radio/MPT-ACC 80
3.6.14 How to modify an SDH cross-conn. with SDHACC 84
3.6.15 SDH Cross-Connections with SDHCHAN 87
3.6.15.2 PDH to SDH 90
3.6.16 How to modify an SDH cross-con. with SDHCHAN 92
3JK Edition 2.0
1 1 6
Table of Contents [cont.]
Page
3.6.16.2 PDH to SDH 94
3.6.17 ATM Cross-Connections (ETSI market only) 95
3.6.17.1 ASAP Radio 96
3.6.17.2 Radio Radio 99
3.6.17.3 Radio Ethernet 102
3.6.17.4 ASAP Ethernet 104
3.6.18 How to modify an ATM cross-connection 106
3.6.18.1 ASAP - Radio 107
3.6.18.2 Radio - Radio 108
3.6.18.3 Radio - Ethernet 109
3.6.18.4 ASAP - Ethernet 110
3.6.19 LAG-LAG Cross-Connections 111
3.6.19.1 Ethernet LAG - Radio LAG cross-conn. 112
3.6.19.2 Radio LAG - Radio LAG cross-conn. 114
3.6.20 How to modify a LAG-LAG cross-connection 116
3.6.20.1 Ethernet LAG to Radio LAG 117
3.6.20.2 Radio LAG to Radio LAG 118
3.6.21 Ring Cross-Connections 119
3.6.21.1 PDH - Ring 120
3.6.21.2 Radio Ring 122
3.6.21.3 Ethernet - Ring 125
3.6.21.4 Pass-through 128
3.6.22 How to modify a Ring cross-connection 131
3.6.22.1 PDH - Ring 132
3.6.22.2 Radio - Ring 133
3.6.22.3 Ethernet - Ring 134
3.6.22.4 Pass-through 135
3.7 Menu AUX Cross Connections 136
3.7.1 Local User Service Channel Cross-connection 137
3.7.2 Service Channels Cross-connect. in pass-through 138
3.7.3 How to create an AUX cross-connection 139
3.7.4 How to delete an AUX Cross Connection 141
3.8 Menu XPIC Configuration 142
3.8.1 1+0 XPIC 144
3.8.2 1+1 XPIC 147
3.8.3 How to remove the XPIC association 149
3.9 Menu VLAN Configuration 150
3.9.1 802.1D 151
3.9.2 802.1Q 152
3.9.2.1 VLAN 1 Management 154
3.9.2.2 VLAN Table Management 155
3.9.3 Ethernet Ring 157
3.10 Menu Traffic Descriptors 158
3.11 Menu Profile Management 161
3.11.1 User Profiles Management 162
3.11.2 User Management 163
3.11.3 How to Create a New User 164
3.11.4 How to Delete a User 166
3.11.5 Change the Password (by the Administrator) 167
3.11.6 Change Password (by the User) 168
3.12 Ethernet Features Shell 169
3.12.1 Simple examples for LAG creation 170
Blank Page 172
3JK Edition 2.0
1 1 7
Page
4 Menu Diagnosis 173
4.1 Menu Diagnosis 174
4.2 Alarms 175
4.2.1 File Menu 181
4.2.2 Filters Menu 182
4.2.2.1 Close Filter ... 183
4.2.2.2 Add a Filter 184
4.2.2.3 Edit Selected Filter 185
4.2.2.4 Delete Selected Filter 186
4.2.2.5 Delete Filters ... 187
4.2.2.6 Save Filters As ... 188
4.2.2.7 Load Filters From ... 189
4.2.3 Help Menu 190
4.3 Log Browsing 191
4.3.1 Event Log Browser 192
4.3.1.1 File Menu 194
4.3.1.2 Help Menu 197
4.4 Remote Inventory 198
4.5 Abnormal Condition List 199
4.6 Summary Block Diagram View 200
4.6.1 Main Block diagram view 201
4.6.2 PDH unit secondary view 202
4.6.3 SDH unit secondary view 206
4.6.4 Radio unit secondary view (ODU300) 210
4.6.5 MPT-ACC unit secondary view (MPT-HC) 216
4.6.6 MPT-ACC unit secondary view (MPT-MC) 222
4.6.7 XPIC 228
4.7 Current Configuration View 230
5 Menu Supervision 231
5.1 Menu Supervision 232
5.2 Access State 233
5.2.1 Requested (Switching OS <-> WebEML access state) 234
5.2.2 OS (Switching WebEML access state <-> OS) 235
5.3 Restart NE 236
5.4 Restart MPT 237
5.5 MIB Management 238
5.5.1 Backup 239
5.5.2 Restore 240
5.5.3 Remove file 241
5.6 SW Licence 242
6 Tab-panel Equipment 243
6.1 Tab-pabel equipment 244
6.2 Starting From Scratch 247
6.3 Tab panels in the Resource Detail Area 248
6.3.1 Alarms tab-panel 249
6.3.2 Settings tab-panel 250
6.3.2.1 Equipment Type 251
6.3.2.2 Alarm Profile 256
6.3.2.3 Protection Type (P32E1DS1 & MD300) 257
6.3.2.4 Protection Type with MPT Access unit 259
6.3.2.5 Protection Type Configuration with STM-1 units 261
6.3.2.6 Unit stacking 262
6.3.3 Remote Inventory tab-panel 263
Blank Page 264
3JK Edition 2.0
1 1 8
Page
7 Tab-panel Protection Schemes 265
7.1 General 266
7.2 EPS Management 268
7.2.1 Protection Scheme Parameters 269
7.2.2 Commands 270
7.3 RPS Management 271
7.3.1 Alarms 272
7.3.3 Commands 274
7.4 HSB Protection Management 275
7.4.2 Commands 277
Blank Page 278
8 Tab-panel Synchronization 279
8.1 Menu Synchronization 280
8.2 Synchronization Sources assignment 281
8.3 Synchronization sources assignment rules 285
8.4 Allowed synchronization sources assignment 286
8.5 SSM Summary Table 287
Blank Page 288
9 Tab-panel Connections 289
9.1 Menu Connections 290
10 PDH view for PDH domain 291
10.1 PDH Unit configuration 292
10.1.1 Alarms tab-panel 294
10.1.2 Settings tab-panel 295
10.1.3 General information on Circuit Emulation 296
10.1.4 Node Timing configuration 299
10.2 Loopback 300
10.2.1 How to activate a loopback 301
10.2.2 How to remove a loopback 302
11 SDH view for SDH domain 303
11.1 General information 304
11.1.1 Protection 305
11.1.2 Clocking options 306
11.1.3 Tab-panels 307
11.2 Alarms 308
11.3 Settings for SDHACC unit (Transparent mode) 309
11.4 Settings for SDHCHAN (Channelized mode) 310
11.4.1 Signal Mode 312
11.4.2 Service Profile 313
11.4.3 Buttons 314
11.4.4 General information on C. E. 315
11.4.4.1 TDM2TDM 317
11.4.4.2 TDM2ETH 318
12 EAS View for EAS Domain 319
12.1 EAS Domain 320
12.1.1 Ethernet Physical Interface 321
12.1.1.1 Alarms tab-panel 322
12.1.1.2 Settings tab-panel (Ethernet Port#1 to Port#4) 323
3JK Edition 2.0
1 1 9
Page
13 Ethernet Ring Configuration view 325
13.1 Ethernet Ring Protection (ERP) overview 326
13.1.1 Topology 327
13.1.2 Ring Link and Ring Port 328
13.1.3 Ring Protection Link (RPL) 329
13.1.4 RPL Owner 330
13.2 ERP Configuration procedure 331
13.2.1 Step 1: Topology creation 332
13.2.2 Step 2: ERP Instance Creation 334
13.2.3 Step 3: Add VLANs to created instances 338
13.2.4 Step 4: ERP Instances enabling 340
13.3 Configuration example of an Ethernet ring 341
14 Radio view for Radio domain 343
14.1 Radio domain menu 344
14.2 Alarms 345
14.3 Settings 346
14.3.1 ODU300 347
14.3.1.1 Direction area 348
14.3.1.2 Channel area 360
14.3.2 MPT-HC 366
14.3.3 MPT-MC 387
14.4 Measurement 407
14.4.1 How to read a Power Measurement file 411
14.5 Loopback 412
14.5.1 How to activate a loopback 415
14.5.2 How to remove a loopback 416
14.6 Power Source 417
15 ATM view for ATM DOMAIN 419
15.1 ATM view for ATM DOMAIN 420
15.1.1 E1 Layer 421
15.1.2 IMA Layer 422
15.1.3 ATM Layer 425
15.1.3.1 ATM Layer Configuration 426
15.1.3.2 VP Layer Configuration 428
15.1.3.3 VC Layer Configuration 433
15.1.4 ATM PW Layer 436
15.1.4.1 ATM PW Parameters 437
15.1.4.2 VPI/VCI Translation 440
16 Core-E view for Core-E and Ethernet domain 441
16.1 Core-E domain 442
16.1.1 Ethernet Physical Interface 443
16.1.1.1 Alarm tab-panel 444
16.1.1.3 Settings tab-panel (Ethernet Port#5 and #6) 446
16.1.2 TMN Interface 447
16.1.2.1 Alarms tab-panel 448
16.1.2.2 TMN In-band 449
16.1.2.3 TMN Ethernet port 450
16.1.2.4 TMN Ethernet Port #4 451
16.1.3 Ethernet LAG 452
16.1.3.1 MPT-HC connected to the Core-E 454
3JK Edition 2.0
1 1 10
Page
17 AUX view for AUX DOMAIN 455
17.1 AUX view for AUX DOMAIN 456
17.1.1 Settings 457
17.1.2 External Points 458
17.1.2.1 Input External Points 459
17.1.2.2 Output External Points 460
18 Annex A: Network Element Overview 461
18.1 Main View 462
18.2 NE Configuration area 463
18.2.1 NE Information 464
18.2.2 NE Description 465
18.2.3 Command Buttons 466
18.3 Status & Alarms area 467
18.4 Supervision Function 468
18.5 MenuBar 469
18.6 Sequence for NEtO interface and NE list 471
18.7 CS (Community String) 472
Answer the Questions 476
Blank Page 477
End of Module 478
3JK Edition 2.0
1 1 11
1 WebEML start
3JK Edition 2.0
1 1 12
1 WebEML start
1.1 WebEML start
This chapter explains all the screens of the WebEML, which is started
by a double click on the WebEML icon of the PC desktop.
The PC must be connected to the TMN port of the Core-E unit in the
MSS.
1) Start the WebEML by double click on the relevant icon on the PC desktop.
3JK Edition 2.0
1 1 13
1 WebEML start
1.1 WebEML start [cont.]
2) NEtO opens. Insert the IP address of the NE (default: 10.0.1.2) and click OK.
For more details on NEtO refer to Annex A: Network Element Overview.
Note: To access the NE the PC must be configured to Get automatically an IP address, because the NE is
configured as DHCP Server with default IP address 10.0.1.2.
3JK Edition 2.0
1 1 14
1 WebEML start
1.1 WebEML start [cont.]
3) When the NE is supervised, click Show.
4) The Main view opens.
3JK Edition 2.0
1 1 15
2 WebEML Main View
3JK Edition 2.0
1 1 16
2 WebEML Main View
2.1 WebEML Main view
The WebEML Main View Area manages all domains from which the
operator can start. It is organized with tab panels, e.g. many windows
placed one upon another. Each window is selectable (placing it on top
of the others) with a tab shown on the top.
Two Main views are possible according to the MSS version:
MSS-8
MSS-4
3JK Edition 2.0
1 1 17
2 WebEML Main View
2.1 WebEML Main view [cont.]
MSS-8
Tab-panels
Each tab-panel represents a set of functions. The following tab-panels are present:
Equipment (to manage the equipment configuration)
Schemes (to manage the protection schemes in 1+1 configuration)
Synchronization (to manage the synchronization)
Connections (to manage the cross-connections)
Each tab-panel consists of three areas:
Resource-Tree Area: displays all the available resources of the NE.
Resource-List Area: may be represented by: Tabular View or Graphical View.
Tabular View: displays a tabular representation of the selected resource. As default, no tabular element is shown.
Graphical View: displays a graphical representation of the selected resource. As default, no tabular element is shown.
Resource-Detail Area: displays detailed information of a selected item in the Resource List area. As a default, no entry view is
displayed as a consequence of the default behavior of the Resource List area.
Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration functions. Following multiple
main views are available:
Equipment view, for Equipment configuration;
Radio view, for Radio domain (double click on a Radio unit);
PDH view, for PDH domain (double click on a PDH unit);
SDH view, for SDH domain (double click on an SDH unit);
EAS view, for EAS domain (double click on a P8ETH unit);
ATM view, for ATM domain (double click on an ASAP unit);
AUX view, for Auxiliary channel domain (double click on the AUX peripheral unit);
Core-E view, for Core-E and Ethernet domain (double click on a Core-E unit).
Navigation from main view to multiple main views (related to the equipment components) can be done by simply double-clicking on the
component graphical representation. Such operation will open a new window containing selected secondary view. Starting from main
view, the operator will also see all slots and ODUs layout. Each slot contains schematics of available board (if present) together with
status and other details. Slots schematics will in fact contain usual alarms information with a clarifying coloured icon that reports the
same icon visible in tree view.
Other icons are:
On the right of the unit front panel, a new icon could be a check mark ( ) or a switch symbol ( ).
: it means the slot is active;
: it means the slot is in stand-by mode.
As shown in Figure, an X-shaped icon ( ) will be added on the left to slots when some cross connections are related to it.
3JK Edition 2.0
1 1 18
2 WebEML Main View
2.1 WebEML Main view [cont.]
MSS-4
Tab-panels
Each tab-panel represents a set of functions. The following tab-panels are present:
Equipment (to manage the equipment configuration)
Schemes (to manage the protection schemes in 1+1 configuration only)
Synchronization (to manage the synchronization)
Connections (to manage the cross-connections)
Each tab-panel consists of three areas:
Resource-Tree Area: displays all the available resources of the NE.
Resource-List Area: may be represented by: Tabular View or Graphical View.
Tabular View: displays a tabular representation of the selected resource. As default, no tabular element is shown.
Graphical View: displays a graphical representation of the selected resource. As default, no tabular element is shown.
Resource-Detail Area: displays detailed information of a selected item in the Resource List area. As a default, no entry view is
displayed as a consequence of the default behavior of the Resource List area.
Figure (Main view) is the entry point of the application and provides basic diagnostic and configuration functions. Following multiple
main views are available:
Equipment view, for Equipment configuration;
Radio view, for Radio domain (double click on a Radio unit);
PDH view, for PDH domain (double click on a PDH unit);
SDH view, for SDH domain (double click on an SDH unit);
EAS view, for EAS domain (double click on a P8ETH unit);
ATM view, for ATM domain (double click on an ASAP unit);
AUX view, for Auxiliary channel domain (double click on the AUX peripheral unit);
Core-E view, for Core-E and Ethernet domain (double click on a Core-E unit).
Navigation from main view to multiple main views (related to the equipment components) can be done by simply double-clicking on the
component graphical representation. Such operation will open a new window containing selected secondary view. Starting from main
view, the operator will also see all slots and ODUs layout. Each slot contains schematics of available board (if present) together with
status and other details. Slots schematics will in fact contain usual alarms information with a clarifying coloured icon that reports the
same icon visible in tree view.
Other icons are:
On the right of the unit front panel, a new icon could be a check mark ( ) or a switch symbol ( ).
: it means the slot is active;
: it means the slot is in stand-by mode.
As shown in Figure, an X-shaped icon ( ) will be added on the left to slots when some cross connections are related to it.
3JK Edition 2.0
1 1 19
2 WebEML Main View
2.2 Main Tool Bar Area
This area contains a selection of handy quick-access buttons for
common features.
Left arrow to previous screen
Second button: not operative
Right arrow to next screen
Block Diagram View: opens the Summary Diagram view
Current Configuration View: opens the Current Configuration view
Cross-Connections: opens the Cross-Connections menu
Segregated Ports: opens the Segregated Ports menu
Ethernet Ring: opens the Ethernet Ring Configuration View
AUX Cross Connections: opens the AUX Cross Connections menu
3JK Edition 2.0
1 1 20
2 WebEML Main View
2.2 Main Tool Bar Area [cont.]
XPIC Configuration: opens the XPIC Configuration menu
VLAN management: opens the VLAN Management menu
WT Performance Monitoring Suite: opens the WT Performance Monitoring
Suite menu
3JK Edition 2.0
1 1 21
2 WebEML Main View
2.3 Severity Alarm Panel
The WebEML provides an alarm functionality that informs the operator on the severity of
the different alarms in the NE as well as on the number of current alarms. There are five
different alarm severity levels. In the WebEML these different levels are associated with
colors:
Red: Critical alarm (CRI).
Orange: Major alarm (MAJ).
Yellow: Minor alarm (MIN).
Cyan: Warning alarm (WNG).
Blue: Indeterminate (IND).
Each alarm severity is represented by an alarm icon situated in the top left hand corner
of the view. These alarm icons are constantly represented on the different Equipment
views (NE view, Board view or Port view) so that the operator is always aware of the
alarms occurring in the system.
Furthermore the shape of the alarm icons in the alarm panel gives an indication of the
occurrence of alarms. The figures below describe the different examples.
An alarm icon with a circle inside it (and a number at the bottom of the icon) indicates
that alarms of the number and the type defined by the icon are occurring.
An alarm icon with a rectangle inside it indicates that no alarms of the type defined by
the icon are occurring.
An alarm icon grayed out indicates that spontaneous incoming alarm notification have
been inhibited.
N.B. The meaning of the icons in the Severity alarm synthesis is:
1) CRI - Critical alarm
Synthesis of alarms that needs immediate troubleshooting (typical: NE isolation).
2) MAJ - Major (Urgent) alarm
Synthesis of alarms that needs immediate troubleshooting.
3) MIN - Minor (Not Urgent) alarm
Synthesis of alarms for which a deferred intervent can be decided.
4) WNG - Warning alarm
Synthesis of alarms due to failure of other NE in the network.
5) IND - Indeterminate alarm
Synthesis of alarms not associated with the previous severities. Not operative.
3JK Edition 2.0
1 1 22
2 WebEML Main View
2.4 Domain Alarm Synthesis Panel
This area contains the bitmaps (more than one) representing the alarms
per domain. Each bitmap indicates the number of alarm occurrences for
each domain.
The meaning of the icons in the Domain alarm synthesis area is:
1) EXT - External Point
Synthesis of the External Points (Housekeeping alarms).
2) EQP Equipment alarm
Synthesis of alarms of the Equipment domain.
3) TRS Transmission alarm
Synthesis of alarms of the Transmission domain.
3JK Edition 2.0
1 1 23
2 WebEML Main View
2.5 Management State Control Panel
The different management states concerning the NE are also
represented via icons located in the top right corner of the equipment
views.
These icons are (from up to down):
1) Laptop icon: Local Access state: indicates whether the NE is managed by a
WebEML or by the OS
2) COM icon: Operational state: indicates whether or not the communication
with the OS is established.
3) SUP icon: Supervision state: indicates whether or not the NE is under OS
supervision.
4) OS icon: OS isolation.
5) NTP Server Status icon.
6) AC icon: abnormal condition state: indicates whether some abnormal
conditions have been recognized. The operator can visualize them with the
Diagnosis -> Abnormal condition list menu.
N.B.: As for the alarm icons, a rectangular management state icon represents the stable state while a
circular icon shape represents an unstable management state.
The meaning of the icons in the Management State Control Panel is:
1) Local Access State
GREEN LED: Indicates that the Craft Terminal has the OS permission to manage the NE (granted).
CYAN LED: Indicates that the Craft Terminal has not the OS permission to manage the NE (denied).
2) COM NE rechable/unreachable
GREEN LED: Identifies the Enable operational state of the connection between NE and Craft Terminal
(link down).
RED LED: Identifies the Disable operational state of the connection between NE and Craft Terminal
(link down).
3) SUP Supervision state
GREEN LED: NE is under supervision
BROWN LED: NE is not under supervision
Used in the OS.
4) OS OS isolation
5) NTP Network Timing Protocol
BROWN LED: Protocol disabled
GREEN LED: Protocol enabled, but the two servers are unreachable.
CYAN LED: Protocol enabled and one of the two servers is reachable.
6) AC Abnormal Condition
GREEN LED: Normal operating condition.
CYAN LED: Detection of an ABNORMAL operative condition. Type: switch forcing.
3JK Edition 2.0
1 1 24
2 WebEML Main View
2.6 Selection Criteria
Each tree node consists of possibly three symbols and a label. The first
optional symbol indicates structure state: if symbol is , three can be
expanded showing its contained lower levels. Tree structure can be
collapsed if symbol is . With no symbol, node represents a tree leaf.
Second symbol is the graphical representation of resource itself. Third
symbol is alarm status of component. The operator can select resource
by clicking with mouse to perform the action dependent on click type.
Resource Detail Area related to the selected item is displayed.
Each resource listed above may be selected by using the mouse by a:
Single left click:
By a single left click the resource is highlighted. This selection causes the activation
of the resource list area, e.g., every time the operator selects a resource in the
resource tree area the corresponding data are displayed in the Resource list area.
Double left click:
Double click operation on resource tree items allows the operator expanding tree
structure, so activating the display/update of resource list area, that will display
same information as for single click operation. As soon as a node is expanded,
another double click on such node would collapse tree structure to its closed view.
3JK Edition 2.0
1 1 25
2 WebEML Main View
2.7 Button Policy
The possible buttons for selection are the following:
Apply
this button activates the modify, but it does not close the window.
Cancel
this button closes the window without modifying the parameters displayed in the
window.
OK
this button activates the modify and closes the window
Close
this button closes the window
Help
this button provides the help management for the functions of the supporting
window.
3JK Edition 2.0
1 1 26
Blank Page
3JK Edition 2.0
1 1 27
3 Menu Configuration
3JK Edition 2.0
1 1 28
3.1 Menu Configuration
Menu Configuration is divided in:
NE Time
Network Configuration
Alarm Severities
System Settings
Cross Connections
AUX Cross Connections
XPIC Configuration
VLAN Configuration
Traffic Description
Profiles Management
Ethernet Features Shell
3JK Edition 2.0
1 1 29
3.2 Menu NE Time
The NE local time can be displayed and/or re-aligned to the OS time basis.
From the Configuration pull down menu, select the NE Time option.
The dialogue box opens, from which the local NE can be set.
The NE Time dialogue box displays the current NE time and the current OS time.
To re-align the NE time to the OS time, click on the Set NE Time With OS Time check box and click the
Apply pushbutton to validate.
The Refresh pushbutton causes the refresh of the screen.
The NTP Status field is a read-only field, which shows the configuration regarding the NTP (Network Time
Protocol), if the protocol has been enabled and configured in Menu Configuration Network
Configuration NTP Configuration.
The NTP Status field shows:
status of NTP (enabled/disabled);
IP address of the Main Server, which distributes the time to all the NEs in the network;
IP address of the Spare Server (IP address of a second NTP Server), which replaces the Main Server in case
of failure.
Note: If a change of Change Time Zone on the PC is applied with the JUSM opened, in order to make it
updated on WebEML Close/Open the JUSM application and Read Time another time.
3JK Edition 2.0
1 1 30
3.3 Menu Network Configuration
The Network Configuration allows to perform the following operations:
Local Configuration:
defines the local virtual NE address
NTP Configuration
defines the Network Time Protocol
Ethernet Configuration
not implemented
IP Configuration which comprises:
IP static routing configuration: defines the Host/Network destination address for IP
static routing
OSPF Area configuration: defines the Open Shortest Path First address
IP Point-To-Point Configuration: defines the IP address of the interfaces which use
the PPP protocol (not implemented)
Routing information:
shows a summary of the information relevant to the routing which has been
configured.
3JK Edition 2.0
1 1 31
3.3.1 Local Configuration
Select the Network Configuration option and then, from the cascading
menu, the Local Configuration option.
The dialogue box opens, which allows to configure the local IP address
of the NE.
This local IP address is the IP address associated to a virtual interface
and to the other interfaces which use the PPP protocol (the TMN-RF
channels).
Default IP address: 10.0.1.2
Default mask: 255.255.255.255
Apply button is used to perform a configuration change of the data contained in the dialogue box and
closes it; the dialogue is visible until the end of the operations and a wait cursor is displayed.
Close button closes the dialogue.
Help button provides some useful information on the dialogue.
3JK Edition 2.0
1 1 32
3.3.2 NTP Configuration
This menu allows to enable the NTP (Network Time Protocol).
Put a check mark in the NTP protocol field to enable the protocol and write in the Main Server address
field the IP address of the server, which is in charge to distribute the time to all the NEs in the network. In
the Spare Server address field write the IP address of the Spare Server.
The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The
following information can appear:
"Main server reachable"
"Spare server reachable"
"None servers reachable"
"Both servers reachable"
Click on Refresh to update the screen.
Click on Apply to send to the NE the NTP Configuration.
3JK Edition 2.0
1 1 33
3.3.3 IP Static Routing Configuration
By selecting IP static routing configuration a dialog-box opens, which
allows to configure the parameters for IP Static Routing Configuration.
The following fields and data are present:
IP Address: allows to define the IP address necessary to reach a specific
host/network
IP Mask: allows to define the IP Mask to reach a network
Default Gateway IP Address: allows to define the address of the next hop
gateway
Interface type: allows to use point to point interfaces made available by the
NE.
In the Host or Network Address Choice field select:
Host to address to a single IP address;
Network to address to a range of IP addresses.
In the Default Gateway or Point to Point I/F Choice select:
Default Gateway IP Address for the Ethernet interface;
Point to Point Interface Index for the NMS channels.
Apply button is used to perform a configuration change of the data contained in the complete table and
close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Close button closes the dialogue without changing of the data.
This is the IP interface to a host or network. Typically used at a spur to interface a host over the RF path. In
this scenario, the Default Gateway IP Address is 0.0.0.0 and the IP Mask (greyed out) is 0.0.0.0. Also
typically used at an end terminal in a radio link for interface with the network.
WARNING:
No pending (open) static routes are allowed.
The default software uses first the static routes and then the dynamic routes. An open static route is
always considered as a preferential path.
If in the screen the Default Gateway IP Address check box has been selected, write in the Default Gateway
IP Address field below the relevant IP address.
By pressing Create pushbutton it is possible to create new or change existing IP static routes
3JK Edition 2.0
1 1 34
3.3.3 IP Static Routing Configuration [cont.]
3JK Edition 2.0
1 1 35
3.3.4 OSPF Area Configuration
By selecting OSPF Area Configuration a dialog-box opens, which allows
to configure the parameters for OSPF (Open Shortest Path First) Area
Table Configuration.
The following fields and data are present:
OSPF Area IP Address
OSPF Area Stub
The fields give a synthetical information that includes all the addresses
(specific to a NE and to a Network) in an Area.
Apply button is used to perform a configuration change of the data contained in the complete RAP table
and close the view; the view is visible until the end of the operations and a wait cursor is displayed.
New button is used to insert a new page.
Delete button is used to delete the selected page.
Close button closes the dialogue without changing of the data.
WARNING: When the area is a Stub area, all the interfaces (NMS and Ethernet) must be defined Stub".
By pressing Create pushbutton a new screen opens.
N.B. 3 areas max. can be created.
In this new screen write the IP address, the IP mask and select the flag (True/False).
3JK Edition 2.0
1 1 36
3.3.4 OSPF Area Configuration [cont.]
3JK Edition 2.0
1 1 37
3.3.5 Routing Information
By selecting Routing Information a dialog-box opens: this screen is a
read-only screen and displays the routing parameters currently active
on the NE.
The pushbutton Refresh allows to refresh the information shown in the screen.
The Close button closes the dialogue without changing of the data.
3JK Edition 2.0
1 1 38
3.4 Menu Alarm Severities
This screen is a read-only screen. It is only possible to select one Profile Name and display the relevant
alarms.
3JK Edition 2.0
1 1 39
3.4 Menu Alarm Severities [cont.]
In this screen in the Profile Name field are listed the 4 default Alarm
Severity Profiles:
Profile "No Alarms". With this profile all alarms are disabled.
Profile "All Alarms". This profile enables the emission of all the alarms.
Profile "Radio Tx Alarms". This profile enables the emission of the Tx
alarms of the radio link.
Profile "Radio Rx Alarms". This profile enables the emission of the Rx
alarms of the radio link.
An Alarm Profile is the complete set of the equipment alarms with their
severity in case of Service Affecting situation and No Service Affecting
situation.
Each alarm has its Service Affecting and No Service Affecting attribute,
which can differ according to the Alarm Severity Profile.
In the current release only to 3 objects in the equipment (MSS subrack,
TMN local Ethernet, Radio) can be assigned a specific Alarm Profile.
3JK Edition 2.0
1 1 40
1. Select the object to which an Alarm Profile has to be associated.
2. Click on the icon.
3JK Edition 2.0
1 1 41
3. Select the Alarm Profile to be associated.
4. Put a check mark on the
"Show details" box.
5. The list of the alarms with
the relevant severity will
appear.
6. Click on Apply to
associate the
Alarm Profile.
3JK Edition 2.0
1 1 42
3.5 Menu System Settings
This menu allows the system configuration, providing the setting of
some parameters for the NE setup.
The NE configuration tab-panel has 8 fields:
Tributary Port Configuration
Quality Of Service
DHCP
Admission Control for Adaptive Modulation (ODU300 only)
Ethernet LOS Criteria
Static Lag Criteria
Event and Alarm Log
NE MAC Address
1) Tributary Port Configuration
This field allows to set the suitable impedance of the E1 stream (Unbalanced 75 ohms/Balanced 120 ohm).
To activate the new impedance, click on Apply.
2) Quality Of Service
This field allows to set the suitable Quality Of Service (Disabled/DiffServ/802.1p). To activate the new
value, click on Apply.
The Ethernet switch provides a Quality of Service mechanism to control all streams. If the QoS is disabled,
all traffic inside the switch has the same priority, this means that for each switch port there is only one
queue (FIFO) therefore the first packet that arrives is the first that will be transmitted.
The following values are available:
IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If the tag is
present the correspondent priority is assigned to the packet;
DiffServ: each packet is classified based on DSCP field in the IP header to assign the priority;
3) DHCP
The DHCP server configures automatically IP address, IP mask and default gateway of the PC Ethernet
interface used to reach the NE.
The PC must be configured to get automatically an IP address.
The DHCP server uses an address pool of 10 IP address, defined according to the NE TMN port IP address.
The IP mask is set to the mask of the NE TMN port and the default gateway is set to the NE IP address.
The lease time is fixed to 10 minutes.
To activate the DHCP server, select Enabled and click on Apply.
3JK Edition 2.0
1 1 43
3.5 Menu System Settings [cont.]
4) Admission Control for Adaptive Modulation (ODU300 only)
The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Modulation)
can be enabled or disabled. Default: Enabled.
When the Admission Control is "Enabled", the check is performed taking into account the capacity of the 4
QAM modulation scheme for the relevant Channel Spacing.
Taking as example 28 MHz channel spacing (with around 130 Mbit/s of net throughput available with
64QAM), the maximum number of E1s that could be provisioned is 18; the remaining capacity is devoted to
other types of traffic such as ATM or Ethernet.
When RSL value decreases, modulation schemes are downgraded first from 64QAM to 16QAM: the traffic
with lower priority exceeding 16QAM bandwidth is dropped and of course the E1s are kept. As soon as the
RSL value further decreases, modulation scheme are downgraded to 4QAM and all the traffic exceeding
4QAM bandwidth is dropped (while the E1s are kept). It should be noted that there is no possibility to
provision a number of E1s greater than 18, because being all the E1s with the same priority, it should not
possible from system point of view to decide "which" E1s should be dropped passing from 16QAM to 4QAM.
In order to facilitate provisioning and commissioning operations, a specific admission control check at
WebEML level has been inserted, avoiding any potential mistakes from the user provisioning a number of
E1s that are not fitting inside 4QAM bandwidth.
When the Admission Control is "Disabled", the check is performed taking into account the capacity of the
highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or 16 QAM for
4-16 QAM range).
It is possible to provision a number of E1s exceeding the 4QAM throughput; always keeping 28 MHz channel
as example, it is possible to provision more than 18E1s, up to 37E1s (value linked with 16QAM capacity). In
this case, when RSL value degrades and modulation scheme is downgraded from 16QAM to 4QAM, all the
TDM traffic is impacted. This feature is answering the need of transmitting an high number of E1s, but
without giving up the benefits of adaptive modulation for Ethernet traffic.
3JK Edition 2.0
1 1 44
3.5 Menu System Settings [cont.]
5) Ethernet LOS Criteria
By enabling this feature the following additional criteria are added to the Core protection switching
criteria:
LOS of Optical User Ethernet interface
Card Fail of SFP optical module
Card Missing of SFP optical module
LOS of any Electrical User Ethernet interfaces, including the LOS of the forth User Ethernet interface
working as TMN Local Ethernet interface.
Note: the default switching criteria are:
Core Card Missing
Core Card Fail
Control Platform operational status failure
Flash Card realignment in progress
Flash Card failure
6) Static Lag Criteria
This feature is available only if the spare Core unit has been installed.
By enabling this feature the Ethernet ports of the Core-E unit in stand-by are in ON state (as the ports of
the Active Core-E unit), but the Ethernet traffic is not forwarded.
This behavior allows to reduce the out of service time of user traffic passing through the User Ethernet
interfaces in case of Core protection switching.
This feature shall not be used, when the NE is connected to an equipment performing Link Aggregation
and not supporting Active/Standby management of aggregated links.
7) Event and Alarm Log
As default the Logging is enabled. If set to "Disabled" the events are not sent to the Event Log Browser
application.
8) NE MAC Address
This field is a read-only field, which shows the MAC address of the NE. This MAC address must be used in
the cross-connection with TDM2Eth profile.
3JK Edition 2.0
1 1 45
3.6 Menu Cross Connections
The Main view is a graphical representation of Cross-connectable slots. Slots and Ethernet ports
(represented by connectors) are arranged according to the equipment configuration:
The CORE module is on the left side of the screen.
The even numbered slots of rows 2 to 4 are on the top of the screen.
The odd numbered slots of rows 2 to 4 are on the bottom of the screen.
Protection groups are represented by:
PDH modules have a dashed line "connecting" the two connector icons. The even card connector icon is
grayed out.
EAS (Ethernet Access Service) modules have a dashed box surrounding the two slots.
MPT radios have a dashed line "connecting" the two connector icons. The higher numbered radio's
connector icon is grayed out.
There are a maximum of 6 Ethernet ports placed on the Core-E area in the left side of the screen. Port 4
is visible only when set to transport mode. If Ethernet port 4 is set to TMN, icon 4 is not shown. Port 5
and 6 are visible, if in the Core-E unit has been installed and enabled the SFP plug-in.
There are a maximum of 6 PDH/SDH/ASAP/Radio/MPT-ACC slots (placed in the MSS-8 sub-rack) or 2
PDH/SDH/ASAP/Radio/MPT-ACC slots (placed in the MSS-4 sub-rack).
P8ETH unit is not cross-connectable.
Note: In the following pages the examples will be done with MSS-8.
When two units are protected, the 2 protected slots are linked by a dashed line, (e.g.: Slot#5 RADIO is
protected with Slot#6 RADIO).
Note: Ethernet port#5 and port#6 will appear only if the optional SFP plug-in has been installed and
enabled in the Core-E unit. To enable the SFP plug-in go to the Setting tab-panel of the Core-E unit in the
Equipment tab-panel.
3JK Edition 2.0
1 1 46
3.6.1 LAG/RING area
This area includes the created LAGs (if any) and the created Ethernet
Ring (if any).
3JK Edition 2.0
1 1 47
3.6.1 LAG/RING area
3.6.1.1 LAG
If a LAG (Radio or Ethernet) has been created by using menu Configuration > Ethernet Features Shell in
the LAG area (on the right side of the screen) will appear the icons of the LAG with the identifying number
of the LAG.
Different icons are used to identify Radio LAG or Ethernet LAG.
The Ethernet ports involved in an Ethernet LAG are only present in the LAG area (not in the CORE-E area).
In the figure LAG #4 is a Radio LAG, LAG #1 is an Ethernet LAG.
3JK Edition 2.0
1 1 48
3.6.1 LAG/RING area
3.6.1.2 Ring
If an Ethernet Ring has been created by using the Ring icon in the Tool bar, the icon of the Ring will appear
with the identifying number.
3JK Edition 2.0
1 1 49
3.6.2 Connectors
The connectors representing the MSS slots are start- and end-point for
actual cross-connections. By using the mouse drag-and-drop operations
the operator can create cross-connections through these points. These
connectors have specific icons:
identifies Ethernet RJ-45 connector (Ethernet ports);
identifies PDH slots;
identifies Radio slots (to interface ODU300);
identifies MPT-ACC slots (to interface MPT-HC/MPT-HC V2/MPT-MC);
identifies Radio LAG;
identifies Ethernet LAG;
identifies an Ethernet Ring.
3JK Edition 2.0
1 1 50
3.6.2 Connectors [cont.]
The connectors have different colours depending on the associated
slots state:
White: a connector able to accept a cross-connection and has no active cross-
connection yet;
Green: a connector able to accept a cross-connection and already has one
active cross-connection at least;
Blue: a connector not able to accept a cross-connection.
3JK Edition 2.0
1 1 51
3.6.2 Connectors [cont.]
After a cross-connection creation between the points, their state will
change and a line will be drawn between the two cross-connected
points.
3JK Edition 2.0
1 1 52
3.6.3 Graphical Area
This area contains a panel and various components representing NE cross-connectable slots (or connectors).
The operator can directly edit with the mouse this graphical area to visually create and modify cross-
connections between available connectors. Figure shows an example of ongoing cross-connections
configuration.
Some steps would differ depending on cross-connection types.
3JK Edition 2.0
1 1 53
3.6.4 Buttons
At the bottom in the menu there are four buttons:
Apply: will apply changes (if any) to NE. After theyve been applied it will
update graphical state by performing a refresh; if the operation completes
without errors the sub-sequent refresh wont produce any visual change (in
other words, the state of the NE will be consistent with what is shown in the
GUI) anyway, clicking on Apply button will show a progress dialog;
Refresh: reloads the data from the NE and update the graphical state; any
modification performed and not applied will be lost;
Close: closes the cross-connection view, and return to the caller
(JusmMainView), any modification performed and not applied will be lost;
Help: opens the Help On Line.
3JK Edition 2.0
1 1 54
3.6.5 Segregated port view
From the Cross Connection view by pressing Alt+W the Segregated Port
view opens.
In the default configuration all the slots and Ethernet ports in Core unit are cross-connectedable each other
(all the slots/ports are not segregated).
To go back to the Cross Connection View press Alt+W.
Note: The MPT Access unit ports can be segregated from each other, but they cannot be individually
segregated with other ports belonging to other units.Only the complete MPT Access unit can be segregated
with other ports.
3JK Edition 2.0
1 1 55
3.6.6 How to segregate slots or ports
Double click on a slot icon or an Ethernet port icon and select the
slots/ports that can be connected (this means that the not selected
slots/ports cannot be connected; they are segregated).
Example: with a double click on the icon of Slot#5 RADIO figure opens.
To segregate Slot#5 RADIO from Ethernet ports#2, #3, #4, #5 in the
Core unit, click on the relevant square to remove the check mark.
3JK Edition 2.0
1 1 56
3.6.6 How to segregate slots or ports [cont.]
By clicking OK the Segregated Port view opens, which now shows (with
dashed lines) the segregated ports.
With the mouse pointer on a dashed line the following message will appear: "Dashed lines mean that these
ports cannot be cross-connected".
Warning: In the Nx(1+0) configuration (multiple RF channels in the same radio direction) to avoid loops only
one radio port must be active (all the other radio ports must be segregated), if the Ethernet switch is set in
802.1D mode.
3JK Edition 2.0
1 1 57
3.6.7 How to create a cross-connection
A cross-connection between two points is performed by:
Moving the mouse pointer on the source slot;
Press the left button and, while keeping button pressed, move mouse pointer
onto destination slot;
Release the left button.
3JK Edition 2.0
1 1 58
3.6.7 How to create a cross-connection [cont.]
Cross-connections Example
If the action involves two cross-connectable slots, a dialog will appear allowing the operator to setup a cross-
connection. Looking at figure, it is possible to see different aspects of configuration created by the operator:
Slot#8 PDH is cross-connected to Slot#5 radio ODU300, to Slot#4 MPT-ACC and to Ethernet Port#1;
Slot#4 MPT-ACC is cross-connected to Ethernet Port#1;
Slot#5 RADIO (and Slot#6 RADIO) are cross-connected to Ethernet Port#2;
Slot#3 MPT-ACC is cross-connected to Slot#4 MPT-ACC;
Ethernet Port#3 PDH (blue) could not accept cross-connections;
Slot#3 and Slot#4 (green) could accept more cross-connections;
Slot#5 and Slot#6 are in 1+1 configuration.
Each connection line is coloured according to slots types it connects (as shown in Figure):
PDH-Radio connection: black line;
SDH-Radio connection: black line;
ATM-Radio connection: orange line;
PDH-Eth connection: blue line;
ATM-Eth connection: magenta line;
Radio-Radio connection: red line;
Radio-Eth connection: green line;
Ring connection: cyan line.
These colours will be applied to the graphical area, when the operator releases the mouse button above cross-
connection destination slot.
Note: the ATM cross-connection lines have the following colours:
ATM-Radio connection: orange line;
ATM-Eth connection: magenta line.
In the types of cross-connections above Eth means "Ethernet User Port" or "Ethernet LAG" and Radio means "Radio to
interface ODU300" or "Radio LAG".
3JK Edition 2.0
1 1 59
3.6.8 Creation Dialogs
When connecting two linkable slots through a cross-connection, a dialog
will appear, close to the destination point. This dialog contains
connection information, depending on start- and end-point of
connection itself. Each cross-connection has different parameters and
required data and information will depend on ongoing cross-connecting.
Dialog boxes can ask for specific Flow Ids through a set of checkboxes,
a field to fill-in external (incoming) Flow Ids, Ethernet parameters
and so on. All the dialog boxes have a specific title describing the
building cross-connection; this states both slots numbers and types.
The Ok button will visually save the current modifications (this
means that data are graphically saved only, not sent to the NE!)
The Cancel button will graphically discard ongoing cross-connection,
keeping the previous graphical.
3JK Edition 2.0
1 1 60
3.6.9 Information Dialogs
By using the right-click button, the operator can gain information about
the graphical representation of the cross-connections. This information
can be obtained on both connectors and connection lines. The operator
can perform different actions in the area, depending on target and
mouse-click type:
Connector, right click: a dialog with information about all selected
tributaries for that connector will appear.
Line, right click: a dialog with information about selected tributaries for that
line will appear.
3JK Edition 2.0
1 1 61
3.6.10 TDM Cross-Connections
The Cross-connections to be implemented are:
PDH to Radio/MPT-ACC
Radio to Radio or MPT-ACC to MPT-ACC or Radio to MPT-ACC or MPT-ACC to
Radio
Radio/MPT-ACC to Eth
PDH to Eth
After a cross-connection has been created, two cross-connected slots
are visually linked by a line: a line in the context of this application
represents a bundle of flows, which share same source and destination
entity.
Note: In the types of cross-connections above Eth means "Ethernet User Port" or "Ethernet LAG" and Radio
means "Radio to interface ODU300" or "Radio LAG".
3JK Edition 2.0
1 1 62
3.6.10.1 PDH to Radio/MPT-ACC
By dragging a connection between a PDH slot and a Radio slot or MPT-
ACC slot, the operator will see the configuration dialog in Figure.
PDH to Radio configuration dialog
Configuration parameters will ask to specify Flow ID number, as associated in PDH slot.
3JK Edition 2.0
1 1 63
3.6.10.1 PDH to Radio/MPT-ACC [cont.]
Once correctly completed the cross-connection configuration and
clicked on OK button, the operator can see a black line describing
the PDH to Radio cross-connection defined (see Figure).
Completed PDH to Radio cross-connection
3JK Edition 2.0
1 1 64
3.6.10.2 Radio to Radio
Radio to Radio or MPT-ACC to MPT-ACC or Radio to MPT-ACC or MPT-
ACC to Radio
By dragging a connection between two different radio slots, the operator can
see the configuration dialog in Figure.
To create other cross-connections drag other lines between the two radio
slots and repeat the operations.
Radio to Radio configuration dialog
Configuration parameters will introduce Flow ID number, as coming from remote radio signal, and a
parameter related to profile and TDM Clock Source. The operator has to fill in data to complete the cross-
connection configuration. The operator can use ranges and values.
To create in one shot several cross-connections the operator can use in the Flow Id field the notation [n-
m] to create all Flow IDs from n to m, both included. If the operator wants to specify different Flow Ids
grouping them without using ranges, commas can used to separate values.
For example:
by entering in the FlowId field 10-15 in one shot will be created all the cross connections from FlowId 10
to FlowId 15 (10 and 15 included);
by entering in the FlowId field 10, 200, 250 in one shot will be created the cross connections with FlowId
10, FlowId 200 and FlowId 250.
It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], ... and so on. Based
on used input style (ranges or values), the operator will see two different confirmation dialogs.
3JK Edition 2.0
1 1 65
3.6.10.2 Radio to Radio [cont.]
clicked on OK button, the operator will see a red line describing the
Radio-Radio cross-connection defined (see Figure).
Completed Radio to Radio cross-connection
3JK Edition 2.0
1 1 66
3.6.10.3 Radio/MPT-ACC to Ethernet
By dragging a connection between a Radio slot and an Ethernet port,
the operator will see the configuration dialog in Figure.
Radio/MPT-ACC to Ethernet configuration dialog (ranges)
3JK Edition 2.0
1 1 67
3.6.10.3 Radio/MPT-ACC to Ethernet [cont.]
By using [n-m] the operator will specify adding all Flow IDs from n to m,
both included. If the operator wants to specify different Flow Ids
grouping them without using ranges, it can use commas to separate
values as shown in figure.
Radio/MPT-ACC to Ethernet configuration dialog (values)
It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], and so on. Based
3JK Edition 2.0
1 1 68
3.6.10.3 Radio/MPT-ACC to Ethernet [cont.]
clicked on OK button, the operator will see a green line describing
the Radio/MPT-ACC to Ethernet cross-connection defined).
Completed Radio/MPT-ACC to Ethernet cross-connection
3JK Edition 2.0
1 1 69
3.6.10.4 PDH to Ethernet
By dragging a connection between a PDH slot and an Ethernet port, the
operator can see the configuration dialog in Figure.
PDH to Ethernet configuration dialog
To create other cross-connections drag other lines between the PDH slot and the Ethernet port and repeat
the operations.
Configuration parameters will introduce Flow ID number, as associated in PDH slot, and all parameters
related to such Flow ID. The operator has to put the correct MAC address to complete the cross-connection
configuration.
3JK Edition 2.0
1 1 70
3.6.10.4 PDH to Ethernet [cont.]
clicked on OK button, the operator will be able to see a blue line
describing the PDH to Ethernet cross-connection defined (see Figure).
Completed PDH to Ethernet cross-connection
Considering a connection to Ethernet ports, when a port reaches its full capacity, the operator will see a
specific report.
3JK Edition 2.0
1 1 71
3.6.11 Cross-Connections with TDM2Eth Profile
No protection
1+1 radio protection between NE B and C
In these types of cross-connections the destination MAC address of the adjacent NE (unicast address in case
of unprotected configurations, multicast address in case of protected configurations) must be inserted
during the cross-connection creation. In the figures of the current and next slide 3 examples are given.
3JK Edition 2.0
1 1 72
3.6.11 Cross-Connections with TDM2Eth Profile [cont.]
1+1 EPS protection in NE A
3JK Edition 2.0
1 1 73
3.6.11 Cross-Connections with TDM2Eth Profile [cont.]
To assign the multicast MAC address
of a NE start from the unicast MAC
address and change a digit in the
first pair of digits in order to
generate an odd binary number:
example change the first pair of the
address from 00 to 01.
Note: The unicast MAC address of the NE is shown in the System Settings menu (Bridge Address).
3JK Edition 2.0
1 1 74
3.6.12 How to modify a TDM cross-connection
An existing cross-connection can be modified by double-clicking with
the left mouse button on its symbolic line.
Now from the screen you have to delete the cross-connections by
removing the check mark from the relevant Flow Id box and create
again a new cross-connections.
3JK Edition 2.0
1 1 75
3.6.12.1 PDH to Radio/MPT-ACC
In figure the operator is modifying a previously created cross-connection (in this case Slot#8 PDH and Slot#5
radio): this action brings up a dialog almost like the creation one, but with some differences in allowed
actions:
previously assigned tributaries (400 to 405 in the example) are active and selected;
tributaries assigned to another cross-connection (406 to 431) are not active and not selected.
3JK Edition 2.0
1 1 76
ACC to Radio
The operator can click on a specific (red) line in order to modify connection parameters. With a double click
with the mouse on the connection line, the dialog window shown in Figure will appear.
Remove the check mark and create again a cross-connection.
3JK Edition 2.0
1 1 77
3.6.12.3 Radio/MPT-ACC to Ethernet
The operator can click on specific (green) line in order to modify connection parameters. With a double
click with the mouse on the connection line, the dialog window shown in Figure can be managed by the
operator.
3JK Edition 2.0
1 1 78
3.6.12.4 PDH to Ethernet
The operator can click on specific (blue) line in order to modify connection parameters. With a double click
with the mouse on the connection line, the dialog window shown in Figure can be managed by the operator.
3JK Edition 2.0
1 1 79
3.6.13 SDH Cross-Connections with SDHACC
Transparent mode (ETSI market only)
SDH to Radio/MPT-ACC
Radio to Radio or MPT-ACC to MPT-ACC or Radio to MPT-ACC or MPT-ACC to
Radio
entity.
3JK Edition 2.0
1 1 80
3.6.13.1 SDH to Radio/MPT-ACC
By dragging a connection between a SDH slot and a Radio slot or MPT-
The Flow ID is automatically recognized as associated to the SDH slot.
3JK Edition 2.0
1 1 81
3.6.13.1 SDH to Radio/MPT-ACC [cont.]
clicked on "OK" button, the operator will see a black line describing the
SDH to Radio cross-connection defined .
3JK Edition 2.0
1 1 82
ACC to Radio
By dragging a connection between two different Radio slots, the operator will see the configuration dialog
in figure.
To create other cross-connections drag other lines between the two radio slots and repeat the operations.
Configuration parameters will introduce Flow ID number, as coming from remote radio signal, and the
profile. The operator has to fill in data to complete the cross-connection configuration.
3JK Edition 2.0
1 1 83
3.6.13.2 Radio to Radio [cont.]
clicked on OK button, the operator will see a red line describing the
Radio to Radio cross-connection defined.
3JK Edition 2.0
1 1 84
3.6.14 How to modify an SDH cross-conn. with SDHACC
removing the check mark from the relevant Flow ID box and create
3JK Edition 2.0
1 1 85
In Figure, the operator is modifying a previously created cross-connection (in this case Slot#8 SDH and Slot#4
MPT-ACC): this action brings up a dialog almost like the creation one, but with some differences in allowed
actions:
Previously assigned STM-1 (222 in the example) is active and selected;
In the example of the figure there is no other Flow ID and for this reason it is not possible to create
another cross-connection.
Select the Flows ID and click OK to remove the cross-connection, then click Apply.
3JK Edition 2.0
1 1 86
ACC to Radio
3JK Edition 2.0
1 1 87
3.6.15 SDH Cross-Connections with SDHCHAN
Channalized mode (ETSI market only)
SDH to Radio/MPT-ACC
PDH to SDH
entity.
3JK Edition 2.0
1 1 88
By dragging a connection between a SDH slot and a Radio slot or MPT-
3JK Edition 2.0
1 1 89
3.6.15.1 SDH to Radio/MPT-ACC [cont.]
clicked on "OK" button, the operator will see a black line describing the
SDH to Radio cross-connection defined .
3JK Edition 2.0
1 1 90
3.6.15.2 PDH to SDH
By dragging a connection between one PDH slot and one SDH, the
operator will see the configuration dialog in figure.
Select the Flow ID of the E1 in the PDH unit and the E1 of the SDH. Press the Right Arrow button.
Note: In the SDH unit only the E1 streams enabled (Unframed), but with no associated Flow Id, can be
cross-connected to a PDH unit.
3JK Edition 2.0
1 1 91
3.6.15.2 PDH to SDH [cont.]
clicked on OK button, the operator will see a black line describing
the cross-connection.
3JK Edition 2.0
1 1 92
3.6.16 How to modify an SDH cross-con. with SDHCHAN
3JK Edition 2.0
1 1 93
In Figure, the operator is modifying a previously created cross-connection (in this case Slot#8 SDH and Slot#4
MPT-ACC): this action brings up a dialog almost like the creation one, but with some differences in allowed
actions:
Deselect the Flow ID and select another Flow Id and click OK to change the cross-connection, then click
Apply.
3JK Edition 2.0
1 1 94
3.6.16.2 PDH to SDH
The operator can click on a specific line in order to modify connection
parameters. With a double click with the mouse on the connection line,
the dialog window shown in figure will appear.
Select the cross-connection on the right-side field, click on the Left Arrow button, click OK, then click on
Apply.
3JK Edition 2.0
1 1 95
3.6.17 ATM Cross-Connections (ETSI market only)
ASAP-Radio
Radio-Radio
Radio-Eth
ASAP-Eth
In the types of cross-connections above Eth means "Ethernet User Port"
or "Ethernet LAG" and Radio means "Radio to interface ODU300" or
"Radio LAG".
entity.
3JK Edition 2.0
1 1 96
3.6.17.1 ASAP Radio
By dragging a connection between an ASAP slot and a radio slot, the
operator will see the configuration dialog (ODU300) in Figure.
Configuration parameters will ask to:
select the ATM interface (this interface is the IMA group: from 1 to 8)
select the PW label
enter the VPI
assign the VLAN ID
enter the Destination MAC Address (only with MPT-HC or MPT-MC)
Note: The Traffic Descriptor is automatically created.
Note: ATM "Light" Cross-connection Provisioning
In this release when a cross-connection toward a radio direction with MPT is involved, the related
provisioning is performed in almost the same way as with ODU300, with the following main differences:
MAC DA is also explicitly provisioned in the NE acting as TPE role
admission control, in terms of checking bandwidth required bt ATM PW flow against the available
bandwidth on radio interface, is never performed.
3JK Edition 2.0
1 1 97
3.6.17.1 ASAP Radio [cont.]
By dragging a connection between an ASAP slot and a radio slot, the
operator will see the configuration dialog (MPT-HC or MPT-MC) in
Figure.
3JK Edition 2.0
1 1 98
3.6.17.1 ASAP Radio [cont.]
clicked on OK button, the operator will see a black line describing
the ASAP-radio cross-connection defined (see Figure).
3JK Edition 2.0
1 1 99
3.6.17.2 Radio Radio
The ATM Radio-Radio Cross-connections can be implemented between
ODU300-ODU300, MPT-MPT but not between ODU300-MPT.
By dragging a connection between two different radio slots, the
operator will see the configuration dialog in Figure.
To create other cross-connections drag other lines between the two
radio slots and repeat the operations.
3JK Edition 2.0
1 1 100
3.6.17.2 Radio Radio [cont.]
The operator has to fill in data to complete the cross-connection
configuration.
Configuration parameters are:
select the Service: ATM or PW3
select the PW label
assign the VLAN ID
associate the Traffic Descriptor by clicking on Browse and selecting a Traffic Descriptor previously
created.
Note: an ATM PW is made up of two undirectional flows.
3JK Edition 2.0
1 1 101
3.6.17.2 Radio Radio [cont.]
3JK Edition 2.0
1 1 102
3.6.17.3 Radio Ethernet
By dragging a connection between a Radio slot and an Ethernet port,
select the Service: ATM or PW3
select the PW label
assign the VLAN ID
enter the Destination MAC address
associate the Traffic Descriptor by clicking on Browse and selecting a Traffic Descriptor previously
created.
Note: an ATM PW is made up of two undirectional flows.
3JK Edition 2.0
1 1 103
3.6.17.3 Radio Ethernet [cont.]
the Radio-Ethernet cross-connection defined.
3JK Edition 2.0
1 1 104
3.6.17.4 ASAP Ethernet
By dragging a connection between an ASAP slot and an Ethernet port,
To create other cross-connections drag other lines between the ASAP
slot and the Ethernet port and repeat the operations.
select the ATM interface
select the PW label
enter the VPI
assign the VLAN ID
enter the Destination MAC address
Note: The Traffic Descriptor is automatically created.
The operator has to put the correct Destination MAC address to complete the cross-connection
configuration.
3JK Edition 2.0
1 1 105
3.6.17.4 ASAP Ethernet [cont.]
clicked on OK button, the operator will be able to see a green line
describing the ASAP-Ethernet cross-connection defined (see Figure).
specific report.
3JK Edition 2.0
1 1 106
3.6.18 How to modify an ATM cross-connection
removing the check mark from the relevant Flow Id box and create
3JK Edition 2.0
1 1 107
3.6.18.1 ASAP - Radio
In Figure the operator is modifying a previously created cross-connection: this action brings up a dialog
almost like the creation one:
Previously assigned tributaries (111 in the example) are active and selected;
Tributaries assigned to another cross-connection are not active and not selected.
Select the ATM interface and remove the check mark and create again a cross-connection.
3JK Edition 2.0
1 1 108
3.6.18.2 Radio - Radio
Select the ATM Service and remove the check mark and create again a cross-connection.
3JK Edition 2.0
1 1 109
3.6.18.3 Radio - Ethernet
The operator can click on specific (green) line in order to modify connection parameters. With a double
click with the mouse on the connection line, the dialog window shown in Figure can be managed by the
operator.
Select the ATM Service and remove the check mark and create again a cross-connection.
3JK Edition 2.0
1 1 110
3.6.18.4 ASAP - Ethernet
The operator can click on specific (blue) line in order to modify connection parameters. With a double click
with the mouse on the connection line, the dialog window shown in Figure can be managed by the operator.
Select the ATM interface and remove the check mark and create again a cross-connection.
3JK Edition 2.0
1 1 111
3.6.19 LAG-LAG Cross-Connections
Two types of cross-connections can be implemented:
Ethernet LAG - Radio LAG cross-connections
Radio LAG - Radio LAG cross-connections
3JK Edition 2.0
1 1 112
3.6.19.1 Ethernet LAG - Radio LAG cross-conn.
By dragging a connection between a Radio LAG icon and an Ethernet
LAG icon, the operator will see the configuration dialog in Figure.
Configuration parameters will introduce the Service (TDM or ATM), Flow ID number and all parameters
related to such Flow ID. The operator has to put the correct MAC address to complete the cross-connection
configuration.
3JK Edition 2.0
1 1 113
3.6.19.1 Ethernet LAG - Radio LAG cross-conn. [cont.]
clicked on OK button, the operator will be able to see a green line
describing the Radio LAG to Ethernet LAG cross-connection defined.
To create other cross-connections drag other lines between the Radio LAG and the Ethernet LAG and repeat
the operations.
3JK Edition 2.0
1 1 114
3.6.19.2 Radio LAG - Radio LAG cross-conn.
By dragging a connection between two different Radio LAG icons, the
operator will see the configuration dialog in Figure.
Configuration parameters will introduce the Service (TDM or ATM), Flow ID number, as coming from remote
radio signal, and a parameter related to profile and TDM Clock Source. The operator has to fill in data to
complete the cross-connection configuration. The operator can use ranges and values.
To create in one shot several cross-connections the operator can use in the Flow ID field the notation [n-m]
to create all Flow IDs from n to m, both included. If the operator wants to specify different Flow IDs
grouping them without using ranges, commas can used to separate values.
For example:
by entering in the FlowId field 10-15 in one shot will be created all the cross connections from FlowId 10
to FlowId 15 (10 and 15 included);
by entering in the FlowId field 10, 200, 250 in one shot will be created the cross connections with FlowId
10, FlowId 200 and FlowId 250.
It is not possible to merge the two solutions (ranges and values) by writing [n-m],[a-b], ... and so on. Based
3JK Edition 2.0
1 1 115
3.6.19.2 Radio LAG - Radio LAG cross-conn. [cont.]
the Radio LAG to Radio LAG cross-connection defined .
3JK Edition 2.0
1 1 116
3.6.20 How to modify a LAG-LAG cross-connection
3JK Edition 2.0
1 1 117
3.6.20.1 Ethernet LAG to Radio LAG
In Figure, the operator is modifying a previously created cross-connection (in this case Radio LAG #2 SDH
and Ethernet LAG #24): this action brings up a dialog almost like the creation one, but with some
differences in allowed actions:
Previously assigned Flow ID (654 in the example) is active and selected;
In the example of the figure there is no other Flow ID and for this reason it is not possible to create
another cross-connection.
Select the Service and the Flows ID and click OK to remove the cross-connection, then click Apply.
3JK Edition 2.0
1 1 118
3.6.20.2 Radio LAG to Radio LAG
The operator can click on a specific (red) line in order to modify
connection parameters. With a double click with the mouse on the
connection line, the dialog window shown in Figure will appear.
Previously assigned Flow ID (654 in the example) is active and selected;
In the example of the figure there is no other Flow ID and for this reason it is not possible to create another
cross-connection.
Select the Service and the Flows ID and click OK to remove the cross-connection, then click Apply.
3JK Edition 2.0
1 1 119
3.6.21 Ring Cross-Connections
PDH - Ring cross-connections
Radio - Ring cross-connections
Ethernet - Ring cross-connections
Pass-through cross-connections
Warning: After the Ring cross-connection creation enable the ERP in the Ring menu (click on the Ring icon
in the Tool bar).
3JK Edition 2.0
1 1 120
3.6.21.1 PDH - Ring
By dragging a connection between a PDH slot and the Ring icon, the
Configuration parameters will ask to select the instance and to select Flow ID number, as associated in PDH
slot.
3JK Edition 2.0
1 1 121
3.6.21.1 PDH - Ring [cont.]
clicked on OK button, the operator will see a cyan line describing the
PDH to Radio cross-connection defined (see Figure).
3JK Edition 2.0
1 1 122
3.6.21.2 Radio Ring
By dragging a connection between a Radio slot and the Ring icon, the
Configuration parameters are the Ring Instance, VLAN (multiple selection can be done), Service Profile and
TDM Clock Source (if the Profile in TDM2Eth). The operator has to fill in data to complete the cross-
connection configuration and click on the Right Arrow button.
3JK Edition 2.0
1 1 123
3.6.21.2 Radio Ring [cont.]
The screen in figure will appear.
3JK Edition 2.0
1 1 124
3.6.21.2 Radio Ring [cont.]
cross-connection.
3JK Edition 2.0
1 1 125
3.6.21.3 Ethernet - Ring
By dragging a connection between an Ethernet port and the Ring icon,
Configuration parameters are the Ring Instance, VLAN (multiple selection can be done), Service Profile, TDM
Clock Source (if the Profile in TDM2Eth) and the destination MAC Address. The operator has to fill in data to
complete the cross-connection configuration and click on the Right Arrow button.
3JK Edition 2.0
1 1 126
3.6.21.3 Ethernet - Ring [cont.]
3JK Edition 2.0
1 1 127
3.6.21.3 Ethernet - Ring [cont.]
clicked on OK button, the operator will be able to see a cyan line
describing the cross-connection.
specific report.
3JK Edition 2.0
1 1 128
3.6.21.4 Pass-through
By clicking on the Ring icon, the operator will see the configuration
dialog in Figure.
Configuration parameters are the Ring Instance, VLAN (multiple selection can be done), Service Profile and
TDM Clock Source (if the profile is TDM2Eth). The operator has to fill in data to complete the cross-
connection configuration and click on the Right Arrow button.
3JK Edition 2.0
1 1 129
3.6.21.4 Pass-through [cont.]
3JK Edition 2.0
1 1 130
3.6.21.4 Pass-through [cont.]
cross-connection (see Figure).
3JK Edition 2.0
1 1 131
3.6.22 How to modify a Ring cross-connection
3JK Edition 2.0
1 1 132
3.6.22.1 PDH - Ring
In Figure, the operator is modifying a previously created cross-connection (in this case Slot#3 PDH and
Radio): this action brings up a dialog almost like the creation one, but with some differences in allowed
actions:
Deselect the Flow Id and select another one. Click OK and Apply.
3JK Edition 2.0
1 1 133
3.6.22.2 Radio - Ring
The operator can click on a specific line in order to modify connection parameters. With a double click with
the mouse on the connection line, the dialog window shown in Figure will appear.
Select the cross-connected VLANs in the right-side field and click on the Left Arrow arrow. Change the
Instance, if required, then select another VLAN and click the Right Arrow button. Click on OK and Apply.
3JK Edition 2.0
1 1 134
3.6.22.3 Ethernet - Ring
The operator can click on a specific line in order to modify connection parameters. With a double click with
the mouse on the connection line, the dialog window shown in Figure will appear.
3JK Edition 2.0
1 1 135
3.6.22.4 Pass-through
The operator can click on specific line in order to modify connection parameters. With a double click with
the mouse on the connection line, the dialog window shown in Figure can be managed by the operator.
3JK Edition 2.0
1 1 136
3.7 Menu AUX Cross Connections
Two types of AUX Cross-Connections can be implemented:
Local User Service Channel Cross-Connection
Service Channels Cross-connection in pass-through
Note: Cross-Connection towards MPT
In this release cross-connection of Service Channels towards a radio direction with MPT is not supported.
The operator therefore will not have the possibility to select a radio direction with MPT for such cross-
connection.
3JK Edition 2.0
1 1 137
3.7.1 Local User Service Channel Cross-connection
The two local user 64 kbit/s Service Channels on the AUX peripheral
unit can be cross-connected to one radio link with one of the three
available radio Service Channels.
Note:
Before disabling a local user Service Channel interface, all Service Channel cross-connections involving
this interface must be removed.
Before disabling an Auxiliary or Radio peripheral, any Service Channel cross-connections involving this
peripheral must be removed.
3JK Edition 2.0
1 1 138
3.7.2 Service Channels Cross-connect. in pass-through
Independently of the presence of the Auxiliary peripheral unit, it is
always possible to cross-connect each individual radio Service Channel
with a radio Service Channel of another radio direction, without any
local termination.
3JK Edition 2.0
1 1 139
3.7.3 How to create an AUX cross-connection
1. Select in the New Cross-Connection area the firt Termination Point (this can be a local service channel or
a service channel in a radio link).
2. Select the second Termination Point as shown in the example in the figure.
Note: The cross-connections are bi-directional.
3. Click on Add. The new cross-connection will appear in the list (upper part of the screen as shown in the
next figure).
Note: Button Apply has not been implemented.
3JK Edition 2.0
1 1 140
3.7.3 How to create an AUX cross-connection [cont.]
3JK Edition 2.0
1 1 141
3.7.4 How to delete an AUX Cross Connection
1. Select the Cross-Connection to be deleted from the list (as shown in the figure).
2. Click on Delete.
Note: The multiple deletion of the Cross-Connection is not possible.
Note: Button Apply has not been implemented.
3JK Edition 2.0
1 1 142
3.8 Menu XPIC Configuration
Two XPIC Configurations can be implemented:
1+0 XPIC
1+1 XPIC
The 1+1 XPIC Configuration consists of two groups of 1+ HSB with different polarization.
The XPIC Configuration menu opens by clicking on the relevant button on the Tool bar.
In the XPIC Configuration will appear in GREEN only the MPT-HC V2 with a mask with XPIC (1+0 or 1+1 HSB,
no Adaptive Modulation, no ATPC, 128 or 256 QAM, 28 or 56 MHz) previously configured in the Radio menu
and with a suitable polarization (vertical or horizontal) as shown in the following figure.
3JK Edition 2.0
1 1 143
3.8 Menu XPIC Configuration [cont.]
3JK Edition 2.0
1 1 144
3.8.1 1+0 XPIC
To configure the 1+0 XPIC, drag with the mouse from an MPT icon to
another MPT icon. The two MPT must have different polarization.
Put a check mark and click on OK.
Click on Apply.
3JK Edition 2.0
1 1 145
3.8.1 1+0 XPIC [cont.]
The following screen shows the two MPT-HC V2 associated in the XPIC
Configuration.
3JK Edition 2.0
1 1 146
3.8.1 1+0 XPIC [cont.]
Now if you go in the Radio menu in the Associated Interface field will appear the radio channel associated in
the XPIC configuration, as shown in the figure. If click on the icon of the Associated Interface you navigate
on the associated radio channel.
3JK Edition 2.0
1 1 147
3.8.2 1+1 XPIC
To configure the 1+1 XPIC, drag with the mouse from the icon of the
Main of one 1+1 HSB to the Main of another 1+1 HSB. The 1+1 HSB
groups must have different polarization.
Put a check mark and click on OK.
Click on Apply.
3JK Edition 2.0
1 1 148
3.8.2 1+1 XPIC [cont.]
The following screen shows the two MPT-HC V2 associated in the XPIC
Configuration.
3JK Edition 2.0
1 1 149
3.8.3 How to remove the XPIC association
To remove the association double click on the connection line, remove
the check mark, click on OK and Apply.
3JK Edition 2.0
1 1 150
3.9 Menu VLAN Configuration
Two different ways to manage the Ethernet traffic are allowed:
802.1D (MAC Address Bridge)
802.1Q (Virtual Bridge)
3JK Edition 2.0
1 1 151
3.9.1 802.1D
When the NE is configured in this mode (default configuration), the Ethernet traffic is switched according to
the destination MAC address without looking the VLAN.
The packets from the user Ethernet ports having the VLAN ID out the allowed range (0 and 2-4080) are
dropped. The packets having a VLAN ID already used for a TDM flow are accepted.
3JK Edition 2.0
1 1 152
3.9.2 802.1Q
When the NE is configured in this mode, the management of Ethernet traffic looking the VLAN is enabled.
In this modality, one VLAN will be assigned to all Ethernet frames inside the MPR network.
WARNING: The VLAN ID values configurable must be in the range 2 - 4080. The VLAN IDs already defined to
cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot be used. The management system prohibits
the definition of VLAN ID already used. The VLAN ID must be different also from the Flow Id associated to E1
tributaries not yet cross connected
3JK Edition 2.0
1 1 153
3.9.2 802.1Q [cont.]
Note on LAG: if a Radio LAG or an Ethernet LAG has been created, they will appear in the VLAN
management, as shown in the next figure.
3JK Edition 2.0
1 1 154
3.9.2 802.1Q
3.9.2.1 VLAN 1 Management
VLAN-ID 1 is automatically defined by the NE when the 802.1Q bridge
type is selected.
VLAN-ID 1 is shown to the operator, but it cannot be neither changed
nor deleted.
All the user Ethernet ports (enabled and disabled) and all the radio
ports are members of the VLAN 1.
In egress VLAN-ID 1 is always removed from all the ports.
New: to create a new VLAN (refer to VLAN table management)
Edit: to change the parameters of a VLAN (VLAN name, VLAN member ports, VLAN untagged ports in egress).
Delete: to delete a VLAN-ID. It is possible to remove a VLAN-ID from the VLAN-ID table even if this VLAN-ID
has been already configured on one or more user ports as Port VLAN to be added in ingress to untagged
frames. As consequence, the VLAN-ID=1 and PRI=0 are added to the untagged frames received on this port.
Before applying this deletion, a confirmation of the operation is shown to the operator.
Export: to export the VLAN configuration in a file with extension CSV. The file can be stored in the PC to be
read later.
Filter: by inserting a name in the "Filter by Name" box and by clicking on Filter will be displayed in the
table only the VLAN, which name corresponds (totally or partially) to the name written in the "Filter by
Name" box.
Clear Filter: by clicking this button all the VLAN created in VLAN table will again appear.
Refresh: the VLAN table is updated.
3JK Edition 2.0
1 1 155
3.9.2 802.1Q
3.9.2.2 VLAN Table Management
To create a VLAN follow the following instructions.
1) VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 - 4080)
N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) cannot be
used.
2) VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.
N.B.: There is no check on unambiguity name.
3) VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant check
box. All the user Ethernet ports and all the Radio directions can be considered. Both enabled and disabled
user Ethernet ports (radio ports when declared are implicitly enabled) can be member of a VLAN. This
means that a disabled port can be configured as a member of a VLAN and a port already member of a VLAN
can be disabled continuing to be a member of the same VLAN.
4) Untagged Ports field: Select, among the ports belonging to this VLAN (members), the untagged ports (in
egress the VLAN will be removed from the frames). Only the user Ethernet ports, enabled and disabled, are
manageable. The VLAN cannot be removed from the radio ports (with the exception of the VLAN 1).
N.B.: The VLAN-ID values allowed are in the range 2 - 4080. By default, for the VLAN IDs defined, all the
ports are members and the Untag flag is set to False, which means all the frames are transmitted with
Tag.
N.B.: Tagged frames
If one tagged packet with VLAN-ID X is received on a port which is not member of the VLAN-ID X, the packet
is dropped.
3JK Edition 2.0
1 1 156
3.9.2 802.1Q
3.9.2.2 VLAN Table Management [cont.]
In the following figure, as example, three VLANs have been created
(VLAN 2, 3 and 4).
3JK Edition 2.0
1 1 157
3.9.3 Ethernet Ring
If an Ethernet Ring has been created, the VLAN ID of the R-APS relevant to the ERP Instances must be
inserted in the VLAN Configuration as shown in the figure.
3JK Edition 2.0
1 1 158
3.10 Menu Traffic Descriptors
This menu allows to create or to delete the traffic descriptors, that will
be associated to the ATM traffic at the ingress and/or at the egress.
3JK Edition 2.0
1 1 159
3.10 Menu Traffic Descriptors [cont.]
To create a Traffic Descriptor:
1. Select the domain: ATM (if in the NE the ASAP unit is present) or PWE3 (in the
repeater nodes or in the nodes, where an Ethernet termination is present)
2. Insert a label to identify the Traffic Descriptor
3. Configure the following parameters:
Service Category: CBR, UBR+ or UBR (rtVBR and nrtVBR are not managed)
Conformance Definition: CBR.1 (VBR.1, VBR.2, VBR.3 are not maneged)
4. Configure the following TD Parameters: PCR, CDVT, MDCR
5. Enable or disable the Policing. For each VP/VC it is possible to enable/disable a cell-
based ATM Policing, based on the related ingress ATM Traffic Descriptor. The default
configuration of ATM Policing is according to configured Service Category:
enabled for VP/VC having Service Category CBR;
disabled for VP/VC having Service Category UBR+ and UBR.
6. Click on Create
7. The already created Traffic Descriptor will appear in the List Traffic Descriptors
area.
To delete a Traffic Descriptor:
1. Select in the List Traffic Descriptors area the Traffic Descriptor to be deleted and
click on Delete.
Note: By clicking on Refresh the list of the Traffic Descriptors will be updated.
Note: The maximum number of ATM Traffic Descriptors configurable on a NE is given by 2 times the max
number of configurable VPs multiplied by max number of ASAP Cards that can be hosted: 2 (2 traffic
Descriptors per circuit) x 128 (128 circuits max.) x 6 (6 ASAP units in the NE max.).
3JK Edition 2.0
1 1 160
3.10 Menu Traffic Descriptors [cont.]
The types of ATM Traffic Contract (that is the Service Category/
Conformance Definition pair) to be supported by MPR system and its
relation with Traffic Descriptor parameters is reported in the table
below.
(CLP=0+1) (CLP=0+1)
MDCR = 0 CDVT PCR atmClpTransparentNoScr CBR.1 ubr
(CLP=0+1) (CLP=0+1)
MDCR > 0 CDVT PCR atmClpTransparentNoScr CBR.1 ubr+
(CLP=0+1)
- CDVT PCR atmClpTransparentNoScr CBR.1 cbr
Traffic
Descr
Param3
Traffic
Descr
Param2
Traffic
Descr
Param1
Traffic Descr Type Conform
Def.
Service
Category
Notes:
1. UBR+ Service Category is defined as an UBR Service Category with Traffic Descriptor Parameter 3 (MDCR)
> 0
2. ATM Traffic Descriptor Parameters for VP/VC rates (PCR,SCR) are defined in terms of cell/second, for
CDVT the unit is microseconds, for MBS the unit is cells
3. Range for ATM Traffic Descriptor Parameters with VP/VC rates is 0 to the bandwidth of related physical
or logical ATM interface, range for CDVT is 0 to 40000 microseconds, range for MBS is 0 to 1000 cells.
3JK Edition 2.0
1 1 161
3.11 Menu Profile Management
After the Start Supervision, each time the operator performs the Show
Equipment action, the following Dialog screen is displayed after the
window with JUSM start-up message and before the window with
loading bar indicating JUSM start-up progress.
The operator has to insert the user name and related password: by
clicking on the Apply button, the parameters are sent to NE.
The default Operator Name is initial.
The default Password is adminadmin.
According to the operator authentication (correct couple username/password) managed by the NE, the
operator will be authorized or not to continue. If the login parameters are not correct, an error message
will be displayed, while the Login window is still open for a new attempt. After 3 consecutive failed
attempts the login procedure is closed and JUSM does not start.
On the contrary if the user name and password are correct, JUSM will be started and the operator will be
allowed to perform the actions according to the right related to his profile.
WARNING: The NE rejects usernames and passwords that do not meet the following rules:
Password length: the length must be not less than eight (8) characters. Moreover the password length
must be not longer than 20 characters.
The existing passwords less than eight characters (e.g., 6 or 7 characters), created with older software
versions, are accepted and maintained.
Password composition: the password can include full ASCII characters set (UPPER/lower case, numeric
and special characters).
Username length: the length must be not longer than 20 characters.
By clicking on the Cancel button, the login procedure is stopped and the JUSM does not start.
3JK Edition 2.0
1 1 162
3.11.1 User Profiles Management
If the operator right allows the profiles management, the operator can
perform some actions on the profiles.
Under Configuration menu, the Profiles Management menu displays
two items:
Users Management
Change Password
These items will be enabled according to the right of user profile
recognised at login.
3JK Edition 2.0
1 1 163
3.11.2 User Management
By clicking on Users Management the window displayed in the Figure
appears.
The operator can perform the following actions:
Create a new User by clicking on the Create button.
After the selection of a user in the table, its possible:
Delete an existing User (the Admin user cannot be deleted) by clicking on the
Delete button.
Change PW (by Administrator) by clicking on the Change PW button.
By clicking on the Cancel button the Profiles Management window closes.
By clicking on the Help button the help browser will display the help-on-line pages dedicated to this
function.
3JK Edition 2.0
1 1 164
3.11.3 How to Create a New User
By clicking on the Create button, the following window appears and
allows the user Administrator to create a new user.
3JK Edition 2.0
1 1 165
3.11.3 How to Create a New User [cont.]
The operator has to insert the parameters to define the new user and
his profile rights:
1. AdminPassword: the password of Administrator for confirmation and
validation.
2. UserName: the specific name to be assigned to the new User (if it exists,
the action will be failed).
3. Profile: the specific profile to be assigned to the new User.
4. Password: the specific password to be assigned to the new User.
5. Confirm Password: again the specific password to be assigned for
confirmation and validation.
The supported profiles are:
Administrator: full access also for security parameters
Operator: person in charge to operate at network level, not at radio side; dangerous operations that require NE reconfiguration at
radio site are not permitted including backup/restore and restart NE features; could change own password
CraftPerson: person in charge for installation and the maintenance at radio site; full access to NE but not for security parameters,
only for own password
Viewer: only to explore the NE
Supported operations by the profiles:
Administrator profile: All the NE parameters are accessible both in writing and reading mode. Also the management of user accounts
is allowed (create/delete user accounts and change of all passwords).
Operator profile: Full reading access to NE parameters. For writing mode the following parameters are allowed to change:
ATPC configuration (enabled, disabled)
Performance Monitoring management
start/stop CD
threshold tables configuration
reset
archiving (only for NMS system)
Supported for all the types of Performance Monitoring (Radio Hop/Link, E1, Received Power Levels, ....)
NTP protocol:
Enabled/Disabled
NTP main server address configuration
NTP spare server address configuration
CraftPerson profile: This operator has the same priviledges of the Administrator, but cannot manage the user accounts
Viewer profile: This operator can only read and can change his own password.
By clicking on Apply button, at first JUSM performs a syntax check of each field: if there are some errors, JUSM will display the specific
message and allows the operator to correct them. If all parameters are correct, all parameters are sent to NE; after to have
automatically closed the window, a message with result of the action will be displayed.
By clicking on Cancel button, the Create User window closes and no action will be performed.
3JK Edition 2.0
1 1 166
3.11.4 How to Delete a User
After the selection of a User in the Profile Table, by clicking on the
Delete button, at first a confirmation dialog (Figure Delete user
confirmation) will be displayed; then the window to confirm the
administrator password will be displayed (Figure Confirm
Administrator Password to Delete a User).
Delete user confirmation Confirm Administrator Password
to Delete a User
By clicking on the Apply button, a message with the result action will be displayed after to have closed
automatically the window above.
If the operator clicks on Cancel button the window will closes and no action is performed.
3JK Edition 2.0
1 1 167
3.11.5 Change the Password (by the Administrator)
The Administrator User can change the password of another user: select
the user in the Profile Table and then click on Change PW button. The
following dialog box is displayed:
Change Password of User by Admin
The admin has to insert his password and the new password for
selected user in the two text fields.
By clicking on Apply button, at first JUSM performs a syntax check of each field: if there are some errors,
JUSM will display the specific message and allows the operator to correct them. If all parameters are
correct, all parameters are sent to NE; after to have automatically closed the window, a message with
result of the action will be displayed.
By clicking on Cancel button, the window will be closed.
3JK Edition 2.0
1 1 168
3.11.6 Change Password (by the User)
If the operator wants to change his password, he has to select the
Change Password menu item.
The following dialog will be displayed:
Change User Password
The operator has to insert the current password and the new password
in the two text fields.
By clicking on Apply button, at first JUSM performs a syntax check of each field: if there are some errors,
JUSM will display the specific message and allows the operator to correct them. If all parameters are
correct, all parameters will be sent to NE; after to have automatically closed the window, a message with
result of the action will be displayed.
By clicking on Cancel button, the window closes.
3JK Edition 2.0
1 1 169
3.12 Ethernet Features Shell
The LAG can be created by CLI commands launched with the WebEML
from the menu Configuration > Ethernet Features Shell.
3JK Edition 2.0
1 1 170
3.12.1 Simple examples for LAG creation
Here below two examples of the CLI commands useful to create LAG.
Example 1 : Ethernet LAG with Ethernet User port 1 and 2
1. Create the LAG with index 1, Ethernet type, size 2 (2 user ports: max
allowed number) called mario
lag 1 create type ethernet name mario size 2
2. Add User port 1 of the Core unit (slot 1) with priority 128 (128 means that
the two ports have the same priority)
lag 1 port add 1/1 priority 128
3. Add User port 2 of the Core unit (slot 1) with priority 128
4. Enable the LAG
lag 1 enable true
In bold characters the keywords, in italic characters the variables.
N.B.: When from the WebEML is launched the CLI, the WebEML closes.
Note 1: To know if an MPT is grouped in a radio LAG, letter L is placed on the MPT icon on the Equipment
view, but in this view it not possible to see the association of a specific MPT to a specific Radio LAG.
Note 2: To know if an Ethernet user port is grouped in an Ethernet LAG, in the CORE-E domain in the
Ethernet Physical Interface tab-panel the Settings tab-panel of the Ethernet port grouped in a LAG is gray
(no changes can be done), but it not possible to see the association of a specific User Ethernet port to a
specific Ethernet LAG.
3JK Edition 2.0
1 1 171
3.12.1 Simple examples for LAG creation [cont.]
Example 2: Radio LAG between port 1 on MPACC in slot 3 and port
2 on MPTACC in slot 4
1. Create the LAG with index 5, Radio type, size 2 (2 radio ports: max allowed
number), called paolo
lag 5 create type radio name paolo size 2
2. Add port 1 of the MPTACC in slot 3 with priority 128
3. Add port 2 of the MPTACC in slot 4 with priority 128
4. Enable the LAG
lag 5 enable true
In bold characters the keywords, in italic characters the variables.
N.B.: When from the WebEML is launched the CLI, the WebEML closes.
Note 1: To know if an MPT is grouped in a radio LAG, letter L is placed on the MPT icon on the Equipment
view, but in this view it not possible to see the association of a specific MPT to a specific Radio LAG.
Note 2: To know if an Ethernet user port is grouped in an Ethernet LAG, in the CORE-E domain in the
Ethernet Physical Interface tab-panel the Settings tab-panel of the Ethernet port grouped in a LAG is gray
(no changes can be done), but it not possible to see the association of a specific User Ethernet port to a
specific Ethernet LAG.
3JK Edition 2.0
1 1 172
Blank Page
3JK Edition 2.0
1 1 173
4 Menu Diagnosis
3JK Edition 2.0
1 1 174
4 Menu Diagnosis
4.1 Menu Diagnosis
Menu Diagnosis is divided in:
Alarms
Log Browsing
Remote Inventory
Abnormal Condition List
Summary Block Diagram View
Current Configuration View
Performance Monitoring
3JK Edition 2.0
1 1 175
4 Menu Diagnosis
4.2 Alarms
Alarms Monitor is an application which allows to display and store the alarms of all the NEs requiring it.
Alarms Monitor can be also started by clicking on the Alarms Monitor button on NEtO.
3JK Edition 2.0
1 1 176
4 Menu Diagnosis
4.2 Alarms [cont.]
On the left side of the application, below each NE, two global lists of
alarms are displayed:
CURRENT_ALARM shows all the equipment alarms currently present,
ALARM_LOG shows all the equipment alarms currently present and the
history of the alarms (i.e. cleared alarms).
Each global list has some default filters (5 filters for the
CURRENT_ALARM list and 8 filters for the ALARM_LOG list), as follows:
1) CRI contains all the alarms having a CRITICAL severity
2) MAJ contains all the alarms having a MAJOR severity
3) MIN contains all the alarms having a MINOR severity
4) WRG contains all the alarms having a WARNING severity
5) IND contains all the alarms having an INDETERMINATE severity
6) CLR contains all the alarms which are in the CLEARED state, that is, which
are no longer active (this filter is available within the list ALARM_LOG only).
For each list and for each filter, the number of active alarms is shown
inside brackets.
These two lists can be filtered using customized filters provided by
means of the menu Filters Add a Filter.
Note: When an alarm is no longer active it disappears from the current Global list and it is displayed in the
ALARM_LOG list as a cleared alarm.
3JK Edition 2.0
1 1 177
4 Menu Diagnosis
4.2 Alarms [cont.]
Single clicking on a filter or on a global list on the left part of the
screen shows up on the right side the relevant tab panel with all the
alarms.
At the top right, the field Synthesis shows the number of active alarms
for any severity.
The alarms have a different color according to their severity and their
state.
Red: CRITICAL alarm
Brown: MAJOR alarm
Yellow: MINOR alarm
Blue: WARNIG alarm
White: INDETERMINATE alarm (Note that the equipment has no alarm having
such severity)
Green: CLEARED alarm (alarm no longer active).
Note: when the application is opened for the first time, only the tab-panels of the two global lists are
displayed on the right part of the window.
3JK Edition 2.0
1 1 178
4 Menu Diagnosis
4.2 Alarms [cont.]
Within the tab-panel, each alarm is provided with the information
below.
Time & Date: date and time of the alarm. The format of date and time is
yyyy/mm/dd hh:mm:ss.
Probable cause: name of the probable cause of the alarm.
Alarm Type: alarm class (TRS = Transmission Alarm alarm not created inside
the equipment, but generated by a connected equipment or due to
transmission/propagation problems; EQUIPMENT: inside alarm of the
equipment).
Friendly Name: object of the equipment where the alarm occurred.
Severity: alarm severity.
Add Text: this is an additional text regarding the alarm.
Specific problem: for some alarms, additional information is provided about
the involved resource (for instance, when a threshold alarm is raised, it
states the specific threshold exceeded)
3JK Edition 2.0
1 1 179
4 Menu Diagnosis
4.2 Alarms [cont.]
Right-clicking on an alarm row opens the menu shown in the following
figure.
Navigate to USM: to navigate to the object involved with the selected alarm and to open the relevant
window. Note: this option is available in the CURRENT_ALARM global list and in the relevant filters only.
Export Alarm: to create a file containing alarms data. Alarms have to be selected by means of the menu
Select All. Generated file formats are CSV, HTML, XML and PDF.
Print current view: it is possible to print the list of the alarms. The Print Dialog box is shown to choose
the printer and set Print range and Copies number.
Select All: to select all the alarm of the list for further use, e.g. to export alarms to a file.
Select None: to select no alarm.
3JK Edition 2.0
1 1 180
4 Menu Diagnosis
4.2 Alarms [cont.]
The Menu Bar provides the following menus:
File
Filters
Help
3JK Edition 2.0
1 1 181
4.2 Alarms
4.2.1 File Menu
Save Log for selected NE
This menu allows to save a file with one of the two global lists of each NE.
Select the global list of a specific NE, open the Save History menu for the
selected NE and enter filename and relevant directory in the opening
window.
Load Log to selected NE
By means of this menu it is possible to display the global list of a certain NE
previously saved.
Remove selected NE
By means of this menu an NE, selected in the list, can be removed.
Export Alarms
This menu allows to save a file with the alarms of the selected Log. Select
the log, select "Export Alarms" menu, choose the file format (CSV, HTML, HML
or PDF) and then assign the name of the file.
3JK Edition 2.0
1 1 182
4.2 Alarms
4.2.2 Filters Menu
The Menu Filters provides the following menus:
Close Filter
Add a Filter
Edit Selected Filter
Delete Selected Filter
Delete Filters
Save Filters As
Load Filters From
3JK Edition 2.0
1 1 183
4.2.2 Filters Menu
4.2.2.1 Close Filter ...
The Filter, currently open, is closed.
3JK Edition 2.0
1 1 184
4.2.2 Filters Menu
4.2.2.2 Add a Filter
This menus allows to create customized logs adding some new specific
filters. The windows which opens is shown below.
Filter Name field
Enter the filter name in the Filter Name field.
The filters can be created selecting one of the following fields (or more). To save the created filter click on the Done
pushbutton. (Clicking on the Cancel pushbutton clears the filter configuration). The created filter appears on the left
side of the application.
Scope field
Select APT (Current) to create a filter showing the current alarms only or select Log to create a filter for current and
cleared alarms.
The filter can be applied to all the NEs by selecting All or it can be applied to one or more NEs by selecting one or
more NEs using the mouse.
Alarm Type field
Select Alarm Type to create a filter for the selected type of alarm:
TRS = Transmission Alarm
EQUIPMENT = Equipment alarm
Perceived severity field
Select Perceived severity and then one or more severity levels and/or Cleared state to filter the alarm having the
selected severity levels.
Event Time field
Select Event Time and then enter the starting date (From) and the ending date (To) to filter the alarms created
during that specific time frame only.
Probable Cause field
Select Probable Cause and the choose a specific alarm (one or more) to filter these particular alarms only.
Resource field
Put a check mark on the Resource box and write the object name the alarms of which have to be filtered (if
required).
3JK Edition 2.0
1 1 185
4.2.2 Filters Menu
4.2.2.3 Edit Selected Filter
A filter, previously created, can be modified.
3JK Edition 2.0
1 1 186
4.2.2 Filters Menu
4.2.2.4 Delete Selected Filter
A filter, previously created, can be deleted.
3JK Edition 2.0
1 1 187
4.2.2 Filters Menu
4.2.2.5 Delete Filters ...
When this menu is selected, the window shown below opens.
By means of this menu the filters previously created can be canceled. Default filters cannot be canceled.
Select one specific NE (or more NEs) in the Scope column, select a specific filter (or more filters) in the
Filters column and then click on the Done Pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.
3JK Edition 2.0
1 1 188
4.2.2 Filters Menu
4.2.2.6 Save Filters As ...
A default filter, or a filter previously created by means of the Add a
filter menu can be saved to be used for some other LCTs.
Select in the Scope and Filters columns a specific filter to be saved, enter the filter name in the Name
field, select the Folder where to save the file relevant to filter and then click on the Done Pushbutton.
Clicking on the Cancel pushbutton all the selections are cleared.
3JK Edition 2.0
1 1 189
4.2.2 Filters Menu
4.2.2.7 Load Filters From ...
A filter previously saved can be loaded on the LCT by means of the
following menu.
Click on Browse to navigate and then choose the filter file to be loaded. The Scope and the Loaded Filters
columns will show respectively the NE list and the filters list made available by the selected file.
Entering some characters in the Filters Prefix field and then clicking on the Done pushbutton, the inserted
characters are attached before the names of the Loaded Filters. For instance entering <Vim>, the names of
the filters change from APT to VimAPT.
3JK Edition 2.0
1 1 190
4.2 Alarms
4.2.3 Help Menu
This menu shows the Product Version.
3JK Edition 2.0
1 1 191
4 Menu Diagnosis
4.3 Log Browsing
In the Diagnosis pull-down menu select the Log Browsing option.
The Software Trace Log option is reserved to the Alcatel-Lucent technicians.
The Event Log option opens the Event Log browser application.
3JK Edition 2.0
1 1 192
4.3 Log Browsing
4.3.1 Event Log Browser
Event Log Browser is an application which allows to display all the
events occurred in the NE. The max. number of stored events is 500.
An event is meant to be:
a configuration change
a change of the value
of an attribute
an automatic switchover
a manual operation carried
out by the operator.
The following information is provided for each event:
Time: date and time of occurrence of the event. The format is week day/month/day hh:mm:ss.
Reference Time (CEST) year.
Notification ID: a unique identifier for the event.
Explanation: a statement built with the event log data to explain what the event represents.
3JK Edition 2.0
1 1 193
4.3 Log Browsing
4.3.1 Event Log Browser [cont.]
The Menu Bar provides the following menus:
File
Help
3JK Edition 2.0
1 1 194
4.3.1.1 File Menu
The Menu File makes available the following menus:
Refresh Tables
Export
Print
Exit
Refresh Tables
By means of this menu the event log is refreshed.
A refresh may be executed as well clicking on the relevant pushbutton below
the menu bar.
3JK Edition 2.0
1 1 195
4.3.1.1 File Menu [cont.]
Export
This menu allows to export the alarm table as a file.
The file can have the HTML, CSV, PDF or XML format. The file can store all
the events (All entries) or only those selected by means of the pointer of the
mouse (Selection).
The Export may be executed as well clicking on the relevant pushbutton
below the menu bar.
3JK Edition 2.0
1 1 196
4.3.1.1 File Menu [cont.]
Print
It is possible to print the event list (all or just the selected ones). The Print
Dialog box shows up allowing to choose the printer and set print range and
number of copies.
The print may be executed as well clicking on the relevant pushbutton below
the menu bar.
3JK Edition 2.0
1 1 197
4.3.1.2 Help Menu
This menu shows the Product Version.
3JK Edition 2.0
1 1 198
4 Menu Diagnosis
4.4 Remote Inventory
This screen is a read-only screen, which shows all the information on
the equipment.
3JK Edition 2.0
1 1 199
4 Menu Diagnosis
4.5 Abnormal Condition List
The Abnormal Condition List option in the Diagnosis menu displays all
the abnormal conditions currently active in the NE.
An abnormal condition is generated each time a non usual condition is
present in the NE, detected automatically (i.e. automatic Tx mute) or
as consequence of management systems operation (i.e. force switching,
loopbacks, manual Tx mute).
The list of the events which cause an abnormal condition:
Forced switch (EPS, RPS, TPS)
Lockout (EPS, RPS, TPS)
Loopback activation
Local radio Tx mute (manual)
Adaptive Modulation in normal mode
3JK Edition 2.0
1 1 200
4 Menu Diagnosis
4.6 Summary Block Diagram View
The Summary Block Diagram View of the Diagnosis menu displays a
global logical view (strictly related to the physical implementation)
highlighting a synthesis of all the alarms and statuses present in the
system.
3JK Edition 2.0
1 1 201
4.6.1 Main Block diagram view
The Figure shows an example of the Main block diagram view.
Each block has its Alarm indicator (coloured ball icon) that shows the alarm status (different colors according to the alarm severity).
N.B.: The Core-E has 2 alarm indicators in case of Core-E protection (as shown in figure) and only 1 alarm indicator (the ball icon on
the left side) in case of unprotected configuration.
In the Main view the current configuration of the MSS is shown, with the equipped units (PDH or SDH or Radio or MPT-ACC), with the
created LAG, with the protection schemes and with the cross-connections implemented between the different units and the different
Ethernet ports, if any.
Note 1: The connection line between Slot #5 and Slot #6 in figure means that the two ports of the two units are involved in a protection
scheme.
Note 2: The connection square between Slot #3 and Slot #4 in figure means that the SDHACC units are involved in a EPS protection
scheme.
Note 3: Different icons are used to identify Radio LAG or Ethernet LAG. In figure LAG #4 is a Radio LAG, LAG #1 is an Ethernet LAG.
Note 4: An Ethernet User port involved in an Ethernet LAG disappears from the CORE-E area (in figure port #1 and #2 are grouped in
Ethernet LAG#1. Port #5 and #6 are not shown because are optional and have not been configured.
On the RADIO/MPT-ACC slot icon there is the symbol because on this unit a loopback can be activated, the symbol because it is
also possible to activate a Performance monitoring and/or the Ethernet traffic counters. If these symbols are green, it means that the
loopback is active or the Perfomance monitoring/Ethernet Counters have been activated.
By double clicking on an object it s possible to navigate to specific views. In detail:
by double clicking on the Alarm indicator the relevant active alarm is displayed
by double clicking on the Abnormal Condition List box, it is possible to navigate to the Abnormal Condition List menu;
by double clicking on the TMN Local Interface box, it is possible to navigate to the TMN view in the Core-E unit;
by double clicking on a PDH slot icon, it is possible to navigate to the secondary view for the PDH unit;
by double clicking on a Radio slot icon, it is possible to navigate to the secondary view for the Radio unit;
by double clicking on an MPT-ACC slot icon, it is possible to navigate to the secondary view for the MPT-ACC unit.
by double clicking on a Protection switch the relevant configuration is displayed;
by double clicking on a Loopback the relevant configuration is displayed.
The Refresh button will close all secondary windows, updating the main view one, and re-opening all previously opened secondary
windows, with updated content views.
All diagrams are automatically refreshed. According to following figures, bold light green lines update according to the actually NE
working way; alarm icons update as well.
The green line is the current active path.
3JK Edition 2.0
1 1 202
4.6.2 PDH unit secondary view
Depending on the configuration, different diagrams are shown to the
operator, describing the actual NE status and working mode.
1+0 block diagram (PDH unit) (without Core-E protection)
Performance monitoring icons ( ) are shown in green whenever a PM is active.
By double clicking on the Performance Monitoring icon ( ) the navigation to the Performance Monitoring
tool starts.
3JK Edition 2.0
1 1 203
4.6.2 PDH unit secondary view [cont.]
1+0 block diagram (PDH unit) (with Core-E protection)
3JK Edition 2.0
1 1 204
1+1 block diagram (PDH units) (without Core-E protection)
3JK Edition 2.0
1 1 205
1+1 block diagram (PDH units) (with Core-E protection)
3JK Edition 2.0
1 1 206
4.6.3 SDH unit secondary view
1+0 block diagram (SDH unit) (without Core-E protection)
Performance monitoring icons ( ) are are not supported.
3JK Edition 2.0
1 1 207
4.6.3 SDH unit secondary view [cont.]
1+0 block diagram (SDH unit) (with Core-E protection)
3JK Edition 2.0
1 1 208
1+1 block diagram (SDH units) (without Core-E protection)
3JK Edition 2.0
1 1 209
1+1 block diagram (SDH units) (with Core-E protection)
3JK Edition 2.0
1 1 210
4.6.4 Radio unit secondary view (ODU300)
1+0 block diagram (Radio unit) (without Core-E protection)
Loopback icons ( ) are shown in green colour ( ) whenever a loopback is active.
tool starts.
Ethernet Counters icon ( ) is shown in green whenever the counter has been activated.
By double clicking on the Loopback icon, on the PM icon or on the Ethernet Counters icon the navigation to
the relevant menus starts.
The switch blocks are updated according to the signal path, following light green-coloured line.
3JK Edition 2.0
1 1 211
4.6.4 Radio unit secondary view (ODU300) [cont.]
1+0 block diagram (Radio unit) (with Core-E protection)
3JK Edition 2.0
1 1 212
1+1 FD block diagram (Radio units) (without Core-E protection)
3JK Edition 2.0
1 1 213
1+1 FD block diagram (Radio units) (with Core-E protection)
3JK Edition 2.0
1 1 214
1+1 Hot Standby block diagram (Radio units) (without Core-E protection)
3JK Edition 2.0
1 1 215
1+1 Hot Standby block diagram (Radio units) (with Core-E protection)
3JK Edition 2.0
1 1 216
4.6.5 MPT-ACC unit secondary view (MPT-HC)
1+0 block diagram (MPT-ACC unit) (without Core-E protection)
tool starts.
3JK Edition 2.0
1 1 217
4.6.5 MPT-ACC unit secondary view (MPT-HC) [cont.]
1+0 block diagram (MPT-ACC unit) (with Core-E protection)
3JK Edition 2.0
1 1 218
1+1 FD block diagram (MPT-ACC units) (without Core-E protection)
3JK Edition 2.0
1 1 219
1+1 FD block diagram (MPT-ACC units) (with Core-E protection)
3JK Edition 2.0
1 1 220
1+1 Hot Standby block diagram (MPT-ACC units) (without Core-E
protection)
3JK Edition 2.0
1 1 221
1+1 Hot Standby block diagram (MPT-ACC units) (with Core-E protection)
3JK Edition 2.0
1 1 222
4.6.6 MPT-ACC unit secondary view (MPT-MC)
1+0 block diagram (MPT-ACC unit) (without Core-E protection)
tool starts.
3JK Edition 2.0
1 1 223
4.6.6 MPT-ACC unit secondary view (MPT-MC) [cont.]
1+0 block diagram (MPT-ACC unit) (with Core protection)
3JK Edition 2.0
1 1 224
1+1 Hot Standby block diagram (MPT-ACC units) (without Core protection)
3JK Edition 2.0
1 1 225
1+1 Hot Standby block diagram (MPT-ACC units) (with Core protection)
3JK Edition 2.0
1 1 226
1+1 FD block diagram (MPT-ACC units) (without Core protection)
3JK Edition 2.0
1 1 227
1+1 FD block diagram (MPT-ACC units) (with Core protection)
3JK Edition 2.0
1 1 228
4.6.7 XPIC
1+0 XPIC
3JK Edition 2.0
1 1 229
4.6.7 XPIC [cont.]
1+1 XPIC
If an MPT-HC V2 has an XPIC+RPS external module installed and if the XPIC has been enabled in the Radio
menu, the XPIC+RPS module will appear in the Block diagram, as shown in the figure.
3JK Edition 2.0
1 1 230
4 Menu Diagnosis
4.7 Current Configuration View
This view is a read-only screen, which shows the current configuration of the NE.
3JK Edition 2.0
1 1 231
5 Menu Supervision
3JK Edition 2.0
1 1 232
5 Menu Supervision
5.1 Menu Supervision
Menu Supervision is divided in:
Access State
Restart NE
Restart MPT
MIB Management
SW Licence
3JK Edition 2.0
1 1 233
5 Menu Supervision
5.2 Access State
The NE can be managed by the OS or by the WebEML. To control the
competition of the OS and the WebEML, a Local Access Control (LAC) is
available.
If the LAC is access denied, it means that the OS manages the NE and
the WebEML is not allowed to modify the NE configuration (it can only
read). In the view, the icon with a key symbol has a circular shape.
If the LAC is granted, it means that the WebEML is allowed to manage
the NE. In the view, the icon with a key symbol has a rectangular
shape.
If the LAC is requested, it means that the WebEML has requested a
permission from the OS and is waiting for a replay.
However, the OS does continue to provide a certain number of services.
These services include:
Alarm reception and processing,
Performance processing,
Switching back to the OS access state.
The access state of an NE can be modified from two types of views.
3JK Edition 2.0
1 1 234
5.2 Access State
5.2.1 Requested (Switching OS <-> WebEML access state)
Select the Supervision pull down menu. Then select the Requested
option from the Access State cascading menu.
If the OS does not answer in a predefined time, it is assumed that the
NE is in the Craft access state and can be managed by a WebEML.
3JK Edition 2.0
1 1 235
5.2 Access State
5.2.2 OS (Switching WebEML access state <-> OS)
Select the Supervision pull down menu. Then from the Access State
cascading menu select the OS option.
The NE is now managed by the OS.
N.B. The key symbol icon on the management states of the NE view indicates whether the NE is managed
by a WebEML or by the OS.
N.B. Local WebEML access is denied on recovery phase after a loss of communication of the NE. When the
communication with the NE is lost, the OS automatically recovers the communication and forces the state
existing before the loss of communication (therefore, WebEML access can be denied or granted).
3JK Edition 2.0
1 1 236
5 Menu Supervision
5.3 Restart NE
The Restart operation is a software reset and can be executed in
normal traffic conditions.
From the Supervision cascading menu, select the Restart NE option.
A dialogue box opens.
Click the Yes button to confirm the restart NE operation
Click the No button to abort the restart NE operation.
WARNING: After the activation of the Restart NE Command (or after the pressing of the HW reset push-
button) the supervision of the local NE and the remote NEs is lost.
3JK Edition 2.0
1 1 237
5 Menu Supervision
5.4 Restart MPT
The Restart MPT operation is a software reset and can be executed in
normal traffic conditions.
From the Supervision cascading menu, select the Restart MPT option.
A dialogue box opens.
Tick the MPT to be restarted and click the Restart button.
3JK Edition 2.0
1 1 238
5 Menu Supervision
5.5 MIB Management
It is divided in:
Backup
Restore / Activate
Remove file
3JK Edition 2.0
1 1 239
5.5 MIB Management
5.5.1 Backup
This menu allows to save on the WebEML the NE configuration.
To backup the configuration write the filename in the File Name field
and press Save.
Confirm the backup operation by clicking Yes to start the operation.
When the backup is completed in the upper part appears the list of the
previously created backups.
Warning: The backup file name must not include the following characters: space, &, /.
The file name contains always the version as prefix (example: "V020100_", corresponding to version V2.1.0;
"V030100_", corresponding to version V3.1.0). This prefix is inserted automatically by the SW, when the MIB
back-up file is created, and is used automatically by the SW, when the MIB restore mustbe performed.
Note: There is one default repository folder of MIB back-up files for all NEs having the same SWP-release.
The folder name is "backup", and is under the path where you have performed the Local copy of
WebEML(Jusm/CT).
This folder is automatically selected when you perform any of the commands of the MIB managerment
menu.
3JK Edition 2.0
1 1 240
5.5 MIB Management
5.5.2 Restore
This menu allows to download to the NE a previously created backup.
Select one of the backups to be downloaded in the upper part and press
Open.
Confirm the restore operation by clicking Yes to start the operation.
When the restore is completed a message appears asking to activate
the restored file. Click on Yes.
3JK Edition 2.0
1 1 241
5.5 MIB Management
5.5.3 Remove file
This menu allows to remove from the list of the backups one particular
backup.
To remove a backup select the backup file in the upper part and press
Remove file.
Confirm the operation by clicking Yes to start the operation.
By pressing Refresh the list of backups in the upper part of the screen is
updated.
3JK Edition 2.0
1 1 242
5 Menu Supervision
5.6 SW Licence
In this screen the following fields are present.
RMU Serial Number: in this read-only
field appears the Serial Number of
the Flash Card.
License String: in this read-only field
appears the type of the license
written in the Flash Card.
License Key: this field is used to
upgrade the license. To upgrade the
license copy in this field the code of
the new license and click on Apply.
The Refresh button activates a new reading of the read-only fields.
3JK Edition 2.0
1 1 243
6 Tab-panel Equipment
3JK Edition 2.0
1 1 244
6.1 Tab-pabel equipment
The ODU300 is identified by a number indicating the slot number in the MSS, where the Modem unit is
installed.
The MPT-HC or MPT-MC is identified by two digits:
the first digit indicating the slot number in the MSS, where the MPT Access unit is installed (if the MPT is
connected to the port of the Core-E unit the digit is 1),
the second digit indicating the enabled Ethernet port in the MPT Access unit or in the Core-E unit (from 1
to 6).
NB: The icon of the MPT-HC or MPT-MC will appear only if the MPT Access unit has been configured in the
MSS and one port (from 1 to 4) has been enabled.
3JK Edition 2.0
1 1 245
6.1 Tab-pabel equipment [cont.]
ODUs involved in a Radio LAG are identified by letter L as shown in the
following figure.
3JK Edition 2.0
1 1 246
6.1 Tab-pabel equipment [cont.]
MPT-HC V2 equipped with an XPIC+RPS module for the XPIC
configuration are identified by the symbol shown in the next figure.
3JK Edition 2.0
1 1 247
6.2 Starting From Scratch
When the equipment configuration panel is open starting from a scratched NE,
the operator will see the panel in figure below. The Resource Tree area
contains a list of empty slots that have to be configured.
Icon is used to identify an empty slot.
To configure a card:
Select a slot.
Click on Settings panel.
Select the unit type in the Equipment type profile.
Click on Apply.
3JK Edition 2.0
1 1 248
6.3 Tab panels in the Resource Detail Area
For every unit there are 3 tab-panels:
Alarms
Settings
Remote Inventory
3JK Edition 2.0
1 1 249
6.3.1 Alarms tab-panel
The Alarms tab panel provides the fault management, which checks the
current state of alarms related to the selected object.
The alarm tab panel has one row for each possible alarm, but only rows
related to the active alarms are highlighted. When the alarm disappears
it is automatically cleared in the screen.
By putting a tick in the Include alarms from sub-nodes box the alarms
currently active in the sub-nodes of the object will also appear.
For every alarm the following information is given:
Severity: the severity associated to the alarm and assigned in the Alarm
Profile
Event Time: the time of the generation of the alarm
Entity: the entity involved in the alarm
Probable Cause: the probable cause of the alarm
3JK Edition 2.0
1 1 250
6.3.2 Settings tab-panel
In the Setting tab-panel the following fields are present:
Equipment Type
Alarm Profile
Protection Type Configuration
Protection Type Configuration with MPT Access unit
Protection Type Configuration with STM-1 units
Unit stacking
3JK Edition 2.0
1 1 251
6.3.2.1 Equipment Type
The operator must set for all the slots the expected equipment type.
The list box shows the expected equipment type (P32E1DS1 or MD300) for slot
3 to 8;
Select the unit type in the equipment type profile and click Apply.
3JK Edition 2.0
1 1 252
6.3.2.1 Equipment Type [cont.]
Core-E unit Ethernet port configuration
The Ethernet ports of the Core-E can be configured in 2 ways:
to be used as GigaEthernet interface for Ethernet traffic (Note: for port#5 and
port#6 the optional SFP must be installed);
to be used to connect an MPT: MPT-HC or MPT-MC to port#1 to port#4; an MPT-HC
only to port#5 and port#6.
Select the option (SFP or MPT-HC/MPT-MC) and click on Apply.
3JK Edition 2.0
1 1 253
MPT Access unit configuration
In the Setting tab-panel one or two of the four Ethernet ports (to be
connected to the MPT-HC or MPT-MC) must be enabled as shown in figure.
Select as Usage MPT-HC or MPT-MC (in 2 ports max) and click on Apply.
N.B.: Port#1 and Port#2 are electrical Ethernet ports and Port#3 and Port#4 are optical Ethernet ports.
Port#1 and Port#3, Port#2 and Port#4 are mutually exclusive.
3JK Edition 2.0
1 1 254
SDH unit configuration
The Settings tab-panel of the STM-1 unit is shown below.
The Equipment type can be "SDHACC" or "SDHCHAN".
Select the optical SFP (SFP-O) or the electrical SFP (SFP-E) installed on the
STM-1 ports (SFP#1 and/or SFP#2 with SDHACC, only SFP#1 with SDHCHAN)
and click Apply.
3JK Edition 2.0
1 1 255
P8ETH unit configuration
Port #5 to #8 can be configured to accept an optical SFP.
Select option SFP and click on Apply.
3JK Edition 2.0
1 1 256
6.3.2.2 Alarm Profile
This function relates to an alarm severity profile to be assigned to a
selected object (it has been implemented in MSS shelf, in Local TMN
Ethernet interface and in the Radio object).
3JK Edition 2.0
1 1 257
6.3.2.3 Protection Type (P32E1DS1 & MD300)
This function allows the operator to configure the NE protection type.
This function is shown selecting slots 3 to 8 only.
After the equipment selection, protection type list box is filled with
allowed protection types list (the content depends on expected
equipment configured):
If it is configured as P32E1DS1, allowed protection types are 1+0 and 1+1
EPS;
If it is configured as MD300, allowed protection types are 1+0, 1+1 HSB
and 1+1 FD.
If the operator selects a protection type equal to received one, apply
button is disabled.
If operator selects a protection type different from received one, apply
button is enabled.
If slot is in protection mode (received protection type different from
1+0): apply button related to expected-equipment is disabled
(equipment changing is allowed in 1+0 configuration only).
N.B.: For slots 1 and 2 (reserved to Main and Spare Core-E boards), protection type is configured by the
system, according to equipped Core-E board.
3JK Edition 2.0
1 1 258
6.3.2.3 Protection Type (P32E1DS1 & MD300) [cont.]
Protection Example
Configuring a 1+1 protected board, if peer board is not configured, the WebEML will be in charge of
applying such configuration to un-configured peer board, before creating protection in MIB.
If the user applies a new expected protection type, both tree view and configuration panel are reloaded
and updated. With a configured 1+1 protection, involved slots are bounded by light green lines.
3JK Edition 2.0
1 1 259
6.3.2.4 Protection Type with MPT Access unit
To configure the protection scheme select the MPT.
In the example MPT-HC#52: connected to Port#2 of the MPT Access unit in Slot#5.
Choose in the Protect Port field one port available in the list. As protection can be also used an MPT
connected to the same MPT Access unit.
Choose the suitable Protection Type (1+1 FD or 1+1 HSB) and click on Apply.
3JK Edition 2.0
1 1 260
6.3.2.4 Protection Type with MPT Access unit [cont.]
After the configuration in the screen will appear the two jointed MPT-HC.
3JK Edition 2.0
1 1 261
6.3.2.5 Protection Type Configuration with STM-1 units
To configure the protection select 1+1 EPS in the Protection Type field
and click Apply.
N.B.: The field Protection Type appear only when the 2 STM-1 units have the same configuration (only with
SFP-O, not with SFP-E).
3JK Edition 2.0
1 1 262
6.3.2.6 Unit stacking
Two MPT-Access units or two P8ETH units installed on the same row are
automatically grouped in a stacking configuration. The stacking
configuration is highlighted by the violet color as shown in the following
figure (units in slots #3 and #4).
3JK Edition 2.0
1 1 263
6.3.3 Remote Inventory tab-panel
The Remote Inventory feature stores information used to identify all
product components.
The whole information related to selected equipment type can be read,
if available, in the remote inventory panel, inside the Resource Detail
area. Remote inventory data wont be available for levels that do not
have remote inventory itself, as IDU Ch#1 or IDU Ch#0.
3JK Edition 2.0
1 1 264
Blank Page
3JK Edition 2.0
1 1 265
7 Tab-panel Protection Schemes
3JK Edition 2.0
1 1 266
7.1 General
The 1+1 protection schemes implemented are:
Equipment protection: EPS protection in Tx and Rx sides (this protection
scheme can be implemented for all the unit types: Modem unit, PDH unit and
Core-E unit)
Rx Radio protection: RPS Hitless Switch in Rx side
HSB protection: Hot Stand-by protection (available for the Radio unit only)
FD protection: Frequency Diversity protection (available for the Radio unit
only)
The Synchronization protection scheme will appear, if in the
synchronization tab panel the Primary Source and the Secondary Source
have been selected or the NE has been configured as Master with Free
Running mode.
Note 1: For the pair of Core-E units (slot 1 and 2) the only protection type is the Equipment Protection.
Note 2: For the pair of Radio units or MPT Access units the protection type are the Equipment Protection,
Radio Protection and HSB Protection or FD protection.
Note 3: For the pair of PDH units the only protection type is the Equipment Protection.
Note 4: For the pair of SDH units the only protection type is the Equipment Protection.
3JK Edition 2.0
1 1 267
7.1 General [cont.]
Protection scheme screen
To see the current position of the switches enter the menu Diagnosis Summary Block Diagram View and
click on the icon of the equipped units.
3JK Edition 2.0
1 1 268
7.2 EPS Management
The Equipment Protection Management is performed by selecting the
Equipment Protection tree element.
This window allows a complete view of all NE resource involved in the
EPS protection.
The tab-panels are:
Protection Scheme Parameters
Commands
3JK Edition 2.0
1 1 269
7.2 EPS Management
7.2.1 Protection Scheme Parameters
The tab-panel Scheme Parameters displays the parameters that can
be modified.
The parameters are:
Protection Type: this parameter is defined at creation time and it is read
only. The supported type is: 1+1, e.g. a working channel (Main) is protected
by a protecting channel (Spare).
Restoration Criteria: it defines if automatic restoration from protecting to
protected channel is allowed (revertive mode) or inhibited (not revertive
mode). The operator choice for Restoration Criteria will be applied by
clicking on Apply button.
Note: The Core-E protection type is Not-Revertive and cannot be changed. The PDH/SDH protection type is
Not-Revertive and cannot be changed.
Note: In case of 1+1 HSB-EPS, the restoration criteria are always greyed out. No changes can be done
separately for 1+1 HSB-EPS. The restoration criteria selected for HSB-TPS will be applied to EPS
automatically.
3JK Edition 2.0
1 1 270
7.2 EPS Management
7.2.2 Commands
To enter the Commands menu click on the Spare #0 element in the
Tree view or on the Main #1 element.
The operator by the Craft Terminal can modify the state of the switch
through commands Lockout, Forced and Manual. Select the suitable
command and click on Apply.
Lockout has higher priority than Forced: the activation forces in service
Channel 1 (default channel), independently of the possible active
alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation
of this command forces in service Channel 0, independently of the
possible active alarms. This command activates signaling ABN.
Automatic Switch is the normal operation condition: the position of
the switch depends on the commands generated by the logic.
Manual has the lowest priority: it is performed only if there are no
alarms that can activate an automatic switch. It cannot be performed if
Lockout or Forced commands are already activated. If this command is
active, it will be removed by an incoming alarm. This command does
not activate signaling ABN.
Note:
On the Main#1 channel the only available commands are Manual and Forced (only Forced for the Core-E
protection).
On the Spare#0 channel the only available commands are Manual and Lockout (only Lockout for the
Core-E protection.
Warning: All the commands are not error free.
Note: The Forced command for channel 1 is equivalent to the Lockout command for the channel 0. In
both case, the result is that the relevant channel protection path is forced to standby status.
Command priority list
N.B. To release a previously activated command select None and click on Apply.
Warning for Core-E protection in Stacking Configuration with 3 Nes
If the Static Lag Criteria has not been enabled in the System Settings menu, after a Forced command to
restore the correct operation the Lockout command has to be entered.
4 Manual
3 Automatic switch
2 Forced
1 Lockout
Priority Command
3JK Edition 2.0
1 1 271
7.3 RPS Management
The Radio Protection Management is performed by selecting the Rx
Radio Protection element tree.
This window allows a complete view of all NE resource involved in a
RPS protection.
The tab-panels are:
Alarms
Commands
3JK Edition 2.0
1 1 272
7.3 RPS Management
7.3.1 Alarms
The Alarms tab-panel lists the alarms relevant to the protection
configuration.
3JK Edition 2.0
1 1 273
7.3 RPS Management
The tab-panel Protection Scheme Parameters displays the
parameters that can be modify.
The Scheme Parameters are:
Restoration Criteria field: the possible values are Revertive (automatic
restoration allowed) or not Revertive (automatic restoration Inhibited)
Virtual RPS (not implemented)
3JK Edition 2.0
1 1 274
7.3 RPS Management
7.3.3 Commands
To enter the Commands menu click on the Spare #0 element in the Tree view
or on the Main #1 element.
The operator by the Craft Terminal can modify the state of the switch through
commands Lockout, Forced and Manual. Select the suitable command and
click on Apply.
Lockout has higher priority than Forced: the activation forces in service
Channel 1 (default channel), independently of the possible active alarms. This
command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation of this
command forces in service Channel 0, independently of the possible active
alarms. This command activates signaling ABN.
Automatic Switch is the normal operation condition: the position of the switch
depends on the commands generated by the logic.
Manual has the lowest priority: it is performed only if there are no alarms that
can activate an automatic switch. It cannot be performed if Lockout or Forced
commands are already activated. If this command is active, it will be removed
by an incoming alarm. This command does not activate signaling ABN. The
Manual command can be activated only if the two channels are aligned.
Note:
On the Main#1 channel the only available commands are Manual and Forced.
On the Spare#0 channel the only available commands are Manual and Lockout.
The Manual command can be activated only if the two channels are aligned.
4 Manual
3 Automatic switch
2 Forced
1 Lockout
Priority Command
3JK Edition 2.0
1 1 275
7.4 HSB Protection Management
The Transmission Protection Management is performed by selecting the
HSB Protection element tree.
This window allows a complete view of all NE resource involved in the
protection.
The tab-panels are:
Commands
3JK Edition 2.0
1 1 276
The tab-panel Protection Scheme Parameters displays the
parameters that can be modified.
Protection Type: this parameter is defined at creation time and it is read
only. The supported type are: 1+1 (onePlusOne) ,e.g. a working element is
protected by one protecting unit.
Restoration Criteria: it defines if automatic restoration from protecting to
protected unit is allowed (revertive mode) or inhibited (not revertive mode).
The operator choice for Restoration Criteria will be applied clicking on
Apply button.
3JK Edition 2.0
1 1 277
7.4.2 Commands
To enter the Commands menu click on the Spare #0 element or on the
Main #1 element in the Tree view.
The operator by the Craft Terminal can modify the state of the switch
through commands Lockout, Forced and Manual. Select the suitable
command and click on Apply.
Lockout has higher priority than Forced: the activation connects to the
antenna Transmitter 1 (default transmitter), independently of the
possible active alarms. This command activates signaling ABN.
Forced has higher priority than the automatic operation: the activation
of this command connects to the antenna Transmitter 0, independently
of the possible active alarms. This command activates signaling ABN.
Automatic Switch is the normal operation condition: the position of
the switch depends on the commands generated by the logic.
Manual has the lowest priority: it is performed only if there are no
alarms that can activate an automatic switch. It cannot be performed if
Lockout or Forced commands are already activated. If this command is
active, it will be removed by an incoming alarm. This command does
not activate signaling ABN.
Note:
On the Main#1 channel the only available commands are Manual and Forced.
On the Spare#0 channel the only available commands are Manual and Lockout.
Warning: All the commands are not error free.
4 Manual
3 Automatic switch
2 Forced
1 Lockout
Priority Command
3JK Edition 2.0
1 1 278
Blank Page
3JK Edition 2.0
1 1 279
8 Tab-panel Synchronization
3JK Edition 2.0
1 1 280
8.1 Menu Synchronization
Synchronization menu allows the operator to manage the synchronization features.
Using Synchronization tab view (shown in the figure below) the operator can select and configure
synchronization source(s) for the equipment.
Together with Role and Restoration criteria, the operator can select Input and Output ports and can
discriminate between different possible Primary or Secondary sources, according to the Role.
The Resource list area shows the configuration summary describing current synchronization.
As for all other views, Synchronization contains Alarms tab as well and it allows discriminating
synchronization-specific alarms.
Each Network Element must have a reference Clock (NEC), which will be distributed to each board of the
NE. Such clock is a 25 MHz generated in the Core-E Module in the Clock Reference Unit (CRU) function.
The NEC is locked to a Synchronization Source.
The NEC also provides a Sync Out port on the Core-E Module, which can be used to synchronize other NEs.
3JK Edition 2.0
1 1 281
8.2 Synchronization Sources assignment
The physical interfaces to be assigned to Primary and Secondary
synchronization sources can be chosen among the following:
[1] Free Run Local Oscillator. Quality Level value is fixed to QL-SEC/EEC1
(G.812/G8262), the value of QL Priority is Master1 if the NEC is configured as
Master and Slave1 if the NEC is configured as Slave.
[2] Any E1 available at input traffic interfaces (the specific E1 port has to be
chosen). Default value for Quality Level is QL-SSU-A (G.812), the value of QL
Priority is Master1 if the NEC is configured as Master and Slave1 if the NEC is
configured as Slave.
[3] A specific synchronization signal available from the dedicated Sync-In
port, which can be configured according the following options:
a) 2.048 MHz, electrical levels according to G.703, clause 13;
b) 5 MHz, + 6 dBm into 50 ohm, sine-wave;
c) 10 MHz, + 6 dBm into 50 ohm, sine-wave;
d) 1.024 MHz, electrical levels according to G.703, clause 13 with the following
exceptions:
timing properly scaled from 2.048 MHz to 1.024 MHz.
3JK Edition 2.0
1 1 282
8.2 Synchronization Sources assignment [cont.]
[4] The Symbol Rate of the RX signal of any available Radio (the specific
Radio Port has to be chosen). When the SSM support is enabled the QL and QL
Priority are acquired from ESMC PDUs received on the specific radio
interface. When the SSM support is disabled the default value for Quality
Level is QL-SSU-A (G.812), the value of QL Priority is Master1 if the NEC is
configured as Master and Slave1 if the NEC is configured as Slave.
3JK Edition 2.0
1 1 283
[5] Any Synchronous Ethernet clock source available at enabled User Ethernet
traffic interfaces (both electrical and optical) configured in synchronous slave
operation mode (the specific User Ethernet port has to be chosen). From ITU-
T G.8261 point of view, the MSS is a Synchronous Ethernet equipment
equipped with a system clock (NEC) following the ITU-T G.8262
recommendation. A User Ethernet interface configured in synchronous
operation mode can work only at 1000 Mbit/s.
In the particular case of electrical User Ethernet interfaces, these interfaces
perform link auto negotiation to determine the master/slave role for clocks
delivery over the link. The clock slave role must be configured as part of auto
negotiation parameters in order to use the interface as Synchronous Ethernet
clock source input, either as Primary or Secondary. This check is performed
by WebEML/NMS but not by EC. The clock master role must be configured as
part of auto negotiation parameters in order to use the interface as
Synchronous Ethernet clock source output to distribute NEC to other
equipments. For Synchronous Ethernet clock sources from electrical User
Ethernet ports the Fail alarm will be raised when Loss of Synch (i.e. Ethernet
Link Down) will happen. For Synchronous Ethernet clock sources from optical
User Ethernet ports the Fail alarm will be raised when Loss of Optical signal
will happen.
3JK Edition 2.0
1 1 284
[6] Any STM1 available at SDH input traffic interfaces (the specific STM1 port
must be selected). Default value for Quality Level is QL-SSU-A (G.812), the
value of QL Priority is Master1 if the NEC is configured as Master and Slave1 if
the NEC is configured as Slave.
[7] None of the above, this means that no physical synchronization interface
is assigned to the synchronization clock source input. In case of failure of the
other clock source input the CRU enters the Holdover state.
3JK Edition 2.0
1 1 285
8.3 Synchronization sources assignment rules
Some rules have to be followed while assigning the Primary and
Secondary clock sources.
The NEC has to be defined (configured) as Master or Slave.
If a specific interface is chosen as Primary, it cannot be selected as
Secondary too.
If an E1/T1 is chosen to be Primary source, another E1/T1 coming from the
same peripheral cannot be selected as Secondary source and vice-versa.
If an MPT radio interface is chosen to be Primary source, another MPT radio
interface connected to the same MPT Access peripheral cannot be selected as
Secondary source and vice-versa.
If an STM1 is chosen to be Primary source, another STM1 coming from the
same peripheral cannot be selected as Secondary source and vice-versa.
3JK Edition 2.0
1 1 286
8.4 Allowed synchronization sources assignment
Only one Master is allowed in the network.
If Master:
The Restoration Mode must be chosen between Revertive and Non-Revertive;
The Primary clock source input must be chosen among 1), 2), 3), 5) or 6).
If the selected Master Primary clock source input is 1):
the Master Secondary clock source input doesn't need to be selected because
the Primary is never supposed to fail. If the selected Master Primary clock
source input is 2), 3), 5) or 6):
the Master Secondary clock source input must be selected among 1), 2), 3),
5), 6) or 7).
If Slave:
The Restoration Mode is fixed to Revertive.
The Primary clock source input must be chosen among 3), 4) or 5). Slave
Primary clock source input is allowed to be 3) or 5) for full indoor
configuration and for Piling configuration.
The Secondary clock source input must be chosen among 1), 2), 3), 4), 5), 6)
or 7).
3JK Edition 2.0
1 1 287
8.5 SSM Summary Table
By pressing the SSM Summary button the SSM summary Table opens,
which shows the SSM status (enabled/disabled) of the interfaces
carrying the SSM messages.
3JK Edition 2.0
1 1 288
Blank Page
3JK Edition 2.0
1 1 289
9 Tab-panel Connections
3JK Edition 2.0
1 1 290
9 Tab-panel Connections
9.1 Menu Connections
This menu (available in the Main view) contains a summary table for all the implemented cross-connections.
This menu is shown in the figure.
In the Resource Detail Area are available two different functions usable to export and save cross-
connections data with different formats:
hardcopy (Send To Printer);
file (Export To File).
3JK Edition 2.0
1 1 291
10 PDH view for PDH domain
3JK Edition 2.0
1 1 292
10.1 PDH Unit configuration
This menu opens with double click on a PDH unit in the Equipment tab-panel.
In the Resource List Area is given the information related to the tributaries:
1) Port Number: port for a given channel and type of port
2) Signal Mode: type of frame (Framed/Unframed/Disabled)
3) Flow Id: identifier of the tributary for the cross-connection
4) Service Profile: possible profile to be associated to the tributary (TDM2TDM/TDM2Eth)
5) Payload: bytes of the payload (256)
6) ECID Tx: Emulated Circuit Identifier in Tx direction
7) ECID Rx: Emulated Circuit Identifier in Rx direction
8) TDM Clock source: type of the clock to be associated to the tributary (Adaptive/Differential)
Note: The selection of TDM clock source (clock recovery type) as to be common for all the E1 belonging to
the same 32E1 PDH card, independently if the node timing has been enabled in the same NE, it is possible
to mix 32 E1 PDH card with E1s set in DCR and 32 E1 PDH card with E1s set in ACR. Of course the NODE
TIMING must be use properly
Note: Columns 5, 6, 7 and 8 are only available if the Service Profile is TDM2Eth.
3JK Edition 2.0
1 1 293
10.1 PDH Unit configuration [cont.]
For every E1 tributary two tab-panels are available:
Alarms tab-panel
Settings tab-panel
3JK Edition 2.0
1 1 294
10.1.1 Alarms tab-panel
The Alarms tab panel has one row for each possible alarm, but only
rows related to the active alarms are highlighted. When the alarm
disappears it is automatically cleared in the screen.
Profile
Managed Object Class: the class of the alarm.
3JK Edition 2.0
1 1 295
This tab-panel performs all available functions for a tributary port. The
managed tributary types are: E1. To define the involved ports, the
interface selection in the tree view is first required; therefore the
selection of the desired tributary port in the tabular view enables the
Resource Detail list to show the available functions for the single one
resource.
Warning: to change something in the Settings tab-panel first changes the Signal Mode to Framed/Unframed. Then, all
the other fields can be changed.
In the Setting tab-panel there are the following fields:
Port Number: identifies the ports for a given interface and type of port (read-only fields)
Signal Mode. The possible values are:
Unframed for the unframed received signal
Framed for the collection of the performances at the input in Tx side and at the output in Rx side
Disabled
The current state can be modified selecting a different signal mode value and then click on the Apply button to
send the new value to NE.
Service Profile: The possible profiles are:
TDM2TDM
TDM2Eth
Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be associated to an
identifier. Enter the Flow identifier value in the relevant field (possible values: 2 to 4080) and press Apply.
WARNING: The Flow Id must be unique in the MPR network.
Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile is TDM2Eth.
Note: With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time Protocol is
used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real Time Protocol is used) or
Adaptive (RTP is not used). In the unit it is not possible to have mixed configurations with service profiles using RTP
and other service profiles not using RTP.
Example: if in the unit only one E1 has service profile TDM2TDM it is possible to configure other E1 with service
profile TDM2Eth only with the Differential clock source (not with the Adaptive clock source). If the Adaptive clock
source is requested the E1 must be connected to another PDH unit.
Alarm profile: Not implemented now.
Buttons:
Apply: the configuration for the selected E1 tributary will become active
Apply to All: the configuration present in the screen will be applied to all the ports.
Help: by clicking on this button the operator calls the help on line.
3JK Edition 2.0
1 1 296
10.1.3 General information on Circuit Emulation
9500 MPR-E performs Circuit Emulation on PDH TDM flows, and then
transport those "TDM packets" mixed to native Ethernet frames.
The Circuit Emulation IWF (inter-working function) is according the
Metro Ethernet Forum implementation agreement known as MEF 8,
limited to the structure agnostic case.
MEF 8 emulated circuits is based on exchange of service parameters
between two CES IWFs at either end of the emulated circuit; if one of
those IWFs belong to the 9500 MPR-E the following parameters are
defined:
MAC addresses of the two IWFs
Payload size
ECID (2 different values may be used for each direction).
TDM clock source
clock recovery adaptive
clock recovery differential
VLAN (One Vlan is assigned to each bi-directional circuit emulated E1 flow)
It is suggested to set ECID Tx and ECID Rx with the same value of the Flow Id.
Two different cases of Circuit Emulation services are implemented:
1) TDM2TDM
2) TDM2ETH
3JK Edition 2.0
1 1 297
10.1.3 General information on Circuit Emulation[cont.]
TDM2TDM
Both the IWFs belong to 9500 MPR-E and the packets are not supposed
to go out the 9500 MPR-E network.
The IWF parameters listed above, have predetermined values and dont
need to be provisioned.
MAC addresses are determined as consequences of the cross connections.
Payload size: fixed to 121 bytes
ECID will be the same value as Flow Id
TDM clock source: clock recovery differential,
Flow Id provisioned by ECT/NMS
3JK Edition 2.0
1 1 298
10.1.3 General information on Circuit Emulation[cont.]
TDM2ETH
Only one of the IWFs belongs to 9500 MPR-E and the packets are
supposed to go out the 9500 MPR-E network.
MAC addresses: in all involved nodes are determined as consequences of the
cross connections; the only exception is the Ethernet Terminal Node (the
node where that TDM2ETH traffic goes through an user Ethernet port). In
such ETN the source address will be the node Mac address, the dest. mac
address will be provisioned by ECT/NMS.
ECID: provisioned by ECT/NMS, 2 different values may be used for each
direction
TDM clock source will be provisioned by ECT/NMS: clock recovery adaptive,
Flow Id will be provisioned by ECT/NMS (One Vlan is assigned to each bi-
directional circuit emulated E1 flow)
3JK Edition 2.0
1 1 299
10.1.4 Node Timing configuration
Click on the slot icon to access the Node Timing menu.
Node Timing: timing from the network clock as defined in G.8261. The enabling of the Node Timing is
applied to all E1s of the PDH unit.
By enabling the Node Timing the E1 streams in Rx side are retimed at the output with the network element
clock.
3JK Edition 2.0
1 1 300
10.2 Loopback
The functions described in this section allow to perform the test
operations by loopbacks.
Note: The loopbacks can be activated on the local NE only.
In the Resource List Area are listed all the loopbacks which can be performed. In the current software
version only the IF cable loopback is available.
In this area the following information is given:
Interface: number of the channel and type of the loopback
Direction: type of the loopback
Activation: activation status of a loopback (Active/Not Active)
Activation date: date of loopback activation
Timeout: timeout period, if has been set.
3JK Edition 2.0
1 1 301
10.2 Loopback
10.2.1 How to activate a loopback
Select the E1 tributary and select the loopback to be activated by
clicking on the relevant object in the Resource Tree Area or by
selecting the relevant row in the Resource List Area.
Select Active in the Activation field.
Click on Apply.
The Loopback is now ACTIVE (in the row in the Resource List Area the
Activation field of the loopback will change from Not Active to Active).
In the Timeout Period field a timeout period can be set for the loopback activation (max. 4 days).
At the end of this period the loopback will be automatically deactivated.
3JK Edition 2.0
1 1 302
10.2 Loopback
10.2.2 How to remove a loopback
Select the loopback to be removed by clicking on the relevant object in
the Resource Tree Area or by selecting the relevant row in the Resource
List Area.
Select Not Active in the Activation field.
Click on Apply.
The Loopback is now DEACTIVATED (in the row in the Resource List Area
the Activation field of the relevant loopback will change from Active to
Not Active).
3JK Edition 2.0
1 1 303
11 SDH view for SDH domain
3JK Edition 2.0
1 1 304
11.1 General information
The STM-1 unit supports up to 2 STM-1 interfaces.
The STM-1 unit can be used in two different working modes, addressing two
different network scenarios:
STM-1 channelized
STM-1 transparent
The STM-1 channelized mode is available by provision the unit as "SDHCHAN"
and the STM-1 transparent mode is available by provision the unit as "SDHACC".
The STM-1 unit can support 1 channelized STM-1 or up to 2 transparent STM-1
interfaces.
The STM-1 channelized interface works as a terminal multiplexer; it terminates
or originates the SDH frame. It multiplexes NxE1 into an STM-1
electrical/optical line connection. Typical application is a direct connection to
SDH add-drop multiplexers (ADMs). STM-1 card manages one 155 Mbit/s STM1
interface and up to 63xE1. Standard VC4 mapping of lower-order E1 traffic
streams to/from STM-1 is applied, that means that a VC4 directly maps up to
63xVC12 into an STM-1 signal (in turn each VC12 contains 1xE1).
Link options include:
1+0 non-protected operation
1+1 EPS protection (available ONLY with the optical interface)
3JK Edition 2.0
1 1 305
11.1.1 Protection
When the protection of the unit is required (1+1 EPS protection), two
STM-1 units must be installed.
3JK Edition 2.0
1 1 306
11.1.2 Clocking options
Clock source from the incoming STM-1 signal can be selected as
Network Element source clock. In the event the clock source is lost,
clocking falls back to the internal clock or to other of any synch in
options.
3JK Edition 2.0
1 1 307
11.1.3 Tab-panels
Two tab-panels are present:
Alarms: shows the active alarms
Settings: allows to configure the STM-1 interface.
3JK Edition 2.0
1 1 308
11.2 Alarms
The alarm tab panel has one row for each possible alarm, but only rows
related to the active alarms are highlighted. When the alarm disappears
it is automatically cleared in the screen.
Profile
3JK Edition 2.0
1 1 309
11.3 Settings for SDHACC unit (Transparent mode)
This tab-panel allows to configure the STM-1 signal.
To configure the STM-1:
Put a check mark in the Port Status box to enable the STM-1.
Click on Apply.
Set the Auto Laser Shutdown: Enabled/Disabled ForcedOn/Disabled ForcedOff. This field will appear only
if the Settings tab-panel of the STM-1 unit the optical SFP has been selected.
Enable the J0, if required, by selecting one of the two modes (SixteenBytesFrame/OneRepeatedByte) and
in the Expected Receiving Value field enter the expected value. Note: byte J0 is only read, no
Regeneration section Termination is done.
Click on Apply on the left part.
Enter the Flow ID (range: 2 to 4080). Warning: the flow id must be unique in the MPR network.
Select the Jitter Buffer Depth: High/Low.
Select the TDM Clock Source: Differential/Node Timing.
Click on Apply on the right part.
N.B.: The Service profile is fixed to SDH2SDH: the STM-1 is packetized and is transmitted over an MPR radio
port.
N.B.: The Alarm Profile field is not supported in the current release.
3JK Edition 2.0
1 1 310
11.4 Settings for SDHCHAN (Channelized mode)
This tab-panel allows to configure the STM-1 signal.
To configure the STM-1:
Put a check mark in the Port Status box to enable the STM-1.
Set the Auto Laser Shutdown: Enabled/Disabled ForcedOn/Disabled ForcedOff. This field will appear only
if the Settings tab-panel of the STM-1 unit the optical SFP has been selected.
Select the Clock Source.
Enable the J0, if required, by selecting one of the two modes (SixteenBytesFrame/OneRepeatedByte) in
the Expected Receiving Value field and enter the expected value and in the Sending J0 field select one
of the two modes and enter the value to be transmitted.
Note: byte J0 is only read, no Regeneration section Termination is done.
Click on Apply.
Enable, if required, the E1 Node Timing Configuration. The Node Timing is the timing from the network
clock as defined in G.8261. The enabling of the Node Timing is applied to all E1s of the unit. By enabling
the Node Timing the E1 streams in Rx side are retimed at the output with the network element clock.
Configure all the E1s to be mapped/demapped in the STM-1. The E1s are identified by a progressive
number from #1 to #63, but also by the standard SDH identification (x-y-z).
3JK Edition 2.0
1 1 311
11.4 Settings for SDHCHAN (Channelized mode) [cont.]
The E1 tab-panel performs all available functions for the tributary. To define the involved ports, the
interface selection in the tree view is first required; therefore the selection of the desired tributary port in
the tabular view enables the Resource Detail list to show the available functions for the single one
resource.
Warning: to change something in the Settings tab-panel first change the Signal Mode to Unframed or
Framed. Then, all the other fields can be changed.
In the Setting tab-panel there are the following fields:
Port Number: identifies the ports for a given interface and type of port (read-only fields).
3JK Edition 2.0
1 1 312
11.4.1 Signal Mode
The possible values are:
Framed for the collection of the performances at the input in Tx side and at
the output in Rx side
Disabled
The current state can be modified selecting a different signal mode
value and then click on the Apply button to send the new value to
NE.
3JK Edition 2.0
1 1 313
11.4.2 Service Profile
The possible profiles are:
TDM2TDM
TDM2Eth
Flow Id: To implement cross-connections between line side and radio
side each E1 tributary must be associated to an identifier. Enter the
Flow identifier value in the relevant field (possible values: 2 to 4080)
and press Apply.
Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be
written only if the Service Profile is TDM2Eth.
Note: The service profile must be the same for all the E1s.
Alarm profile: Not implemented now.
3JK Edition 2.0
1 1 314
11.4.3 Buttons
Apply: the configuration for the selected E1 tributary will become
active
Apply to All: the configuration present in the screen will be applied to
all the ports.
3JK Edition 2.0
1 1 315
11.4.4 General information on C. E.
9500MPR performs Circuit Emulation on PDH TDM flows, and then
transport those "TDM packets" mixed to native Ethernet frames.
The Circuit Emulation IWF (inter-working function) is according the
Metro Ethernet Forum implementation agreement known as MEF 8,
limited to the structure agnostic case.
MEF 8 emulated circuits is based on exchange of service parameters
between two CES IWFs at either end of the emulated circuit; if one of
those IWFs belong to the 9500MPR the following parameters are
defined:
MAC addresses of the two IWFs
Payload size
ECID (2 different values may be used for each direction)
TDM clock source
clock recovery adaptive
VAN (One Vlan is assigned to each bi-directional circuit emulated E1 flow)
RTP, which is optional in MEF8, is always present, but not used if the
clock recovery is not differential.
3JK Edition 2.0
1 1 316
11.4.4 General information on C. E. [cont.]
Two different cases of Circuit Emulation services are implemented:
1. TDM2TDM
2. TDM2ETH
3JK Edition 2.0
1 1 317
11.4.4.1 TDM2TDM
Both the IWFs belong to 9500MPR and the packets are not supposed to
go out the 9500 MPR network.
The IWF parameters listed above, have predetermined values and dont
need to be provisioned.
MAC addresses are determined as consequences of the cross connections.
ECID will be the same value as Flow Id
TDM clock source: clock recovery differential,
Flow Id provisioned by ECT/NMS
3JK Edition 2.0
1 1 318
11.4.4.2 TDM2ETH
Only one of the IWFs belongs to 9500MPR and the packets are supposed
to go out the 9500 MPR network.
MAC addresses: in all involved nodes are determined as consequences of the
cross connections; the only exception is the Ethernet Terminal Node (the
node where that TDM2ETH traffic goes through an user Ethernet port). In
such ETN the source address will be the node Mac address, the dest. mac
address will be provisioned by ECT/NMS.
ECID : provisioned by ECT/NMS, 2 different values may be used for each
direction
TDM clock source will be provisioned by ECT/NMS: clock recovery adaptive,
Flow Id will be provisioned by ECT/NMS (One Vlan is assigned to each bi-
directional circuit emulated E1 flow).
3JK Edition 2.0
1 1 319
12 EAS View for EAS Domain
3JK Edition 2.0
1 1 320
12 EAS View for EAS Domain
12.1 EAS Domain
This chapter describes the function types offered to the operator in
order to navigate the EAS board. The EAS (Ethernet Access Service)
domain contains the P8ETH, displaying functions associated with the
EAS Ethernet Interfaces.
The P8ETH domain main view contains a single tab-panel:
Ethernet Physical Interface
This domain view consists of the following areas:
Resource Tree, displaying Ethernet physical interface with related port
number;
Resource List, displaying tabular information about tributaries in tree area;
Resource Detail, providing access to EAS Ethernet Interface detail view
Alarms and Settings.
3JK Edition 2.0
1 1 321
12.1 EAS Domain
12.1.1 Ethernet Physical Interface
The Ethernet Port#5 to Port#8 will only appear if optional SFP plug-ins have been enabled in the EAS unit
(refer to Equipment menu).
This tab-panel refers to the Ethernet ports, which can be used as traffic ports and includes two tab-panels
each Ethernet port:
Alarms tab-panel
Settings tab-panel
3JK Edition 2.0
1 1 322
12.1.1.1 Alarms tab-panel
Alarm view shows the Ethernet ports-related alarms. Selecting the
node in Tree area allows checking Ethernet tributary alarms current
state.
3JK Edition 2.0
1 1 323
12.1.1.2 Settings tab-panel (Ethernet Port#1 to Port#4)
This Settings view performs all the available functions for Ethernet electrical tributary ports. Information related to a
data port configuration is provided by the following parameters:
Port Status (Enabled or Disabled);
Alarm Profile (not implemented);
Auto-Negotiation Status (Enabled or Disabled);
Flow Control (Enabled or Disabled);
Configuration (Other / Configuring / Complete / Disabled / Parallel Detect Fail) all read-only;
Advertised Capability (10 Mb/s Half Duplex, 10 Mb/s Full Duplex, 100 Mb/s Half Duplex, 100 Mb/s Full
Duplex, 1000 Mb/s Full Duplex). Note that the 1000 Mb/s Capability can only be selected when Auto-Negotiation
is enabled;
VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged. For each port it is
possible to configure:
Acceptable Frame Type:
Admit tagged only (only tagged frames are allowed in ingress; the untagged frames are dropped)
Admit all (tagged and untagged frames are allowed in ingress)
Default value: Admit all.
Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields (to be added in
ingress to untagged frames), must be configured. Only VLAN-ID values already defined (in the VLAN management
menu) can be configured for this purpose. The Priority values allowed are in the range 0 - 7.
The default Port VLAN-ID and Priority values are: VLAN-ID=1; Priority=0.
VLAN 1 is always removed when the frame is forwarded.
N.B.: Untagged frames: The untagged frames received on one user Ethernet port, configured as Admit tagged only,
are dropped.
N.B.: Priority frames: The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as Admit
tagged only, are dropped. The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit all
configuration enabled, are managed as untagged frames for VLAN-ID field, while the Priority field is the same of the
received packets.
The Restart button forces auto-negotiation to begin link re-negotiation.
3JK Edition 2.0
1 1 324
This Settings view performs all the available functions for Ethernet SFP tributary ports. Information related to the port
configuration is provided by the following parameters:
Advertised Capability (1000 Mb/s Full Duplex).
VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged. For each port it is
possible to configure:
Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields (to be added in
ingress to untagged frames), must be configured. Only VLAN-ID values already defined (in the VLAN management
menu) can be configured for this purpose. The Priority values allowed are in the range 0 - 7.
N.B.: Untagged frames: The untagged frames received on one user Ethernet port, configured as Admit tagged only,
are dropped.
N.B.: Priority frames: The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as Admit
tagged only, are dropped. The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit all
configuration enabled, are managed as untagged frames for VLAN-ID field, while the Priority field is the same of the
received packets.
The Optical Info field is a read-only field.
The Restart button forces auto-negotiation to begin link re-negotiation.
3JK Edition 2.0
1 1 325
13 Ethernet Ring Configuration view
3JK Edition 2.0
1 1 326
13.1 Ethernet Ring Protection (ERP) overview
Ethernet Ring Protection (ERP), specified in ITU-T G.8032
recommendation, is a protection mechanism for Ethernet ring
topologies.
3JK Edition 2.0
1 1 327
13.1.1 Topology
An ERP Topology is a collection of Ethernet Ring Nodes forming a closed
physical loop. Each Ethernet Ring Node is connected to two adjacent
Ethernet Ring Nodes via a duplex communications facility.
Note: The minimum number of Ethernet Ring Nodes in an Ethernet Ring is 2 and the max. number is 16.
3JK Edition 2.0
1 1 328
13.1.2 Ring Link and Ring Port
Each Ethernet Ring Node is connected to adjacent Ethernet Ring Nodes
participating in the same ERP Topology, using two independent Ring
Links. A Ring Link is bounded by two adjacent Ethernet Ring Nodes and
a port for a Ring Link is called a Ring Port.
3JK Edition 2.0
1 1 329
13.1.3 Ring Protection Link (RPL)
The fundamentals of ring protection architecture are:
principle of loop avoidance
utilization of learning, forwarding and address table mechanisms defined in
the Ethernet flow forwarding function
Loop avoidance in the ring is achieved by guaranteeing that, at any
time, traffic may flow on all but one of the Ring Links. This particular
link is called the Ring Protection Link (RPL).
Under normal conditions the RPL is blocked (i.e., not used for traffic).
3JK Edition 2.0
1 1 330
13.1.4 RPL Owner
One designated node, the RPL Owner, is responsible to block traffic
over the RPL.
Under a ring failure condition, the RPL Owner is responsible to unblock
the RPL, allowing the RPL to be used for traffic.
3JK Edition 2.0
1 1 331
13.2 ERP Configuration procedure
3JK Edition 2.0
1 1 332
13.2.1 Step 1: Topology creation
Create new Ring Topology field
1. Write Label.
2. Select Port (E/W) from the list of available Radio Directions
(according to NE Provisioning).
3. Press Create.
4. The created topology will appear in the list as shown in the next
figure.
Note: The Port can be associated only to an ODU300 in 1+0.
3JK Edition 2.0
1 1 333
13.2.1 Step 1: Topology creation [cont.]
3JK Edition 2.0
1 1 334
13.2.2 Step 2: ERP Instance Creation
1. Press Create.
2. The following screen opens.
3JK Edition 2.0
1 1 335
13.2.2 Step 2: ERP Instance Creation [cont.]
3. Write New ERP Label.
4. Write R-APS VLAN ID. The WebEML does the following checks:
admitted values are in [2-4080] range
VLAN Id is not already used in 802.1Q or XConnection
VLAN Id is not already used in other ERP instances
VLAN Id is already used in TMN In-band, but the TMN In-band working mode
is disabled
5. Write R-APS MEG Level. The WebEML does the following checks:
admitted values are in [0-7] range
6. Select the RPL Owner (if needed) and choose the Port (East or West).
7. Press Create.
3JK Edition 2.0
1 1 336
8. The created instance is shown on the ERP Instance List.
3JK Edition 2.0
1 1 337
9. Repeat steps 1 to 7 to create another instance (max. number: 2).
Next figure shows the 2 created instances.
3JK Edition 2.0
1 1 338
13.2.3 Step 3: Add VLANs to created instances
1. Select the Instance in the ERP Instances List.
2. Write in the text field the VLANs.
Printing Format is supported to manage in one shot multiple groups of
VLAN IDs: i.e. (5-10, 100-130, 150).
The WebEML checks the following:
the admitted values are in [1-4080] range
VLAN Id is not used yet as R-APS VLAN Id in any instance
VLAN Id is not associated yet to other instances
VLAN Id is already used in TMN In-band, but the TMN In-band working mode is
disabled
3JK Edition 2.0
1 1 339
13.2.3 Step 3: Add VLANs to created instances [cont.]
3. Press the Arrows button.
The new added VLANs not yet configured are highlighted in Yellow, as
shown in the figure.
4. Press Apply. After applying the configuration the list will display all
the configured VLANs in white background.
3JK Edition 2.0
1 1 340
13.2.4 Step 4: ERP Instances enabling
After having configured XConnection and or 802.1Q, select the
Instance in the Instance List and:
1. enable it by ticking the EPR Enabled check box.
2. Click on Apply.
Note: All the parameters in Runtime Parameters Panel can be modified at run time (ERP Instance
enabled).
Note: After the operator clicks on Close button, the WebEML checks VLAN Id 1 association. If VLAN Id 1 is
not associated to any instances, a Warning will alert the operator in order to avoid traffic (if untagged)
loop.
3JK Edition 2.0
1 1 341
13.3 Configuration example of an Ethernet ring
In Figure is shown a simple example of an Ethernet ring.
VLAN Id 100 and an E1 stream (with Flow Id 500) are inserted in NE1 and extracted in NE4 and viceversa.
3JK Edition 2.0
1 1 342
13.3 Configuration example of an Ethernet ring [cont.]
Procedure:
1. Select in the VLAN Management menu 802.1Q.
2. Select in the System Settings menu 802.1p in the Quality of Service area.
3. Configure the ERP.
Note: Configure first the RPL Owner NE3.
Warning: insert VLAN 100 and Flow Id 500 in the Ring instance.
4. Create the Cross-connection for the E1 stream.
PDH-Ring cross-connection for NE1 and NE4
Pass-through cross-connection for NE2 and NE3
5. Insert in the VLAN Management table of the VLAN Management menu the
VLAN Id 100 inserted in the ring instance.
3JK Edition 2.0
1 1 343
14 Radio view for Radio domain
3JK Edition 2.0
1 1 344
14.1 Radio domain menu
The Radio domain view allows the operator to manage the resources of
the radio transmission channel.
Three types of Outdoor Units are available:
ODU300 (up to 256 QAM/up to 56 MHz)
MPT-HC or MPT-HC V2 (High Capacity: up to 256 QAM/up to 56 MHz)
MPT-MC (Medium Capacity: up to 128 QAM/up to 28 MHz)
A Radio NE consists of one or two radio channels with a set of
functional blocks (tributary ports, radio ports etc).
This domain view consists of three areas.
Four tab panels are present in the Resource Detail Area.
The tab-panel Power Source is available only with the MPT Access unit
to interface MPT-HC or MPT-MC.
Note: with the WebLWebEML the possible selection is only MPT-HC. From the functional point of view MPT-
HC and MPT-HC V2 are equal.
Only if an MPT-HC V2 is installed with the XPIC+RPS external module the XPIC configuration can be
implemented.
The areas of the domain view are:
Resource Tree Area: displays the radio ports sorted by channel number.
Resource List Area: displays tabular information about the selected resource in tree area.
Resource Detail Area: displays, through tab windows, the object s properties selected in list area. This
area enables to execute the available functions for involved resource.
The tab panels present in the Resource Detail Area are:
Alarms: shows the active alarms
Settings: configures the radio parameters
Measurements: performs the Tx and Rx power measurements.
Loopback: activates the loopbacks available with the equipment.
3JK Edition 2.0
1 1 345
14.2 Alarms
The Alarms tab panel has one row for each possible alarm, but only
rows related to the active alarms are highlighted. When the alarm
disappears it is automatically cleared in the screen.
Profile
3JK Edition 2.0
1 1 346
14.3 Settings
ODU300
MPT-HC
MPT-MC
3JK Edition 2.0
1 1 347
14.3 Settings
14.3.1 ODU300
To configure click in the Main view on the icon of the Modem unit to be
configured.
The Radio Main View opens.
The Radio Main View is divided in two parts:
on the left side is present the Direction # menu
on the right side is present the Channel #1 menu (for 1+0 configuration) and
Channel #1 and Channel #0 menus (for 1+1 configuration).
Warning: to configure the Radio unit first configure the Shifter and the Tx Frequency in the Frequency
field (in the Channel menu) and click on Apply. Then configure all the other parameters.
3JK Edition 2.0
1 1 348
14.3.1 ODU300
14.3.1.1 Direction area
This area is divided in 6 parts:
1) User Label
2) Mode
3) Link Identifier Configuration
4) PPP RF
5) Alarm Profile
6) Synchronization
3JK Edition 2.0
1 1 349
14.3.1 ODU300
14.3.1.1 Direction area [cont.]
1) User Label
A label can be inserted in this field to identify the radio direction (0 to
15 characters).
3JK Edition 2.0
1 1 350
2) Mode
Operation without the Adaptive Modulation
14.3.1 ODU300
Select in the Mode field Presetting.
Select in the Reference Channel
Spacing field the suitable channel
spacing to be used.
Select in the Modulation field the
suitable Modulation scheme.
According to the selected Channel
Spacing and to the Modulation the
relevant capacity in the Capacity field
will appear.
To confirm the selection
click on Apply.
The operation mode can be without or with the Adaptive Modulation.
3JK Edition 2.0
1 1 351
Operation with the Adaptive Modulation
14.3.1 ODU300
Select in the Mode field Adaptive
Modulation.
Select in the Modulation Range
field the Modulation range (4/16
QAM or 4/16/64 QAM) to be used
by the Adaptive Modulation.
spacing.
The Reference Mode field is not
supported.
To confirm the selection click on
Apply.
Select in the Remote
Switching Threshold
field how many dB the
switching thresholds
have to be moved from
the default value (+4
dB/-2 dB). The default
value is approx. 6 dB
below the 10-6 Rx
threshold (NB).
The Current Modulation
field is a read-only field,
which shows the current
used modulation. The
current modulation will
depend on the fading
activity during the
propagation.
With a check mark in the
Manual Operation box it is
possible to force a
modulation scheme by
selecting the scheme in the
Forced Modulation field.
The main idea behind Adaptive Modulation in Point to Point system is to adjust adaptively the modulation as
well as a range of other system parameters based on the near-instantaneous channel quality information
perceived by the receiver, which is fed back to the transmitter with the aid of a feedback channel.
The switching between the modulation schemes is hitless and maintains the same RF channel bandwidth.
The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB) without ATPC.
NB: Example: if the default switching threshold is -64 dBm by setting +4 dB the new value is -60 dBm and by
setting -2 dB the new value is -66 dBm.
Note: If the current Modulation scheme is 4 QAM, it not possible to force to 64 QAM, but first must be
forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to pass to 4 QAM first must
be forced to 16 QAM and then to 4 QAM.
Warning: with the up and down arrows, below the Forced Modulation field, it is possible to increase or
decrease the part of the screen relevant to the parameters of the Adaptive Modulation.
3JK Edition 2.0
1 1 352
14.3.1 ODU300
How to change the operation mode (from operation without
Adaptive Modulation to operation with Adaptive Modulation) in 1+1
HSB configuration
Follow the procedure:
1. Mute the 2 Transmitters
2. Remove the protection scheme: enter the Equipment tab-panel, select the
unit and remove the protection scheme
3. Enter the Main Radio unit setting tab-panel: set Mode Adaptive Modulation
4. Create again the protection scheme: enter the Equipment tab-panel,
select the unit and create the protection scheme (1+1 HSB)
5. Remove the muting from the Transmitters.
3JK Edition 2.0
1 1 353
14.3.1 ODU300
Channel Spacing Change
Capacity Up-Grade
When the admission control is enabled, this applies when the lowest modulation
scheme of the new channel spacing has a capacity which is larger than the one with
the old channel spacing. In this case all the pre-configured TDM or ATM PW will be
kept. The residual bandwidth for the lowest modulation scheme is recomputed.
When the admission control is disabled, this applies when the highest modulation
the old channel spac-ing. In this case all the pre-configured TDM or ATM PW will be
kept. The residual band-width for the highest modulation scheme is recomputed.
Capacity Down-Grade
When the admission control is enabled this applies when the lowest modulation
scheme of the new channel spacing has a capacity which is smaller than the one with
the old channel spacing. If all the pre-configured TDM or ATM PW stays in the
capacity associated to the lowest modulation scheme, they will be kept and the
residual bandwidth for the lowest modulation scheme is recomputed. If all the pre-
configured TDM or ATM PW cannot stay in the capacity associated to the lowest
modulation scheme, the change of channel spacing is rejected by WebEML/NMS.
A specific behavior must be followed when the Channel Spacing needs to be changed, to pre-serve any
pre-configured TDM or ATM PW. Consequently, two cases must be taken into account: Capacity Up-grade
and Capacity Down-Grade.
3JK Edition 2.0
1 1 354
14.3.1 ODU300
When the admission control is disabled this applies when the highest modulation
the old channel spac-ing. If all the pre-configured TDM or ATM PW stays in the
capacity associated to the highest modulation scheme, they will be kept and the
residual bandwidth for the highest mod-ulation scheme is recomputed. If all the pre-
configured TDM or ATM PW cannot stay in the capacity associated to the highest
3JK Edition 2.0
1 1 355
14.3.1 ODU300
Modulation Change
Capacity Up-Grade
This applies when the new modulation scheme has a capacity which is larger than the
old one.
When the admission control is enabled all the pre-configured TDM or ATM PW are
kept.
When the admission control is disabled all the pre-configured TDM or ATM PW will
work if the current capacity is able to support all of them, otherwise all pre-
configured TDM or ATM PW will not work.
Capacity Down-Grade
This applies when the new modulation scheme has a capacity which is smaller than
the old one.
When the admission control is enabled, since the admission control was performed
with the capacity of the lowest modulation scheme, all the pre-configured TDM or
ATM PW will be kept.
When the admission control is disabled, since the admission control was performed
with the capacity of the highest modulation scheme, all the pre-configured TDM or
ATM PW will be kept if the current capacity is able to support all of them, otherwise
all pre-configured TDM or ATM PW will be completely lost.
When the AM engine changes the modulation, the pre-configured TDM or ATM PW traffic must be managed
according to the behavior here after described. Two cases must be taken into account: Capacity Up-grade
3JK Edition 2.0
1 1 356
14.3.1 ODU300
Modulation Working Mode Change
From Static to Adaptive
Adaptive Modulation can be enabled only if the ATPC is disabled.
When the Adaptive Modulation is enabled and Admission Control is enabled the
behavior is:
If all the pre-configured TDM or ATM PW in the Old Static Modem Profile, stay in the capacity
associated to the lowest Modulation Scheme, the request of change is accepted and the
residual bandwidth for the lowest Modulation Scheme is computed.
If all the pre-configured TDM or ATM PW cannot stay in the capacity associated to the lowest
Modulation Scheme, the request of change is rejected.
When the Adaptive Modulation is enabled and Admission Control is disabled all the
pre-con-figured TDM or ATM PW in the Old Static Modem Profile stay in the capacity
associated to the highest Modulation Scheme, then the request of change is always
accepted and the residual bandwidth for the highest Modulation Scheme is
computed.
From Adaptive to Static
When the Adaptive Modulation is disabled, if all the pre-configured TDM or ATM PW
in the Old Adaptive Modem Profile, stays in the capacity of the New Static Modem
Profile, the request is accepted and the residual bandwidth for new Static Modem
Profile will be computed. If all the pre-configured TDM or ATM PW cannot stay in the
capacity of the New Static Modem Profile, the request of change is rejected.
A specific behavior must be followed when it is needed to move from Adaptive Modulation to Static
Modulation or vice-versa, in order to preserve any pre-configured TDM or ATM PW. Two cases must be taken
into account: from Static to Adaptive Modulation and from Adaptive to Static Modulation. The working
mode changes, here below described, are generic. The changes cover both the change of the modulation
but with the same Channel Spacing and the change of the Channel Spacing.
3JK Edition 2.0
1 1 357
14.3.1 ODU300
3) Link Identifier
This part allows the operator to define the expected and sent identifier
values of parameters related to the link management and, if necessary,
modify them.
The operator choices will be sent to the NE by clicking on the related
Apply button.
If the Link Identifier is Enabled the following fields can be written:
Expected Identifier: this field is the link identifier expected at the receiving
NE
Sent Identifier: this field is the link identifier inserted on the transmitting NE
(range: 1-256).
3JK Edition 2.0
1 1 358
14.3.1 ODU300
4) PPP RF
The PPP-RF interface is a communication interface based on the use
of an inframe RF proprietary 64 kbit/s channel. Through the PPP-RF
interface the NE can exchange management messages with a remote OS
(or Craft Terminal) station.
The PPP-RF channel can be Enabled or Disabled.
If enabled, in the Remote Address field will appear the IP address of
the remote connected NE.
In the Routing IP Protocol field enter the used IP protocol and in case
of OSPF protocol select also the associated OSPF area.
3JK Edition 2.0
1 1 359
14.3.1 ODU300
5) Alarm Profile
Not implemented in the current release.
6) Synchronization
Tick on Enable to enable the transmission of the SSM message over the
radio channel.
3JK Edition 2.0
1 1 360
14.3.1 ODU300
14.3.1.2 Channel area
1) Frequency
2) ATPC (this menu is alternative to RTPC menu)
3) Manual Transmit Power Control (this menu is alternative to ATPC menu)
4) Tx Mute
5) Alarm Profile
3JK Edition 2.0
1 1 361
14.3.1 ODU300
14.3.1.2 Channel area [cont.]
1) Frequency
The system can operate with different types of ODU according to the RF
band and to the channel arrangement. There are ODUs which can
manage only one shifter or several predefined shifters.
In the Shifter field select the suitable shifter.
In the Tx frequency field insert the suitable Tx frequency (the Rx
frequency is automatically calculated by using the inserted Tx
frequency and the shifter) and press push-button Apply.
By pressing the Data Help button the list of all the available ODUs with
the relevant P/N, shifter and Tx frequency will appear. The Data Help
table is usefull, if you are not connected to the ODU.
3JK Edition 2.0
1 1 362
14.3.1 ODU300
2) ATPC
The ATPC can be Enabled or Disabled.
The new value will be applied when the Apply button is pressed. If the
ATPC has been enabled, the ATPC Range and ATPC Rx Threshold
parameters must be filled.
ATPC Range
The Min Tx power and Max Tx power, regarding the Tx Range in the ATPC
management, can be written in the relevant field.
When the Apply button is pressed the new values will be applied.
ATPC Rx Threshold
The value of the low power threshold can be changed by writing the new
value in the field. When the Rx power is equal to this power the ATPC
algorithm starts to operate.
Note: the ATPC area is not present if the Adaptive Modulation has been selected.
3JK Edition 2.0
1 1 363
14.3.1 ODU300
3) Manual Transmit Power Control
Manual Transmit Power Control (without Adaptive Modulation)
If the ATPC is disabled the manual Tx Power field is present. For the Tx
Power range refer to the table.
In this field write the new value within the allowed transmitted power range.
The range is shown on the right side of Manual Transmit Power Control area.
Tx Power (with Adaptive Modulation)
The operator can modify only the 4 QAM field. In this field the operator has
to enter the constant power, which will be used with 4 QAM modulation. The
power range is shown on the right side and depends on the selected
reference mode.
Note: the same power value will be used by the 16 QAM and 64 QAM modulation schemes
3JK Edition 2.0
1 1 364
14.3.1 ODU300
4) Tx Mute
The information related to the transmitter status is shown in the Tx
Mute field (Off/Manual/Auto). To squelch the transmitter select Enable
and press Apply button.
The following indications will appear in the Tx Mute field:
Off: Transmitter not squelch
Manual: Transmitter squelched due to the manual operation
Auto: Transmitter squelched due to an automatic operation
3JK Edition 2.0
1 1 365
14.3.1 ODU300
5) Alarm Profile
By clicking on the icon the Alarm Severity Profile menu opens, which
allows to associate to the radio channel a specific alarm profile. Select
one Alarm Profile in the Profile Name list (4 alarm profiles are listed)
and click Apply. Tick the Show details check box to see the severity
associated to each alarm.
3JK Edition 2.0
1 1 366
14.3 Settings
14.3.2 MPT-HC
To configure click in the Main view on the icon of the MPT-HC or of the
MPT Access unit to be configured.
The Radio Main View has 3 tab-panels:
Power Source
Port ##1
Port ##2 (this tab-panel is present if in the MPT Access unit a second port has
been configured)
Warning: First configure the Port and then the Power Source. Pay attention to configure properly the Power
Source.
3JK Edition 2.0
1 1 367
14.3.2 MPT-HC
1) User Label
2) Mode
3) XPIC Configuration
5) PPP RF
6) Alarm Profile
7) Synchronization
3JK Edition 2.0
1 1 368
14.3.2 MPT-HC
1) User Label
15 characters).
3JK Edition 2.0
1 1 369
2) Mode
14.3.2 MPT-HC
Select in the Reference Channel Spacing
field the suitable channel spacing to be
used (up to 56 MHz).
Select in the Modulation field the suitable
Modulation scheme (up to 256 QAM).
According to the selected Channel Spacing
and to the Modulation the relevant
capacity in the Capacity field will appear.
To confirm the selection click on Apply.
Select the Option mask: Current mask or
New mask with or without XPIC
Note: The SDH capacity mask must be selected in the following two profiles:
In the first case 1xSTM-1 or 72 E1s can be transmitted.
In the second case 2xSTM-1 or 145 E1s can be transmitted.
2 145 128QAM 56
1 72 128QAM 28
# STM-1 SDH2SDH # E1 TDM2TDM FCM Mode Modulation CS (MHz)
3JK Edition 2.0
1 1 370
14.3.2 MPT-HC
Modulation.
the lowest modulation scheme
(from QPSK) to be used by the
Adaptive Modulation.
spacing.
click on Apply.
Choose in the
Supported Modulation
field all the modulation
schemes to be used with
the Adaptive
Modulation. The
modulation schemes
(from the lowest to the
highest scheme) must
be contiguous
activity during the
propagation.
possible to force a
Select in the Option field the
spectral efficiency class to be set
as reference: Current mask or New
mask
The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB/1+1 FD) Radio
configuration without ATPC).
Note: The SDH capacity mask must be selected in the following two profiles:
In the second case 2xSTM-1 or 145 E1s can be transmitted.
Note: The Remote Switching Threshold is not supported.
Note: If the current Modulation scheme is 4 QAM, it not possible to force to 64 QAM, but first must be
forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to pass to 4 QAM first must
be forced to 16 QAM and then to 4 QAM.
2 145 128QAM 56
1 72 128QAM 28
3JK Edition 2.0
1 1 371
14.3.2 MPT-HC
HSB configuration
3JK Edition 2.0
1 1 372
14.3.2 MPT-HC
Capacity Up-Grade
Capacity Down-Grade
3JK Edition 2.0
1 1 373
14.3.2 MPT-HC
3JK Edition 2.0
1 1 374
14.3.2 MPT-HC
Modulation Change
Capacity Up-Grade
old one.
kept.
Capacity Down-Grade
the old one.
3JK Edition 2.0
1 1 375
14.3.2 MPT-HC
behavior is:
computed.
3JK Edition 2.0
1 1 376
14.3.2 MPT-HC
This field is available only with the MPT-HC V2 with the XPIC+RPS external module installed and if in the
Mode area in the Option field a mask with XPIC has been selected.
Note: The XPIC can be implemented in 1+0 or 1+1 HSB with the Static Modulation (Presetting Mode) and
with RTPC (no ATPC).
How to configure the XPIC
1. In the Polarization field select the polarization to be used by the radio channel (Vertical or Horizontal).
2. Go in the XPIC Configuration menu by clicking the relevant button in the Tool bar. Refer to XPIC
Configuration.
3. Now in the Associated Interface field will appear the radio channel associated in the XPIC Configuration.
4. By clicking on the icon on the right of the Associated Interface field you can navigate to the associated
radio channel menu.
3JK Edition 2.0
1 1 377
14.3.2 MPT-HC
4) Link Identifier
modify them.
Apply button.
NE
(range: 0-256).
The "Link Identifier Mismatch" drops all the traffic.
3JK Edition 2.0
1 1 378
14.3.2 MPT-HC
5) PPP RF
3JK Edition 2.0
1 1 379
14.3.2 MPT-HC
6) Alarm Profile
7) Synchronization
radio channel.
3JK Edition 2.0
1 1 380
14.3.2 MPT-HC
1) Frequency
4) RSL Driving Criteria (only in 1+1 configuration without Adaptive
Modulation)
5) MSE Driving Criteria (only in 1+1 configuration with Adaptive Modulation)
6) Tx Mute
7) Alarm Profile
Note: The Channel #1 area is always present (in 1+0 and 1+1 configuration). The Channel #0 area is present
in 1+1 configuration only.
Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field (in
the Channel menu) and click on Apply. Then configure all the other parameters.
3JK Edition 2.0
1 1 381
14.3.2 MPT-HC
1) Frequency
In the Rx frequency field will appear the calculated Rx frequency, but
this frequency can be changed in +5 MHz range to implement the
Exotic shifter configuration, if required. Change the Rx frequency
and press Apply.
table is usefull, if you are not connected to the ODU.
3JK Edition 2.0
1 1 382
14.3.2 MPT-HC
2) ATPC
ATPC Range
ATPC Rx Threshold
3JK Edition 2.0
1 1 383
14.3.2 MPT-HC
The operator can modify only the Tx power relevant to the lowest modulation
scheme. In this field the operator has to enter the constant power, which will
be used with the lowest modulation.
Note: the same power value will be used by the other modulation schemes
3JK Edition 2.0
1 1 384
14.3.2 MPT-HC
4) RSL Driving Criteria
Select in the RSL Driving Criteria field the suitable value. In 1+1 FD and
HSB configurations both the transmitters can be driven by the lowest or
by the highest RSL values of the two remote demodulators.
5) MSE Driving Criteria
Select in the MSE Driving Criteria field the suitable value. In 1+1 FD and
HSB configurations both the transmitters can be driven by the lowest
(1) or by the highest MSE values (2) of the two remote demodulators.
3JK Edition 2.0
1 1 385
14.3.2 MPT-HC
6) Tx Mute
3JK Edition 2.0
1 1 386
14.3.2 MPT-HC
7) Alarm Profile
3JK Edition 2.0
1 1 387
14.3 Settings
14.3.3 MPT-MC
To configure click in the Main view on the icon of the MPT-MC or of the
MPT Access unit to be configured.
The Radio Main has 3 tab-panels:
Power Source
Port ##1
Port ##2 (this tab-panel is present if in the MPT Access unit a second port has
been configured)
Warning: First configure the Port and then the Power Source. The MPT-MC cannot support 1+1 FD.
The MPT-MC cannot support 1+1 FD.
3JK Edition 2.0
1 1 388
14.3.3 MPT-MC
1) User Label
2) Mode
3) XPIC Configuration (not supported)
5) PPP RF
6) Alarm Profile
7) Synchronization
3JK Edition 2.0
1 1 389
14.3.3 MPT-MC
1) User Label
15 characters).
3JK Edition 2.0
1 1 390
2) Mode
14.3.3 MPT-MC
field the suitable channel spacing to be
used (up to 28 MHz).
Select in the Modulation field the suitable
Modulation scheme (up to 128 QAM).
According to the selected Channel Spacing
and to the Modulation the relevant
capacity in the Capacity field will appear.
To confirm the selection click
on Apply.
Select the Option mask: Current mask or
New mask with or without XPIC
Note: The SDH capacity mask must be selected in the following profile:
1 72 128QAM 28
3JK Edition 2.0
1 1 391
14.3.3 MPT-MC
Modulation.
the lowest modulation scheme
(from QPSK) to be used by the
spacing.
click on Apply.
Choose in the
Supported Modulation
field all the modulation
schemes to be used with
the Adaptive
Modulation. The
modulation schemes
(from the lowest to the
highest scheme) must
be contiguous
activity during the
propagation.
possible to force a
Select the Option mask: Current
mask or New mask with or without
XPIC
The Adaptive Modulation is available for unprotected (1+0) and Protected (1+1 HSB/1+1 FD) Radio
configuration without ATPC).
Note: The SDH capacity mask must be selected in the following profile:
Note: In 1+1 configuration the Driving MSE field is not supported.
Note: The Remote Switching Threshold is not supported.
Note: Example: if the current Modulation scheme is 4 QAM, it not possible to force to 64 QAM, but first must
be forced to 16 QAM and then to 64 QAM. Also if the current Modulation is 64 QAM, to pass to 4 QAM first
must be forced to 16 QAM and then to 4 QAM.
1 72 128QAM 28
3JK Edition 2.0
1 1 392
14.3.3 MPT-MC
HSB configuration
3JK Edition 2.0
1 1 393
14.3.3 MPT-MC
Capacity Up-Grade
Capacity Down-Grade
3JK Edition 2.0
1 1 394
14.3.3 MPT-MC
3JK Edition 2.0
1 1 395
14.3.3 MPT-MC
Modulation Change
Capacity Up-Grade
old one.
kept.
Capacity Down-Grade
the old one.
3JK Edition 2.0
1 1 396
14.3.3 MPT-MC
behavior is:
computed.
3JK Edition 2.0
1 1 397
14.3.3 MPT-MC
Not available with the MPT-MC.
4) Link Identifier
modify them.
Apply button.
NE
(range: 0-256).
The "Link Identifier Mismatch" drops all the traffic.
3JK Edition 2.0
1 1 398
14.3.3 MPT-MC
5) PPP RF
3JK Edition 2.0
1 1 399
14.3.3 MPT-MC
6) Alarm Profile
7) Synchronization
radio channel.
3JK Edition 2.0
1 1 400
14.3.3 MPT-MC
1) Frequency
4) RSL Driving Criteria (only in 1+1 configuration without Adaptive
Modulation)
5) MSE Driving Criteria (only in 1+1 configuration with Adaptive Modulation)
6) Tx Mute
7) Alarm Profile
Note: The Channel #1 area is always present (in 1+0 and 1+1 configuration).
The Channel #0 area is present in 1+1 configuration only.
Warning: To configure the unit first configure the Shifter and the Tx Frequency in the Frequency field (in
the Channel menu) and click on Apply. Then configure all the other parameters.
3JK Edition 2.0
1 1 401
14.3.3 MPT-MC
1) Frequency
In the Rx frequency field will appear the calculated Rx frequency, but
this frequency can be changed in +5 MHz range to implement the
Exotic shifter configuration, if required. Change the Rx frequency
and press Apply.
table is usefull if you are not connected to the ODU.
3JK Edition 2.0
1 1 402
14.3.3 MPT-MC
2) ATPC
ATPC Range
ATPC Rx Threshold
3JK Edition 2.0
1 1 403
14.3.3 MPT-MC
The operator can modify only the Tx power relevant to the lowest modulation
scheme. In this field the operator has to enter the constant power, which will
be used with the lowest modulation.
Note: the same power value will be used by the other modulation schemes
3JK Edition 2.0
1 1 404
14.3.3 MPT-MC
4) RSL Driving Criteria
Select in the RSL Driving Criteria field the suitable value. In 1+1 FD and
HSB configurations both the transmitters can be driven by the lowest or
by the highest RSL values of the two remote demodulators.
5) MSE Driving Criteria
Select in the MSE Driving Criteria field the suitable value. In 1+1 FD and
HSB configurations both the transmitters can be driven by the lowest
(1) or by the highest MSE values (2) of the two remote demodulators.
3JK Edition 2.0
1 1 405
14.3.3 MPT-MC
6) Tx Mute
3JK Edition 2.0
1 1 406
14.3.3 MPT-MC
7) Alarm Profile
3JK Edition 2.0
1 1 407
14.4 Measurement
The Power Measurements capability is performed by means of the
Measurement tabbed panel.
The Measurement screen allows the operator to set initial parameters
for the required measurement.
"Measurement interval" fields allow the operator to set the time
duration of the measurement. The default is Days: 7, Hours: 0, Minutes:
0. A 7-day measurement interval is also the maximum allowed interval.
"Sample time" field is the period between two consecutive
measurement samples. The choice is among 2, 4, 6, 30, 60 sec.
The last section of the dialog is referred to an optional Log file.
By selecting Create File the log file is created and a default path and
name for this file is displayed to the operator. The file is stored in the
MPRE_CT_V00.07.08 directory.
Note: The file name must not include the following characters: \ ? : * < > |.
3JK Edition 2.0
1 1 408
14.4 Measurement [cont.]
The log file contains the sample value and records the measurement up
to a maximum dimension (7 days for a 2 s sample time).
By clicking on the "Start" button the screen "Power Measurement
Graphic" appears.
The Power Measurement Graphic is available only if the WebEML is
connected to the NE.
The Power Measurement Graphic screen shows the Tx and Rx
measurements related to the local and remote NE.
Through this screen the operator can see, in real time, the power
transmitted by the local and remote transmitter (Tx) and the power
received by the local and remote receiver (Rx).
The top graphic screen area shows the TX curves (local and remote),
while the bottom area shows the Rx curves (local and remote). Note
that the colors represent the linked end-point of the two NE; for
example, if the local TX is blue, the remote receiver will also have the
same color.
3JK Edition 2.0
1 1 409
The top of the screen offers all the characteristics present in the
current measurement:
Radio port: gives the symbolic name associated to the radio channel being
analyzed
Sample time: indicates the frequency used to send the measurement requests
to NE;
Start time: is the first request time;
Stop time: is the interval time selected in the previous parameters window,
added to the start time;
Time: is the current response time;
Log File: is the complete pathname of the file where the received values are
stored.
3JK Edition 2.0
1 1 410
By clicking on "Show details" box, on the left side of the Power Measurement
Graphic, a new table appears; this table shows the following relevant values of
the received and transmitted power:
Tx Local End
max Tx local value and date when this value was received for the first time.
min. Tx local value and its current date when this value was received for the first time.
current Tx local value and its current date.
Tx Far End
max Tx remote value and date when this value was received for the first time.
min. Tx remote value and its current date when this value was received for the first time.
current Tx remote value and its current date.
Rx Local End
max Rx local value and date when this value was received for the first time.
min. Rx local value and its current date when this value was received for the first time.
current Rx local value and its current date.
Rx Far End
max Rx remote value and date when this value was received for the first time.
min. Rx remote value and its current date when this value was received for the first time.
current Rx remote value and its current date.
Note: When not receiving any signal, RSL value is not set to a fixed specific value.
Note: PTx and PRx levels software readings tolerance: PTx=Real Value 3dB; PRx=Real Value 5dB.
WARNING:
Radio analog transmitted power level (local ODU)
In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm. In case of mute
status the value shown at management system is -100 dBm. If the power level read is out of the allowed
range, the value shown by the management system is -101 dBm.
Radio analog received power level (local ODU)
In case of ICP or Cable Loss alarms the value shown at management system is -99.8 dBm. In case of
failure on reading the register containing the received power the value shown at management system is
-99.7 dBm. If the power level read is out of the allowed range, the value shown by the management
system is -101 dBm.
Radio analog transmitted power level (remote ODU)
In case of broken radio link the value shown at management system is -99.6 dBm. In case of mute status
the value shown at management system is -100 dBm. In case of failure on reading the register containing
the remote transmitted power the value shown at management system is -99.7 dBm. If the power level
read is out of the allowed range, the value shown by the management system is -101 dBm. In case of
alarms on the remote NE on one of the two radio channels in HSB configuration (typically ICP, Cable
Loss, Crad Missing, Card Fail), the value shown by the management system is -127 dBm.
Radio analog received power level (remote ODU)
In case of failure on reading the register containing the remote received power the value shown at
management system is -99.7 dBm. If the power level read is out of the allowed range, the value shown
by the management system is -101 dBm. In case of alarms on the remote NE on one of the two radio
channels in HSB configuration (typically ICP, Cable Loss, Card Missing, Card Fail), the value shown by
the management system is -127 dBm.
3JK Edition 2.0
1 1 411
14.4 Measurement
14.4.1 How to read a Power Measurement file
Tick the Read File box and press the Select File button.
The directory of the WebEML automatically opens to navigate and get
the power measurement file.
Select the desired file and click the Open. The selected file will appear
in the Log file field.
Click button Start (on the right side of the Sample Time field). The file
opens.
The buttons in the lower part of the window allow to flow the graph
within the measurement interval.
N.B. As default the measurement files are stored in the MPRE_CT_Vxx.xx.xx directory and have extension
.txt.
Note: The measurement file can be opened also with a standard text editor (e.g. WordPad). Go in the
directory where the txt files have been stored and open the file. The measurements are shown in the
tabular mode.
3JK Edition 2.0
1 1 412
14.5 Loopback
The functions described in this section allow to perform the test
operations by loopbacks.
In the Resource List Area are listed all the loopbacks which can be
performed.
In the current software version the following loopbacks can be
implemented:
IF cable loopback with ODU300
Core-facing and Radio-facing loopbacks with MPT-HC and MPT-MC
In this area the following information is given:
1) Interface: the number of the channel and the type of the loopback
2) Direction: the type of the loopback
3) Activation: the activation status of a loopback (Active/Not Active)
4) Activation date: the date of loopback activation
5) Timeout: the timeout period, if has been set.
Resource Tree Area: displays the object on which the loopbacks can be performed, sorted by number.
Resource List Area: displays tabular information about the loopback supported by the resource selected
in the tree area.
Resource Detail Area: displays, through tabbed windows, the properties done in list area. This area
enable to perform the available functions for the involved resource.
N.B.: The loopbacks can be activated on the local NE only.
3JK Edition 2.0
1 1 413
14.5 Loopback [cont.]
Loopback with ODU300
In the figure is given the association of the loopback and the position in the block diagram of the equipment
provided by the Summary Block Diagram View option, available in the Diagnosis menu.
3JK Edition 2.0
1 1 414
14.5 Loopback [cont.]
Loopbacks with MPT-HC and MPT-MC
In the figure is given the association of the loopback and the position in the block diagram of the equipment
provided by the Summary Block Diagram View option, available in the Diagnosis menu.
3JK Edition 2.0
1 1 415
14.5 Loopback
14.5.1 How to activate a loopback
[1] This operation must be done only with the Modem unit connected
with ODU300. Before to activate the loopback mute the Transmitter.
Double click on the front panel of the Modem unit and enter the
Settings tab-panel.
[2] Select the loopback to be activated by clicking on the relevant
object in the Resource Tree Area or by selecting the relevant row in the
Resource List Area.
[3] Select Active in the Activation field.
[4] Click on Apply.
[5] The Loopback is now ACTIVE (in the row in the Resource List Area
the Activation field of the relevant loopback will change from Not
Active to Active).
Note: The loopback are active only on the cross-connections with TDM2TDM and TDM2Eth profiles.
Note: In the Timeout Period field a timeout period can be set for the loopback activation (max. 4 days). At
the end of this period the loopback will be automatically deactivated.
3JK Edition 2.0
1 1 416
14.5 Loopback
14.5.2 How to remove a loopback
[1] Select the suitable loopback to be removed by clicking on the
relevant object in the Resource Tree Area or by selecting the relevant
row in the Resource List Area.
[2] Select Not Active in the Activation field.
[3] Click on Apply.
[4] The Loopback is now DEACTIVATED (in the row in the Resource List
Area the Activation field of the relevant loopback will change from
Active to Not Active).
[5] Remove the squelch of the local Transmitter.
3JK Edition 2.0
1 1 417
14.6 Power Source
This menu is available only with MPT-HC and MPT-MC and it refers to
the 2 different modes to power supply the MPT:
QMA
PFoE
Two Sources are available because the MPT Access unit can interface two MPT.
If the Type is Disabled no power supply is provided to the MPT.
After the power supply selection click on Apply.
N.B.: The Alarm Profile field is not supported.
3JK Edition 2.0
1 1 418
14.6 Power Source [cont.]
Mode 1 - QMA (only with MPT-HC)
This mode is the default mode.
In this mode the MPT-HC is power supplied with a dedicated coaxial cable
connected on the QMA connector on the front panel of the MPT Access unit.
Mode 2 - PFoE (Power Feed on Ethernet)
In this mode the MPT-HC or MPT-MC are power supplied by using the
electrical Ethernet cable.
Warning: Check the MPT Access card P/N before to provide power supply to the PFoE port. To check the
P/N use the Remote Inventory facility.
Warning: To implement this mode with MPT-HC the DC Extractor must be installed, near the MPT-HC, to
separate the Ethernet traffic and the power supply.
Warning: If you connect directly (without the DC Extractor) the MPT-HC with PFoE, you can cause
irreversible damages to the MPT-HC.
3JK Edition 2.0
1 1 419
15 ATM view for ATM DOMAIN
3JK Edition 2.0
1 1 420
15 ATM view for ATM DOMAIN
15.1 ATM view for ATM DOMAIN
The configuration of the ASAP unit is divided in four tab-panels:
E1 Layer
IMA Layer
ATM Layer
ATM PW Layer
Warning: Migrations to MPR-E 2.1.
All the ATM PW flows configured on the NE but not yet cross-connected must be deleted before
performing the download of the MPR-E 2.1 SW Package. Otherwise, with the MPR-E 2.1 SW Package, later
configuration related to these ATM PW flows can lead to incoerent DataBase contents.
3JK Edition 2.0
1 1 421
15.1.1 E1 Layer
ASAP E1 Layer view
This menu allows to configure the physical E1 layer.
To configure the E1 layer:
1. Select the E1 port# (from 1 to 16)
2. Select the Signal mode: Framed/Disabled
3. Select the Clock mode: node-timed/loop-timed.
4. Click on Apply.
Note: By clicking on Apply To All the same configuration will be applied to the 16 E1 ports.
Note: The line impedance is fixed to 75 ohm or 120 ohm.
Note: The Alarm Profile is not implemented in the current release.
3JK Edition 2.0
1 1 422
15.1.2 IMA Layer
ASAP IMA Layer view
In the ASAP unit max. 8 IMA groups can be created.
To configure an IMA group:
1. Select the IMA group (from #01 to #08).
2. Enter the Near End ID (this identifier will be written in the ATM cells of the IMA protocol).
3. Enter the Min number of links (this is the minimum numbers of working E1 links, with which the IMA
group is still operational).
4. Enter the Max Differential Delay (in ms) between the E1 streams of the IMA group.
5. Click on Apply in the IMA Group Parameters are.
6. Select the E1 streams, which will be associated to the IMA group, by putting a check mark in the Add
check box. Up to 16 E1 links can be associated to the same IMA group.
7. Click on Apply in the IMA Link Table area.
Note: When an E1 has to be removed from an IMA group it is necessary, before applying the operation, to
set the administrative status to down. In this case there is no affect on the traffic.
Note: The Administrative Status must be set to Up in the ATM Layer tab-panel.
3JK Edition 2.0
1 1 423
15.1.2 IMA Layer [cont.]
By clicking on the Monitor in the Link column in the IMA Link Table
area, the screen in Figure opens.
This screen is a read-only screen in which all the parameters regarding the E1 link are shown.
3JK Edition 2.0
1 1 424
15.1.2 IMA Layer [cont.]
By clicking on the IMA Group Monitoring the screen in Figure opens.
This screen is a read-only screen in which all the parameters regarding the IMA group are shown.
3JK Edition 2.0
1 1 425
15.1.3 ATM Layer
ATM Layer Configuration
VP Layer Configuration
VC Layer Configuration
3JK Edition 2.0
1 1 426
15.1.3 ATM Layer
15.1.3.1 ATM Layer Configuration
By clicking in the ATM # mode, as shown in Figure, the ATM Interface
type can be selected: UNI or NNI.
ATM Interface type
Each ATM interface (from #01 to #08) is an IMA group.
To activate an IMA group set the Admin Status to Up and click on Apply.
3JK Edition 2.0
1 1 427
15.1.3 ATM Layer
15.1.3.1 ATM Layer Configuration [cont.]
ASAP ATM Layer view
3JK Edition 2.0
1 1 428
15.1.3 ATM Layer
15.1.3.2 VP Layer Configuration
Create a VPI
To create a new VPI click on Create VPI. The next screen opens.
3JK Edition 2.0
1 1 429
15.1.3 ATM Layer
15.1.3.2 VP Layer Configuration [cont.]
The definition of a VP over an ATM i/f is performed by the
configuration the following parameters:
VPI: in the range 0 to the value configured for the ATM i/f ;
VP role: Not Logical (Connection end-point) or Logical (Termination end-
point).
Ingress and Egress Traffic Descriptors: For each VP it is possible to associate
its ingress and egress ATM Traffic Descriptors.
This applies in both cases of VP configured as Connection or Termination end-
point. In the latter case, the VP ATM Traffic Descriptor is used only to
characterize the available bandwidth for ATM Admission Control function.
Click on Browse (the next screen opens for the Ingress Traffic Descriptor) and
select the TD in the Select TD field and click on OK.
If the VP Role is configured as VP Connection end-point, then:
ATM PW Service will be done in VPC mode, that is transport of ATM traffic into Ethernet frames is done by
encapsulating all ATM cells (i.e. for all VCs transported by that VP) with the configured VPI into the same
Ethernet flow;
VP ATM Traffic Descriptor will be directly used to derive the traffic characteristic of the related ATM PW
Ethernet flow.
If the VP Role is configured as VP Termination end-point, then:
ATM PW service will be done in VCC mode, that is transport of ATM traffic into Ethernet frames is done by
encapsulating into the same Ethernet flow only the ATM cells belonging to the same VC (with the
configured VPI);
the VP configuration actually defines a "logical" ATM i/f, a specific VCI range can be configured by NMS
through SNMP interface for that VP (within the range previously configured for the ATM i/f); by ECT
instead, this parameter is not configurable (that is the default range for the ATM i/f range applies);
VP ATM Traffic Descriptor is not used to derive the traffic characteristic of the related ATM PW Ethernet
flow(s) but only to define the available bandwidth for "logical" ATM i/f (in ordet to perform ATM Admission
Control at VC level);
ATM Policing and Shaping are not applicable at VP level (but instead are to be configured at VC level).
3JK Edition 2.0
1 1 430
15.1.3 ATM Layer
The TD must be previously created in menu Configuration -> Traffic
Descriptors.
Ingress Policing: this field allows to configure the policing in Ingress.
Egress Shaping: this field is a read-only field. The shaping is automatically
assigned according to the Service Category.
The configuration of a Traffic Descriptor associated to a Logical VP must be:
Service Category = CBR
PCR = sum of PCR of its CBR type VCs and MDCR of its UBR+ type VCs
CDVT = don't care
Policing = don't care
3JK Edition 2.0
1 1 431
15.1.3 ATM Layer
Edit VPI
To modify a previously created VPI select the VPI from the Available VP list
and click Edit VPI.
Change the parameters and click on Apply.
Delete VPI
To delete a previously created VPI select the VPI from the Available VP list
and click Delete VPI.
For every created VP an ATM Admission Control is performed in order to
check that the resulting allocated bandwidth is less or equal to the
bandwidth available on the ATM i/f.
This applies in both cases of VP that is being configured as Connection or
Termination end-point.
In case the resulting allocated bandwidth is greater than the ATM i/f
available bandwidth, the VP definition cannot be performed and an error
indication is returned.
Note: The VPI can be modified only if it is not involved in cross-connection. Otherwise the cross-connection
must be deleted, the PWE3 must be deleted and the VPI set to "Not in service".
Note: The VPI can be deleted only if it is not involved in cross-connection. Otherwise the cross-connection
must be deleted, the PWE3 must be deleted and the VPI set to "Not in service".
Note: If the VP contains the VC, the VC must be removed.
Note: VP ATM Admission Control.
3JK Edition 2.0
1 1 432
15.1.3 ATM Layer
The allocated bandwidth is computed as the sum of the egress VP ATM Traffic
Descriptor parameters, according to the type of Traffic Contract (ATM Service
Category/Conformance Definition pair) reported in the below table:
In case of VP that is being configured as Termination end-point, the egress VP
ATM Traffic Descriptor parameter defined in the above table is also defining
the available bandwidth for the related "logical" ATM i/f.
MDCR (= 0) CBR.1 ubr
MDCR (> 0) CBR.1 ubr+
PCR CBR.1 Cbr
VP/VC Bandwidth Conformance Definition Service Category
3JK Edition 2.0
1 1 433
15.1.3 ATM Layer
15.1.3.3 VC Layer Configuration
The VC Layer Management is used to define the characteristics of the
VCs transported over an already configured VP.
The VC Layer Configuration and relevant buttons are available only if a
VPI has been configured Logical as VP Role.
Create VCI
To create a VCI select the relevant VP in the Available VP list and click
on Create VCI. The next screen opens.
3JK Edition 2.0
1 1 434
15.1.3 ATM Layer
15.1.3.3 VC Layer Configuration [cont.]
The definition of a VC (over an already configured VP) is performed by
the configuration the following parameters:
VCI: in the range from 32 to the value configured for the underlaying logical
(VP) ATM interface
Ingress and Traffic Descriptor. For each VC it is possible to associate its
ingress and egress ATM Traffic Descriptors.
Click on Browse (the next screen opens for the Ingress Traffic Descriptor) and
select the TD in the Select TD field and click on OK.
The TD must be previously created in menu Configuration -> Traffic
Descriptors.
Ingress Policing: this field allows to configure the policing in Ingress.
Egress Shaping: this field is a read-only field. The shaping is automatically
assigned according to the Service Category.
3JK Edition 2.0
1 1 435
15.1.3 ATM Layer
15.1.3.3 VC Layer Configuration [cont.]
Edit VCI
To modify a previously created VCI select the VCI from the Available VC list
and click Edit VCI.
Change the parameters and click on Apply.
Delete VCI
To delete a previously created VCI select the VCI from the Available VC list
and click Delete VCI.
For every created VC an ATM Admission Control is performed in order to
check that the resulting allocated bandwidth is less or equal to the
bandwidth available on the underlying VP, that is the "logical" ATM i/f.
In case the resulting allocated bandwidth is greater than the "logical" ATM i/f
available bandwidth, the VC definition cannot be performed and an error
indication is returned.
The allocated bandwidth is computed as the sum of the egress VC ATM Traffic
Descriptor parameters, according to the type of Traffic Contract (ATM Service
Category/Conformance Definition pair).
Note: The VCI can be modified only if it is not involved in cross-connection. Otherwise the cross-connection
must be deleted, the PWE3 must be deleted and the VCI set to "Not in service".
Note: The VCI can be deleted only if it is not involved in cross-connection. Otherwise the cross-connection
must be deleted, the PWE3 must be deleted and the VCI set to "Not in service".
Note: VC ATM Admission Control.
3JK Edition 2.0
1 1 436
15.1.4 ATM PW Layer
3JK Edition 2.0
1 1 437
15.1.4 ATM PW Layer
15.1.4.1 ATM PW Parameters
To configure an ATM PW Layer select the Interface (from #01 to #08),
enter the following parametrs and click on Apply.
PW Label: it is possible to configure for each ATM PW, only one value, to be
assigned to both Inbound (Packet -> ATM direction) and Outbound (ATM ->
Packet direction) PW Labels. The value must be in the range: 16-65535.
Since de-multiplexing of ATM PW flows towards ATM interface is based on
ATM PW Inbound Label value, a check on all Inbound values, configured on
the same NE, must be done in order to avoid duplications.
The remaining fields of the 32-bit PW Label to be inserted into ATM PW
frames will be assigned as below reported:
3-bit EXP field is assigned according to the ATM PW flow CoS
1-bit S field is set to 1 (Bottom of Stack)
8-bit TTL is set to 255
Click on Create to configure another ATM PW.
To delete an ATM PW select the ATM PW and click on Delete.
3JK Edition 2.0
1 1 438
15.1.4 ATM PW Layer
15.1.4.1 ATM PW Parameters [cont.]
VPC/VCC Mode: it is possible to configure to have ATM PW Service in:
VPC mode, i.e the multiplexing of one (N=1) or more (N>1) VPs to the same ATM PW Ethernet
flow;
VCC mode, i.e the multiplexing of one (N=1) or more (N>1) VCs, belonging to the same VP, to the
same PWE3 ATM flow, will be supported.
In order to perform an ATM PW Service in VPC mode, the related VP must had be previously
configured at ATM Layer as Connection end-point.
In order to perform an ATM PW Service in VCC mode, it must had been previously configured at
ATM Layer the related VP, as Termination end-point, and VC.
Max Cell Concatenation and Max Delay (timeout): for each ATM PW flow it is possible
to configure how ATM cells will be concatenated into the same Ethernet packet:
1. a timeout, after the reception of first ATM cell, expires;
2. a maximum number of concatenated ATM cells is reached
The above configuration parameters allow, for each ATM PW, to find the trade-off between
latency and ATM PW encapsulation overhead.
The timeout is configurable in the range 0.1 to 40 ms, with 0.1 ms steps. Default value is 1 ms.
The maximum number of concatenated cells is is configurable by ECT/NMS in the range 1 to 28
cells, with 1 cell step . Default value is 1 cell (limitation for Cell Concatenation).
In this release the following limitations apply:
only timeout values from 1 to 10 ms, with 1 ms step, are configurable and tested;
only maximum cell concatenation number 1, 2, 4, 5, 10, 28 cells are configurable and tested.
If in VPC mode, the VPI only can be changed. If in VCC mode, the VPI only, the VCI only or both can be
changed.
3JK Edition 2.0
1 1 439
15.1.4 ATM PW Layer
15.1.4.1 ATM PW Parameters [cont.]
Admin Status: this field is a read-only field. The status is automatically set to "up",
when a cross-connection is established and set to "down", when a cross-connection is
deleted.
3JK Edition 2.0
1 1 440
15.1.4 ATM PW Layer
15.1.4.2 VPI/VCI Translation
For each ATM PW flow, it is possible to change the VPI/VCI value of
transported cells to a different value from that used in the ATM VP/VC
configuration.
Ingress VPI/VCI Translation (ATM -> Ethernet direction): VPI/VCI value can
be changed to a configurable value in the ATM Cell(s) encapsulated into ATM
PW Ethernet frames:
if the ATM PW is configured in VPC mode, only VPI can be changed, with range from
0 to 255 or 4095 according to UNI or NNI configuration of related ATM interface;
if the ATM PW is configured in VCC mode, then VPI, VCI or both can be changed, with
range from 0 to 65535
No check shall be performed on the new VPI/VCI values against the VPI/VCI
range foreseen for ATM i/f (VPC mode) or terminating VP (VCC mode).
Egress VPI/VCI Translation (Ethernet -> ATM direction): whatever is the
VPI/VCI value within ATM cell(s) transported by ATM PW frame, it is changed
into the ATM Cells sent towards ATM interface to the configured value of
related VP (in case of VPC mode) or VC (VCC mode).
3JK Edition 2.0
1 1 441
16 Core-E view for Core-E and Ethernet
domain
3JK Edition 2.0
1 1 442
16 Core-E view for Core-E and Ethernet domain
16.1 Core-E domain
The Core-E domain multiple main view contains two tab-panels:
Ethernet Physical Interface
TMN Interface
Core-E Main view
Resource Tree, displaying Ethernet physical interface with related port number;
Resource List, displaying tabular information about tributaries in tree area;
Resource Detail, providing access to Core-E detail view Alarms and Settings.
3JK Edition 2.0
1 1 443
16.1 Core-E domain
This tab-panel refers to the Ethernet ports, which can be used as traffic
ports and includes two tab-panels:
Alarm tab-panel
Settings tab-panel
If the optional SFP optical plug-in has been enabled in the Core-E unit in port #5 and/or in port #6 (refer to
Equipment menu) also the relevant Ethernet Port # will appear (see Figure above).
3JK Edition 2.0
1 1 444
16.1.1.1 Alarm tab-panel
Alarm view shows the Ethernet ports-related alarms.
Selecting the node in Tree area allows checking Ethernet tributary
alarms current state.
3JK Edition 2.0
1 1 445
The Settings view performs all the available functions for Ethernet tributary ports. Information related to a data port configuration is
provided by the following parameters:
Warning: Before enabling an Ethernet port, when the Static LAG Criteria and the Ethernet Interface Criteria for 1+1 EPS Core
features have been enabled in Menu Configuration > System Settings, it is recommended first to disable the Ethernet Interface
Criteria for 1+1 EPS Core feature. This feature could be enabled again after that this additional port has been properly configured.
No traffic impact is foreseen with this operation.
N.B.: Only asymmetric pause capability can be configured to transmit pause frame but not receive pause frame on the Ethernet
ports. If a pause frame is received on Ethernet ports such frame is dropped. Default values for manual mode are 100 Mbit/s, full
duplex, pause disable
Advertised Capability (10 Mb/s Half Duplex, 10 Mb/s Full Duplex, 100 Mb/s Half Duplex, 100 Mb/s Full Duplex). The
Restart button allows forcing auto-negotiation to begin link re-negotiation.
VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged. For each port it is possible to
configure:
Admit all (tagged and untagged frames are allowed in ingress). Default value: Admit all.
Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields, to be added in ingress to
untagged frames, must be configured. Only VLAN-ID values already defined (in the VLAN management menu) can be configured for
this purpose. The Priority values allowed are in the range 0 - 7.
The default Port VLAN-ID and Priority values are: VLAN-ID=1; PCP=0.
The VLAN 1 is always removed, when the frame is forwarded.
N.B.: Untagged frames - The untagged frames received on one user Ethernet port, configured as Admit tagged only, are
dropped.
N.B.: Priority frames - The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as Admit tagged only,
are dropped. The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit all configuration enabled, are
managed as untagged frames for VLAN-ID field, while the Priority field is the same of the received packets.
Synchronous Ethernet Operation Mode - From the Ethernet traffic interfaces (configured as 1000 Mb/s) it is possible to recover the
physical Rx synchronization signal or to deliver the Network Element Clock synchronization signal (in this case the Ethernet port must
be set as Sync-E Master). This feature is needed in order to realize "synchronous Ethernet Networks" addressed by G.8261. Enable the
Synch-E mode by setting Synchronous and selecting the operating mode: Master or Slave. Note: If the electrical Ethernet port has to
be used as Synchronous Source, the Ethernet port must be set as Synch-E Slave.
3JK Edition 2.0
1 1 446
16.1.1.3 Settings tab-panel (Ethernet Port#5 and #6)
The Settings view performs all the available functions for Ethernet tributary port#5. Information related to the port configuration is
provided by the following parameters:
Warning: Before enabling an Ethernet port, when the Static LAG Criteria and the Ethernet Interface Criteria for 1+1 EPS Core
features have been enabled in Menu Configuration > System Settings, it is recommended first to disable the Ethernet Interface
Criteria for 1+1 EPS Core feature. This feature could be enabled again after that this additional port has been properly configured.
No traffic impact is foreseen with this operation.
N.B.: Only asymmetric pause capability can be configured to transmit pause frame but not receive pause frame on the Ethernet
ports. If a pause frame is received on Ethernet ports such frame is dropped. Default values for manual mode are 100 Mbit/s, full
duplex, pause disable
Advertised Capability (1000 Mb/s Full Duplex). The Restart button allows forcing auto-negotiation to begin link re-negotiation.
Optical Info field: it is a read-only field.
VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged. For each port it is possible to
configure:
Admit all (tagged and untagged frames are allowed in ingress). Default value: Admit all.
Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields, to be added in ingress to
untagged frames, must be configured. Only VLAN-ID values already defined (in the VLAN management menu) can be configured for
this purpose. The Priority values allowed are in the range 0 - 7.
The default Port VLAN-ID and Priority values are: VLAN-ID=1; PCP=0.
The VLAN 1 is always removed, when the frame is forwarded.
N.B.: Untagged frames - The untagged frames received on one user Ethernet port, configured as Admit tagged only, are
dropped.
N.B.: Priority frames - The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as Admit tagged only,
are dropped. The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit all configuration enabled, are
managed as untagged frames for VLAN-ID field, while the Priority field is the same of the received packets.
Synchronous Ethernet Operation Mode - From the optical Ethernet traffic interface it is possible to recover the physical Rx
synchronization signal or to deliver the Network Element Clock synchronization signal (in this case the Ethernet port must be set as
Sync-E Master). This feature is needed in order to realize "synchronous Ethernet Networks" addressed by G.8261. Enable the Synch-E
mode by setting Synchronous.
3JK Edition 2.0
1 1 447
16.1 Core-E domain
16.1.2 TMN Interface
The interfaces are of two types:
1) TMN Ethernet on a dedicated connector
2) Port #4 of the Ethernet traffic ports, which can be dedicated to TMN
purpose and not to traffic.
This tab-panel has 2 tab-panels:
Alarm tab-panel
Settings tab-panel
3JK Edition 2.0
1 1 448
16.1.2.1 Alarms tab-panel
Alarm view shows the Ethernet ports-related alarms.
Selecting the node in Tree area allows checking Ethernet tributary
alarms current state.
3JK Edition 2.0
1 1 449
16.1.2.2 TMN In-band
The TMN In-Band feature allows the extension of the DCN over User Ethernet interfaces used to carry user
traffic.
Two default TMN In-Band interfaces (TMN In-band #1 and #2) are supported, each having its own IP address
and subnet.
The TMN traffic delivered In-Band is VLAN tagged and identified by a specific VLAN ID defined by the
operator in the range 2-4080.
The delivery of TMN In-Band can be enabled on all User Ethernet interface of the Core board, both Optical
and Electrical.
Note 1: the Ethernet ports involved in a LAG cannot be used as TMN In-band interface.
Note 2: If the TMN In-band interface has been configured and the traffic classifier is according to 802.1p,
the priority on the TMN traffic is highest. If the traffic classifier is according to DiffServ, the priority on the
TMN traffic is low and the traffic on the other Ethernet ports must be taken in consideration.
Note 3: If two Ethernet ports, associated to the same TMN In-band logical interface, are segregated, the
two ports do not communicate each other, as for the normal Ethernet traffic (they have the same VLAN ID).
If two Ethernet ports, configured in different TMN In-band logical interfaces, are segregated, the two ports
can communicate each other, as they have 2 different VLAN IDs).
The OSPF and related Area ID can be enabled on a TMN In-Band interface.
For each TMN In-Band interface the following parameters must be selected:
IP address and subnet: default 10.0.3.2/24 for interface #1 and 10.0.4.2/24 for interface #2
VLAN ID: default 4097 for interface #1 and interface #2
List of User Ethernet interfaces where transmit/receive TMN In-Band traffic: default None (multiple
selection or deselection can be done by holding the Ctrl key, while clicking on one or more entries)
OSPF enable/disable: default disabled for both interfaces
Area ID in case of OSPF protocol enabled: default 0.0.0.0
3JK Edition 2.0
1 1 450
16.1.2.3 TMN Ethernet port
If used, the TMN Ethernet must be:
Enabled.
Assigned an IP address with its IP mask.
Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also the area
number.
Click on the Alarm Profile icon to open the Alarm Severity Profile menu to associate to the TMN Ethernet
port a specific alarm profile. Select one Alarm Profile in the Profile Name list (4 alarm profiles are
listed). Tick the Show details check box to see the severity associated to each alarm.
Click on Apply to activate the selections.
3JK Edition 2.0
1 1 451
16.1.2.4 TMN Ethernet Port #4
If the Ethernet Port 4 has been used as TMN port, the port 4 must be:
Enabled.
Assigned an IP address with its IP mask.
Selected the IP Routing Protocol: Static Routing or OSPF. If OSPF has been selected, assign also the area
number.
Click on Apply to activate the selections.
3JK Edition 2.0
1 1 452
16.1 Core-E domain
16.1.3 Ethernet LAG
If in the Configuration > Ethernet Features Shell menu have been created the Ethernet LAGs (Link
Aggregation Group), the created Ethernet LAGs will appear in the Ethernet Physical Interface tab-panel as
shown in the figure. In the figure two LAGs have been created (Port #1 and Port #11).
3JK Edition 2.0
1 1 453
16.1 Core-E domain
16.1.3 Ethernet LAG [cont.]
Each Ethernet LAG has its Setting tab-panel.
In this tab-panel only the VLAN configuration field can be modified (all the other fields are read-only).
VLAN configuration. The traffic, received on each user Ethernet port, can be untagged or tagged. For
each port it is possible to configure:
Port VLAN ID: if the Acceptable Frame Type is set to Admit all the VLAN-ID and Priority fields (to be
added in ingress to untagged frames), must be configured. Only VLAN-ID values already defined (in the
VLAN management menu) can be configured for this purpose. The Priority values allowed are in the
range 0 - 7.
N.B.: Untagged frames
The untagged frames received on one user Ethernet port, configured as Admit tagged only, are
dropped.
N.B.: Priority frames
The priority packets (VLAN-ID=0) received on one user Ethernet port, configured as Admit tagged
only, are dropped.
The priority packets (VLAN-ID=0) received on one user Ethernet port, with the Admit all configuration
enabled, are managed as untagged frames for VLAN-ID field, while the Priority field is the same of the
received packets.
3JK Edition 2.0
1 1 454
16.1.3 Ethernet LAG
16.1.3.1 MPT-HC connected to the Core-E
The electrical Ethernet ports#1 to 4 or the Ethernet port #5 or/and #6 can be used to connect an MPT. In
this case a new tab-panel will appear which allows to access directly to the MPT menu.
Note: Ethernet ports#1 to #4 can be used to connect on MPT-MC or MPT-HC; Ethernet ports#5 and #6 can be
used to connect only an MPT-HC (port#5 and #6 are available by installing the relevant SFP).
In the example an MPT-HC (tab-panel Port #5) has been connected to Port #5.
The Ethernet Port #5 is not available as an Ethernet Physical Interface: it has been removed from the
Tributaries Data list.
3JK Edition 2.0
1 1 455
17 AUX view for AUX DOMAIN
3JK Edition 2.0
1 1 456
17 AUX view for AUX DOMAIN
17.1 AUX view for AUX DOMAIN
The AUX peripheral unit has two tab-panels:
Settings
External points
3JK Edition 2.0
1 1 457
17.1.1 Settings
To enable the 64 kbit/s user Service channel #1 or #2 set the Channel
Status to Enabled and click Apply.
Note: the Protocol Type is fixed to Synchronous 64 kbit/s RS422/V.11 DCE co-directional.
Note: The EOW Interface is not implemented in the current release.
3JK Edition 2.0
1 1 458
17.1.2 External Points
There are two types of external points:
input external points
output external points
By clicking on the tree root the tree will be expanded.
A single left click selection of a tree element causes the activation of
the corresponding Tabular representation displayed in the "Resource list
area" (upper righ side of the screen).
A click on a row in the Resource list area opens the Settings menu.
3JK Edition 2.0
1 1 459
17.1.2.1 Input External Points
An input external point is described by the following parameters:
Id: identification number
UserLabel: associates a user friendly name to an external point
Polarity: describes the polarity (Active Low/ Active High)
External State: describes the state (on /off)
Alarm Profile: describes the associated Alarm Profile (not implemented)
After a row selection, the user can modify the User Label, the Polarity.
The operator choices will be sent to NE after selecting the "Apply" button.
3JK Edition 2.0
1 1 460
17.1.2.2 Output External Points
Seven output external points are available.
The output external points (CPO#1 ... 7) are described by the following parameters:
Id: identification number
UserLabel: a user friendly name can be associated to an external point
Polarity: describes the polarity (Active Low/ Active High). In this field the polarity of the external point
can be changed.
Criteria: fixed to Manual. (The output can be activated manually). Note: the Automatic mode is not
supported in this release.
External State: describes the state (on /off). In this field the external point can be activated (on) or
deactivated (off).
The operator choices will be sent to NE by clicking on the "Apply" button.
3JK Edition 2.0
1 1 461
18 Annex A: Network Element Overview
3JK Edition 2.0
1 1 462
18.1 Main View
When NEtO starts, the main view screen is shown below.
This screen has three specific areas:
NE Configuration area: displays NE general information (left side);
Status & Alarms area: reports supervision status and alarms (right side).
Discovered NEs: in the lower part of the screen is shown the list of the discovered
NEs. With a double click on a row the IP address of the NE in the row automatically is
written in the NE Info field.
Show and Alarm Monitor buttons are enabled when a NE is supervised
only. Supervision starts as soon as the operator writes an IP address in the
specific field and press the OK button.
The Network Element Overview (NEtO) is the starting point of the WebEML application.
NEtO functions require to know the NE identity by means of the related IP Address.
Only one NE can be managed in a NEtO session.
The User Interface is provided by the NEtO Main View.
NEtO Main view can also be reduced by using the shrink glass ( ) button in the Menu Bar.
The reduced NEtO view allows the operator to save screen space while continuously checking supervision
and alarms status. Gray icons mean that supervision is not active.
The magnifying glass ( ) button allows to show the normal NEtO main view.
The alarm severity icon appears in operating system tray bar, close to system clock and other system
software icons.
This icon also has a specific tooltip, visible when mouse cursor is moved over it, that will show: name of
application, NE IP address, and highest severity alarms number. The tray-bar icon is present in the Windows
system bar (in the lower part of the screen). The tray-bar icon takes the color of the most severe alarm.
The tray-bar icon is not interactive and does not present any menu or executable command if clicked either
with left or right mouse button.
3JK Edition 2.0
1 1 463
18.2 NE Configuration area
The NE configuration area is divided in three sections:
1) NE Info section, containing information related to NE addressing;
2) NE Description section, with information about NE characteristics;
3) Command Buttons section, providing buttons to manage NEtO functions.
3JK Edition 2.0
1 1 464
18.2.1 NE Information
This area is related to the wanted NE identification.
IP Address field displays the actual NE IP address used by NEtO
functions.
OK button will start supervision on specified NE, if reachable. Keyboard shortcut Alt + o behaves as
clicking on OK button with mouse.
Whether the IP address is correctly written, other than clicking on OK button, supervision process will
start on specified NE by pressing enter (carriage return) key on keyboard.
3JK Edition 2.0
1 1 465
18.2.2 NE Description
This area contains some parameters displaying general information
about the supervised NE.
Parameters can be read and modified (and applied to NE using the
Apply button).
Please note that changing these labels values will also automatically update NEtO window title content:
window title will always contain Site Name of supervised NE. Keyboard shortcut Alt + a behaves the
same as clicking on Apply button with mouse.
3JK Edition 2.0
1 1 466
Command buttons available through NEtO are:
Show button will start WebEML (JUSM/CT) application on a
supervised NE.
Alarm Monitor button starts the Alarm Monitor application.
WTPMS button starts the WT Performance Monitoring Suite
application.
Buttons Show and Alarm Monitor will be enabled when NE is
supervised only.
Exit button will close NEtO, stopping a possibly running supervision
and closing all related applications.
18.2.3 Command Buttons
Keyboard shortcut Alt + S behaves as clicking on Show button with mouse. Keyboard shortcut Alt + m
behaves as clicking on Alarm Monitor button with mouse. Key-board shortcut Alt + E behaves as clicking
on Exit button with mouse.
3JK Edition 2.0
1 1 467
18.3 Status & Alarms area
Information on supervision status and active alarms are shown in this
area.
Round-shaped icons change their colours according to current NEtO functions and situation. With respect to
Supervision status:
green colour means that supervision function is ongoing,
red colour means that NE link does not work,
gray icons mean that supervision is not active (to be started).
Alarm synthesis contains the list of the alarms listed by severity: whether an icon is not grey, means that
such kind of severity contains one alarm at least.
The round-shaped icons change the colour and the letter inside according to the severity of the active
alarms:
orange (letter M): Major alarm
yellow (letter m): Minor alarm
blue (letter W): Warning alarm
Note: the Indeterminate alarms are not supported.
3JK Edition 2.0
1 1 468
18.4 Supervision Function
The supervision function allows operator registering a new manager
inside NE MIB and performing cyclic (periodic) monitoring on
connection.
To start supervision, the operator must specify NE IP address in the IP
Address field and then simply press OK button.
If supervision succeeds, screen is updated with information retrieved
from NE and supervision icon changes its colour from gray to green
stating NE is correctly supervised.
When a supervision error, a link down or other problems arise during
supervision, icon will become red. Alarm Synthesis area will be updated
as well. Clicking on Show button, NEtO will open the WebEML
(JUSM/WebEML) for MPR equipment.
To close an ongoing supervision, simply click on Exit button (this will
also close NEtO) or change NE IP address and click OK button to start
supervision procedure on a different NE (this will stop previous
supervision).
3JK Edition 2.0
1 1 469
18.5 MenuBar
(New)
(Open)
(Community String)
This icon opens the current list of the favourite NEs, if the list has
been previously saved.
(Magnifying glass)
NEtO Main view can also be minimized by using the shrink glass ( ) button.
Using both (New) and (Open) icons, the operator will be able to
open NEs table modal window (see following Figure).
Open icon allows opening a previously saved file containing a list of
NEs.
New icon allows creating a new list, specifying the file name
containing its data, only when those data will be saved.
NEtO can manage and organize a list of available NEs by showing operator a table containing such data.
3JK Edition 2.0
1 1 470
18.5 MenuBar [cont.]
NEtO List Management
Get Current button is used to read information from main NEtO view. This operation will always add a
new line in NE list table with all information related to currently supervised NE. This happens even though a
NE with corresponding IP address is still present in the list;
New button, adding a new NE from scratch. This allows the operator to fill the IP Address field only
with its needed NE.
Remove button, removing a selected NE;
Set Current button, filling main NEtO view IP address with datum from selected NE. The operator must
previously select a valid line in NEs table and then click on Set Current button so filling NEtO main
window data. This operation will automatically close the NE list window but does not start supervision on
set NE;
Save button, saving table list in a specified file.
To close this window click on Close button.
All data are saved in a custom XML format called NEtO and this structured file will contain all data shown
in Figure related to all NEs added to the list.
The operator can have its own NEs lists repository, containing all .NEtO files that it produced with NEs
information inside.
3JK Edition 2.0
1 1 471
18.6 Sequence for NEtO interface and NE list
1. Fill NEtO main view IP Address field with NE IP address;
2. Start supervision by clicking Ok button;
3. Open the NEs table (any method, through New or Open button);
4. Click on Get Current;
5. Save the list and Close the list window.
This operation will produce a clean and up-to-date NEs table list. The NE table lists are not updated, if the
operator will modify, NE site name site location or even IP address. Such data are used for references
purposes, but the operator must take care to keep them updated.
3JK Edition 2.0
1 1 472
18.7 CS (Community String)
To access the Community String menu click on the CS icon on the right
corner on the upper part of NEtO. The menu Community String Request
allows to get/change the data regarding the Community String, if
necessary, and only if the NE Administrator has defined a community
string (different from the default value) for the specific NE you want
to login. To proceed, you must know this string, and you must write it
before to start the Supervision of such NE.
3JK Edition 2.0
1 1 473
18.7 CS (Community String) [cont.]
Insert the Community String (1) then click OK (2).
Button Use Default resets the community string at the default value,
at NEtO side only.
Now, insert the NE IP address in the NE Info area, click on OK to start
the Supervision of such NE.
Warning: The same Community String must be inserted in the NE by using the WebInterface.
3JK Edition 2.0
1 1 474
Open a WEB_browser and enter http://IP address of the NE.
The following screen opens.
Enter:
User Name: initial;
Password: adminadmin.
3JK Edition 2.0
1 1 475
The WebInterface menu opens. Select menu Administration >
Community String and enter the Community String.
Warning: if a different CS is inserted in NEtO (different from the CS inserted in the NE), the supervision
does not start.
3JK Edition 2.0
1 1 476
Answer the Questions
Configure the equipment.
Enable the tributaries.
Create some cross-connections.
Set the Transmitter of Channel 1 to transmit a constant power.
Read the Rx power of Channel 1.
Read the RF frequency of Channel 1.
Show the current position of the switches (through their commands in
the WebEML).
Manually switch the 3 switches to the protecting channel (through their
commands in the WebEML).
Activate the loopback.
3JK Edition 2.0
1 1 477
Blank Page
3JK Edition 2.0
1 1 478
End of Module
Operator Interface MPR Node
3JK Edition 2.0
Module 2
Initial Configuration MPR Node
3JK Edition 2.0
Section 1
NE Operation
3JK Edition 2.0
NE Operation Initial Configuration MPR Node
1 2 2
Blank Page
First edition External Consultant 2007-07-30 01
Document History
3JK Edition 2.0
1 2 3
Objectives
Configure the equipment starting from a scratched NE.
3JK Edition 2.0
1 2 4
Objectives [cont.]
3JK Edition 2.0
1 2 5
Table of Contents
Page
1 Initial Configuration 7
1.1 General Requirements 8
1.2 Initial Turn-up 10
1.3 Enable Plug-In Cards 14
1.4 Provision Plug-In Cards 37
1.5 Provision ASAP Card 62
1.6 Provision AUX Card 64
1.7 Provision XPIC 66
1.8 Provision Synchronization 67
1.9 Provision NTP protocol 69
1.10 Provision NE Time 70
1.11 Provision VLAN 71
1.12 Provision Cross-connections 72
1.13 Provision AUX Cross-Connections 73
1.14 Provision Ethernet Ring 74
1.15 Provision LAG 75
1.16 Provision System 76
1.17 Provision Local NE IP Address 80
1.18 Provision TMN Ethernet Port 81
1.19 Provision Ethernet Port 4 for TMN (if required) 82
1.20 Provision TMN in-band 83
1.21 Provision IP Static Routing 84
1.22 Provision OSPF Static Routing 86
2 Provisioning by Provisioning tool 87
2.1 Start Provisioning Tool 88
2.2 Provisioning Tool screens 91
2.3 Configuration Options Screen 95
2.4 Core-E Configuration 96
2.5 E1 configuration 99
2.6 STM-1 configuration 100
2.7 Modem Provisioning 102
2.8 MPT Access configuration (1+0) 106
2.9 MPT Access Provisioning 107
2.10 MPT Access configuration (prot. enabling: 1+1) 112
2.11 MPT Access Prov. (without A. M.) (1+1) 113
2.12 MPT Access Prov. (with A. M.) (1+1) 115
2.13 Synchronization Configuration 117
2.14 XPIC Configuration 121
2.15 Ring Configuration 122
2.16 Cross Connections Configuration 123
2.17 Segregated Port Configuration 124
2.18 802.1D management 125
2.19 802.1Q management 126
2.20 VLAN Management 128
2.21 Port VLAN Configuration 129
2.22 Network Configuration 130
2.23 Trusted Managers 132
2.24 Typical Report Panel 133
Exercise 134
Blank Page 135
End of Module 136
3JK Edition 2.0
1 2 6
Page
3JK Edition 2.0
1 2 7
1 Initial Configuration
3JK Edition 2.0
1 2 8
1.1 General Requirements
PC HW Configuration
CPU: AMD Atlhon/Intel Celeron/Intel Pentium 4 or higher
RAM: 500 MB (1 GB recommended - strongly recommended with Windows
Vista)
Hard Disk space: 1.5 GB (available space for log files, JRE excluded)
Display Resolution: 1024x768 pixel
CD-ROM Drive: 24X
Ethernet Interface: Ethernet Card 10/100 Mbps
Operating Systems Supported
Microsoft Windows XP Professional service pack 3 or Microsoft Windows Vista
Ultimate service pack 2
3JK Edition 2.0
1 2 9
1.1 General Requirements [cont.]
Additional requirements
Microsoft Internet Explorer 6 SP1, 7, 8, Mozilla Firefox 2, 3, 3.5
The Administrator password is needed only for Java installation
When Java has been installed, the standard user can run the TCO Suite
Java Runtime Environment (JRE) 6 Update 14
Disable all Firewall software on PC used
3JK Edition 2.0
1 2 10
1.2 Initial Turn-up
1 - Copy software on PC.
Before operating the user system interface (USI) for the first time, the
programs contained on the CD ROM must be copied on the PC.
A - Insert CD ROM disk into PC.
B - On Windows desktop, double click on My Computer icon. My Computer window
displays.
C - In My Computer window, click on CD ROM icon. Files window displays
D - Copy Craft Terminal software on PC on a directory.
2 - Turn on the 9500MPR.
3 - Establish communication between equipment and Craft terminal
computer. Default NE IP address: 10.0.1.2
4 Startup
Follow the steps on following figures to open communication with the
equipment.
Note: if it is necessary to scratch the MIB use the following procedure.
Database scratch procedure:
1. Power off the equipment
2. Move the dip-switch 2 on the Core-E board.
3. Re-plug the Core-E board in the subrack.
4. When EC software starts, detects the switch position and starts with database scratch: all the
configuration information will be erased (radio parameters, synch, XCONN, network, ecc). The information
of SWP is maintained (the stand-by and active SWP banks are not deleted).
5. It is possible to understand when the scratch procedure is over: make a ping towards NE with default IP
address.
6. After this, plug-out the Core-E board and restore the original dip-switch 2 position.
7. Re-plug the Core-E board.
Note: Average time necessary to scratch the database (from SW start): 6-7 minutes.
3JK Edition 2.0
1 2 11
1.2 Initial Turn-up [cont.]
Startup Procedure
See next slide
O Enter the IP
Address or
DNS name
O Click OK
3JK Edition 2.0
1 2 12
OType your password
must not be less
than six (6) or more
than 20 characters
and must be
composed of full
ASCII characters set
(UPPER/lower case,
numeric and special
characters)
O Click on
Apply
O Type your
username must
not be more than
20 characters
O If the Supervision
is ongoing, click
Show
Note: Profile Types there are four user profiles defined.
Administrator (full access also for NMS local system security parameters).
CraftPerson: person in charge for installation and the mantenance at radio site; full access to NE but not for
security parameters, only for own password.
Operator (person in charge to operate at the network level, not at the radio side).
Viewer (view screens only).
Note: Default User Accounts at the NE installation time, two default user accounts are created on NE
independently from the SNMP operating mode.
Profile: administrator
Username: initial
Password: adminadmin
Profile: craftPerson
Username: Craftperson
Password: craftcraft
3JK Edition 2.0
1 2 13
Provisioning MPR
START
Enable Plug-In Cards
Provision Plug-In Cards
Provision Synchronization
Provision NE Time
Provision VLAN (if required)
Provision System
Provision management parameters
Provision NTP Protocol
Provision AUX Cross-Connections
Provision Ethernet Ring
Provision LAG
Provision Cross-Connections
Provision XPIC (if required)
Note: Changes to provisioning do not have to be made in any particular order.
See the figure for the recommended sequence.
Warning: If from this NE remote NEs have to be reached, remember to configure properly the Routing
Protocol of the PPP RF channel, if the remote NE is connected through the radio link or of the NMS Ethernet
Port, if the remote NE is connected through the Ethernet cable.
3JK Edition 2.0
1 2 14
All the cards that can be inserted in MSS4 or MSS8 chassis must be
enabled in the equipment section:
SFP optical plug-in
Spare CORE-E (in slot 2 only)
E1-PDH Access card
STM-1 Access card
Modem Access card (ODU300 interconnection)
MPT Access card (MPT interconnection)
AUX board
ASAP board
EAS board
FAN board
Enable the MSS cards by using the following procedures.
1.3 Enable Plug-In Cards
3JK Edition 2.0
1 2 15
1.3 Enable Plug-In Cards [cont.]
Enabling SFP optical
plug-in
O Apply the
Equipment
Type
O Click to start
O The Ethernet ports of the Core-E
can be configured in 2 ways:
1. to be used as GigaEthernet
interface for Ethernet traffic
(Note: for port#5 and port#6 the
optional SFP must be
installed);
2. to be used to connect an MPT:
MPT-HC or MPT-MC to
port#1 to port#4; an MPT-HC
only to port#5 and port#6.
O Settings
tab
3JK Edition 2.0
1 2 16
Enabling Spare
Core-E Card
O Click to start
O Choose Core-E from the dropdown menu for
the spare protected Core-E card in slot 2
O Settings tab
O Apply the
Equipment Type
Alarm Profile:
not supported
3JK Edition 2.0
1 2 17
Enabling E1
Access Card 1
O Click to start
O Choose the P32E1DS1 unit
O Settings tab
O Click to apply
changes
3JK Edition 2.0
1 2 18
Enabling E1
Access Card 2
O Click to start
O Choose the P32E1DS1 unit
O Settings tab
O Click to apply
changes
3JK Edition 2.0
1 2 19
Enabling
protection
O Click to start
O Select 1+1 EPS
O Settings tab
O Click to apply
changes
This operation must be done to enable the EPS protection.
3JK Edition 2.0
1 2 20
Enabling STM-1
Access Card 1
O Click to start
O Choose the SDHACC or
SDHCHAN unit
O Settings tab
O Click to apply
changes
3JK Edition 2.0
1 2 21
Enabling SFP for SDHACC
O Select the optical SFP (SFP-O) or the electrical
SFP (SFP-E) installed on the STM-1 ports (SFP#1
and/or SFP#2) and click Apply.
Note: It is not possible to enable SFP #1 and
SFP #2 at the same time.
3JK Edition 2.0
1 2 22
Enabling SFP for SDHCHAN
O Select the optical SFP (SFP-O) or the electrical
SFP (SFP-E) installed on the STM-1 port (SFP#1)
and click Apply.
3JK Edition 2.0
1 2 23
Enabling STM-1
Access Card 2
O Click to start
O Choose the SDHACC unit
O Settings tab
O Click to apply
changes
3JK Edition 2.0
1 2 24
Enabling
protection
O Click to start
O Select 1+1 EPS
O Settings tab
O Click to apply
changes
3JK Edition 2.0
1 2 25
Enabling Modem
Card 1
(to interface
ODU300)
O Click to start
O Settings tab
O Click to apply
changes
O Choose the MD300 unit
Note: ODU is automatically enabled when Modem Card is enabled.
3JK Edition 2.0
1 2 26
Enabling
Modem Card 2
O Click to start
O Settings tab
O Click to apply
changes
O Choose the MD300 unit
Note: ODU is automatically enabled when Modem Card is enabled.
3JK Edition 2.0
1 2 27
Enabling
Modem Card
protection
O Click to start
O Settings tab
O Click to apply
changes
O Select the suitable protection scheme
This operation must be done to enable the protection: 1+1 FD or 1+1 HSB.
3JK Edition 2.0
1 2 28
Enabling MPT
Access Card 1
(to interface
te MPT-HC and
MPT-MC)
O Click to start
O Settings tab
O Click to apply
changes
O Choose the MPTACC unit
3JK Edition 2.0
1 2 29
Enabling one port
in the MPT
Access Card
O Select as Usage MPT-HC or MPT-MC in one or
two Ports.
N.B. Port#1 and Port#2 are electrical Ethernet
ports and Port#3 and Port#4 are optical
Ethernet ports.
O Click on Apply
N.B.: Two unprotected or protected MPT-HC or MPT-MC can be connected to one MPT Access unit.
3JK Edition 2.0
1 2 30
Enabling MPT
Access Card 2
O Click to start
O Settings tab
O Click to apply
changes
O Choose the MPTACC unit
3JK Edition 2.0
1 2 31
Enabling one port
in the MPT
Access Card
O Select as Usage MPT-HC or MPT-MC in one or
two Ports.
N.B. Port#1 and Port#2 are electrical Ethernet
ports and Port#3 and Port#4 are optical
Ethernet ports.
O Click on Apply
3JK Edition 2.0
1 2 32
Enabling protection
O To configure the protection scheme
select the MPT-HC. (In the example
MPT-HC#31: connected to Port#1 of
the MPT Access unit in Slot#3)
O Settings
tab
O Click to apply
changes
O Select the suitable
protection scheme
This operation must be done to enable the protection: 1+1 FD or 1+1 HSB.
3JK Edition 2.0
1 2 33
Enabling ASAP
Card
O Click to start
O Settings tab
O Click to apply changes
O Choose the P8ETH unit
3JK Edition 2.0
1 2 34
Enabling EAS
Card
O Click to start
O Settings tab
O Click to apply changes
O Choose the P8ETH unit
3JK Edition 2.0
1 2 35
Enabling AUX
Card
O Click to start
O Settings tab
O Click to apply
changes
O Choose the AUX unit
3JK Edition 2.0
1 2 36
Enabling Fan
Unit
O Click to start
O Settings tab
O Click to apply
changes
O Select the FANS
3JK Edition 2.0
1 2 37
1.4 Provision Plug-In Cards
Core-E Card Provisioning (Ethernet ports 1-4)
Go to next page
O Double left click
3JK Edition 2.0
1 2 38
1.4 Provision Plug-In Cards [cont.]
Core-E Card Provisioning (Ethernet ports 1-4)
O Check to enable the
selector port. Uncheck
to disable first in order
to change any settings.
Current provisioning for Ethernet
Ports #01-#04. Area updates when
Apply buttons are clicked
O Check to enable
input and output pause
features.
O For the configuration
refer to the Core-E unit.
O Check to allow
communication at the
selected data rate between
two locations. Choose half
duplex for only one
direction at a time, or full
duplex for communication
in both directions at the
same time.
O Check to enable NE auto-
negotiation functions.
O Click this Apply button.
G Click Apply button.
O From the Ethernet traffic
interfaces (configured as
1000 Mb/s) it is possible to
recover the physical Rx
synchronization signal or to
deliver the Network Element
Clock synchronization signal
(in this case the Ethernet
port must be set as Sync-E
Master). Enable the Synch-E
mode by setting Synchronous
and selecting the operating
mode: Master or Slave.
Note (9): If the electrical Ethernet port has to be used as Synchronous Source, the Ethernet port must be
set as Synch-E Slave.
3JK Edition 2.0
1 2 39
Core-E Card Provisioning (Ethernet port 5)
Go to next page
O Double left click
3JK Edition 2.0
1 2 40
Core-E Card Provisioning (Ethernet port 5)
O Check to enable the
selector port. Uncheck to
disable first in order to
change any settings.
Current provisioning for Ethernet
Port #05. Area updates when Apply
buttons are clicked.
OCheck to enable
input and output pause
features.
The Optical Info field is a
read-only field not
implemented in the current
release.
OCheck to enable NE
auto-negotiation functions.
O Click this Apply button.
O Click Apply button.
OFor the configuration
refer to the Core-E unit.
O From the Ethernet
traffic interfaces
(configured as 1000
Mb/s) it is possible to
recover the physical Rx
synchronization signal
or to deliver the
Network Element Clock
synchronization signal
(in this case the
Ethernet port must be
set as Sync-E Master).
Enable the Synch-E
mode by setting
Synchronous and
selecting the operating
mode: Master or Slave.
Note (7): If the electrical Ethernet port has to be used as Synchronous Source, the Ethernet port must be
set as Synch-E Slave.
3JK Edition 2.0
1 2 41
PDH Access Card Provisioning
Go to next page
O Double left click
3JK Edition 2.0
1 2 42
PDH Access Card Provisioning (TDM2TDM)
O
OSee details
O Choose TDM2TDM if
radio is being used
to transport E1 data
only (no Ethernet).
O O
O Flow ID number required to
transport E1 data.
Flow Id number: is system unique and must not be repeated in radio network. Loss of E1 data can occur.
3JK Edition 2.0
1 2 43
PDH Access Card Provisioning (TDM2ETH)
O
O O
O
O
O Flow ID number required to
transport E1 data.
OSee details
O
Flow Id number: is system unique and must not be repeated in radio network. Loss of E1 data can occur.
3JK Edition 2.0
1 2 44
PDH Access Card
Details
O Select Disabled if port (E1 line) is not:
being used as a source or destination (typical choice for a line
not being used at a terminal or not being dropped and inserted
at a repeater);
being dropped or inserted (typical choice for a line being passed
through at a through repeater and not being dropped and
inserted at a drop and insert repeater).
Select Framed: to be able to collect the performances at the input
in Tx side and at the output in Rx side.
Select Unframed:
being used as a source or destination (typical choice for a line
being used at a terminal);
being dropped or inserted (typical choice for a line being
dropped and inserted at a drop and insert repeater)
Signal Mode.
Configures line format.
Allows user to choose if
line is dropped and
inserted (by selecting
Framed/Unframed) or
passed through or not
used (by selecting
Disabled)
3JK Edition 2.0
1 2 45
SDH Access Card (SDHACC)
Go to next page
O Double left click
3JK Edition 2.0
1 2 46
SDH Access Card (SDHACC)
O Put a check mark in the
Port Status box to enable
the STM-1.
OEnable the J0, if required, by
selecting one of the two modes
(SixteenBytesFrame/
OneRepeatedByte) and in the
Expected Receiving Value field
enter the expected value.
Note: byte J0 is only read, no
Regeneration section
Termination is done.
OSelect the Jitter
Buffer Depth: High/Low
O Enter the Flow ID (range:
2 to 4080). Warning: the
flow id must be unique in
the MPR network.
OSelect the TDM
Clock Source:
Differential/
Node Timing.
O Click Apply button.
O Click on Apply on
the left part.
G Click on Apply on
the right part.
O Set the Auto Laser Shutdown: Enabled/Disabled
ForcedOn/Disabled ForcedOff. This field will
appear only if the Settings tab-panel of the STM-1
unit the optical SFP has been selected.
Flow ID number is system unique and must not be repeated in radio network. Loss of STM-1 data can occur.
3JK Edition 2.0
1 2 47
SDH Access Card (SDHCHAN)
Go to next page
O Double left click
3JK Edition 2.0
1 2 48
Go to next page
O
O
O
O
O
O
[2] Put a check mark in the Port Status box to enable the STM-1.
[3] Set the Auto Laser Shutdown: Enabled/Disabled ForcedOn/Disabled ForcedOff. This field will
appear only if the Settings tab-panel of the STM-1 unit the optical SFP has been selected.
[4] Select the Clock Source.
[5] Enable the J0, if required, by selecting one of the two modes (SixteenBytesFrame/OneRepeated
Byte) in the Expected Receiving Value field and enter the expected value and in the Sending J0
field select one of the two modes and enter the value to be transmitted. Note: byte J0 is only read,
no Regeneration section Termination is done.
[6] Click on Apply.
[7] Enable, if required, the E1 Node Timing Configuration. The Node Timing is the timing from the
network clock as defined in G.8261. The enabling of the Node Timing is applied to all E1s of the unit.
By enabling the Node Timing the E1 streams in Rx side are retimed at the output with the network
element clock.
3JK Edition 2.0
1 2 49
O
O
G
11 16
12
13
15
14
[8] Configure all the E1s to be mapped/demapped in the STM-1. The E1s are identified by a progressive
number from #1 to #63, but also by the standard SDH identification (x-y-z).
The E1 tab-panel performs all available functions for the tributary. To define the involved ports, the
interface selection in the tree view is first required; therefore the selection of the desired tributary port
in the tabular view enables the Resource Detail list to show the available functions for the single one
resource.
[9] Select Settings.
[10] Signal Mode:
The possible values are:
Framed for the collection of the performances at the input in Tx side and at the output in Rx side
Disabled
[11] Click on Apply.
[12] Service Profile:
The possible profiles are:
TDM2TDM
TDM2Eth
[13] Flow Id: To implement cross-connections between line side and radio side each E1 tributary must be
associated to an identifier. Enter the Flow identifier value in the relevant field (possible values: 2 to
4080) and press Apply.
[14] Fields ECID Tx, ECID Rx, Payload Size and TDM Clock Source can be written only if the Service Profile is
TDM2Eth.
Note: The service profile must be the same for all the E1s.
[15] Alarm profile: Not implemented now.
[16] Click on Apply.
3JK Edition 2.0
1 2 50
Modem Card
Go to next page
O Double left click
3JK Edition 2.0
1 2 51
Presetting mode
Mode. Select Presetting from
dropdown list.
Reference. Displays reference
channel spacing based on
capacity and modulation.
Select from dropdown list.
Modulation. Displays modulation
scheme based on reference channel
spacing and capacity.
Capacity. Read Only Field.
PPP RF. Check to enable PPP
RF port. When not checked
(disabled) user cannot change:
Routing IP Protocol
OSPF Area
Remote Address
Alarm Profile. Not managed
Click to enable Open Shortest Path
First protocol then select area
name that has OSPF protocol.
Check to enable radio ID mismatch
function.
Enter number from 1 to 255 for
receiver ID. Must match transmitter
ID at other end of hop.
transmitter ID. Must match associated
receiver ID at other end of hop.
Tick on Enable to enable the
transmission of the SSM message over
the radio channel.
With the Presetting mode the Adaptive modulation is disabled.
3JK Edition 2.0
1 2 52
Shifter. Select the frequency
separation from the Shifter
Data Help list.
Range. Displays range of Tx
RF frequencies that may be
entered.
Tx Mute. Read Only Field.
Status of Local Tx Mute
function.
By clicking on the icon the Alarm
Severity Profile menu opens,
which allows to associate to the
radio channel a specific alarm
profile. Select one Alarm Profile
in the Profile Name list (4 alarm
profiles are listed) and click
Apply. Tick the Show details
check box to see the severity
Remote ATPC Rx Threshold.
Default value is -55 dBm.
ATPC Power Range.
Tx RF Frequency is automatically
entered by ODU when ODU is
connected to MSS. If the ODU is
not connected to the MSS, enter
the Tx RF frequency, within
allowed range.
Read Only Field.
Displays Rx RF frequency.
Result of calculation:
Rx Freq - Tx Freq = Shifter Freq.
ATPC. Check to enable ATPC.
Note: When the Mode is changed from Presetting to Adaptive Modulation, the radio defaults to 14 MHz
bandwidth at 4 QAM. If the capacity of the radio (number of E1 lines cross connected) exceeds the available
capacity of a 14 MHz Channel at 4 QAM, Adaptive Modulation will not enable. It may be necessary to
perform one of the following provisioning changes:
1.Reduce the quantity of E1 lines being transported to meet the required capacity.
2.Increase Reference Channel Spacing.
3JK Edition 2.0
1 2 53
Adaptive Modulation Mode
Modulation Range.
Displays modulation scheme
based on the modulation mode.
Select from the drop down list.
Remote Threshold (dB).
The default level is 0, which corresponds to
threshold. The operator can select
switching levels above threshold (0 to +4 dB
corresponding to threshold level +0 to 4 dB)
or below threshold (0 to -2 dB)
corresponding to threshold level -0 to 2 dB).
Reference Channel Spacing.
Displays reference channel
spacing based on the
modulation mode and the
modulation range. Select from
the drop down list.
Reference Modulation.
Not supported.
Mode. Select from the drop
down list.
3JK Edition 2.0
1 2 54
Manual Operation.
When checked, allows user to select
and test a specific modulation scheme.
Current Modulation.
Read Only Field. Displays
modulation scheme the radio
is currently using.
PPP RF.
Check to enable PPP RF port. When not
checked (disabled) user cannot change:
Routing IP Protocol
OSPF Area
Remote Address
Link Identifier Configuration.
Check to enable radio ID
mismatch function.
Expected Identifier.
Enter number from 1 to 255
for receiver ID. Must match
transmitter ID at other end of
Hop.
Forced Modulation.
Select modulation scheme (one from
the Modulation Range selected) to
test. When activated by the Apply
button, radio is forced to operate
using selected modulation scheme.
Sent Identifier.
for Transmitter ID. Must
match associated receiver ID
at other end of hop.
3JK Edition 2.0
1 2 55
Select the frequency separation
from the dropdown list.
Displays range of TX RF frequencies
that may be entered.
Read Only Field.
Displays RX RF frequency.
Rx Freq - Tx Freq = Shifter
Freq.
Check to enable the muting of
Tx output power.
The Tx Power function allows the
operator to select the transmitter
output power for the 4 QAM
modulation.
Read Only Field.
function.
Tx RF Frequency is
automatically entered by ODU
when ODU is connected to
MSS. If the ODU is not
connected to the MSS, enter
allowed range.
3JK Edition 2.0
1 2 56
MPT Access Card Provisioning
Go to next page
O Double left click
3JK Edition 2.0
1 2 57
Power Source configuration
Mode 1 - QMA (only with MPT-HC)
In this mode the MPT-HC V1 is
power supplied with a dedicated
coaxial cable connected on the
QMA connector on the front panel
of the MPT Access unit.
Mode 2 - PFoE (Power Fixed on
Ethernet)
In this mode the MPT-HC or MPT-MC
are power supplied by using the
electrical Ethernet cable.
Note: To implement this mode with
MPT-HC the Power Extractor must be
installed, near the MPT-HC, to
separate the Ethernet traffic and the
power supply.
Note:
To unprovision an MPT:
perform a Tx Mute;
unprovision the MPT;
remove the power supply.
3JK Edition 2.0
1 2 58
Presetting Mode
Mode. Select Presetting
from dropdown list.
Reference Channel Spacing.
Displays reference channel
spacing based on capacity and
modulation. Select from
dropdown list.
Modulation. Displays modulation
scheme based on reference channel
spacing and capacity.
Capacity. Read Only Field.
PPP RF. Check to enable PPP
RF port. When not checked
(disabled) user cannot change:
Routing IP Protocol
OSPF Area
Remote Address
Alarm Profile. Not supported.
Click to enable Open Shortest Path
First protocol then select area name
that has OSPF protocol. Select from
dropdown list.
Check to enable radio ID mismatch
function.
receiver ID. Must match transmitter
transmitter ID. Must match associated
Tick on Enable to enable the
transmission of the SSM message over
the radio channel.
See note
With the Presetting mode the Adaptive modulation is disabled.
Note: This field is available only with the MPT-HC V2 with the XPIC+RPS external module installed and if in
the Mode area in the Option field a mask with XPIC has been selected.
The XPIC can be configured in 1+0 or 1+1 HSB (no adaptive modulation, no ATPC).
N.B.: NOT ALL the channel spacings and modulation schemes can support the XPIC Configuration.
Select the suitable Polarization: Vertical or Horizontal.
3JK Edition 2.0
1 2 59
Shifter. Select the frequency
separation from the Shifter
Data Help list.
Range. Displays range of Tx
RF frequencies that may be
entered.
Tx Mute. Read Only Field.
function.
By clicking on the icon the
Alarm Severity Profile menu
opens, which allows to
associate to the radio channel
a specific alarm profile. Select
one Alarm Profile in the Profile
Name list (4 alarm profiles are
listed) and click Apply. Tick the
Show details check box to see
the severity associated to each
alarm.
Remote ATPC Rx Threshold.
Default value is -55 dBm.
ATPC Power Range.
allowed range.
Read Only Field.
ATPC. Check to enable ATPC.
Select in the RSL Driving Criteria
field the suitable value. In 1+1
FD and HSB configurations both
the transmitters can be driven by
the lowest or by the highest RLS
values of the two remote
demodulators.
3JK Edition 2.0
1 2 60
Adaptive Modulation Mode
Mode. Select from dropdown list.
Modulation.
Select the lowest modulation scheme.
Reference Channel Spacing. Displays
reference channel spacing based on the
modulation mode and the modulation range.
Select from the dropdown list
Manual Operation. When checked,
allowed user to select and test a specific
modulation scheme.
Choose in the Supported Modulation field
all the modulation schemes to be used with
the Adaptive Modulation. The modulation
schemes (from the lowest to the highest
scheme) must be contiguous.
Note: With MPT-MC max. scheme is 128 QAM.
Current Modulation. Read Onyl Field.
Displays modulation scheme the radio is
currently using.
Forced Modulation. Select modulation
scheme (one from the Modulation Range
selected) to test. When activated by the
Apply button, radio is forced to operate
using selected modulation scheme.
The Remote Switching Threshold field is not
supported.
PPP RF. Check to enable PPP RF port.
When not checked (disabled) user cannot
change: - Routing IP Protocol
- OSPF Area
- Remote Address
Link Identifier Confguration.
Check to enable radio ID mismatch function.
Expected Identifier. Enter number from 1 to
255 for receiver ID. Must match transmitter
Sent Identifier. Enter number from 1 to 255
for transmitter ID. Must match associated
Select the spectral efficiency class to be set
as reference: None, Old ETSI mask or New
ETSI mark.
Not supported in Adaptive Modulation mode
3JK Edition 2.0
1 2 61
from the dropdown list.
Displays range of Tx RF
frequencies that may be entered.
The Tx Power function allows
the operator to select the
transmitter output power of
each modulation scheme. The
default level is the expected
output power. The minimum
and maximum range of each
modulation scheme is shown in
parenthesis (min XX- max YY).
Read Only Field.
Status of Local Tx Mute function.
Check to enable the Tx output
power out of ODU.
allowed range.
Read Only Field.
Select in the RSL Driving
Criteria field the suitable value.
In 1+1 FD and HSB configurations
both the transmitters can be
driven by the lowest or by the
highest RLS values of the two
remote demodulators.
3JK Edition 2.0
1 2 62
1.5 Provision ASAP Card
Go to next page
O Double left click
3JK Edition 2.0
1 2 63
1.5 Provision ASAP Card [cont.]
The configuration of the ASAP unit is divided in four tab-panels:
E1 Layer
IMA Layer
ATM Layer
ATM PW Layer
For the configuration of the tab-panels refer to S3-M1.
3JK Edition 2.0
1 2 64
1.6 Provision EAS Card
O Double left click
O Settings
tab
O Apply the Equipment
Type
O Port #5 to #8 can be configured
to accept an optical SFP.
Configuration the Ethernet ports as explained in S3-M1.
3JK Edition 2.0
1 2 65
1.6 Provision AUX Card
Go to next page
O Double left click
3JK Edition 2.0
1 2 66
1.6 Provision AUX Card [cont.]
The configuration of the AUX unit is divided in two tab-panels:
Settings
External Points
For the configuration of the tab-panels refer to S3-M1.
For the ATM traffic the Traffic Descriptors must be also configured. Refer to Menu Configuration -> Traffic
Descriptors in S3-M1.
3JK Edition 2.0
1 2 67
1.7 Provision XPIC
The XPIC configuration can be implemented only with the MPT-HC V2.
For the configuration refer to S3-M1 chapter 3.8.
3JK Edition 2.0
1 2 68
1.8 Provision Synchronization
All the NEs radios in the network must be synchronized to the same
clock.
One radio in the network is provisioned Master.
All other radios in the network must be provisioned Slave.
The slave radios all sync to the clock provided by the master.
3JK Edition 2.0
1 2 69
1.9 Provision NTP protocol
Enable the NTP (Network
Time Protocol).
Put a check mark in the NTP protocol field to enable the protocol and write in the Main Server address
field the IP address of the server, which is in charge to distribute the time to all the NEs in the network. In
the Spare Server address field write the IP address of the Spare Server, if any.
The Server reachability field is a read-only field, which shows the reachability of the NTP servers. The
following information can appear:
"Main server reachable"
"Spare server reachable"
"None servers reachable"
"Both servers reachable"
Click on Apply to send to the NE the NTP Configuration.
Refresh push-button can be used to update the screen.
3JK Edition 2.0
1 2 70
1.10 Provision NE Time
NE Time Provisioning
O If NPT Protocol is disabled, when
checked, enables function to
synchronize Operating System and
Network Equipment Times.
O
O
O Click to display
pop-up dialog for NE
Time configuration.
The user can synchronize the NE time from either the PC/laptop or Network Time Protocol (NTP) servers.
Time and date provisioning is accomplished using the NE Time Configuration screens.
3JK Edition 2.0
1 2 71
1.11 Provision VLAN
To provision VLAN refer to S3-M1 chapter 3.6.
3JK Edition 2.0
1 2 72
1.12 Provision Cross-connections
The available cross-connections are listed in the next paragraphs:
To create the TDM cross-connections refer to S3_M1 par. 3.6.10.
To create the SDH cross-connections with SDHACC - Transparent mode refer
to S3_M1 par. 3.6.13.
To create the SDH cross-connections with SDHCHAN - Channalized mode refer
to S3_M1 par. 3.6.15.
To create the ATM Cross-connections refer to S3_M1 par. 3.6.17.
To create the LAG-LAG Cross-connections refer to S3_M1 par. 3.6.19.
To create the Ring Cross-connections refer to S3_M1 par. 3.6.21.
3JK Edition 2.0
1 2 73
1.13 Provision AUX Cross-Connections
From the Configuration menu select AUX Cross-Connections.
O Select in the New
Cross-connection
area the first
Termination
Point (this can
be a local
service channel
or a service
channelin a radio
link)
O Select the second
Termination Point
(the cross-
connections are
bi-directional)
O Click on Add.
The new cross-
connection will
appear in the
list
Valid Cross Connections:
Local User Service Cross-Connection
Pass-through User Service Cross-Connection
3JK Edition 2.0
1 2 74
1.14 Provision Ethernet Ring
Refer to S3_M1 chapter 13.
3JK Edition 2.0
1 2 75
1.15 Provision LAG
LAG creation
Go to next page
O O
3JK Edition 2.0
1 2 76
1.16 Provision System
System Setting
Go to next page
O
O
Follow the steps to provision tributary port impedance, quality of service classification, and enter NE MAC
address.
3JK Edition 2.0
1 2 77
System Setting
1.16 Provision System [cont.]
O O
O O
O O
1) Tributary Port Configuration
This field allows to set the suitable impedance of the E1 stream (Unbalanced 75 ohms/Balanced 120 ohm).
To activate the new impedance, click on Apply.
2) Quality Of Service
This field allows to set the suitable Quality Of Service (Disabled/DiffServ/802.1p). To activate the new
value, click on Apply.
The Ethernet switch provides a Quality of Service mechanism to control all streams. If the QoS is disabled,
all traffic inside the switch has the same priority; this means that for each switch port there is only one
queue (FIFO) therefore the first packet that arrives is the first that will be transmitted.
The following values are available:
O IEEE std 802.1p: the packet is examined for the presence of a valid 802.1P user-priority tag. If the tag
is present the correspondent priority is assigned to the packet;
O DiffServ: each packet is classified based on DSCP field in the IP header to determine the priority.
3) DHCP
The DHCP server configures automatically IP address, IP mask and default gateway of the PC Ethernet
interface used to reach the NE. The PC must be configured to get automatically an IP address.
The DHCP server uses an address pool of 10 IP addresses, defined according to the NE TMN port IP address.
The IP mask is set to the mask of the NE TMN port and the default gateway is set to the NE IP address.The
lease time is fixed to 10 minutes.To activate the DHCP server, select Enabled and click on Apply.
3JK Edition 2.0
1 2 78
O G
4) Admission Control for Adaptive Modulation (ODU300 only)
The Admission Control for TDM flows (cross-connected to radio direction working in Adaptive Modulation)
can be enabled or disabled. Default: Enabled.
When the Admission Control is "Enabled", the check is performed taking into account the capacity of the 4
QAM modulation scheme for the relevant Channel Spacing.
Taking as example 28 MHz channel spacing (with around 130 Mbit/s of net throughput available with
64QAM), the maximum number of E1s that could be provisioned is 18; the remaining capacity is devoted to
other types of traffic such as ATM or Ethernet.
When RSL value decreases, modulation schemes are downgraded first from 64QAM to 16QAM: the traffic
with lower priority exceeding 16QAM bandwidth is dropped and of course the E1s are kept. As soon as the
RSL value further decreases, modulation scheme are downgraded to 4QAM and all the traffic exceeding
4QAM bandwidth is dropped (while the E1s are kept). It should be noted that there is no possibility to
provision a number of E1s greater than 18, because being all the E1s with the same priority, it should not
possible from system point of view to decide "which" E1s should be dropped passing from 16QAM to 4QAM.
In order to facilitate provisioning and commissioning operations, a specific admission control check at CT
level has been inserted, avoiding any potential mistakes from the user provisioning a number of E1s that
are not fitting inside 4QAM bandwidth.
When the Admission Control is "Disabled", the check is performed taking into account the capacity of the
highest modulation scheme for the relevant Channel Spacing (64 QAM for 4-16-64 QAM range or 16 QAM for
4-16 QAM range).
It is possible to provision a number of E1s exceeding the 4QAM throughput; always keeping 28 MHz channel
as example, it is possible to provision more than 18E1s, up to 37E1s (value linked with 16QAM capacity). In
this case, when RSL value degrades and modulation scheme is downgraded from 16QAM to 4QAM, all the
TDM traffic is impacted. This feature is answering the need of transmitting an high number of E1s, but
without giving up the benefits of adaptive modulation for Ethernet traffic.
3JK Edition 2.0
1 2 79
11 12
13 14
15 16
5) Ethernet LOS Criteria
By enabling this feature the following additional criteria are added to the Core protection switching criteria:
LOS of Optical User Ethernet interface
Card Fail of SFP optical module
Card Missing of SFP optical module
LOS of any Electrical User Ethernet interfaces, including the LOS of the forth User Ethernet interface working as TMN
Local Ethernet interface.
Note: the default switching criteria are:
Core Card Missing
Core Card Fail
Control Platform operational status failure
Flash Card realignment in progress
Flash Card failure
6) Static Lag Criteria
This feature is available only if the spare Core unit has been installed.
By enabling this feature the Ethernet ports of the Core-E unit in stand-by are in ON state (as the ports of the Active
Core-E unit), but the Ethernet traffic is not forwarded.
This behavior allows to reduce the out of service time of user traffic passing through the User Ethernet interfaces in
case of Core protection switching.
This feature shall not be used, when the NE is connected to an equipment performing Link Aggregation and not
supporting Active/Standby management of aggregated links.
7) Event and Alarm Log
As default the Logging is enabled. If set to "Disabled" the events are not sent to the Event Log Browser application.
8) NE MAC Address
This field is a read-only field, which shows the MAC address of the NE. This MAC address must be used in the cross-
connection with TDM2Eth profile.
3JK Edition 2.0
1 2 80
1.17 Provision Local NE IP Address
Local Configuration
Provisioning
O
O
O Click to display pop-
up dialog for the IP
Configuration
O Enter NE IP address
O Apply the IP Address
Note: After IP address change, the NE restarts.
3JK Edition 2.0
1 2 81
1.18 Provision TMN Ethernet Port
O Double click on the front panel of the Core-E unit in the Equipment menu
O Select the TMN Ethernet
O Select the Setting tab-panel
O Enable TMN Ethernet
O Enter IP address
O Click on the Alarm Profile icon to
open the Alarm Severity Profile menu
to associate to the TMN Ethernet port
a specific alarm profile. Select one
Alarm Profile in the Profile Name list
(4 alarm profiles are listed). Tick the
Show details check box to see the
severity associated to each alarm
O Enter IP Mask and click on Apply
O Select Static Routing for manual
routing. Select OSPF (Open
Shortest Path First protocol) for
automatic routing
Follow the steps to provision TMN Ethernet on the Core-E Card to carry SNMP data.
3JK Edition 2.0
1 2 82
1.19 Provision Ethernet Port 4 for TMN (if required)
O Double click on the front panel of the Core-E unit in the Equipment menu
O Select the Port #4 TMN Ethernet
O Select the Setting tab-panel
O Enable the TMN Port 4
O Enter IP address
O Select Static Routing for manual
routing. Select OSPF (Open
Shortest Path First protocol) for
automatic routing
O Enter IP Mask
and click on
Apply
O Click on the Alarm Profile icon to open the
Alarm Severity Profile menu to associate to
the TMN Ethernet port a specific alarm
profile. Select one Alarm Profile in the
Profile Name list (4 alarm profiles are listed).
Tick the Show details check box to see the
severity associated to each alarm
3JK Edition 2.0
1 2 83
1.20 Provision TMN in-band
O IP address and subnet:
default 10.0.3.2/24 for
interface #1 and 10.0.4.2/24
for interface #2
O VLAN ID: default
1000 for interface
#1 and 1001 for
interface #2
O List of User Ethernet interfaces
where transmit/receive TMN In-
Band traffic: default None
(multiple selection with the mouse
can be done)
O Area ID in case of OSPF protocol
enabled: default 0.0.0.0
OOSPF enable/disable: default disabled
for both interfaces
O Enable
3JK Edition 2.0
1 2 84
1.21 Provision IP Static Routing
IP Static Routing Provisioning
Go to next page
O O
O
O Click to display pop-up
dialog for IP Static Routing
Configuration
Follow the steps to provision.
3JK Edition 2.0
1 2 85
1.21 Provision IP Static Routing [cont.]
IP Static Routing
Provisioning
O Route to a specific
IP address.
O Input IP address.
O IP Mask.
O IP interface to a host
or network. Typically
used at a spur to
interface a host over
the RF path. In this
scenario, the Default
Gateway IP Address is
0.0.0.0 and the IP
Mask (greyed out) is
0.0.0.0. Also typically
used at an end
terminal in a radio link
for interface with the
network.
O List of RF path
directions.
Click to view
drop down
list.
G Create new or change existing IP static routes.
3JK Edition 2.0
1 2 86
1.22 Provision OSPF Static Routing
OSPF Static Routing
Provisioning
O
O
O
O IP Static Routing
Configuration screen.
Click to display pop-up
dialog for OSPF Area
Configuration
Follow the steps to provision Open Shortest Path First (OSPF) protocol static (automatic) routing.
3JK Edition 2.0
1 2 87
2 Provisioning by Provisioning tool
3JK Edition 2.0
1 2 88
O Double click on the mpreSuite310 icon on the Desktop.
O Click on MPR Tools.
2.1 Start Provisioning Tool
3JK Edition 2.0
1 2 89
2.1 Start Provisioning Tool [cont.]
O Double click on the MSS-4/MSS-8 icon.
3JK Edition 2.0
1 2 90
2.1 Start Provisioning Tool [cont.]
O Click on the Provisioning Tool button.
Start provisioning
3JK Edition 2.0
1 2 91
2.2 Provisioning Tool screens
The Provisioning Tool can be used "offline" and "online".
In case of offline, it allows to prepare the provisionning in back office. Minimizing time on field and
mistakes.
With the online mode you can either apply the "offline" configuration or fullfil online.
This tool is recommended for first installation.
Thanks to a step by step approach this tool is easy to handle and allows to minimise time for provisioning
WebEML is more flexible and mandatory to configure AUX and ATM boards (not yet supported in provisioning
tool).
Select:
the direct connection to the NE by putting a check mark on Connect to NE. When you locally connect
the PC to the NE, in the IP Address field automatically (through the autodiscovery) appears the IP Address
of the NE (in the NE the default configuration of the DHCP server is enabled; for this reason your PC must
be configured to obtain an IP Address automatically).
Click on OK.
Note 1: If the DHCP server is disabled, the IP address to be entered is the IP address of the NMS Ethernet
port.
or
the off-line configuration by putting a check mark on Do not connect to NE and by clicking on Apply.
3JK Edition 2.0
1 2 92
2.2 Provisioning Tool screens [cont.]
Opening screen with off-line operation
The buttons present in this screen has the following meaning:
Open: allows opening an existing MCML (XML-based) configuration file. MCML file can contains NE
configuration data and it can be used to fill panels fields and data.
Get: not operative.
Create: allows to create a new configuration file.
Prev: not operative.
Cancel: not operative.
By clicking on the "Open" button a window opens, which gives the possibility to open a configuration file
created in an older version. If an older configuration file is open a new screen appears, which asks to
convert the file.
By clicking on the "Create" button it will be possible to create a file in the current version or in the older
version.
After opening a configuration file, the user will see a configuration preview in order to understand, for
example, if the file is correct and contains the wanted configuration. Click "Next" button from such preview
panel or "Create" button.
3JK Edition 2.0
1 2 93
Opening screen with the direct connection to the NE
The buttons present in this screen has the following meaning:
Open: allows opening an existing MCML (XML-based) configuration file. MCML file can contains NE
configuration data and it can be used to fill panels fields and data.
Get: this button is operative if you are physically connected to the NE and it is used to upload the
configuration from the NE to the tool.
Create: allows to create a new configuration file.
Prev: not operative.
Cancel: not operative.
By clicking on the "Open" button a window opens, which gives the possibility to open a configuration file
created in an older version. If an older configuration file is open a new screen appears, which asks to
convert the file.
By clicking on the "Create" button it will be possible to create a file in the current version or in the older
version.
After opening a configuration file, the user will see a configuration preview in order to understand, for
example, if the file is correct and contains the wanted configuration. Click "Next" button from such preview
panel or "Create" button.
3JK Edition 2.0
1 2 94
Press the Clear Database and Restart NE button and then press Create to create a new configuration or
press Open to open a previously created configuration.
N.B.: If you don't press the Clear Database and Restart NE button at the end of the configuration you can
save the file, but you cannot apply the configuration to the NE. (The Apply button will not be available at
the end of the procedure).
3JK Edition 2.0
1 2 95
2.3 Configuration Options Screen
Protections options
for the Core-E cards
Protections options
for Slot 3 and Slot 4
This screen is a generic one that depicts all of the pull-down options possible depending on which card is
selected in the card slot. Protections options shown are for all cards.
Warning: the Provisioning Tool allows to configue all the units, except the EAS unit, ASAP unit and AUX unit.
(The EAS unit, ASAP unit and the AUX unit must be configured with the LCT).
Warning: To configure the equipment extract the ASAP and/or AUX units, if any.
Note: the SDH unit is available in 2 versions:
O SDHACC (operation in transparent mode)
O SDHCHAN (operation in channalized mode)
Warning: If from this NE remote NEs have to be reached, remember to configure properly the Routing
Protocol of the TMN-RF channel, if the remote NE is connected through the radio link or of the NMS
Ethernet Port, if the remote NE is connected through the Ethernet cable.
Buttons:
Restore: allows to restore in the screen the initial data without any change
Prev: the procedure goes back to the previous step (the changed data may be lost after the Warning
message)
Next: the procedure goes on to the next step (some checks and data storage is done)
Cancel: the procedure goes back to step 1 (Opening screen)
3JK Edition 2.0
1 2 96
2.4 Core-E Configuration
E1 Access
Card Icon
Modem card +
ODU300 icon
When checked this
feature enables input
and output pause
features
Check to enable auto
negotiation
Check to allow communication at data
rate but in only one direction at a time.
Check to allow communication at data
rate in both directions at the same time.
MPT Access card
+ MPT-HC icon
Ethernet
Icon
Enable the Ethernet port by
selecting Transport.
Select MPT-HC or MPT-MC to
connect an MPT.
Note:
A white icon indicates that there are no cross-connections, but cross-connections can be created.
A blue icon indicates the destination is full. The limits granted by the license key have been exceeded. A
message is also displayed stating that no more E1 ports will be accepted.
A green icon indicates that the source and destination are available and the destination can accept more E1
ports.
3JK Edition 2.0
1 2 97
2.4 Core-E Configuration [cont.]
Select Transport if ETH Port 4 on the Core
Card is used to transport Ethernet data.
Select TMN if ETH Port 4 on the Core
Card is used for SNMP data.
Check to select the
operation mode
Select Master or
Slave
Tick to enable the SSM
3JK Edition 2.0
1 2 98
2.4 Core-E Configuration [cont.]
Priority forwarding disabled.
The Quality Of Service feature enables priority
forwarding in the Core-E Card switch based on how
the packets are tagged: not tagged or tagged
802.1p or DiffServ. For general traffic, the packets
are not tagged and QOS can be disabled. The user
has to know if the packets are tagged, and if
tagged 802.1p or DiffServ in order to know which
QOS function to chose.
Each packet is based on DSCP field
in IP header to determine priority.
Each packet is classified based on
presence of valid 802.1p user priority tag.
Check to enable the
optical SFP plug-in
Check to enable the
Admission Control
3JK Edition 2.0
1 2 99
2.5 E1 configuration
Select Unbalance 75 Ohm
if tributary cable is coax.
Select Balance
120 Ohm if
tributary cable
is twisted pair.
Choose TDM2TDM
if radio is being
used to transport
E1 data only (no
Ethernet).
Choose TDM2ETH if radio
is being used to transport
just Ethernet or Ethernet
plus E1 data.
Flow ID is unique
to network. No
two Flow IDs in a
network can be
the same.
Tx Over-the-hop ID
Rx Over-the-hop ID.
Must match Rx/Tx ID
at other end.
The purpose of TMN
Clock Source
provisioning is to
select the mode
that will be used to
sync TDM E1 data to
the node
Synchronization
source. The user
can select one of
two modes:
Adaptive and
Differential.
Select Adaptive to
sync TDM output to
packets.
Select Differential
to sync TDM output
to NE
Synchronization
source.
Note: With the TDM2TDM service profile the TDM Clock source is fixed to Differential (RTP - Real Time
Protocol is used); with the TDM2Eth service profile the TDM Clock source can be Differential (RTP - Real
Time Protocol is used) or Adaptive (RTP is not used). In the unit it is not possible to have mixed
configurations with service profiles using RTP and other service profiles not using RTP. Example: if in the
unit only one E1 has service profile TDM2TDM it is possible to configure other E1 with service profile
TDM2Eth only with the Differential clock source (not with the Adaptive clock source). If the Adaptive clock
source is requested the E1 must be connected to another PDH unit.
3JK Edition 2.0
1 2 100
2.6 STM-1 configuration
SDHACC
Enter the
Expected Value
Select the Jitter
Buffer Depth:
High/Low
Select the TDM Clock
Source:
Differential/Node
Timing
Enter the Flow ID (range:
2 to 4080). Warning: the
flow id must be unique in
the MPR network.
Enable the J0, if required,
by selecting one of the two
modes (SixteenBytesFrame/
OneRepeatedByte) and in
the Expected Receiving
Value field enter the
expected value. Note: byte
J0 is only read, no
Regeneration section
Termination is done.
Set the Auto Laser Shutdown:
Enabled/ Disabled ForcedOn/
Disabled ForcedOff. This
field will appear only if the
Settings tab-panel of the
STM-1 unit the optical SFP
has been selected.
Select the type:
Electrical or Optical
Put a check
mark in the
Port Status
box to enable
the STM-1
3JK Edition 2.0
1 2 101
2.6 STM-1 configuration [cont.]
SDHCHAN
Select the Port type:
SFP-O (Optical) or
SFE-E (Electrical)
Set the Auto Laser Shutdown:
Enabled/Disabled
ForcedOn/Disabled ForcedOff.
This field will appear only if
the Settings tab-panel of the
STM-1 unit the optical SFP has
been selected.
Put a check
mark in the
Port Status
box to enable
the STM-1
Select the
Clock Source
Enable the J0, if
required, by selecting
one of the two modes
(SixteenBytesFrame/On
eRepeatedByte) in the
Expected Receiving
Value field and enter
the expected value and
in the Sending J0 field
select one of the two
modes and enter the
value to be
transmitted.
Note: byte J0 is only
read, no Regeneration
section Termination is
done.
In the Single Tributary Configuration area
configure all the E1s to be mapped/demapped
in the STM-1. The E1s are identified by a
progressive number from #1 to #63.
Note: all the E1s can be configured in one
shot by entering the parameters in the "One
Shot" tributary Configuration.
Enable, if required, the E1 Node Timing
Configuration. The Node Timing is the timing
from the network clock as defined in G.8261.
The enabling of the Node Timing is applied to
all E1s of the unit. By enabling the Node
Timing the E1 streams in Rx side are retimed
at the output with the network element clock.
3JK Edition 2.0
1 2 102
Modem Configuration Screen (without Adaptive Modulation)
2.7 Modem Provisioning
The Revertive Restoration
Criteria are available only
in 1+1 configuration, if
you want traffic on the
protection channel to
automatically switch back
to the main channel when
alarms clear or a switch
command is released.
Check to enable
PPP RF port.
The user can
select:
Static routing or
OSPF Area
Check to enable
radio ID mismatch
function.
for Receiver ID. Must match
associated Receiver ID at
other end of hop.
match associated
Transmitter ID at other end
of hop.
No check mark here.
Select the modulation scheme.
Select the suitable reference
channel spacing.
Transmission over the
radio channel
3JK Edition 2.0
1 2 103
2.7 Modem Provisioning [cont.]
Select the
frequency
separation from
drop-down list.
Select the
modulation scheme
Enter the Tx RF
frequency within
the allowed range.
Check to enable ATPC.
Enter the Tx Power
No check mark here.
Select the suitable
reference channel
spacing
3JK Edition 2.0
1 2 104
Modem Configuration Screen (with Adaptive Modulation)
The Revertive Restoration
Criteria are available only in
1+1 configuration, if you want
traffic on the protection
channel to automatically
switch back to the main
channel when alarms clear or
a switch command is released.
Enable PPP RF port.
The user can select:
Static routing or
OSPF Area
Check to enable radio
ID mismatch function.
for Receiver ID. Must match
associated Receiver ID at
other end of hop.
match associated Transmitter
Enter the Tx Power.
Check mark to enable the Adaptive
Modulation. The only available
configuration is: 1+0, 1+1 HSB.
radio channel
Note 1: With the Adaptive Modulation the only available configuration is: 1+0 or 1+1 HSB.
Note 2: The operator can modify only the 4 QAM field. In this field the operator has to enter the constant
power, which will be used with 4 QAM modulation. The power range is shown on the right side and depends
on the selected reference mode.
The same power value will be used by the 16 QAM and 64 QAM modulation schemes.
3JK Edition 2.0
1 2 105
Select the
frequency
separation
from drop-
down list.
Enter the Tx
RF frequency
within the
allowed range.
Check mark
to enable the
Adaptive
Modulation.
The only
available
configuration
is: 1+0, 1+1
HSB.
Select in the Scheme field the
Modulation range (4/16 QAM
or 4/16/64 QAM) to be used by
the Adaptive Modulation.
spacing.
Select in the Reference
Mode field the spectral
efficiency class to be set
as reference.
Select in the
Thresholds field
how many dB
the switching
thresholds have
to be moved
from the default
value (+4 dB/-2
dB). The default
value is approx.
6 dB below the
10-6 Rx
threshold.
Enter the Tx Power.
3JK Edition 2.0
1 2 106
2.8 MPT Access configuration (1+0)
Enable one or two of
the four ports by
selection the MPT
type: HC or MC:
Port#1 and Port#2 are
electrical Ethernet
ports and Port#3 and
Port#4 are optical
Ethernet ports.
Select the power
supply type: QMA or
PFoE
N.B.: The selection of the Power Supply mode to supply the MPT can be: PFoE (through 1 cable for MPT-MC
or MPT-HC with the DC Extractor) or QMA (through 2 cables for MPT-HC).
3JK Edition 2.0
1 2 107
2.9 MPT Access Provisioning
MPT Access Provisioning (without Adaptive Modulation)
Check to enable PPP RF port.
Static routing or
OSPF Area
Check to
enable radio
ID mismatch
function.
Enter number
from 1 to 255 for
Transmitter ID.
Must match
associated
Transmitter ID at
other end of hop.
Receiver ID. Must match associated
Receiver ID at other end of hop.
No check mark here.
Select in the ETSI mask field
the spectral efficiency class to
be set as reference: None, Old
ETSI mask or New ETSI mask
Select the suitable reference
channel spacing.
Tick to enable
the SSM
Transmission over
the radio channel
See Note
To configure the XPIC go to MPT-HC V2 with XPIC slide.
3JK Edition 2.0
1 2 108
2.9 MPT Access Provisioning [cont.]
Select Tx (Go) and Rx
(Return) separation
frequency from drop-
down list.
Enter the Tx RF frequency
within the allowed range.
Enter the Tx Power
Check mark to enable
ATPC, if required.
3JK Edition 2.0
1 2 109
MPT-HC V2 with XPIC
In the Polarization field
select the polarization
to be used by the radio
channel (Vertical or
Horizontal).
Go in the XPIC
Configuration menu.
3JK Edition 2.0
1 2 110
MPT Access Provisioning (with Adaptive Modulation)
Check to enable
PPP RF port.
The user can
select:
Static routing or
OSPF Area
Check to enable
radio ID
mismatch
function.
Enter number from 1 to
255 for Transmitter ID.
Must match associated
of hop.
Receiver ID. Must match associated
Receiver ID at other end of hop.
Check mark to enable the
Enter the Tx Power
Tick to enable
the SSM
Transmission
over the radio
channel
Choose in the
Supported
Modulation field all
the modulation
schemes to be used
with the Adaptive
Modulation. The
modulation schemes
(from the lowest to
the highest scheme)
must be contiguous.
3JK Edition 2.0
1 2 111
from drop-down list.
Enter the Tx RF frequency
within the allowed range.
spacing.
Select in the Reference Mode field
the spectral efficiency class to be
set as reference.
Select in the ETSI mask field the
spectral efficiency class to be set
as reference.
Enter the Tx Power
3JK Edition 2.0
1 2 112
2.10 MPT Access configuration (prot. enabling: 1+1)
Enable one of the four ports for the
unit on the left side and on the
right side: Port#1 and Port#2 are
electrical Ethernet ports and
Port#3 and Port#4 are optical
Ethernet ports.
Click on Add to enable the
protection scheme
Select the protection scheme:
1+1 HSB, 1+1 FD.
With MPT-MC only 1+1 HSB
Select the Ports used in the
protection scheme
3JK Edition 2.0
1 2 113
2.11 MPT Access Prov. (without A. M.) (1+1)
Select Revertive feature if
you want traffic on the
protection channel to
automatically switch back
to the main channel when
alarms clear or a switch
Check to enable
PPP RF port.
The user can
select:
Static routing or
OSPF Area
Check to
enable radio
ID mismatch
function.
Enter number
from 1 to 255 for
Receiver ID. Must
match associated
Receiver ID at
other end of hop.
Transmitter ID. Must match associated
Transmitter ID at other end of hop.
No check
mark here.
Select the suitable
reference channel spacing.
Tick to enable the SSM Transmission
over the radio channel
See Note
To configure the XPIC go to MPT-HC V2 with XPIC slide.
3JK Edition 2.0
1 2 114
2.11 MPT Access Prov. (without A. M.) (1+1) [cont.]
Select Tx (Go)
and Rx (Return)
separation
frequency from
drop-down list.
Enter the Tx RF
frequency within
the allowed range.
Enter the Tx Power
Check mark to
enable the ATPC,
if required
Select in the ETSI
mask field the
spectral efficiency
class to be set as
reference: None,
Old ETSI mask or
New ETSI mask
3JK Edition 2.0
1 2 115
2.12 MPT Access Prov. (with A. M.) (1+1)
Select Revertive feature
if you want traffic on
the protection channel
to automatically switch
back to the main
channel when alarms
clear or a switch
Check to enable PPP RF port.
Static routing or
OSPF Area
Check to enable radio
ID mismatch function.
Enter number from 1 to
255 for Receiver ID. Must
match associated
Receiver ID at other end
of hop.
match associated
of hop.
Enter the Tx Power.
Check mark to enable the Adaptive
Modulation. The available
configurations are: 1+1 HSB, 1+1
FD.
radio channel
3JK Edition 2.0
1 2 116
2.12 MPT Access Prov. (with A. M.) (1+1) [cont.]
Select the frequency
separation from
drop-down list.
Enter the Tx RF
frequency within
the allowed range.
Choose in the Supported Modulation field all the
modulation schemes to be used with the Adaptive
Modulation. The modulation schemes (from the
lowest to the highest scheme) must be contiguous.
field the suitable channel spacing.
Select in the Reference Mode
field the spectral efficiency
class to be set as reference.
The Remote
Switching
Threshold field
is not
supported.
Select in the ETSI mask field the spectral
efficiency class to be set as reference.
Select in the MSE Driving Criteria
field the suitable value. In 1+1
FD and HSB configurations both
the transmitters can be driven in
a not relevant mode (0) or by
the lowest (1) or by the highest
MSE values (2) of the two remote
demodulators.
3JK Edition 2.0
1 2 117
Master
2.13 Synchronization Configuration
Synchronization Role: Master.
Restoration Criteria:
- Revertive - Switches sync
source back to primary source
after alarm on primary source
clears.
- Non-Revertive - Does not switch
back to primary source after
primary alarm clears and stays on
secondary sync source.
This field will appear, if as Source
(Primary or Secondary) has been
selected the Synch-In port:
1.024 MHz, 2.048 MHz, 5 MHz,
10 MHz.
Synch-Out Port configuration -
Connector that can be used to
provide sync to another radio
or ancillary equipment: 1.024
MHz, 2.048 MHz, 5 MHz,
10 MHz.
3JK Edition 2.0
1 2 118
2.13 Synchronization Configuration [cont.]
This field will appear, if a
Secondary Source has
been selected. Select the
suitable configuration.
Primary source:
- Synch-In Port - Clock from
external source received on
the Sync In connector on the
Core card.
-Any available E1 - Clock
from E1 source via E1
peripheral.
-Any available Synch-E -
Clock from Giga Ethernet
traffic.
- Any available STM-1 port
- Clock from STM-1 source
via STM-1 peripheral.
- Free Run Local Oscillator
- Local oscillator on Core
Card.
Secondary source:
external source received on the
Sync In connector on the Core
card.
- Any available E1 - Clock from
E1 source via E1 peripheral.
- Any available Synch-E - Clock
from Giga Ethernet traffic.
- Any available STM-1 port -
Clock from STM-1 source via
STM-1 peripheral.
- Local oscillator on Core Card.
- None
- No source.
Enter the WTR time in the
range 0-12 minutes at 10
second step. (Default: 5
minutes)
3JK Edition 2.0
1 2 119
Slave
Synchronization
Role: Slave.
This field will appear, if
as Primary Source has
been selected the Rx
Symbol Rate. Select the
radio slot to be used.
Synch-Out Port configuration -
Connector that can be used to
provide sync to another radio
or ancillary equipment: 1.024
MHz, 2.048 MHz, 5 MHz,
10 MHz.
This field will appear, if as Secondary Source has
been selected the Any available E1.
Select the slot number and the E1 tributary number.
3JK Edition 2.0
1 2 120
This field will appear, if as
Source (Primary or Secondary)
has been selected the Synch-In
port: 1.024 MHz, 2.048 MHz,
5 MHz, 10 MHz.
Primary source:
external source received on the
Sync In connector on the Core
card.
- Any available Synch-E - Clock
from Giga Ethernet traffic.
- Rx Symbol Rate - Clock
extracted from the radio side.
Secondary source:
- Synch-In Port - Clock
from external source
received on the
Sync In connector on the
Core card.
- Any available E1 - Clock
from E1 source via E1
peripheral.
- Any available Synch-E -
Clock from Giga Ethernet
traffic.
- Any available STM-1 port
- Clock from STM-1 source
via STM-1 peripheral.
- Rx Symbol Rate - Clock
extracted from the radio
side.
- Local oscillator on Core
Card.
- None
- No source.
3JK Edition 2.0
1 2 121
2.14 XPIC Configuration
In the XPIC
Configuration will
appear in GREEN only
the MPT-HC V2 with a
mask with XPIC (1+0
or 1+1 HSB, no
Adaptive Modulation,
no ATPC) configured
in the Radio menu
and with a suitable
polarization (vertical
or horizontal)
Note: To configure the XPIC refer to S3-M1 chapter 3.8 where the explanation refer to the JUSM menu. The
creation procedure is identical. The only difference is in pushbutton Apply, Refresh and Close: not available
in the Provisioning tool.
3JK Edition 2.0
1 2 122
2.15 Ring Configuration
Note: To configure the Ring refer to S3-M1 chapter 3.6.21 where the explanation refer to the JUSM menu.
The creation procedure is identical. The only difference is in pushbutton Apply, Refresh and Close: not
available in the Provisioning tool.
3JK Edition 2.0
1 2 123
2.16 Cross Connections Configuration
By pressing Alt+W the
Segregated Port View
opens (refer to the
next figure).
Note: To create the Cross-Connection refer to S3_M1 par. 3.5 where the explanation refer to the JUSM
menu. The creation procedure is identical. The only difference is in pushbutton Apply, Refresh and Close:
not available in the Provisioning tool.
3JK Edition 2.0
1 2 124
2.17 Segregated Port Configuration
By pressing Alt+W the
Cross Connection
View opens (refer to
the previous figure).
Note: To segregate the ports refer to S3_M1 par. 3.5 where the explanation refer to the JUSM menu. The
procedure is identical. The only difference is in pushbutton Apply, Refresh and Close: not available in the
Provisioning tool.
3JK Edition 2.0
1 2 125
2.18 802.1D management
When the NE is configured in this
mode (default configuration), the
Ethernet traffic is switched according
to the destination MAC address
without looking the VLAN. The
packets from the user Ethernet ports
having the VLAN ID out the allowed
range (0 and 2-4080) are dropped.
The packets having a VLAN ID already
used for a TDM flow are accepted.
3JK Edition 2.0
1 2 126
2.19 802.1Q management
When the NE is
configured in this mode,
the management of
Ethernet traffic looking
the VLAN is enabled. In
this mode, one VLAN
will be assigned to all
Ethernet frames inside
the MPR network.
VLAN 1 Management
VLAN-ID 1 is automatically defined by the NE when the
802.1Q bridge type is selected. VLAN-ID 1 is shown to the
operator, but it can-not be neither changed nor deleted.
All the user Ethernet ports (enabled and disabled) and all
the radio ports are members of the VLAN 1. In egress
VLAN-ID 1 is always removed from all the ports.
3JK Edition 2.0
1 2 127
2.19 802.1Q management [cont.]
ADD VLan: to create a
new VLAN (refer to VLAN
management figure)
EDIT VLan: to change the
parameters of a VLAN (VLAN
name, VLAN member ports,
VLAN untagged ports in egress).
DEL VLan: to delete a VLAN-ID. It is possible
to remove a VLAN-ID from the VLAN-ID table
even if this VLAN-ID has been already
configured on one or more user ports as Port
VLAN to be added in ingress to untagged
frames. As consequence, the VLAN-ID=1 and
PRI=0 are added to the untagged frames
received on this port. Before applying this
deletion, a confirmation of the operation is
shown to the operator.
By clicking Next the Port VLan
configuration screen opens
3JK Edition 2.0
1 2 128
2.20 VLAN Management
[1] VLAN ID field: Enter the VLAN ID (the configurable values must be in the range 2 - 4080)
N.B.: The VLAN IDs already defined to cross-connect internal flows (i.e. TDM2TDM, TDM2ETH) can-not be
used.
[2] VLAN Name field: Enter the VLAN Name: a text string of up to 32 characters.
N.B.: There is no check on unambiguity name.
[3] VLAN Ports field: Select the ports members of this VLAN by putting a check mark on the relevant check
box. All the user Ethernet ports and all the Radio directions can be considered. Both enabled and disabled
user Ethernet ports (radio ports when declared are implicitly enabled) can be member of a VLAN. This
means that a disabled port can be configured as a member of a VLAN and a port already member of a VLAN
can be disabled continuing to be a member of the same VLAN.
[4] Untagged Ports field: Select, among the ports belonging to this VLAN (members), the untagged ports (in
egress the VLAN will be removed from the frames). Only the user Ethernet ports, enabled and disabled, are
manageable. The VLAN cannot be removed from the radio ports (with the exception of the VLAN 1).
N.B.: The VLAN-ID values allowed are in the range 2 - 4080. By default, for the VLAN IDs defined, all the
ports are members and the Untag flag is set to False, which means all the frames are trans-mitted with
Tag.
N.B.: Tagged frames - If one tagged packet with VLAN-ID X is received on a port which is not member of the
VLAN-ID X, the packet is dropped.
3JK Edition 2.0
1 2 129
2.21 Port VLAN Configuration
The untagged
frames, received
on each user
Ethernet port (port
1 to 4, and port 5
if the optical SFP
plug-in has been
installed and
configured), can
be Accepted or
Discarded.
If the untagged
frames are accepted,
the VLAN-ID and
Priority fields must
be configured. Only
VLAN-ID values
already defined (in
the VLAN
management menu)
can be configured for
this purpose. The
Priority values
allowed are in the
range 0 - 7.
The default Port
VLAN-ID and Priority
values are: VLAN-
ID=1; Priority=0.
VLAN 1 is always
removed, when the
frame is forwarded.
Note: The Port VLan Configuration screen opens only if in the Bridge Configuration screen the 802.1Q
(Virtual Bridge) has been selected.
3JK Edition 2.0
1 2 130
2.22 Network Configuration
Select Static Routing
for manual routing.
Select OSPF (Open
Shortest Path First
Protocol) for automatic
routing.
Enter IP Address for radio.
Enable TMN VLAN
feature on Core-E.
Enter local
IP Address.
3JK Edition 2.0
1 2 131
2.22 Network Configuration [cont.]
Enable the NTP
Protocol.
Enable the IP address of
the Main NTP server.
Enter the
IP address
of the
Spare
(standby)
NTP
server.
Enter the
parameters for
the TMN In-band
management (if
required)
3JK Edition 2.0
1 2 132
2.23 Trusted Managers
The Manager Type cannot be
changed (it is fixed tp 5620
SAM)
The default UDP Port is 5010,
but with a click on this column
another port can be configured
To remove a manager select the
manager from the list and clik on
Remove Manager(s).
The multiple selection of different
managers can be done to remove
more than one manager in one shot.
To activate a trusted manager click on
Add Manager, then click on the IP
Address column and write the IP
address of the SNMP manager.
To confirm the selection click Enter.
A Trusted manager is an SNMP manager to which the NE automatically sends the TRAPS generated inside the
NE.
3JK Edition 2.0
1 2 133
2.24 Typical Report Panel
Buttons:
Prev: the procedure goes back to the previous step
Save: allows to save the configuration file
Apply: it is operative only if you are physically connected to the NE and it activates the download of the
configuration to the NE
Cancel: the procedure goes back to step 1 (Opening screen)
3JK Edition 2.0
1 2 134
Exercise
Configure completely the NEs of the training center by following the
procedure given in this section.
3JK Edition 2.0
1 2 135
Blank Page
3JK Edition 2.0
1 2 136
End of Module
Initial Configuration MPR Node
3JK Edition 2.0
Module 3
Performance Monitoring MPR Node
3JK Edition 2.0
Section 1
NE Operation
3JK Edition 2.0
NE Operation Performance Monitoring MPR Node
1 3 2
Blank Page
First edition External consultant 2007-07-30 01
Document History
3JK Edition 2.0
1 3 3
Objectives
activate and evaluate the Performance Monitoring application.
3JK Edition 2.0
1 3 4
Objectives [cont.]
3JK Edition 2.0
1 3 5
Table of Contents
Page
1 WT Performance Monitoring Suite 7
1.1 Introduction 8
1.2 How to start the WT PMS 9
1.3 Tool bar 12
1.4 Menu bar 14
1.4.1 Export 16
1.4.2 Print 18
1.5 Feature bar area 19
1.6 PM counter view area 20
1.7 How to start and stop the PM 21
1.8 Stop the PM 23
1.9 Offline Mode 24
1.10 PM selectable options 27
1.11 Ethernet Statistics 28
1.11.1 CORE-ENH unit Ethernet Statistics 29
1.11.1.1 Ethernet Aggregate Tx 30
1.11.1.2 Ethernet Aggregate Rx 31
1.11.1.3 Port Custom view 32
1.11.1.4 Example of the other views 33
1.11.2 MPTACC and MD300 Ethernet Statistics 35
1.11.2.1 Queue #1 to Queue #5 38
1.11.2.2 Ethernet Aggregate Tx 39
1.11.2.3 Customized view builder (Aggr.Tx & Queues) 40
1.11.2.4 Example of the other views 41
1.12 RADIO PMs 44
1.12.1 RADIO PMs procedures 47
1.12.2 Radio Custom view 51
1.12.3 Manage Thresholds 52
1.12.4 How to display a threshold 53
1.12.5 How to create a new threshold 54
1.12.6 How to delete a threshold 56
1.12.7 How to associate a threshold 57
1.13 Adaptive Modulation 58
1.13.1 Performance monitoring procedures 59
1.13.2 Adaptive Modulation Custom view 61
1.14 PDH Performance Monitoring 62
1.14.1 P32E1DS1 unit performances 63
1.14.2 Incoming 64
1.14.3 Outgoing 66
1.14.4 Customized view builder 67
1.14.5 Manage Thresholds 68
1.14.5.1 How to create a new threshold table 69
1.14.5.2 How to delete a threshold 70
1.14.5.3 How to associate a threshold 71
1.14.6 Example of the other views 72
1.15 IMA Layer Statistics 74
1.15.1 IMA Group Monitoring 75
1.16 ATM Interface Statistics 78
1.16.1 Interface 79
1.16.1.1 Logical VPs and Not Logical VPs 80
1.17 RSL History 83
Exercise 84
Exercise 85
3JK Edition 2.0
1 3 6
Page
End of Module 86
3JK Edition 2.0
1 3 7
1 WT Performance Monitoring Suite
3JK Edition 2.0
1 3 8
To open the WT Performance Monitoring Suite click on the relevant icon
in the Menu bar as shown in the figure.
The WT Performance Monitoring Suite provides PM measurements for
Ethernet, Radio, PDH, IMA and ATM user lines.
1.1 Introduction
WT Performance Monitoring
Suite icon
3JK Edition 2.0
1 3 9
1.2 How to start the WT PMS
The WT Performance Monitoring Suite can be invoked:
from NEtO by clicking on the WTPMS (WT Performance Monitoring Suite)
button
from the WebEML by clicking the WTPMS (WT Performance Monitoring Suite)
icon in the Tool Bar
from the WebEML in Main menu > Diagnosis > Performance Monitoring
from the WebEML in Main menu > Diagnosis > Summary Block Diagram View
3JK Edition 2.0
1 3 10
1.2 How to start the WT PMS [cont.]
If it is invoked from NEtO the following screen opens.
Insert Login Name (initial) and Password (adminadmin).
3JK Edition 2.0
1 3 11
1.2 How to start the WT PMS [cont.]
The Welcome screen opens.
3JK Edition 2.0
1 3 12
1.3 Tool bar
The Tool bar provides an interface to collect the performance data
from NE network elements and provides the basic functionalities to
collect the performance related statistics and other types of
measurements.
The buttons in the Toolbar have the following functionalities:
Close button removes a NE from the NE list;
Move to front button (not available);
Move to back button (not available);
Sort button (not available);
Background button (not available);
Start/Stop button starts or stops the counters for the data collection,
when the Current Data have been stopped or started;
Refresh button retrieves the current PM reports form NE and update the
table view and chart view with the recently collected data;
Reset button resets the data collection and related counters;
3JK Edition 2.0
1 3 13
1.3 Tool bar [cont.]
Archive button archives in the NM environment the PDH PM and the
Radio PM (only the radio counters);
Collect button forces in the NM environment the PM collection;
Export button saves the report;
Print button prints the user selected performance point;
Offline Mode button saves the current status of the WT Performance
Monitoring Suite to have later the possibility to see the PM offline;
List View to display all the PM counters in a tabular format;
Overview button to display all the PM counters in a graphic format;
Bird's Eye View button displays a selected PM counter in a graphic
format with the possibility to zoom in/out and autorange the graphic and
to navigate in the graphic;
Note button shows the meaning of each parameter;
Help button show help content.
3JK Edition 2.0
1 3 14
1.4 Menu bar
The following menus are available:
File: Export
Print
Offline mode
Exit: closes the application
Edit (this menu is available only in NM environment):
Collect PM: forces the PM collection
Network: List View
Overview
Birds Eye View
Action: Move to front (not available)
Move to back (not available)
Sort (not available)
Background (not available)
Close: removes a NE from the NE list
In the Menu bar are available the same menus present in the Tool bar.
3JK Edition 2.0
1 3 15
1.4 Menu bar [cont.]
Tools: Start/Stop: starts or stops the counters for the data collection,
when the Current Data have been stopped or started
Reset: resets the data collection and related counters
Refresh: retrieves the current PM reports form NE and update
the table view and chart view with the recently
collected data
Archive (this option is available only in NM environment):
archives in the NM environment the PDH PM and the
Radio PM (only the radio counters)
Windows: shows the list of the open windows
Help: shows some information on the Help
3JK Edition 2.0
1 3 16
1.4 Menu bar
1.4.1 Export
This menu allows to export in specific CSV files all the active
performance tables.
By selecting this menu the following screen opens.
Select the directory (or create a new folder) and click on Open.
3JK Edition 2.0
1 3 17
1.4 Menu bar
1.4.1 Export [cont.]
The tables are saved individually in a specific file with IP address of the
NE, slot number of the unit and type of the counter as shown in the
following figure.
3JK Edition 2.0
1 3 18
1.4 Menu bar
1.4.2 Print
3JK Edition 2.0
1 3 19
1.5 Feature bar area
When a Feature bar is selected by a mouse click, it moves to the upper
part of the Feature bar area and below the bar will appear the tree
representation with the equipped slots and the relevant enabled
objects. By clicking on a slot or an object the relevant PM counters will
appear in the PM Counter view area.
The Configuration area, in the power part, depends on the selected
Feature bar. For the explanation of the Configuration area refer to the
relevant Feature bar.
3JK Edition 2.0
1 3 20
1.6 PM counter view area
The PM counters can be displayed in three different views:
List View
Overview
Birds Eye View
In the List View all the available PM counters are shown in the tabular format.
In the List View by using the Custom View tab-panel the view can be customized by enabling the display
of only few counters.
In the Overview all the PM counters are shown in the graphic format in one screen.
In the Birds Eye View the PM counters are shown in the graphic format.
By using the navigation bar in the upper part of the screen a specific port or a specific counter can be
displayed.
As default all the counters, selected through the navigation bars, are displayed, but by deselecting the
check box of a particular counter on the legenda, the relevant counter is removed from the view.
In the lower part of the screen the Default counters and the Elaborated Counters are shown in a tabular
format.
Default Counters: collected on the NE
Elaborated Counters: processed on the PC and available only when the PC is connected to the NE.
By right clicking with the mouse on the graphic the following options will appear:
Copy: to storage the image
Save as: to save the image as .png or .jpeg
Print: to print the image
Zoom In: to enlarge the image
Zoom Out: to shrink the image
AutoRange: to fit the image
3JK Edition 2.0
1 3 21
1.7 How to start and stop the PM
1) Select the type of PM. In the example shown in the figure which follows, Ethernet Statistics has been
selected.
2) Select the slot. The slot selection corresponds to the selection of the unit. In the example which follows
Ethernet Statistics has been selected. The selection of the unit will cause the display of the counters of all
its subordinate objects, i.e. in this example the counters of all equipped ports will be displayed.
3) Optionally, after the selection of the unit, you can select one of its subordinate objects. In this case, only
the selected object is highlighted in the frame area.
N.B.: The PM can be started individually or at slot level.
5) Start the counters by pressing button Stopped. Button Stopped (red-colored) changes appearance and
becomes green. The start time is displayed in the Configuration area (left-lower part of the window).
Note for Ethernet Statistics: before to start the counters, select the collecting Interval and Duration in the
Configuration area. Available collecting Intervals are 5s, 10s, 30s and 60s. The Duration is from 1 hour to 24
hours.
3JK Edition 2.0
1 3 22
1.7 How to start and stop the PM [cont.]
3JK Edition 2.0
1 3 23
1.8 Stop the PM
To stop PM application select the counter and click Stop button. Start
and Stop buttons are shown below.
N.B.: The PM can be stopped individually or at slot level.
3JK Edition 2.0
1 3 24
1.9 Offline Mode
By clicking the Offline button on the Tool-bar the current status of the
WT Performance Monitoring Suite is saved.
Click on Yes to save the current NE status.
Write the archive name and click OK.
3JK Edition 2.0
1 3 25
1.9 Offline Mode [cont.]
The current status is saving.
Close NEtO. Click on the Offline Mode icon on the Desktop.
The screen in figure opens. Select the file and click on OK.
Now the WT Performance Monitoring Suite previously saved open and
you can navigate in all the menus.
3JK Edition 2.0
1 3 26
1.9 Offline Mode [cont.]
Note: the Toolbar and the Menu bar are the same bars of the WTPMS. The only differences are:
Start/Stop and Refresh buttons are not available in the Offline Mode
allows to open another NE in offline mode.
3JK Edition 2.0
1 3 27
1.10 PM selectable options
Several tab-panels can be present:
A - NEs List: it includes all the NEs, which launched the application
B - Specific tab-panel (identified by the NE IP address) for each NE, which launched the application.
By clicking an NE in the NEs List or in the specific NE tab-panel, the available PM will appear.
The following types of Performance Monitoring are available:
Ethernet Statistics
Radio PM
Adaptive Modulation PM
PDH PM
IMA Layer Statistics
ATM Interface Statistics
RSL History
3JK Edition 2.0
1 3 28
1.11 Ethernet Statistics
This option provides Ethernet PM statistical counters.
In the left area select bar Ethernet Statistics. The selected bar is moved to
the upper part of the left tree area.
You can expand the tree view of slots 1-8.
The slot equipped by CORE-ENH unit allows to select the enabled user ports
1-6.
The Ethernet Statistics are available in the Core-ENH unit, in MPTACC unit
and in MD300 unit.
The MPTACC unit is the interface to MPT-HC/MPT-MC.
The MD300 unit is the interface to ODU300.
Note: Stability measurement on Ethernet counters (with duration from few hours to 24 Hours) should be
performed by selecting an high value (60 seconds) as collection time of the performances (refer to
parameter Interval in the Configuration subwindow).
3JK Edition 2.0
1 3 29
1.11.1 CORE-ENH unit Ethernet Statistics
1) From the left-hand side tree execute the suitable selection of the
CORE-ENH unit, to get the display of the counters of all ports.
2) From the Configuration subwindow (lower left side of the window),
select the Interval (the collection time of the performances): 4, 6, 30,
60 seconds. The default value is 4 sec. From the same subwindow
select the Duration of the performance monitor in hour and minutes.
The max. duration is 24 hours.
3) Click on the Start button to start the monitoring.
4) The right-hand area contains the statistic data for the Ports.
Per each port the following tabs are selectable:
Ethernet Aggregate Tx
Ethernet Aggregate Rx
Custom view
N.B.: Ethernet Counters can be displayed in three different modalities:
List View
Overview
Birds Eye View
In the example, the List View is shown. To display the other views select in the Menu bar the view or click
the view on the relevant icon in the Tool bar.
3JK Edition 2.0
1 3 30
1.11.1.1 Ethernet Aggregate Tx
The available performances at port level are (see Port 1 selected in the above figure):
TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet
header characters.
TTF: total number of Ethernet frames transmitted out by the interface.
TDF: total number of Transmitted Ethernet frames, which were chosen to be discarded due to buffer
congestion.
N.B.: Reserved Multicast frames are discarded, but the TDF counter is not incremented.
TTF Unicast: total number of Ethernet Unicast frames transmitted out by the Virtual Ethernet Interface.
TTF Multicast: total number of good packets transmitted by this address that were directed to a multicast
address. This number does not include packets directed to the broadcast address.
TTF Broadcast: total number of good packets transmitted by this address that were directed to the
broadcast address.
3JK Edition 2.0
1 3 31
1.11.1.2 Ethernet Aggregate Rx
The available performances at port level (see Port 1 selected in the above figure):
TRO: total number of octects of Ethernet frames received by the Virtual Ethernet Interface, including
Ethernet header characters.
TRF: total number of Ethernet frames received by the Virtual Ethernet Interface.
TRSEF: total number of errored frames.
TDF: total number of Ethernet frames discarded for congestion.
TRF Unicast: total number of Ethernet Unicast frames received correctly by the Virtual Ethernet
Interface.
TRF Multicast: total number of good packets received that were directed to a multicast address. This
number does not include packets directed to the broadcast address.
TRF Broadcast: total number of good packets received that were directed to the broadcast address. This
number does not include multicast packets.
3JK Edition 2.0
1 3 32
1.11.1.3 Port Custom view
You can customize the view by clicking on tab Custom View.
The customized View Builder box is presented.
The view is divided into two areas:
left area which contains the list of the selectable counters
right area which contains the list of the selected counters
The user can select a counter on the left area and by clicking the upper arrow move it to the right area in
order to customize the counter view.
The opposite operation can be done by selecting the counter in the right area and by clicking the lower
arrow to move it to the left area.
Click on OK button to confirm.
3JK Edition 2.0
1 3 33
1.11.1.4 Example of the other views
Note: Click on the Navigation bar to change the view.
Note: In the buttom 2 tab-panels show the counters:
Deafult Counters: collected on the NE row
Elaborated Counters: processed on the PC and are available only when the PC is connected to the NE.
3JK Edition 2.0
1 3 34
1.11.1.4 Example of the other views [cont.]
3JK Edition 2.0
1 3 35
1.11.2 MPTACC and MD300 Ethernet Statistics
In the figure is shown the screen regarding the MPTACC unit with an MPT-MC connected. The screen for the
MPT-HC is the same. The screen for the MD300 is the same.
N.B.: Ethernet Counters can be displayed in three different modalities:
List View
Overview
Birds Eye View
In the example, the List View is shown. To display the other views select in the Menu bar the view or click
the view on the relevant icon in the Tool bar.
3JK Edition 2.0
1 3 36
1.11.2 MPTACC and MD300 Ethernet Statistics [cont.]
The figure which follows shows examples of selection of a MPTACC unit:
MPTACC in slot #3 refers to a 1+1 configuration
MPTACC in slot #4 refers to a 1+0 configuration
MPTACC in slot #5 refers to a non 1+1 configuration
3JK Edition 2.0
1 3 37
1.11.2 MPTACC and MD300 Ethernet Statistics [cont.]
Per each Direction the following tabs are selectable:
Queue #1 to Queue #5
Ethernet Aggregate Tx
Custom view
Two types of MPT are available:
MPT-HC (High Capacity), up to 256QAM
MPT-HC (Medium Capacity), up to 128QAM
The MPTACC unit has 8 output queues:
Queue 8 is reserved to TDM2TDM traffic.
Queue 7 is reserved to TDM2Eth traffic.
Queue 6 is reserved to TMN traffic.
The remaining 5 queues are reserved to Ethernet traffic. Queue 5 is the highest priority queue.
3JK Edition 2.0
1 3 38
1.11.2.1 Queue #1 to Queue #5
Select the tab of the queue to display. The available performances at queue level (for each queue) are:
TTO: total number of octets of Ethernet frames transmitted out by the Interface, including Ethernet
header characters.
TDF: total number of Transmitted Ethernet frames which were chosen to be discarded due to buffer
congestion.
3JK Edition 2.0
1 3 39
1.11.2.2 Ethernet Aggregate Tx
The available performances at aggregate level are:
TTO: total number of octets of Ethernet frames transmitted out by the
Interface, including Ethernet header characters.
TDF: total number of Transmitted Ethernet frames which were chosen to be
discarded due to buffer congestion.
N.B.: Reserved Multicast frames are discarded, but the TDF counter is not
incremented.
3JK Edition 2.0
1 3 40
1.11.2.3 Customized view builder (Aggr.Tx & Queues)
You can customize the view by clicking on tab Custom View.
The customized View Builder box is presented.
3JK Edition 2.0
1 3 41
1.11.2.4 Example of the other views
Modem unit
3JK Edition 2.0
1 3 42
Birds Eye View - MPT Access unit (Default Counters)
3JK Edition 2.0
1 3 43
Birds Eye View (Elaborated Counters)
3JK Edition 2.0
1 3 44
1.12 RADIO PMs
Two different radio sections can be monitored:
Radio Hop Section: the section between two radio stations inside the
protection section
Radio Link Section: the section identifying the protected section.
The performance monitoring (PM) gives indication on the quality of the service and the levels of the Tx
power and Rx power.
Quality of service PM is performed in accordance with G.826 and G.784.
It is assumed that the quality of the single tributary (E1, ) can be derived from the quality of the
aggregate signal, therefore no dedicated quality of service PM is foreseen on the single tributaries.
Considering one section (see figure), one current register is for 15 min report and one for 24 h report; 96
history data can be stored for 15 min report and 8 history data for 24 h report.
N.B.: The 15 min Performance Monitoring data are stored in the History Data report only if errors have been
occurred.
The 24 h Performance Monitoring data are always stored in the History Data report.
3JK Edition 2.0
1 3 45
1.12 RADIO PMs [cont.]
The performance reports can be of 2 different types:
15 minutes
24 hours
The following description explains the functions to provide the PM
process with a granularity period of 15 min. The same functions are
provided for 24h PM process.
The PM are of HOP or LINK type:
HOP refers to the PM before the RPS switch.
LINK refers to Performance Monitoring after the RPS switch. The current
report can be seen (and configured) and the history log can be seen.
3JK Edition 2.0
1 3 46
1.12 RADIO PMs [cont.]
Two types of counters are supported:
1.Radio Counters
2.Analog Counters
1) The Radio counters are the following:
Errored Seconds
Severely Errored Seconds (N.B.)
Background Block Error
Unavailable Seconds
2) The Analog counter parameters are the following:
Minimum level: minimum power level during the elapsed time
Avarage level: avarage power level during the elapsed time
Maximum level: maximum power level during the elapsed time
N.B.: According to ITU-T G.826 a second is declared Severely Errored Second if it is a second period with
more than 30 % of errored blocks or at least one defect.
3JK Edition 2.0
1 3 47
1.12 RADIO PMs
1.12.1 RADIO PMs procedures
RADIO Performance Monitoring provides quality data regarding the radio
channels.
To the RADIO measurements thresholds can be associated. See
procedure which follows.
Only the quality of the aggregate signal is provided.
In the left area select bar RADIO PM. The selected bar is moved to the upper
part of the left tree area.
Select the slot housing the MD300 or the MPTACC unit.
Select the Direction, in this example Direction #7.1/8.1 (MPT-HC).
Select the granularity tab-panel (15 min/24h). In the example which follows
15 min granularity has been selected.
N.B.: Radio Counters can be displayed in three different modalities:
List View
Overview
Birds Eye View
3JK Edition 2.0
1 3 48
1.12 RADIO PMs
1.12.1 RADIO PMs procedures [cont.]
In the following example, the List View is shown.
To display the other views select in the Menu bar the view or click the view on the relevant icon in the Tool
bar.
1) The following Radio tabs are selectable:
Hop Ch 0 (Spare channel)
Hop Ch 1 (Main channel)
Link (RPS active channel)
3JK Edition 2.0
1 3 49
1.12 RADIO PMs
1) Radio tabs: in the example (refer to the next figure), which follows,
Radio Hop Ch 1 has been selected.
The view contains the following collection data parameters:
Time. It displayes the time of the Performance Monitoring. This time changes after the Auto Refresh.
Elapsed Time. It displays the elapsed time in the current interval of monitoring.
Suppressed Intervals. It displays the number of intervals (reports) suppressed in the History because they
dont have errors.
N.B.: If an interval is suspected, it is highlighted in red. An interval is defined as suspect if at least one of
the following conditions occurs in the collection period:
the elapsed time deviates more than 10 seconds of the nominal time
loss of the Performance Monitoring data in the equipment
performance counters have been reset during the interval.
The displayed counters are:
BBE (Background block Errors)
ES (Errored Seconds)
SES (Severily Errored Seconds)
UAS (Unavailable Seconds)
3JK Edition 2.0
1 3 50
1.12 RADIO PMs
2) Analog tabs: in the example (refer to the next figure), which
follows, Analog Hop Rx Ch #1 has been selected.
The following Analog tabs are selectable:
Analog Hop Tx Ch #0 (Spare channel)
Analog Hop Tx Ch #1 (Main channel)
Analog Hop Rx Ch #0 (Spare channel)
Analog Hop Rx Ch #1 (Main channel)
Analog Link (RPS switch included)
Suppressed Intervals. Not supported.
N.B.: If an interval is suspected, it is highlighted in red. An interval is defined as suspect if at least one of
Minimum level: minimum power level during the elapsed time
Avarage level: avarage power level during the elapsed time
Maximum level: maximum power level during the elapsed time
3JK Edition 2.0
1 3 51
1.12 RADIO PMs
1.12.2 Radio Custom view
You can customize the view by clicking on tab Custom View. The
customized View Builder box is presented.
3JK Edition 2.0
1 3 52
1.12 RADIO PMs
1.12.3 Manage Thresholds
It describes how to display or change or create the thresholds assigned
to Performance Monitoring counters.
There are threshold tables for the HOP and for the LINK.
There are two default thresholds for HOP: Threshold #1 (to be
associated to 15 min report) and Threshold #4 (to be associated to 24
h report).
There are two default thresholds for LINK: Threshold #1 (to be
associated to 15 min report) and Threshold #3 (to be associated to 24
h report).
The user can manage thresholds to be associated to Hop or Link 15min
report or 24h report. The following actions are available, starting from
button Manage Thresholds in the Configuration area:
Thesholds display
Create threshold
Delete threshold
Associate a threshold to a monitoring point
3JK Edition 2.0
1 3 53
1.12 RADIO PMs
1.12.4 How to display a threshold
Click on button Manage Thresholds. The Manage Thresholds subwindow
is displayed.
3JK Edition 2.0
1 3 54
1.12 RADIO PMs
1.12.5 How to create a new threshold
Four threshold tables can be created for the HOP (Threshold #2, #3, #5 and #6).
Two threshold tables can be created for the LINK (Threshold #2 and #4).
Two standard thresholds are available for the HOP (Threshold #1, #4).
Two standard thresholds are available for the LINK (Threshold #1 and #3).
To create a new threshold:
1. Click on Manage Thresholds button. The Manage Threshold subwindow opens.
2. Select HOP or LINK.
3JK Edition 2.0
1 3 55
1.12 RADIO PMs
1.12.5 How to create a new threshold [cont.]
3. Select the Measurement type: 15 min or 24 h.
4. Enter the values for the Low and High thresholds.
5. Click on Create. Automatically the new threshold takes a name with a progressive number. See below the
figure.
3JK Edition 2.0
1 3 56
1.12 RADIO PMs
1.12.6 How to delete a threshold
Only the created thresholds can be deleted. The default thresholds
can be only displayed.
1. Select the Threshold to be deleted and click on Delete button.
3JK Edition 2.0
1 3 57
1.12 RADIO PMs
1.12.7 How to associate a threshold
You can assign the desired theshold to a certain Monitoring Point.
Execute the following steps:
1. From the left-hand side lower Configuration area select the Monitor Point.
2. Select the Collection Period (15 min or 24 h)
3. Select the Threshold. The list of the available thresholds for the previously
selected Monitoring Point is presented by clicking on the down arrow beside
the field name (threshold in this case).
4. Notice that only the thresholds applicable to the selected Monitoring Point
are presented.
5. The Threshold to be selected is identified by a number, in accordance to
the detailed list contained in the upper area of the Manage Thresholds
dialog box.
6. Click on Apply button to confirm the assignment.
3JK Edition 2.0
1 3 58
1.13 Adaptive Modulation
If the Adaptive Modulation has been enabled in the Modem unit for
ODU300 or in the MPT Access unit for MPT, in the WT Performance
Monitoring Suite will appear also the performances regarding the
Adaptive Modulation: these performances show the time during which a
specific modulation scheme has been active.
3JK Edition 2.0
1 3 59
1.13.1 Performance monitoring procedures
In the following example, the List View is shown. To display the other
views, select in the Menu bar the view or click the view on the relevant
icon in the Tool bar.
1. In the left area select bar ADAPTIVE MODULATION PM. The selected bar is moved to the upper part of the
left tree area.
2. Select the slot housing the MD300 or the MPTACC unit.
3. Select the Direction, in this example Direction #1.4 (MPT-HC).
4. Select the granularity tab-panel (15 min/24h). In the example, which follows, 15 min granularity has been
selected.
N.B.: The Counters can be displayed in three different modalities:
List View
Overview
Bird's Eye View
3JK Edition 2.0
1 3 60
1.13.1 Performance monitoring procedures [cont.]
The following tabs are selectable:
AM (Adaptive Modulation)
Custom View
Select AM.
The AM screen will open.
Modulation schemes (from 4 QAM to 256 QAM). It shows (for each modulation scheme) the time during
which a specific modulation scheme has been used.
N.B.: If an interval is suspected, it is highlighted in red. An interval is defined as "suspect" if at least one of
3JK Edition 2.0
1 3 61
1.13.2 Adaptive Modulation Custom view
3JK Edition 2.0
1 3 62
1.14 PDH Performance Monitoring
The PDH Performance Monitoring are available in the P32E1DS1 unit.
3JK Edition 2.0
1 3 63
1.14.1 P32E1DS1 unit performances
Selecting the P32E1DS1 unit, the Performance Monitoring (PM) gives indication
on the quality of the E1 Tributaries, which have been configured as "Framed".
E1 Tributaries, configured as "Framed" are shown in bold; for all the other E1
Tributaries (in grey) the performance are not available, because the relevant
streams are disabled or they have been configured as "Unframed".
Two types of performances are available:
Incoming: performances detected at the input in Tx side.
Outgoing: performances detected at the output in Rx side.
The Quality is performed in accordance with G.826 and G.784.
The performance reports are of 2 different types:
15 minutes
24 hours
The following description explains the functions to provide the Performance
Monitoring process with a granularity period of 15 min. The same functions are
provided for 24h Performance Monitoring process.
Incoming
Outgoing
Customer View
Note: by selecting the unit slot all the PM of the enabled E1s can be started in "one-shot".
Note: 9500MPR is transparent regarding the E1 stream. The CRC is used to detect the quality of the E1
stream.
Note: For a better quality in the Performance Monitoring it is recommended to start up to 128 E1 PM
counters on the same NE. This means 4 counters (Incoming 15 Minutes, Incoming 24 hours, Outgoing 15
Minutes and Outgoing 24 Hours) for 32 E1 streams.
N.B.: The Counters can be displayed in three different modalities:
List View
Overview
Birds Eye View
In the following example, only the List View is shown. To display the other views select in the Menu bar the
view or click the view on the relevant icon in the Tool bar.
3JK Edition 2.0
1 3 64
1.14.2 Incoming
3JK Edition 2.0
1 3 65
1.14.2 Incoming [cont.]
The displayed parameters are:
Time. It displays the time of the Performance Monitoring. This time changes
after the Auto Refresh
Elapsed Time. It displays the elapsed time in the current interval of
Performance Monitoring.
Suppressed Intervals: number of intervals (reports) which are automatically
suppressed, because they dont have errors.
BBE (Background Block Errors)
ES (Errored Second)
SES (Severely Errored Second)
UAS (Unavailable Second).
Note: If an interval is suspected, it is highlighted in red. An interval is defined as Suspect if at least one
of the following conditions occurs in the collection period:
Note: These values refer to the last refresh performed with the Refresh button in the Tool bar.
3JK Edition 2.0
1 3 66
1.14.3 Outgoing
The displayed parameters are:
Time. It displays the time of the Performance Monitoring. This time changes
after the Auto Refresh
Elapsed Time. It displays the elapsed time in the current interval of
Performance Monitoring.
Suppressed Intervals: number of intervals (reports) which are automatically
suppressed, because they dont have errors.
BBE (Background Block Errors)
ES (Errored Second)
SES (Severely Errored Second)
UAS (Unavailable Second).
Note: If an interval is suspected, it is highlighted in red. An interval is defined as Suspect if at least one
of the following conditions occurs in the collection period:
Note: These values refer to the last refresh performed with the Refresh button in the Tool bar.
3JK Edition 2.0
1 3 67
1.14.4 Customized view builder
The user can select a counter on the left area and by clicking the upper
arrow move it to the right area in order to customize the counter view.
The opposite operation can be done by selecting the counter in the
right area and by clicking the lower arrow to move it to the left area.
3JK Edition 2.0
1 3 68
There are two default threshold:
Threshold #1 (to be associated to 15 min report)
Threshold #4 (to be associated to 24 h report).
3JK Edition 2.0
1 3 69
1.14.5.1 How to create a new threshold table
To create a new threshold table:
Click on the Manage Threshold. The E1 Threshold screen will appear.
Select the Measurement type: 15 min or 24 h.
Enter the values for the Low and High thresholds.
Click on Create. Automatically the new threshold takes a name with a
progressive number.
Note: Four threshold tables can be created (Threshold #2, #3 for 15 min report and #5 and #6 for 24 h
report).
3JK Edition 2.0
1 3 70
1.14.5.2 How to delete a threshold
Click on the Threshold to be deleted in the upper area of Manage
Thresholds window.
Click on Delete button to delete the threshold.
Note: Only the created thresholds can be deleted. The default thresholds can be only displayed.
3JK Edition 2.0
1 3 71
1.14.5.3 How to associate a threshold
To associate a Threshold to E1 tributary:
From the left-hand side lower Configuration area select the Monitor Point
(Incoming/Outgoing).
Select the Collection Period (15 min or 24h )
Select the Threshold. The list of the available thresholds for the previously
selected Monitoring Point is presented by clicking on the down arrow beside
the field name (threshold in this case).
Notice that only the thresholds applicable to the selected Monitoring Point
are presented.
The Threshold to be selected is identified by a number, in accordance to the
detailed list contained in the upper area of the Manage Thresholds dialog
box.
Click on Apply button to confirm the assignment.
3JK Edition 2.0
1 3 72
1.14.6 Example of the other views
3JK Edition 2.0
1 3 73
1.14.6 Example of the other views [cont.]
3JK Edition 2.0
1 3 74
1.15 IMA Layer Statistics
The IMA Layer Statistics are available with the A16E1DS1 unit.
3JK Edition 2.0
1 3 75
1.15.1 IMA Group Monitoring
For each configured and active IMA Group the following counters are
available:
Unavail Secs
NeNumFailures
Unavail Secs: counter of the seconds where the IMA group traffic state machine is down.
NeNumFailures: counter of the number of times a failure alarm condition (Config-Aborted, Insufficient-
Links, Config-Aborted-FE, Insufficient-Links-FE, Blocked-FE) has been reported for Near-End IMA Group.
Note: By selecting the slot, no tables will appear.
The quality of IMA Group and Links is evaluated by monitoring IMA Group and Link Counters.
This monitoring is based on IMA standard.
The Counters can be displayed in three different modalities:
List View
Overview
Birds Eye View
3JK Edition 2.0
1 3 76
1.15.1 IMA Group Monitoring [cont.]
For each active IMA link, belonging to an activated IMA Group, the following counters are available:
IMA Violation: counter of errored, invalid or missing ICP cells, except during SES-IMA or UAS-IMA
conditions;
OIF (Out of IMA Frame) anomalies: counter of OIF anomalies, except during SES-IMA or UAS-IMA
conditions;
NeSES (Severly Errored Seconds): counter of one second intervals containing more then 30% of the ICP
cells counted as IMA Violation, or one or more link defects (e.g., LOS, OOF/LOF, AIS, or LCD), LIF
defects, or LODS defects, except during UAS-IMA condition, for Near-End side;
NeUAS (UnAvailable Seconds): counter of the seconds unavailability beginning at the onset of 10
contiguous SES-IMA and ends at the onset of 10 contiguous seconds with no SES-IMA, for Near-End side;
Ne Tx UUS (UnUsable Seconds): counter of unusable seconds declared by the Link State Machine at TX
and RX directions for Near-End side;
Ne Tx failure: counter of the number of times a failure alarm condition has been entered on this link at
Tx direction for Near-End side;
Ne Rx failure: counter of the number of times a failure alarm condition has been entered on this link at
Rx direction for Near-End side.
3JK Edition 2.0
1 3 77
3JK Edition 2.0
1 3 78
1.16 ATM Interface Statistics
The quality of ATM PW Service is evaluated by monitoring the ATM
interface and VP/VC cell counters.
Interface #
Not Logical VPs
Logical VPs
Custom View
The Counters can be displayed in three different modalities:
List View
Overview
Birds Eye View
3JK Edition 2.0
1 3 79
1.16.1 Interface
Select the Interface as shown in figure (Interface #1 has been
selected).
For each configured and active ATM interface the following counters are available:
Received Cells: counter of the number of cells received on the ATM interface.
Transmitted Cells: counter of the number of cells transmitted on the ATM interface.
Inv Header Discarded Cells: counter of the number of cells discarded because of Invalid Header, invalid
VPI or invalid VCI.
3JK Edition 2.0
1 3 80
1.16.1 Interface
1.16.1.1 Logical VPs and Not Logical VPs
In the screen will appear all the configured VP/VC.
In the figure the screen refers to VP #20/VC #201 and VP #20/VC #202.
3JK Edition 2.0
1 3 81
1.16.1 Interface
1.16.1.1 Logical VPs and Not Logical VPs [cont.]
In the figure the screen refers to VP #10/VP #11.
For each active VP, if configured as Termination end-point, and active VC configured over an active ATM
interface, the following counters are available:
Discarded Cells: counter of the total number of valid VP/VC cells discarded by the traffic policing entity.
This includes cells originally received with CLP=0 and CLP=1.
Discarded CLP0 Cells: counter of the total number of valid VP/VC cells received with CLP=0 and
discarded by the traffic policing entity.
Tagged Cells: counter of the total number of valid VP/VC cells tagged by the traffic policing entity from
CLP=0 to CLP=1 and transmitted.
Usage Rx: counter of the total number of valid VP/VC cells received including both CLP=0 and CLP=1
cells. The cells are counted prior to the application of the traffic policing.
Usage Tx: counter of the total number of valid VP/VC cells transmitted including both CLP=0 and CLP=1
cells. The cells are counted prior to the application of the traffic policing.
Usage Rx CLP0: counter of the number of valid VP/VC cells received with CLP=0. The cells are counted
prior to the application of the traffic policing.
Usage Tx CLP0: counter of the number of valid VP/VC cells transmitted with CLP=0. The cells are counted
prior to the application of the traffic policing.
3JK Edition 2.0
1 3 82
The user can select a counter on the left area and by clicking the upper
arrow move it to the right area in order to customize the counter view.
The opposite operation can be done by selecting the counter in the
right area and by clicking the lower arrow to move it to the left area.
3JK Edition 2.0
1 3 83
1.17 RSL History
RSL History performances are not supported in the current release.
3JK Edition 2.0
1 3 84
Exercise
Using the test link described in the following slide,
do the following steps:
1. Enable Performance Monitoring on the NE A and B to
monitor the quality of the path connecting the two
Test Instruments
2. Using the variable attenuator, simulate a link degradation and display the
current and the historical collected data
3JK Edition 2.0
1 3 85
Exercise
B
A
Test
Instr.
Operator 1 Operator 2
VARIABLE
ATTENUATOR
Test
Instr.
3JK Edition 2.0
1 3 86
End of Module
Performance Monitoring MPR Node
3JK Issue 2.0
Module 1
Fault Management
3JK Issue 2.0
Section 2
Maintenance
9500 MPR
3JK Issue 2.0
Maintenance Fault Management
2 1 2
Blank Page
First edition ALU University,
Marcoussis
2010-10-28 01
Document History
3JK Issue 2.0
2 1 3
Module Objectives
Upon completion of this module, you should be able to:
Perform the troubleshooting of the 9500 MPR.
3JK Issue 2.0
2 1 4
Module Objectives [cont.]
3JK Issue 2.0
2 1 5
Table of Contents
Page
1 Fault Management 7
1.1 Troubleshooting 8
1.1.1 Before Going to Site Checklist 9
1.1.2 Troubleshooting Basics 11
1.1.3 Troubleshooting Path Problems 62
1.1.3.1 Path Problems on a Commissioned Link 63
1.1.3.2 Path Problems on a New Link 65
1.1.4 Troubleshooting Configuration Problems 66
1.1.5 Troubleshooting Ethernet Problems 68
1.1.6 Troubleshooting TMN Problems 70
Blank Page 74
2 Failed Equipment Removal and Replacement 75
2.1 MSS-8/MSS-4 Card Removal and Replacement 76
2.2 Core-E Card Removal and Replacement 79
2.3 Flash Card Replacement Procedure 81
2.4 ODU Removal and Replacement 83
2.5 MPT-HC Removal and Replacement 84
2.6 MPT-MC Removal and Replacement 85
End of Module 86
3JK Issue 2.0
2 1 6
Page
3JK Issue 2.0
2 1 7
1 Fault Management
3JK Issue 2.0
2 1 8
1 Fault Management
1.1 Troubleshooting
This section provides guidance on:
Before Going to Site Checklist
Troubleshooting Basics
Troubleshooting Path Problems
Troubleshooting Configuration Problems
Troubleshooting Ethernet Problems
Troubleshooting TMN Problems
3JK Issue 2.0
2 1 9
1.1 Troubleshooting
1.1.1 Before Going to Site Checklist
Where possible, before going to site obtain the following information:
Does the fault require immediate attention?
Determine who is the best-placed person to attend the fault.
Confirm the nature and severity of the reported fault, its location, 9500 MPR
type, frequency band, high/low end ODU, capacity, modulation and
configuration (non protected, protected, diversity). Ask:
Is just one 9500 MPR link affected, or a number of links in the same geographical
area?
Is the path down completely or is traffic passing but with a BER alarm?
Is only one or a number of tributaries affected?
Could the fault be in the equipment connected to 9500 MPR, rather than in 9500
MPR? Are there alarms on other, connected equipment?
Is it a hard or intermittent fault?
Do alarms confirm which end of an alarmed link is faulty?
Could the weather (rain, ice, high wind, temperature) be a factor in the
reported fault?
Note: If the fault suggests a rain fade or other weather related fade condition and it matches the
prevailing weather conditions, do not take any action until the weather abates.
3JK Issue 2.0
2 1 10
1.1 Troubleshooting
1.1.1 Before Going to Site Checklist [cont.]
Does link history suggest any fault trends?
Does the fault history for the link indicate a likely cause?
Is the 9500 MPR link newly installed?
Has there been any recent work done on the link?
Ensure that you have with you:
Appropriate spares. Where an equipment failure is suspected, these should include
replacement cards/plug-ins and ODU. If an ODU is suspected then local/national
climbing safety requirements must be adhered to.
A laptop PC loaded with Craft Terminal, and an Ethernet connection cable. (You
need the 9500 MPR IP address and also the addresses for any remote sites to be
accessed).
If login security has been enabled, you need the 'engineer' password for the local and
also any remote sites to be accessed.
Any special test equipment that may be needed, such as a BER tester.
Toolkit.
Key(s) for access to the site.
3JK Issue 2.0
2 1 11
1.1 Troubleshooting
1.1.2 Troubleshooting Basics
Check front-panel LED indications. These provide summary alarm
indications, which can help narrow down the location and type of
failure.
Where a Status LED on a plug-in is off (unlit), but power to the MSS is
confirmed by LEDs on other plug-ins, check the seating of the affected plug-
in.
Check Main Screen. When logging into 9500 MPR with Craft Terminal,
the opening screen is the Main Screen. Use the information provided to
check for severity and problem type. Refer to table Alarm Matrix for
probable cause and recommended action.
This section provides general guidance on 9500 MPR troubleshooting.
3JK Issue 2.0
2 1 12
1.1 Troubleshooting
1.1.2 Troubleshooting Basics [cont.]
Table Alarm Matrix
continue
Check link partner and cable
between link partner and ETH
1-4 connector
Loss of Ethernet is detected on ETH
1-4 on Core-E Card
Minor Major LOS on Gigabit
ETH Interface
- - Minor Minor PPP IP Fail
between link partner and ETH 4
connector
No Ethernet input signal detected
on ETH 4 on Core-E Card
Minor Minor LOS on ETH TMN
Interface
Provision card Card in slot is not provisioned
(enabled)
Minor N/A Unconfigured
Equipment
Install the plug-in in the SFP
slot
The SFP optional plug-in is
provisioned, but not present
Minor Major SFP missing
alarm
Install Core-E Card in slot Core-E card is missing from slot Minor N/A Card Missing
Install correct configured card Card in slot does not match card
configured in Core-E memory
Minor N/A Equipment
Mismatch
Replace Core-E Card Core-E card failed Minor Major Card Fail Core-E Card
1+1 EPS 1+0
Action Most Probable Cause Configuration/
Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 13
1.1 Troubleshooting
continue
Replace Core-E card On detection of card failure the E1
port, Ethernet port, Radio port
objects emit a communication
Alarm notification showing the
transmission resources are affected
by the equipment failure
Major Major Underlying Resource
Unavailable (URU)
Install correct flash card
for license
Wrong flash card installed on Core-E
Card
Major Major License Mismatch for
Equipment
Provisioned
Check sync source for
errors
Sync clk errors detected at Sync in
port on Core-E Card
Minor Minor Degraded Signal on
Sync Interface
Check sync source and
cable between sync source
and Sync in port
No sync clk detected at Sync in port
on Core-E Card
Minor Minor LOS on Sync
Interface
Wait for downloading to
complete
Status of download Minor Minor Firmware Download
In Progress
Core-E Card
1+1 EPS 1+0
Alarm
Alarm Description Equipment
3JK Issue 2.0
2 1 14
1.1 Troubleshooting
continue
Check for upstream E1 source
for errors
AIS detected by the receive
circuits on one or more E1 lines,
indicating upstream failure
Major Major AIS on PDH Tributary
(RX)
Replace E1 Access Card Low quality sync signal for E1
Access Card
Minor Minor Degraded Signal
Check E1 source and/or cable No E1 input signal detected on
any one or more of 32 lines
Minor Major LOS on PDH
Tributary
Enable card Card is not Enabled on the
Settings screen
Major Major Unconfigured
Equipment
Install E1 Access Card in slot E1 Access Card is missing from
slot
Minor Major Card Missing
Install correct configured card Card in slot does not match Card
Minor Major Equipment Mismatch
Replace E1 Access Card Failure of E1 Access Card Minor Major Card Fail E1 Access
Card
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 15
1.1 Troubleshooting
continue
Replace E1 Access card On detection of card failure the
E1 port objects emit a
communication Alarm
notification showing the
transmission resources are
affected by the equipment failure
Underlying Resource
Unavailable (URU)
E1 Access
Card
complete
In Progress
1. Check/troubleshoot far
end alarms
2. Replace alarmed E1
Access Card
Packets are not being received by
the emulation circuits
Major Major Loss of CESoETH
Frame
Check E1 source AIS detected on one or more E1
lines at input to PDH 32xE1
Access Card
Major Major AIS on PDH Tributary
(TX)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 16
1.1 Troubleshooting
continue
Check STM-1 source RS-TIM (regeneration section trace
identifier mismatch) detected on each STM-
1 channel from external line which is known
as J0 byte in regeneration section overhead
Minor Major Tx Regeneration
section trace
identifier
mismatch (J0)
Check STM-1 source Loss of frame from external line side Minor Major Tx Loss of STM-1
frame (LOF)
Check STM-1 source Loss of STM-1 frame alignment on each
incoming STM-1 channel detected according
to G.783
Minor Major Tx Out of STM-1
Frame (OOF)
Check STM-1 source
and/or cable
No STM-1 input signal detected on any one
or more of 32 lines
Minor Major LOS on STM-1
Tributary
Enable card Card is not Enabled on the Settings screen Major Major Unconfigured
Equipment
Install STM-1 Access
Card in slot
STM-1 Access Card is missing from slot Minor Major Card Missing
Install correct
configured card
Card in slot does not match Card configured
in Core-E memory
Minor Major Equipment
Mismatch
Replace STM-1 Access
Card
Failure of STM-1 Access Card Minor Major Card Fail STM-1 Access
Card
(transparent)
1+1 EPS 1+0
Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 17
1.1 Troubleshooting
continue
Check STM-1 source Managed only if the addressed STM-1
has been configured as primary or
secondary synchronization source
Minor Major Sync Degraded
signal
has been configured as
primary/secondary synchronization
source
Minor Major Sync Fail
Check STM-1 source In the direction from external line,
when the line BER exceeds 5*10-5
Minor Major Tx Excessive BER
(HBER)
Check STM-1 source From external line. The Multiplex
Section Remote Defect Indication
(MS-RDI) is used to return an
indication to the transmit end that
the received end has detected an
incoming section defect or is
receiving MS-AIS
Minor Major Tx Multiplex
section remote
defect indication
(MS-RDI)
Check STM-1 source Multiplex Section AIS (MS-AIS)
specified as all "1"s in the entire
STM-1 from external line, excluding
the STM-1 RSOH
section alarm
indication signal
(MS-AIS)
STM-1 Access
Card
(transparent)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 18
1.1 Troubleshooting
continue
Replace STM-1 Access card On detection of card failure the
STM-1 port objects emit a
communication Alarm notification
showing the transmission resources
are affected by the equipment
failure
Major Major Underlying
Resource
Unavailable (URU)
1. Check/troubleshoot far
end alarms
2. Replace alarmed
Packets are not being received by
the emulation circuits
Major Major Loss of CESoETH
Frame
complete
In Progress
Check STM-1 source In the direction to external line,
Major Major Rx Excessive BER
(HBER)
STM-1 Access
Card
(transparent) Check STM-1 source Multiplex Section AIS (MS-AIS) is
STM-1 to external line, excluding
the STM-1 RSOH
Major Major Rx Multiplex
section alarm
indication signal
(MS-AIS)
Check STM-1 source Loss of frame to external line side Minor Major Rx Loss of STM-1
frame (LOF)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 19
1.1 Troubleshooting
continue
Check STM-1 source RS-TIM (regeneration section trace
identifier mismatch) detected on
each STM-1 channel from external
line which is known as J0 byte in
regeneration section overhead
Minor Major Tx Regeneration
section trace
identifier mismatch
(J0)
Check STM-1 source Loss of frame from external line side Minor Major Tx Loss of STM-1
frame (LOF)
Check STM-1 source Loss of STM-1 frame alignment on
each incoming STM-1 channel
detected according to G.783
Minor Major Tx Out of STM-1
Frame (OOF)
Enable card Card is not Enabled on the Settings
screen
Major Major Unconfigured
Equipment
Check STM-1 source and/or
cable
No STM-1 input signal detected on
any one or more of 32 lines
Minor Major LOS on STM-1
Tributary
Install STM-1 Access Card in
slot
STM-1 Access Card is missing from
slot
Minor Major Card Missing
STM-1 Access
Card
(channalized)
Install correct configured
card
Card in slot does not match Card
Mismatch
Replace STM-1 Access Card Failure of STM-1 Access Card Minor Major Card Fail
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 20
1.1 Troubleshooting
continue
has been configured as
primary/secondary synchronization
source
Minor Major Sync Fail
has been configured as primary or
secondary synchronization source
Minor Major Sync Degraded
signal
Check STM-1 source In the direction from external line,
Minor Major Tx Excessive BER
(HBER)
STM-1 Access
Card
(channalized)
Check STM-1 source From external line. The Multiplex
Section Remote Defect Indication
(MS-RDI) is used to return an
indication to the transmit end that
the received end has detected an
incoming section defect or is
receiving MS-AIS
section remote
defect indication
(MS-RDI)
Check STM-1 source Multiplex Section AIS (MS-AIS)
STM-1 from external line, excluding
the STM-1 RSOH
section alarm
indication signal
(MS-AIS)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 21
1.1 Troubleshooting
continue
STM-1 Access
Card
(channalized)
Check STM-1 source This alarm is raised when 8 to 10
consecutive invalid pointers is received
or 8 to 10 consecutive NDF is received.
The alarm becomes significant and must
be reported if STM-1 LOS, STM-1 LOF ,
STM-1 TIM, MS-AIS, or AU4-AIS alarms
are not present. As consequent
action, any E1 extracted from STM-1
will be replaced with AIS (and then
circuit emulated according the
provisioned settings).
Minor Major Loss of
Administrative Unit
Pointer
(AU4-LOP)
Check STM-1 source The AU4-AIS is specified as all "1"s in
the entire high order path
Administrative Unit. The alarm becomes
significant and must be reported if STM-
1 LOS, STM-1 LOF, STM-1 TIM, or MS-AIS
alarm is not present. As consequent
action, any E1 extracted from STM-1
will be replaced with AIS (and then
circuit emulated according the
provisioned settings).
Minor Major High Order Path
alarm indication
signal (AU4-AIS)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 22
1.1 Troubleshooting
continue
STM-1 Access
Card
(channalized)
Check STM-1
source
The value of H4 byte in VC-4 POH is not in the
range (01H-04H) or H4 multiframe is not
recovered within 'm' VC-4 frames, a LOM defect
shall be declared; 'm' shall be in the range of 8
to 40 and is not configurable. The alarm becomes
significant and must be reported if STM-1 LOS,
STM-1 LOF, STM-1 TIM, MS-AIS, AU4-AIS, AU4-
LOP or VC4-SLM alarms are not present. As
consequent action, any E1 extracted from STM-1
will be replaced with AIS (and then circuit
emulated according the provisioned settings).
Minor Major Loss of Multiframe
of Tributary Unit
(VC4-LOM)
Check STM-1
source
This alarm is raised when the value of C2 byte in
VC-4 POH is different between received VC-4 and
Tx VC-4. The vale of C2 byte should be 0x02 for
E1 mapping for channelized SDH. The alarm
becomes significant and must be reported if STM-
1 LOS, STM-1 LOF , STM-1 TIM, MS-AIS, AU4-AIS or
AU4-LOP alarms are not present. As
consequent action, any E1 extracted from STM-1
will be replaced with AIS (and then circuit
emulated according the provisioned settings).
Minor Major High OrderSignal
Label Mismatch
(VC4 -SLM)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 23
1.1 Troubleshooting
continue
STM-1 Access
Card
(channalized)
Check STM-1 source This alarm is raised when 8 to 10
consecutive invalid pointers is received
or 8 to 10 consecutive NDF is received.
STM-1 TIM,or MS-AIS, AU4-AIS, AU4-LOP,
VC4-LOM VC4-SLM or TU12-AIS alarms
are not present. As consequent action
the relevant E1 will be replaced with
AIS (and then circuit emulated
according the provisioned settings).
Minor Major Loss of Tributary
Unit Pointer
(TU12-LOP)
Check STM-1 source The TU12-AIS is specified as all "1"s in
the entire low order pathTributary Unit.
STM-1 TIM, MS-AIS or AU4-AIS, AU4-LOP,
VC4-SLM or VC4-LOM alarms are not
present. As consequent action, the
relevant E1 will be replaced with AIS
(and then circuit emulated according
the provisioned settings).
Minor Major Low Order Path
alarm indication
signal (TU12-AIS)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 24
1.1 Troubleshooting
continue
STM-1 Access
Card
(channalized)
Check STM-1 source It reports the Alarm Indication Signal
detected on E1 in STM-1 on ingressing
(Tx side) and it is detected according to
G.775-sect.4. The alarm becomes
significant and must be reported if
STM-1 LOS, STM-1 LOF , STM-1 TIM, MS-
AIS , HP-AIS or LP-AIS alarm is not
present.
Minor Major E1 in STM-1 Tx
Alarm Indication
Signal (E1-tx AIS)
Check STM-1 source This alarm is raised when the value of
V5 [bit5-7] in VC-12 POH is different
from the expected value (010:
asyncronous mapping). The alarm
becomes significant and must be
reported if STM-1 LOS, STM-1 LOF ,
STM-1 TIM, MS-AIS, AU4-AIS, AU4-LOP,
VC4-SLM, VC4-LOM, TU12-AIS or TU12-
LOP alarms are not present. As
consequent action the relevant E1 will
be replaced with AIS (and then circuit
emulated according the provisioned
settings)
Minor Major Low Order Path
Signal Label
Mismatch
(VC12-SLM)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 25
1.1 Troubleshooting
continue
Check STM-1 source It reports the loss of frame detected on
each E1 in STM-1 on egressing (Rx side)
and it is detected according ITU-T
G.706-sect.4, and G.706-Annex_B. The
alarm becomes significant and must be
reported if the E1 is configured as
framed and a Loss of CESoETH Frames
or E1-rx AIS alarms are not present. Due
to LOF alarm detection an AIS must be
inserted as consequent action. AIS
insertion: set all '1' on data.
Minor Major E1 in STM-1 Rx Loss
Of Frame (E1-rx
LOF)
STM-1 Access
Card
(channalized)
Check STM-1 source It reports the Alarm Indication Signal
detected on each E1 in STM-1 on
egressing (Rx side) and it is detected
according to G.775-sect.4. The alarm
becomes significant and must be
reported if a Loss of CESoETH Frame
alarm is not present.
Minor Major E1 in STM-1 Rx
Alarm Indication
Signal (E1-rx AIS)
Check STM-1 source Due to Loss-of-CESoETH alarm detection
an AIS is inserted as consequent action.
AIS insertion: set all '1' on data.
Minor Major E1 in STM-1 Loss of
CESoETH Frames
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 26
continue
Check E1 source
and/or cable
Loss of signal on each incoming E1 signal
(detected according to ITU-T G.775-sect.4)
- Major Loss Of Signal
(LOS)
Wait for downloading
to complete
Status of download - Minor Firmware Download
In Progress
Enable card Card is not Enabled on the Settings screen - Major Unconfigured
Equipment
Install ASAP Card in
slot
ASAP Card is missing from slot - Major Card Missing
Install correct
configured card
Card in slot does not match Card configured
in Core-E memory
- Major Equipment
Mismatch
Replace ASAP Card Failure of ASAP Card - Major Card Fail 16E1DS1
ASAP Card
STM-1 Access
Card
(channalized)
Replace STM-1
Access card
On detection of card failure the STM-1 port
objects emit a communication Alarm
notification showing the transmission
resources are affected by the equipment
failure
Major Major Underlying
Resource
Unavailable (URU)
to complete
In Progress
1+1 EPS 1+0
Alarm
1.1 Troubleshooting
3JK Issue 2.0
2 1 27
1.1 Troubleshooting
continue
Check the IMA configuration
of the Far End equipment
Loss of IMA Frame on each
incoming E1 signal, when the E1
port is used as IMA link (detected
according to IMA Standard AF-
PHY-0086.000)
- Major Loss of IMA Frame
(LIF)
16E1DS1
ASAP Card
Check the ATM scrambling of
the Far End equipment
Loss of ATM cell delineation on
each incoming E1 signal, when
the E1 port is used as physical
layer for ATM (detected
according to ITU-T I.432)
- Major Loss of Cell
Delineation (LCD)
Check to CRC4 multiframe
alignment of the Far End
equipment
Loss of frame on each incoming
E1 signal (detected according to
ITU-T G.706-sect.4)
- Major Loss Of Frame (LOF)
Check E1 source Alarm Indication Signal detected
on each incoming E1 signal (Tx
side) (detected according to ITU-
T G.775-sect.4)
- Major Tx Alarm Indication
Signal (Tx AIS)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 28
1.1 Troubleshooting
continue
16E1DS1
ASAP Card
Check the Far End equipment It reports, when the E1 port is
used as IMA link, the OR of other
alarms that are foreseen by IMA
Standard AF-PHY-0086.000:
- RFI-IMA
- Tx-Mis-Connected
- Rx-Mis-Connected
- Tx-Unusable-FE
- Link Rx-Unusable-FE
- Major RDI/Link Failure
Check the synchronization of
the Far End equipment
It reports the event that, when
the E1 port is used as IMA link, it
is not synchronized with the
other links within the IMA group
(detected according to IMA
Standard AF-PHY-0086.000)
- Major Link Out of Delay
Synchronisation
(LODS)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 29
1.1 Troubleshooting
continue
16E1DS1
ASAP Card
Check the Far End equipment It reports, for a configured IMA
Group, the event that its Group
Traffic State Machine is 'down',
that is NE and FE Group State
Machine are both NOT in
"operational" state (IMA Standard
AF-PHY-0086.000)
IMA Group TSFAlarm is also
generated by OR of the following
alarms (IMA Standard AF-PHY-
0086.000):
- Tx-Unusable-FE
- Link Rx-Unusable-FE
- Group Start-up-FE
- Group Config-Aborted
- Group Config-Aborted-FE
- Group Insufficient-Links
- Group Insufficient-Links-FE
- Group Blocked-FE
- Group GR-Timing-Mismatch
- Major IMA Group Trail
Signal Fail (TSF)
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 30
1.1 Troubleshooting
continue
between link partner and
Ethernet connector
Loss of Ethernet is detected - Major LOS on Gigabit ETH
Interface
Provision card Card in slot is not provisioned
(enabled)
- N/A Unconfigured
Equipment
Install correct configured card Card in slot does not match card
- Major Equipment Mismatch
Install EAS Card in slot EAS card is missing from slot - Major Card Missing
Install the plug-in in the SFP
slot
The SFP optional plug-in is
provisioned, but not present
- Major SFP missing alarm
Replace EAS Card EAS card failed - Major Card Fail EAS Card
Replace 16E1DS1 ASAP On detection of card failure the
E1 port objects emit a
communication Alarm
Major Major Underlying Resource
Unavailable (URU)
16E1DS1
ASAP Card
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 31
1.1 Troubleshooting
complete
Status of download - Minor Firmware Download
In Progress
EAS Card
Replace EAS card On detection of card failure the
Ethernet port objects emit a
communication Alarm
- Major Underlying Resource
Unavailable (URU)
Enable fan unit Unit is not Enabled on the
Settings screen
Minor Minor Unconfigured
Equipment
Install fan unit Fan unit is missing from slot Major Card Missing
Replace fan unit Fan failed Major Card Fail Fans Unit
1+1 EPS 1+0
Alarm
3JK Issue 2.0
2 1 32
1.1 Troubleshooting
Modem Card and ODU300 Alarm Matrix
continue
Check/repair IF cable
connection on alarmed
Modem Card
Bad cable connection at
IF in/out connector on
Modem Card
Minor Minor Major PNU Cable Loss
Enable card Card is not Enabled on
the Settings screen
Minor Minor Minor Unconfigured
Equipment
Install Modem Card in
slot
Modem Card is missing
from slot
Minor Minor Major Card Missing
Install correct
configured card
Card in slot does not
match card configured in
Core-E memory
Minor Minor Minor Equipment
Mismatch
Replace Modem Card Modem Card failed Minor Minor Major Card Fail Modem
Card
1+1 FD 1+1 HS 1+0
Action Most Probable Cause
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 33
1.1 Troubleshooting
continue
1.Replace main Modem
Card
2.Replace protect
Modem Card
3.Replace main ODU
4.Replace protect ODU
Delay between main and
protect RF paths
detected
Minor Minor N/A Loss of
Alignment
1.Switch far-end XMTRs
(in a protected
system). If alarm
clears, replace far-end
off-line Modem Card.
2.Check/troubleshoot
far-end alarms
3.Replace alarmed
Modem card
Far-end equipment
problems, RF path
problems, or local
circuit failures have
caused BER to increase
to the point that frames
are being lost
Minor Minor Minor Loss of Radio
Frame
Modem
Card
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 34
1.1 Troubleshooting
continue
No action is required at
this time. Monitor
receive signal for
increased degrading
10E-9 BER detected Minor Minor N/A Early Warning
1. Verify RF path is
clear, antenna is
aligned, and no
existing weather -
related problems
2. Verify RSL is above
RCV threshold. If not
check upstream
transmitter
output/troubleshoot
transmitter
Bit Error Rate threshold
(10E-4) exceeded on
Receiver input circuits
on modem
Minor Minor Major High BER
Replace Modem Card Internal receive circuit
failure
Minor Minor Major Demod
Function Fail
Modem
Card
1+1 FD 1+1
HS
1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 35
1.1 Troubleshooting
continue
Alarm threshold
exceeded on standby
Modem Card after
switching from main to
standby
Minor N/A Major TCA on Radio
Hop
Switch far-end XMTRs
(in a protected
system). If alarm
clears, replace far-end
off-line Modem Card
Alarm threshold
exceeded on standby
Modem Card
Major N/A N/A TCA on Radio
Link
Set numbers at both
ends of hop to match
Link identifier number
provisioned on Modem
Card settings screen is
different from link
identifier number
provisioned at other end
of hop
Major Major Major Link Identifier
Mismatch
Modem
Card
1+1 FD 1+1
HS
1+0
Configuration/Alarm
Alarm
Description
Equipment
TCA Threshold Crossing Alarm
3JK Issue 2.0
2 1 36
1.1 Troubleshooting
continue
Replace Modem Card Low quality sync signal
from Modem Card
Minor Minor Minor Degraded
Signal
to complete
Download status Minor Minor Minor Firmware
Download In
Progress
10 consecutive SES
(unavailable time period)
detected on standby
Modem Card after
switching from admin to
standby
Minor N/A Major UAT on Radio
Hop
Switch farend XMTRs
(in a protected
system). If alarm
clears, replace farend
off-line Modem Card
10 consecutive SES
detected on main Modem
Card
Major N/A N/A UAT on Radio
Link
Modem
Card
1+1 FD 1+1
HS
1+0
Configuration/Alarm
Alarm
Description
Equipment
UAT Un-Available Time
3JK Issue 2.0
2 1 37
1.1 Troubleshooting
continue
Replace Modem Card On detection of card
failure the Radio port
objects emit a
communication Alarm
affected by the
equipment failure
Major Major Major Underlying
Resource
Unavailable
(URU)
Replace Modem Card
with correct card
type
Modem card type does not
match card type stored in
memory on the Core-E
Card flash card
Major Major Major License
Mismatch for
Equipment
Provisioned
Modem
Card
1+1 FD 1+1
HS
1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 38
1.1 Troubleshooting
continue
Re-configure shifter
value
Configured shifter value
not supported by ODU
Minor Minor Major Shifter
Frequency
Mismatch
ODU300
Re-configure TX power
value
Configured TX power
value not supported by
ODU
Minor Minor Minor TX Power
Mismatch
Re-configure frequency Frequency out-of-range
of configured TX
frequency
Minor Minor Major RF Frequency
Mismatch
Replace ODU ODU receiver circuit
failed
Minor Minor Major RCV Function
Fail
Replace ODU ODU does not match
ODU configured in Core-
E memory
Minor Minor Major Equipment
Mismatch
Replace ODU ODU failed Minor Minor Major Card Fail
1+1 FD 1+1
HS
1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 39
1.1 Troubleshooting
to complete
Download In
Progress
1.Replace ODU
2.Replace alarmed
Modem Card
Loss of communication
with ODU
Minor Minor Minor ODU Not
Responding
Download correct
software version
Software version on ODU
does not match software
version on Core
Minor Minor Minor Software
Mismatch
ODU300
1+1 FD 1+1
HS
1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 40
1.1 Troubleshooting
MPT Access Peripheral Card and MPT-HC/MPT-HC V2 Alarm Matrix
continue
Check/repair the cable
connection. If ok,
replace MPT-HC
Power Supply Failure - - Major MPT Power
Supply Failure
Enable card Card is not Enabled on
the Settings screen
- - Minor Unconfigured
Equipment
Install MPT Access
Card in slot
MPT Access Card is
missing from slot
- - Major Card Missing
Install correct
configured card
Card in slot does not
match card configured in
Core-E memory
- - Major Equipment
Mismatch
Replace MPT Access
Card
MPT Access Card failed - - Major Card Fail MPT Access
Card
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 41
1.1 Troubleshooting
continue
Check the cable
connection. If ok,
replace the MPT
Accerss unit
Partial failure of
electrical or optical
cable for the GbEth port
- - Minor Ethernet Link
Error
Check the cable
connection. If ok,
replace the MPT
Accerss unit
Loss of the incoming
Ethernet signal (the
signal is missing) or a
communication problem
with the remote peer
(i.e. the communication
has not been established
for physical problem on
cable or interface -> link
down)
- - Major Loss Of
Ethernet Signal
MPT Access
Card
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 42
1.1 Troubleshooting
continue
Replace MPT-HC MPT-HC receiver circuit
failed
Minor Minor Major RCV Function
Fail
Replace MPT-HC MPT-HC does not match
MPT-HC configured in
Core-E memory
Minor Minor Major Equipment
Mismatch
Replace MPT-HC MPT-HC failed Minor Minor Major Card Fail MPT-HC/
MPT-HC V2
to complete
Download status - - Minor Firmware
Download In
Progress
Check the cable This alarm is active only
when the interface is
selected as Primary or
Secondary
synchronization source
- - Minor Degraded Signal
of the MPT
Ethernet
Interface
MPT Access
Card
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
RCV Receiver
3JK Issue 2.0
2 1 43
1.1 Troubleshooting
continue
Download correct
software version
Software version on MPT-
HC does not match
software version on Core
Minor Minor Minor Software
Mismatch
Change the
modulation
parameters
The modulation
parameters already
configured and stored in
the MPR DB are not
actually supported by MPT
Minor Minor Major Modulation
parameters
Mismatch
Re-configure TX
power value
Configured TX power value
not supported by MPT-HC
Minor Minor Minor TX Power
Mismatch
Re-configure shifter
value
Configured shifter value
not supported by MPT-HC
Minor Minor Major Shifter
Frequency
Mismatch
Re-configure
frequency
Frequency out-of-range of
configured Tx frequency
Minor Minor Major RF Frequency
Mismatch
MPT-HC/
MPT-HC V2
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 44
1.1 Troubleshooting
continue
1. Switch far end
equipment (in a protected
system). If alarm clears,
replace far end off-line
MPT-HC.
2. Check/troubleshoot
far end alarms
3. Replace alarmed MPT-
HC
Far end problems, RF
path problems, or
local circuit failures
have caused BER to
increase to the point
that frames are being
lost
Minor Minor Major Loss of Radio
Frame
complete
Download In
Progress
1. Replace MPT-HC
2. Replace alarmed MPT
Access Card
Loss of
communication with
MPT-HC
Minor Minor Minor MPT-HC Not
Responding
MPT-HC/
MPT-HC V2
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 45
1.1 Troubleshooting
continue
clear, antenna is
aligned, and no existing
weather-related
problems
RCV threshold. If not
check upstream
transmitter
output/troubleshoot
transmitter
(10E-4) exceeded
Minor Minor Major High BER
Replace MPT-HC Internal receive circuit
failure
Minor Minor Major Demod
Function Fail
1. Replace main MPT-
MS
2. Replace protect
MPT-MS
protect RF paths
detected
Minor Minor N/A Loss of
Alignment
MPT-HC/
MPT-HC V2
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 46
1.1 Troubleshooting
continue
Check the radio hop Communication problem
between the local MPT
and the remote MPT for
all the functionalities
requiring a
communication loop
(ATPC, ACM, Pre-
distorsion)
Minor Minor Minor MPT Loop
Communication
alarm
Set numbers at both
provisioned is different
from link identifier
number provisioned at
other end of hop
Major Major Major Link Identifier
Mismatch
this time. Monitor
receive signal for
increased degrading
10E-9 BER detected Minor Minor N/A Early Warning MPT-HC/
MPT-HC V2
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 47
1.1 Troubleshooting
continue
Check the radio hop This alarm can raise if
the addressed Radio
interface has been
configured as
primary/secondary
synchronization source.
It is active if the
frequency of the clock
recovered from radio Rx
signal is mistuned
Minor Minor Minor Sync Degraded
signal
MPT-HC/
MPT-HC V2
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 48
1.1 Troubleshooting
continue
Check the cable For the MPT Coupling
optical port:
- the loss of incoming
Ethernet signal (the
signal is missing);
- a communication
problem with the
alternate MPT (i.e. the
communication has not
been established for
physical problem on
cable or interface -> link
down).
When this alarm is
raised, RPS is not
working
Minor Minor N/A Coupling port
Loss of
Ethernet Signal
MPT-HC/
MPT-HC V2
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 49
1.1 Troubleshooting
continue
Check the cable For the MPT Traffic
optical port, the ratio
between the number of
received errored packets
and the total number of
received packets is
above a given threshold
Minor Minor Minor Traffic port
Link Error
Check the cable For the MPT Coupling
optical port, the ratio
between the number of
received errored packets
and the total number of
received packets is
above a given threshold.
When this alarm is
raised, RPS is not
working
Minor Minor N/A Coupling port
Link Error
MPT-HC/
MPT-HC V2
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 50
1.1 Troubleshooting
continue
Alarm threshold
exceeded on standby
MPT-HC after switching
from main to standby
Minor N/A Major TCA on Radio
Hop
Switch far end
equipment (in a
protected system). If
alarm clears, replace
far end off-line MPT-HC
Alarm threshold
exceeded on standby
MPT-HC
Major N/A N/A TCA on Radio
Link
Check the radio hop The MPT is not able to
lock the air Tx symbol
rate to the NE Clock
Minor Minor Minor MPT Tx Clock
Failure
MPT-HC/
MPT-HC V2
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 51
continue
1.1 Troubleshooting
Check the settings Point to point IP failure Minor Minor Minor PPP IP Fail
Replace MPT-HC Low quality sync signal
from MPT-HC
Minor Minor Minor Degraded Signal
10 consecutive SES
(unavailable time
period) detected on
standby MPT-HC after
switching from admin to
standby
Minor N/A Major UAT on Radio
Hop
Switch far end
equipment (in a
protected system). If
alarm clears, replace
far end off-line MPT-HC
10 consecutive SES
(unavailable time
period) detected on
main MPT-HC
Major N/A N/A UAT on Radio
Link
MPT-HC/
MPT-HC V2
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 52
1.1 Troubleshooting
Chec the cable Loss of signal on the
XPIC interface
N/A Major N/A XPIC cable loss
(only for MPT-
HC V2 with the
RPS+XPIC
external
module
installed
Remove the protection
configuration or modify
the hardware
1+1 configuration has
been provisioned
between the two MPT-
HC or the two MPT-HC
V2, but the RPS or the
XPIC module have not
been deployed. When
this alarm is active, the
Transmitter is muted
Major Major N/A Incompatible
protection
MPT-HC/
MPT-HC V2
1+1 FD 1+1 HS 1+0
Configuration/Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 53
1.1 Troubleshooting
MPT Access Peripheral Card and MPT-MC Alarm Matrix
continue
Re-configure TX power
value
Configured TX power value
not supported by MPT-MC
Minor Minor TX Power
Mismatch
Re-configure shifter value Configured shifter value not
supported by MPT-MC
Minor Major Shifter Frequency
Mismatch
Re-configure frequency Frequency out-of-range of
configured Tx frequency
Minor Major RF Frequency
Mismatch
Replace MPT-MC MPT-MC receiver circuit
failed
Minor Major RCV Function Fail
Replace MPT-MC MPT-MC does not match
MPT-MC configured in Core-E
memory
Mismatch
Replace MPT-MC MPT-MC failed Minor Major Card Fail MPT-MC
1+1 HS 1+0
Alarm
Alarm
Description
Equipment
RCV Receiver
3JK Issue 2.0
2 1 54
1.1 Troubleshooting
continue
complete
Download status Minor Minor Firmware
Download In
Progress
1. Replace MPT-MC
2. Replace alarmed MPT
Access Card
Loss of communication with
MPT-MC
Minor Minor MPT-HC Not
Responding
Download correct
software version
Software version on MPT-MC
does not match software
version on Core
Minor Minor Software
Mismatch
Change the modulation
parameters
The modulation parameters
already configured and
stored in the MPR DB are not
actually supported by MPT
Minor Major Modulation
parameters
Mismatch
MPT-MC
1+1 HS 1+0
Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 55
1.1 Troubleshooting
continue
1. Replace main MPT-HC
2. Replace protect MPT-
HC
protect RF paths detected
Minor Minor Loss of Alignment
Replace MPT-MC Internal receive circuit
failure
Minor Major Demod Function
Fail
1. Switch far end
equipment (in a
protected system).
If alarm clears,
replace far end off-
line MPT-MC.
2. Check/troubleshoot
far end alarms
3. Replace alarmed
MPT-MC
Far end problems, RF path
problems, or local circuit
failures have caused BER to
increase to the point that
frames are being lost
Minor Major Loss of Radio
Frame
MPT-MC
1+1 HS 1+0
Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 56
1.1 Troubleshooting
continue
this time. Monitor receive
signal for increased
degrading
10E-9 BER detected Minor N/A Early Warning
clear, antenna is
aligned, and no
existing weather-
related problems
RCV threshold.
If not check
upstream transmitter
output/troubleshoot
transmitter
(10E-4) exceeded
Minor Major High BER MPT-MC
1+1 HS 1+0
Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 57
1.1 Troubleshooting
continue
Check the radio hop This alarm can raise if the
addressed Radio interface has
been configured as
primary/secondary
synchronization source. It is
active if the frequency of the
clock recovered from radio Rx
signal is mistuned
Minor Minor Sync Degraded
signal
Check the radio hop Communication problem between
the local MPT and the remote
MPT for all the functionalities
requiring a communication loop
(ATPC, ACM, Pre-distorsion)
Minor Minor MPT Loop
Communication
alarm
Set numbers at both
provisioned is different from link
identifier number provisioned at
other end of hop
Major Major Link Identifier
Mismatch
MPT-MC
1+1 HS 1+0
Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 58
1.1 Troubleshooting
continue
Switch far end equipment
(in a protected system). If
alarm clears, replace far
end off-line MPT-MC
10 consecutive SES
detected on main MPT-MC
N/A N/A UAT on Radio
Link
Alarm threshold exceeded
on standby MPT-MC after
switching from main to
standby
N/A Major TCA on Radio Hop
Switch far end equipment
(in a protected system). If
alarm clears, replace far
end off-line MPT-MC
Alarm threshold exceeded
on standby MPT-MC
N/A N/A TCA on Radio Link
Check the radio hop The MPT is not able to lock
the air Tx symbol rate to the
NE Clock
Minor Minor MPT Tx Clock
Failure
MPT-MC
1+1 HS 1+0
Alarm
Alarm
Description
Equipment
3JK Issue 2.0
2 1 59
1.1 Troubleshooting
Check the settings Point to point IP failure Minor Minor PPP IP Fail
Replace MPT-MC Low quality sync signal from
MPT-MC
Minor Minor Degraded Signal
10 consecutive SES
detected on standby MPT-MC
after switching from admin
to standby
N/A Major UAT on Radio Hop MPT-MC
1+1 HS 1+0
Alarm
Alarm
Description
Equipment
continue
3JK Issue 2.0
2 1 60
1.1 Troubleshooting
Check the basics first.
For example, if multiple alarms are present, and these include power supply voltage
or hardware alarms, always check their cause before looking at resultant down-
stream path failure or path warning (signal) alarms.
Similarly, if a path-related failure is indicated (no hardware or software alarms),
investigate the path. Go to the Craft Terminal History screen (15 minute view), to
check supporting data, such as low RSL and incidence of intermittent pre-failure BER
alarms, which if present are evidence of a path-related failure.
Refer to Troubleshooting Path Problems for more information.
Check if symptoms match the alarm.
Alarms reflect the alarm state, but in exceptional circumstances an alarm may be
raised because of a failure to communicate correctly with the alarm source, or a
failure in alarm management processing.
Always check to see if symptoms match the alarm, using LED indications and the
Craft Terminal.
3JK Issue 2.0
2 1 61
1.1 Troubleshooting
Check if recent work may be a cause. Recent work at the site may be a
cause or contributing factor. Check for a configuration change, software
upgrade, power recycling (reboot), or other site work:
Many hardware alarms are only initiated as a loss-of-communications alarm during a
reboot, software upgrade, or reconfiguration. By not being able to communicate with
the MSS, their settings cannot be loaded. The fault may be at the hardware device
(most likely), communications to it, or the MSS.
Hardware/software compatibility alarms will be raised when a new plug-in is
installed that needs a later version of 9500 MPR software.
Hardware incompatible alarms will be raised when a plug-in is installed in a slot that
has been configured for a different plug-in.
MSS before an ODU. If there is doubt about whether a fault is in the MSS or
ODU, always replace the MSS first; it is quicker and easier.
Hot-pluggable. MSS cards are hot-pluggable. There is no need to power-down
before replacing, but traffic will be lost unless the plug-in is protected.
Plug-in restoration time. Ensure adequate time is allowed for services to
resume when a plug-in is replaced.
3JK Issue 2.0
2 1 62
1.1 Troubleshooting
1.1.3 Troubleshooting Path Problems
A path-related problem, with the exception of interference, is
characterized by traffic being similarly affected in both directions.
Generally, if you are experiencing only a one-way problem, it is not a
path problem.
Normally a path problem is signaled by a reduced RSL, and depending on its
severity, a high BER.
Only in worst case situations, such as an antenna knocked out of alignment,
will a path fail completely, and stay that way.
For weather-related problems, such as rain or ducting, the path problem will
disappear as the weather returns to normal.
Note: A path extends from ODU antenna port to ODU antenna port.
3JK Issue 2.0
2 1 63
1.1.3.1 Path Problems on a Commissioned Link
A path problem on an existing link, one that has been operating
satisfactorily may be caused by:
Weather-related path degradation
If BER alarms are fleeting / not permanent and RSL returns to its normal,
commissioned level after the alarm is cleared, rain, diffraction, or multipath fading
is indicated. Rain fade is the likely cause of fade for links 13 GHz and higher.
Diffraction and multipath/ducting for links 11 GHz and lower. If these alarms are
persistent, there could be a problem with the link design or original installation.
Changed antenna alignment or antenna feed problem
If RSLs do not return to commissioned levels after a period of exceptionally strong
winds, suspect antenna alignment.
Also, check the antenna for physical damage, such as may occur with ice-fall. For a
remote-mounted ODU, check its antenna feeder.
New path obstruction
Where all other parameters check as normal, and the path has potential for it to be
obstructed by construction works, view/survey the path for possible new
obstructions.
3JK Issue 2.0
2 1 64
1.1.3.1 Path Problems on a Commissioned Link [cont.]
Interference from other signal sources
Interference usually affects traffic in just one direction. Unlike other path problems,
RSL is not affected. If suspected, check for new link installations at, or in the same
geographical area, as the affected site. Ultimately, a spectrum analyzer may have to
be used to confirm interference, which is not an easy task given the need to connect
directly to the antenna port, after removing the ODU.
3JK Issue 2.0
2 1 65
1.1.3.2 Path Problems on a New Link
For a new link, potential problems can extend to also include:
Incorrect antenna alignment
One or both antennas incorrectly aligned. Refer to Installation alignment procedure.
Mismatching antenna polarizations
Given a typical polarization discrimination of 30 dB, for most links it is not possible
to capture a signal to begin the antenna alignment process.
Incorrect path calculations
If the RSLs are too low or too high, antenna alignment is correct, and Tx power
settings are correct, check the path calculations used to determine the link
performance. A good calculation match is +/- 2 dB. Disagreements in excess of 3 dB
should be investigated.
Reflections
Reflection (path cancellation) problems may not have been picked up at the path
planning stage, particularly if the survey was a simple line-of-sight. If suspected,
resurvey the path.
3JK Issue 2.0
2 1 66
1.1 Troubleshooting
1.1.4 Troubleshooting Configuration Problems
Configuration problems should only occur during the set up of a new
link, or reconfiguration of an existing link. The more common problems
may be broadly categorized as:
Compatibility problems
The two alarms that may activate are Configuration Not Supported, and SW/HW
Incompatible:
Configuration Not Supported: The plug-in installed is not enabled or is incorrect for the
configuration.
SW/HW Incompatible: Typically raised when new hardware is plugged into an existing MSS that
has software from an earlier release. To remove the alarm, compatible 9500 MPR software is
required; install the latest software.
Incorrect circuit connections
No alarms are activated for incorrect circuit connections. An incorrect assignment
means the expected end-to-end circuit connectivity will not happen. Re-check circuit
assignments for all nodes carrying the lost circuit(s)
Take extra care when configuring ring circuits.
3JK Issue 2.0
2 1 67
1.1 Troubleshooting
1.1.4 Troubleshooting Configuration Problems [cont.]
Incorrect ID naming, and commissioning
All traffic-carrying circuits must have a unique flow ID for the cross-connect
capability to operate.
Incorrect/incompatible trib settings
Trib line interface settings incorrect, or line levels incompatible. While no alarm
activates for an incorrect setting, its effect may result in line levels being too low
(LOS alarm), or too high, resulting in a high BER.
3JK Issue 2.0
2 1 68
1.1 Troubleshooting
1.1.5 Troubleshooting Ethernet Problems
The most common Ethernet problems are network and connectivity
related and therefore always check the following first:
for User and NMS ports, verify link partner capability, provisioning, and
connection
for Radio ports, verify the cabling between ODU and MSS.
The LEDs on the Core-E card front panel for each Ethernet connector
are a good indicator of correct connectivity and activity on the
Ethernet port.
This section gives general guidance on troubleshooting problems related to the four Ethernet ports on the
Core-E Card.
3JK Issue 2.0
2 1 69
1.1 Troubleshooting
1.1.5 Troubleshooting Ethernet Problems [cont.]
In order for the green Link LED to light:
1 - Cable must be connected to Ethernet port
2 - Ethernet port must be enabled (provisioned Enabled on MSS Settings
Screen)
3 - Speed and mode (on MSS Settings Screen) must be provisioned the same as
the link partner.
The yellow LED opposite the green on the connector indicates activity
only.
The flashing yellow LED is not an indicator of signal type or quality.
3JK Issue 2.0
2 1 70
1.1 Troubleshooting
1.1.6 Troubleshooting TMN Problems
This section gives general guidance on troubleshooting TMN problems
related to NMS Ethernet ports.
The most common TMN problems are network related and first alert is
normally observed by improper operation at the SNMP master. Always
check the following first:
Verify master is properly registered in NE to receive traps
Verify SNMP version matches system requirements
Verify correct community string and privileges
Verify proper network routing.
Refer to the next table for detailed TMN network troubleshooting.
Core-E Card.
Refer to table Troubleshooting Ethernet Problems on next slides for detail troubleshooting using the
LEDs locally at the alarmed site.
3JK Issue 2.0
2 1 71
1.1 Troubleshooting
1.1.6 Troubleshooting TMN Problems [cont.]
Configure external routers to
allow only network management
related traffic through the
Management network of the
radios. Dynamic route updates
(OSPF) may attempt to reroute
high speed traffic through the TMN
network if a high speed link fails.
4. IP traffic other than network
management traffic being routed
through radio network
Download to fewer radios at a
time.
3. Multiple remote software
downloads in process
Poll the radios more slowly. 2. Polling radios for PM data or
missed alarms too rapidly
There may be too many radios
being managed within a single
region. Split the radio network
management into different regions
and backhaul the traffic for each
region through separate channels.
1. Normal network management
traffic is saturating the
communications channel.
Unusually slow communication in
radio network
Possible Solution Possible Cause Problem
Continue
Core-E Card.
3JK Issue 2.0
2 1 72
1.1 Troubleshooting
Check network connectivity.
Check redundant network paths
and routing. Traceroute (tracert)
is useful for locating path or
routing faults.
2. Communication failure in
network
Register the Manager as a craft
device. Manager registration type
can be changed as needed to type
ct to allow control operation and
then be changed back to nml for
normal operation.
To perform control operations, the
Manager must be registered as a
craft device.
Unable to operate controls using
SNMP
Use the correct write community
string
2. If the TMN Interface is
configured for SNMPv2, the write
community string is probably
wrong.
Use the correct community string. 1. Incorrect community string Can Read SNMP objects but cannot
write to SNMP objects
Register Manager with NE. 1. Manager not registered in NE to
receive traps
No traps being received from NE
Continue
Core-E Card.
3JK Issue 2.0
2 1 73
1.1 Troubleshooting
Use traceroute (tracert) to help
locate for communication path or
routing problems.
Possible communication path
failure or routing failure within
the radio network.
Unable to communicate with the
NE through the radio network
(unable to ping the NE).
Verify community string or
username/ passphrase.
If using SNMPv2, using the wrong
community string
Can ping the TMN Interface but
cannot communicate with the NE
using SNMP, or can only see a few
SNMP objects in the NE.
Core-E Card.
3JK Issue 2.0
2 1 74
Blank Page
3JK Issue 2.0
2 1 75
2 Failed Equipment Removal and
Replacement
3JK Issue 2.0
2 1 76
2 Failed Equipment Removal and Replacement
2.1 MSS-8/MSS-4 Card Removal and Replacement
Never install, change or remove a card without first connecting to the
shelf with an ESD grounding cable. Failure to do so may cause ESD
damage to the cards.
Plug-ins must be withdrawn and inserted using their finger-grip
fastener/pulls. Never withdraw or insert using attached cable(s).
Pulling on the cables may damage the cable, plug-in connector, and/or
plug-in card connector attachment.
When installing a plug-in, ensure its backplane connector is correctly
engaged before applying sufficient pressure to bring the plug-in panel
flush with the front panel. Improper alignment can result in damaged
pins on the backplane connector and/or damage to the plug-in
connector.
All plug-in cards can be removed and installed with power applied.
3JK Issue 2.0
2 1 77
2.1 MSS-8/MSS-4 Card Removal and Replacement [cont.]
All slots must be filled with either a peripheral plug-in card or a blank
panel. Failure to do so will compromise EMC integrity and cooling air
from the fan.
Use extreme caution when connecting or disconnecting the ODU cable
on the Radio Access Card. The shelf battery voltage is present on the
center conductor of the connector. When removing or replacing a Radio
Access Card, withdraw the card or the function from the shelf before
disconnecting the cable to the ODU. Failure to follow these cautions
may cause arcing and/or possible power spikes that could affect traffic
on other links installed at the node.
Removing an in-service card in an unprotected link will cause loss of
traffic. Removing an in-service card in a protected link requires
switching the traffic onto the standby (protection) channel.
3JK Issue 2.0
2 1 78
2.1 MSS-8/MSS-4 Card Removal and Replacement [cont.]
If the main Core-E Card fails, traffic and platform data will switch to
the spare Core-E Card automatically. Do not remove power from the NE
during the removal and replacement of the failed main Core-E Card
without first reviewing/performing the following procedure:
Turn off NE power.
Remove failed main Core-E Card.
Turn on NE power.
Wait for two (2) minutes.
Install replacement Core-E Card.
3JK Issue 2.0
2 1 79
2.2 Core-E Card Removal and Replacement
If the Main Core-E Card in slot 1 fails, traffic/services protection and
control platform protection switches to the spare Core-E Card in slot 2.
Loopbacks and all other manual operations, such as manual switch, tx
mute, will be lost (deactivated). Alarms previously active will be newly
detected and reported via notification, with a new time stamp.
After the removal of a faulty card, when you re-insert the new card,
before re-connecting the Ethernet cables between the Core-E card and
other systems, wait that the Core-E card LED STATUS (S) ends its
flashing activity.
3JK Issue 2.0
2 1 80
2.2 Core-E Card Removal and Replacement [cont.]
Verify the replacement Core-E Card meets the following compatibility
rules:
Main Core-E Card (in slot 1) and Spare Core-E Card (in slot 2) must be the
same type.
Local and far end Core-E Cards must use the same software version, but do
not have to be the same type.
3JK Issue 2.0
2 1 81
2.3 Flash Card Replacement Procedure
First case: Core-E Protected
1) Get a spare FLASH CARD with the same sw-package release and license of the
Main flash.
2) Remove the faulty FLASH CARD from the main Core-E and insert the spare
one.
3) Insert the Core-E with the new FLASH CARD.
4) The MIB (MAIN FLASH) will be automatically aligned with the MIB (SPARE
FLASH).
Second case: Core-E Not Protected
1) Get a spare FLASH CARD with the same sw-package release and license.
2) Remove the faulty FLASH CARD from the main Core-E and insert the spare
one.
3) Insert the Core-E with the new FLASH CARD.
4) Carry-out the RESTORE procedure.
3JK Issue 2.0
2 1 82
ATTENTION
(caution to avoid complete traffic loss)
Do not insert in the system a Flash Card the content of which is unknowned.
You must be aware that, if a Flash Card with SW information different from
that running in the system is inserted as it is, the software download will
be automatically carried out from the Flash Card toward the System, thus
causing a complete system crash.
2.3 Flash Card Replacement Procedure [cont.]
NOTE
The license of the Spare Flash card can be different from the license of the Main
Flash card.
Only the license of the Main Flash card manages the NE.
By changing the Main Flash card, also the MAC address changes: in this case the
cross-connection must be reviewed.
3JK Issue 2.0
2 1 83
2.4 ODU Removal and Replacement
Get a spare unit with the same P/N.
Disconnect the MSS-ODU cable.
Change the ODU.
Reconnect the MSS-ODU cable.
Check with the CT that there are no alarms.
Note for 1+1 configurations:
before replacing the ODU make sure that the traffic is transmitted over the other channel. Otherwise,
force with the CT the traffic onto the other channel.
3JK Issue 2.0
2 1 84
2.5 MPT-HC Removal and Replacement
Disconnect the cables and the co-box from the MPT-HC to be replaced
and connect them to the spare MPT-HC.
Reconfigure the MPT by using the WebEML (menu Commissioning >
Configuration) or if a backup file is available, restore the MPT
configuration by the WebEML (menu Commissioning > Configuration >
Backup/Restore).
3JK Issue 2.0
2 1 85
2.6 MPT-MC Removal and Replacement
Disconnect the cables and connect them to the spare MPT-MC.
Reconfigure the MPT by using the WebEML (menu Commissioning >
Configuration) or if a backup file is available, restore the MPT
configuration by the WebEML (menu Commissioning > Configuration >
Backup/Restore).
3JK Issue 2.0
2 1 86
End of Module
Fault Management
3JK Issue 2.0
Module 2
Software Download
3JK Issue 2.0
Section 2
Maintenance
9500 MPR
3JK Issue 2.0
Maintenance Software Download
2 2 2
Blank Page
First edition ALU University,
Marcoussis
2010-10-28 01
Document History
3JK Issue 2.0
2 2 3
Module Objectives
Upon completion of this module, you should be able to:
Download a new software version.
3JK Issue 2.0
2 2 4
Module Objectives [cont.]
3JK Issue 2.0
2 2 5
Table of Contents
Page
1 MPR Node Software Download Menu 7
1.1 Server Access Configuration 8
1.2 Init Software Download 9
1.3 Software Status 10
1.4 How to upgrade the software from an older version 12
Blank Page 13
End of Module 14
3JK Issue 2.0
2 2 6
3JK Issue 2.0
2 2 7
1 MPR Node Software Download Menu
3JK Issue 2.0
2 2 8
This menu allows to configure the FTP server to be used to download
the SWP to the NE.
Copy the ECT directory present in the SWP CD on the FTP server.
Server access configuration screen
1.1 Server Access Configuration
User Id and Password are the login information to access the FTP server.
In the Address field write the IP address of the FTP server.
In the Port field write the port to be used and in the Root Directory field write the FTP server directory
name from which the software can be downloaded.
By clicking on the Set Default button, the server access values will be filled in automatically with the
default configuration.
The CT is the default FTP server with the following parameters:
User Id: anonymous
Password: -
Address: local host IP address.
Port: 21
Root Dir: /
N.B. the System Default can be changed by writing different values in the fields and then by clicking
on button OK.
3JK Issue 2.0
2 2 9
Through this menu the software is downloaded to the NE in order to
upgrade the NE software version.
Init Software Download screen
1.2 Init Software Download
Follow the steps to perform this procedure:
1. Click Add to add the available software packages on the PC.
2. Browse to the directory where the NE software was installed and click Open.
3. Highlight the description file (i.e. R95M.DSC) and click Open.
4. Highlight the line and click on the Init Download button.
The Forced check box can be used to force download (i.e. the complete description file is downloaded
to the NE).
5. Click Yes to begin the download process.
6. When the SW download starts, a screen showing the in progress operation of the download appears. The
download is aborted if the Abort button is pressed.
7. Click Ok.
Recommended operation: Before to start the software download it is recommended to disable the
ATPC operation (if it has been enabled) and to set in RTPC mode the max.
Tx power.
Warning: if the Software Download is in progress and more managers are connected to the same NE,
the WebEML makes grey the Init Download button to save the NE from contemporary and
concurred downloads.
3JK Issue 2.0
2 2 10
Software Status screen
1.3 Software Status
By clicking on the Software Unit
Status button a software unit status
screen opens (see on the next page)
and gives additional information on
the software package.
This menu gives the information of the software installed in the NE.
The following information is displayed:
Name: software name
Version: software version
Operational state: enabled or disabled
Current status: committed or standby
The committed status refers to the software currently in use
Note: With MPT-HC the Sw Status is available only after the MPT-HC software download completion.
Note: The equipment software is installed on the compact flash, which has two banks.
This screen has two panels (each for one bank):
panel 1 refers to bank 1 with the Committed software and relevant information;
panel 2 refers to bank 2 with the Stand by software and relevant information.
The Flash Card, which stores the NE software, contains 2 banks.
The 2 banks can store 2 different software versions. One bank will be committed (active) and the other
bank will be standby.
Note: The second bank appears when a new software package has been downloaded the first time.
During download, necessary to update the software version, the download file is automatically stored in
the standby bank.
To activate the new version first check the operational status of the standby bank. If the status is enabled
(this means that download took place without errors) select Activation or Forced Activation in the Software
Management Action field and click on the Apply Action button.
By selecting Forced Activation the bank to be activated is forced to restart.
By selecting Activation the bank to be activated restarts only if the content of the two banks differ.
3JK Issue 2.0
2 2 11
By clicking on the Software Units Status button a screen opens, giving
additional information on the software package.
The following information is displayed on the screen:
MDPAR: firmware version of the FPGA involved in the MSS/ODU
communication channel
OC_R: software on the ODU300 Controller (ODU300)
BOMPT, FDUSU, FMPVG, SWMPT, PAMPT, FADAM: FPGA firmware version
(MPT)
The other software packages are the FPGA softwares in the other units.
1.3 Software Status [cont.]
3JK Issue 2.0
2 2 12
1.4 How to upgrade the software from an older version
Start the SW Download on the Standby bank
Activate the Standby bank by pressing Activation and Apply Action on
the SW Status menu
Start again the SW Download on the Standby bank
Activate the Standby bank by pressing Activation and Apply Action on
the SW Status menu
3JK Issue 2.0
2 2 13
Blank Page
3JK Issue 2.0
2 2 14
End of Module
Software Download
@@COURSENAME - Page 1
@@COURSENAME
@@PRODUCT
1
Last But One Page
@@COURSENAME - Page 2
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

9500MPR R. 3.1 Node Configuration Operation and Maintetance

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

9500MPR R. 3.1 Node Configuration Operation and Maintetance

Uploaded by

Copyright:

Available Formats

9500MPR (Microwave Packet Radio) (ETSI) R 3.

1 Node Configuration O&M -

Section 1 Module 1 Page 1

You might also like